Вы находитесь на странице: 1из 50

Lecture 2: Methods & Modeling

Information System Engineering

ISE-Lecture2-

FGR Summer

Outline
System

development methodology

ISE-Lecture2-

FGR Summer

Introduction

Purpose of the systems development function is to develop

effective

systems in the most

efficient

way possible.

The traditional systems development life cycle SDLC - (with which you are all familiar) was a first attempt to provide a controlled environment for systems development

ISE-Lecture2-

FGR Summer

Systems development life cycle

ISE-Lecture2-

FGR Summer

SDLC

Main criticisms: rigid, iterations allowed

no back-tracking or

Modern dev. frameworks built from this.

ISE-Lecture2-

FGR Summer

systems development methodology


Generic development framework Essential Steps Optional Steps

Order of steps METHODOLOGY

TOOLS & TECHNIQUES

ISE-Lecture2-

FGR Summer

hniques

Defining a Methodology
Avison & Fitzgerald (2006)

ISE-Lecture2-

FGR Summer

Technical Model

Method

ISE-Lecture2-

FGR Summer

The Technical model


DATA MODEL PROCESS MODEL BEHAVIOR MODEL

Tools & Techniques


ISE-Lecture2FGR Summer 9

Managerial model

Order in which steps are to be covered, how to control the activities. It provides the framework within which the development will take place. It defines stages, be undertaken.

steps

and

tasks

to

ISE-Lecture2-

FGR Summer

10

Managerial model
WHEN WHICH HOW

END - DELIVERABLES

ISE-Lecture2-

FGR Summer

11

End-deliverables (1)
Each

defined stage will have a prescribed end-deliverable or product which must be delivered as the stage is completed. Similarly, each step or task may have a sub-deliverable or sub-product associated with it

ISE-Lecture2-

FGR Summer

12

End-deliverables (2)
End-deliverable

may be presented in

the form of a

document/specification, a design, a presentation or as generated, tested code. It provides a


prescribed review stage and milestone for the project.

Forms an essential part of project management and review process.


ISE-Lecture2FGR Summer 13

The modelling concept


Model:
a

simplification/abstraction of the real object from a particular perspective of a particular part of a system (often a graphical representation) providing clear and unambiguous information about the system
ISE-Lecture2FGR Summer 14

view

Model: An example 2D model of a house

ISE-Lecture2-

FGR Summer

15

Model: An example 3D model of a house

ISE-Lecture2-

FGR Summer

16

Different real world models


Road map: model of a transport network


within a particular area.

Architects blueprint: schematic


representation of a building or a bridge .

A musical score: a graphical/text


representation of the musical notes and tempo required to play a piece of music

ISE-Lecture2-

FGR Summer

17

Software models: Example Class diagram

ISE-Lecture2-

FGR Summer

18

Software models: Example Sequence diagram

ISE-Lecture2-

FGR Summer

19

Software models: Example Story board To set out the


sequence for an animation or website design

ISE-Lecture2-

FGR Summer

20

Software models: Example Use case diagram

To show the interaction between user and system

ISE-Lecture2-

FGR Summer

21

Software models: Example Gantt chart

To depict the time available and the scheduling within that time

ISE-Lecture2-

FGR Summer

22

Importance of models
Modelling

tools enable analyst to:

Focus

upon key systems features and divorce them from any physical implementation issues. system requirements with low cost and minimal risk his/her understanding of the user requirements through a graphical representation of the required system
ISE-Lecture2FGR Summer 23

Investigate Verify

Abstraction

The process of focusing upon those features of something that are essential for the task in hand, and that are not.

ignoring

those

We build a model of something we are interested in to provide an view of that thing.

abstracted

Has great importance in modern development environment.


ISE-Lecture2FGR Summer 24

Abstraction

We need to comprehend complex situations


Focus

upon those characteristics of the business pertinent to the problem in hand those elements distinct from the problem situation.

Disregarding

When

modelling real world entities even more important that we consider the entity (object) within a given context
ISE-Lecture2FGR Summer 25

Abstraction example
Modelling
try

a car:

and model it by its external characteristics

how it looks, how many doors it has etc. - try and model it internal combustion engine how many valves it has, fuel injection system etc..
Depends

upon the task in hand

ISE-Lecture2-

FGR Summer

26

