Abstract
The importance of non-functional requirements for computer systems is increasing. Satisfying these requirements require special attention to the software architecture, once an unsuitable architecture introduces greater complexity in addition to the intrinsic complexity of the system. Some studies have shown that, despite requirements engineering and software architecture activities act on different aspects of development, they must be performed iteratively and intertwined to produce satisfactory software systems. The STREAM process presents a systematic approach to reduce the gap between requirements and architecture development, emphasizing the functional requirements, being the non-functional ones used in an ad hoc way. However, nonfunctional requirements typically influence the system as a whole. This paper presents a process to improve STREAM in making the choice of architectural patterns from non-functional requirements, in order to guide the refinement of an architectural solution.
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.
