A contribution to the scientific foundations of systems engineering: Solution spaces and requirements

Abstract

Some researchers have suggested that scientific foundations expressed in a mathematical form are needed to thrust the success of systems engineering as a discipline on its own merit. In order to contribute the development of such systems science, this paper investigates from a foundational standpoint the relationships between stakeholder needs, system requirements, and sets of systems. Various theorems and corollaries are proposed and mathematically proven. The theoretical elements are presented as a foundation for the development of a science for requirements engineering. The proposed foundations are finally tested to mathematically describe, in a rigorous and precise manner, qualities of good requirements, which are otherwise traditionally defined using vague narrative. By showcasing practical examples of the theoretical aspects, the paper is intended to serve as a bridge between practitioners and theorists.

Keywords

Systems science / systems theory / requirements engineering / mathematical formulation / requirements qualities / formal concepts

References

[1] Abadi C. D., Bahill T.. Separating product and process requirements, 2002

[2] Abadi C. D., Bahill T.. The difficulty in distinguishing product from process. Systems Engineering, 2003, 6: 106-115.

[3] Adams K. M., Hester P. T., Bradley J. M., Meyers T. J., Keating C. B.. Systems theory as a foundation for understanding systems. Systems Engineering, 2014, 17: 112-123.

[4] Alvarez J., Castell N., Slavkova C.. Combining knowledge and metrics to control software quality factors, 1996.

[5] Bahill A. T., Dean F. F.. What is systems engineering? A consensus of senior systems engineers, 1996

[6] Bernard Y.. Requirements management within a full model-based engineering approach. Systems Engineering, 2012, 15(2): 119-139.

[7] Boehm B., Valerdi R., Honour E.. The ROI of systems engineering: some quantitative results for software-intensive systems. Systems Engineering, 2008, 11(3): 221-234.

[8] Bokhari M. U., Siddiqui S. T.. Metrics for requirements engineering and auotmated requirements tools, 2011

[9] Boulding K. E.. General systems theory: the skeleton of science. Management Science, 1956, 2: 197-208.

[10] Buede D. M.. The Engineering Design of Systems: Models and Methods, 2009.

[11] Caddy I. N., Helou M. M.. Supply chains and their management: application of general systems theory. Journal of Retailing and Consumer Services, 2007, 14(5): 319-327.

[12] Carson R. S.. A set theory model for anomaly handling in system requirements analysis, 1995.

[13] Carson R. S.. Designing for failure: anomaly identification and treatment in system requirements analysis, 1996

[14] Carson R. S.. Requirement completeness: a deterministic approach, 1998

[15] Carson R. S., Aslaksen E., Gonzales R.. Requirements completeness, 2004

[16] Carson R. S., Shell T.. Requirements completeness: absolute or relative?. Systems Engineering, 2001, 4: 230-231.

[17] Chapman W. L., Rozuenblit J., Bahill A. T.. System design is a NP-complete problem. Systems Engineering, 2001, 4: 222-229.

[18] Cherns A.. The principles of sociotechnical design. Human Relations, 1976, 29(8): 783-792.

[19] Cherns A.. Principles of sociotechnical design revisited. Human Relations, 1987, 40(3): 153.

[20] Fertig J., Zapata R.. A mathematical formulation for systems synthesis, 1977

[21] Ford T. C., Colombi J. M., Jacques D. R., Graham S. R.. On the application of classification concepts to systems engineering design and evaluation. Systems Engineering, 2009, 12(2): 141-154.

[22] Friedman G.. Constraint Theory: Multidimensional Mathematical Model Management, 2005.

[23] Goguen J.. Tossing algebraic flowers down the great divide, 1999 93-129.

[24] Gunter C. A., Gunter E. L., Jackson M., Zave P.. A reference model for requirements and specifications. IEEE Software, 2000, 17(3): 37-43.

[25] Hall A. B.. Metasystems Methodology: A New Synthesis and Unification, 1989

[26] Honour E.. Understanding the value of systems engineering, 2004

[27] Hood C., Widermann S., Fichtinger S., Pautz U.. Requirements Management, the Interfaces between Requirements Development and All Other Systems Engineering Processes, 2008

[28] Hooks I. F.. Managing requirements, 2001

[29] IEEE. Institute of Electrical and Electronics Engineers, Recommended practice for software requiremetns specification, 1993

[30] INCOSE. (2011). INCOSE Systems Engineering Handbook, v.3.2.2.

[31] INCOSE. (2012). Guide for Writing Requirements: The International Council of Systems Engineering.

[32] Jureta I. J., Mylopoulos J., Faulkner S.. Revisiting the core ontology and problem in requirements engineering, 2008.

[33] Kar P., Bailey M.. Requirements management working group: characteristics of good requirements. INCOSE International Symposium, 1996, 6(1): 1225-1233.

[34] Kasser J. E.. Applying Total Quality Management to Systems Engineering, 1995

[35] Kasser J. E.. The First Requirements Elucidator Demonstration (FRED) tool. Systems Engineering, 2004, 7: 243-256.

[36] Katasonov A., Sakkinen M.. Requirements quality control: a unifying framework. Requirements Engineering, 2006, 11: 42-57.

[37] Kennet R. S.. Software specification metrics: a quantitative approach to assess the quality of documents, 1996

