ABSTRACT
On the basis of some experience in the use of UML-based methods, we believe that a more refined and stringent structuring of the knowledge in the Requirement Specification may help the specification process and make easier the consistency checks among the various components. Thus we propose a way of structuring and representing the Requirement Specification artifacts that presents a number of novelties w.r.t. the best-known current methods. Our proposal is multiview, use case-driven and UML-based; thus also object-oriented. However, also benefitting of some earlier work, notably in the Structured Analysis, we take a rather abstract view, trying to avoid a preemptive decision on the classes structuring the system to build; that is achieved not only making a sharp distinction between business/domain modelling and the system, but also dealing with the system at the requirement level as a black box, providing only the minimal structure needed to express the interactions with the context.
- E. Astesiano and G. Reggio. Consistent Structuring of Requirements in the UML. Technical Report DISI-TR-02-27, DISI, Università di Genova, Italy, 2002. Available at ftp://ftp.disi.unige.it/person/ReggioG/AstesianoReggio02b.pdf.Google Scholar
- D. F. D'Souza and A. C. Wills. Objects, Components, and Frameworks with UML: The Catalysis Approach. Object Technology Series. Addison-Wesley, 1999. Google ScholarDigital Library
- M. Fowler and K. Scott. UML Distilled: Second Edition. Object Technology Series. Addison-Wesley, 2001.Google Scholar
- H. Gomaa. Designing Concurrent, Distributed and Real-Time Applications with UML. Addison-Wesley, 2000. Google ScholarDigital Library
- M. Jackson. Software Requirements & Specifications: a Lexicon of Practice, Principles and Prejudices. Addison-Wesley, 1995. Google ScholarDigital Library
- Rational. Rational Unified Process© for System Engineering SE 1.0. 2001.Google Scholar
- R. Soley and OMG Staff Strategy Group. Model Driven Architecture. Available at ftp://ftp.omg.org/pub/docs/omg/00-11-05.pdf, 2000.Google Scholar
- UML Revision Task Force. OMG UML Specification 1.3, 1999. Available at http://www.rational.com/media/uml/post.pdf.Google Scholar
- E. Yourdon. Modern Structured Analysis. Prentice-Hall, 1989. Google ScholarDigital Library
- Knowledge structuring and representation in requirement specification
Recommendations
Test aspect of requirement specification
This paper presents the test aspect of URN. User Requirements Notation (URN) is the part of ITU-T's family of languages. URN contains two kinds of notation. The first one, Goal-oriented Requirement Language (GRL) is used to describe business goals, non-...
A Hybrid Knowledge Representation as a Basis of Requirement Specification and Specification Analysis
Special issue on software maintenanceA formal requirement specification language, the frame-and-rule oriented requirement specification language FRORL, developed to facilitate the specification, analysis, and development of a software system is presented. The surface syntax of FRORL is ...
Formal Specification Generation from Requirement Documents
Automatic generation of formal specifications from requirement reduces cost and complexity of formal models creation. Thus, the generated formal model brings the possibility to carry out system property verification. This paper proposes a Controlled ...
Comments