Change cases: use cases that identify future requirements
Proceedings of the 11th ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
Software architecture in practice
Software architecture in practice
Software architecture classification for estimating the cost of COTS integration
Proceedings of the 21st international conference on Software engineering
Adaptive Object-Oriented Software: The Demeter Method with Propagation Patterns
Adaptive Object-Oriented Software: The Demeter Method with Propagation Patterns
Management Information Systems: Managing the Digital Firm
Management Information Systems: Managing the Digital Firm
Architectural Mismatch: Why Reuse Is So Hard
IEEE Software
Architectural Mismatch: Why Reuse Is So Hard
IEEE Software
Documenting and Analyzing a Context-Sensitive Design Space
WICSA 3 Proceedings of the IFIP 17th World Computer Congress - TC2 Stream / 3rd IEEE/IFIP Conference on Software Architecture: System Design, Development and Maintenance
The pervasiveness of evolution in GRUMPS software
Software—Practice & Experience
The Use of the SAGA Tool for Gathering Requirements for Future Information Systems
HICSS '96 Proceedings of the 29th Hawaii International Conference on System Sciences Volume 2: Decision Support and Knowledge-Based Systems
A Model of Structured Discourse for Cooperating Intelligent Agent
HICSS '96 Proceedings of the 29th Hawaii International Conference on System Sciences Volume 2: Decision Support and Knowledge-Based Systems
Requirements monitoring in distributed environments
SDNE '95 Proceedings of the 2nd International Workshop on Services in Distributed and Networked Environments
How well can we predict changes at architecture design time?
Journal of Systems and Software
Consistency Management of Product Line Requirements
RE '01 Proceedings of the Fifth IEEE International Symposium on Requirements Engineering
IEEE Software
Recovering architectural assumptions
Journal of Systems and Software
Driving and managing architectural decisions with aspects
ACM SIGSOFT Software Engineering Notes
A survey of architecture design rationale
Journal of Systems and Software
Modeling and Documenting the Evolution of Architectural Design Decisions
SHARK-ADI '07 Proceedings of the Second Workshop on SHAring and Reusing architectural Knowledge Architecture, Rationale, and Design Intent
Documenting after the fact: Recovering architectural design decisions
Journal of Systems and Software
Automating the Trace of Architectural Design Decisions and Rationales Using a MDD Approach
ECSA '08 Proceedings of the 2nd European conference on Software Architecture
On the Role of Architectural Design Decisions in Software Product Line Engineering
ECSA '08 Proceedings of the 2nd European conference on Software Architecture
A scoped approach to traceability management
Journal of Systems and Software
A Tool to Visualize Architectural Design Decisions
QoSA '08 Proceedings of the 4th International Conference on Quality of Software-Architectures: Models and Architectures
Managing assumptions during agile development
SHARK '09 Proceedings of the 2009 ICSE Workshop on Sharing and Reusing Architectural Knowledge
A family of languages for architecture constraint specification
Journal of Systems and Software
Viability for codifying and documenting architectural design decisions with tool support
Journal of Software Maintenance and Evolution: Research and Practice
A model for variability design rationale in SPL
Proceedings of the Fourth European Conference on Software Architecture: Companion Volume
Software designers, are you biased?
Proceedings of the 6th International Workshop on SHAring and Reusing Architectural Knowledge
Building up and reasoning about architectural knowledge
QoSA'06 Proceedings of the Second international conference on Quality of Software Architectures
On the modularity impact of architectural assumptions
Proceedings of the 2012 workshop on Next Generation Modularity Approaches for Requirements and Architecture
Issue-based variability management
Information and Software Technology
Hi-index | 0.00 |
Design for change is a well-known adagium in software engineering. We separate concerns, employ well-designed interfaces, and the like to ease evolution of the systems we build. We model and build in changeability through parameterization and variability points (as in product lines). These all concern places where we explicitly consider variability in our systems. We conjecture that it is helpful to also think of and explicitly model invariability, things in our systems and their environment that we assume will not change. We give examples from the literature and our own experience to illustrate how evolution can be seriously hampered because of tacit assumptions made. In particular, we show how we can explicitly model assumptions in an existing product family. From this, we derive a metamodel to document assumptions. Finally, we show how this type of modeling adds to our understanding of the architecture and the decisions that led to it.