[38] Klir G.. An Approach to General Systems Theory, 1969

[39] Klir G.. Trends in General Systems Theory, 1972.

[40] Klir G.. A review of model-based systems engineering. International Journal of General Systems, 1996, 25(2): 179-180.

[41] Korn J.. Problem of identity of systems engineering, 1997

[42] Larsen R. F., Buede D. M.. Theoretical framework for the continuous early validation (CEaVa) method. Systems Engineering, 2002, 5: 223-241.

[43] Lee R. E., Hooks I., Barker B. G.. Larson W. J., Kirkpatrick D., Sellers J. J., Thomas L. D., Verma D.. Engineering and managing system requirements. Applied Space Systems Engineering, 2009 95-139.

[44] Mattson C. A., Messac A.. Pareto frontier based concept selection under uncertainty, with visualization. Optimization and Engineering, 2006, 6: 85-111.

[45] Mesarovic M. D.. General systems theory and its mathematical foundation, 1967

[46] Micouin P.. Toward a property based requirements theory: system requirements structured as a semilattice. Systems Engineering, 2008, 11(3): 235-245.

[47] Mulej M., Protocan V., Zenko Z., Kajzer S., Ursic D., Knez-Riedl J., Ovsenik J.. How to restore Bertalanffian systems thinking. Kybernetes, 2004, 33(1): 48-61.

[48] Nakamori Y.. Systems methodology and mathematical models for knowledge management. Journal of Systems Science and Systems Engineering, 2003, 12(1): 49-72.

[49] Parnas D. L., Madey J.. Functional documents for computer systems. Science of Computer Programming, 1995, 25(1): 41-61.

[50] Rechtin E.. System Architecting: Creating & Building Complex Systems, 1991

[51] Sahraoui A.-E.-K., Buede D., Sage A.. Systems engineering research. Journal of Systems Science and Systems Engineering, 2008, 17(3): 319-333.

[52] Salado A., Nilchiani R.. A categorization model of requirements based on Max-Neef’s model of human needs. Systems Engineering, 2014, 17: 348-360.

[53] Salado A., Nilchiani R.. The concept of order of conflict in requirements engineering. IEEE Systems Journal, 2016, 10: 25-35.

[54] Sanchez J.. Application of statistical processes on a set theory model for anomaly handling in system requirements analysis, 1996.

[55] Sheard S. A., Mostashari A.. Principles of complex systems for systems engineering. Systems Engineering, 2009, 12: 295-311.

[56] Shell T.. System function implementation and behavioral modeling: a systems theoretic approach. Systems Engineering, 2001, 4: 58-75.

[57] Sherwin J.. An approach towards holism in science and engineering. Journal of Systems Science and Systems Engineering, 2010, 19(3): 285-305.

[58] Simpson M. J., Simpson J. J.. Formal systems concepts, 2006

[59] Simpson M. J., Simpson J. J.. Formal, theoretical aspects of systems engineering - Comments of "Principles of Complex Systems for Systems Engineering" [Syst Eng 12 (2009), 295-311]. Systems Engineering, 2010, 13: 204-207.

[60] Sipilä P., Perttula M.. Influence of task information on design idea generation performance, 2006

[61] Spanoudakis G., Finkelstein A., Till D.. Overlaps in requirements engineering. Automated Software Engineering, 1999, 6: 171-198.

[62] Takahara Y., Liu Y., Yano Y.. A formal systems approach to solver design-hill climbing method with push down stack. Journal of Systems Science and Systems Engineering, 2003, 12(2): 138-158.

[63] Thompson K. R.. "General system" defined for predictive technologies of A-GSBT (Axiomatic-General Systems Behavioral Theory). Scientific Inquiry, 2006, 7: 1-11.

[64] Vajna D., Kittel K., Bercsey T.. The autogenetic design theory, product development as an analogy to biological evolution, 2011

[65] Van Lamsweerde A.. Goal-oriented requirements engineering: a guided tour, 2001

[66] von Bertalanffy L.. General Systems Theory - Foundations, Development, Applications, 1969

[67] Warfield J. N.. An Assault on Complexity (Vol. Monograph 3), 1973

[68] Warfield J. N., Hill J. D.. A unified Systems Engineering Concept (Vol. Monograph 1), 1972

[69] Weinberg G. M.. An Introduction to General Systems Thinking, 1975

[70] Williams D. W., Hall T., Kennedy M.. A framework for improving requirements engineering process management. Software Quality Journal, 1999, 8: 133-147.

[71] Wolff K. E.. Towards a conceptual system theory, 2000

[72] Wymore A. W.. A Mathematical Theory of Systems Engineering: The Elements, 1977

[73] Wymore A. W.. Model-based systems engineering. Proceedings of the Spie, 1993, 9150(1): 101-111.

[74] Yan X. T., Sawada H.. A framework for supporting multidisciplinary engineering design exploration and life-cycle design using underconstrained problem solving. Artificial Intelligence for Engineering Design, Analysis and Manufacturing, 2006, 20: 329-350.

[75] Zave P., Jackson M.. Four dark corners of requirements engineering. ACM Transactions on Software Engineering and Methodology (TOSEM), 1997, 6(1): 1-30.