System Engineering - Aalborg Universitetpeople.cs.aau.dk/~ivan/SOE2000/SOE02.pdf · Business System...

SOE2 1

1SOE2000

System Engineering

Software Engineering 2

2SOE2000

SystemEngineeringHierarchy

World view

Domain view

Element view

Detailed view

Business orProduct Domain

Domain of interest

System element(component)

Constituent

SOE2 2

3SOE2000

Business Process Engineering

• Uses an integrated set of procedures,methods, and tools to identify howinformation systems can best meet thestrategic goals of an enterprise

• Focuses first on the enterprise and then onthe business area

• Creates enterprise models, data models andprocess models

• Creates a framework for better informationmanagement distribution, and control

4SOE2000

The BPEHierarchy

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 ISPConstruction and delivery

• using CASE and 4GTs, testing

SOE2 3

5SOE2000

BPEHierarchy

InformationStrategy Planning

(World view)

Business AreaAnalysis

(Domain view)

Business SystemDesign

(Element view)

Construction &

Integration(Detailed view)

The enterprise

business area

Processingrequirement

A businessarea

Softwareengineer

6SOE2000

Information 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 clusteringBusiness Process Engineering

SOE2 4

7SOE2000

Defining Objectives and Goals

Objective-general statement of directionGoal-defines measurable course of actionExamples:

• objective-reduce manufactured cost of ourproduct

• goals➩ decrease reject rate by 20% in first 6 months➩ gain 10% price concessions from suppliers➩ re-enqineer 30% of components for ease of manufacture

during first year

Objectives tend to be strategic while goals tend tobe tactical Business Process Engineering

8SOE2000

Business Area Analysis

Define "naturally cohesive groupings of businessfunctions and data" (Martin)

Perform many of the same activities as ISP, but narrowscope to individual business area

Identify existing (old) information systems anddetermine compatibility with new ISP model

• define systems that are problematic

• defining systems that are incompatible with

• new information model

• begin to establish re-engineering prioritiesBusiness Process Engineering

SOE2 5

9SOE2000

The BAA Processadmin.

sales QC

acct engineering

distribution

manufacturing

ProcessFlow

Models

ProcessFlow

ModelsData

Model

DataModel

ProcessDecomp.Diagram

ProcessDecomp.Diagram

Matricese.g.

entity/processmatrix

Matricese.g.

entity/processmatrix


10SOE2000

CASE and Business ProcessEngineering: Data oriented Tools

• Supporting information engineering by James Martin andothers.

• Data is seen as the main resource of the enterprise.• Based on data-models defining the basic data units and data relationship

for the entire enterprise. Databases and process logic are derived fromthese models.

• Information matrices, entity-relationship diagrams (ERD), entity-hierarchydiagrams, process-hierarchy diagrams, dialog-flow diagrams, screen-design,data-structure-diagrams, database-generators, COBOL-generators.

• Information Engineering Facility (IEF), InformationEngineering Workbench (IEW) , ER-Designer (ERD).


SOE2 6

11SOE2000

Information Engineering Facility (IEF)• Enforces top-down planning, analysis, design, and

implementation.• Primarily used for developing on-line/batch, screen-

oriented administrative systems.• Supports developing windows-based applications.• Strong separation of database and process-logic.• Information planning, analysis and design is done on a

workstation, after relevant parts of the entire data modelhas been downloaded from main-frame.

• Compilation of modules, database generation and codegeneration takes place on the mainframe.


12SOE2000

Information Engineering Facility II

Information strategy planning

Business area analysis

Business application design

Technical design


SOE2 7

13SOE2000

IEF - Information planning

MatricesPr

oduc

ing

Customer

C = CreateR = ReadU = UpdateD = Delete

Entity Types

Order

Mar

ketin

g

Cus

tom

er re

gist

ratio

n

Acc

ept O

rder

Cha

nge

Ord

er

C

ance

l ord

er

Bus

ines

s Fu

nctio

ns

CU

DR

UD


14SOE2000

IEF - Analysis

Entity relationship diagrams

Customer

Product

Supplier Part

Order Warehouse

Order line

Places Consists of

Mentions

Supplies

Is stored in

Stored in

Consists of

Supplies


SOE2 8

15SOE2000

IEF - Analysis II

Process hierarchy

Runningthe company

Marketing

Selling

Customerregistration

Orderprocessing

Acceptorder

Changeorder

Cancelorder

Producing


16SOE2000

IEF - Analysis III

Process dependencies

Orderrequest

Acceptorder

ChangeOrder

CancelledOrders

Availableproducts

Cancelorder

OrdersOrder inf

Order

Product inf

Order

Order


SOE2 9

17SOE2000

IEF - Analysis: Process-handling

Process: ACCEPT ORDER ACCEPT ORDER

IMPORTS: Entity View to_be_ordered_product...........

EXPORTS: Entity View confirmed order_line...........

ENTITY ACTIONS: Entity View confirmed order_line...........

READ to_be_controlled productWITH name EQUAL TO to_be_ordered product name

WHEN not foundESCAPE

...........CREATE confirmed orderSET date TO "system date"SET number TO "next free value"ASSOCIATE WITH to_be_controlled customer WHICH places ITASSOCIATE WITH confirmed order_line WHICH details ITWHEN already exists

.........

MOVE confirmed order TO accepted order,


18SOE2000

