Software architecture: perspectives on an emerging discipline
Software architecture: perspectives on an emerging discipline
Software architecture in practice
Software architecture in practice
Objects, components, and frameworks with UML: the catalysis approach
Objects, components, and frameworks with UML: the catalysis approach
The Unified Modeling Language reference manual
The Unified Modeling Language reference manual
Software technology maturation
ICSE '85 Proceedings of the 8th international conference on Software engineering
Applied software architecture
Acme: architectural description of component-based systems
Foundations of component-based systems
UML components: a simple process for specifying component-based software
UML components: a simple process for specifying component-based software
Problem frames: analyzing and structuring software development problems
Problem frames: analyzing and structuring software development problems
Documenting Software Architectures: Views and Beyond
Documenting Software Architectures: Views and Beyond
Why can't they create architecture models like "Developer X"?: an experience report
Proceedings of the 25th International Conference on Software Engineering
Software Engineering (7th Edition)
Software Engineering (7th Edition)
Reasoning about partial goal satisfaction for requirements and design engineering
Proceedings of the 12th ACM SIGSOFT twelfth international symposium on Foundations of software engineering
Engineering distributed software: a structural discipline
Proceedings of the 10th European software engineering conference held jointly with 13th ACM SIGSOFT international symposium on Foundations of software engineering
Hi-index | 0.00 |
System builders have historically used informal software architecture models to understand options, make choices, and communicate with others. Research into software architecture over the past fifteen years has indicated that more precise architecture models may be beneficial. At a large financial firm, we applied precise software architecture techniques on four software projects and this experience has revealed a number of practical issues. We made the following observations across the projects: 1) Architecture models can be used to bridge gaps between business requirements and technology, 2) A small collection of techniques and a detail knob are practical and useful in a variety of projects, 3) Architecture modeling techniques amplify the skills of the architects, 4) A model of domain concepts and relationships is helpful when building architecture models, and 5) It is difficult to know when to stop adding detail to your architecture model. We believe that these observations motivate future research and can help practitioners make software architecture more effective in practice.