EVALUATION OF CAPTURING ARCHITECTURALLY SIGNIFICANT REQUIREMENTS METHODS
DOI:
https://doi.org/10.22159/ajpcr.2017.v10s1.19589Keywords:
Architecturally Significant Requirement method, Use Case DiagramAbstract
Every software development organization strives for customer satisfaction. It is universally accepted that the success of software development lies in the clear understanding of the client requirements. During requirement elicitation and analysis stage, the system analyst identifies the functional and non-functional requirements from the customer. Security, usability, reliability, performance, scalability and supportability are the significant quality attributes of a software system. These quality attributes are also referred as non-functional requirements. Only a few functional and quality attributes requirement help to identify and shape the software architecture. A software system's architecture is the set of prime design decisions made about the system. If the requirement influences the architectural design decision then, it is referred as Architecturally Significant Requirement (ASR). Identifying and specifying all the possible ASR are important tasks in the requirement elicitation and analysis stage.In this research, general problems that are faced while capturing and specifying ASR in requirement elicitation and analysis is studied. Among the different requirement elicitation techniques, use case diagram has been identified and enhanced to solve the problem of capturing and specifying ASR during the requirement elicitation and analysis phase
Â
Downloads
References
Alan, M, Davis 1993, ‘Software Requirements: Analysis and Specification’, Prentice Hall Press, Upper Saddle River, NJ, USA.
Alistair Suteliffe& Pete Sayer 2013, ‘Requirements Elicitation: Towards the Unknown Unknowns’, 21stRequirements Engineering Conference (RE), IEEE International.
Andrea Herrmann & Barbara Paech 2009, ‘Practical challenges of requirements prioritization based on risk estimation’, Empirical Software Engineering, vol. 14, pp. 644-684.
Antony, J, Lattanze 2009, ‘Architecting Software Intensive Systems’, CRC press.
Armour, F & Miller, G 2000, ‘Advanced Use Case Modeling:Software Systems.’ , Addison-Wesley.
Base, L, Clements, P &Kazman, R 2003, ‘Software Architecture in Practice’, Addison-Wesley.
Barbacci, M, Ellison, R, Lattanze, A, Staffor, J, Weinstock, C, Wodod 2003, ‘Quality Attribute Workshops (QAWs)’, Third Edition, Pittsburgh, PA: Software Engineering Institute, Carnegie Mellor University.
BenteAnda, Dag Sjeberg&Magne Jorgensen 2001, ‘Quality and Understandability of Use Case Models’, Proceedings of the 15th European Conference on Object-Oriented Programming, pp. 402-428.
Bill Davey & Chris Cope 2008, ‘Requirements Elicitation- What’s Missing?’, Issues in Information Science and Information Technology, vol. 5.
Charles Babers 2003, ‘Architecture Development Made Simple’, CJC Publishing.
Christian, FJ, Lange, Michel, RV, Chaudron& Johan Muskens 2006, ‘In Practice: UML Software Architecture and Design Description’, IEEE SOFTWARE, pp. 40-46.
Cockburn, A 2000, ‘Writing Effective Use cases’. Boston, MA, Addision- Wesley.
Daryl Kulak &Eamonn Guiney 2012, ‘Use Cases: Requirements in Context’, Addison-Wesley.
Ellen Gottesdiener 2008, ‘Good Practices for Developing User Requirements’, CrossTalkThe Journal of Defense Software Engineering.
Grady Booch, James Rumbaugh & Ivar Jacobson 2001, ‘The Unified Modeling Language User Guide’, Addition Wesely.
GuttormSindre, Andreas, L, Opdahal 2005, ‘Eliciting Security requirements with misuse cases’ Requirements Engineering, vol. 10, pp. 34-44.
Jane Coughlam& Robert, D, Macredie 2002, ‘Effective Communication in Requirements Elicitation: A Comparison of Methodologies’, Requirements Engineering, vol. 7, pp. 47-60.
Jane Clelan-Huang, RaffaellaSettimi, Suchang Zou & Peter Solc 2007, ‘Automated classification of non-functional requirements’, Requirements Engineering.
Ian Somerville 2011, ‘Software Engineering’, Pearson Education India.
Kurt Bittner & Ian Spence 2002, ‘Use Case Modeling’, Addison- Wesley.
Len Bass, John Bergey, Paul Clements, Paulo Merson, IpekOzkaya&RaghvinderSangwan 2006, ‘A comparison of Requirements Specification Methods from a Software Architecture Perspective’, Technical Report, Carnegie Mellon Software Engineering Institute, Pittsburgh, www.sei.cmu.edu/reports/06tr013.pdf.
Lianping Chen, Muhammad Ali Babar & Bashar Nuseibeh 2013, ‘Characterizing Architecturally Significant Requirements’, IEEE Software.
Liming Zhu& Ian Gorton 2007, ‘UML Profiles for Design Decisions and Non-Functional Requirements’, Sharing and Reusing Architectural Knowledge – Architecture, Rationale, and Design Intent, 2007. SHARK/ADI '07,IEEE..
RaghvinderSangwan, Colin Neil, Matthew Bass &Zakaria El Houda 2008, ‘Integrating a software architecture-centric method into object-oriented analysis and design’, The Journal of Systems and Software, vol.81, pp. 727-746.
Remco, C, de Boer & Hans van Vliet 2009, ‘ On the similarity between requirements and architecture’, The Journal of Systems and Software, vol. 82, pp. 544-550.
Richard, N, Taylor, NenadMedvidovi& Eric, M, Dashofy 2010, ‘Software Architecture Foundations, Theory, and Practice’, John Wiley & Sons, Inc.
Published
How to Cite
Issue
Section
The publication is licensed under CC By and is open access. Copyright is with author and allowed to retain publishing rights without restrictions.
