Premium
4.4.3 Using A System Object Methodology in Software Intensive Systems
Author(s) -
Wray Richard B.
Publication year - 2000
Publication title -
incose international symposium
Language(s) - English
Resource type - Journals
ISSN - 2334-5837
DOI - 10.1002/j.2334-5837.2000.tb00415.x
Subject(s) - computer science , software system , software engineering , object oriented design , systems engineering , software development , object oriented programming , systems development life cycle , object (grammar) , context (archaeology) , unified modeling language , software development process , software , programming language , artificial intelligence , engineering , paleontology , biology
Systems Engineering typically relies upon functionally oriented system definition. However, for software intensive systems that rely upon object‐oriented development, functionally oriented system definition provides insufficient input to software development. Development of object‐oriented software can be improved by providing input to the software process using an object‐oriented system methodology that merges precepts from the Fusion Methodology and the Unified Modeling Language. A hybrid system object methodology must establish at least the user/system context and the models of the key elements of a system design (including the system object model, life cycle model and operations model). Relationships between these models in the methodology include definition of the system boundary, classes and attributes of objects, events and system operations. This paper summarizes underlying object modeling precepts important to systems engineering and describes this hybrid system object methodology.