Vous êtes sur la page 1sur 24

MODULE 2

SYSTEMS ANALYSIS AND DESIGN LIFE CYCLE Contents


2.1 Systems Analysis and Design life Cycle: Requirements determination, requirements specifications 2.2 Feasibility analysis, final specifications, hardware and software study, system design, system implementation, system evaluation, system modification. 2.3 Role of systems analyst, attributes of system analyst, tools used in system analysis
Systems Analysis And Design

V. Rajaraman

MOTIVATION Designing Information system for an organization is a very complex job. Students should know how to logically divide a complex job into smaller manageable steps. Each step must have a logical beginning and end and must be self contained.

System Analysis And Design

V. Rajaraman

1 of 23

MOTIVATION

Division of large jobs into logical steps will Enable one to assess progress at the end of each step

Steps may be assigned to persons with specialized competance Allocation of human and financial resources appropriate for each step can be planned

System Analysis And Design

V. Rajaraman

2 of 23

LEARNING GOALS 1. Nine Steps in designing Information Systems. 2. Tasks performed in each step. 3. Nature of tasks performed by Systems Analysts. 4. The attributes of Systems Analysts. 5. The tools used by Systems Analysts.

System Analysis And Design

V. Rajaraman

3 of 23

LIFE CYCLE OF SYSTEMS ANALYSIS AND DESIGN


Steps involved in Analysis and Design

1. 2. 3. 4. 5. 6. 7. 8. 9.
2.1.1

Requirements Determinations Requirements Specifications Feasibility Analysis Final Specifications Hardware Study System Design System Implementation System Evaluation System Modification
System Analysis And Design

V. Rajaraman

4 of 23

LIFE CYCLE OF SYSTEMS ANALYSIS AND DESIGN


Step 1 : Requirements Determination

Arrived at by a consensus among managers Priorities among applications determined Pick high priority applications.

2.1.2

System Analysis And Design

V. Rajaraman

5 of 23

LIFE CYCLE OF SYSTEMS ANALYSIS AND DESIGN


Step 2 : Requirements Specification

Known as System Requirements Specification (SRS) Understand the existing System Applications where a system is required are listed Arrive at the specifications of the users Requirements after discussions with the user A system may encompass several applications
2.1.3
System Analysis And Design

V. Rajaraman

6 of 23

LIFE CYCLE OF SYSTEMS ANALYSIS AND DESIGN


Step 3 : Feasibility Analysis Formulate Goals of the system and quantify goals
Find alternative methods of meeting the goals For each alternative assess resources needed - Human Resources - Time and Money - Equipment needed Assess cost of each alternative Find the best alternative method subject to resource constraints

2.2.1

System Analysis And Design

V. Rajaraman

7 of 23

LIFE CYCLE OF SYSTEMS ANALYSIS AND DESIGN


Step 4 : Final Specifications

Specifications would state what the system would achieve. Specification drawn up are improved for implementation. SRS written- given to user and agreement reached
2.2.2
System Analysis And Design

V. Rajaraman

8 of 23

LIFE CYCLE OF SYSTEMS ANALYSIS AND DESIGN


Step 5 : Hardware Study

Determine Hardware and Software required to execute the application. Determine Response time,Volume of data to be processed, Frequency of reports etc & then pick the hardware.

2.2.3

System Analysis And Design

V. Rajaraman

9 of 23

LIFE CYCLE OF SYSTEMS ANALYSIS AND DESIGN


Step 6 : System Design

Logical Design of the System Objects Identified Database Designed Program Specification drawn up Implementation Plan Drawn up Test Plan
System Analysis And Design

2.2.4

V. Rajaraman

10 of 23

LIFE CYCLE OF SYSTEMS ANALYSIS AND DESIGN


Step 7 : System Implementation

Write Programs Create Database Document System Train Users Trial run of the system

Test and Accept

2.2.5

System Analysis And Design

