Engineering cycle
An editor has nominated this article for deletion. You are welcome to participate in the deletion discussion, which will decide whether or not to retain it. |
The engineering cycle is a framework used in Design Science for Information Systems and Software Engineering.
Design science is a valid research methodology to develop solutions for practical engineering problems.[1] Design science is particularly suitable for wicked problems.[2]
The engineering cycle consists of:
- Problem investigation.
- Treatment design.
- Treatment validation.
- Treatment implementation.
- Implementation evaluation.
The design cycle consists of the first 3 tasks of the engineering cycle: investigation, design, and validation.
The engineering and design cycles do not prescribe a mandatory, rigid sequence of activities. Moreover, they are often applied recursively for sub-problems of the main research objective.
The engineering cycle and the design cycle are often applied in several iterations (hence “cycle”). In such a case, the evaluation may become the investigation part of the next engineering cycle.
History
The engineering cycle model was proposed by Roel Wieringa in his book "Design Science Methodology for Information Systems and Software Engineering".[3]
Validation vs. evaluation in the engineering cycle
In the engineering cycle model, validation is part of the design cycle. It involves checking if the designed artifacts support the initial assumptions. It is executed in a theoretical, “laboratory” environment; such as through discussions and interviews with practitioners and experts. Validation is executed before the implementation in practice.
On the other hand, evaluation is executed after the implementation in practice of the designs. It involves analyzing the behavior, effects, and impact of the designed artifacts in practice, in the field. In our case, this meant implementation and analysis of the designs in actual, industry IT projects.
Stefan Morcov proposes a parallel between these 2 activities and a similar framework, the Technology Readiness Level (TRL) model.[4] The TRL model was proposed by NASA and is currently also widely applied in the European Union's research programs such as Horizon. Thus, validation leads to TRL level 4 - “Technology validated in a laboratory environment”; while evaluation leads to a TRL level 6 - “Technology demonstrated in a relevant environment”.[5][6]
See also
References
- ^ Peffers, Ken; Tuunanen, Tuure; Rothenberger, Marcus A.; Chatterjee, Samir (2007-12-01). "A Design Science Research Methodology for Information Systems Research". Journal of Management Information Systems. 24 (3): 45–77. doi:10.2753/MIS0742-1222240302. ISSN 0742-1222.
- ^ Hevner; March; Park; Ram (2004). "Design Science in Information Systems Research". MIS Quarterly. 28 (1): 75. doi:10.2307/25148625.
- ^ Wieringa, Roel (2014). Design science methodology for information systems and software engineering. Heidelberg. ISBN 978-3-662-43839-8. OCLC 899248827.
{{cite book}}: CS1 maint: location missing publisher (link) - ^ Morcov, Stefan (2021). Managing Positive and Negative Complexity: Design and Validation of an IT Project Complexity Management Framework. Leuven: KU Leuven University.
- ^ Héder, Mihály. "From NASA to EU: the evolution of the TRL scale in Public Sector Innovation" (PDF). The Innovation Journal: The Public Sector Innovation Journal. 22(2).
- ^ European Commission (2021). "Horizon Europe - Work Programme 2021-2022. 13. General Annexes (European Commission Decision C(2021)1940 of 31 March 2021)" (PDF). Europa. Retrieved 26 September 2021.
{{cite web}}: CS1 maint: url-status (link)