Abstract
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.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
