A framework for information systems architecture
IBM Systems Journal
Telos: representing knowledge about information systems
ACM Transactions on Information Systems (TOIS)
Foundations for the study of software architecture
ACM SIGSOFT Software Engineering Notes
Using style to understand descriptions of software architecture
SIGSOFT '93 Proceedings of the 1st ACM SIGSOFT symposium on Foundations of software engineering
Software packaging
Representing and using performance requirements during the development of information systems
EDBT '94 Proceedings of the 4th international conference on extending database technology: Advances in database technology
Representing and using non-functional requirements: a process-oriented approach
Representing and using non-functional requirements: a process-oriented approach
Dealing with non-functional requirements: three experimental studies of a process-oriented approach
Proceedings of the 17th international conference on Software engineering
The sciences of the artificial (3rd ed.)
The sciences of the artificial (3rd ed.)
Extending the Potts and Bruns model for recording design rationale
ICSE '91 Proceedings of the 13th international conference on Software engineering
SAAM: a method for analyzing the properties of software architectures
ICSE '94 Proceedings of the 16th international conference on Software engineering
On formal requirements modeling languages: RML revisited
ICSE '94 Proceedings of the 16th international conference on Software engineering
Understanding “why” in software process modelling, analysis, and design
ICSE '94 Proceedings of the 16th international conference on Software engineering
Software architecture: practice, potential, and pitfalls
ICSE '94 Proceedings of the 16th international conference on Software engineering
Software architectures: critical success factors and cost drivers
ICSE '94 Proceedings of the 16th international conference on Software engineering
The Pareto principle applied to software quality assurance
Handbook of software quality assurance (3rd ed.)
On the criteria to be used in decomposing systems into modules
Communications of the ACM
Performance Engineering of Software Systems
Performance Engineering of Software Systems
Representing and Using Nonfunctional Requirements: A Process-Oriented Approach
IEEE Transactions on Software Engineering - Special issue on knowledge representation and reasoning in software development
Dealing with Security Requirements During the Development of Information Systems
CAiSE '93 Proceedings of Advanced Information Systems Engineering
Using non-functional requirements to systematically support change
RE '95 Proceedings of the Second IEEE International Symposium on Requirements Engineering
Problem-Solving Methods in Artificial Intelligence
Problem-Solving Methods in Artificial Intelligence
Quality management activities for software architecture and software architecture process
SE'07 Proceedings of the 25th conference on IASTED International Multi-Conference: Software Engineering
Security policy refinement and enforcement for the design of multi-level secure systems
Journal of Computer Security - Privacy, Security and Trust (PST) Technologies: Evolution and Challenges
Architecture-based refinements for secure computer systems design
Proceedings of the 2006 International Conference on Privacy, Security and Trust: Bridge the Gap Between PST Technologies and Business Services
Visualization and comparison of architecture rationale with semantic web technologies
Journal of Systems and Software
Hi-index | 0.00 |
Quality issues such as modifiability, performance, reusability, comprehensibility and security, are often crucial to a software system. As such, quality requirements (or nonfunctional requirements, NFRs) should be addressed as early as possible in a software lifecycle and properly reflected in a software architecture before committing to a detailed design. This paper discusses how the treatment of NFRs as goals (which may be synergistic or conflicting) serves to systematically guide selection among architectural design alternatives. During the architectural design process, goals are decomposed, design alternatives are analysed with respect to their tradeoffs, design decisions are made and rationalised, and goal achievement is evaluated. This process can be supported by a body of knowledge. This paper1 outlines an approach by which such knowledge can be organised. The approach draws on our framework for dealing with NFRs, which has been applied to several NFRs (accuracy, performance, security), used to study several information systems, and is now applied to architecture. This approach is illustrated by a preliminary study of architectural design for a KWIC (Key Word in Context) system.