Formalization, Testing and Execution of a Use Case Diagram

Errors in a requirements model have prolonged detrimental effects on reliability, cost, and safety of a software system. It is very costly to fix these errors in later phases of software development if they cannot be corrected during requirements analysis and design. A use case diagram, as a requirements model, plays an important role in giving requirements for a software system. It provides a communication tool between software requirements developers and prospective users to understand what requirements of a software system are. However most descriptions of a use case diagram are written in some informal language, leading to possible misunderstanding between developers and users. In this paper, we propose a new rigorous review technique which can be applied to software requirements models. Using this new technique before a software system is fully designed will help us find some potential errors in a requirements model, resulting in reduced time, labor and expenditure in software development.

[1]  Cliff B. Jones,et al.  Systematic software development using VDM , 1986, Prentice Hall International Series in Computer Science.

[2]  Lee J. White.  Software Testing and Verification , 1987, Adv. Comput..

[3]  Antoni Diller,et al.  Z - an introduction to formal methods , 1990 .

[4]  Yuri Gurevich,et al.  Evolving algebras 1993: Lipari guide , 1995, Specification and validation methods.

[5]  Robyn R. Lutz.  Targeting safety-related errors during software requirements analysis , 1993, SIGSOFT '93.

[6]  Robyn R. Lutz,et al.  Analyzing software requirements errors in safety-critical, embedded systems , 1993, [1993] Proceedings of the IEEE International Symposium on Requirements Engineering.

[7]  Betty H. C. Cheng,et al.  A Formal Semantics for Object Model Diagrams , 1995, IEEE Trans. Software Eng..

[8]  A. Jefferson Offutt,et al.  SOFL: A Formal Engineering Methodology for Industrial Applications , 1998, IEEE Trans. Software Eng..

[9]  Shaoying Liu.  Verifying Consistency and Validity of Formal Specifications by Testing , 1999, World Congress on Formal Methods.

[10]  A. Jefferson Offutt,et al.  Using UML Collaboration Diagrams for Static Checking and Test Generation , 2000, UML.

[11]  Shane Sendall,et al.  From Use Cases to System Operation Specifications , 2000, UML.

[12]  Martin Gogolla,et al.  Validating UML Models and OCL Constraints , 2000, UML.

[13]  Lionel C. Briand,et al.  A UML-Based Approach to System Testing , 2001, UML.

[14]  Kevin J. Compton,et al.  A toolset for supporting UML static and dynamic model checking , 2002, Proceedings 26th Annual International Computer Software and Applications.

[15]  Shaoying Liu,et al.  Developing Quality Software Systems Using the SOFL Formal Engineering Method , 2002, ICFEM.

[16]  Mohsen Guizani,et al.  Execution of A Requirement Model in Software Development , 2004, IASSE.