A New Approach to Component-Based Development of Software Architecture
the author of the article can submit here a request for assignment of a DOI number to this resource!
Cost of the service: euros 10,00 (for a DOI)
Information system architecture handles requirements of information and systems to support a business through describing structural and behavioral capabilities of the system. Software architecture is defined in terms of computational components and interactions among those components. In this context, component-based development is an approach considered the most promising way of developing information systems. Typically, UML 2 component diagrams are used as an architecture-level artifact for modeling business and technical software architectures. Nevertheless, UML notation in and of itself is insufficient for creating meaningful component models. This paper asserts that this difficulty in creating meaningful component models has originated from the use of UML diagrams; furthermore, the paper proposes an alternative flow-based diagramming methodology for software architecture development. The new concept presented in the paper is development of a hierarchy of components on the basis of this flow-based representation. The viability of this idea is demonstrated through a study case of an actual system.
Copyright © 2013 Praise Worthy Prize - All rights reserved.
DOC Enterprise IT Architecture Advisory Group, Information Technology Architecture: What is it, why should you care, and how do you do one? February 10, 2004.
J. Ward, J. Peppard, Strategic Planning for Information Systems, 3rd ed., John Wiley, 2002.
F. D. Raines, Information Technology Architectures, Memoranda 97-16, June 18, 1997, US Government Office of Budget and Management. http://www.whitehouse.gov/omb/memoranda_m97-16
R. Mcilree, The Enterprise Architecture Definition Collection Part III. Blog, http://enterprisearchitect.typepad.com/
Office of the Chief Information Officer, Information Technology Plan FY 2012 to 2016, Smithsonian Institution Information Technology Plan. http://www.google.com.kw/url?sa=t&rct=j&q=&esrc=s&frm=1&source=web&cd=1&cad=rja&ved=0CDYQFjAA&url=http%3A%2F%2Focio.os.doc.gov%2Fs%2Fgroups%2Fpublic%2F%40doc%2F%40os%2F%40ocio%2F%40oitpp%2Fdocuments%2Fcontent%2Fprod01_002345.pdf&ei=_SC3UNKDEs364QT2jYGgBA&usg=AFQjCNHi2QbDo9iODMawyWAmUlv2gH5TdQ&sig2=sac5vtrjc7rztGKScWIo1Q
B. D. Rouhani, S. Kharazmi, Presenting new solution based on Business Architecture for Enterprise Architecture, International Journal of Computer Science Issues, Vol. 9, n. 3, 2012.
O. Barais, A.F. Le Meur, L. Duchien, J. Lawall, Software architecture evolution, in T. Mens, S. Demeyer (editors), Software Evolution, pages 233-262, Springer-Verlag, 2008.
R. N. Taylor, N. Medvidovic, E. M. Dashofy, Software Architecture: Foundations, Theory, and Practice, Wiley, 2009.
M. Shaw, D. Garlan, Software Architecture: Perspectives on an Emerging Discipline, Prentice-Hall, Upper Saddle River, NJ, USA, 1995. ISBN 0-13-182957-2.
Ghazvini, G.A., Sharafi, S.M., Emadi, S., Performance modeling of heterogeneous software architectural styles, (2010) International Review on Computers and Software (IRECOS), 5 (6), pp. 652-659.
M. Goulão, F. B. Abreu, Bridging the gap between Acme and UML 2.0 for CBD, Specification and Verification of Component-Based Systems (SAVCBS'2003), at the ESEC/FSE 2003, Helsinki, Finland, 2003.
W. Jing,Y. Shi, Z. LinLin, N. YouCong, AC2-ADL: Architectural Description of Aspect-Oriented Systems, International Journal of Software Engineering and Its Applications, Vol. 3, n. 1, 2009.
OMG, OMG Unified Modeling Language Specification”, Version 1.5, Object Management Group, March 2003.
S. W. Ambler, UML 2 Component Diagrams. http://www.agilemodeling.com/artifacts/componentDiagram.htm
W.M.P. van der Aalsta, K. M. van Heeb, R. A. van der Toornb, Component-based software architectures: a framework based on inheritance of behaviour, Science of Computer Programming, Vol. 42, n. 2–3, pp. 129–171, 2002.
W. J. Lewis, A Component Framework Model for Information Technology Architecture, The Data Administration Newsletter, TDAN, June 1, 1998. http://www.tdan.com/view-articles/4253
K. van Hee, N. Sidorova, M. Voorhoeve, J. van der Woude, Architecture of Information Systems using the theory of Petri nets, lecture notes. http://www.google.com.kw/url?sa=t&rct=j&q=&esrc=s&frm=1&source=web&cd=3&cad=rja&ved=0CDgQFjAC&url=http%3A%2F%2Fwww.win.tue.nl%2F~sidorova%2Fpm%2Fdictaat-sm1.pdf&ei=d7e2UJDEMYLk4QSHxoCIAQ&usg=AFQjCNEe_NNfEhkLXEfNse2iGrjM8GxYHA&sig2=rueDzPiwjm-uHTdVI4lb5g
G. Booch, J. Rumbaugh, I. Jacobson, The Unified Modeling Language. Addison-Wesley, 1999.
M. Noureddine, From Software Architecture to UML Class Diagrams, Journal Name, Vol. 4. n. 3, pp. 408–413, 2009.
M. Pichler, Diagram: A Component Modeling Example, June 21, 2011. http://applicationarchitecture.wordpress.com/2011/06/21/diagram-a-component-modeling-example/
Al-Fedaghi, S., Annotations of security requirements, (2012) International Review on Computers and Software (IRECOS), 7 (4), pp. 1470-1477.
Al-Fedaghi, S., AlZanaidi, D., Flow-based scenarios in mobile communication systems and networks, (2012) International Review on Computers and Software (IRECOS), 7 (1), pp. 83-91.
S. Al-Fedaghi, Developing Web Applications, International Journal of Software Engineering and Its Applications, Vol. 5, no. 2, pp. 57–68, 2011.
S. Al-Fedaghi, States and Conceptual Modeling of Software Systems, (2009) International Review on Computers and Software (IRECOS), 4 (6), pp. 718–727.
- There are currently no refbacks.
Please send any question about this web site to email@example.com
Copyright © 2005-2022 Praise Worthy Prize