Scribd
Upload
49 views4 pages

Week 5

This document provides an overview of Week 5 of the course IT 323 System Integration and Architecture I. The key points covered are: - The course focuses on system integration and evaluating integration architectures. - Objectives include discussing sequence diagram elements and symbols. - Instruction will be through lectures and case studies. - Unified Modeling Language diagrams including use case diagrams, class diagrams, sequence diagrams, and state diagrams will be covered. - Sequence diagrams show the flow of messages between objects over time and are used to document use case scenarios.

Uploaded by

Marjorie Montaño
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
49 views4 pages

Week 5

This document provides an overview of Week 5 of the course IT 323 System Integration and Architecture I. The key points covered are: - The course focuses on system integration and evaluating integration architectures. - Objectives include discussing sequence diagram elements and symbols. - Instruction will be through lectures and case studies. - Unified Modeling Language diagrams including use case diagrams, class diagrams, sequence diagrams, and state diagrams will be covered. - Sequence diagrams show the flow of messages between objects over time and are used to document use case scenarios.

Uploaded by

Marjorie Montaño
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

LEARNING MODULE

FOR
IT 323 SYSTEM INTEGRATION AND ARCHITECTURE I

_____________________________________________________

WEEK 5

COURSE OUTLINE

COURSE CODE : IT 323


TITLE : System Integration and Architecture 1
TARGET POPULATION : All Bachelor of Science and Information System
INSTRUCTOR : MS. MELISSA T. ZOLINA
Overview:

The course focuses on how a proposed system will be integrated with other existing or planned systems. It
addresses the System Integration problem using architectures as the basis and then addresses the evaluation of the
architectures in terms of the capabilities they provide.

Objectives:

 Discuss the Elements of a Sequence Diagrams


 State the Sequence Diagrams- Object Symbols

Instruction to the Learner

Teaching this course will be in lecture form. A number of case studies will also be used to illustrate
some concepts as mentioned in the indicative content. The System of Systems Integration Problem Human,
Organizational, Societal Cultural, Economic, and Technological aspects. The theory and practice of business
process integration, legacy integration, new systems integration, business-to-business integration, integration of
commercial-off-the-shelf (COTS) products, interface control and management, testing, integrated program
management, integrated Business Continuity Planning (BCP). Specific focus will be given to issues of interface
integration and interoperability of systems.

Getting Started

Unified Modeling Language (UML)

• Use case diagrams

• Class diagrams

• Sequential diagrams

• State Diagrams

Sequence Diagrams

 A Sequence Diagram is an interacting diagram that emphasizes the time ordering of messages
 It shows a set of objects and the messages sent and received by those objects.
 Sequence diagrams can be used to document use case scenarios
 Captures required objects early in analysis and verify object usage later in design
 Shows the flow of messages from one object to another, and as such correspond to the methods and events
supported by a class/object
Elements of a Sequence Diagrams

Graphically, a sequence diagram is a table that shows objects arranged along the X axis and messages, ordered in
increasing time, along the Y axis

Example

1. The Customer inserts a bank card, the Card Input sends the cards information to the Card Transaction
Handler, which detects that the Card Transaction Handler, which detects that the card is invalid (not invalid:
if no message is returned, the card is assumed valid).
2. The Card Transaction Handler instructs the Graphical User Interface (GUI) to display a message requesting
the customer’s Personal Identification Number (PIN)
3. The GUI request the PIN and the customer enters his or her PIN, which is then passed to the Card
Transaction Handler
4. The Card Transaction Handler checks if the PIN is correct. In this scenario it is not, and the GUI is instructed
to inform the customer that the PIN is invalid

Sequence Diagrams- Object Symbols

 An object in a sequence diagram is rendered as a box with dashed An order line


line descending from it.
 The line is called the object lifeline, and it represents the existence of an
object over a period of time

 Messages are rendered as horizontal {check()} arrows being passed


from
Object to object as time advances down the object lifeline
 Conditions (such as [check = “true”] ) indicate when a message
gets passed
 Notice that the bottom arrow is not solid, and there is no
accompanying message
 This arrows indicates return from a previous message not a new
message

Sequence Diagrams- Iteration Marker

 An iteration marker, such as * (as shown ) or * [I=1…n],


indicates that a message will be repeated as indicated

Sequence
Diagram-
Example

You might also like