Premium
4.1.1 Benefits in Using Object‐Oriented Methodology For Architecture Modeling
Author(s) -
Osvalds Gundars
Publication year - 2004
Publication title -
incose international symposium
Language(s) - English
Resource type - Journals
ISSN - 2334-5837
DOI - 10.1002/j.2334-5837.2004.tb00526.x
Subject(s) - computer science , software engineering , object oriented design , documentation , object oriented programming , systems engineering , representation (politics) , object (grammar) , engineering , programming language , artificial intelligence , politics , law , political science
Currently enterprise and systems architecture models being developed by Systems Engineers to describe the stakeholders' problem often use the Structured/Functional Methodology while software designers usually use the Object‐Oriented Methodology. Thus, architectures represented with Functional Representation may not be fully implemented, as designed, by the software developers who use Object‐Oriented Representation. The systems engineer should consider the benefits in utilizing an Object‐Oriented Methodology in developing the architecture design. A benefit, in the use of the same representation, is the ability to create a concordant set of engineering products that are traceable from the design to the system implementation. Another benefit is that the Object‐Oriented Methodology is that it closely matches the stakeholders' view of the world which consists of objects that perform actions and utilize information. Therefore the use of the Object‐Oriented Methodology in the design and documentation of enterprise and system architectures provides reusable design artifacts for the software developers.