System Engineering

based on
Chapter 6 - Software Engineering: A Practitioner’s Approach, 6/e

1
 Waterfall model 1 [aka Royce1970]
Systems Engineering

Software Req. Analysis Operation/Maintenance

Project Planning

Design

Implementation

Testing/Verification

Release
2
 System Engineering
 Elements of a computer-based system
 Software
 Hardware
 People
 Database
 Documentation
 Procedures

 Systems
 A hierarchy of macro-elements

3
 Business Process (Re-)Engineering
 to identify how information systems can best meet the strategic
goals of an enterprise, using an integrated set of procedures, methods, and
tools, given a set of business rules and constraints.

 focuses first on the enterprise and then on the business area

 creates enterprise models, data models and process models

(processes/services and interrelationships of processes and data)

 creates a framework for better information management,

distribution, and control
4
 System Architectures
 Three different architectures must be analyzed and designed within the
context of business objectives and goals:

 data architecture provides a framework for the information needs of a

business or business function (e.g., incident location, patient status,
ambulance location, drivers’ lunch hours and break, hospital locations, etc.)

 application architecture encompasses those elements of a system that

transform objects within the data architecture for some business purpose
(e.g., determine ambulance availability, determine hospital availability, etc.)

 technology infrastructure provides the foundation for the data and application
architectures (e.g., communication lines, computer platforms, etc.)

5
 System Modeling with UML
 Deployment diagrams
 Each 3-D box depicts a hardware element that is part of the
physical architecture of the system
 Activity diagrams
 Represent procedural aspects of a system element
 Class diagrams
 Represent system level elements in terms of the data that describe
the element and the operations that manipulate the data

6
 Conveyor Line Sorting System (CLSS)
CLSS must be developed such that boxes moving along a conveyor line will
be identified and sorted into one of six bins at the end of the line. The
boxes will pass by a sorting station where they will be identified. Based
on an identification number printed on the side of the box and a bar
code, the boxes will be shunted into the appropriate bins. Boxes pass in
random order and are evenly spaced. The line is moving slowly.

A desk-top computer located at the sorting station executes all CLSS

software, interacts with the bar-code reader to read part numbers on
each box, interacts with the conveyor line monitoring equipment to
acquire conveyor line speed, stores all part numbers sorted, interacts
with a sorting station operator to produce a variety of reports and
diagnostics, sends control signals to the shunting hardware to sort the
boxes, and communicates with a central factory automation system. 7
Deployment Diagram
CLSS proce s s or

So rt in g s u b s ys t e m Ope rat o r dis play

Se n so r d at a
s h u nt con t rolle r
acq uis it ion s u b s ys t e m

Co n ve yo r Bar cod e re ade r Sh un t act u at or

Pu ls e t ach

8
 Activity Diagram
s t a rt c o n v e y o r lin e

re a d b a r c o d e g e t c o n v e y o r sp e e d

v a lid b a r c o d e in v a lid b a r c o d e

d e t e r m in e b in lo c a t io n s e t f o r re je c t b in

se n d sh u n t
c o n t ro l d a t a

g e t sh u n t st a t u s re a d b a r c o d e g e t c o n v e y o r st a t u s

p ro d u c e re p o rt e n t ry

c onve yor s t oppe d c o n v e y o r in m o t io n

9
 Class Diagram
c lass nam e

Bo x
at t rib ut es
b arc o de not e us e of c a pit a l
fo rwa rdSpe e d le t t e r f or m ult i-word
co nve yo rLo ca t io n a t t ribut e na m e s
he ig ht
widt h
de pt h
weig ht
co nt e nt s
o pera t io ns
( pa re nt he s e s a t e nd
rea dBarc o de ( ) of na m e indic a t e t he
updat eSpe e d ( ) lis t of a t t ribut e s t ha t t he
rea dSpe ed ( ) ope ra t ion re quire s )
updat eLo c a t io n( )
rea dLo c at io n( )
g et Dim e nsio ns( )
g et We ig ht( )
che ckCo nt ent s( )
10
 Requirements Engineering
based on
Chapter 7 - Software Engineering: A Practitioner’s Approach, 6/e
copyright © 1996, 2001, 2005
R.S. Pressman & Associates, Inc.

For University Use Only

May be reproduced ONLY for student use at the university level
when used in conjunction with Software Engineering: A Practitioner's Approach.
Any other reproduction or use is expressly prohibited.

11
 Requirements Engineering Process:
A Basic Framework [Loucopolos]
Many variations and extensions
 3 fundamental activities:
understand, (formally) describe, attain an agreement on, the problem

User
User reqs
User feedback

knowledge Req. models

Elicitation Specification Validation
For more knowledge Val. result

Domain knowledge Domain knowledge

Problem
Domain
(domain experts, laws, standards, policies, documents, etc.)
 Elicitation: determine what’s really needed, why needed, whom to talk to
 Specification: produce a (formal) RS model: translate "vague" into "concrete", etc. make various decisions on what
& how
 Validation: assure that the RS model satisfies the users’ needs
12
 Requirements Engineering
 Elicitation - Inception—ask a set of questions that establish …
 (basic) understanding of the problem
 the people who want a solution
 the nature of the solution that is desired, and
 the effectiveness of preliminary communication and collaboration between
