requests
Description
These PPT's are for the students going for SAD
Document Sample
Software Development
Life Cycle
Pre-sales Activity 1
Activity Output
Details Document
1. Business Promotion
2. Product Promotion 1. Brochure
1. Plan Business Promotion.
3. Demonstration 2. Mailers/Letters
2. Identify Potential Customer.
4. Sales Call 3. Presentations
5. Meetings 4. Emails
Role
1. Sales Person
2. Marketing Person
3. Business Analyst
Pre-sales Activity 2
Activity Details
Output
Request for The Customer needs a solution and sends
Proposal (RFP) RFP Document
a request for Proposal
Role
Customer
Pre-sales Activity 3
Details
1. Identify the Sales Person who will interact Output
with the customer.
Activity 2. Customer Requirements are studied. Document
3. Identify the project type (Development/
Prepare Draft Maintenance/Migration). 1. Draft Proposal
Proposal 4. Identify the Lifecycle model (Waterfall 2. Technical
/Iterative). Evaluation
5. Identify the nature of costing for the project Document
(Fixed Cost/Time and material). (If Required)
6. Evaluate the technology
7. Estimate the Size and Cost of the project.
Role
1. Sales Person
2. Marketing Person
3. Business Analyst
4. Solution Group
Pre-sales Activity 4
Details Output
Activity
Document
1. Senior Management reviews the Draft proposal.
Review Proposal 2. Solutions Group reviews the Draft Proposal for
technical issues. Review Comments
Role
1. Senior Management
2. Solutions Group
Pre-sales Activity 5
Details
Activity 1. Prepare the final proposal with changes Output
suggested in review.
2. Ensure that the proposal reaches the customer Document
1. Prepare Proposal
in time.
2. Send Proposal
3. Follow-up with the customer. Final Proposal.
3. Follow-up
4. Find out if any additional information is
required.
5. Revise the proposal if required.
Role
1. Sales Person
2. Marketing Person
3. Business Analyst
Pre-sales Activity 6
Output
Details Document
Activity
Letter/Fax/E-Mail
Close Proposal The Pre-Sales activity ends with the customer
from customer.
indicating the acceptance of the proposal.
(No verbal
acceptance)
Role
1. Sales Person
2. Marketing Person
3. Business Analyst
Post-Sales Activity 1
Details
Output
Activity 1. The Post-Sales activity starts with the
customer indicating the acceptance of the
Identify the Project proposal. E-Mail/MOM
Manager 2. The Project Manager responsible for the Indicating
Planning and Execution of the Project identification of PM
is identified.
Roles
1. Senior Management
2. Project Manager
Post-Sales Activity 2
Details
Activity Output
Prepare Vision and Scope Document for
Define Objective and the project which defines the Business Vision and Scope
Scope of the project. Background, Objective and High-Level Document
scope of the project.
Roles
Business Analyst
Requirements Phase
Details Output
Activity
1. High-Level Business Requirements are
1. Collect Customer collected from the Customer. 1. Business
Requirements. 2. Interact with actual users and Requirement
2. Elicit User understand the User Requirements. Document (BRD).
Requirements. 3. If the customer is knowledgeable, he 2. Business Use-
may himself prepare the BRD. cases.
Roles
1. Business Analyst
2. Systems Analyst
Requirements Phase
Details
Activity Output
1. BRD is shared with the Customer
to ensure that Customer Requirements are
Approval/Review of
captured properly. Updated BRD.
BRD.
2. BRD is updated as per Customer
feedback.
Roles
1. Customer
2. Business Analyst
Requirements Phase
Details
1. Prepare Statement of Work (SOW)
Document which defines:
Scope of Work
Activity Major Milestones Output
Schedules
Sign SOW with the Deliverables and
customer. Acceptance Criteria SOW Document.
2. The above SOW is accepted
and signed by ITcube and the
Customer as acceptance to the
agreed work.
Roles
1. Customer
2. Senior Management
3. Business Analyst
Project Kick-Off
Details
Output
Activity
1. Project Kick-Off meeting is arranged by
Project Manager. MOM (Minutes of
Project Kick-Off.
2. All Relevant Stakeholders attend the Meeting for Kick-Off)
Meeting.
Roles
1. Project Manager
2. Relevant Stakeholders
Project Planning Phase
Details Output
Activity 1. Estimate the project size, schedule and
WBS, Project Plan,
Test Plan,
the resources required.
Configuration Plan,
1. Estimation 2. Identify the Work Breakdown Structure
QA Plan, Risk Plan,
2. Prepare Project 3. Prepare various Plans as needed for the
Communication Plan,
Plan project.
Training Plan,
4. Tailoring required for the project is
Measurement Plan,
defined.
Function-Point
5. All the documents are reviewed.
Analysis Document.
Roles
1. Project Manager
2. Project Team
Requirements Development
Details
Activity Output
1. Business Requirements and use-cases
are studied.
Requirement 2. Functional Requirements are identified. Functional Requirements
Development 3. Functional requirements are mapped Document.
with Business Requirements.
4. All the documents are reviewed.
Roles
1. Business Analyst
2. Systems Analyst
Analysis and Design Phase
Details Output
Activity 1. Define the Project Architecture and
1. Design Document
prepare Design Document.
2. Technical Use-cases
1. Design of Architecture 2. Prepare Data Dictionary, DFD and ERD.
3. Screen Specifications
2. Database Design 3. Prepare Screen Specifications and
4. DFD
Technical Use-cases.
5. ERD
4. All the documents are reviewed.
Roles
1. Systems Analyst
2. Project Team
Development
Output
Details
1. Code
Activity 2. Unit Test-cases
1. Configuration baselines are established. 3. Product Integration
2. Develop the code and components. Document
Develop the
3. Review the code. 4. Integrated Application
Application
4. Unit Test the components. 5. Configurable Items
5. Integrate the product. List
6. Baseline
Document.
Roles
1. Developers
2. TL/PL
3. Configuration Engineer
Testing and Validation
Details Output
Activity
1. Prepare Test-Cases 1. Test-Cases
2. Execute the Test-Cases 2. Review of Test-Cases
Validate the
3. Identify and track defects 3. Test Execution
Application
4. Prepare Test Execution Reports Report
5. Bug Report 4. Bug Report
Roles
1. Testers
Project Tracking and Monitoring
Output
Details 1. Project Tracking
Report
2. Time Sheets
1. Project Execution is monitored.
Activity 2. Corrective actions are taken where
3. Weekly Status
Reports
necessary 4. Planned vs Actual
Monitor the project 3. Project Status meetings are held Reports
regularly 5. Project Progress
4. Audits and reviews are Review Report
conducted 5. Issue Log
6. CR Log
7. Project Status MOM
8. Risk Tracking Sheet
Roles
1. Project Manager
2. TL/PL
3. QA Engineer
Delivery
Output
Details
Activity 1. Release Note
1. Identify the Deliverables. 2. Audit Reports
2. Prepare Release Note. 3. User
Plan for Delivery
3. Prepare the product for Delivery. Documentation
4. Conduct Delivery Audits. 4. Product/
Application
Roles
1. Project Manager
2. TL/PL
3. QA Engineer
4. Configuration Engineer
Deployment and Acceptance
Activity Details Output
1. Product is deployed at Customer’s site
Deploy the product E-Mail/Letter/FAX
2. Customer performs User Acceptance
UAT (Acceptance by
Testing
3. Customer Accepts the Product Customer)
Roles
1. Customer
Project Closure and Sign-Off
Details Output
Activity 1. All Project artifacts and assets are stored
in the repository. 1. MOM.
Project Closure 2. Lessons-Learnt meeting is conducted. 2. Project Closure .
3. Project Resources are released. 3. Audit Report.
4. Project Closure Audit is conducted. 4. Project Measures.
Roles
1. Project manager
2. Project Team
3. QA Engineer
