Comprehensive measurement framework for enterprise architectures

Enterprise Architecture defines the overall form and function of systems across an enterprise involving the stakeholders and providing a framework, standards and guidelines for project-specific architectures. Project-specific Architecture defines the form and function of the systems in a project or program, within the context of the enterprise as a whole with broad scope and business alignments. Application-specific Architecture defines the form and function of the applications that will be developed to realize functionality of the system with narrow scope and technical alignments. Because of the magnitude and complexity of any enterprise integration project, a major engineering and operations planning effort must be accomplished prior to any actual integration work. As the needs and the requirements vary depending on their volume, the entire enterprise problem can be broken into chunks of manageable pieces. These pieces can be implemented and tested individually with high integration effort. Therefore it becomes essential to analyze the economic and technical feasibility of realizable enterprise solution. It is difficult to migrate from one technological and business aspect to other as the enterprise evolves. The existing process models in system engineering emphasize on life-cycle management and low-level activity coordination with milestone verification. Many organizations are developing enterprise architecture to provide a clear vision of how systems will support and enable their business. The paper proposes an approach for selection of suitable enterprise architecture depending on the measurement framework. The framework consists of unique combination of higher order goals, non-functional requirement support and inputs-outcomes pair evaluation. The earlier efforts in this regard were concerned about only custom scales indicating the availability of a parameter in a range.

[1]  Leonard J. Bass,et al.  Designing software architectures to achieve quality attribute requirements , 2005, IEE Proc. Softw..

[2]  Julio Cesar Sampaio do Prado Leite,et al.  Nonfunctional requirements: from elicitation to conceptual models , 2004, IEEE Transactions on Software Engineering.

[3]  John A. Zachman,et al.  A Framework for Information Systems Architecture , 1987, IBM Syst. J..

[4]  Naji Habra,et al.  Towards a generic framework for empirical studies of Model-Driven Engineering , 2008 .

[5]  Philippe Kruchten,et al.  The 4+1 View Model of Architecture , 1995, IEEE Softw..

[6]  Paul Clements,et al.  Software Architecture in Practice: Addison-Wesley , 1998 .

[7]  Marie-Pierre Gervais,et al.  MDA Tool Components: a proposal for packaging know-how in model driven development , 2007, Software & Systems Modeling.

[8]  David Chen,et al.  Standards on enterprise integration and engineering—state of the art , 2004, Int. J. Comput. Integr. Manuf..

[9]  Lawrence Chung,et al.  Dealing with Non-Functional Requirements: Three Experimental Studies of a Process-Oriented Approach , 1995, 1995 17th International Conference on Software Engineering.

[10]  Oscar Pastor,et al.  Analyzing the influence of certain factors on the acceptance of a model-based measurement procedure in practice: An empirical study , 2008, ICSE 2008.

[11]  Paul Clements,et al.  Software architecture in practice , 1999, SEI series in software engineering.

[12]  Eila Niemelä,et al.  A Survey on Software Architecture Analysis Methods , 2002, IEEE Trans. Software Eng..

[13]  Ivar Jacobson,et al.  The Unified Software Development Process , 1999 .

[14]  Xiaoqing Frank Liu,et al.  Analysis of Conflicts among Non-Functional Requirements Using Integrated Analysis of Functional and Non-Functional Requirements , 2007, 31st Annual International Computer Software and Applications Conference (COMPSAC 2007).

[15]  IEEE-SA Standards Board , 2000 .