Scribd
Upload
37 views

Information Level EA Artifacts

The document discusses the information level and artifacts in enterprise architecture (EA). The information level describes the flow and relationships of EA components through requirements, principles and models to guide current and future views. Key artifacts include knowledge management plans, data models, activity matrices and data dictionaries. Traditional modeling uses entity relationship diagrams and data flow diagrams, while object-oriented modeling represents real-world situations as objects with attributes and relationships. Diagrams like use case diagrams, class diagrams and state transition diagrams describe system behaviors and object lifecycles.

Uploaded by

Don Xiao
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
37 views

Information Level EA Artifacts

The document discusses the information level and artifacts in enterprise architecture (EA). The information level describes the flow and relationships of EA components through requirements, principles and models to guide current and future views. Key artifacts include knowledge management plans, data models, activity matrices and data dictionaries. Traditional modeling uses entity relationship diagrams and data flow diagrams, while object-oriented modeling represents real-world situations as objects with attributes and relationships. Diagrams like use case diagrams, class diagrams and state transition diagrams describe system behaviors and object lifecycles.

Uploaded by

Don Xiao
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 32

Information Level

and EA Artifacts
Information Level
(Current View)
Part of the EA process that describes flow and
relationship of EA components and is represented
through a set of requirements, principles and
models.
Information Level
(Current View)
Serves as guidance for current view and future
view to flexibly share and exchange information
assets to achieve effective enterprise changes.
Information Level – Current View

Artifacts

 Knowledge Management Plan (D-1)

 Information Exchange Matrix (D-2)

 Object State-Transition Diagram (D-3)

 Object Event Sequence Diagram (D-4)

 Logical Data Model (D-5)


Information Level – Current View

Artifacts (cont’d)

 Physical Data Model (D-6)

 Activity/Entity (CRUD) Matrix (D-7)

 Data Dictionary/Object Library (D-8)


Information Level – Current View

Modeling Techniques

 Traditional Modeling
o Entity Relationship Diagram/Model
o Data Flow Diagram

 Object-Oriented Modeling
o Class/Object Model
Traditional Modeling

Approach to information systems development


that is based on the modeling technique

called Entity-Relationship Diagramming (ERD)


Traditional Modeling

ER
Diagram
Traditional Modeling

Data Flow
Diagram
Object-Oriented Modeling

Based upon real world situations.

These situations are represented as objects, with


different attributes.
Object-Oriented Modeling
Object-Oriented Modeling

POKEMON
CLASS

Mom/Dad Mom/Dad

Son - Pikachu
Object-Oriented Modeling

Characteristics

 Polymorphism

 Inheritance

 Encapsulation
Object Defining Characteristics
Object Defining Characteristics

Inheritance
Object Defining Characteristics
Object-Oriented Modeling

Why use objects?

 Allows analysts and programmers to take a more


intuitive approach to design information systems,
applications, databases, and websites.
Object-Oriented Modeling

Why use objects? (cont’d)

 Also, because objects are specific sequences of


code they can be reused, which saves
programming time and increases quality and
performance.
Object-Oriented Modeling

Diagrams to describe Narrative Use-Case

 Use-Case Diagram

 Class/Object Diagram

 Object Sequence Diagram

 Object State-Transition Diagram


Use-Case Diagram

show a static overall view of the activities and


actors in an information system, and how the
information will be exchanged.
Use-Case Diagram
Class Diagram

Show the actual classifiers and their relationships


in a system
Class/Object Diagram
Object Diagram

Shows the instances of the classifiers in models. It


use notation that is similar to that used in class
diagrams.
Class/Object Diagram
Object Sequence Diagram

show how groups of objects exhibit behaviors in


response to a specific event called a trigger. Note
that the same Object can exhibit different
behaviors in response to different events
Object Sequence Diagram
Object State-Transition Diagram

Shows the entire lifecycle of a particular Object, in


terms of how event triggers can invoke different
behaviors
Object State-State Transition Diagram
Information Level – Artifacts

Data Dictionaries

Repositories for the data entities and attribute


that an enterprise collects and stores in
databases.
Data Dictionaries

Documents

 Standards for the format of data

 Relationships dependencies and rules

 Dependencies among data entities


Information Level – Artifacts

Object Dictionaries

Repositories for reusable objects.

The discrete pieces of programming code that


actually make up an object.

You might also like