1

MMISMO_OMMETHODS OF MANAGEMENT INFORMATION

SYSTEMS MODELING

Course code: IEZ001210W

Grażyna Hołodnik-Janczura, Ph.D.

K4/Z1

Operation Research, Finance, and Information System Engineering Division

B-4, room 517

phone: (71) 320-23-35

e-mail: grazyna.holodnik-janczura@pwr.wroc.pl

office hours on: www.wiz.pwr.edu.pl/pracownicy

Website: https://www.ii.pwr.edu.pl/~ghj/

GHJ - PWR

2

CONDITIONS FOR RECEIVING CREDIT

• To receive credit a student must meet the following criteria:

• Lecture

• take two tests: min. 50% of score for each one

• first test: 11.04.2019

• second test: 06.06.2019

• Laboratory

• carry out the lab work

• achieve a score min. 50%

• deadlines:

• Part A: 04.04/28.03.2019

• Part B: 10.06/23.05.2019

GHJ - PWR

MISMO_BIS BASED ON BARKER RICHARD AND CLIFF LONGMAN (CASE*MATHOD)

CONTENTS

I. Function Hierarchy Diagram (FHD)

II. Function Dependency Diagram (FDD)

III. Entity Relationship Diagram (ERD)

IV. Basic technique of logical relational database design from an entity relationship model

V. CRUD Method and Function Logic

GHJ - PWR 3

• Basic literature

• Barker R., Longman C., CASE*Method: Function and Process Modelling, Addison-Wesley Pub. Comp., 1992

• Barker R., CASE*Method: Entity Relationship Modelling, Addison-Wesley Pub. Comp., 1991

• Additional literature

• Chen P.P., The entity-relationship modelling, ACM Transactions on Database Systems, 1976

• Date C.J., An introduction to database systems, Addison-Wesley Pub. Comp., 1986

• De Marco T. (1979) Structured analysis and system specification, Prentice Hall, Englewood Cliffs, NJ

• Flynn D.J., Fragoso Diaz O., Information Modelling, An International perspective, Prentice Hall, 1996

• Gane C., Sarson T., (1989) Structured systems analysis: tools and techniques, Prentice Hall, Englewood Cliffs, NJ.

GHJ - PWR 4

Literature

WHEN TO USE INFORMATION SYSTEMSMODELING TECHNIQUES?

GHJ - PWR 5

Design

Project Planning

Requirements

Definition

Development

Integration

& Test

Installation

& Acceptance

FHD

FDD

ERD

RDBD

CRUD

Techniques & Models

SDLC – Waterfall Model

LECTURE 1

• Introduction

• Basic definitions

• Function Hierarchy Diagram

• Objectives of the function modeling

• Categories of function

• Business function definition

• Function decomposition

• Layout style patterns to illustrate the function hierarchy

• Approach in hierarchy modeling

• FHD example

• Summary

• Literature

• [Barker I] Barker R., Longman C., CASE*Method: Function and Process Modelling, Addison-Wesley Pub. Comp., 1992

GHJ - PWR 6

A KEY GOAL FOR US

• Obtaining detailed knowledge of the Structural Methods and Techniques for Management Information Systems Modeling

• Achieving practical skills in building these models

• focused on what the business really does need to achieve

• using relevant and appropriate functional modeling techniques

• Information models become a part of a specification of business requirements

• Information system modeling is a means, not an end – enables to understand requirements, to plan and invent good system designs, and develop appropriate systems

GHJ - PWR 7

MANY METHODS, MANY STANDARDS: TWO APPROACHES OF INFORMATION SYSTEMS

DEVELOPMENT

• Traditional approach: structured methods developed which distinguished the functional approach from the data structured one• Information Engineering (IE)• Structured Systems Analysis and Design Method (SSADM)• CASE*Method (Computer Aided Systems/Software Engineering)• Yourdon Systems Method (YSM)• Metodologica Informatica (MEIN)

• Modern approach: Object-oriented (OO) methods – the technique of integrating processes and data into one object called• Object Modeling Technique (OMT)• Rational Unified Process (RUP)

GHJ - PWR 8

MODELING TOOLS

• Software product modeling technique implementation with a different automation degree, which supports system requirements gathering, modification, publishing and prototyping.

• The highly advanced tools generate new deliverables, e.g. generate database design from an entity relationship model.

• CASE tools, e.g. IE Workbench, Designer 2000, Easy CASE, Architect.

