Editing Systems engineering (section)

===Holistic view===
Systems engineering focuses on analyzing and [[Requirements elicitation|eliciting]] customer needs and required functionality early in the [[development cycle]], documenting requirements, then proceeding with design synthesis and system validation while considering the complete problem, the [[system lifecycle]]. This includes fully understanding all of the [[Project stakeholders|stakeholders]] involved. Oliver et al. claim that the systems engineering process can be decomposed into:
* A ''Systems Engineering Technical Process''
* A ''Systems Engineering Management Process''

Within Oliver's model, the goal of the Management Process is to organize the technical effort in the lifecycle, while the Technical Process includes ''assessing available information'', ''defining effectiveness measures'', to ''create a behavior model'', ''create a structure model'', ''perform trade-off analysis'', and ''create sequential build & test plan''.<ref name="Okk">{{Cite book|last1=Oliver|first1=David W.|author2=Timothy P. Kelliher|author3=James G. Keegan Jr.|date=1997|title=Engineering Complex Systems with Models and Objects|url=https://archive.org/details/engineeringcompl00oliv|url-access=limited|publisher=McGraw-Hill|pages=[https://archive.org/details/engineeringcompl00oliv/page/n100 85]–94|isbn=978-0-07-048188-6}}</ref>

Depending on their application, although there are several models that are used in the industry, all of them aim to identify the relation between the various stages mentioned above and incorporate feedback. Examples of such models include the [[Waterfall model]] and the [[VEE model]] (also called the V model).<ref>{{cite web|url=http://www.gmu.edu/departments/seor/insert/robot/robot2.html|title=The SE VEE|publisher=SEOR, George Mason University|access-date=26 May 2007|archive-url=https://web.archive.org/web/20071018220159/http://www.gmu.edu/departments/seor/insert/robot/robot2.html|archive-date=18 October 2007|df=dmy-all}}</ref>