Introducing Systems Analysis

Introduction
DCS 310 Systems Analysis
Based on material I.T. Hawryszkiewycz
DCS 310 Systems Analysis Introduction Slide 1

What is an Information System?

essential concepts

What is Systems Analysis?

developing systems development processes

Course overview
DCS 310 Systems Analysis Introduction Slide 2

What is an Information System? A system that processes the information needed by people in an organisation

Information Systems

A computer based information system is a system that uses a computer

DCS 310 Systems Analysis Introduction Slide 3 DCS 310 Systems Analysis Introduction Slide 4

DCS 310 Systems Analysis Introduction

Slide 5

DCS 310 Systems Analysis Introduction

Slide 6

Uses of Information Systems

Systems are Built for a Purpose Systems are designed for a purpose Where does the purpose come from?
the users of the system systems allow people to achieve organisational objectives: business goals

Business application
meeting customer orders sending out invoices

Making decisions Everyday activities

writing a letter sending a message

Distinguish
behaviour of a system purpose of a system
Slide 7 DCS 310 Systems Analysis Introduction Slide 8

Control systems
DCS 310 Systems Analysis Introduction

An Abstract View of a System

behaviour
System Boundary

Systems and Sub-Systems

input
Sub-system Sub-system Sub-system

System

System Environment

output purpose, or business goal

Slide 9

System Environment

communication
Slide 10

DCS 310 Systems Analysis Introduction

DCS 310 Systems Analysis Introduction

Hierarchy of Systems
Each system is a subsystem of other systems
the gear is a component

An Information System and Users

People Computer system Communication Documents

Engine

System properties are emergent

bolt is strong engine is powerful car is fast

Usefulness is an emergent property of an IS

DCS 310 Systems Analysis Introduction Slide 11 DCS 310 Systems Analysis Introduction Slide 12

Organisations and Data

Organisations use and produce data (or information)
data used to control data used to to decide e.g. accounts, plans, designs, procedures, staff records, letters, price lists

Information Systems Recap Systems are made up of sub-systems Systems are designed for a purpose
systems have users achieving tasks

Systems operate in an environment

INVOICE $1,000,000

A database contains information

logical/physical organisation of data
DCS 310 Systems Analysis Introduction Slide 13

the environment for an Information Systems is typically an organisation

Systems process data

DCS 310 Systems Analysis Introduction Slide 14

Questions What word describes both the:

parts of a system, and environment of a system?

Developing Systems

Give examples of information systems you use or containing information about you.

DCS 310 Systems Analysis Introduction

Slide 15

DCS 310 Systems Analysis Introduction

Slide 16

Building a House
Family
Architect
Pro b lem sa nd

Building a House
describes what they want: requirements

Descriptions Ideas
ch an ge s

Dream House

Architect
prepares a plan

Builder
builds according to the plan

The plan is critical

Plan
DCS 310 Systems Analysis Introduction

Building to Plan

House

family know what they will get builder knows what to build
DCS 310 Systems Analysis Introduction Slide 18

Slide 17

THE SAME IN COMPUTING, BUT ...

System Analyst / Designer Description Ideas

Specifications Specifications describe exactly what a system must accomplish A specification is often a plan or model of the required system Concept of a specification is not new
critical part of engineering of any system

Dream System Initial concept

What do these look this?

Plan/Specification Software Engineer
DCS 310 Systems Analysis Introduction

Actual System
Slide 19 DCS 310 Systems Analysis Introduction Slide 20

Analysis Process
System Analyst

System Lifecycle
Someone has an idea for a new system. The idea is analysed and refined. Alternatives are evaluated. A specification is prepared.

What we really need?

Plan/Specification

Gather the requirements Analyse the requirements Prepare a specification

Slide 21

Concept

Analysis
The specification is passed to a designer. Queries are raised and clarifications given. Some function are too expensive and are simplified or dropped.
DCS 310 Systems Analysis Introduction

Design

DCS 310 Systems Analysis Introduction

Slide 22

Information System Models

Specifications include models
abstract: some details are ignored decomposition

Example Model: Class Diagram

Customer
name address
1

Class Association
1

Models of Information Systems

Use cases: model system use Objects: model data & function Data flows: model flow of information the house plan is a model
places

