Software Development Standard Deliverables. Project Lifecycle Methodology



Similar documents
Software Development Standard Deliverables

This is the software system proposal document for the <name of the project> project sponsored by <name of sponsor>.

2003 Patricia Ensworth Page 1

Custom Software Development Approach

OE PROJECT CHARTER TEMPLATE

Why Test ITSM Applications for Performance? Webinar

FSW QA Testing Levels Definitions

Project Audit & Review Checklist. The following provides a detailed checklist to assist the PPO with reviewing the health of a project:

Net Developer Role Description Responsibilities Qualifications

WHITE PAPER. Effectively managing project performance reporting.

Terrace Consulting Services

Program Lifecycle Methodology Version 1.7

Subject Area 1 Project Initiation and Management

Green Migration from Oracle

Smarter Balanced Assessment Consortium. Recommendation

Project QA and Collaboration Plan for <project name>

SECTION 4 TESTING & QUALITY CONTROL

Re: RFP # 08-X MOTOR VEHICLE AUTOMATED TRANSACTION SYSTEM (MATRX) FOR MVC ADDENDUM #10

Software Quality Testing Course Material

Roadmap. Software Engineering. Software Engineering. Project Life Cycle. Database. Project Lifecycle

Statement and Confirmation of Own Work

Design Document Version 0.0

Laila TECHNICAL SKILLS

In this Lecture you will Learn: Development Process. Unified Software Development Process. Best Practice

SOFTWARE DEVELOPMENT PLAN

Project Lifecycle Management (PLM)

Appendix 2-A. Application and System Development Requirements

Project Implementation Process (PIP)

Real-time Data Replication

A Comprehensive Approach to Master Data Management Testing

VAIL-Plant Asset Integrity Management System. Software Development Process

Request for Proposal for Application Development and Maintenance Services for XML Store platforms

Test Plan Template: (Name of the Product) Prepared by: (Names of Preparers) (Date) TABLE OF CONTENTS

INFORMATION SECURITY POLICIES AND PROCEDURES: A PRACTITIONER'S REFERENCE, SECOND EDITION

MNLARS Project Audit Checklist

Life Cycle Quality Gates

Time Monitoring Tool Software Development Plan. Version <1.1>

<Company Name> <Project Name> Software Development Plan. Version <1.0>

Project Plan for <project name>

Process Improvement Plan

Application Management Services (AMS)

Chapter 6 Implementation Planning

Overview. Implementation of the international transaction log. Overall ITL role and approach. Support from ITL developer/operator

UDC Software Development Life Cycle

Construction Management System (CMS) Deliverable Review Process

Draft Document STATE OF MICHIGAN. SACWIS Planning Department of Human Services Strategic Implementation Plan: Project Staffing

Oracle Insurance Policy Administration System Quality Assurance Testing Methodology. An Oracle White Paper August 2008

SCI$U:'e$learning'for'patient'education'in'spinal'cord'injury'rehabilitation' Background'and'development'process' E$learning'in'patient'education'

8. Master Test Plan (MTP)

Implementing a SQL Data Warehouse 2016

SolovatSoft. Load and Performance Test Plan Sample. Title: [include project s release name] Version: Date: SolovatSoft Page 1 of 13

Project Management Planning

Project Start Up. Start-Up Check List. Why a Project Check List? What is a Project Check List? Initial Release 1.0 Date: January 1997

Configuration Management Plan

IT Project: System Implementation Project Template Description

Note to the Project Guides MSC (CS-FOSS) Final Semester Projects

VA ICJIS. Program Management Plan

Oakland County Department of Information Technology Project Scope and Approach

Custom Development Methodology Appendix

Development of the website for the Ministry of Foreign Affairs

Real Web Project Management : Case Studies and Best Practices from the Trenches Thomas J. Shelford Gregory A. Remillard

DIRECTIVE NUMBER: v2.0. SUBJECT: Correctional Integration Systems Change Management Plan

Oakland County Department of Information Technology Project Scope and Approach

LDAP Authentication Configuration Appendix

INTRODUCTION: Plan and Schedule Development Create a Work Breakdown Structure (WBS) The detailed guidelines and examples start on the following page.

Developing and Deploying Siebel ebusiness Applications

SECTION 2 PROGRAMMING & DEVELOPMENT

Implementing a Data Warehouse with Microsoft SQL Server 2012

Template K Implementation Requirements Instructions for RFP Response RFP #

Introduction and Overview

The Agile Audit. 2. Requirements & Technical Architecture

Project Plan 1.0 Airline Reservation System

System Development and Life-Cycle Management (SDLCM) Methodology

SYSTEMS ANALYSIS DESIGN

Software Engineering. Software Engineering. Software Costs

Project Management Guidelines

ecms Document Management Request for Proposal: Questions & Responses

A view on governance. SharePoint Kennisdelingsdag. Nick Stuifbergen, consultant 28 January 2011

Business Analysis From Yes-M Systems LLC Length: Approx 7 weeks/55 hours Audience: Students with or without IT experience or knowledge Student

SCHEDULE 8 Generalist Project Services Framework 2015

Software Process Training

PROJECT MANAGEMENT METHODOLOGY SECTION 3 -- PLANNING PHASE

Business white paper. Best practices for implementing automated functional testing solutions

IBM Rational DOORS Next Generation

A Comparative Study of Database Design Tools

Case Study. Software Product Reengineering, Maintenance, Support Services Java based Enterprise Product.

Architect, Data Warehousing and Business Intelligence. Information & Education Technology Services. Associate Director, Applications Development

COMMONWEALTH OF MASSACHUSETTS EXECUTIVE OFFICE OF HEALTH AND HUMAN SERVICES

