Control Cases during the Software Development Life-Cycle

The control case is a tool that may be applied in software development to model non-functional requirements during the requirements engineering process. The control case complements the use case in requirements design by capturing the systems qualities not addressed by the use case. This includes attributes such as performance, security, and the prescribed technology and standards. Together, the use case and control case offer a more complete representation of the requirements that define the system to be developed. In this paper, we extend the previous work on the control case by illustrating how this modeling tool is applied during the software development lifecycle (SDLC) from initial requirements through to commercial deployment. This includes business process analysis, detailed requirements gathering, architecture & design, software build, systems testing, and deployment. This work helps to bridge the gap in applying the control case to model non-functional requirements, illustrating how control cases are decomposed and refined further during the SDLC.

[1]  Chung Yee Lee,et al.  Business process management: survey and methodology , 1995 .

[2]  Eric S. K. Yu,et al.  Towards modelling and reasoning support for early-phase requirements engineering , 1997, Proceedings of ISRE '97: 3rd IEEE International Symposium on Requirements Engineering.

[3]  Ian Sommerville,et al.  Requirements Engineering: Processes and Techniques , 1998 .

[4]  Geri Schneider,et al.  Applying Use Cases: A Practical Guide , 1998 .

[5]  Jan Bosch,et al.  Software architecture design: evaluation and transformation , 1999, Proceedings ECBS'99. IEEE Conference and Workshop on Engineering of Computer-Based Systems.

[6]  Connie U. Smith,et al.  Performance solutions: a practical guide to creating responsive , 2001 .

[7]  Alistair Cockburn,et al.  Patterns for Effective Use Cases , 2002 .

[8]  Paolo Giorgini,et al.  The TROPOS Analysis Process as Graph Transformation System , 2002 .

[9]  G. Stoneburner,et al.  Risk Management Guide for Information Technology Systems: Recommendations of the National Institute of Standards and Technology , 2002 .

[10]  Mike P. Papazoglou,et al.  Service-oriented computing: concepts, characteristics and directions , 2003, Proceedings of the Fourth International Conference on Web Information Systems Engineering, 2003. WISE 2003..

[11]  L. M. Cysneiros.  Addressing Agent Autonomy in Business Process Management-With Case Studies on the Patient Discharge Process , 2004 .

[12]  Robert V. Brill,et al.  Applied Statistics and Probability for Engineers , 2004, Technometrics.

[13]  Pericles Loucopoulos,et al.  Goal Modeling in Requirements Engineering: Analysis and Critique of Current Methods , 2005, Information Modeling Methods and Methodologies.

[14]  L. Laibinis,et al.  Fault Tolerance in Use-Case Modeling , 2005 .

[15]  Stephan Reiff-Marganiec,et al.  Towards a Task-Oriented, Policy-Driven Business Requirements Specification for Web Services , 2006, Business Process Management.

[16]  Shazia Wasim Sadiq,et al.  Using a temporal constraint network for business process execution , 2006, ADC.

[17]  Ali Arsanjani,et al.  Service-Oriented Modeling and Architecture for Realization of an SOA , 2006, 2006 IEEE International Conference on Services Computing (SCC'06).

[18]  Jun-Jang Jeng.  Service-Oriented Business Performance Management for Real-Time Enterprise , 2006, The 8th IEEE International Conference on E-Commerce Technology and The 3rd IEEE International Conference on Enterprise Computing, E-Commerce, and E-Services (CEC/EEE'06).

[19]  Christopher J. Pavlovski,et al.  Modeling Architectural Non Functional Requirements: From Use Case to Control Case , 2006, 2006 IEEE International Conference on e-Business Engineering (ICEBE'06).

[20]  Christopher J. Pavlovski,et al.  Non-Functional Requirements in Business Process Modeling , 2008, APCCM.

[21]  Christopher J. Pavlovski,et al.  Control case approach to record and model non-functional requirements , 2008, Inf. Syst. E Bus. Manag..