Moving From Problem Space to Solution Space

Extracting and elaborating software requirements and transforming them into viable software architecture are still an intricate task. This paper defines a solution architecture which is based on the blurred amalgamation of problem space and solution space. The dependencies between domain constraints, requirements and architecture and their importance are described that are to be considered collectively while evolving from problem space to solution space. This paper proposes a revised version of Twin Peaks Model named Win Peaks Model that reconciles software requirements and architecture in more consistent and adaptable manner. Further the conflict between stakeholders- win-requirements is resolved by proposed Voting methodology that is simple adaptation of win-win requirements negotiation model and QARCC.

Authors:

• Bilal Saeed Raja
• M. Ali Iqbal
• Imran Ihsan

Keywords:

• Functional Requirements
• Non Functional Requirements
• Twin Peaks Model
• QARCC.

References:

[1] Standish Research Paper, Chaos Study, 1995, available on-line at
http://www.standishgroup.com .
[2] B. Paech, A.H. Detroit, D. Kerkow and A. von Knethen, "Functional
requirements, non-functional requirements, and architecture should not
be separated - A position paper". REFSQ' 2002, Essen, Germany,
September 9-10 2002.
[3] Bashar Nuselbeh, "Weaving Together Requirements and Architectures",
in proceedings of IEEE Computer, 34, 3 (March 2001), pp. 115-119.
[4] Paul Gr├╝nbacher, Alexander Egyed, and Nenad Medvidovic.
"Reconciling Software Requirements and Architectures: The CBSP
Approach." in Proceedings of the Fifth IEEE International Symposium
on Requirement Engineering, 2001.
[5] Boehm, Barry "Conflict Analysis and Negotiation Aids for Cost-Quality
Requirements", Center for Software Engineering and Computer Science
Department, University of Southern California, 1999.
[6] Hall, J.G.; Jackson, M.; Laney, R.C.; Nuseibeh, B.; Rapanotti, L.
"Relating software requirements and architectures using problem
frames". Proceedings of the IEEE Joint International Requirements
Engineering Conference (RE'02), Essen, Germany, 9-13 September,
2002, Pages: 137- 144.
[7] Boehm, B. and Egyed, A., "Software Requirements Negotiation: Some
Lessons Learned", in proceedings of the 20th International Conference
on Software Engineering, April 1998.
[8] Alexander Egyed, Barry Boehm, "Analysis of System Requirements
Negotiation Behavior Patterns". Proceedings of 7th Annual
International Symposium on Systems Engineering, 1997.
[9] Robert Glass, "Software Runaways: Lessons Learned from Massive
Project Failure" published in the magazine Computerworld, 1989.
[10] Steve McConnell, "Software Project Survival Guide" a book published
by Microsoft Press, 1998.
[11] Awais Rashid , Ana Moreira , Jo─üo Ara├║jo, "Modularisation and
composition of aspectual requirements", Proceedings of the 2nd
international conference on Aspect-oriented software development, p.11-
20, March 17-21, 2003, Boston, Massachusetts.
[12] Hall J.G., Rapanotti, L., "A reference model for requirements
engineering", in IEEE Proceedings of International Requirements
Engineering Conference (RE'03), USA, September 2003.