Software Requirements Specification. Task Management System. for. Prepared by. Version 1.0. Group Name: Pink and Purple. Date:

Business Intelligence Tool Migration. Title: Domain: Client: Location:

Appeals Case Management System Project. Scope Management Plan. November 20, 2014

Security Incident Management Process. Prepared by Carl Blackett

Establish and maintain Center of Excellence (CoE) around Data Architecture

Transcription:

Software Development Standard Deliverables Lifecycle Methodology Created By Version 1.1 Narendranath June 13 2008 Development Lifecycle Methodology Document Control Change Record Date Author Revision Change Reference 09/18/2004 Narendranath 1 Initial Draft Reviewer Name Position Distribution Copy Number Name Location 1 Management SCR SOFT 2 Clients 3 Partners

june/13/2008pm SCR SOFT Proprietary and Confidential idevelopment Lifecycle Methodology june/13/2008pm SCR SOFT Proprietary and Confidential ii Table of Contents Document Control...i Change Record...i Reviewer...i Distribution...i PROJECT LIFECYCLE METHODOLOGY...1 Development Lifecycle Methodology Lifecycle Methodology LIFECYCLE STAGE DOC. NO. DELIVERABLE NAME OWNER DESCRIPTION P1: Business Proposal P1 Steering Committee Proposal Business Owner This is a high level document that approves the project and the goals of the project. 3 Summary 3 Cost 3 Impact (including tangible and intangible benefits) 3 Implementation Strategy (including dependencies, Risks and Resource conflicts) 3 References (identification of the people and documentation that can further support the project proposal). P2: Requirements Clarification P2 Requirements Document. 3 Definition of Terms (Glossary) 3 Biz Requirements (Mid Level) 3 Priorities 3 Process Flow Diagram

3 User experience (Number of users, security requirements etc.) 3 Success Criteria 3 Functionality not Required P3: Planning P3.1 Detailed FunctionalSpecification 3 Detailed Functional Specifications of each Module of the Application 3 Detailed Feature Requirements P3.2 High Level Plan Gantt Chart of high level project tasks. Should identify the different phases of the lifecycle and deliverables as milestones.

june/13/2008pm SCR SOFT Proprietary and Confidential 1Development Lifecycle Methodology LIFECYCLE STAGE DOC. NO. DELIVERABLE NAME OWNER DESCRIPTION P4: Design/Prototype P4.1 Infrastructure DesignDocument Dev Tech Lead 3 Physical Architecture 3 Network Architecture 3 Tools P4.2 Database Design Document Database Tech. Lead 3 Database scope (elaborate on items not discussed in the general scope and describe the scope in greater detail) 3 Data Flow Technical Architecture 3 Data Model Diagrams 3 Entity descriptions (including the descriptions of the columns and applicable business rules) 3 Database Capacity Planning Issues Issues 3 General Notes 3 Resolved 3 Unresolved 3 Appendix (may include the DDL for the Design version of the Data Models).

P4.3 Front-End/Middle TierDesign Document. UI Design Front- End/Middle Tier Tech Lead 3 UML Diagrams 3 Class Descriptions 3 GUI Mockups 3 Use Cases 3 Error Handling 3 Event Logging 3 APIs and Interfaces

june/13/2008pm SCR SOFT Proprietary and Confidential 2Development Lifecycle Methodology LIFECYCLE STAGE DOC. NO. DELIVERABLE NAME OWNER DESCRIPTION P5: Finalize Product Specification P6: Development None Conduct Review - Finalize All P1 P4 Documents As Necessary P6.1 Database DevelopmentSpecification Database Tech. Lead There are no documents to be produced for this stage. 3 Detailed ETL Design Doc, including field transformations 3 Low level data flow 3 Updated ERD and Specs 3 Unit Tested SQL and PL/SQL Code along with appropriate relase documentation. P6.2 Front/middle TierDevelopment Specs Front- End/Middle Tier Tech Lead 3 Unit tested code along with appropriate release documentation. 3 Update UML diagrams and documentation 3 Updated Functional Specifications. 3 Unit Tested SQL and PL/SQL Code along with appropriate relase documentation.

P6.3 Test Plan QA Lead 3 Detailed test plan for each module (based on User acceptance criteria Security considerations) 3 Separate sections for different types of testing to be conducted (Stress test, Performance Test, etc. inculding sub-sections for different modules to be tested).

june/13/2008pm SCR SOFT Proprietary and Confidential 3Development Lifecycle Methodology LIFECYCLE STAGE DOC. NO. DELIVERABLE NAME OWNER DESCRIPTION P7: Release Management & QA P7.1 QA Test Results QA Lead 3 Test Environment (including specifications for the Hardware, Software, and Network). 3 Integration Test results 3 Regression Test Results 3 Stress Test Results 3 Usability Test results 3 Data Validation. 3 Actual QA Scripts P7.2 Installation and Release Document Dev Tech Lead 3 Release Notes identifying important notes not included in the Development documents. 3 Installation Guide (identification of the steps to be taken to install, including specifying the set up of the environment for the software. 3 Migration plan 3 Other sections that may be specific to each project P8: Operations P8.1 Operations Manual Dev Tech Lead 3 Front-tier operations 3 Database operations 3 Monitoring Operations 3 Other sections that may be specific to each project. P8.2 SLA 3 Performance Requirements 3 Uptime Requirements 3 Maintenance Requirements

june/13/2008pm SCR SOFT Proprietary and Confidential 4Development Lifecycle Methodology LIFECYCLE STAGE DOC. NO. DELIVERABLE NAME OWNER DESCRIPTION P9: Debrief P9 Summary 3 Feedback 3 Areas For Improvement 3 Recommendations

june/13/2008pm SCR SOFT Proprietary and Confidential 5