Lecture 1 Welcome Topic 1 MSC228 2012 T1 2012

7/31/2019 Lecture 1 Welcome Topic 1 MSC228 2012 T1 2012

1/24

1

Information Systems Analysisand Design

MSC228

Trimester 1 / 2012

Topic 1

2

The first bit of business info

The University wishes to make you aware of the Emergency EvacuationProcedures that are in place for your safety.

Please look around and familiarize yourself with the exits in this room and foreach new venue in which you attend classes. You should also familiariseyourself with the building's emergency exits and assembly areas which can befound on Fire Emergency Floor Plans placed in the hallway of all buildings.

In the unlikely event of an evacuation, you will hear a continuous loud beepingtone. On this alert signal you should prepare yourself to evacuate the building,

If you hear a continuous two tone siren sound please evacuate in an orderlyfashion to the assembly areas. All building occupants must evacuate on thisevacuation signal,

Remember not to use lifts during evacuation.

Please follow the instructions given by Emergency Wardens, Security staff orEmergency Services personnel.

At the end of the evacuation, you will be advised when it is safe to return to thebuilding.

2

3

Welcome! Your MSC228 teaching staff:Unit Chair

Burwood Campus and Off-Campus

Co-Lecturing and Teaching

Ms Merete [email protected]

Dr. David Wilde

Burwood Campus

Co-Lecturing and Teaching

[email protected]

Mr Graham Bignall

Geelong [email protected]
http://c/Users/Merete/Desktop/MSC228%20T1%202012/[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]://c/Users/Merete/Desktop/MSC228%20T1%202012/[email protected]


2/24

4

Learning materialsPrescribed textbook

Dennis, A., Wixom, B.H. & Roth, R. 2009Systems Analysis and Design,

4th edn, John Wiley & Sons Inc $129.95

Other materials

2012 Study Guide $13 and DSO

On DSO

2012 Lecture notes and tutorials

2012 Assignment details

Readings as advised

5

Learning materialsAdditional resourcesThere are many other good books that are available in the library, eg:

Avison, D. E and Guy Fitzgerald, 2003, Information systems development:methodologies, techniques, and tools, London : McGraw-Hill, 3rd ed

Brown, David, 2002, Introduction to Object-Oriented Analysis: Objects and UML in PlainEnglish, 2nd Edition, John Wiley

Hoffer, J.A., George J.F. & Valacich J.S. 2002, Modern Systems Analysis and Design 3rdedn Prentice Hall, Upper Saddle River, NJ.

Kendall, K. E. & Kendall, J. E. 2004, Systems Analysis and Design, 6th edn, Prentice

Hall, Englewood Cliffs, NJ.

Satzinger J.W., Jackson R.B. & Burd S .D. 2004, Systems Analysis and Design in aChanging World, 3rd edn, Course Technology

6

StructureLecture (2 hour session pw)

Look at the way in which information systems are planned,analysed, designed and implemented.

Tutorial (1 hour session pw)

Examine and discuss analysis and design issues.

Deakin Studies Online (DSO)

Online delivery of most of the learning materials (except thetextbook/software)

Most of the communication for this unit is carried out via DSO


3/24

7

Class Times and Locations

On campus students

Burwood Lecture: Tuesdays 15 17 LT3

Tutorials: Mondays 10 and 11; Tuesdays 12

Geelong Lecture: Thursdays 15 17 LT ka5.332

Tutorials: Thursdays 12 and 14

8

DSO (D2L)

Logging in to DSO

Browser; Use Microsoft Internet Explorer 5.0 or higher

Mozilla

http://www.deakin.edu.au/current-students/index.php

Remember to log out when you are finished

9

Assessment

Assignment 1 Individual 15% Due 2/4/2012

Assignment 2 Individual 35% Due 21/5/2012

Exam 50% Hurdle

Getting help

DSO discussions, Tutorials, Your lecturer
http://www.deakin.edu.au/current-students/index.phphttp://www.deakin.edu.au/current-students/index.phphttp://www.deakin.edu.au/current-students/index.phphttp://www.deakin.edu.au/current-students/index.phphttp://www.deakin.edu.au/current-students/index.php


4/24

10

What to avoid

Plagiarismis the copying of another persons ideas orexpressions without appropriate acknowledgment andpresenting these ideas or forms of expression as your own.

