Functional and Non-functional Requirements Specification for Enterprise Applications

Comprehensive and accurate software requirements capture is essential for successful development of software systems. Enterprise applications have an additional challenge of eliciting requirements that need to be well understood by i) the business users of the system having extensive domain knowledge ii) application developers having extensive system implementation and development knowledge. Current tools vary from providing textual descriptions to formal semantic languages for specifying requirements. The business users are unable to actively participate in the analysis, as formal and textual specifications represent two extreme ends of requirements elicitation. Ambiguity or lack of understanding often poses a challenge on validation and verification of system requirements specification. The paper presents a Use case Specification Framework that brings structure to requirements specification while retaining its simplicity. The framework enables business users to understand and verify functional requirements and two critical non functional requirements – performance and usability.

[1]  Geary A. Rummler,et al.  Improving Performance: How to Manage the White Space on the Organization Chart , 1990 .

[2]  Ivar Jacobson,et al.  The use-case construct in object-oriented software engineering , 1995 .

[3]  Margus Veanes,et al.  Validating use-cases with the AsmL test tool , 2003, Third International Conference on Quality Software, 2003. Proceedings..

[4]  Woo Jin Lee,et al.  Integration and Analysis of Use Cases Using Modular Petri Nets in Requirements Engineering , 1998, IEEE Trans. Software Eng..

[5]  David Chenho Kung,et al.  Formal approach to scenario analysis , 1994, IEEE Software.

[6]  Kendall Scott,et al.  UML distilled - applying the standard object modeling language , 1997 .

[7]  Geri Schneider,et al.  Applying use cases (2nd ed.): a practical guide , 2001 .

[8]  Björn Regnell,et al.  Improving the use case driven approach to requirements engineering , 1995, Proceedings of 1995 IEEE International Symposium on Requirements Engineering (RE'95).

[9]  Daniel Amyot,et al.  On the Extension of UML with Use Case Maps Concepts , 2000, UML.

[10]  Alistair Cockburn,et al.  Writing Effective Use Cases , 2000 .

[11]  Stephen A. White,et al.  Business Process Modeling Notation (BPMN), Version 1.0 , 2004 .

[12]  Remco M. Dijkman,et al.  An Algorithm to Derive Use Cases from Business Processes , 2002, ICSE 2002.

[13]  John M. Carroll,et al.  Scenario-based design: envisioning work and technology in system development: john wiley & sons , 1995 .