Enterprise Architecture: A Framework Supporting System Quality Analysis

Enterprise Architecture is a model-based approach to business-oriented IT management. To promote good IT decision making, an enterprise architecture framework needs to explicate what kind of analyses it supports. Since creating enterprise architecture models is expensive and without intrinsic value, it is desirable to only create enterprise architecture models based on metamodels that support well-defined analyses. This paper suggests a metamodel derived specifically with a set of theory-based system quality analyses in mind. The ISO 9126-based theory behind the system quality analysis is introduced in the shape of an extended influence diagram. Finally, an example illustrates that our theory-based metamodel does support system quality analysis.

[1]  Richard E. Neapolitan,et al.  Learning Bayesian networks , 2007, KDD '07.

[2]  Barry Boehm,et al.  Characteristics of software quality , 1978 .

[3]  Robert Lagerström.  Analyzing System Maintainability using Enterprise Architecture Models , 2007 .

[4]  Ronald A. Howard,et al.  Influence Diagram Retrospective , 2005, Decis. Anal..

[5]  Eila Niemelä,et al.  The impact of maintainability on component-based software systems , 2003, 2003 Proceedings 29th Euromicro Conference.

[6]  Grace A. Lewis,et al.  Current Perspectives on Interoperability , 2004 .

[7]  Ira Pramanick,et al.  High Availability , 2001, Int. J. High Perform. Comput. Appl..

[8]  A. Scheer.  Business Process Engineering: Reference Models for Industrial Enterprises , 1994 .

[9]  M. Mari,et al.  The impact of maintainability on component-based software systems , 2003, 2003 Proceedings 29th Euromicro Conference.

[10]  Stefan Poslad,et al.  Towards improved trust and security in FIPA agent platforms , 2004 .

[11]  Pontus Johnson,et al.  Enterprise Software System Integration : An Architectural Perspective , 2002 .

[12]  Michael Scriven.  Definitions in analytical philosophy , 1954 .

[13]  Ross D. Shachter.  Evaluating Influence Diagrams , 1986, Oper. Res..

[14]  Jakob Nielsen,et al.  Usability engineering , 1997, The Computer Science and Engineering Handbook.

[15]  Kurt Kosanke.  CIMOSA—overview and status , 1995 .

[16]  Russell R. Barton,et al.  Institute for Operations Research and the Management Sciences , 2004, INFORMS J. Comput..

[17]  Mathias Ekstedt,et al.  Enterprise Architecture : Models and Analyses for Information Systems Decision Making , 2007 .

[18]  Finn V. Jensen,et al.  Bayesian Networks and Decision Graphs , 2001, Statistics for Engineering and Information Science.

[19]  Richard N. Taylor,et al.  A language and environment for architecture-based software development and evolution , 1999, Proceedings of the 1999 International Conference on Software Engineering (IEEE Cat. No.99CB37002).

[20]  Manuel J. Barranco García,et al.  A Method for Estimating Maintenance Cost in a Software Project: A Case Study , 1997, J. Softw. Maintenance Res. Pract..

[21]  Herbert Hecht,et al.  Systems Reliability and Failure Prevention , 2003 .

[22]  日本規格協会.  情報技術 : 情報セキュリティ管理実施基準 : 国際規格 : ISO/IEC 17799 = Information technology : code of practice for infromation security management : international standard : ISO/IEC 17799 , 2000 .

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

[24]  Siu Leung Chung,et al.  An Economic Model to Estimate Software Rewriting and Replacement Times , 1996, IEEE Trans. Software Eng..

[25]  Juan Carlos Granja-Alvarez,et al.  A method for estimating maintenance cost in a software project: a case study , 1997 .

[26]  Ronald A. Howard,et al.  Influence Diagrams , 2005, Decis. Anal..

[27]  Gary Stoneburner.  SP 800-33. Underlying Technical Models for Information Technology Security , 2001 .

[28]  Robert Lagerström,et al.  Enterprise architecture analysis with extended influence diagrams , 2007, Inf. Syst. Frontiers.

[29]  Michael R. Lyu,et al.  Handbook of software reliability engineering , 1996 .

[30]  K. K. Aggarwal,et al.  An integrated measure of software maintainability , 2002, Annual Reliability and Maintainability Symposium. 2002 Proceedings (Cat. No.02CH37318).

[31]  Theodore J. Williams,et al.  The Purdue Enterprise Reference Architecture , 1992, DIISM.

[32]  Jakob Nielsen,et al.  Ten Usability Heuristics , 2006 .

[33]  Ross D. Shachter.  Probabilistic Inference and Influence Diagrams , 1988, Oper. Res..

[34]  S. Mohan,et al.  Performance Solutions: A Practical Guide to Creating Responsive, Scalable Software [Book Review] , 2003, IEEE Software.

[35]  Sushil Jajodia,et al.  Rewriting Histories: Recovering from Malicious Transactions , 2004, Distributed and Parallel Databases.

[36]  Mark Kasunic,et al.  Measuring Systems Interoperability: Challenges and Opportunities , 2001 .

[37]  Yuan-Shun Dai,et al.  Computing systems reliability - models and analysis , 2004 .

[38]  Gary Stoneburner,et al.  Underlying technical models for information technology security :: recommendations of the National Institute of Standards and Technology , 2001 .

[39]  A. Berztiss,et al.  Requirements Engineering , 2002, J. Object Technol..

[40]  David Garlan,et al.  Specifying and Analyzing Dynamic Software Architectures , 1998, FASE.

[41]  Rick Kazman,et al.  Evaluating Software Architectures: Methods and Case Studies , 2001 .

[42]  Robert Lagerström,et al.  Extended Influence Diagram Generation , 2007, IESA.

[43]  Robert B. Grady,et al.  Software Metrics: Establishing a Company-Wide Program , 1987 .

[44]  Floyd Piedad,et al.  High Availability: Design, Techniques and Processes , 2000 .

[45]  Daniel P. Siewiorek,et al.  High-availability computer systems , 1991, Computer.

[46]  Thomas Redman,et al.  Data quality for the information age , 1996 .