the customer and the developer
 Specification — can be any one (or more) of the following:
 A written document
 A set of models - A formal mathematical?
 A collection of user scenarios (use-cases)
 A prototype
 Validation — a review mechanism that looks for
 errors in content or interpretation
 areas where clarification may be required
 missing information
 inconsistencies (a major problem when large products or systems are engineered)
 conflicting or unrealistic (unachievable) requirements. 13
Eliciting Requirements - Inception
 Identify (key) stakeholders
 These are the people who will be involved in the negotiation
 “who else do you think I should talk to?”
 Recognize multiple points of view
 Work toward collaboration

 The first questions

 Who is behind the request for this work?
 Who will use the solution?
 What will be the (economic) benefit of a successful solution
 Is there another source for the solution that you need?

14
 Eliciting Requirements
 meetings are conducted and attended by both software engineers and customers
 rules for preparation and participation are established
 an agenda is suggested
 a "facilitator" (can be a customer, a developer, or an outsider) controls the meeting
 a "definition mechanism" (can be work sheets, flip charts, or wall stickers or an
electronic bulletin board, chat room or virtual forum) is used

 the goal is
 to identify the problem
 propose elements of the solution
 negotiate different approaches, and
 specify a preliminary set of solution requirements

15
 Elicitation Work Products
 a statement of need, scope, and feasibility.
 a list of customers, users, and other stakeholders who
participated in requirements elicitation
 a description of the system’s technical environment (cf.
enterprise model in system engineering).
 a list of requirements (preferably organized by function)
and the domain constraints that apply to each.
 a set of usage scenarios that provide insight into the use of
the system or product under different operating
conditions.
 any prototypes developed to better define requirements.
requirements

16
 Building the Analysis Model
 Elements of the analysis model
 Scenario-based elements
 Functional—processing narratives for software functions
 Use-case—descriptions of the interaction between an
“actor” and the system
 Class-based elements
 Implied by scenarios
 Behavioral elements
 State diagram
 Flow-oriented elements
 Data flow diagram

17
 Use-Cases
 A collection of user scenarios that describe the thread of usage of a system
 Each scenario is described from the point-of-view of an “actor”—a person or
device that interacts with the software in some way

 Each scenario answers the following questions:

 Who is the primary actor, the secondary actor (s)?
 What are the actor’s goals?
 What preconditions should exist before the story begins?
 What main tasks or functions are performed by the actor?
 What extensions might be considered as the story is described?
 What variations in the actor’s interaction are possible?
 What system information will the actor acquire, produce, or change?
 Will the actor have to inform the system about changes in the external
environment?
 What information does the actor desire from the system?
 Does the actor wish to be informed about unexpected changes? 18
 Use-Case Diagram
Ar ms / dis a rms
s ys t e m

Ac c e s s e s s ys t e m s e ns or s
via Int e rne t

home ow ne r

Re s ponds t o
a la r m e ve nt

Enc ount e r s a n
e r ror c ondit ion

s ys t e m Re c onfigure s s e ns ors
a dminis t ra t or a nd r e la t e d
s ys t e m fe a t ure s

19
 Class Diagram
From the SafeHome system …

Sensor

name/id
type
location
area
characteristics

identify()
enable()
disable()
reconfigure ()
20
 State Diagram
Re a ding
Init ia liz a t ion
c omma nds not ja mme d

t ur n c opie r subsyst e ms
syst e m st a t us=“not re a dy” syst e m st a t us=“Re a dy” pa pe r full
“on“ r e a dy
displa y msg = “ple a se wa it ” displa y msg = “e nt e r c md”
displa y st a t us = blinking displa y st a t us = st e a dy

e nt ry/ swit c h ma c hine on e nt r y/ subsyst e ms re a dy

do: run dia gnost ic s do: poll use r input pa ne l
do: init ia t e a ll subsyst e ms do: re a d use r input
do: int e rpre t use r input

t urn c opie r “off”

st a rt c opie s

Ma king c opie s loa d pa pe r

c opie s c omple t e
syst e m st a t us=“Copying”
syst e m st a t us=“loa d pa pe r”
displa y msg= “c opy c ount =”
displa y msg= “loa d pa pe r”
displa y me ssa ge =#c opie s pa pe r t ra y e mpt y displa y st a t us= blinking
displa y st a t us= st e a dy

e nt ry/ st a rt c opie s pa pe r ja mme d e nt ry/ pa pe r e mpt y

do: ma na ge c opying do: lowe r pa pe r t ra y
do: monit or pa pe r t ra y do: monit or fill swit c h
do: monit or pa pe r flow proble m dia gnosis do: ra ise pa pe r t ra y

syst e m st a t us=“Ja mme d”

displa y msg = “pa pe r ja m”
displa y me ssa ge =loc a t ion
displa y st a t us= blinking not ja mme d
e nt ry/ pa pe r ja mme d
do: de t e rmine loc a t ion
do: provide c orre c t ivemsg. 21
do: int e rrupt ma king c opie s
 Validating Requirements
 Is each requirement consistent with the overall objective for the system/product?
 Have all requirements been specified at the proper level of abstraction? That is, do
some requirements provide a level of technical detail that is inappropriate at this
stage?
 Is the requirement really necessary or does it represent an add-on feature that may
not be essential to the objective of the system?
 Is each requirement bounded and unambiguous?
 Does each requirement have attribution? That is, is a source (generally, a specific
individual) noted for each requirement?
 Do any requirements conflict with other requirements?

 Is each requirement achievable in the technical environment that will house

the system or product?
 Is each requirement testable, once implemented?
 Does the requirements model properly reflect the information, function and
behavior of the system to be built.
22