Systems development life cycle (SDLC)

In order to tackle a complex project such as building a new system,

you will have to proceed systematically through a series of steps.

One methodology is the systems development life cycle. The systems

development life cycle (SDLC) is a methodology for understanding the
business objectives of any system and designing an appropriate
solution.


 System Development Life Cycle
An effective System Development Life Cycle (SDLC) should result in a high quality system that meets customer
expectations, reaches completion within time and cost evaluations, and works effectively and efficiently in the current
and planned Information Technology infrastructure.

System Development Life Cycle (SDLC) is a conceptual model which includes policies and procedures for developing
or altering systems throughout their life cycles.

The systems development life cycle (SDLC) is a conceptual model used in project management that describes the stages involved
in an information system development project, from an initial feasibility study through maintenance of the completed
application.

SDLC can apply to technical and non-technical systems. In most use cases, a system is an IT technology such as hardware and
software. Project and program managers typically take part in SDLC, along with system and software engineers, development
teams and end-users.
• The system-development life cycle enables users to transform a newly-developed project into an
operational one.

• The System Development Life Cycle, "SDLC" for short, is a multistep, iterative process, structured in a
methodical way. This process is used to model or provide a framework for technical and non-technical
activities to deliver a quality system which meets or exceeds a business' expectations or manage
decision-making progression
Adopting a life cycle methodology does not guarantee success, but it is far
better than having no plan at all.

The SDLC method also helps in creating documents that communicate

objectives, important milestones, and the uses of resources to management.
Phases of SDLC
Systems Development Life Cycle is a systematic approach which explicitly breaks down the work into phases that are
required to implement either new or modified Information System.

1. Planning
2. System Analysis
3. System Design
4. System Development
5. System Testing
6. Implementation and Maintenance
Feasibility Study or Planning
 This is the first phase in the systems development process.
 The purpose of this first phase is to find out the scope of the problem and determine solution. Define the
problem and scope of existing system.
 Overview the new system and determine its objectives. It identifies whether or not there is the need for a new
system to achieve a business’ strategic objectives
 Confirm project feasibility and produce the project Schedule.
 Resources, costs, time, benefits and other items should be considered here.
 During this phase, threats, constraints, integration and security of system are also considered.
 A feasibility report for the entire project is created at the end of this phase.

*The company might be trying to meet or exceed expectations for their employees, customers and stakeholders
too. The purpose of this step is to find out the scope of the problem and determine solutions. Resources, costs,
time, benefits and other items should be considered at this stage
Analysis and Specification
• The second phase is where businesses will work on the source of their problem or the need for a change.
• Gather, analyse, and validate the information. Examine the information needs of end-user and enhances the system goal.
• Define the requirements and prototypes for new system
• In the event of a problem, possible solutions are submitted and analyzed to identify the best fit for the ultimate goal(s) of
the project. Evaluate the alternatives and prioritize the requirements.
• This is where teams consider the functional requirements of the project or solution.
• It is also where system analysis takes place—or analyzing the needs of the end users to ensure the new system can meet
their expectations.
• Systems analysis is vital in determining what a business"s needs are, as well as how they can be met, who will be
responsible for individual pieces of the project, and what sort of timeline should be expected.
• Systems analysis is vital in determining what a business needs are, as well as how they can be met, who will be
responsible for individual pieces of the project, and what sort of timeline should be expected.
• A Software Requirement Specification (SRS) document, which specifies the software, hardware, functional, and network
requirements of the system is prepared at the end of this phase.
• One way to start is to identify the specific business objectives for your site, and then develop a list of
system functionalities (types of information systems capabilities you will need to achieve your
business objectives) and information requirements (the information elements that the system must
produce in order to achieve the business objectives).
• There are several tools businesses can use that are specific to the second phase. They include:

• CASE (Computer Aided Systems/Software Engineering)

• Requirements gathering
• Structured analysis
System Design
•A system design specification is a description of the main components in the system and their relationship to one
another.
•Includes the design of application, network, databases, user interfaces, and system interfaces.
•Transform the SRS document into logical structure, which contains detailed and complete set of specifications that
can be implemented in a programming language.
•The system design can be broken down into two components: a logical design and a physical design. A logical design
describes the flow of information at your e-commerce site, the processing functions that must be performed, the
databases that will be used, the security and emergency backup procedures that will he instituted, and the controls that
will be used in the system.
•A physical design translates the logical design into physical components. For instance, the physical design details the
specific model of server to be purchased, the software to be used, the size of the telecommunications link that will be
required, the way the system will be backed up and protected from outsiders etc
•Create a contingency, training, maintenance, and operation plan.
•Review the proposed design. Ensure that the final design must meet the requirements stated in SRS document.
•Finally, prepare a design document which will be used during next phases.
System Development
.

 The fourth phase is when the real work begins in particular, when
a programmer, network engineer and or database developer are
brought on to do the major work on the project.

 This work includes using a flow chart to ensure that the process
of the system is properly organized. The development phase
marks the end of the initial section of the process.

 The development stage is also characterized by instillation and

