2. Process Models: Systems Engineering and Others

e.g., Nadler, G. (1967): Work Systems Design. The Ideals Concept.

Boehm, B. and Turner, R. (2004): Balancing Agility and Discipline.

In later sections, we loosen the procedures that have been outlined so far in simplified terms for didactical reasons and show that a certain degree of agility is also possible with the systems engineering process model.

First described and criticized in Royce (1970).

Jensen, Randall W.; Tonies, Charles C. (1979): Software Engineering.

Forsberg, K.; Mooz, H. (1991): The relationship of Systems Engineering to the Project Cycle.

INCOSE (International Council on Systems Engineering) has incorporated the SIMILAR process into its manual to illustrate the systems engineer’s procedure.

Bahill and Gissing (1998).

According to IEEE norm Verification = Is the system built properly? and Validation = Is the right system built?

The terms specification and functional specifications are not used consistently in practice. A distinction could be as follows: a specification (requirement specification, client specification) describes the overall requirements of a “product” by the client/commissioning party or from that viewpoint. The functional specification (technical specifications, detailed technical concept, desired concept, overall system specifications, implementation specifications, or feature specifications) describes in concrete form how the contractor is meeting the requirements; this belongs to the contractor.

According to Wikipedia.

Ribbens, J.A. (2000): Simultaneous Engineering.

Stjepandić Josip; Wognum Nel; Verhagen Wim J.C. (eds.) (2016): Concurrent Engineering in the 21st Century.

Boehm (1988): A Spiral Model of Software Development and Enhancement”.

Beck, K. et al. (2001): Manifesto.

Beck, K.; Andres, C. (2008): Extreme Programming.

KISS = Keep It Simple and Smart (variant: Keep It Simple, Stupid).

Coad, Peter; Lefebvre Eric; De Luca, Jeff (1999): Java Modeling in Color with UML.

Palmer, S.R.; Felsing, J.M. (2002): A Practical Guide to Feature-Driven Development.

Cf: Schwaber, K. (2008): The Enterprise and Scrum. Schwaber, K.; Beedle, M. (2001): Agile Software Development with Scrum. Also, Wikipedia.

Cf: Cockburn, A. (1998): Surviving Object-Oriented Projects.

Cockburn, A. (2004): Crystal Clear

Boehm, B; Turner, R. (2004): Balancing Agility and Discipline.

Known as the situational approach in organization theory.

Stelzmann, E. (2011): Agile Systems Engineering.

The approach conceived in the 1970s and then briefly described was not made public because of a lack of practical experience. The project became dormant because the “godfather” in the client company who had been involved and who had supported this project had been sent overseas on more urgent duties. Only years later did we come across a process methodology designated set-based design, which has certain similarities to the approach described above: “In discussing motor car design – specifically the Toyota Prius – Mary Poppendieck said: I think that the trick is to determine what is, in fact, easy to change later, and what will not be easy to change, and spend some time considering those things that are going to be very expensive to change later. And, of course, the trick is also to keep such things to a minimum – through the use of layers, services, etc.” (Source: http://​silkandspinach.​net/​2007/​01/​114/​agile-set-based-design/​, hit on 4.14.2009). See also: Morgan, J.M.; Liker, J.K. (2006): The Toyota Product Development System.

A further important parallel is the real options theory, which at the time was also unknown to us. The main features are described in Part III, Sect. 2.2.5.

Description according to Wikipedia: Real Options.

Further literature: Amram, M.; Kulatilaka, N. (1999); Real Options. Copeland, T.; Antikarov, V. (2001): Real Options. Dixit, A.K.; Pindyck, R.S. (1994): Investment under Uncertainty.

See the remarks in Sects. 1.3 and 2.2.4 on “Agility of Systems engineering” and “Keeping Options Open as an Approach in Support of Agility”.

Presumably the Greek philosopher Thales of Miletus worked with real options as early as 600 BC. In the springtime he purchased from the local owners at a fixed price the option of using the olive presses at harvest time. The rental price for the presses was essentially dependent on the harvest. A good harvest meant a greater demand for olive presses by the farmers. For unknown reasons, Thales expected a good harvest; his calculation worked out, he became rich, and henceforth was considered a man with visionary powers. (Source: Wikipedia).

Thanks to Armin Schulz, Stefan Wenzel, and Thilo Pfletschinger from 3DSE Munich for their inspiring workshops and specific hints.

Komus, A. and Kuberg, M.: Studie “Status Quo Agile” – wie werden agile Methoden in der Praxis eingesetzt? https://​www.​projektmagazin.​de/​artikel/​studie-status-quo-agile-wie-werden-agile-methoden-der-praxis-eingesetzt_​1101303

Stelzmann, E. (2011): Agile Systems Engineering.

N.N. Hybrid project management: the best of both worlds. https://​www.​microtool.​de/​en/​what-is-hybrid-project-management/​

Kruchten, P. (2011): Agile Teenager. https://​www.​infoq.​com/​articles/​agile-teenage-crisis