Foundations for the study of software architecture
ACM SIGSOFT Software Engineering Notes
Beyond definition/use: architectural interconnection
IDL '94 Proceedings of the workshop on Interface definition languages
Abstractions for Software Architecture and Tools to Support Them
IEEE Transactions on Software Engineering - Special issue on software architecture
Formalizing architectural connection
ICSE '94 Proceedings of the 16th international conference on Software engineering
Software architecture in practice
Software architecture in practice
Object-Oriented Software Engineering: A Use Case Driven Approach
Object-Oriented Software Engineering: A Use Case Driven Approach
Runtime recovery and manipulation of software architecture of component-based systems
Automated Software Engineering
Development of software engineering: co-operative efforts from academia, government and industry
Proceedings of the 28th international conference on Software engineering
| Hi-index | 0.00 |
This paper presents the idea of Software Architecture Oriented Requirements Engineering, a complementary approach to existing requirements engineering processes and methods. The main objective is to introduce concepts and principles of software architecture into requirement analysis and requirement specification, supporting requirement reuse, traceability between requirement specifications and system design, and consistency in the whole software development process more effectively. The paper views connectors as the first-class entities in the problem space, not just in the solution space as most of current research on software architecture does, hence the connector recognition and specification are same important as component recognition and specification in requirements engineering. Based on this idea, the paper presents a new software development process and corresponding requirements engineering process, gives some guidelines for connector recognition, and borrows the notations of software architecture description to specify the functional and behavioural requirements at a high abstraction level. It must be pointed out that the approach presented in this paper is not a substitute for existing ones, but a complement to them from another perspective and at a different abstraction level.