1 / 27

The Pro‘s and Con‘s of Employing the Unified Process for Web-Based Applications

The Pro‘s and Con‘s of Employing the Unified Process for Web-Based Applications. Renate Motschnig University of Vienna Department of Computer Science and Business Informatics. Research Goals and Interests. Develop a process model for the effective development of high-quality web-applications

agatha
Download Presentation

The Pro‘s and Con‘s of Employing the Unified Process for Web-Based Applications

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. The Pro‘s and Con‘s of Employing the Unified Process for Web-Based Applications Renate Motschnig University of Vienna Department of Computer Science and Business Informatics

  2. Research Goals and Interests • Develop a process model for the effective development of high-quality web-applications • Primary process-model requirements: • Provide guidance yet sufficient room for individual solutions • Provide tool support • Respect special features of Web-applications

  3. Is the Unified Process qualified • …from the point of view of our experience… • Case Study – UniKid (http://www.univie.ac.at/unikid) • Social Web-application • … as source for examples • Other case studies

  4. Overview • IS the UP helpful in developing web-applications? • Special features of web-applications • Brief survey of Unified Process • Which features are helpful? • What is missing? • Conclusions • Further work

  5. Web-Application • A web-application is a web-system (web-site) that allows its users to execute business logic with a web-browser. (Conallen, 1999).… User input affects the state of the “business“… • A web-application provides a web-interface to an information- or knowledge management system. (Motschnig)

  6. Web-Application - Characteristics • Rich content, structure essential • Navigation is essential • Design for maintenance and change • Often: • Very diverse user profiles • integration of legacy systems • Interfaces • Peak interaction • …

  7. Unified Process • Generic Process Template • Needs to be customized and instantiated • Characteristics: • Iterative and incremental • Architecture-centric • Use-Case Driven • Language (UML) integration and tool support

  8. Overview of the UP

  9. UniKid – Deliverables of the Inception Phase

  10. Use-Cases Inception

  11. First Cut on System Architecture

  12. Complement to the Deliverables of the Inception Phase for Web-Applications

  13. Overview of the UP revisited

  14. Deliverables of the Elaboration Phase

  15. Complements to Deliverables of the Elaboration Phase for Web-Applications

  16. Construction Phase • Basically refinement and implementation of DB and interfaces • 2 increments: • Use - cases for user view • Use – cases for editor view

  17. Testing • Use-Case driven • Detailed specification of use-cases including all alternative scenarios proved very worthwhile • Many “errors“ and inconsistencies found • Navigation path driven – for content issues

  18. Customization of process template Tool and UML Thoughtful suggestion of deliverables per phase, UML diagrams (Use-Case, Class,..) Iterative and incremental proceeding Management workflow: risk reduction, planning aspects initial and final business case UP features found helpful:

  19. The UP does not support: • Graphic-layout considerations • Content issues like acquisition,intuitive naming, structure, design decisions • Navigation design • Interaction design (good tools available) • INTEGRATION of graphic, content and software techical issues within process • They are highly interdependent, need coordination

  20. What needs to be added? Web-Applikation Software aspects Graphic-layout Content Missing: Acquisition Structuring Interlinking Navigation Integration Maintenance • O.K. with specialization: • Special NFR • Usability • Design for change • Performance, … • Special architecture Missing: Page structure Look and feel Integration with content and user-interaction …and a sensible integration of these workflows!!!

  21. Conclusions • UP: highly valuable process template • Supporting: • useful set of deliverables, incremental process • Language – process – tool integration • Management issues, risk reduction • For full support, the UP needs to be complemented, in particular wrt. • Content and Graphics workflow • Navigation design (also diagramming technique required) • Integration of these workflows into the process

  22. Related and Further Work • Content structuring concepts • Organize complexity • Navigation design with templates • Role of the web in knowledge construction, cooperative learning, organizational learning – as a complement to face-to-face meetings. • … in order to use New Media to improve communication and problem-solving

More Related