원문정보
초록
영어
Software architecture is the blueprint for a software system and should provide consistent guidelines for design, implementation, and maintenance throughout the entire lifecycle of the system. Components, interactions between the components, well-formed structure, reasons, and various perspectives reflecting various stakeholders’ concerns changing through the phases of software lifecycle are the key elements of software architecture. The architect identifies and engages the stakeholders, understands and captures stakeholder’s concerns including those regarding life cycle, and lets the concerns reflected in the architecture. To do so, architect should take into consideration various contextual elements regarding the system too. We make an extended list of the elements, especially those of business application software architecture, that the architect should take into consideration and construct a model of the relationships between the elements.
목차
1. Introduction
2. Literature Survey
2.1 Definitions of Software Architecture
2.2. Architectural Context : Rozanski and Woods [2012]
2.3 Project and Program Management : PMI
3. Contextual Model of Application Software Architecture
4. Conflicts between Long-Term Interests and Short-Term Interests
5. Conclusions
References