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