GHJ - PWR 9

MODEL DEFINITION

• The function of models in physics, biology, medicine and other sciences resembles that of myths as paradigms, or patterns, of the human world [Encyclopedia Britannica]

• A description or analogy used to help visualize something that cannot be directly observed [Merriam-Webster Online Dictionary]

• A construction model of a language must be able to identification of the model – this is a precision condition

• A model may be expressed as• A syntax some language (natural language)

• an algebraic formula (formal)

• a schema with rigorous standards and conventions (graphical)

GHJ - PWR 10

META MODEL

A meta model – simply, is a model of a model

[Barker I, s. 361]

• It’s a definition of the construction model by the use of the language of this model

• It’s created during a meta modeling process

• Designing CASE tools is an example of the meta modeling process

GHJ - PWR 11

MODELING

• Modeling is an indispensable technique for presenting ideas, aiding understanding and predicting new ways of doing things

• Arguably our own perception of the world is an elaborate model we create in our brains from the information we have gathered

• Good modeling techniques are supported by rigorous standards and conventions to remove ambiguity

GHJ - PWR 12

SCHEME OF THE PROCESS MODELING

GHJ - PWR 13

individualityof the real world

symbol

idea

It’s coming as a goodunderstanding

expressed by use

presented by

IS – BLACK BOX

• input (x) – input information

• output (y) – output information

• S – relation S (x, y) – models, procedures

GHJ - PWR 14

Sinput (x) output (y)

INFORMATION SYSTEM DEFINITION

• is a specific nervous system of an organization,

• which joins management system elements in a whole

GHJ - PWR 15

[Koźmiński A.]

INFORMATION SYSTEM

• A system is a named, defined and interacting collection of real-world facts, procedures and processes, along with the organized deployment of people, machines, various mechanisms and other resources that carry out those procedures and processes [Barker I, p. 162].

• Information system is a part of an organization responsible for the development, operation and maintenance of computer-based systems [Barker I, p.369].

• The ideal systems are a combination of manual and computer processes that elegantly fit into the way the business needs to run.

GHJ - PWR 16

MANAGEMENT INFORMATION SYSTEM (MIS)

• Is a subset of the overall internal controls of a business covering the application of people, documents, technologies, and procedures by management accountants to solve business problems such as costing a product, service or a business-wide strategy.

• Management information systems are distinct from regular information systems in that they are used to analyze other information systems applied in operational activities in the organization.

[O’Brien, J (1999). Management Information Systems – Managing Information Technology in the Internetworked Enterprise. Boston: Irwin McGraw-Hill]

GHJ - PWR 17

FUNCTION MODELING TECHNIQUES

1. Function Hierarchy Diagram (FHD)

2. Function Dependency Diagram (FDD)

3. Detailed Function Definition – Function Logic

GHJ - PWR 18

OBJECTIVES OF THE FUNCTION MODELING

• Full, exact and accurate understanding of what organizations do

• To provide a model of functional needs of an organization, which will then act as a framework for development of new or enhanced systems

• The function modeling enables to understand requirements, devises good systems designs and creates appropriate systems – is a means, not an end

GHJ - PWR 19

OBJECTIVES OF THE FUNCTION MODELING (CONT.)

• To provide a model that is independent of any mechanism or processing method, allowing objective decisions to be made about alternative implementation techniques and coexistence with existing systems [Barker I, pp.1-2]

GHJ - PWR 20

WHAT IS A MECHANISM?

• Mechanism – a technique or technology for implementing a function: manual, telephone, computer, e-mail …[Barker I, p. 369]

• The function „Receive job request” – this could be done by e-mail, post, telephone, …

• How the business carries out the function to achieve its objectives ? What are new ways the function performs? – is a mechanism

• The decision to choose the mechanism should be based on existing constraints, such as: people, organization, suitable technology, cost made during the design phase

GHJ - PWR 21

BUSINESS FUNCTION DEFINITION

• Business function is an isolated and logically related group of activities

• Business functions in an organization are the way to achievement of their business objectives

• To achieve their of the business objectives is to be conditioned by permanent carrying out of business functions

GHJ - PWR 22

BASIC GROUPS OF MANAGEMENT FUNCTIONS

• Planning: a formulation of objectives, a prediction of future conditions and resources

• Organizing: performing activities which would link various activities of many members of anorganization

• Motivating: creating proper subordinates to tasks assigned to them

