Abstract
problem statement: the main problem in building any system is that many decisions appear through its design. These decisions are affected mainly by the goals that the architect wants to achieve. These goals shape the architectural design of a system; the architect needs to know the best decisions to use them through building the design of a system. Approach: Design fragments used to solve the problem, design decisions controlled by fragments. Fragments themselves need to be controlled to mange the quality that results from them so quality management activities deal in controlling the fragments. Results: Using design fragments helped the architect to choose the most important design decisions to achieve high quality. Conclusion: Goals are affected mainly with quality attributes. Choosing the right decisions made building the good quality software.
Highlights
Architectural design plays a very important role in a software life cycle
By defining the abstraction of the system, architectural design describes certain properties of the system while hiding other properties; this representation provides the guidelines for building the overall system, permits the designers to satisfy the requirement of the customer and suggests a plan for the software construction
It communicates between all stakeholders which are interested in the development of software
Summary
Architectural design ( called software architecture) plays a very important role in a software life cycle. This study presents how architectural design decisions affect on achieving goal that software is built upon. This is done through defining a design fragment concept and the role of quality control on these fragments. QAW is a method that connects system stakeholders early in life cycle of the software to discover the driving quality attributes of the software and clarify system requirements before the software architecture has been created (Barbacci et al, 2002) This gets qualities that are mapped to business goals scenarios for the qualities which are built by stakeholders according to the main goals. Sometimes a design fragment composition concept arises; this is done when a design fragment needs to change another design fragment
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Free) 
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 call