It includes not only written works such as books or journals butdata or images that may be presented in tables, diagrams,designs, plans, photographs, film, music, formulae, web sitesand computer programs.

Plagiarism also includes the use of the work of lecturers or otherstudents as your own without acknowledgment.

At Deakin, there are heavy penalties for plagiarism, so ensurethat your work is original.

Also make sure that your own work is not plagiarised by others!

10

11

Unit Plan

1. Introduction to Systems

Analysis and Design

2. Project Initiation and

Feasibility Analysis

3. Requirements Gathering

4. Techniques: OO1 Use Case

5. Techniques: OO2

Structural/Behavioural

6. Techniques: Structured 1

7. Techniques: Structured 2

8. Techniques: Other

9. Moving to design

10. Human Computer

Interaction

11. Revision

11

12

Systems Analysis and Design

MSC228

Topic 1


5/24

13

(Professor) Peter Juliff

Commercial computer systems designed & developed for:

British Petroleum, ASEA, Parks Australia, Thorn Industries,Trade Union Clinic, Goulburn Valley Canneries, Health Computing Services,NCR, Victoria Institute of Colleges, Victorian Railways,W.A Deutscher, Local Authorities Superannuation Board,Deakin University, Outer Eastern Municipalities Association

Programmed in languages from Burroughs and ICL assemblers through COBOL toVisual Basic

Implemented on Burroughs, Honeywell, ICL and DEC mainframes and Windows-based PC systems.

Introduction

14

What am I doing here ?

1. To put the current practice of systems analysis and design

into some perspective

2. To draw attention to the problems encountered in

implementing computer-based systems

3. To inject a little been there and done that into the exercise

. . . and why is any of this important anyway?

15

Over a period of 40 years . . . .What has changed?

Hardware technology

Data organisation & access

Move from batch to online

processing of data

The importance of human /

computer interaction

The emergence of rapid

development methodologies

through the prototyping capacity

of software

The expectations of users !!!!!

What hasnt changed?

The difficulty of defining system

requirements

The conflict between basing design

on data vs procedure

The (unrealistic) expectation that

users know what they want

The necessity for someone to inject

imagination into the design

The need to have users take

ownership of the system


6/24

16

Systems

Information Systems

Systems Development Life Cycle

Methodologies

The Project Team

Overview

17

Job description of current Business/System Analyst

XXXXXX

We will re-visit this later in the lecture.

18

Systems


7/24

19

Systems

Natural

physical e.g. stellar, geological.

living e.g. animal, plant.

Man-made

Examples please?!

social

Facebook, dance classes

transportation

Tram, train, bus, air etc.

communication

Telephone, internet

information etc.

20

Systems

A system is: an interrelated set ofcomponents that are viewed as a whole.(Teague & Pidgeon,1985)

Each system has a purpose (or goal) and

must work towards that purpose.

Example

Transportation system goal? Many and varied depending on perspective, e.g.

Making money

A way to get around Political

21

Systems

Systems achieve their purpose by accepting inputs, andproducing outputs, via an organised transformation process.

To solve business problems it is essential to identify theorganisation's goals.

But how do we measure goals?


8/24

22

. . . and speaking of goals . . . .

Systems have many goals, many definitions of a user and many conflicting

requirements : e.g.

Banks UniversitiesCustomers Students

Staff Administration staff

Shareholders Academic staff

Govt regulators Govt regulators

In each of these examples, the requirements of one set of users may bediametrically opposed to those of another set.

. . . so - who do you consult to determine the system requirements?

- who are you working for? (Live system vs Unit assignment !!!)

- who are you trying to satisfy?

23

Systems

SystemModelsproduce a simple description of the area understudy. To develop the model we use abstraction and selectivity.

Models are used because it is impossible or

impracticalto deal with the system directly.

Graphical models strongly aid the

imaging or visualisation of a system

24

Information Systems


9/24

25

Data vs. Information

Data is represented as discrete entities e.g. acustomers name, details on an invoice, the date on a

receipt

Information is data transformed into something of

meaning

e.g. sales of a product over a week or a month; a list

of people who owe us money.

It is used to assist people in making informed

decisions.

Information

26

Abacus

Ledger books (or scrolls)

Counting Boards

EDP systems (batch systems)

MIS (shared databases - online systems)

DSS (decision support systems)

EIS (executive information systems)