• Controlling: comparing performance or results of certain actions

GHJ - PWR 23

CONDITIONS FOR BUSINESS FUNCTION CARRY OUT

• Relation with objectives

• Legislation (law)

• Corporate policy

• Role/job type, organization units

• Geographic location

GHJ - PWR 24

FUNCTION HIERARCHY

• Hierarchy has a genealogical tree structure, sometimes similar to an organization structure

• The simplest and most useful technique for a starting-point of business functions modeling is to produce a hierarchy of them,• where each function is described by a simple unambiguous

sentence, starting with a verb.

GHJ - PWR 25

FUNCTION HIERARCHY DIAGRAM (FHD)

• FHD is a business functions model of an organization, these business functions are carried out agreement with their objectives and in the answer to events

• The function hierarchy is a result of n – leveling decomposition top function (root)

• Every function type ‘parent’ is described in more detail with the function type ‘children’

GHJ - PWR 26

APPROACH IN HIERARCHY MODELING

GHJ - PWR 27

The needs

The needs

The full scope to modeling

Not neededdetails

Missing details

Bottom-up only Top-down only

Top-down + Bottom-up

Missing information

[Barker I, p. 56]

FUNCTION DECOMPOSITION

• Constructing a hierarchy from two different directions

• Function decomposition ‘top-down’ plus function grouping ‘bottom-up’

• max 9 sub-functions at the same level

• General model: 2-3 levels

• Detailed model: 5-7 levels

• Creating hierarchy - iteration process

GHJ - PWR 28

BASIC LAYOUT STYLE PATTERNS TO ILLUSTRATE FUNCTION HIERARCHY

[BARKER I, PP. 75-79]

GHJ - PWR 29

a) vertical b) horizontal c) hybrid

ILLUSTRATION OF THE FUNCTION DECOMPOSITION[BARKER I, P. 57]

GHJ - PWR 30

function

parent

sub-function

child

These are all and

only these functions

which do need to

carry out the parentfunction.

The order of these functions

implies no sequence

Decomposition

continuous

until the

required level

of detail

is achieved

CONSTRUCTION RULES OF A FUNCTION NAME

• Starting with a verb, adopt the same form through the hierarchy –an imperative form is recommended

• It should continue with the object of the verb – to things use a singular form

• It should be a full and descriptive text

• Include a condition in the full name for a function execute – a conditional function

• Remove a mechanism: how the business carries out the function?

• Use a function label – simply a short name or tag: a shot mnemonic or a number

GHJ - PWR 31

GHJ - PWR 32

Take a delivery as per order

F111 ...

function name

B. F. position in the hierarchyLabel, reference code decomposition symbol

verb

noun - object

condition

graphic symbol

Business function name components

CATEGORIES OF FUNCTION

• Root function - is applied to function at the top of the hierarchy, this is a function of the highest level

• Leaf function – is applied to functions at the bottom of the hierarchy and the analysis is still incomplete or complete

• Atomic function – a leaf functions if the analysis is complete

• Elementary function – a leaf functions if the analysis is complete and this function has to ensure that the information it manipulates remains consistent and coherent from the business perspective

• Elementary function may be broken up into atomic functions, which arenot the only functions from the business perspective

• Common function – a business function that appears in more than one place in the hierarchy

GHJ - PWR 33

WHEN TO STOP FUNCTION DECOMPOSITION?

• An elementary function level ended decomposition

• Elementary function – an end of decomposition from the business perspective

GHJ - PWR 34

ELEMENTARY BUSINESS FUNCTION DEFINITION

• If started, it must be completed successfully or, if for some reason it can’t be completed, any changes it makes up to the point of failure must be undone [Barker I, p. 40]

• It ensures that all changes to information representing the state of the business are correct and coherent before any of them are made available to another function

• It represented the state of the business

• The term ‘elementary’ is not a property of the function, it applies to a position in a function hierarchy

GHJ - PWR 35

CONCEPT OF THE ELEMENTARY FUNCTION

ILLUSTRATION

GHJ - PWR 36

Transfer dollars from one bank account to another

Taking the money from one account

Putting the money into another account

F 33

F331

F332

If the debit succeed (F331) but, for some reason, the credit fails (F332),than the bank’s business is in an inconsistent state [Barker I, p. 136]

debit

credit

elementary function

atomicfunction

COMMON BUSINESS FUNCTIONS

