![]() This supports the composite structure visualizations that systems engineers seem to prefer, but makes it more difficult to produce node and link graphs, and to perform what-if-analysis along the relationships. Rather than modeling relationships as associations, properties and tagged values are applied.without also stating how this need is met, who provides the information, as the source of the flow. With a flow-oriented approach to information modeling, you cannot model the information needs of organizations, applications, activities etc. #ENTERPRISE ARCHITECTURE SOFTWARE CATEGORIES SOFTWARE#Rather than directly stating that a software application implements a service, you have to state which physical capability configuration provides the service, which hardware artefacts it contains, and finally the software is only included as hosted on the hardware artefacts.Rather that directly stating that a project contributes to a goal, MODAF forces you to add intermediate objects stating when the contribution is delivered (milestone) and what the contribution consists of (capability configuration).For instance, the MODAF and NAF metamodels require you to put in a lot of details that you may not care about on the business architecture level. On the other hand, the more technical frameworks may not offer the high level views that communicate with business people and system users. An IS or management consulting approach will need to be linked with other techniques that adequately cover the technical details of software and systems design. Organizations that are taking up enterprise architecture should be aware of this fragmentation, and make sure that the frameworks and techniques they select fit their needs. In most business sectors, hardware is a standard commodity that IS need not focus too much attention on, while in military systems the hardware is cutting edge, subject to demanding requirements, and a core concern for systems engineering. When IS is concerned with requirements and portfolio management, some systems engineers see these domains as separate from EA. For instance, while the technical disciplines see UML as a suitable modeling framework, few IS and management consultants agree. This wide range of perspectives has lead to confusion about purpose, target audience, terminology, and suitable techniques. Systems-of-systems thinking led them to extend their reach beyond technology and into the enterprise realm. After software engineering established object oriented modelling of the internals of software systems, systems engineering adapted these techniques to hardware and software co-design. Later, information systems people applied similar techniques for aligning the IT with the business it supports, and for IT management in general. Enterprise modelling was first applied to analyse industrial operations, extending IDEF and other process modeling notations. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |