skip to main content
article

A web-based tool for managing architectural design decisions

Published: 01 September 2006 Publication History

Abstract

Software architectures represent the design for describing the main parts of a software system. In software projects, different stakeholders with different roles may need to share the documentation generated during the project. Also, during the architecture construction phase we need to communicate the architecture to the stakeholders involved in the process, but the lack of tools for documenting, managing and sharing this architectural knowledge constitutes a big barrier. In other cases it can be useful to recreate the design decisions taken because such decisions are frequently lost during the development process. To cover these issues, we outline in this paper a web-based tool able to record and manage architecture design decisions.

References

[1]
Bass, L., Clements P. and Kazman, R. Software Architecture in Practice, Addison-Wesley, 2nd edition, (2003).
[2]
Bosch, J. Design and use of Software Architecture. Adopting and Evolving a Product Line Approach. Addison-Wesley, (2000).
[3]
Bosch, J. Software Architecture: The Next Step, Proceedings of the 1st European Workshop on Software Architecture (EWSA 2004), Springer-Verlag, LNCS 3047, pp. 194-199 (2004).
[4]
Clements, P., Bachman, F., Bass, L., Garlan, D., Ivers, J., Little, R., Nord, R. and Stafford, J. Documenting Software Architectures. Views and Beyond, Addison-Wesley (2003).
[5]
Dueñas, J. C. and Hauswirth, M. Hyper-linked Software Architectures for Concurrent Engineering. In Proceedings of Concurrent Engineering Europe 97, Erlangen-Nuremberg, Germany, pp: 3-10. Society for Computer Simulation. (1997).
[6]
Dueñas, J.C. and Capilla, R. The Decision View of Software Architecture, Proceedings of the 2nd European Workshop on Software Architecture (EWSA 2005), Springer-Verlag, LNCS 3047, pp. 222-230 (2005).
[7]
Gomaa, H. and Shin, E. A Multiple View Meta-modeling Approach for Variability Management in Software Product Lines. Eighth International Conference on Software Reuse: Methods, Techniques and Tools. LNCS 3107, Springer Verlag, 2004.
[8]
IEEE Recommended Practice for Architectural Description of Software-Intensive Systems, IEEE Std. 1471-2000 (2000).
[9]
Jansen, A. and Bosch, J. Software Architecture as a Set of Architectural Design Decisions, 5th IEEE/IFIP Working Conference on Software Architecture, (2005).
[10]
Jazayeri, M., Ran, A. and van der Linden, F. Software Architecture for Product Families. Principles and Practice, Addison-Wesley (2000).
[11]
Katara, M. and Katz, S. Architectural Views of Aspects. Proceedings of AOSD 2003, Boston, USA, ACM, pp.1-10 (2003).
[12]
Kruchten P. Architectural Blueprints. The "4+1" View Model of Software Architecture, IEEE Software 12 (6), pp.42-50 (1995).
[13]
Kruchten, P. An Ontology of Architectural Design Decisions, in Proceedings of 2nd Groningen Workshop on Software Variability Management, Groningen, NL (2004).
[14]
Kruchten, P., Lago, P., van Vliet, H. and Wolf, T. Building up and Exploiting Architectural Knowledge, 5th IEEE/IFIP Working Conference on Software Architecture, (2005).
[15]
Lee, K., and Kang, K. Feature Dependency Analysis for Product Line Component Design, International Conference on Software Reuse, LNCS 3107 Springer-Verlag, pp. 69-85, (2004).
[16]
Liao, L. From Requirements to Architecture: The State of the Art in Software Architecture Design, http://www.cs.washington.edu/homes/liaolin/Courses/architecture02.pdf
[17]
Lindvall, M., Rus, I., Jammalamadaka, R. and Thakker, R. Software Tools for Knowledge Management. Fraunhofer Center for Experimental Software Engineering, Maryland, USA, http://www.dacs.dtic.mil/techs/kmse/swtools4km.pdf (2001).
[18]
Perry, D.E. and Wolf, A.L. "Foundations for the Study of Software Architecture", Software Engineering Notes, ACM SIGSOFT, October 1992, pp. 40-52
[19]
Rozanski, N. and Woods. E. Software Systems Architecture, Addison-Wesley (2005).
[20]
Shaw, M. and Garlan, D. Software Architecture, Prentice Hall (1996).
[21]
Tang, A., Babar, M.A., Gorton, I. and Han, J.A. A Survey of the Use and Documentation of Architecture Design Rationale, 5th IEEE/IFIP Working Conference on Software Architecture, (2005).
[22]
Tyree, J. and Akerman, A. Architecture Decisions: Demystifying Architecture. IEEE Software, vol. 22, no 2, pp. 19-27, (2005).
[23]
The GRIFFIN project, A GRId For information about architectural knowledge, http://griffin.cs.vu.nl/
[24]
Wang, A., Sherdil, K. and Madhavji, N.H. ACCA: An Architecture-centric Concern Analysis Method, 5th IEEE/IFIP Working Conference on Software Architecture, (2005).
[25]
Woods, E. Experiences Using Viewpoints for Information Systems Architecture: An Industrial Experience Report. F. Oquendo (Ed) Proceedings of the First European Workshop on Software Architecture, LNCS 3047, Springer Verlag (2004).

