Scribd
Upload
86 views3 pages

SISBUSI Notes

The document summarizes the phases of the System Development Life Cycle (SDLC) model: 1) Analysis phase to determine requirements 2) Design phase to develop the system blueprint 3) Implementation phase to build the system 4) Testing phase to ensure requirements are met 5) Maintenance phase for ongoing improvements It also outlines key activities in SDLC like developing feasibility reports, information requirements, system design, documentation, and implementation planning.

Uploaded by

Eloise Dy
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
86 views3 pages

SISBUSI Notes

The document summarizes the phases of the System Development Life Cycle (SDLC) model: 1) Analysis phase to determine requirements 2) Design phase to develop the system blueprint 3) Implementation phase to build the system 4) Testing phase to ensure requirements are met 5) Maintenance phase for ongoing improvements It also outlines key activities in SDLC like developing feasibility reports, information requirements, system design, documentation, and implementation planning.

Uploaded by

Eloise Dy
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

SDLC - System/ Software Development Life -Wca work centered analysis-

Cycle aka Waterfall Model/ Classical Model proponent: steven alter


Phase 1: Analysis - What do we need to - Work of the information
do? analyst
Phase 2: Design - How do we do it? - Bpr - help in framing an
Phase 3: Implementation - Lets do it! approach for rethinking the
Phase 4: Testing - Were we able to do it? business in a creative way
Phase 5: Maintenance - Are there some business process
more work to do? Any rooms for reengineering)
improvement? 3. Analyzing system needs
- Tools: dfd (data flow diagram)
Activity Planning and Control - Analyzes the structured decisions
Steps made
1. Identify problems, opportunities and - Prepares a system proposal
objectives 4. Designing the recommended system
- critical to success for the rest of the - the analyst designs accurate data
project entry procedures so that data going
- problem s will be brought up by into the is is correct
ememe - Designing files or databases
- Allow the business gain competitive - Design controls and backup
advantage procedures to protect the system
Output: Feasibility report and data
(containing a problem definition and Eme eme
summarizing the objectives) feasible/not
feasible Systems flowcharting
2. Determining info requirements Flowcharting- a graphical method of
Tools: interviewing., sampling, investigating illustrating the step by step solution of a
hard data, questionnaires,observation problem
- Striving to understand hat info user
needs to perform their job Program flowchart - programmers
- Information analyst- specialist System flowchart/ process flowchart -
- Know the details of the graphic rep of the steps and procedures
current system
- Who- people involved System Flowchart Symbols
- What the business
activity
- Where the
environment it takes
place
- When- the timing
- How the current
procedures are
performed
- Official receipt, delivery receipt,
invoice
- Manual database: name eme

Annotation is jus description

flowchart
Include process participants in the heading

Computerized manual

5. Developing and documenting system analyst- make an is plan


is plan is a project

control
take appropriate action to expedite ( crash/
speed up)
resched activities to finish on time

implementation
buy erp
outsource (freelance programmer)
come up with own it dept

system design
designing effective output
output any useful info/data delivered to user
designing effective input
should

steps in drawing dfd


draw the context diagram
draw the diagram 0
show all the child diagram
convert logical dfd to physical dfd
- manual semi—-> fully automated

rule :
there will only be one process
many data entities and data flows
data store not allowed

You might also like