Scribd
Upload
16 views

SDLC

Uploaded by

ather.mihs
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
16 views

SDLC

Uploaded by

ather.mihs
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 12

SDLC

The Waterfall Model


 Planning/Requirement
 Systems analysis,
 Systems design,
 Development,
 Testing,
 Implementation,
 Maintenance

Systems Development Life Cycle


(SDLC)
 Define the system's scope.
 Set the boundaries what the system will and will
not do.
 Estimate the time to implement the system.
◦ Important tasks in systems that take over a year to
implement.
◦ Systems requiring more than a year to implement
should be done in phases.
 Estimate the cost to implement.
◦ Usually actual cost of system implementation is 10 to
100 times greater than the estimated cost.
 Describe the benefits.
◦ In some cases, the intangible benefits out-weigh the
tangible ones.

Planning
 Determine how the current system works
 Determine solution to improve the new or

existing system.
 Look for alternative solutions.
 The first solution may not be the best.

Systems Analysis
Method Advantages Disadvantages

Interview
Detailed data, you can change Time-consuming, problems
questions during process classifying/quantifying data

Can reach a lot of people, quickly Questions may be mis-interpreted. People


Questionnaire (compared to interview/observation). may not respond at all or may do only
Numerical analysis possible. some questions.

Document The data required for the system can Documents may be lacking, out-of-date
Search be identified accurately. etc (interview could discover this).

Problem may not be described (or in detail).


Literature Can find descriptions/problems of
Search Again, working without experienced
previous implementations (saves work).
users.

Observation
Observations are independent of user Time consuming and observer can affect
bias (unlike interview/questionnaire). process.

Systems Analysis…
 The "How" phase, - determines how to implement the system study
solutions.
◦ input requirements:
 Determine the input source, such as, databases, data entry by
keyboard, mouse or screens (monitors), data screening, voice, data
communications, etc.
◦ Output requirements:
◦ Determine the output media, such as, hard or soft output.
 The output is determined first since it dictates the input requirements.
◦ Storage requirements:
◦ Define the databases.
 Records and Fields
◦ System controls and backup:
◦ Determine "what can go wrong scenarios".
◦ Unauthorized access, determine security measures for software &
hardware.
◦ Lost or corrupted databases
 determine on-site backup.

Systems design
 Build software programs according to design specifications.
 Make or by decision.
◦ Write the programs in-house or purchase software
packages.

 Purchase Considerations:
◦ Customization: Programs you write will meet design
specifications.
◦ Extensive customization should be avoided for two
reasons.
 First, it is costly and time consuming.
 Second, implementing software package revisions,
requires that customization changes be reapplied in
some cases does not retrofit(add something that did not have it
when manufactured.) easily.

 Re-Engineering:
◦ An alternative to customization in that the company
changes it's procedures to comply with the software
package specifications.

Development
 Test the system.
"What if" testing by the system analyst.
Beta testing by the system users.
Alpha testing until the system stabilizes.
 Normal Data

◦Data that is expected to be entered into the


program. Including data at the limits of what is
expected.
 Extreme Data

◦This will be outside the normal limits of the


program, What happens if a user enters incorrect
data by mistake.
 Abnormal Data

◦Data that is not expected, for example a string


instead of an integer value.

Testing
 •Develop user procedures.
•Train the users.
•Some approaches for turning-on the system:
Direct: Turn-off the old system and start-up the
new system.

Run the old & new system side by side
Parallel:
until the new system has proven to be
reliable. Should be avoided when there is not
enough users to keep both systems running.

Phased:Parts of the new system are phased in
separately.

The system is used by a limited number
Pilot:
of users like a department, or a district, or a
region etc.
Implementation
 Fix bugs.
 Keep the system current.
 Make improvements.

 Some of the post implementation problems:


◦ Insufficient support during the initial turn-on
phase.
◦ Insufficient support for maintaining the system.

 Prototype Systems:
◦ Prototype systems are developed when the
system requirements are not firm, that is, when
there are more questions than answers.

◦ Prototype systems involve an iteration process,


that is, they are reworked again and again until
the system meets user expectations.
Maintenanc
e
The
End

You might also like