1. Systems Development Life Cycle
Time 5 Minutes
Hi All,
Good Morning/Good Afternoon
In the next four hours, we are going to cover Quality Management System, Accenture Deliver Suite and System Development Lifecycle.
Lets start with a brief introduction.
I am …………….from ……….. team.
This session is split into 2 sessions. In the first half we will cover the SDLC concepts and in the latter session the Accenture Delivery Suite and IDC QMS.
At the end of this session, you will have an understanding of the Quality Management System, ADS and SDLC.
I welcome you all to Accenture family.

2. Course Objectives To know about various types of
Software Development Life Cycle Models
Time: 2 mins
Main objective of the session is
To know about various types of Software Development Life Cycles
To know about various methodologies, tools, architectures and metrics available in Accenture
To have an overview of Quality Management System
To see the quality journey at IDC

3. Software Development Life Cycle Models

4. Definition The Software Development Life Cycle (SDLC) model is
An approach to have a linear sequence of steps to
develop a system or software product
To execute the process from start to finish
without revisiting any previous step
One of the oldest systems development models
and is still the most commonly used
Time: 3 mins
Ask the participant what they understand by lifecycle
What is Human Life Cycle ?
When we are born, we are babies and then grow into a child, then become an adult and finally old. In the same way, we have various phases in software development life cycle as well.
The SDLC is an approach to developing information system / software product by linear sequence of steps, from start to finish without revising any previous step.

5. Time – 5 Minutes
The normal software life cycle will starts from initiation, concepts development, planning, Requirement Analysis, Design, Build, testing, and maintenance.
Explain the high level activities at each stage

6. Why SDLC ? We need to follow SDLC
To execute projects with proven frame work
To define and focus roles and responsibilities
To enforce planning and control
To have consistency among deliverables
To increase productivity by executing the project in
systematic manner
To reduce the rework effort during project execution
Time: 3 mins
We have to tell them the benefits of using sdlc.
We can execute projects with already successful framework
We can monitor and control project
We can have consistency among deliverables

7. Types of SDLC Waterfall Model Proto typing Model Incremental Model
Spiral Model
Synchronize and Stabilize Model (Microsoft)
Rapid Application Development Model (RAD)
V – Model
Time : 2 Minutes
Explain about various sdlc types

8. Waterfall Model Waterfall model is the base Model of SDLC
Main features are:
Whole process of software
development is divided into separate
phases
Derives from its name, giving cascading
effect from one phase to another phase
Each phase has well defined starting
and ending point with identifiable
deliveries to the next phase
Most commonly used model
Time : 2 Minutes
In waterfall model, requirement starts first then followed by high level design and low level design. Once designing is over, the next phase of coding will start. Unit testing has to be done by the developers only then it should go to the next phase. Every phase will have a review mechanism. Review objective is to find defects and close them in the same phase. This is referred as Defect containment. Defects should not be allowed to leak to other phases. While the defect leakage is higher, the more the rework. The cost of fixing the defect is high, if defect is identified in the final phase. For e.g, if we fix defect in requirement phase, we will have to spend $ 1, if defect is leaked to the next phase, cost of fixing is high. If The client report the defect to IDC, then we have to spend $ 100 to fix the defect.

9. Prototyping Model
Prototyping is the process of quickly putting together a working model.
This model
Provides proof of concept
Gives users an idea of what the final system looks like
Increases the system development speed
Helps to identify any problems with earlier design
Enables users to give quicker feedback on the approach
Is Cost effective
Is not the final product and suitable especially for the analysis phase
Time : 2 Minutes
Prototype is look and feel of the product. In software development, a prototype is a rudimentary working model of a product or information system, usually built for demonstration purposes or as part of the development process. In the System development life cycle Prototyping Model, a basic version of the system is built, tested, and then reworked as necessary until an acceptable prototype is finally achieved from which the complete system or product can now be developed.
Prototype is not the final product. Customer approval is needed for to proceed to the next phase.

