SD LIFE CYCLE

I. Systems Analysis
2. Conceptual Design
3. Physical Design
4. Implementation and Conversion
5. Operations and Maintenance WHY BEHAVIORAL PROB OCCUR?
throughout the life cycle, planning must be done & Fear Disruption
behavioral aspects of change must be considered Lack of top-mgt Manner change is
INVOLVEMENT IN SDLC support introduced
I. IS steering committee Bad prior experiences Biases & emotions
2. Project Development Team Poor communication Personal characteristics
3. Programmers
4. Systems Analysts
5. Management
6. Users

INTRO TO SYSTEMS DEVELOPMENT WAYS TO PREVENT

Management support Keep system simple

Two plans needed:

SD PLANNING
I. Project Development Plan
and Systems Analysis Satisfy user needs
Involve users
Keep open commu-
nication
Reduce fears Test system prior im-
Specific to a project & authored by the project team
2. Master Plan (CHAPTER 22) Avoid emotionalism plementation

Long-range & authored by steering committee

outlining prioritized projects & timetables

CAPITAL BUDGETING
I. Payback period
2. Net Present Value (NPV)
PLANNING TECHNIQUES
3. Internal Rate of Return (IRR)
I. Program evaluation and review technique (P E R T)
used to identify critical paths, plan resources, FEASIBILITY ANALYSIS
estimate task duration & identify potential risks I. software product in terms of how much beneficial
2. Gantt chart product development will be for the org. in a
horizontal bar chart used to visually represent a practical POV
project plan over time 2. Below are 5 types of feasibility:
Economic Scheduling
Technical Operational
SITI NUR ASYIFFA BINTI MOHD AZAHA Legal
(2022787353)
AC220B5H