Systems Analysis

1
Systems Analysis
2
Agenda

• Why Systems Analysis?
• Precursors of Analysis
• The Process of Systems Analysis
• The Products of Systems Analysis
• Summing It Up

3
Why Systems Analysis
4
Basic Problem Solving
See Think Say
5
Precursors of Analysis

• Experience with existing system
• There might not be an existing system
• Environment or system changes
• Neither is more likely
• Someone notices or anticipates effects of changes
  
• A systematic study is called for

6
Process of Systems Analysis

• Document current system
• Detail symptoms
• Determine alternatives
• Evaluate alternatives (feasibility)
• Select or prioritize alternatives
• Create logical design (functions)
• Create physical design (processes)

User Involvement
7
Activities in the Process

• Detailed observation of users
• Interviews with users
• Economic, process evaluation
• Feasibility study (time, money, will, technical)
• Alternative evaluation
• Charting, functional specification
• Process design

8
Roles in the Process

• Client and client management
• Users (current and/or planned)
• Other stakeholders
• Systems analysts
• Facilitators
• Prototypers or builders

In prototyping, a mock system is constructed
and continuously modified until it meets user
needs. The result is an implicit model of what
must actually be constructed. Prototypes are
rarely efficient and generally have to be
optimized by technical people.
9
Products of Systems Analysis
Usually text, sometimes charts Various graphical
formats Text, system diagrams Technical charts,
flowcharts, data flow diagrams, various data
representation charts, process charts
10
Summing It Up

• Driven by organizational needs
• Based on system theory
• User involvement falls during SA
• Client is in control
• Methods are technical
• Generally work is collaborative, but might not
  always be
• SA is part of a larger, more complex process