V. Rajaraman

11 of 23

LIFE CYCLE OF SYSTEMS ANALYSIS AND DESIGN


Step 8 : System evaluation

Find out from Users whether the System meets specified requirements. List areas of dissatisfaction and find reasons Suggest if there has to be any improvements to the system

2.2.6

System Analysis And Design

V. Rajaraman

12 of 23

LIFE CYCLE OF SYSTEMS ANALYSIS AND DESIGN


Step 9 : System Modification

Fix errors Add/Delete features as required by users Tune the System Continuously monitor system and assess performance

2.2.7

System Analysis And Design

V. Rajaraman

13 of 23

System Life Cycle Diagram


User Requirements Revised Prioritized Requirements Specifications Requirements Specification Feasibility Analysis Feasibility Study

Requirements Determination Decision to Design Information System System Implementation System System Evaluation

Test Plan Logical Design Functional Specifications

System Design

System Specification Analysis

Configuration Data Hardware Study

Physical Requirements

Revised Requirements System Maintenance

Budget & schedule

Improved System

2.2.8

14 of 23

ROLE OF SYSTEMS ANALYST Defining Requirements - Involves Interviewing Users Prioritizing Requirements - Obtain Users Consensus Fact Gathering - Data, Facts, Opinions of Managers - Lower level Users should be consulted

2.3.1

System Analysis And Design

V. Rajaraman

15 of 23

ROLE OF SYSTEMS ANALYST Analysis and evaluation - Arrive at appropriate system Solving problems - Hazy requirements converted into specific requirements - Suggest many alternative solutions - Quantify cost and benefits

2.3.2

System Analysis And Design

V. Rajaraman

16 of 23

ROLE OF SYSTEMS ANALYST Drawing up specifications


- FUNCTIONAL SPECIFICATIONS

- Understood by users and programmers - Accepted by users - Precise and detailed - Account for possible changes

2.3.3

System Analysis And Design

V. Rajaraman

17 of 23

ROLE OF SYSTEMS ANALYST

SYSTEM DESIGN Logical design of system - Objects identification - Normalizing database - Test plan Design must be modular to accommodate change

2.3.4

System Analysis And Design

V. Rajaraman

18 of 23

ROLE OF SYSTEMS ANALYST

Evaluating Systems - Evaluation after use for sometime - Plan periodicity for evaluation - Modify as needed

2.3.5

System Analysis And Design

V. Rajaraman

19 of 23

ATTRIBUTES OF A SYSTEMS ANALYST


KNOWLEDGE OF ORGANISATION

- Knowing users jargon & practices - Know Management functions.


KNOWLEDGE OF COMPUTERS AND SOFTWARE

- Knowledge of system design tools - Keep abreast of modern developments


2.3.6
System Analysis And Design

V. Rajaraman

20 of 23

ATTRIBUTES OF A SYSTEMS ANALYST


GOOD INTERPERSONNAL RELATIONS
- Need to work as team member - Lead smaller teams - Interface with programmers & Users - Motivator.

ABILITY TO COMMUNICATE
- Oral Presentation - Report Writing - Answer queries

2.3.7

System Analysis And Design

V. Rajaraman

21 of 23

ATTRIBUTES OF A SYSTEMS ANALYST


ANALYTICAL MIND
- Problem solving attitude - Ability to assess trade offs - Sound commonsense - Curiosity to learn about new organizations

BREADTH OF KNOWLEDGE
- Broad Liberal Knowledge - Variety of jobs to be tackled in diverse organizations

2.3.8

System Analysis And Design

V. Rajaraman

22 of 23

TOOLS USED BY SYSTEMS ANALYST Data Flow Diagram Decision Tables Modeling Language such as UML Normalization of Databases Testing tools ISO/CMM procedure manuals

2.3.9

System Analysis And Design

V. Rajaraman

23 of 23

Vous aimerez peut-être aussi