|
SDLC Tutorial
system development life cycle it is
a process through which any software should passed
befor implimented it contains various stages
1. Requirement Analysis
2. Designing
3. Coding
4. Testing
5. Maintenance.
It will support the models for developing
sytem or software by using
1. Water Fall Model
2. Spiral Model
3. Prototype Model
4. Agile Model etc.
Systems Development Life Cycle:
Building the System
All methods undertake the seven steps listed under
insourcing to different degrees:
Insourcing
Insourcing having IT specialists within an organization
to build the organization’s system by :
Planning – establishing
the plans for creating an information system by
:
Defining the system to be developed
– based on the systems prioritized according
to the organization’s critical success factor
(CSF), a system must be identified and chosen
the project scope – a high level of system
requirements must be defined and put into a project
scope document
Developing the project plan - – all details
from tasks to be completed, who completed them
and when they were completed must be formalized
Managing and monitoring the project plan –
this allows the organization to stay on track,
creating project milestones and feature creeps
which allow you to add to the initial plan
Analysis – the users and IT specialists
collaborate to collect, comprehend, and logistically
formalize business requirements by :
Gathering the business requirements' – IT
specialists and knowledge workers collaborate
in a joint application design (JAD) and discuss
which tasks to undertake to make the system most
successful
Analyzing the requirements – business requirements
are prioritized and put in a requirements definition
document where the knowledge worker will approve
and place their signatures
Design – this is where the technical
blueprint of the system is created by :
Designing the technical architecture – choosing
amongst the architectural designs of telecommunications,
hardware and software that will best suit the
organization’s system and future needs
Designing the systems model – graphically
creating a model from graphical user interface
(GUI), GUI screen design, and databases, to placement
of objects on screen
Development – executing the design
into a physical system by :
Building the technical architecture – purchasing
the material needed to build the system
Building the database and programs – the
IT specialists write programs which will be used
on the system
Testing – testing the developed system
Write the test conditions – test conditions
are conducted by comparing expected outcomes to
actual outcomes. If these differ, a bug is generated
and a backtrack to the development stage must
occur.
Deployment – the systems are placed
and used in the actual workforce and
The user guide is created
Training is provided to the users of the system
- usually through workshops or online
Maintenance – keeping the system up
to date with the changes in the organization and
ensuring it meets the goals of the organization
by
Building a help desk to support the system users
– having a team available to aid technical
difficulties and answer questions
Implementing changes to the system when necessary.
Selfsourcing
Selfsourcing having knowledge workers within an
organization build the organization’s system
Align selfsourcing applications to
the goals of the organization – All intentions
must be related to the organization’s goals
and time management is key.
Establish what external assistance will be necessary
– this may be where an IT specialist in the
organization may assist
Document and formalize the completed system created
for future users –
Provide ongoing support - being able to maintain
and make adjustments to the system as the environment
changes..
Prototyping
Prototyping creating a model, which displays the
necessary characteristics of a proposed system
Gathering requirements – these
requirements will be stated by the knowledge workers
as well as become apparent in comparison with
the old or existing system
Create prototype of system – Confirm a technically
proficient system by using prototypes and create
basic screen and reports
Review by knowledge workers - create a model of
the system that will be analyzed, inspected and
evaluated by knowledge workers who will propose
recommendations to have the system reach its maximum
potential
Revise the prototype – if necessary
Market the idea of the new system – use the
prototype to sell the new system and convince
the organization of the advantages of switching
up to the new system
Outsourcing
Outsourcing having a third party (outside the
organization) to build the organization’s
system so expert minds can create the highest
quality system by.
Outsourcing for development software
-
Purchasing existing software and paying the publisher
to make certain modifications and paying the publisher
for the right to make modifications yourself
Outsourcing the development of an entirely new
unique system for which no software exists
Selecting a target system – make sure there
is no confidential information critical to the
organization that others should not see. If the
organization is small enough, consider selfsourcing
Establish logical requirements - IT specialists
and knowledge workers collaborate in a joint application
design (JAD) and discuss which tasks to undertake
to make the system most successful to gather business
requirements
Develop a request for a proposal – a request
for proposal (RFP) is created and formalized.
It includes everything the home organization is
looking for in the system and can be used as the
legal binding contract
Evaluate request for proposed returns and choose
a vendor amongst the many who have replied with
different prototypes
Test and Accept a Solution – the chosen system
must be tested by the home organization and a
sign-off must be conducted
Monitor and Reevaluate – keep the system
up to date with the changing environment and evaluate
the chosen vendor’s ability and accommodate
to maintain the system
|
