Software architecture: perspectives on an emerging discipline
Software architecture: perspectives on an emerging discipline
Pattern-oriented software architecture: a system of patterns
Pattern-oriented software architecture: a system of patterns
From object-oriented to goal-oriented requirements analysis
Communications of the ACM
Guiding Goal Modeling Using Scenarios
IEEE Transactions on Software Engineering
Experience with performing architecture tradeoff analysis
Proceedings of the 21st international conference on Software engineering
PuLSE: a methodology to develop software product lines
SSR '99 Proceedings of the 1999 symposium on Software reusability
Applying WinWin to quality requirements: a case study
ICSE '01 Proceedings of the 23rd International Conference on Software Engineering
FORM: A feature-oriented reuse method with domain-specific reference architectures
Annals of Software Engineering
Feature-Oriented Project Line Engineering
IEEE Software
Software Reuse Research: Status and Future
IEEE Transactions on Software Engineering
IEEE Transactions on Software Engineering
IEEE Software
Requirements Abstraction Model
Requirements Engineering
Improving use case driven analysis using goal and scenario authoring: a linguistics-based approach
Data & Knowledge Engineering - Special issue: Application of natural language to information systems (NLDB04)
From requirements negotiation to software architecture decisions
Information and Software Technology
Reuse of Architectural Knowledge in SPL Development
ICSR '09 Proceedings of the 11th International Conference on Software Reuse: Formal Foundations of Reuse and Domain Engineering
Ontological analysis for generating baseline architectural descriptions
ECSA'10 Proceedings of the 4th European conference on Software architecture
Specific modeling of the business processes
DNCOCO'10 Proceedings of the 9th WSEAS international conference on Data networks, communications, computers
Hi-index | 0.00 |
One of the benefits of software product line approach is to improve time-to-market. The changes in market needs cause software requirements to be flexible in product lines. Whenever software requirements are changed, software architecture should be evolved to correspond with them. Therefore, domain architecture should be designed based on domain requirements. It is essential that there is traceability between requirements and architecture, and that the structure of architecture is derived from quality requirements. The purpose of this paper is to provide a framework for modeling domain architecture based on domain requirements within product lines. In particular, we focus on the traceable relationship between requirements and architectural structures. Our framework consists of processes, methods, and a supporting tool. It uses four basic concepts, namely, goal based domain requirements analysis, Analytical Hierarchy Process, Matrix technique, and architecture styles. Our approach is illustrated using HIS (Home Integration System) product line. Finally, industrial examples are used to validate DRAMA.