Slide 1

Systems Analysis and Design

Michael BrydonSummer 2003

Slide 2

Introduction to the CourseCourse structure

Lectures: material from the Dennis textLabs: in-lab assignments, demonstrations, and consulting hoursCourse web site: http://www.bus.sfu.ca/bus362Office hours:

Me: Thursday “open door” after class until 5:30 PMTAs: To Be Announced

Slide 3

Course DeliverablesMajor project: 30%

analysis of a real-world systemAs-is: system description (process and data)To-be: process model, data model, interface mock-up (for computerized components)

done in teamsup to four people (not five)all teams marked the same regardless of numberteamwork assessment at the end of the course

Slide 4

Course DeliverablesAssignments: 20%

nine assignments during the termdone in groups of up to four (not five)

may be same groups as major projectmay be different groups

lab time and supervision is provided for completion of the assignmentseach assignment is due the following week at the start of class

late assignments are not acceptedeach group must register for each assignment using the student information system (see course home page)keep a copy so that we may go over the tricky bits in class

Slide 5

Course DeliverablesMidterm exam: 20%

held in Week 8covers planning and analysis stages

Final exam: 30%closed bookcovers entire course

Slide 6

Blind Design ProjectAs-is model

create a model of the current business processgraphical or semi-graphical

Requirements specificationidentify the high-level requirements for a betterbusiness process

System concept (to-be model)describe the new business processes and any systems used to support the process

Slide 7

An Information SystemObjectives

automateinformate

Building blocksdata (database)automation (programming language)interface (forms, reports, etc.)

Slide 8

Introduction

Chapter 1

Slide 9

Key IdeasMany failed systems were abandoned because analysts tried to build wonderful systems without understanding the organization.The primarily goal is to create value for the organization.

Slide 10

Key IdeasThe systems analyst is a key person analyzing the business, identifying opportunities for improvement, and designing information systems to implement these ideas.It is important to understand and develop through practice the skills needed to successfully design and implement new information systems.

Slide 11

THE SYSTEMS DEVELOPMENT LIFE CYCLE

Slide 12

Major Attributes of the Lifecycle

The project --Moves systematically through phases where each phase has a standard set of outputsProduces project deliverablesUses deliverables in implementationResults in actual information systemUses gradual refinement

Slide 13

Project PhasesPlanning (Why build the system?)Analysis (Who, what when, where will the system be?)Design (How will the system work?)Implementation (System delivery)

Slide 14

Identifying business valueAnalyze feasibilityDevelop work planStaff the projectControl and direct project

Planning

Slide 15

AnalysisInformation gatheringProcess modelingData modeling

Analysis

Slide 16

A “Simple” Process for Making Lunch

Slide 17

Physical designArchitectural designInterface designDatabase and file designProgram design

Design

Slide 18

ConstructionInstallation

Implementation

Slide 19

Processes and DeliverablesProcess Product

Planning

Analysis

Design

Implementation

Project Plan

System Proposal

System Specification

New System and Maintenance Plan

Slide 20

SYSTEM DEVELOPMENT METHODOLOGIES

Slide 21

What Is a Methodology?

A formalized approach or series of stepsExamples

Process-CenteredData-CenteredObject-Oriented

Slide 22

Waterfall Development Method

Slide 23

Pros and Cons of the Waterfall Method

Pros Cons

Identifies systems requirements long before programming begins

Design must be specified on paper before programming begins

Long time between system proposal and delivery of new system

Slide 24

Alternatives to the SDLC

Parallel DevelopmentRapid Application Development (RAD)Phased DevelopmentPrototypingSpiral DevelopmentPackaged Systems

Slide 25

Parallel Development Method

Slide 26

Pros and Cons of Parallel Development

Pros Cons

Reduces ScheduledTime

Less Chance ofRework

Still Uses PaperDocuments

Sub-projects May BeDifficult to Integrate

Slide 27

Rapid Application Development

CASE toolsJAD sessionsFourth generation/visualization programming languagesCode generators

Slide 28

Oracle’s Designer ToolProcess modeling (with swim lanes)

Slide 29

Functional decomposition of processing

Oracle’s Designer Tool

Slide 30

Oracle’s Designer ToolCreate an Entity-Relationship Diagram

Slide 31

Oracle’s Designer ToolSpecify logical and physical details for entities in ERD

Slide 32

Oracle’s Designer ToolGenerate relational database from CASE tool

Slide 33

Three RAD CategoriesPhased development

A series of versionsPrototyping

System prototypingThrow-away prototyping

Design prototyping

Slide 34

How Prototyping Works

Slide 35

Throwaway Prototyping

Slide 36

Criteria for Selecting the Appropriate Methodology

Clear user requirementsFamiliar technologyComplexityReliabilityTime scheduleSchedule visibility

Slide 37

TEAM ROLES AND SKILLS

Slide 38

Information Systems Roles

Business analystSystem analystInfrastructure analystChange management analystProject manager

Slide 39

SummaryThe Systems Development Lifecycleconsists of four stages: Planning, Analysis, Design, and ImplementationThere are five major developmentmethodologies: the waterfall method, the parallel development method, the phased development method, system prototyping and design prototyping.There are five major team roles: business analyst, systems analyst, infrastructure analyst, change management analyst and project manager.