*
Order * number stock_item
delivers

Delivery date
route
Slide 24

DCS 310 Systems Analysis Introduction

Slide 23

DCS 310 Systems Analysis Introduction

The Systems Analyst

USER Has requirements SYSTEM That satisfies user requirements

Work of the Analyst Develop new systems

gather / analyse / specify

What does the user really need?

DATA PROCESS To find requirements and build system
DCS 310 Systems Analysis Introduction

Change existing systems

new or changes requirements conversions (or re-engineering) to alternate systems or equipment

The information needed in the system

Always a change, really!

DCS 310 Systems Analysis Introduction Slide 26

Slide 25

Skills Needed by Analysts Communication skills Analytical skills Understanding

businesses I.S. systems

Information Systems Department Development

evaluates new proposals assists users to develop systems allocates personnel to analyze and develop systems

Creativity and imagination How does this compare to a programmer?

DCS 310 Systems Analysis Introduction Slide 27

Manages and maintains

manages the system when operational supports equipment and network
DCS 310 Systems Analysis Introduction Slide 28

Questions How do you find out:

how a system is behaves? what purpose a system has?

System Development Recap Analysis process

gather / analyse / specify

Specification or plan
derived from the users requirements basis for design and implementation

Models
abstract views of the system, used in specification (or design)
DCS 310 Systems Analysis Introduction Slide 29 DCS 310 Systems Analysis Introduction Slide 30

System Development Recap System Analyst

discovers and understand the users requirements needs communication skills, business and technical understanding

Development Processes

DCS 310 Systems Analysis Introduction

Slide 31

DCS 310 Systems Analysis Introduction

Slide 32

Processes
The way we do things More formally:
A pattern of related activities to achieve a defined goal

IS Development Processes Methodologies

what steps are used in analysis?

Productivity
what activities are most worthwhile? how are tools used?

IS Development:

Activities carried out to: ! identify what is needed ! build a system to do it

DCS 310 Systems Analysis Introduction Slide 33

Achieving quality
how do we ensure that a system satisfies it users?
DCS 310 Systems Analysis Introduction Slide 34

Business Processes
Processes used by business organisations
e.g. buying/selling a house e.g. employing staff

Course Overview
See the course webpage for more information
Slide 35 DCS 310 Systems Analysis Introduction Slide 36

I.T. Systems support business processes

DCS 310 Systems Analysis Introduction

Course Aims

Course Topics
1. 2. 3. 4. 5. 6. 7. Requirements Capture Use cases Object modelling Sequence diagrams State charts Activity Diagrams Development Method
Slide 38

I expect you to be able to:

Apply systems analysis techniques
practical work with small scale examples

Use and compare analysis methodologies,

object-oriented analysis (UML)

Understand limitations of main methodologies

DCS 310 Systems Analysis Introduction

Slide 37

DCS 310 Systems Analysis Introduction

Course Components Lectures

2 hours Thursday

Software Engineering
The course is complementary to Software Engineering (DCS-235)
SA covers early stages of the development lifecycle SE covers design, implementation, testing,

Examples
review during lectures

Both courses use UML, especially Class Diagrams

but, beware, do not confuse analysis with design

Course work
2 marked assignments, 20%

Both courses use Together

available in the ITL can be used for exercises and course work

Exam, 80%
DCS 310 Systems Analysis Introduction Slide 39

DCS 310 Systems Analysis Introduction

Slide 40

Groups - Coursework Coursework in groups of about 3 Students doing SE should group with others in the same SE group

Course Books
Object-Oriented Systems Analysis and Design, Bennett et al (2nd edition)
chapters 1-3: background chapters 4-11: OO analysis chapters 21, 22: management issues

Plus material on structured method, from

e.g. Modern Structured Analysis, Yourdon (in library, also related book online) e.g. Introduction to Systems Analysis and Design, 5e, Hawryszkiewycz (in library)
DCS 310 Systems Analysis Introduction Slide 41 DCS 310 Systems Analysis Introduction Slide 42

Summary Systems analysis: the process of

discovering and analysing the requirements preparing a specification

Exercises and course works are key part of the learning on this course Read Bennett chapters 1 3
DCS 310 Systems Analysis Introduction Slide 43