Software Development Life Cycle: 2 Weeks
Software Development Life Cycle: 2 Weeks
Software Development Life Cycle: 2 Weeks
Analyze 3 weeks
Test 4 weeks
Release/Warranty 4 weeks
Concept Evaluation/Initialization
Business cases:
Financial Valuation
Cost-Benefit analysis
Planning
Communication
Verification (Testing)
Validation
Gather and model the requirements ( user, quality and security) into a requirement
specification
Capture the events
Create data models as applicable
Define/update the business processes as well as the quality
Review decommissioning evaluation and recommendation
Document decommissioning requirements
Update the business case to identify the affect of the decommissioning benefits and cost
Complete risk based testing ; create test strategy and test plan
(Risk based test scores are given to the requirements eg: 1,2,3 and there is a formula
to calculate the risk ( using Excel)
The first set of task in the Analyze phase involve Gathering user and quality
requirement which are aligned to the business needs of the project
The prompt and appropriate approval of phase end documentation is a prime review
point for the internal and external audits(Including Sarbanes-Oxley Reviews)
Test conditions/ Test cases -----> Test scenarios ---> Test Strategies
Design Phase
Leverage analysis model as the basis of the system design in conjunction with the
existing development, executives and operation architectures
Review decommissioning impact and document the general approach and procedures
required to accomplish the decommissioning
The info gathered in the design phase ensures the detailed user interface, database
and processes are defined and documented for use in the build phase. Additionally
the test strategy and conditions are further refined.
Build phase
(Output of the build phase is to ensure that all test errors are corrected, produce executable
code, procedures, training and system test component)
Test Phase
Release phase
The work environment reflects only the new system and those remnants of the old system
which are still in use.
Redundant elements of the old system are removed
Review and analyze the system to verify that is performs the functions stated in design
Document any changes or enhancements identified during the initial production cycles
that would make the new system more responsive to user and business needs
Warranty phase
1. Requirement reports
2. Flow diagram(As is ,To be Power point or visio )
3. Data Modeling( if present in the project)
4. Event description
5. Appendix
SDLC METHODOLOGY
Waterfall method:
RUP
Inception phase, developers define the scope of the project and its business case
Elaboration phase, developers analyze the project's needs in greater detail and define its
architectural foundation
Construction phase, developers create the application design and source code
Agile development is good for reducing overheads and for small teams
In Agile, Bugs are tested for every stage and also tested finally
Agile XP
Communication between customers and other team members and stresses more on
customer satisfaction
XP emphasizes in team work( Customers, manager,developer)
Feedback given on Day 1 of software testing to the customers and implement changes as
suggested
Early delivery and implementation of suggested changes
Scrum
Differences