Abstract
When design software architecture for large systems, designers often face with the problem how to move from requirements to a coarse-grained abstract architecture, then gradually refine it into more concrete ones, and last to detail design and implementation. Steps involved to implement such a process remain vague. Designers usually implement this process intuitively and opportunistically. We propose a Gradually Proceeded Software Architecture Design Process called GADesign. GADesign divides software architecture design into several phases and provides a sequence of well-defined steps to make this process more transparent and easier to be implemented.
This work is supported by Beijing Government’ Sponsor Plan for New Star in Science and Technology (No. H013610270112).
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
References
Garlan, D., Allen, R., Ockerbloom, J.: Exploiting Style in Architectural Design Environments. ACM SIGSOFT Software Engineering Notes 19, 175–188 (1994)
Luckham, D.C.: Rapide: a Language and Toolset for Simulation of Distributed Systems by Partial Ordering of Events. In: DIMACS Partial Order Methods Workshop IV. Princeton University, Princeton (1996)
Shaw, M., DeLine, R., Klein, D.V.: Abstractions for Software Architecture and Tools to Support Them. IEEE Transactions on Software Engineering 21, 314–335 (1995)
Allen, R.: A Formal Approach to Software Architecture. Technical Report, CMU-CS-97-144, Carnegie Mellon University (1997)
Shaw, M., Clements, P.: A Field Guide to Boxology: Preliminary Classification of Architectural Styles for Software Systems. In: Proceedings of 21st International Computer Software and Applications Conference, pp. 6–13 (1997)
Buschmann, F., Meunier, R., Rohnert, H., Sommerlad, P., Stal, M.: Pattern-Oriented Software Architecture: a System of Patterns. Addison-Wesley, Reading (1996)
Kazman, R., Abowd, G., Bass, L., Clements, P.: Scenario-Based Analysis of Software Architecture. IEEE Software 13, 47–55 (1996)
Kazman, R., Klein, M., Clements, P.: ATAM: Method for Architecture Evaluation (CMU/SEI-2000-TR-004, ADA382629). Software Engineering Institute, Carnegie Mellon University, Pittsburgh (2000), http://www.sei.cmu.edu/publications/documents/00.reports/00tr004.html
IEEE Standard 1471: IEEE Recommended Practice for Architectural Description of Software-Intensive Systems. IEEE Computer Society, Los Alamitos (2000)
Clements, P., Bachmann, F., Bass, L.: Documenting Software Architectures: Views and Beyond. Addison-Wesley, MA (2002)
Kazman, R.: Tool Support for Architecture Analysis and Design. In: Proceedings of the Second Int. Workshop on Software Architectures, pp. 94–97. ACM Press, New York (1996)
Grundy, J., Hosking, J.: Softarch: Tool Support for Integrated Software Architecture Development. International Journal Of Software Engineering and Knowledge Engineering (2003)
Bass, L., Clements, P., Kazman, R.: Software Architecture in Practice. Addison-Wesley, Reading (2003)
Kazman, R., Kruchten, P., Nord, R.L., Tomayko, J.E.: Integrating Software-Architecture-Centric Methods into the Rational Unified Process. TECHNICAL REPORT,CMU/SEI-2004-TR-011, Software Engineering Institute, Carnegie Mellon University (2004), http://www.sei.cmu.edu/publications/documents/04.reports/04tr011.html
Jacobson, I., Booch, G., Rumbaugh, J.: The Unified Software Development Process. Addison-Wesley, MA (1999)
Hong, M., Feng, C., Yaodong, F.: ABC: Architecture Based, Component Oriented Software Development Method. Journal of Software 14, 721–732 (2003)
Bachmann, F., Bass, L., Chastek, G.: The Architecture Based Design Method. Technical Report CMU/SEI-2000-TR-001, Software Engineering Institute, Carnegie Mellon University (2000), http://www.sei.cmu.edu/publications/documents/00.reports/00tr001.html
Bachmann, D., Bass, L., Klein, M.: Moving from Quality Attribute Requirements to Architectural Decisions. In: Proceedings of Second International Software Requirements to Architectures Workshop Located at ICSE 2003, pp. 122–130 (2003)
Object Management Group. UML 2.0 Superstructure Specification: Final Adopted Specification (August 2003), http://www.omg.org/docs/ptc/03-08-02.pdf
Gamma, E., Helm, R., Johnson, R., Vlissides, J.: Design Patterns-Elements of Reusable Object-Oriented Software. Addison-Wesley, MA (1995)
Douglass, B.P.: Doing Hard Time: Developing Real-Time Systems with UML, Objects, Frameworks, and Patterns. Addison-Wesley, Reading (1999)
Buschmann, F.: Building Software with Patterns (1998), http://www.daimi.au.dk/~apaipi/dpf/EuroPLoP.pdf
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2006 Springer-Verlag Berlin Heidelberg
About this paper
Cite this paper
Tian, L., Zhang, L., Zhou, B., Qian, G. (2006). A Gradually Proceeded Software Architecture Design Process. In: Li, M., Boehm, B., Osterweil, L.J. (eds) Unifying the Software Process Spectrum. SPW 2005. Lecture Notes in Computer Science, vol 3840. Springer, Berlin, Heidelberg. https://doi.org/10.1007/11608035_18
Download citation
DOI: https://doi.org/10.1007/11608035_18
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-540-31112-6
Online ISBN: 978-3-540-32450-8
eBook Packages: Computer ScienceComputer Science (R0)