• A business function that appears in two or more places in a hierarchy [Barker I, p. 114]

• Must:• curry out the same functional processing,• manipulate the same information in the same way (entity,

attribute, relationship)• have exactly the same decomposition

The common functions are called: a master and the rest of them are a subordinate

• a master function may have more then one subordinate function, in practice they are not more than two,

• subordinate function can’t be a master function for another subordinate function.

GHJ - PWR 37

PRESENTATION OF THE COMMON BUSINESS FUNCTION

GHJ - PWR 38

P 55

P551

P552

P2

Label of the masterfunctionSubordinate

function

CONCEPT OF THE COMMON FUNCTIONS ILLUSTRATION

GHJ - PWR

39

Reserve seat on course

Check availability of seaton identified course

Reserve seat onrequested course

Inform and confirmreservation details

Remove reservationfrom one to another

Delete carried outreservation

Reserve seat on course

Calculate quota of removereservation

R11 R12

R111

R112

R113

R121

R122

R123

R11

FUNCTIONS WITH IDENTICAL DESCRIPTIONS – ARE NOT COMMON

• Compare the detailed definitions of the common functions – you may find that although they are not identical, they

• Set a task for an employee – a function to produce a schedule forwork

• Set a task for an employee – a function to manage the personnel of an organization

• Each function manipulates the same or other information in adifferent way

GHJ - PWR 40

COMMON FUNCTIONS - HAVE DIFFERENT DESCRIPTIONS

• It is more likely for two functions that are really common functions to have different descriptions, e.g. functions can be written from different viewpoints [Barker I, p. 117]:

• Allocate a class to a specified room for a regular slot during a term –a function to produce a schedule for a class

• Allocate a room for use by a class at a regular time each week throughout a period – a function to manage the resources of the college

• Each function manipulates the same information in the same way

GHJ - PWR 41

REMOVING COMMON FUNCTIONS[BARKER I, P. 116]

GHJ - PWR 42Common functions

Move to here

Modify the name

of a function

if necessary

The lowest point in hierarchy

which is parent to

the common function

FUNCTION HIERARCHY DIAGRAM (FIRST AND SECOND OF LEVEL)

GHJ - PWR 43

MB

Manage the transport business

Market serviceand promotethe business

Analyze routeusage

Publish route

Promotethe service

Recruitand maintain

adequate personnel

Define andmaintain

crew schedule

Recruitpersonnel

Providestaff training

Provide ticketsales andbook seat

Sell ticket

Book seat

Providepassengercheck-in

Providefinance

Providesupplier

accounting

Producereport

Providecustomer

accounting

Plan andmaintain adequate

transport

Create a transportplan for all routes

Purchase a newtransport

Renovateold transport

MAR EMP RES ACC TS

M1

M2

M3

E1

E2

E3

R1

R2

R3

A1

A2

A3

T1

T2

T3…

…

…

…

…

… …

…

…

…

…

…

…

…

…

FUNCTION HIERARCHY DIAGRAM (THIRD OF LEVEL)

GHJ - PWR 44

Recruit personnel

Makea job offer

Analyzea job

application

Make ajob interview

Book seat

Accept a newbooking

Change onebooking

to another

Acceptwithdrawalof booking

E2

R2

E21

E22

E23

R21

R22

R23

…

…

Select andaccept

applicant

…

…

…E24

…

…

GHJ - PWR 45

Select and accept applicant

Review documents

Negotiate job termsand conditions

Accept contract

E24

E241

E242

E243

Function Hierarchy Diagram (fourth of level)

THE KEY ISSUES

• Functions, what the organization has to do to achieve its objectives

• Unambiguous definition – represents the essence of what the business does, as opposed to how it does it

• Independence from mechanism – at the business level, functions should be defined in a manner that is independent of how they will eventually be carried out

• Attitude and quality – the analyst must be objective, persuasive and educational, the models must be correct, useful and appropriate

• A means, not an end – function modeling enables to understand requirements, devises good systems designs and createsappropriate systems

GHJ - PWR 46

FHD SUMMARY

• Six interrogative words used in the research questions :• What: what does and needs to do• Why: relation with objectives• Who: role/job titles• When: sequence and timing• Where: organization structure• How: mechanism

• In a function hierarchy model only:• what is an operation the business does, or needs to do• why is the objective it is trying to achieve by doing it

GHJ - PWR 47

[Barker I, p. 80]