Examples of Information Systems

27

Information Systems

A collection of components that work together to provide

information to help in the operations and management of

an organization. Nickerson (2001, p4)

Its purpose is to get good information to the

right people at the time when they need it

the right time.


10/24

28

New Information Systems

Information systems projects are usually triggered by

Problems Payroll system not working effectively

Opportunities Selling products online

Directives New tax laws

29

Systems Development Life Cycle (SDLC)

30

Systems Development Life Cycle

1. PlanningWhy build the system?

2. AnalysisWho, what, when, where will the system be?

3. DesignHow will the system work?

4. ImplementationSystem delivery

Most systems analysis methodologies follow the basicsteps of the SDLC


11/24


12/24

34

Analysis

Information gathering

Models created

2. Analysis

35

Information gathering

From whom?

. . . I f youre relying on the current users, think again

- they arent aware of what may be possible

- they arent even completely aware of the current system

What to gather?

. . . What will be carried into the new system?

- the data? Surely, but + or the status quo?

- the procedures? Can we not improve/eliminate these?

Who provides the imagination?

36

Models created

What to model? Current system

Data - useful if its to be carried forward

Procedures - useless unless theyre to be carried forward

What is the point of being an expert on a system about to be junked?

Immersion in the current system is likely to ensure its replication

New system Start from scratch when developing procedures

Is there a way to produce the result by a different means than is currently used?

Can more information be produced from the data than is currently feasible?

. . . let me give you an example


13/24

37

Physical design

Architectural design

Interface design

Database and file design

Program design

3. Design

38

Construction

Installation

Maintenance

4. Implementation

39

Processes and Deliverables

Process Product

Planning

Analysis

Design

Implementation

Project Plan

System Proposal

SystemSpecification

New System andMaintenance Plan


14/24

40

Methodologies

41

Methodologies

A formalized approach or series of steps

Aim is to provide a guide which if followed will lead to a successfulinformation system

Building a house without a plan is unlikely to get you your dreamhouse

Writing code without a well-thought-out system request may work forsmall programs, but rarely works for large ones.

42

The Need for a Methodology

Specific detailed ways of creating systems, that have been atleast partially tested and documented, are termed

METHODOLOGIES


15/24

43

The Need for a Methodology

With the growth of the use of computers during the

1950s and 1960s it was recognised that:

The role of the systems analyst was important

There was a need for integrated IS development

To facilitate IS development a detailed IS developmentmethodology was desirable

The Nike methodology - Just Do It

The IBM methodology we have the solution already,just amend your problem to fit it.

44

What is a Methodology?

A collection ofprocedures, techniques, tools anddocumentationaids which will help the systems developers in their efforts toimplement a new information system.

A methodology will consist ofphases, themselves consisting ofsub-phases, which will guide the systems developer in their choice of thetechniques that might be appropriate at each stage of the project andalso help them plan, manage, control and evaluate information system

projectsAvison and Fitzgerald (2003)

45

What is a Methodology? Procedure A set of activities to be carried out to achieve a desired outcome

Technique A way of doing a particular activity in the information systems developmentprocess

Tool An aid, often computer-based, that enables some of the procedures or certaintechniques to be carried out automatically or semi-automatically

Documentation Aid Particular notations or ways of presenting data that captureaspects of the system to be implemented that are deemed important

Phase/Sub-Phase A logical grouping/sub-grouping of procedures carried out at aparticular stage of the system development


16/24

46

What is a Methodology? The Philosophical View

Avison and Fitzgerald argue also that a methodology should be based upona particular philosophical view

This distinguishes a methodology from a method (a recipe)

It shapes what is emphasized, and assumptions made

Examples of a Philosophical View:

People are important

One should take a Scientific approach

One should aim to automate the development work

47

Methodologies

What is relevant is that

the requirements of a batch mode payroll system, or aninformation retrieval system, or an on-line auction systemare dramatically different

the wants, needs, views and levels of knowledge and skillsof the many people and organizations touched by IS areradically different

It would be surprising if a single methodology used to develop

systems for all of these scopes and contexts was equallysuccessful.

48

Structured Design

Rapid Application Design

Object-oriented analysis and design

.

many others including:

SSM and Multiview

Methodologies


17/24

49

. . . Hold it right there !!!

What are the methodologies producing? Documentation vs Information

