Professional Documents
Culture Documents
US OOAD 02 Requirements
US OOAD 02 Requirements
SCADA System
Nine System’s Characteristics
“Systems” Thinking
Identify something as a system
7
Information Systems
Def. An Information System (IS) is a collection of
interrelated components that collect, process, store, and
provide as output the information needed to complete a
business task.
8
Types of Information Systems
9
Hierarchy of Information Systems
Hierarchy: System, Subsystem, Supersystem
Ex: customer support system: order entry subsystem, order fulfillment
subsystem, shipping and back order subsystem, product catalog
maintenance, etc.
10
System Boundary vs. Automation
Boundary
System boundary: separates system from other
systems and from its environment
11
Example _ System Boundary
Example _ Automation Boundary
Part B
REQUIREMENT ANALYSIS
Conceptual Model for SW Architectures
Requirements Analysis
Traditional SE suggests requirements analysis should
remain unsullied by any consideration for a design
17
New Perspective on Requirements
Analysis
Existing designs and architectures provide the solution
vocabulary
18
Software Architecture’s Elements
A software system’s architecture typically is not (and
should not be) a uniform monolith
Definition
A software component is an architectural entity that
encapsulates a subset of the system’s functionality and/or data
restricts access to that subset via an explicitly defined interface
has explicitly defined dependencies on its required execution
context
Definition
A software connector is an architectural building block
tasked with effecting and regulating interactions among
components
Streaming connectors
Distribution connectors
Wrapper/adaptor connectors
23
Configurations
Components and connectors are composed in a specific
way in a given system’s architecture to accomplish that
system’s objective
Definition
An architectural configuration, or topology, is a set of
specific associations between the components and
connectors of a software system’s architecture
Example for Context Diagram
Small
Individuals Businesses
Users
act as act as
Buyers Sellers
buy items from the
buy sell
items items
in the in the
perform
accounting duties
Security using the
Employees Officers
Global
handle sends
Personal
security violations information
Marketplace
of the to the
(GPM)
provide
User Support
user support
work for Agents authorizes
for the
credit card
transactions
via the
Global
Personal
Marketing Authorization
Corp. Processor
Gateway
Deployment Diagram
Network Architecture Diagram
What’s the difference between software that
works and software that works well?
Example
You’ve been hired to build an online store
Capacity
Localization Regulatory
Performance Portability
Reliability
Example
• Scalability, performance, efficiency: “The website
should process each request within 4 seconds or less
99% of the time.”
Questions:
1. Which requirements are functional business requirements?
2. Which requirements are non-functional business requirements?
3. What kinds of non-functional requirements are they? Provide two
additional examples.
Any Questions?