1. Public Management Information Systems System Analysis Thursday, August 01, 2019
Hun Myoung Park, Ph.D.
Public Management & Policy Analysis Program Graduate School of International Relations

2. System Development Life Cycle
Investigation (planning)
Systems analysis
Systems design
System development
Systems implementation
System maintenance

3. Why SDLC?
Systematic approach to give guidelines for improving efficiency and effectiveness
To avoid system failures: lack of communication (acceptance); politics (sunk costs) and leaderships; technical incompetence; education & training
Considered as conceptual model and depending on institutional settings.

4. Caution in SDLC Programming is a part of system development
Phases (steps) may not always be distinct and thus may overlap
Phases are interrelated and interdependence
Detecting errors in an early phase will save the cost

5. Prototyping Iterative approach to revise prototypes.
“During each iteration, requirements and alternative solutions to the problem are identified and analyze, new solutions are designed, …” (p. 507)
“[A]n iterative process involving analysts and users whereby a rudimentary version of an information system is built and rebuilt according to user feedback.” (p.195)

7. Other Approaches Rapid application development (RAD)
Agile (usage-centered) development
Extreme programming (XP)
Adaptive software development, lean software development, rational unified process, feature-driven development
Customization, fast cycles, error-correction

8. System Investigation Determine organization’s objectives
Business process reengineering (BPR)
Feasibility analysis (economic, legal, operational, schedule feasibility)
Describing (tangible and intangible) costs and benefits of each solutions
Propose alternative solutions (keep or revise old system, or get a new system)

9. System Analysis 1
Data collection to gather data for information needs, resources, and capabilities
Data analysis for data modeling and activity modeling
Requirement analysis is to “determine user, stakeholder, and organizational needs” (p.526).

10. System Analysis 2 Determine the nature and scope of the project.
Sources of data
Observations of users (conversations)
Written documents
Computer-based information

11. System Analysis 3 Traditional Data Collection
Interviews (individuals and groups)
Observing users
Questionnaires
Reviewing documents

12. System Analysis 4 Joint application development (JAD)
A highly organized intensive workshop to bring together system owners (managers), users, and technicians (e.g., analysts, programmers, engineers) to jointly define and design systems
“[A]nalysts control the sequence of questions answered by users” (p.192)

13. System Analysis 5 Computer-aided software engineering (CASE) tools
Data flow diagram (DFD),
System flowcharts (flow diagram)
Connectivity diagrams, grid charts, decision tables,
Object-oriented analysis

14. System Analysis 6 Business process reengineering (BPR)
“[L]ooking for new ways to perform current tasks” rather than “automating existing processes” (p.197).
“[N]ot just to improve each business process, but, … to reorganize the complete flow of data … to eliminate unnecessary steps, achieve synergies among … separate steps…” (p.197).

15. System Analysis 7
Key business processes are “structured set of measurable activities designed to produce a specific output for a particular customer or market” (p.198).
Is an activity dysfunctional? Important? Feasible?
Employ disruptive technologies that “enable the breaking of long-held business rules that inhibit …” (p.199).

16. Highlights Iteration, but not a one-shot game
Not a technicians’ job but all stakeholders’ jobs to improve their performances
User centered approach; keep analyzing users needs all the time