BIS310: Structured Analysis and Design

Introduction andSystems Planning

Week 1

Outline

• Introduction to the Information Systems Analysis and Design

• Systems Development Environment• Determining Requirements• SDLC Overview• Identifying and Selecting IS Development Projects• Initiating and Planning System Development

Projects

Introduction

• Information Systems Analysis and Design– Complex process whereby computer-based

information systems are developed and maintained

• Application Software– Result of systems analysis and design– Designed to support specific organizational

functions or processes

Data and Processes

• Three key components of an information system– Data– Data Flows– Processing Logic

• Data vs. Information– Data

• Raw facts

– Information• Derived from data• Organized in a manner that humans can understand.

Organizational Responsibilities in Systems Development

• Systems Analysts work in teams– Project Based– Includes

• IS Manager• Programmers• Users• Other specialists

– Characteristics of Successful Teams• Diversity of backgrounds• Tolerance of diversity• Clear and complete communication• Trust• Mutual Respect• Reward structure that promotes shared responsibility

Skills of a Successful Systems Analyst• Analytical

– Understanding of organizations– Problem solving skills– System thinking

• Ability to see organizations and information systems as systems

• Technical– Understanding of potential and limitations of technology

• Management– Ability to manage projects, resources, risk and change

• Interpersonal– Effective written and oral communication skills

Approaches to Development

• Joint Application Design (JAD)– Users, Managers and Analysts work together for

several days– System requirements are reviewed– Structured meetings

• Prototyping– Building a scaled-down working version of the system

• Rapid Application Development (RAD)– Utilizes prototyping to delay producing system design

until after user requirements are clear

Systems Development Life Cycle and Methodologies

• Methodology: the process used to develop information systems.

• A systems development life cycle (SDLC) is a logical process by which systems analysts, software engineers, programmers, and end-users build information systems and computer applications to solve business problems and needs.

Systems Development Life Cycle

• Series of steps used to manage the phases of development for an information system

• Consists of five phases:– Planning– Analysis– Design– Implementation– Maintenance

1

Survey Phase

2

Study Phase

3

Definition Phase

4

Targeting Phase

6

Design Phase

7

Construction Phase

5

Purchasing Phase

(if necessary)

8

Delivery Phase

System Users

System Owners

Information Technology

Vendors

Unplanned System Problem

Planned System Project

Project and System Scope

System Objectives

Business Requirements

Technology Requirements

Design Requirements

Technology Integration

Requirements

Design Specifications

Prototypes

Operational System

Business Requirements

Business Requirements

Request for

Proposals

Proposals

Production System

ConfigurationPhase

Problems, opportunities, or directives

ProblemsProblems are undesirable situations that prevent the organization from fully achieving its purpose, goals, and objectives.

An opportunityopportunity is a chance to improve the organization even in the absence of specific problems.

A directivedirective is a new requirement that's imposed by management, government, or some external influence.

Identifying and Selecting IS Development Projects

• Sources of projects– Management and business units– Managers who want to make a system more efficient or less costly– Formal planning groups

• Top-Down Identification– Senior management or steering committee– Focus is on global needs of organization

• Bottom-up Identification– Business unit or IS group– Don’t reflect overall goals of the organization

Corporate and Information Systems Planning

• Need for planning– Improperly planned projects result in systems

that cannot be shared across an organization– As business processes change, lack of

integration will hamper strategy and business process changes

Corporate and Information Systems Planning

• Corporate Strategic Planning– Process of developing and refining models of

the current and future enterprise as well as a transition strategy

– Three-step process• Current Enterprise

• Future Enterprise

• Strategic Plan (Competitive Strategy)

Corporate and Information Systems Planning

• Information Systems Planning (ISP)– An orderly means of assessing the information needs of

an organization and defining the systems, databases and technologies that will best satisfy those needs

– Three key activities:• Describe the Current Situation

• Describe the Target (or Future) Situation

• Develop a Transition Plan and Strategy

Corporate and Information Systems Planning

• ISP must look at information systems and technologies in terms of how they help the business achieve its objectives defined during corporate strategic planning.

• Parallel activities of CSP and ISP

Initiating and Planning System Development Projects

• Project Initiation– Establishment of project team– Development of relationship with customer– Project Initiation Plan– Establishment of Management Procedures– Establishment of Project Workbook and Project

Management Environment

• Project Planning = Survey Phase– Defining clear, discrete activities and the work needed

to complete each activity

Initiating and Planning System Development Projects

• Deliverables and Outcomes– Baseline Project Plan (BPP)

• Scope

• Benefits

• Costs

• Risks

• Resources

– Statement of Work (SOW)• Describes deliverables

• Outlines work needed to be performed

Group Project

• Check Group Assignment– Go to “Communication” -> “Group” page– If you don’t see your name in the group section,

let the instructor know ASAP– Try communicating with other members of the

group– Check the first group exercise posted in the

“Assignment” Area.