Integrating a software architecture-centric method into object-oriented analysis and design
Journal of Systems and Software
Non-functional requirements in business process modeling
APCCM '08 Proceedings of the fifth Asia-Pacific conference on Conceptual Modelling - Volume 79
Behavioral Model Composition: a Non Functional Requirements Driven Approach
Proceedings of the 2009 conference on New Trends in Software Methodologies, Tools and Techniques: Proceedings of the Eighth SoMeT_09
Identificando expectativas de qualidade de SIs com o apoio de modelos de negócio
Companion Proceedings of the XIV Brazilian Symposium on Multimedia and the Web
Towards a framework for estimating system NFRs on behavioral models
Knowledge-Based Systems
Accountability in enterprise mashup services
Advances in Software Engineering
Hi-index | 0.00 |
While the functional requirements of a system can be effectively modeled through the Use Case driven approach, there is no standard or de facto method for modeling non-functional requirements of the system architecture. Often such requirements are dealt with in a reactive manner rather than proactively. Yet increasingly a contributing factor in project difficulty and failure are the non-functional requirements imposed on the solution architecture. This paper proposes a Control Case approach to record and model non-functional requirements. This technique enables the control case to represent the nonfunctional requirements from different perspectives, most typically the various operating conditions. Furthermore, we propose an extension to the 4+1" view model for depicting software architecture by adding the control case view. The combination of both the use case and control case views thus reflects the complete requirements across the collective system life cycle views: design, process, implementation and deployment.