An alternative systems engineering paradigm, MBSE on steroids which also dissolves the perennial problem of poor requirements
Join us in the Oasis Café on Thursdays at 7 pm New York local time via Zoom Meeting ID: 873 4055 1993 Passcode: 557756 (See session recordings)
Recent presentations
Using Object-oriented Systems Engineering to make a cup of coffee
This presentation provides a case study example of the System Development Process (SDP) without requirements. It shows how there are fewer opportunities for errors as compared to using requirements. The case study is simple yet complex enough to not only demonstrate some benefits of Object-oriented Systems Engineering OOSE (e.g., use of inheritance and templates to minimize the probability of realizing the wrong system), it also shows the tight coupling between systems engineering and project management. The presentation also points out why systems engineers should never use +/- when discussing tolerances, but use ranges instead and concludes with some lessons learned.
Let’s just stop writing requirements, we can’t write them properly anyhow
The perennial problem of poor requirements has not been solved in more than 50 years. The presentation discusses the problem, and summarizes the application of systems thinking to the problem. The presentation then proposes to dissolve the problem using an out-of-the-box requirements-free solution to the problem; Object-oriented Systems Engineering (OOSE), (MBSE on steroids) which integrates systems engineering and project management, provides several examples of Computer Enhanced Systems Engineering (CESE) and Project Management tools system development using the alternative paradigm, shows how the early states of the OOSE system development process follow the problem-solving process and concludes with the benefits of OOSE which include lower costs and shorter development times – all requirements free!
Request copies of presentation slides in pdf format
Earlier publications from, and pertaining to, the research
- Kasser, J. E., Getting the right requirements right, proceedings of the 22nd Annual International Symposium of the INCOSE, Rome, Italy, 2012.
- Tran X.L., Kasser J.E., Towards Improving the Recognition and Correction of Poorly Written Requirements, proceedings of the Systems Engineering Test and Evaluation (SETE) Conference, Brisbane, 2005.
- Kasser J.E., Researching the Properties of Object-Oriented Requirements, proceedings of the Conference on Systems Engineering Research, Los Angeles, 2004.
- Kasser J.E., Object-Oriented Requirements Engineering and Management, proceedings of the SETE 2003, Canberra, Australia, 2003.
- Lentz V.A., Lerner B., Cost Effective Systems Engineering for Companies that Build-on-Speculation, International Symposium of the INCOSE 2003.
- Kasser J.E. Does Object-Oriented System Engineering Eliminate the Need for Requirements?, proceedings of the 12th International Symposium of the INCOSE, Las Vegas, NV, 2002.
- Lentz V.A., Lerner B., Functional Analysis for Existing Products: a Detailed Procedure, proceedings of the 12th International Symposium of the INCOSE, Las Vegas, NV, 2002.
- Cook S. C., Kasser J.E., Asenstorfer J., A Frame-Based Approach to Requirements Engineering, proceedings of the 11th International Symposium of the INCOSE, Melbourne, Australia, 2001.
- Adifon L., Lentz V.A., Lerner B., Daryl J. Marvin D.L., Validating a Commercial Product Architecture, proceedings of the 11th International Symposium of the INCOSE, Melbourne, Australia, 2001.
- Kasser J.E., A Framework for Requirements Engineering in a Digital Integrated Environment (FREDIE), proceedings of the SETE 2000, Brisbane, Australia, 2000.
- Kasser J.E., Yes Virginia, You Can Build a Defect Free System, on Schedule and Within Budget, proceedings of the INCOSE 7th International Symposium, Los Angeles, CA, 1997.
