Advertisement

Systematic Development of Complex Web-Based User Interfaces

  • Henrik Behrens
  • Thorsten Ritter
  • Hans-Werner Six
Chapter
Part of the Lecture Notes in Computer Science book series (LNCS, volume 2598)

Abstract

Software components realising the graphical user interface (GUI) of a highly interactive system or the user interface of a Web application form an essential part of the entire implementation and significantly affect the effectiveness and maintainability of the software system. In this paper, we propose a software engineering based approach for the development of complex Web-based user interfaces (Web-UIs). The method comprises two basic tasks. The first task gathers and models the UI requirements. The second task maps the UI requirements model into a Web-UI software architecture. To this end, we propose DAWID (DIWA-based Web User Interface Development), an approach that adapts the DIWA framework for GUI development to Web-UIs. Since DIWA consequently applies fundamental software engineering (SE) principles and its adaption to Web-UIs requires only minimal changes, the resulting DAWID architecture also stays fully compliant with the SE principles.

Keywords

Software Architecture Activity Diagram Class View Main Window Decision Interaction 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
    Apache Software Foundation: Struts Jakarta Project, http://jakarta.apache.org/struts
  2. 2.
    Booch, G., Rumbaugh, J., Jacobson, I.: The Unified Modeling Language Users Guide. Addison-Wesley/acm Press, Reading, MA (1999)CrossRefGoogle Scholar
  3. 3.
    Gamma, E., Helm, R., Johnson, R., Vlissides, J.: Design Patterns — Elements of Reusable Object-Oriented Software, Addison-Wesley (1994)Google Scholar
  4. 4.
    Seshadri, G.: Understanding JavaServer Pages Model 2 Architecture, JavaWorld, http://www.javaworld.com/javaworld/jw-12-1999/jw-12-ssj-jspmvc.html
  5. 5.
    Homrighausen, A., Six, H.-W., Winter, M.: Round-Trip Prototyping Based on Integrated Functional and User Interface Requirements Specifications. Requirements Engineering, Vol. 7, Nr. 1, Springer, London (2002)Google Scholar
  6. 6.
    Jacobson I., Booch G., Rumbaugh J.: The Unified Software Development Process. Addison-Wesley/acm Press, Reading, MA (1999)Google Scholar
  7. 7.
    Kösters, G., Six, H.-W., Winter6M.: Coupling Use Cases and Class Models as a Means for Validation and Verification of Requirements Specifications. Requirements Engineering, Vol. 6, Nr. 1, Springer, London (2001) 3–17Google Scholar
  8. 8.
    Object Managment Group: Unified Modeling Language Specification. Version 1.3, OMG (1999)Google Scholar
  9. 9.
    Six, H.-W., Voss, J.: A Software Engineering Perspective to the Design of a User Interface Framework. Proc. IEEE CompSAC’ 92, Chicago (1992)Google Scholar
  10. 10.
    Sun Microsystems Inc.: Sun ONE Application Framework (JATO), http://devel-oper.iplanet.com/tech/appserver/framework/

Copyright information

© Springer-Verlag Berlin Heidelberg 2003

Authors and Affiliations

  • Henrik Behrens
    • 1
  • Thorsten Ritter
    • 1
  • Hans-Werner Six
    • 1
  1. 1.Software Engineering, Dept. of Computer ScienceFernUniversitätHagenGermany

Personalised recommendations