Zhiqiang Fan
Tao Yue
ABSTRACT
Architecture description is critical for the development of large-scale software-intensive systems. However, there isn't a generic framework that can guide modelers through the derivation process of a domain-specific architecture modeling method (AMM). This process is usually complicated especially when the system is large-scale. In this paper, we propose a generic framework (named as GCVL) to guide modelers to devise AMMs for various domains. GCVL framework has been evaluated by applying it to derive an AMM (named as SAMM) for the ship command and control systems. SAMM is evaluated through a full-size industrial application. Results of the evaluation show that GCVL framework is applicable to define AMMs for large-scale software-intensive systems.
- ISO/IEC/IEEE 42010:2011(E): System and software engineering -- Architecture description. Dec. 1, 2011.Google Scholar
- Tom Strei. Open Architecture Overview. Oct 2003. 6th Annual System Engineering Conference, http://www.dtic.mil/ndia/2003systems/strei.pptGoogle Scholar
- Medvidovic, N. and RN Taylor, "A Classification and Comparison Framework for Software Architecture Description Languages," IEEE Transactions on Software Engineering, Jan, 2000. 26(1): pp: 70--93 Google ScholarDigital Library
- K. Goseva-Popstojanova, A. E. Hassan, A. Guedem, W. Abdelmoez, D. E. M. Nassar, H. H. Ammar, and A. Mili, Architectural-level risk analysis using UML, IEEE Trans. Softw. Eng., vol. 29, no. 10, pp: 946--960, 2003. Google ScholarDigital Library
- OMG. OMG Unified Modeling Language (OMG UML), Superstructure, V2.1.2. http://www.omg.org/docs/formal/07-11-02.pdfGoogle Scholar
- Sea Ling and Heinz Schmidt, Time Petri nets for workflow modeling and analysis, in Proc. IEEE Int. Conf. SMC, 2000, vol. 4, pp: 3039--3044.Google Scholar
- Karsai, G., Krahn, H., Pinkernell, C., et al. Design Guidelines for Domain Specific Languages. In: 9th OOPSLA Workshop on Domain-Specific Modeling (DSM' 09). (October 2009)Google Scholar
- OMG. OMG Systems Modeling Language (OMG SysML), Version 1.1. http://www.omg.org/spec/SysML/1.1. 02 Nov. 2008.Google Scholar
- DoD Deputy Chief Information Office.. DoD Architecture Framework Version 2.02. August 2010. http://cio-nii.defense.gov/sites/dodaf20/products/DoDAF_v2-02_web.pdfGoogle Scholar
- Ministry of Defence of the United Kingdom, Ministry of Defence Architecture Framework (MoDAF) Viewpoints and View, http://www.mod.uk/DefenceInternet/AboutDefence/WhatWeDo/InformationManagement/MODAF/ViewpointsAndViews.htmGoogle Scholar
- NATO Consultation, Command and Control Board, NATO Architecture Framework v3, 2007.Google Scholar
- The Open Group, The Open Group Architecture Framework (TOGAF), http://pubs.opengroup.org/architecture/togaf9-doc/arch/Google Scholar
- Philippe B. Kruchten. The 4+1 View Model of Architecture, IEEE Software, Nov 1995, 12(6): 42--50 Google ScholarDigital Library
- Draft Federal Information Processing Standards Publication 183. Integration definition for function modeling (IDEF0). 1993Google Scholar
- Federal Information Processing Standards Publication 184. Integration Definition for Information Modeling (IDEFIX). 21 Dec 1993. http://www.itl.nist.gov/fipspubs/idef1x.docGoogle Scholar
- Richard J. Mayer et al. Information Integration for Concurrent Engineering (IICE): IDEF3 Process Description Capture Method Report.Google Scholar
- Papyrus. http://www.papyrusuml.orgGoogle Scholar
- No Magic, Inc. Magic Draw. https://www.magicdraw.com/what_isGoogle Scholar
- IBM. Rational Tau. http://www.ibm.com/developerworks/rational/products/tau/Google Scholar
- Sabine Buckl, Sascha Krell, Christian M. Schweda, A Formal Approach to Architectural Descriptions - Refining the ISO Standard 42010, 6th International Workshop, CIAO! 2010, pp: 77--91Google Scholar
- International Organization for Standardization: ISO/IEC 42010:2007 systems and software engineering - recommended practice for architectural description of software-intensive systems (2007)Google Scholar
- T. B. Callo-Arias, P. America, and P. Avgeriou, "Defining execution viewpoints for a large and complex software-intensive system", Proceedings of WICSA/ECSA 2009, pp:1--10Google ScholarCross Ref
- Clements P., F. Bachmann, L. Bass, D. Garlan, J. Ivers, R. Little, R. Nord, and J. Stafford, Documenting Software Architectures: Views and Beyond, Boston: Addison-Wesley, 2002 Google ScholarDigital Library
- M. Z. Iqbal, S. Ali, T. Yue, and L. Briand, Experiences of Applying UML/MARTE on Three Industrial Projects, ACM/IEEE 15th International Conference, MODELS 2012, pp: 642--658 Google ScholarDigital Library
Index Terms
- A generic framework for deriving architecture modeling methods for large-scale software-intensive systems
Recommendations
Software architecture constraint reuse-by-composition
Architecture constraints are specifications which enable developers to formalize design rules that architectures should respect, like the topological conditions of a given architecture pattern or style. These constraints can serve as a documentation to ...
Architecture Design for the Large-Scale Software-Intensive Systems: A Decision-Oriented Approach and the Experience
ICECCS '09: Proceedings of the 2009 14th IEEE International Conference on Engineering of Complex Computer SystemsSoftware architectures are considered the key means to manage the complexity of large-scale systems from the high abstraction levels and system-wide perspectives. The traditional software design methodologies and the emerging architecture design methods ...
Modeling and implementing software architecture with acme and archJava
OOPSLA '04: Companion to the 19th annual ACM SIGPLAN conference on Object-oriented programming systems, languages, and applicationsSoftware architecture describes the high-level organization of a software system, and is essential both for reasoning about system properties and for implementing and evolving code. This poster describes two architecture-related tools: AcmeStudio for ...
Comments