Documentation without information is a waste of everybodys time

Information for whom? The users? - can they understand it?

The developers? - will they use it?

The maintenance techos? - will it explain what was done, and why?

Can it drive the database definition and/or the software?

50

Structured Design

Projects move methodically from one step to the nextstep

Generally, a step (or phase) is finished before the nextone begins

Uses modelling tools to show business processes andbusiness data

51

Waterfall Development Method

Fig 1-2, p8, Dennis et al

With waterfall development- based methodologies, the analysts and usersproceed sequentially from one phase to the next.


18/24

52

Structured Design Benefits

Structure provides a good aid to developers to improve chances of success

Usually have to complete one stage before moving on

Diagramming relatively easy to understand, i.e. not programming based

The system requirements are identified long before programming begins.

Drawbacks

Hard to go backwards in process

Less creativity

Can be time consuming

53

Rapid Application Development (RAD)

RAD-based methodologies adjust the SDLC phases to get some part of systemdeveloped quickly and into the hands of the users.

Most RAD-based methodologies recommend that analysts use special techniques andcomputer tools to speed up the analysis, design, and implementation phases, such asCASE (computer-aided software engineering) tools.

Phased (series of versions) or prototyping (all stages performed concurrently)

Comments Effective to create systems quickly e.g. web based systems

Changes can be made easily Criticized for lacking methodological rigor

Possibly the greatest single contribution made by the evolution of modern software

54

How Prototyping Works

Fig 1-4, p11, Dennis et al


19/24

55

Object-Oriented Analysis and Design

Attempts to balance the emphasis on data and process by combining both (data and

procedures) in models

Interaction occurs via messages (that pass information) between the objects

A standard modelling technique is the Unified Modeling Language (UML)

..designed to help the participants in software development efforts build models that willenable the team to:

- visualize the system,

- specify the structure and behaviour of that system,

- construct the system, and

- document the decisions along the way.

(Scott 2001, p1)

56

Object-Oriented Analysis and Design

Use-case driven

Captures the main functionality of the system from a users perspective

Architecture Centric 3 different views (functional, static, dynamic)

Iterative and Incremental

processes are repeated and gradually refined

This we will revisit in weeks 4 and 5.

57

Benefits

Objects can be designed independently giving designers moreflexibility in design

Systems can be more flexible

More rapid and less expensive system development

Another way of improving productivity is through libraries ofreusable objects


20/24

58

Process ModellingDFDs

Context diagram for a fast food ordering system

59

SSM Rich picture Model

60

Use Case Diagram


21/24

61

The Project Team

62

Project Team

System Analysts

System Designers

Project Manager

Programmers

Technical writers

Other stakeholders; System owners, System users, ITvendors and consultants

63

Systems Analyst

The systems analystis a key person analyzing thebusiness, identifying opportunities for improvement,and designing information systems to implementthese ideas.

It is important to understand and develop throughpractice the skills needed to successfully design andimplement new information systems.


22/24

64

Job description of current Business/System AnalystXXXXXX

65

Systems Analyst

Whitten et al, 2000, Fig 1.4

66

Skills Required by Systems Analysts

Interpersonal communication/relations skills

Character and ethics

Flexibility and adaptability

Systems analysis and design skills

Working knowledge of information technology

General business knowledge

Problem-solving skills


23/24

67

Summary

68

Summary

Systems theory and how it relates to Information systems

Information Systems project triggers

Goal of System Development

69

Summary

The Systems Development Lifecycle:1. Planning2. Analysis3. Design4. Implementat ion

Major development methodologies: Structured design RAD Object-Oriented approach

Major development team roles, responsibilities and skillrequirements


24/24

70

What to do now

71

What to do now

Log into DSO, read the Welcome message and explore theenvironment

Download a copy of the Assignment

Purchase the text book

72

Reading - Further Study

To complement this introduction to Topic 1 students shouldread Topic 1 in the Study Guide, and the sections of the textreferred to in that study guide.

Prepare for next weeks tutorial- download the Tutorial Questions and make sure you haveread the material in preparation for next weeks classes.

Test your own understanding of Topic 1 by completing theReview Questions as listed in the study guide

Lecture 1 Welcome Topic 1 MSC228 2012 T1 2012

Documents

Transcript of Lecture 1 Welcome Topic 1 MSC228 2012 T1 2012