1 / 30

A (Web) Service-Oriented Approach to Teaching CS/IS1 Billy Lim, Bryan Hosack, Paul Vogt

A (Web) Service-Oriented Approach to Teaching CS/IS1 Billy Lim, Bryan Hosack, Paul Vogt School of Information Technology Illinois State University. Project Personnel Workshop Participants. Introductions. Schedule. Project Overview/Experience Report (9:00-10:15am)

cosmo
Télécharger la présentation

A (Web) Service-Oriented Approach to Teaching CS/IS1 Billy Lim, Bryan Hosack, Paul Vogt

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. A (Web) Service-Oriented Approach to Teaching CS/IS1 Billy Lim, Bryan Hosack, Paul Vogt School of Information Technology Illinois State University

  2. Project Personnel Workshop Participants Introductions

  3. Schedule • Project Overview/Experience Report (9:00-10:15am) • Hands-On Exercises (10:30am-12:00pm) • Lunch (12:00-1:00pm) • Assignment Development (1:00-2:30pm) • Discussion /Feedback (2:45-4:00pm)

  4. Workshop Objectives 1. Disseminate the use of service-oriented approach to teaching CS1/IS1 2. Explore educational innovations for indoctrinating students the state-of-the-art software development practices using SOA 3. Build a learning/research community of service-orientation-in-CS1/IS1 enthusiasts.

  5. Project Overview • Began with: • "On Integrating Web Services from the Ground Up into CS1/CS2," ACM SIGCSE 2005, St. Louis, MO, Feb., 2005. • Now supported by: • NSF-DUE-CCLI-0837056, "Integrating Service-Oriented Paradigm into Introductory Information Technology Curricula," 2009 – 2011.

  6. Basic Ideas • SOA/Web services have gained popularity in many industries and in upper division/graduate CS/IS curricula • Why not introduce service-orientation earlier in the curriculum? • Service-orientation can make a course more interesting • Service-orientation can better prepare students for upper division classes and for the industry upon graduation • Service-orientation can introduce sound principles of software engineering earlier in the curriculum

  7. Courseware Showcase • Main project site: • http://www.itk.ilstu.edu/ws4intro • The site contains info on: • PowerPoint slides • Lab exercises • Programming assignments • Tutorials • List of Web services used

  8. Experience Report • Outcome 1: Students will provide a better evaluation of the IT1 course by 10% as compared to traditional IT1 course evaluations. Students will also indicate a positive perception of the SOA/Web services learning experience. • Outcome 2: Student course grade performance will increase in the IT1 course by 10% as compared to traditional IT1 course performance. • Outcome 3: Employers of computer science and information technology students will indicate a positive response to an SOA/Web services centered curriculum.

  9. Experience Report (cont’d) • Outcome 1: Limited data…partial support • In hindsight we should have chosen a different measure • The amount of data collected will be limited and probably won’t be statistically significant

  10. Experience Report (cont’d) • Outcome 2: Demographics • 99 students (missing cases were mostly drops) • 34% in WS/SOA section • 12% of the students were female, 88% male • 76% unable to define “What is a WS?” to 88% could define

  11. Experience Report (cont’d) • Outcome 2: Statistically significant improvement in final exam performance and course grade

  12. Experience Report (cont’d) • Outcome 2: Statistically significant improvement in course grade

  13. Experience Report (cont’d) Outcome 2: Grading bias and other concerns TukeyPairwise Comparison’s were not significant for the instructors, except for one pairing. This pairing did not include either of the instructor’s teaching the web service sections. More data will help alleviate concerns about the grading

  14. Experience Report (cont’d) • Outcome 3: Employers of computer science and information technology students will indicate a positive response to an SOA/Web services centered curriculum. • Survey developed (see handout) • Companies contacted/to contact: Amazon, Google, State Farm (other local users), suggestions…

  15. Experience Report (cont’d) • Continued interest in students after the completion of the class • Initial frustration translates to positive response when creating “real-world”-like applications • Engaging experience for faculty • Second semester syndrome

  16. Experience Report (cont’d) • “Do I have to code this? Isn’t there a Web service to do that?” • A student’s comment on the requirement to “validate … the state’s 2-letter abbreviation (must be one of the 50 state abbreviations).” • “But that’s just calling the Web service to get a word from the dictionary, right?” • A student’s remark on needing to handle the part of the assignment that requires them to hit a Web service to randomly generate a word (after he has already completed the part where he provides his own word) in the Hangman program.

  17. Session 2: Web services in CS1/IS1

  18. Reusable Components • Most programs are created by combining components that exist already, not from scratch! • Reusing components saves time and money. • Reused components are likely to be better developed, and more reliable. • New components should be designed to be reusable by other applications. Don’t reinvent the wheels! Source: Savitch & Carrano 2009 CS1 text

  19. Description of class Scanner Package names Class names Software Reuse Source: Savitch & Carrano 2009 CS1 text

  20. Software Reuse via SOA/WS • Latest form of reuse is via “services” • SOA (Service-Oriented Architecture) • “A system for linking resources on demand. In an SOA, resources are made available to other participants in the network as independent services that are accessed in a standardized way. This provides for more flexible loose coupling of resources than in traditional systems architectures.” –Sybase • “Architecture that describes an entity (e.g., application or enterprise) as a set of interdependent services. SOA provides for reuse of existing services and the rapid deployment of new business capabilities based on existing assets.” -- CIO.gov • Many others …

  21. Software Reuse via SOA/WS • One popular way of implementing SOA is via Web services • WS (Web Service) • "a software system designed to support interoperablemachine-to-machine interaction over a network. It has an interface described in a machine-processable format (specifically WSDL). Other systems interact with the Web service in a manner prescribed by its description using SOAP-messages, typically conveyed using HTTP with an XML serialization in conjunction with other Web-related standards.“ – W3C • Laymen terms: a piece of program that can interact with another program using standardized Web protocols • Examples: Google Maps API, Flickr API, Twitter API, Amazon Web services. (API = Application Programming Interface)

  22. NetBeans Generated Code Template try { // Call Web Service Operation <someService> service = new <someService>; < someServicePort> port = service.get<someServicePort>(); // TODO initialize WS operation arguments here declarations of arguments here // TODO process result here <someResult> result = port.methodOfInterest(argument list); System.out.println("Result = "+result); } catch (Exception ex) { // TODO handle custom exceptions here } Bold: Statements of interests; Wish Exception ex was printed as part of the template.

  23. Decision Structure try { // Call Web Service Operation com.cdyne.ws.profanityws.profanity.Profanity service = new com.cdyne.ws.profanityws.profanity.Profanity(); com.cdyne.ws.profanityws.profanity.ProfanitySoap port = service.getProfanitySoap(); // TODO initialize WS operation arguments here java.lang.String text = “You smoked weed? Dumb!"; // TODO process result here com.cdyne.ws.profanityws.profanity.FilterReturn result = port.simpleProfanityFilter(text); if (result.isFoundProfanity()) … else … } catch (Exception ex) { // TODO handle custom exceptions here }

  24. Repetition Structure mypackage.ISUDirectoryLookUpService service = new mypackage.ISUDirectoryLookUpService(); mypackage.ISUDirectoryLookUp port = service.getISUDirectoryLookUpPort(); // TODO initialize WS operation arguments here java.lang.StringlastName = aLastName; java.lang.StringfirstName = ""; java.lang.String city = ""; java.lang.String state = ""; java.lang.String zip = ""; // TODO process result here mypackage.DirectoryResult result = port.findPerson(lastName, firstName, city, state, zip);

  25. Repetition Structure (2) IntlistingSize = result.getItems().getDirectoryRecord().size(); for (inti = 0; i < listingSize; i++) { firstName = result.getItems().getDirectoryRecord().get(i).getFirstName(); lastName = result.getItems().getDirectoryRecord().get(i).getLastName(); zip = result.getItems().getDirectoryRecord().get(i).getZip(); phone = result.getItems().getDirectoryRecord().get(i).getPhone(); state = result.getItems().getDirectoryRecord().get(i).getState(); cityNamePrint = result.getItems().getDirectoryRecord().get(i).getCity(); }

  26. Hands-on Activities • http://r2d2.itk.ilstu.edu/ws4intro/wordpress/?page_id=295

  27. Session 3: Curriculum Development in CS1/IS1 http://r2d2.itk.ilstu.edu/ws4intro/wordpress/?page_id=308

  28. Session 4: The Future of Web services in CS1/IS1 (and CS2/IS2?)

  29. Group Discussion Topics • Phase II objectives? • Viability of the current curriculum in other academic institutions? • Synthesis across the curriculum?

  30. Feedback Please tell us what you think! and THANK YOU FOR ATTENDING!

More Related