Conciliating User Interface and Business Domain Analysis and Design
- 289 Downloads
User Interfaces (UI) are an essential part of most softwares, especially data intensive ones as database or Web based applications.
Most of the approaches dealing with UI focus on design and implementation aspects and are driven by a specific technology. We believe UI specification has already to be taken into account through the analysis phase, because it is closely related to the application Business Domain (BD), which is apprehended in the earliest steps of the Analysis and Design Process (A&D-Pr). Moreover, during the analysis phase, the UI is described in a more abstract way and a larger variety of UI can be taken into consideration.
The UI and the BD aspects of the application have to be studied in a closely-related way. But most of the existing approaches propose a specific notation for the UI, different from the one used to define the BD. And when guidelines are associated with the notation, they focus on the UI and are poorly related to the BD. We propose an integrated approach (i) using a single notation in order to facilitate and support the integration of BD and UI aspects modeling and (ii) proposing an application model distinguishing the UI and BD aspects via separate views and clearly setting relationships between them. We choose the UML notation to illustrate our work in order to facilitate its use in any standard A&D-Pr. Our approach also includes a methodology to explain how to create the application model. Its aim is not only to model the UI from a pure technical point of view, but from a business one, providing guidelines for error management, or business rules support for instance.
In this paper, we present our UML profile for UI and show how we could take advantage of it through the different phases of the A&D-Pr.
KeywordsApplication Model Class Diagram User Interface Modeling Business Rule Error Management
Unable to display preview. Download preview PDF.
- 1.Browne, T., Davila, D., Rugaber, S., Stirewalt, K.: Using declarative descriptions to model user interfaces with MASTERMIND. In: Formal methods in Human-Computer Interaction, Springer, Heidelberg (1997)Google Scholar
- 2.Constantine, L.L., Lockwood, L.A.D.: Software for use: a practical guide to the models and methods of usage-centered design. Addison Wesley, Reading (1999)Google Scholar
- 3.Pinheiro da Silva, P., Paton, N.W.: UMLi: the unified modeling language for interactive applications. In: 3rd International Conference on the Unified Modeling Language, October 2000, pp. 117–132 (2000)Google Scholar
- 4.D’Souza, D., Wills, A.: Objects, Components and Frameworks With UML: The Catalysis Approach. Addison-Wesley, Reading (1998)Google Scholar
- 5.Object Management Group. The UML notation, http://www.omg.org/
- 6.Krutchen, P.: The Rational Unified Process. Object Technology Series. Addison-Wesley, Reading (2000)Google Scholar
- 7.Mirbel, I., De Rivieres, V.: Adapting Analysis and Design to Software Context: the JECKO Approach. In: 8th International Conference on Object-Oriented Information Systems (September 2002)Google Scholar
- 8.De Rivieres, V., Mirbel, I.: Towards a UML profile for building on top of running software. In: UML and the Unified Process, IRM Press (2003)Google Scholar
- 9.Nunes, D.N.J.: Object Modeling for User-Centered Development and User Interface Design: the Wisdom Approach. PhD thesis, Universidade da Madeira, Portugal (2001)Google Scholar
- 10.Puerta, A., Eisenstein, J.: Towards a general computational framework for model-based interface development systems. In: International Conference on Intelligent User Interfaces, January 1999, pp. 171–178 (1999)Google Scholar
- 11.Roberts, D., Berry, D., Isensee, S., Mullally, J.: Designing for the user with OVID: bridging user interface design and software engineering. Macmullan Tech. (1998)Google Scholar