A Pattern for Partial Software Architecture

Article Preview

Abstract:

In software engineering, the problem on obtaining software architecture possessing the framework for satisfying requirements, and properties of playing roles as the technical basis and the managerial basis in software development process has not yet been solved. It is necessary to first solve a partial software architecture problem to get breakthrough. This paper focuses on a small part of MIS software, namely a user requirement assemble, and addresses issues on its structure pattern and architecting. Through the approach – to induce rationale from scenarios and to deduce structure from rationale, it is found that there exists a pattern so called as ‘multiple interfaces plus a functional calculator (MI+C in short)’ structure for all kinds of the assembles, which can be deployed as the technical basis for design and the managerial basis for the development process.

You might also be interested in these eBooks

Info:

Periodical:

Pages:

1838-1843

Citation:

Online since:

December 2012

Export:

Price:

Permissions CCC:

Permissions PLS:

Сopyright:

© 2013 Trans Tech Publications Ltd. All Rights Reserved

Share:

Citation:

[1] D. E. Perry, A. L. Wolf: Foundations for the Study of Software Architecture, ACM Software Engineering Notes, ACM SIGSOFT, ,Vol.7-4 (1992), pp.40-52

DOI: 10.1145/141874.141884

Google Scholar

[2] J. Bosch: Software Architecture: The Next Step, Proc. 1st European Workshop Software Architecture (EWSA04), Springer(2004),pp.194-199

DOI: 10.1007/978-3-540-24769-2_14

Google Scholar

[3] B. Boehm: Software engineering economics, Prentice-Hall(1981).

Google Scholar

[4] The Standish Group: CHAOS Report, http://www.standishgroup.com/chaos_2009.php

Google Scholar

[5] C. Gacek, A. Abd-Allah, B. Clark, B. Boehm: on the definition of software system architecture. Proceedings of the first international workshop on Architectures for software system (1995).

Google Scholar

[6] P. Kruchten. The 4+1 view model of architecture.IEEE Software, Vol.12-6 (1995), pp.45-50.

Google Scholar