change. Focusing on training can be a huge benefit during this
phase.
Developing the system after design using programming
languages either in house or through outsourcing.
The other alternative is to build the system from scratch
especially if you have experience with systems
development.

Advantages of building a site in-house include:

The ability to change and adapt the site quickly as the
market demands.
The ability to build a site that does exactly what the
company needs.
Disadvantages of building a site in-house include:
.

The costs may be higher.

The risks of failure may be greater, given the complexity of
issues such as security, privacy, and inventory management.
The process may be more time-consuming than if you had
an outside specialist firm to manage the effort.
Staff may experience a longer learning curve that delays
your entry into the market
 .

Outsourcing

Most businesses choose to outsource hosting and pay a company to host their Web site, which means
that the hosting company is responsible for ensuring the site is “live”, or accessible, 24 hours a day.

By agreeing to a monthly fee, the business need not concern itself with many of the technical aspects
of setting up and maintaining it, telecommunications links, nor with staffing needs.

You can also choose to co-locate. With co-location a firm purchases or leases a Web server (and has
total control over its operation) but locates the server in a vendor’s physical facility.

The vendor maintains the facility, communications lines, and the machinery.

 Examples of some of the major hosting/co-location providers include Amazon EC2, Bluehost,
CenturyLink, GoDaddy, GSI Commerce, IBM Global Services, Rackspace, ServerBeach, Verio and
Verizon/Terremark.
5.Testing the System
.

Once the system has been built and programmed you will need to engage in a testing process and
depending on the size of the system, this could be fairly difficult and lengthy.
Testing is mandatory whether the system is outsourced or built in-house.
 A complex e-commerce site can have thousands of pathways through the site, each of which must be
documented and tested.
Unit testing involves testing the site’s program modules one at a time.
 System testing involves testing the site as a whole, in the same way a typical user would when using
the site.
 Acceptance testing verifies that the business objectives of the system as originally conceived are in fact
working.
 Acceptance testing is done by the firm’s key personnel and managers as they actually use the system as
installed on a test Internet or intranet server.
• The fifth phase involves systems integration and system testing (of programs and procedures)—normally
carried out by a Quality Assurance (QA) professional—to determine if the proposed design meets the
initial set of business goals.
• Testing may be repeated, specifically to check for errors, bugs and interoperability. This testing will be
performed until the end user finds it acceptable. Another part of this phase is verification and validation,
both of which will help ensure the program’s successful completion.
 This testing will be performed until the end user finds it acceptable.

 Another part of this phase is verification and validation, both of which will help ensure the program’s
successful completion
Implementation and Maintenance
.

 This phase involves the actual installation of the newly developed system.
 This step puts the project into production by moving the data and components from the
old system and placing them into the new system
 Conversion is important to identify the conversion approaches- direct conversion,
parallel, phased etc
 While this can be a risky and complicated move, the cutover typically happens during off-
peak hours, thus minimizing the risk.
 Both system analysts and end-users should now see the realization of the project that has
implemented changes.
Maintenance is when end users can fine-tune the system, if they wish, to boost
performance, add new capabilities or meet additional user requirements.
Maintenance/Support
•Include all the activities such as phone support or physical on-site support for users that is
required once the system is installing.
•Implement the changes that software might undergo over a period of time, or implement any
new requirements after the software is deployed at the customer location.
•It also includes handling the residual errors and resolve any issues that may exist in the system
even after the testing phase.
•Maintenance and support may be needed for a longer time for large systems and for a short
time for smaller systems.
Role of System Analyst
The system analyst is a person who is thoroughly aware of the system and guides the system development project by
giving proper directions. S/He is an expert having technical and interpersonal skills to carry out development tasks
required at each phase.
S/He pursues to match the objectives of information system with the organization goal.

Main Roles
•Defining and understanding the requirement of user through various Fact finding techniques.
•Prioritizing the requirements by obtaining user consensus.
•Gathering the facts or information and acquires the opinions of users.
•Maintains analysis and evaluation to arrive at appropriate system which is more user friendly.
•Suggests many flexible alternative solutions, pick the best solution, and quantify cost and benefits.
•Draw certain specifications which are easily understood by users and programmer in precise and detailed form.
•Implemented the logical design of system which must be modular.
•Plan the periodicity for evaluation after it has been used for some time, and modify the system as needed.
Attributes of a Systems Analyst
The following figure shows the attributes a systems
analyst should possess −
Interpersonal Skills
•Interface with users and programmer.
•Facilitate groups and lead smaller teams.
•Managing expectations.
•Good understanding, communication, selling and teaching abilities.
•Motivator having the confidence to solve queries.

Analytical Skills
•System study and organizational knowledge
•Problem identification, problem analysis, and problem solving
•Sound common sense
•Ability to access trade-off
•Curiosity to learn about new organization

Management Skills
•Understand users jargon and practices.
•Resource & project management.
•Change & risk management.
•Understand the management functions thoroughly.
Technical Skills
•Knowledge of computers and software.
•Keep abreast of modern development.
•Know of system design tools.
•Breadth knowledge about new technologies.