Cited By

View all
  • (2024)Enhancing Automated Program Repair with Solution DesignProceedings of the 39th IEEE/ACM International Conference on Automated Software Engineering10.1145/3691620.3695537(1706-1718)Online publication date: 27-Oct-2024
  • (2024)DRMiner: Extracting Latent Design Rationale from Jira Issue LogsProceedings of the 39th IEEE/ACM International Conference on Automated Software Engineering10.1145/3691620.3695019(468-480)Online publication date: 27-Oct-2024
  • (2024)Are Architecture Design Decisions in Distributed Teams Supported by Tools?Enterprise Information Systems10.1007/978-3-031-64748-2_17(348-365)Online publication date: 26-Jul-2024
  • Show More Cited By

Recommendations

Comments

Information & Contributors

Information

Published In

cover image ACM SIGSOFT Software Engineering Notes
ACM SIGSOFT Software Engineering Notes  Volume 31, Issue 5
September 2006
110 pages
ISSN:0163-5948
DOI:10.1145/1163514
Issue’s Table of Contents

Publisher

Association for Computing Machinery

New York, NY, United States

Publication History

Published: 01 September 2006
Published in SIGSOFT Volume 31, Issue 5

Check for updates

Author Tags

  1. architecture design decisions
  2. requirements
  3. software architecture
  4. software patterns
  5. traceability

Qualifiers

  • Article

Contributors

Other Metrics

Bibliometrics & Citations

Bibliometrics

Article Metrics

  • Downloads (Last 12 months)21
  • Downloads (Last 6 weeks)1
Reflects downloads up to 18 Feb 2025

Other Metrics

Citations

Cited By

View all
  • (2024)Enhancing Automated Program Repair with Solution DesignProceedings of the 39th IEEE/ACM International Conference on Automated Software Engineering10.1145/3691620.3695537(1706-1718)Online publication date: 27-Oct-2024
  • (2024)DRMiner: Extracting Latent Design Rationale from Jira Issue LogsProceedings of the 39th IEEE/ACM International Conference on Automated Software Engineering10.1145/3691620.3695019(468-480)Online publication date: 27-Oct-2024
  • (2024)Are Architecture Design Decisions in Distributed Teams Supported by Tools?Enterprise Information Systems10.1007/978-3-031-64748-2_17(348-365)Online publication date: 26-Jul-2024
  • (2023)"Let’s Discuss it in a Team Meeting!" Collaboration Challenges of Distributed Software Design2023 49th Euromicro Conference on Software Engineering and Advanced Applications (SEAA)10.1109/SEAA60479.2023.00055(315-318)Online publication date: 6-Sep-2023
  • (2022)A Review on Architectural Design and its ProcessSustainable Architecture and Building Materials10.46632/sabm/1/1/11:1(01-07)Online publication date: 1-Apr-2022
  • (2021)Continuous Rationale Visualization2021 Working Conference on Software Visualization (VISSOFT)10.1109/VISSOFT52517.2021.00013(33-43)Online publication date: Sep-2021
  • (2021)Classifying Model-View-Controller Software Applications Using Self-Organizing MapsIEEE Access10.1109/ACCESS.2021.30663489(45201-45229)Online publication date: 2021
  • (2020)The Evolution of Architectural Decision Making as a Key Focus Area of Software Architecture Research: A Semi-Systematic Literature Study2020 IEEE International Conference on Software Architecture (ICSA)10.1109/ICSA47634.2020.00015(69-80)Online publication date: Mar-2020
  • (2020)Does BERT Understand Code? – An Exploratory Study on the Detection of Architectural Tactics in CodeSoftware Architecture10.1007/978-3-030-58923-3_15(220-228)Online publication date: 14-Sep-2020
  • (2019)Leveraging usage data of software architecture artefactsProceedings of the 2nd International Workshop on Establishing a Community-Wide Infrastructure for Architecture-Based Software Engineering10.1109/ECASE.2019.00011(13-21)Online publication date: 27-May-2019
  • Show More Cited By

View Options

Login options

View options

PDF

View or Download as a PDF file.

PDF

eReader

View online with eReader.

eReader

Figures

Tables

Media

Share

Share

Share this Publication link

Share on social media