CAR: 1.8 LX fuel injection engine. ABS breaking system. Power Assisted Steering.

CAR: Racing car Red. Coupe. 5 doors. Sun roof. Alloy wheels. Tinted windows. Leather upholstery

Figure 1: Abstraction of a real-life object: CAR

Three model view


All

information systems can viewed from three different perspectives:

Data

oriented perspective (function) oriented perspective (dynamic) oriented perspective

Process

Behavioural

ISE-Lecture2-

FGR Summer

28

Three model view

Process

3 views together model a system

ISE-Lecture2-

FGR Summer

29

Data modelling

Most important aspect of systems development because: Data


system.
Values

is central

to any information

of data may change, basic structure and types of data in organisation remain (fairly) stable.

ISE-Lecture2-

FGR Summer

30

Data modelling
Data

modelling techniques relationship modelling

Entity

Developed

into class diagrams integrating data, methods and behaviour

ISE-Lecture2-

FGR Summer

31

Data modelling: ER Model

ISE-Lecture2-

FGR Summer

32

Process modelling
Developing
alone,

an accurate data model is a key activity but:


it can not represent the way in which the business works do this we need to understand

to

what

tasks

must be undertaken by the business, and they are performed.

how

This

model: records the functional

requirements of the proposed system not the information requirements.

ISE-Lecture2-

FGR Summer

33

Process model: An example

ISE-Lecture2-

FGR Summer

34

Behavioural modelling

Data + Process: Do not provide true representation of an Information System When representing real world systems we need to consider

how values change over time.

ISE-Lecture2-

FGR Summer

35

Behavioural modelling

Data/process models: provide a static view of an information system. In the real-world events occur and these are translated into transactions in our information system

ISE-Lecture2-

FGR Summer

36

Behavioural modelling
The

behavioural (dynamic) aspects of the system are about


What

happens to data as the result of an event in the real world, represented by a transaction in our information system
ISE-Lecture2FGR Summer 37

Behavior model example: State diagram

ISE-Lecture2-

FGR Summer

38

Summary of systems development methodologies


Hundreds exist Many are a variation on a theme A generic methodology has:


A

technical

bit (model) bit (model)

Tells

you what tools and techniques to use

managerial
ISE-Lecture2-

Gives

you a framework (or roadmap to follow)


FGR Summer 39

Development methodology
Its
A

all about cooking

development method is like a recipe, giving guidelines You can follow the recipe and produce a meal just like a top chef
Alternatively,

you can follow the recipe and produce something inedible (even by the dog)!

ISE-Lecture2-

FGR Summer

40

Where weve got to.


Development

rapidly

techniques have changed over the last 15 years

The approach to systems development still continues to evolve as we utilise new technology and software development approaches
Development

are poor tools

approaches for web-based projects

Many

systems developed using system building

ISE-Lecture2-

FGR Summer

41

Development methodology
Evaluation Framework

Methodology

Roadmap

Techniques & Tools

ISE-Lecture2-

FGR Summer

42

Existing methodologies

In 1995 that over 1,000 brand name methodologies existed A Jungle


ISE-Lecture2FGR Summer 43

Existing methodologies

Today
100

probably

less than

methodologies Number of fundamentally different methodologies even smaller

ISE-Lecture2-

FGR Summer

44

Some popular approachs

SSADM

JAD
ISE-Lecture2FGR Summer 45

There is some agreement


The

important is not so much about methodology You need to adapt your recipe to the ingredients

ISE-Lecture2-

FGR Summer

46

The future of methods


Ad

hoc development

No

formalised

methodology used

Experienced

developers use best of approaches/tools/techniques they have previously encountered.

ISE-Lecture2-

FGR Summer

47

The future of methods

Further development in formal method area


O-O

methods and web-based methods continue to be developed Methods using UML toolset are developed Web-based methods?

ISE-Lecture2-

FGR Summer

48

The future of methods


Adaptable

methods
that can be

Methodologies

adapted for different environments


different

to an ad-hoc approach: choice to mixand-match but within a development framework.

ISE-Lecture2-

FGR Summer

49

The future?
External

development
Avison

& Fitzgerald see a move toward outsourcing. not then concerned with development issues software house devises own framework
ISE-Lecture2FGR Summer 50

Organisations

Вам также может понравиться