Software requirements: objects, functions, and states
Software requirements: objects, functions, and states
A stakeholder win–win approach to software engineering education
Annals of Software Engineering - Special issue on software engineering education
Extreme programming explained: embrace change
Extreme programming explained: embrace change
The Scrum Software Development Process for Small Teams
IEEE Software
The Inmates are Running the Asylum
Software-Ergonomie '99, Design von Informationswelten, Gemeinsame Fachtagung des German Chapter of the ACM, der Gesellschaft für Informatik (GI) und der SAP AG
Agile Modeling: A Brief Overview
Workshop of the pUML-Group held together with the «UML»2001 on Practical UML-Based Rigorous Development Methods - Countering or Integrating the eXtremists
Software Architecture in Practice
Software Architecture in Practice
Software Architecture as a Set of Architectural Design Decisions
WICSA '05 Proceedings of the 5th Working IEEE/IFIP Conference on Software Architecture
Mastering the Requirements Process (2nd Edition)
Mastering the Requirements Process (2nd Edition)
Conceptual Modeling: Foundations and Applications
INTERACT '09 Proceedings of the 12th IFIP TC 13 International Conference on Human-Computer Interaction: Part II
Agility and Architecture: Can They Coexist?
IEEE Software
Agile Architecture Interactions
IEEE Software
Communicating about users in ICTD: leveraging HCI personas
Proceedings of the Fifth International Conference on Information and Communication Technologies and Development
Evaluation and Measurement of Software Process Improvement—A Systematic Literature Review
IEEE Transactions on Software Engineering
Proceedings of the 34th International Conference on Software Engineering
Personas - User Focused Design
Personas - User Focused Design
How do software architects consider non-functional requirements: An exploratory study
RE '12 Proceedings of the 2012 IEEE 20th International Requirements Engineering Conference (RE)
Hi-index | 0.00 |
[Context and motivation] Architecturally significant requirements (ASRs) drive and constrain many aspects of the architecture. It is therefore beneficial to elicit and analyze these requirements in early phases of a project so that they can be taken into consideration during the architectural design of the system. Unfortunately failure to invest upfront effort in exploring stakeholders quality concerns, can lead to the need for significant refactoring efforts to accommodate emerging requirements. This problem is particularly evident in agile projects which are inherently incremental. [Question/Problem] Existing techniques for early discovery of ASRs, such as Win-Win and i*, are typically rejected by agile development teams as being somewhat heavy-weight. A light-weight approach is therefore needed to help developers identify and explore critical architectural concerns early in the project. [Principal ideas/results] In this paper we present the use of Architecturally-Savvy Personas (ASP-Lite). The personas are used to emerge and analyze stakeholders' quality concerns and to drive and validate the architectural design. ASP-Lite emerged from our experiences working with the requirements and architectural design of the TraceLab project. The approach proved effective for discovering, analyzing, and managing architecturally significant requirements, and then for designing a high-level architectural solution which was designed to satisfy requirements despite significant interdependencies and tradeoffs. [Contributions] This paper presents the ASP-Lite approach and describes its support for architectural design in the US$2 Million TraceLab project.