IEF - Design: Dialog-flow

Menu

Accept order

Accept order header

Accept order lines

Accept customer


SOE2 10

19SOE2000

IEF - Design: Screen design

TRANCODE ORDER PROCESSING MM-DD-YY HH:MM:SS

ORDER NUMBER: 9999999CUSTOMER NUMBER: 9999999

NAME: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX XX XXXXXXXXXXXXXXXXXXXXXXXXX

999 999999 XXXXXXXXXXXXXXXXXXXXXXXXXXX 9999 XX $,$$$,$$9.99999 999999 XXXXXXXXXXXXXXXXXXXXXXXXXXX 9999 XX $,$$$,$$9.99

999 999999 XXXXXXXXXXXXXXXXXXXXXXXXXXX 9999 XX $,$$$,$$9.99

999 999999 XXXXXXXXXXXXXXXXXXXXXXXXXXX 9999 XX $,$$$,$$9.99

LINE PRODUCT DESCRIPTION QTY UN UNIT PRICE

<<<ERR>>> <<<ERR>>> <<<ERR>>> <<<ERR>>> <<<ERR>>> <<<ERR>>> <<<ERR>>> <<<ERR>>>

<<<PFK>>> <<<PFK>>> <<<PFK>>> <<<PFK>>> <<<PFK>>> <<<PFK>>> <<<PFK>>> <<<PFK>>>

ORDER DATE: MM-DD-YYSTATE: XX


20SOE2000

IEF: From Analysis to CodeInformationStrategyPlanning

BusinessAreaAnalysis

Business SystemDesign

TechnicalDesign

A

xxx xxx xxxx x x x x

xxx xxx xxxx x x x x

A

Database generering Kode-generering

1-5

12-16

17

6-11

Database generation Code generation


SOE2 11

21SOE2000

IEF: From Analysis to Code

Information Strategy Planning:1 Matrix Processor2 Organizational Hierarchy Diagram3 Subject Area Diagram4 Function Hierarchy Diagram5 Function Dependency Diagram

Business System Design:12 Dialog Flow Diagram13 Screen Design14 Prototyping15 Procedure Action Diagram16 Structure Chart

Technical Design:17 Data Structure Diagram

Business Area Analysis:6 Entity Relationship Diagram7 Process Hierarchy Diagram8 Process Dependency Diagram9 Process Action Diagram10 Structure Chart11 Matrix Processor


22SOE2000

ProductEngineering

System analysis(World view)

Componentengineering

(Domain view)

Analysis & DesignModeling

(Element view)

Construction &

Integration(Detailed view)

The completeproduct

capabilities

Processingrequirement

software

Softwareengineer

hardware

data function behavior

Programcomponent

SOE2 12

23SOE2000

Requirements Engineering

• Elicitation — determining what the customerrequires

• Analysis & negotiation — understanding therelationships among various customerrequirements and shaping thoserelationships to achieve a successful result

• Requirements specification — building atangible model of requirements

24SOE2000

Requirements Engineering

• System Modeling — building arepresentation of requirements that can beassessed for correctness, completeness, andconsistency

• Validation — reviewing the model• Management — identify, control and track

requirements and the changes that will bemade to them

SOE2 13

25SOE2000

System Allocation

Allocation

software

hardware

people

data

documentsprocedures

systemcompo-nents

supportinfra-structure

objects

processes

performance

constraints

Product Engineering

26SOE2000

System Model Template

user interface processing

inputprocessing

outputprocessing

process and controlfunctions

maintenance and self-test

Product Engineering

SOE2 14

27SOE2000

A Conveyor Line Sorting System(CLSS).

Conveyor line motion

Shunt

1

2

3

4

5

6

Sortingstation

ID No. ID No. ID No.

• Read bar code input• Read pulse tachometer• Decode part code data• Do database look-up• Determine bin location• Produce control signal for shunt• Maintain record of box destinations

Bar code

Product Engineering

28SOE2000

System Context Diagram forCLSS

sortingstation

operator

bar codereader

sortingmechanism

conveyorline

mainframe

sortingstation

operator

ConveyorLine

SortingSystem

barcode

linespeedindicator diagnostic data

request queries andreports

shuntcommands

formattedreportingdata

Product Engineering

SOE2 15

29SOE2000

System Flow Diagramoperatorinterface

subsystem

bar codereader

subsystem

sensor dataacquisitionsubsystem

diagnosticssubsystem

shuntcontroller

mainframecommunic.

driver

bar codedecoding

subsystem

shuntcontrol

subsystem

reportformattingsubsystem

data baseaccess

subsystem

barcode

bar code acquisition request

operator requests CLSS queries, reports, displays

shunt control status

reportrequests

sortingreports

key

binlocation

sortrecords

line speed

raw barcode data

pulsetachinput

part numbertiming/location

data

CLSSreports

formattedreporting data

shuntcom-

mands

CLSS processing & control

30SOE2000

The Transition to Software Engineering

Allocation

software

hardware

people

data

documentsprocedures

SoftwareEngineeringbegins …

StructuredAnalysis

StructuredDesign

System Engineering - Aalborg Universitetpeople.cs.aau.dk/~ivan/SOE2000/SOE02.pdf · Business System...

Documents

Transcript of System Engineering - Aalborg Universitetpeople.cs.aau.dk/~ivan/SOE2000/SOE02.pdf · Business System...