From Viewpoints and Abstraction Levels in Software Engineering Towards Multi-Viewpoints/Multi-Hierarchy in Software Architecture

Viewpoints concept could be considered one of the major concepts introduced in the software engineering domain in order to enhance the architectural organization of complex systems by separating its concerns. Despite his ultimate importance, this concept must be evolved and hierarchized in order to allow the jump of software architectures field from its current range of complexity coverage and resolution to a new range more secure, more standardized and more appropriate with the current industrial needs. This paper begins with a survey of the role and usage of the viewpoints, and the hierarchy definition by abstraction levels concepts. Then presents a small but complete analysis of the related works and their limitations, in order to conclude with a proposition of current work on a multi-viewpoints and multi-abstraction levels software architecture.

[1]  H. Fuks,et al.  Multiparty specification , 1989, IWSSD '89.

[2]  WAPAN,et al.  Aspect Oriented Requirement Engineering: A Theme Based Vector Orientation Model , 2010 .

[3]  Antoine Beugnard,et al.  A Definition of "Abstraction Level" for Metamodels , 2009, 2009 16th Annual IEEE International Conference and Workshop on the Engineering of Computer Based Systems.

[4]  H. Delugach.  Using Conceptual Graphs to Analyze Multiple Views Of Software Requirements , 1998 .

[5]  Remco M. Dijkman,et al.  Consistency in multi-viewpoint design of enterprise information systems , 2008, Inf. Softw. Technol..

[6]  Nicholas May.  A Survey of Software Architecture Viewpoint Models , .

[7]  Eoin Woods,et al.  Software Systems Architecture: Working with Stakeholders Using Viewpoints and Perspectives , 2005 .

[8]  Bashar Nuseibeh,et al.  Expressing the relationships between multiple views in requirements specification , 1993, ICSE '93.

[9]  Björn Regnell,et al.  A hierarchical use case model with graphical representation , 1996, Proceedings IEEE Symposium and Workshop on Engineering of Computer-Based Systems.

[10]  Rich Hilliard.  Views and Viewpoints in Software Systems Architecture , 2000 .

[11]  Adil Anwar,et al.  A Formal Approach to Model Composition Applied to VUML , 2011, 2011 16th IEEE International Conference on Engineering of Complex Computer Systems.

[12]  Richard N. Taylor,et al.  Formal Modeling of Software Architectures at Multiple Levels of Abstraction , 1996 .

[13]  Harold Ossher,et al.  Subject-oriented composition rules , 1995, OOPSLA.

[14]  Alexander L. Wolf,et al.  Acm Sigsoft Software Engineering Notes Vol 17 No 4 Foundations for the Study of Software Architecture , 2022 .

[15]  Maria Istela Cagnin,et al.  Guidelines for Business Modeling Elaboration based on Views from Domain Information , 2007, WER.

[16]  Paul Clements,et al.  A Practical Method for Documenting Software Architectures , 2002 .

[17]  William N. Robinson,et al.  Negotiation behavior during requirement specification , 1990, [1990] Proceedings. 12th International Conference on Software Engineering.

[18]  Adil Anwar,et al.  Code generation in VUML profile: A model driven approach , 2009, 2009 IEEE/ACS International Conference on Computer Systems and Applications.

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

[20]  John F. Sowa,et al.  Extending and Formalizing the Framework for Information Systems Architecture , 1992, IBM Syst. J..

[21]  G. P. Mullery,et al.  CORE - a method for controlled requirement specification , 1979, ICSE 1979.

[22]  Houari A. Sahraoui,et al.  Concerned About Separation , 2006, FASE.

[23]  Ian Sommerville,et al.  Viewpoints: principles, problems and a practical approach to requirements engineering , 1997, Ann. Softw. Eng..

[24]  Mahmoud Nassar.  VUML: a viewpoint oriented UML extension , 2003, 18th IEEE International Conference on Automated Software Engineering, 2003. Proceedings..