SDLC Models

By Ritu Beta Soft Systems Inc.

What is a Project?
A project is an activity which achieves specific objectives through a set of defining tasks and effective use of resources.

PLC Phases
Initiation Planning Execution Closure

Initiation Phase
Develop a Business Case Undertake a Feasibility Study Establish the Project Charter Appoint the Project Team Set up the Project Office Perform Phase Review

Planning Phase
Create a Project Plan Create a Resource Plan Create a Financial Plan Create a Quality Plan Create a Risk Plan Create an Acceptance Plan Create a Communications Plan Create a Procurement Plan
Contract the Suppliers Define the Tender Process Issue a Statement of Work Issue a Request for Information Issue a Request for Proposal Create Supplier Contract Perform Phase Review

Execution Phase
Build Deliverables Monitor and Control
Perform Time Management Perform Cost Management Perform Quality Management Perform Change Management Perform Risk Management Perform Issue Management Perform Procurement Management Perform Acceptance Management Perform Communications Management

Closure Phase
Perform Project Closure Review Project Completion

PLC Phases
INITIATION: In the first phase, a need is identified by the client or customer and this results in a Request for Proposals (RfP) which describes and defines the needs and requirements. We can call this phase Initiation. PLANNING: The second phase is characterized by the development of proposed solutions and the Bidding process. A structured bid form which requested specific items of information related to project costs, staffing and other resources, timescales, description of the activities, compliance to technical standards and key deliverables. EXECUTION: The third phase in which the project is executed covers detailed planning and Implementation. CLOSURE: The final phase is terminating the project or Closure. In some cases this is marked with formal acceptance by the customer or client with signed documentation.

SDLC Definition
A software development process is a structure imposed on the development of a software product. Synonyms include software life cycle and software process. There are several models for such processes, each describing approaches to a variety of tasks or activities that take place during the process.

Software Development Life Cycle

Waterfall Model

Advantages of Waterfall Model

Enforced discipline through documents
no phase is complete until the docs are done & checked by SQA group concrete evidence of progress

Drawbacks of Waterfall Model

Document-driven model
customers cannot understand these first time client sees a working product is after it has been coded. Problem here?
leads to products that dont meet customers needs

Assumes feasibility before implementation

re-design is problematic works best when you know what youre doing
when requirements are stable & problem is well-known

Spiral Model

Steps of Spiral
The steps in the spiral model can be generalized as follows:
The new system requirements are defined in as much detail as possible. This usually involves interviewing a number of users representing all the external or internal users and other aspects of the existing system. A preliminary design is created for the new system. This phase is the most important part of "Spiral Model". In this phase all possible (and available) alternatives, which can help in developing a cost effective project are analyzed and strategies are decided to use them. This phase has been added specially in order to identify and resolve all the possible risks in the project development. If risks indicate any kind of uncertainty in requirements, prototyping may be used to proceed with the available data and find out possible solution in order to deal with the potential changes in the requirements. A first prototype of the new system is constructed from the preliminary design. This is usually a scaled-down system, and represents an approximation of the characteristics of the final producA second prototype is evolved by a fourfold procedure: evaluating the first prototype in terms of its strengths, weaknesses, and risks; defining the requirements of the second prototype; planning and designing the second prototype; constructing and testing the second prototype.

Advantages and Disadvantages

Advantages

1. Estimates (i.e. budget, schedule, etc.) become more realistic as work progresses, because important issues are discovered earlier.
2. It is more able to cope with the (nearly inevitable) changes that software development generally entails. 3. Software engineers (who can get restless with protracted design processes) can get their hands in and start working on a project earlier. Disadvantages 1. Applied differently for each application 2. Risk of not meeting budget or schedule

Agile Manifesto
Customer satisfaction by rapid, continuous delivery of useful software Working software is delivered frequently (weeks rather than months) Working software is the principal measure of progress Even late changes in requirements are welcomed (this does not mean code & run. Instead removing an existing feature or moving a deadline forward to accommodate late/unplanned feature requests Close, daily cooperation between business people and developers Face-to-face conversation is the best form of communication (Co-location) Projects are built around motivated individuals, who should be trusted Continuous attention to technical excellence and good design Simplicity Self-organizing teams Regular adaptation to changing circumstances

SCRUM

Daily Scrum
Daily Scrum Each day during the sprint, a project status meeting occurs. This is called a "scrum", or "the daily standup". The scrum has specific guidelines: The meeting starts precisely on time. Often there are teamdecided punishments for tardiness (e.g. money, push-ups, hanging a rubber chicken around your neck) All are welcome, but only "pigs" may speak The meeting is timeboxed to 15 minutes All attendees should stand (it helps to keep meeting short) The meeting should happen at the same location and same time every day During the meeting, each team member answers three questions:
What have you done since yesterday? What are you planning to do by today? Do you have any problems preventing you from accomplishing your goal? (It is the role of the ScrumMaster to facilitate resolution of these impediments. Typically this should occur outside the context of the Daily Scrum so that it may stay under 15 minutes.)

Change Management
What is Change Management? 'Change management (or change control)' is the process during which the changes of a system are implemented in a controlled manner by following a pre-defined framework/model with, to some extent, reasonable modifications In Project Management, Change Management refers to a Project Management process where changes to a project are formally introduced and approved

Change Management Process

Create a project team dedicated to change Communicate the vision and goals of this team Monitor people/organizational issues Determine change management processes/practices Reorganize to support processes and practices Implement processes and practices Monitor completion of the plan; tasks and milestones Communication feedback, revise processes and practices as required