10. Incremental Model
Incremental development is a scheduling and staging strategy
In which the various parts of the system are developed at different times
and integrated as they are completed.
Main features of incremental model are
Increments may be built serially or in parallel
Each increment adds additional or improved
functionality to system
Requires small group of developers
Clients can see the system and provide feedback from time to time
Time : 2 Minutes
Requirements are received from client in a incremental way, all requirements are not got at one time. Project execution shall be done based on information available with project.
Testing of code shall be done on unit basis and checked in to configuration system, if configuration tool is used.

11. Spiral Model
Spiral Model is combined approach of prototype and waterfall
model.
In this model
Each phase is originated with alternative
specifications and risk analysis
Strengths are evaluated and the
necessary amount of testing is proposed for
each prototype
The above process is iterated until customer is satisfied
with that prototype
Final system is constructed based on the refined prototype
Time : 2 Minutes
Identification of risks shall be done in each phase. Risk analysis shall be done in each pahse.Based on strengths necessary amount of testing is proposed.

12. Synchronize and Stabilize Model (Microsoft)
Microsoft model is an approach in which teams work
in parallel on individual application modules and
Integrated later.
Main features of this model are:
Requirements Analysis is done
based on a proxy customer
Project is divided into several units
Each unit is developed by small teams
working in parallel
Testing and debugging is carried out for each
unit (synchronization)
Freezing unit at the end of a particular development
and integrated with other units (stabilization)
Time : 2 Minutes
The requirements analysis is based on proxy customer. The project is decomposed in several units. Testing and debugging done at the end of each day. Freezing of unit is done at every phase/defined milestone.

13. Rapid Application Development (RAD)
RAD (Rapid Application Development) is
a concept with which the products can be
developed faster and of higher quality.
The approach focuses on
Using workshops to gather requirements
in fast manner
Combining the best available techniques in
proper sequence to make them effective
following Prototyping techniques
Using appropriate tools
Re-using of software components / modules
A rigidly paced schedule that defers design
improvements to the next product version
Time : 2 Minutes
Quality is a primary concept in the RAD environment. Systems developed using the RAD development path meet the needs of their users effectively and have low maintenance costs.
The quality of a system is defined as the degree to which the system meets business requirements (or user requirements) at the time it begins operation. This is fundamentally different from the more usual definition of quality as the degree to which a system conforms to written specifications.
Rapid application development, high quality and lower costs go hand-in-hand if an appropriate development methodology is used.

14. Plan Application Product Test Plan Application Product Test
Test Conditions
Expected Results
V - Model
Plan Application Product Test
Prevent Overlapping
Stage Containment
Root Cause Analysis
- Errors
- Defects
- Faults
Entry / Exit Criteria
Plan Application Product Test
Plan Assembly Test
Plan Assembly Test
Plan
Component Test
Develop Test Plan
Perform Test
Verification
Validation
Analysis & Design
Testing
Plan
Component Test
Time : 5 Minutes
The V-Model saves time and money in development while increasing the quality of the results and the reliability of delivery. Adherence to the V-Model leads the way to a substantial decrease in the number of errors found in production after each release. Quality is designed into the system rather than tested in.
Benefits:
Lower defect resolution cost due to earlier detection
Includes validation and verification at each level for stage containment
Improved quality and reliability
Reduction in the amount of rework
Increased testing efficiency with added focus on testing objectives
Better informed scope definitions through requirements traceability
Improved risk management
Success criteria determined up front encouraging a more focused effort
Develop Test Plan
Perform Test
Verification
Validation
Validation – Checks if the right product is built up
Verification – Checks if the right process is followed
Testing Checks the product in operating conditions

15. Quiz What is the base SDLC model from which other
models have been derived ?
A) Rapid Application Development model
B) Waterfall Model
C) Incremental Model
D) V-Model
Time: 1 min
Answer : B

16. Quiz In Accenture, which model is followed for verification
and validation required at each stage of the life cycle?
A) Microsoft Model
B) Waterfall Model
C) Incremental Model
D) V-Model
Time: 1 min
Answer : D

17. Quiz Which model focuses on reusability of components?
A) Microsoft Model
B) Waterfall Model
C) Rapid Application Development Model
D) V-Model
Time: 1 min
Answer : C

18. Quiz Which model focuses on phase based risk analysis? A) Spiral Model
B) Waterfall Model
C) Rapid Application Development Model
D) Microsoft Model
Time: 1 min
Answer : A