Name
Abstract | ||
|---|---|---|
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 (NFR) 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 NFR imposed on the solution architecture. This paper outlines a control case approach to record and model
NFR. This technique enables the control case to represent the NFR from different perspectives, most typically the various
operating conditions. We also propose an extension to the “4 + 1” view model for depicting software architecture by adding
the control case view. In addition, a detailed control case modeling example is illustrated to demonstrate how these techniques
may be applied during development. Taken together, we suggest that 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. |
Year | DOI | Venue |
|---|---|---|
2008 | 10.1007/s10257-007-0057-x | Inf. Syst. E-Business Management |
Keywords | Field | DocType |
control case use case non-functional requirements nfr,operant conditioning,design process,software architecture,use case,life cycle,non functional requirement,functional requirement,system architecture | Functional requirement,Software engineering,Use-case analysis,Computer science,Solution architecture,Knowledge management,Systems architecture,Software architecture,System lifecycle,View model,Operations management,Non-functional requirement | Journal |
Volume | Issue | ISSN |
6 | 1 | 1617-9854 |
Citations | PageRank | References |
5 | 0.53 | 9 |
Authors | ||
2 | ||
Name | Order | Citations | PageRank |
|---|---|---|---|
| Joe Zou | 1 | 141 | 8.85 |
| Christopher J. Pavlovski | 2 | 104 | 7.22 |