Abstract

Integrated formal and informal specification techniques (FISTs) have been the focus of a number of research projects since the mid-eighties. Research in this area aim at producing specification techniques that integrate concepts and notations used in mature formal specification techniques (FSTs) and popular graphical modeling methods such as Structured Analysis (SA) and Object-Oriented Analysis (OOA). In this paper we illustrate, using the results of two case studies, two roles FSTs can play in the context of less formal graphical requirements modeling and analysis techniques. In the first case study discussed an extended Petri Net model is used to prototype a textbook SART (SA/Real-Time) model. In this case, the formal model acts as a prototype, and is used to dynamically validate the requirements expressed in the SART model. In the second case study an integrated OOA method (Fusion) and FST (Z) is used to create requirements models that are graphical and analyzable. In this case, the formal models act as more precise representations of the requirements captured by the graphical models.

Highlights

  • Software requirements engineering is concerned with the systematic analysis and speci cation of software requirements

  • The results of our case studies are a good indication that the application of formal and informal specication techniques (FISTs) to requirements speci cation and analysis can bring about the following bene ts:

  • Use could lead to an understanding of required properties that may not be possible with sole use of formal or informal speci cation techniques

Read more

Summary

Introduction

Software requirements engineering is concerned with the systematic analysis and speci cation of software requirements. One can view requirements engineering as a systematic approach to problem analysis and speci cation, where the goal is to obtain a precise statement of the problem in terms of goals that must be met by the implemented system. The need for precision suggests the use of formal speci cation techniques (FSTs). Precise speci cations facilitate e ective communication among persons with a stake in the development of the software. Variants of the SA method [6] are among the most widely used requirements speci cation and analysis methods in industry. Their simple, intuitively-appealing speci cation concepts and notation are major factors behind.

Methods
Modeling requirements with SART
An extended Petri Net model
Guidelines for transforming SART models to EPNs
Analyzing the EPN model
Modeling the Advising System Problem
Stage 1 - Developing the Object Model
Associate a state schema with each object
Evaluate model
Stage 2 - Developing the Operation Model
Conclusion
Full Text

Published Version (Free)

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.