Editing Software architecture (section)

=== Requirements engineering ===
{{main|Requirements engineering}}
[[Requirements engineering]] and software architecture can be seen as complementary approaches: while software architecture targets the '[[solution space]]' or the 'how', requirements engineering addresses the '[[Computational problem|problem space]]' or the 'what'.<ref name="shekaran94">{{Cite book|author1=C. Shekaran |pages=239–245 |author2=D. Garlan |author3=M. Jackson |author4=N.R. Mead |author5=C. Potts |author6=H.B. Reubenstein |title=Proceedings of IEEE International Conference on Requirements Engineering |chapter=The role of software architecture in requirements engineering |year=1994|doi=10.1109/ICRE.1994.292379 |isbn=978-0-8186-5480-0 |s2cid=3129363 }}</ref> Requirements engineering entails the [[Requirements elicitation|elicitation]], [[Requirements analysis|negotiation]], [[Software Requirements Specification|specification]], [[Data validation|validation]], [[Requirements traceability|documentation]], and [[Requirements management|management]] of [[requirement]]s. Both requirements engineering and software architecture revolve around [[Stakeholder (corporate)|stakeholder]] concerns, needs, and wishes.

There is considerable overlap between requirements engineering and software architecture, as evidenced for example by a study into five industrial software architecture methods that concludes that ''"the inputs (goals, constraints, etc.) are usually ill-defined, and only get discovered or better understood as the architecture starts to emerge"'' and that while ''"most architectural concerns are expressed as requirements on the system, they can also include mandated design decisions"''.<ref name="hofmeister07">{{cite journal|author1=Christine Hofmeister |author2=Philippe Kruchten |author3=Robert L. Nord |author4=Henk Obbink |author5=Alexander Ran |author6=Pierre America |title=A general model of software architecture design derived from five industrial approaches|year=2007|doi=10.1016/j.jss.2006.05.024|journal=Journal of Systems and Software |volume=80 |issue=1  |pages=106–126}}</ref> In short, required behavior impacts solution architecture, which in turn may introduce new requirements.<ref name="boer09">{{Cite journal|author=Remco C. de Boer, [[Hans van Vliet]]|title=On the similarity between requirements and architecture|journal=Journal of Systems and Software|volume=82|issue=3|pages=544–550|year=2009|doi=10.1016/j.jss.2008.11.185|citeseerx=10.1.1.415.6023}}</ref> Approaches such as the Twin Peaks model<ref name="twinpeaks">{{Cite journal|author=Bashar Nuseibeh|title=Weaving together requirements and architectures|journal=Computer|volume=34|issue=3|pages=115–119|year=2001|doi=10.1109/2.910904|url=http://oro.open.ac.uk/2213/1/00910904.pdf |archive-url=https://web.archive.org/web/20120907054241/http://oro.open.ac.uk/2213/1/00910904.pdf |archive-date=2012-09-07 |url-status=live}}</ref> aim to exploit the [[Synergy|synergistic]] relation between requirements and architecture.