Scribd
Upload
76 views20 pages

Systems Analysis and Design: Michael Brydon Summer 2003

The document provides an overview of a Systems Analysis and Design course. It discusses the course structure, deliverables including a major project, assignments, and exams. It also summarizes key ideas around systems analysis and the systems development lifecycle including planning, analysis, design, and implementation phases. Different systems development methodologies like waterfall, rapid application development, and prototyping are introduced. Finally, it outlines different team roles in systems development projects.

Uploaded by

Retariaty Anugrah Kumoro
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
76 views20 pages

Systems Analysis and Design: Michael Brydon Summer 2003

The document provides an overview of a Systems Analysis and Design course. It discusses the course structure, deliverables including a major project, assignments, and exams. It also summarizes key ideas around systems analysis and the systems development lifecycle including planning, analysis, design, and implementation phases. Different systems development methodologies like waterfall, rapid application development, and prototyping are introduced. Finally, it outlines different team roles in systems development projects.

Uploaded by

Retariaty Anugrah Kumoro
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 20

Systems Analysis and Design

Michael Brydon Summer 2003

Slide 1

Introduction to the Course


Course structure
Lectures: material from the Dennis text Labs: in-lab assignments, demonstrations, and consulting hours Course web site: http://www.bus.sfu.ca/bus362 Office hours:
Me: Thursday open door after class until 5:30 PM TAs: To Be Announced
Slide 2

Course Deliverables
Major project: 30%
analysis of a real-world system
As-is: system description (process and data) To-be: process model, data model, interface mock-up (for computerized components)

done in teams
up to four people (not five) all teams marked the same regardless of number teamwork assessment at the end of the course
Slide 3

Course Deliverables
Assignments: 20%
nine assignments during the term done in groups of up to four (not five)
may be same groups as major project may be different groups

lab time and supervision is provided for completion of the assignments each assignment is due the following week at the start of class
late assignments are not accepted each 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 4

Course Deliverables
Midterm exam: 20%
held in Week 8 covers planning and analysis stages

Final exam: 30%


closed book covers entire course

Slide 5

Blind Design Project


As-is model
create a model of the current business process graphical or semi-graphical

Requirements specification
identify the high-level requirements for a better business process

System concept (to-be model)


describe the new business processes and any systems used to support the process
Slide 6

An Information System
Objectives
automate informate

Building blocks
data (database) automation (programming language) interface (forms, reports, etc.)
Slide 7

Introduction
Chapter 1

Slide 8

Key Ideas
Many 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 9

Key Ideas
The 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 10

THE SYSTEMS DEVELOPMENT LIFE CYCLE

Slide 11

Major Attributes of the Lifecycle The project -Moves systematically through phases where each phase has a standard set of outputs Produces project deliverables Uses deliverables in implementation Results in actual information system Uses gradual refinement
Slide 12

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

Planning
Identifying business value Analyze feasibility Develop work plan Staff the project Control and direct project

Slide 14

Analysis
Analysis Information gathering Process modeling Data modeling

Slide 15

A Simple Process for Making Lunch

Slide 16

Design
Physical design Architectural design Interface design Database and file design Program design

Slide 17

Implementation
Construction Installation

Slide 18

Processes and Deliverables


Process Planning Analysis Design Implementation Product Project Plan System Proposal System Specification New System and Maintenance Plan

Slide 19

SYSTEM DEVELOPMENT METHODOLOGIES

Slide 20

What Is a Methodology?
A formalized approach or series of steps Examples
Process-Centered Data-Centered Object-Oriented

Slide 21

Waterfall Development Method

Slide 22

Pros and Cons of the Waterfall Method


Pros Identifies systems requirements long before programming begins Cons Design must be specified on paper before programming begins Long time between system proposal and delivery of new system

Slide 23

Alternatives to the SDLC


Parallel Development Rapid Application Development (RAD) Phased Development Prototyping Spiral Development Packaged Systems
Slide 24

Parallel Development Method

Slide 25

Pros and Cons of Parallel Development


Pros Reduces Scheduled Time Less Chance of Rework Cons Still Uses Paper Documents Sub-projects May Be Difficult to Integrate

Slide 26

Rapid Application Development


CASE tools JAD sessions Fourth generation/visualization programming languages Code generators

Slide 27

Oracles Designer Tool


Process modeling (with swim lanes)

Slide 28

Oracles Designer Tool


Functional decomposition of processing

Slide 29

Oracles Designer Tool


Create an EntityRelationship Diagram

Slide 30

Oracles Designer Tool


Specify logical and physical details for entities in ERD

Slide 31

Oracles Designer Tool


Generate relational database from CASE tool

Slide 32

Three RAD Categories


Phased development
A series of versions

Prototyping
System prototyping

Throw-away prototyping
Design prototyping
Slide 33

How Prototyping Works

Slide 34

Throwaway Prototyping

Slide 35

Criteria for Selecting the Appropriate Methodology


Clear user requirements Familiar technology Complexity Reliability Time schedule Schedule visibility
Slide 36

TEAM ROLES AND SKILLS

Slide 37

Information Systems Roles


Business analyst System analyst Infrastructure analyst Change management analyst Project manager

Slide 38

Summary
The Systems Development Lifecycle consists of four stages: Planning, Analysis, Design, and Implementation There are five major development methodologies: 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.
Slide 39

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy