chapter 6 system engineering
DESCRIPTION
Chapter 6 System Engineering. Software Engineering: A Practitioner’s Approach, 6th edition by Roger S. Pressman. System Engineering. Elements of a computer-based system Software Hardware People Database Documentation Procedures Systems A hierarchy of macro-elements. The Hierarchy. - PowerPoint PPT PresentationTRANSCRIPT
![Page 1: Chapter 6 System Engineering](https://reader035.vdocument.in/reader035/viewer/2022081416/56813ac0550346895da2cdf5/html5/thumbnails/1.jpg)
1
Chapter 6System Engineering
Chapter 6System Engineering
Software Engineering: A Practitioner’s Approach, 6th editionby Roger S. Pressman
![Page 2: Chapter 6 System Engineering](https://reader035.vdocument.in/reader035/viewer/2022081416/56813ac0550346895da2cdf5/html5/thumbnails/2.jpg)
2
System EngineeringSystem Engineering
Elements of a computer-based system Software Hardware People Database Documentation Procedures
Systems A hierarchy of macro-elements
Elements of a computer-based system Software Hardware People Database Documentation Procedures
Systems A hierarchy of macro-elements
![Page 3: Chapter 6 System Engineering](https://reader035.vdocument.in/reader035/viewer/2022081416/56813ac0550346895da2cdf5/html5/thumbnails/3.jpg)
3
The HierarchyThe HierarchyWorld view
Business orProduct Domain
Domain of interest
Domain view
System element
Element view
Detailed view
![Page 4: Chapter 6 System Engineering](https://reader035.vdocument.in/reader035/viewer/2022081416/56813ac0550346895da2cdf5/html5/thumbnails/4.jpg)
4
System ModelingSystem Modeling
define the processes that serve the needs of the view under consideration.
represent the behavior of the processes and the assumptions on which the behavior is based.
explicitly define both exogenous and endogenous input to the model. exogenous inputs link one constituent of a given view with other
constituents at the same level of other levels; endogenous input links individual components of a constituent at a particular view.
represent all linkages (including output) that will enable the engineer to better understand the view.
define the processes that serve the needs of the view under consideration.
represent the behavior of the processes and the assumptions on which the behavior is based.
explicitly define both exogenous and endogenous input to the model. exogenous inputs link one constituent of a given view with other
constituents at the same level of other levels; endogenous input links individual components of a constituent at a particular view.
represent all linkages (including output) that will enable the engineer to better understand the view.
![Page 5: Chapter 6 System Engineering](https://reader035.vdocument.in/reader035/viewer/2022081416/56813ac0550346895da2cdf5/html5/thumbnails/5.jpg)
5
Business Process EngineeringBusiness Process Engineering
uses an integrated set of procedures, uses an integrated set of procedures, methods, and tools to identify how methods, and tools to identify how information systems can best meet the information systems can best meet the strategic goals of an enterprisestrategic goals of an enterprise
focuses first on the enterprise and then focuses first on the enterprise and then on the business areaon the business area
creates enterprise models, data models creates enterprise models, data models and process modelsand process models
creates a framework for better creates a framework for better information management distribution, information management distribution, and controland control
![Page 6: Chapter 6 System Engineering](https://reader035.vdocument.in/reader035/viewer/2022081416/56813ac0550346895da2cdf5/html5/thumbnails/6.jpg)
6
System ArchitecturesSystem Architectures
Three different architectures must be analyzed and designed within the context of business objectives and goals:
data architecture applications architecture technology infrastructure
data architecture provides a framework for the information needs of a business or business function
application architecture encompasses those elements of a system that transform objects within the data architecture for some business purpose
technology infrastructure provides the foundation for the data and application architectures
Three different architectures must be analyzed and designed within the context of business objectives and goals:
data architecture applications architecture technology infrastructure
data architecture provides a framework for the information needs of a business or business function
application architecture encompasses those elements of a system that transform objects within the data architecture for some business purpose
technology infrastructure provides the foundation for the data and application architectures
![Page 7: Chapter 6 System Engineering](https://reader035.vdocument.in/reader035/viewer/2022081416/56813ac0550346895da2cdf5/html5/thumbnails/7.jpg)
7
The BPE HierarchyThe BPE Hierarchy Information strategy planning (ISP)
strategic goals defined success factors/business rules identified enterprise model created
Business area analysis (BAA) processes/services modeled interrelationships of processes and data
Application Engineering a.k.a ... software engineering modeling applications/procedures that
address (BAA) and constraints of ISP Construction and delivery
using CASE and 4GTs, testing
Information strategy planning (ISP) strategic goals defined success factors/business rules identified enterprise model created
Business area analysis (BAA) processes/services modeled interrelationships of processes and data
Application Engineering a.k.a ... software engineering modeling applications/procedures that
address (BAA) and constraints of ISP Construction and delivery
using CASE and 4GTs, testing
![Page 8: Chapter 6 System Engineering](https://reader035.vdocument.in/reader035/viewer/2022081416/56813ac0550346895da2cdf5/html5/thumbnails/8.jpg)
8
Information Strategy PlanningInformation Strategy Planning Management issues
define strategic business goals/objectives
isolate critical success factors conduct analysis of technology impact perform analysis of strategic systems
Technical issues create a top-level data model cluster by business/organizational area refine model and clustering
Management issues define strategic business
goals/objectives isolate critical success factors conduct analysis of technology impact perform analysis of strategic systems
Technical issues create a top-level data model cluster by business/organizational area refine model and clustering
![Page 9: Chapter 6 System Engineering](https://reader035.vdocument.in/reader035/viewer/2022081416/56813ac0550346895da2cdf5/html5/thumbnails/9.jpg)
9
Defining Objectives and GoalsDefining Objectives and Goals Objective—general statement of direction
Goal—defines measurable objective: “reduce manufactured cost of our product”Subgoals:
decrease reject rate by 20% in first 6 monthsgain 10% price concessions from suppliersre-engineer 30% of components for ease of
manufacture during first year Objectives tend to be strategic while
goals tend to be tactical
Objective—general statement of direction Goal—defines measurable objective:
“reduce manufactured cost of our product”Subgoals:
decrease reject rate by 20% in first 6 monthsgain 10% price concessions from suppliersre-engineer 30% of components for ease of
manufacture during first year Objectives tend to be strategic while
goals tend to be tactical
![Page 10: Chapter 6 System Engineering](https://reader035.vdocument.in/reader035/viewer/2022081416/56813ac0550346895da2cdf5/html5/thumbnails/10.jpg)
10
Business Area AnalysisBusiness Area Analysis
define “naturally cohesive groupings of business functions and data” (Martin)
perform many of the same activities as ISP, but narrow scope to individual business area
identify existing (old) information systems / determine compatibility with new ISP model define systems that are problematic defining systems that are incompatible with new
information model begin to establish re-engineering priorities
define “naturally cohesive groupings of business functions and data” (Martin)
perform many of the same activities as ISP, but narrow scope to individual business area
identify existing (old) information systems / determine compatibility with new ISP model define systems that are problematic defining systems that are incompatible with new
information model begin to establish re-engineering priorities
![Page 11: Chapter 6 System Engineering](https://reader035.vdocument.in/reader035/viewer/2022081416/56813ac0550346895da2cdf5/html5/thumbnails/11.jpg)
11
The BAA ProcessThe BAA Process
salesacct
manufacturing
QC
eng’ring
distribution
admin.
DataModel
ProcessDecomposition
DiagramMatrices
e.g.,entity/process
matrix
Process Flow
Models
![Page 12: Chapter 6 System Engineering](https://reader035.vdocument.in/reader035/viewer/2022081416/56813ac0550346895da2cdf5/html5/thumbnails/12.jpg)
12
Product EngineeringProduct EngineeringSystem analysis
(World view)
The completeproduct
capabilities
Componentengineering
(Domain view)
Processing requirement
Analysis & DesignModeling
(Element view)
Construction&
Integration(Detailed view)
software
function
SoftwareEngineering
programcomponent
hardware
data behavior
![Page 13: Chapter 6 System Engineering](https://reader035.vdocument.in/reader035/viewer/2022081416/56813ac0550346895da2cdf5/html5/thumbnails/13.jpg)
13
Product Architecture TemplateProduct Architecture Template
user interface processing
inputprocessing
outputprocessing
maintenance and self-test
process and controlfunctions
![Page 14: Chapter 6 System Engineering](https://reader035.vdocument.in/reader035/viewer/2022081416/56813ac0550346895da2cdf5/html5/thumbnails/14.jpg)
14
Architecture Flow DiagramArchitecture Flow Diagram
bar codereader
subsystem
bar codedecoding
subsystem
data baseaccess
subsystem
shuntcontrol
subsystem
reportformating
subsystem
diagnosticssubsystem
operatorinterface
subsystem
shuntcontroller
mainframecommunications
driver
operator requests CLSS queries, reports, displays
shunt control statusbar code acquisition request
bar code
pulse tach input
linespeed
bar codereader status
sensor status
raw barcode data
partnumber
reportrequests
binlocation
key
sort records
formatedreporting data
sorting reports
shunt commands
CLSS reports
BCR statusshunt status
communications status
timing/location data
operatorinterface
data acquisitioninterface diagnostic interface output interface
CLSS processing & control
sensor dataacquisitionsubsystem
![Page 15: Chapter 6 System Engineering](https://reader035.vdocument.in/reader035/viewer/2022081416/56813ac0550346895da2cdf5/html5/thumbnails/15.jpg)
15
System Modeling with UMLSystem 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
These and other UML models will be discussed later
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
These and other UML models will be discussed later
![Page 16: Chapter 6 System Engineering](https://reader035.vdocument.in/reader035/viewer/2022081416/56813ac0550346895da2cdf5/html5/thumbnails/16.jpg)
16
Deployment DiagramDeployment DiagramCLSS processor
Sorting subsystem
Sensor dataacquisition subsystem
Operator display
shunt controller
Conveyor Pulse tach
Bar code reader Shunt actuator
![Page 17: Chapter 6 System Engineering](https://reader035.vdocument.in/reader035/viewer/2022081416/56813ac0550346895da2cdf5/html5/thumbnails/17.jpg)
17
Activity DiagramActivity Diagram
get conveyor speed
send shunt
control data
get shunt status read bar code
start conveyor line
determine bin location
valid bar code
set for reject bin
conveyor in motion
read bar code
get conveyor status
produce report entry
conveyor stopped
invalid bar code
![Page 18: Chapter 6 System Engineering](https://reader035.vdocument.in/reader035/viewer/2022081416/56813ac0550346895da2cdf5/html5/thumbnails/18.jpg)
18
Class DiagramClass Diagram
Box
barcode forwardSpeed conveyorLocation height width depth weight contents
readBarcode() updateSpeed() readSpeed() updateLocation() readLocation() getDimensions() getWeight() checkContents()
class name
attributes note use of capital letter for multi-word attribute names
operations (parentheses at endof name indicate the list of attributes that theoperation requires)
![Page 19: Chapter 6 System Engineering](https://reader035.vdocument.in/reader035/viewer/2022081416/56813ac0550346895da2cdf5/html5/thumbnails/19.jpg)
19
System EngineeringSystem Engineering A system view of a product encompasses more than just the software.
Elements of a computer-based system: Software Hardware People Database Documentation Procedures Other computer-based systems
A system view of a product encompasses more than just the software.
Elements of a computer-based system: Software Hardware People Database Documentation Procedures Other computer-based systems