A Business Model to Make Software Development Less Intuitive

A business viewpoint on the system distinguishes a "source" model and a "target" model. The "source" model must reflect the system (and its environment) that currently exists and is under investigation. Requirements for systems reflect business ownerspsila, managerspsila and userspsila needs related to the "target" model. Consistency between the "source" and the "target" as well as completeness and traceability of the "target" model still is a challenge. This paper bases check of requirements on a formal business model of the "source" system. It is performed in a formal way by creating a topological model of the "source" systempsilas functioning, and mapping functional requirements for the "target" system onto this model. Further, this holistic view can be decomposed by userspsila goals. Thus a model of the "target" system (requirements) is in compliance with a model of the "source" system (the universe of discourse). Beside that requirements are more complete and traceable.

[1]  Dean Leffingwell,et al.  Managing Software Requirements: A Use Case Approach , 2003 .

[2]  Ivar Jacobson,et al.  Object-oriented software engineering - a use case driven approach , 1993, TOOLS.

[3]  John F. Sowa,et al.  Extending and Formalizing the Framework for Information Systems Architecture , 1992, IBM Syst. J..

[4]  Axel van Lamsweerde,et al.  Goal-Oriented Requirements Engineering: A Guided Tour , 2001, RE.

[5]  Janis Osis.  Software Development with Topological Model in the Framework of MDA , 2004, CAiSE Workshops.

[6]  Janis Osis.  Formal Computation Independent Model within the MDA Life Cycle , 2006, Int. Trans. Syst. Sci. Appl..

[7]  Hermann Kaindl,et al.  A design process based on a model combining scenarios with goals and functions , 2000, IEEE Trans. Syst. Man Cybern. Part A.

[8]  Erika Asnina,et al.  Computation Independent Modeling within the MDA , 2007, IEEE International Conference on Software-Science, Technology & Engineering (SwSTE'07).

[9]  William F. Basener,et al.  Topology and Its Applications: Basener/Topology , 2006 .

[10]  K. P. Hart,et al.  Topology and its Applications , 2007 .

[11]  P ? ? ? ? ? ? ? % ? ? ? ? , 1991 .

[12]  Alistair Cockburn,et al.  Structuring Use Cases with Goals , 2000 .

[13]  John A. Zachman,et al.  A Framework for Information Systems Architecture , 1987, IBM Syst. J..

[14]  Stephen Fickas,et al.  Goal-Directed Requirements Acquisition , 1993, Sci. Comput. Program..

[15]  Tony Gorschek,et al.  Requirements Abstraction Model , 2005, Requirements Engineering.

[16]  Craig Larman,et al.  Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development (3rd Edition) , 1997 .

[17]  Erika Asnina,et al.  Enterprise Modeling for Information System Development within MDA , 2008, Proceedings of the 41st Annual Hawaii International Conference on System Sciences (HICSS 2008).

[18]  Kimberly S. Wasson.  Requirements Metrics : Scaling Up , 2003 .

[19]  Michael Jackson,et al.  Problem frames and software engineering , 2005, Expert Syst. J. Knowl. Eng..

[20]  Narayan C. Debnath,et al.  Improving Model Driven Architecture with Requirements Models , 2008, Fifth International Conference on Information Technology: New Generations (itng 2008).

[21]  Eric S. K. Yu,et al.  Towards modelling and reasoning support for early-phase requirements engineering , 1997, Proceedings of ISRE '97: 3rd IEEE International Symposium on Requirements Engineering.