Software Development Life Cycle

Activity

1. Business Promotion2. Product Promotion3. Demonstration4. Sales Call5. Meetings

Details

1. Plan Business Promotion.2. Identify Potential Customer.

OutputDocument

1. Brochure2. Mailers/Letters3. Presentations 4. Emails

Role1. Sales Person2. Marketing Person3. Business Analyst

Pre-sales Activity 1

Activity

Request for Proposal (RFP)

Details

The Customer needs a solution and sendsa request for Proposal

Output

RFP Document

Role

Customer

Pre-sales Activity 2

Activity

Prepare Draft Proposal

Details

1. Identify the Sales Person who will interact with the customer.2. Customer Requirements are studied.3. Identify the project type (Development/ Maintenance/Migration).4. Identify the Lifecycle model (Waterfall /Iterative).5. Identify the nature of costing for the project (Fixed Cost/Time and material).6. Evaluate the technology7. Estimate the Size and Cost of the project.

OutputDocument

1. Draft Proposal2. Technical Evaluation Document (If Required)

Role1. Sales Person2. Marketing Person3. Business Analyst4. Solution Group

Pre-sales Activity 3

Activity

Review Proposal

Details

1. Senior Management reviews the Draft proposal.2. Solutions Group reviews the Draft Proposal for technical issues.

OutputDocument

Review Comments

Role

1. Senior Management2. Solutions Group

Pre-sales Activity 4

Activity

1. Prepare Proposal2. Send Proposal3. Follow-up

Details

1. Prepare the final proposal with changes suggested in review.2. Ensure that the proposal reaches the customer in time.3. Follow-up with the customer.4. Find out if any additional information is required.5. Revise the proposal if required.

OutputDocument

Final Proposal.

Role1. Sales Person2. Marketing Person3. Business Analyst

Pre-sales Activity 5

Activity

Close Proposal

Details

The Pre-Sales activity ends with the customer indicating the acceptance of the proposal.

OutputDocument

Letter/Fax/E-Mailfrom customer.(No verbal acceptance)

Role1. Sales Person2. Marketing Person3. Business Analyst

Pre-sales Activity 6

Activity

Identify the Project Manager

Details

1. The Post-Sales activity starts with the customer indicating the acceptance of the proposal.2. The Project Manager responsible for the Planning and Execution of the Project is identified.

Output

E-Mail/MOM Indicating identification of PM

Roles1. Senior Management2. Project Manager

Post-Sales Activity 1

Activity

Define Objective and Scope of the project.

Details

Prepare Vision and Scope Document forthe project which defines the Business Background, Objective and High-Level scope of the project.

Output

Vision and Scope Document

Roles

Business Analyst

Post-Sales Activity 2

Activity

1. Collect Customer Requirements.2. Elicit User Requirements.

Details

1. High-Level Business Requirements are collected from the Customer.2. Interact with actual users and understand the User Requirements.3. If the customer is knowledgeable, he may himself prepare the BRD.

Output

1. Business Requirement Document (BRD).2. Business Use- cases.

Roles1. Business Analyst2. Systems Analyst

Requirements Phase

Activity

Approval/Review of BRD.

Details

1. BRD is shared with the Customer to ensure that Customer Requirements are captured properly.2. BRD is updated as per Customer feedback.

Output

Updated BRD.

Roles1. Customer2. Business Analyst

Requirements Phase

Activity

Sign SOW with the customer.

Details

1. Prepare Statement of Work (SOW) Document which defines:Scope of WorkMajor MilestonesSchedulesDeliverables andAcceptance Criteria

2. The above SOW is accepted and signed by ITcube and the Customer as acceptance to the agreed work.

Output

SOW Document.

Roles1. Customer2. Senior Management3. Business Analyst

Requirements Phase

Activity

Project Kick-Off.

Details

1. Project Kick-Off meeting is arranged by Project Manager.2. All Relevant Stakeholders attend the Meeting.

Output

MOM (Minutes of Meeting for Kick-Off)

Roles1. Project Manager2. Relevant Stakeholders

Project Kick-Off

Activity

1. Estimation2. Prepare Project Plan

Details

1. Estimate the project size, schedule and the resources required.2. Identify the Work Breakdown Structure3. Prepare various Plans as needed for the project.4. Tailoring required for the project is defined.5. All the documents are reviewed.

Output

WBS, Project Plan, Test Plan, Configuration Plan, QA Plan, Risk Plan, Communication Plan, Training Plan, Measurement Plan, Function-Point Analysis Document.

Roles1. Project Manager2. Project Team

Project Planning Phase

Activity

Requirement Development

Details

1. Business Requirements and use-cases are studied.2. Functional Requirements are identified.3. Functional requirements are mapped with Business Requirements.4. All the documents are reviewed.

Output

Functional RequirementsDocument.

Roles1. Business Analyst2. Systems Analyst

Requirements Development

Activity

1. Design of Architecture2. Database Design

Details

1. Define the Project Architecture and prepare Design Document.2. Prepare Data Dictionary, DFD and ERD.3. Prepare Screen Specifications and Technical Use-cases.4. All the documents are reviewed.

Output

1. Design Document2. Technical Use-cases3. Screen Specifications4. DFD5. ERD

Roles1. Systems Analyst2. Project Team

Analysis and Design Phase

Activity

Develop the Application

Details

1. Configuration baselines are established.2. Develop the code and components.3. Review the code.4. Unit Test the components.5. Integrate the product.

Output

1. Code2. Unit Test-cases3. Product Integration Document4. Integrated Application5. Configurable Items List 6. Baseline Document.

Roles1. Developers2. TL/PL3. Configuration Engineer

Development

Activity

Validate the Application

Details

1. Prepare Test-Cases2. Execute the Test-Cases3. Identify and track defects4. Prepare Test Execution Reports 5. Bug Report

Output

1. Test-Cases2. Review of Test-Cases3. Test Execution Report4. Bug Report

Roles1. Testers

Testing and Validation

Activity

Monitor the project

Details

1. Project Execution is monitored.2. Corrective actions are taken where necessary3. Project Status meetings are held regularly4. Audits and reviews are conducted

Output1. Project Tracking Report2. Time Sheets3. Weekly Status Reports4. Planned vs Actual Reports5. Project Progress Review Report5. Issue Log6. CR Log7. Project Status MOM8. Risk Tracking Sheet

Roles1. Project Manager2. TL/PL3. QA Engineer

Project Tracking and Monitoring

Activity

Plan for Delivery

Details

1. Identify the Deliverables.2. Prepare Release Note.3. Prepare the product for Delivery.4. Conduct Delivery Audits.

Output

1. Release Note2. Audit Reports3. User Documentation4. Product/ Application

Roles1. Project Manager2. TL/PL3. QA Engineer4. Configuration Engineer

Delivery

Activity

Deploy the productUAT

Details

1. Product is deployed at Customer’s site2. Customer performs User Acceptance Testing3. Customer Accepts the Product

Output

E-Mail/Letter/FAX (Acceptance by Customer)

Roles1. Customer

Deployment and Acceptance

Activity

Project Closure

Details

1. All Project artifacts and assets are stored in the repository.2. Lessons-Learnt meeting is conducted.3. Project Resources are released.4. Project Closure Audit is conducted.

Output

1. MOM.2. Project Closure .3. Audit Report.4. Project Measures.

Roles1. Project manager2. Project Team3. QA Engineer

Project Closure and Sign-Off