Integrating visual goal models into the Rational Unified Process

The Rational Unified Process is a comprehensive process model that is tailorable, provides templates for the software engineering products, and integrates the use of the Unified Modeling Language (UML); it is rapidly becoming a de facto standard for developing software. The process supports the definition of requirements at multiple levels. Currently, the early requirements, or goals, are captured in a textual document called the Vision Document, as the UML does not include a goal modeling diagram. The goals are subsequently refined into software requirements, captured in UML Use Case Diagrams. Given the well documented advantages of visual modeling techniques in requirements engineering, including the efficient communication and understanding of complex information among numerous diverse stakeholders, the need for an enhanced version of the Vision Document template which supports the visual modeling of goals is identified. Here, an Enhanced Vision Document is proposed which integrates two existing visual goal models: AND/OR Graph for functional goals and Softgoal Interdependency Graph for non-functional goals. A specific approach to establishing traceability relationships from the goals to the Use Cases is presented. Tool support has been developed for the Enhanced Vision Document template; the approach is illustrated using an example system called the Quality Assurance Review Assistant Tool.

[1]  Fausto Giunchiglia,et al.  Tropos: An Agent-Oriented Software Development Methodology , 2004, Autonomous Agents and Multi-Agent Systems.

[2]  Olly Gotel,et al.  An analysis of the requirements traceability problem , 1994, Proceedings of IEEE International Conference on Requirements Engineering.

[3]  Ken Platts,et al.  Visualization and Visual Modelling for Strategic Analysis and Problem-Solving , 2005, Ninth International Conference on Information Visualisation (IV'05).

[4]  Herbert A. Simon,et al.  The Sciences of the Artificial , 1970 .

[5]  Matthias Jarke,et al.  Telos: representing knowledge about information systems , 1990, TOIS.

[6]  Philippe Massonet,et al.  Goal-directed elaboration of requirements for a meeting scheduler: problems and lessons learnt , 1995, Proceedings of 1995 IEEE International Symposium on Requirements Engineering (RE'95).

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

[8]  Eric Yu,et al.  From Requirements to Architectural Design –Using Goals and Scenarios , 2001 .

[9]  Matthias Jarke,et al.  Toward Reference Models of Requirements Traceability , 2001, IEEE Trans. Software Eng..

[10]  John Mylopoulos,et al.  Specifying and analyzing early requirements in Tropos , 2004, Requirements Engineering.

[11]  Jaelson Brelaz de Castro,et al.  From software requirements to architectures , 2001, Proceedings of the 23rd International Conference on Software Engineering. ICSE 2001.

[12]  John Mylopoulos,et al.  From object-oriented to goal-oriented requirements analysis , 1999, CACM.

[13]  Frederick P. Brooks,et al.  "No silver bullet" reloaded: retrospective on "essence and accidents of software engineering" , 2007, OOPSLA '07.

[14]  E. Dubois,et al.  From early to late formal requirements: a process-control case study , 1998, Proceedings Ninth International Workshop on Software Specification and Design.

[15]  Wayne W. Zachary,et al.  Decision Support Systems: Designing to Extend the Cognitive Limits , 1988 .

[16]  Ian Spence,et al.  Traceability Strategies for Managing Requirements with Use Cases , 2001 .

[17]  G. A. Miller THE PSYCHOLOGICAL REVIEW THE MAGICAL NUMBER SEVEN, PLUS OR MINUS TWO: SOME LIMITS ON OUR CAPACITY FOR PROCESSING INFORMATION 1 , 1956 .

[18]  Fausto Giunchiglia,et al.  Agent- Oriented Software Development: A Case Study , 2001, SEKE.

[19]  Axel van Lamsweerde,et al.  Handling Obstacles in Goal-Oriented Requirements Engineering , 2000, IEEE Trans. Software Eng..

[20]  Julio Cesar Sampaio do Prado Leite,et al.  Nonfunctional requirements: from elicitation to conceptual models , 2004, IEEE Transactions on Software Engineering.

[21]  John Mylopoulos,et al.  Applying Tropos Methodology to a real case study : Complexity and Criticality Analysis , 2002 .

[22]  Herbert A. Simon,et al.  Why a Diagram is (Sometimes) Worth Ten Thousand Words , 1987 .

[23]  John Mylopoulos,et al.  On formal requirements modeling languages: RML revisited , 1994, Proceedings of 16th International Conference on Software Engineering.

[24]  Philippe Kruchten,et al.  The Rational Unified Process Made Easy - A Practitioner's Guide to the RUP , 2003, Addison Wesley object technology series.

[25]  Andrea Zisman,et al.  Rule-based generation of requirements traceability relations , 2004, J. Syst. Softw..

[26]  Paolo Donzelli,et al.  A goal-driven and agent-based requirements engineering framework* , 2004, Requirements Engineering.

[27]  John Mylopoulos,et al.  Goal-oriented requirements analysis and reasoning in the Tropos methodology , 2005, Eng. Appl. Artif. Intell..

[28]  W. W. Bledsoe,et al.  Review of "Problem-Solving Methods in Artificial Intelligence by Nils J. Nilsson", McGraw-Hill Pub. , 1971, SGAR.

[29]  Håvard D. Jørgensen,et al.  Model-driven visual requirements engineering , 2005, 13th IEEE International Conference on Requirements Engineering (RE'05).

[30]  Dewayne E. Perry,et al.  Deriving Architecture Specifications from KAOS Specifications: A Research Case Study , 2005, EWSA.

[31]  Nils J. Nilsson,et al.  Problem-solving methods in artificial intelligence , 1971, McGraw-Hill computer science series.

[32]  Colette Rolland,et al.  Experience with goal-scenario coupling in requirements engineering , 1999, Proceedings IEEE International Symposium on Requirements Engineering (Cat. No.PR00188).

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

[34]  Philippe Massonet,et al.  GRAIL/KAOS: An Environment for Goal-Driven Requirements Engineering , 1997, Proceedings of the (19th) International Conference on Software Engineering.

[35]  Sam Supakkul,et al.  A UML profile for goal-oriented and use case-driven representation of NFRs and FRs , 2005, Third ACIS Int'l Conference on Software Engineering Research, Management and Applications (SERA'05).

[36]  Annie I. Antón,et al.  Goal-based requirements analysis , 1996, Proceedings of the Second International Conference on Requirements Engineering.