Consistency checking of UML requirements

This paper discusses how to check consistency of UML requirements model which consists of a use case model and a conceptual class model with system constraints. Based on a given semantics, the requirements consistency can be defined and checked formally. The consistency among use cases and constraints are classified into five types. A system operation of interaction between actor and system is formally defined as a pair of pre and post conditions. An atomic use case is described as one system operation, and a composed use case may be defined as several system operations described by an activity diagram. Thus, each use case can also be modelled as a pair of pre and post conditions by composing the pre and post conditions of system operations by introducing a sequence composition operation. Requirement consistency can be logically checked based on the semantics. A simple library system is used as a case study to illustrate the feasibility of the method.

[1]  Pete Sawyer,et al.  Requirements Engineering: A Good Practice Guide , 1997 .

[2]  Craig Larman,et al.  Applying UML and patterns , 1997 .

[3]  Reiko Heckel,et al.  Detection of conflicting functional requirements in a use case-driven approach , 2002, Proceedings of the 24th International Conference on Software Engineering. ICSE 2002.

[4]  Ivar Jacobson,et al.  The Unified Software Development Process , 1999 .

[5]  Shengchao Qin,et al.  A Relational Model for Object-Oriented Designs , 2004, APLAS.

[6]  Dr. Reinhold Plösch.  Contracts, Scenarios and Prototypes , 2004, Springer Berlin Heidelberg.

[7]  Jifeng He,et al.  Using Transition Systems to Unify UML Models , 2002, ICFEM.

[8]  Reiko Heckel,et al.  Detection of conflicting functional requirements in a use case-driven approach: a static analysis technique based on graph transformation , 2002, ICSE '02.

[9]  Stuart Kent,et al.  Constraint Diagrams: Visualizing Invariants in OO Modelling , 1997, OOPSLA 1997.

[10]  Ian Sommerville,et al.  Requirements Engineering: Processes and Techniques , 1998 .

[11]  Constance L. Heitmeyer,et al.  Automated consistency checking of requirements specifications , 1996, TSEM.

[12]  Anneke Kleppe,et al.  The object constraint language: precise modeling with UML , 1998 .

[13]  S. Shavell.  Contracts , 1998 .

[14]  Quan Long,et al.  Generating a Prototype from a UML Model of System Requirements , 2004, ICDCIT.

[15]  Jifeng He,et al.  Formal and use-case driven requirement analysis in UML , 2001, 25th Annual International Computer Software and Applications Conference. COMPSAC 2001.

[16]  James J. Odell,et al.  Advanced object-oriented analysis and design using UML , 1997 .

[17]  Ian Sommerville,et al.  Software Engineering (7th Edition) , 2004 .

[18]  簡聰富,et al.  物件導向軟體之架構(Object-Oriented Software Construction)探討 , 1989 .

[19]  강문설.  [서평]「The Unified Modeling Language User Guide」 , 1999 .

[20]  Reinhold Ploesch.  Contracts, Scenarios and Prototypes: An Integrated Approach to High Quality Software , 2004 .

[21]  Bertrand Meyer,et al.  Object-Oriented Software Construction, 2nd Edition , 1997 .

[22]  C. A. R. Hoare,et al.  Unifying theories of programming , 1998, RelMiCS.

[23]  Ivar Jacobson,et al.  The Unified Modeling Language User Guide , 1998, J. Database Manag..