Software Development Plan

Slides:



Advertisements
Similar presentations
Chapter 7: Key Process Areas for Level 2: Repeatable - Arvind Kabir Yateesh.
Advertisements

System Construction and Implementation Objectives:
Chapter 3 Project Initiation
Network Design and Implementation
NEES Project Management Workshop June 16 June 18 1 Segment 2.
Copyright 2006 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Third Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Fundamentals of Information Systems, Second Edition
Effort in hours Duration Over Weeks Or Months Inception Launch Web Lifecycle Methodology Maintenance Phases Copyright Wonderlane Studios.
Chapter 3 Project Initiation. The stages of a project  Project concept  Project proposal request  Project proposal  Project green light  Project.
Prepared by Long Island Quality Associates, Inc. ISO 9001:2000 Documentation Requirements Based on ISO/TC 176/SC 2 March 2001.
Defining the Activities. Documents  Goal Statement defines why helps manage expectations  Statement of Work what gets delivered defines scope  Software.
Project Management and Scheduling
ASME C&S Training Module B5 MODULE B - PROCESS SUBMODULES B1. Organizational Structure B2. Standards Development: Roles and Responsibilities B3. Conformity.
Chapter 9. Intro  What is Project Management?  Project Manager  Project Failures & Successes Managing Projects  PMBOK  SDLC Core Process 1 – Project.
Bodil Mose Pedersen, DHI Status for implementering af ”Quality Manual”
QUALITY MANAGEMENT SYSTEM ACCORDING TO ISO
Revenue Cycle Management Medical Technology Acquisition and Assessment Team Members: Joseph Dixon, Michael Morotti, Mari Pirie-St. Pierre, David Robbins.
Chapter 22 Systems Design, Implementation, and Operation Copyright © 2012 Pearson Education, Inc. publishing as Prentice Hall 22-1.
Copyright 2002 Prentice-Hall, Inc. Chapter 3 Managing the Information Systems Project Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
BIS310: Structured Analysis and Design Introduction and Systems Planning Week 1.
S/W Project Management
The Key Process Areas for Level 2: Repeatable Ralph Covington David Wang.
CHAPTER 5 Infrastructure Components PART I. 2 ESGD5125 SEM II 2009/2010 Dr. Samy Abu Naser 2 Learning Objectives: To discuss: The need for SQA procedures.
SQA Architecture Software Quality By: MSMZ.
Pre-Project Activities Text Chapters 5 and 6. Pre-Project Activities 1.Contract Review 2.Development Plan 3.Quality Plan.
CCSB223/SAD/CHAPTER141 Chapter 14 Implementing and Maintaining the System.
Typical Software Documents with an emphasis on writing proposals.
Server Virtualization: Navy Network Operations Centers
The Planning Process Copyright, 2006 © L. Ouyang Liubo Ouyang Personal Software Process Lecture 11.
Software Quality Assurance Activities
Unit 8 Syllabus Quality Management : Quality concepts, Software quality assurance, Software Reviews, Formal technical reviews, Statistical Software quality.
Lecture #9 Project Quality Management Quality Processes- Quality Assurance and Quality Control Ghazala Amin.
FCS - AAO - DM COMPE/SE/ISE 492 Senior Project 2 System/Software Test Documentation (STD) System/Software Test Documentation (STD)
S Q A.
1.  Describe an overall framework for project integration management ◦ RelatIion to the other project management knowledge areas and the project life.
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Chapter 3 Systems Planning and Selection 3.1.
Strong9 Consulting Services, LLC 1 PMI - SVC I-80 Breakfast Roundtable Monthly Meeting Thursday, October 12, :00 am – 9:00 am.
Effective Project Management: Traditional, Agile, Extreme Presented by (facilitator name) Managing Complexity in the Face of Uncertainty Ch08: How to Close.
1 1.0 Introduction- ( Extensions of SRS) 1.1 Purpose 1.2 Scope 1.3 Definition and Acronyms `1.4 References ( extensions of SRS) Table of Contents for the.
CMM Level 2: Repeatable Copyright, 2000 © Jerzy R. Nawrocki Quality Management.
Develop Project Charter
WGISS /09/2015 DATA PRESERVATION – CNES APPROACH B. Chausserie-Laprée.
Fundamentals of Information Systems, Second Edition 1 Systems Development.
Chair of Software Engineering Exercise Session 6: V & V Software Engineering Prof. Dr. Bertrand Meyer March–June 2007.
Chapter 12 The Network Development Life Cycle
Bina Nusantara 19 C H A P T E R SYSTEM CONSTRUCTION AND IMPLEMENTATION.
1 Systems Implementation Introduction  The chapter will address the following questions:  What is the systems implementation process in terms of the.
~ pertemuan 4 ~ Oleh: Ir. Abdul Hayat, MTI 20-Mar-2009 [Abdul Hayat, [4]Project Integration Management, Semester Genap 2008/2009] 1 PROJECT INTEGRATION.
David M. Kroenke and David J. Auer Database Processing Fundamentals, Design, and Implementation Appendix B: Getting Started in Systems Analysis and Design.
EN EUROPEAN COMMISSION Budgetary Control Committee of European Parliament Budgetary Control Committee of European Parliament Brian Gray DG BUDGET Workshop.
SwCDR (Peer) Review 1 UCB MAVEN Particles and Fields Flight Software Critical Design Review Peter R. Harvey.
Pertemuan 14 Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
1 Definition Introduction and key stages Steps and standards used Plan Team Characteristics Implementation documentation Reviews & Audit Software Quality.
6/6/ SOFTWARE LIFE CYCLE OVERVIEW Professor Ron Kenett Tel Aviv University School of Engineering.
Milestone Two – Reach Across Houston (RAH) Tuesday, June 14, Team:Matthew Edwards Thomasina Coates Michelle Graham James Henrydoss James McNicholas.
Welcome. Contents: 1.Organization’s Policies & Procedure 2.Internal Controls 3.Manager’s Financial Role 4.Procurement Process 5.Monthly Financial Report.
Presenter: Igna Visser Date: Wednesday, 18 March 2015
Introduction for the Implementation of Software Configuration Management I thought I knew it all !
Software Quality Control and Quality Assurance: Introduction
Software Verification and Validation
Software Requirements
Description of Revision
Chapter 4 Systems Planning and Selection
Quality Management Systems – Requirements
ISO/IEC IEEE/EIA Software Life Cycle Processes Supporting Life Cycle Processes IEEE Supporting Processes.
Quality Measurable characteristic Cyclomatic complexity Cohesion
1 Stadium Company Network. The Stadium Company Project Is a sports facility management company that manages a stadium. Stadium Company needs to upgrade.
System Construction and Implementation
Project Progress Summary - Week 18
3. Software Quality Management
Presentation transcript:

Software Development Plan We will review these items involving the SDP

Table of Contents for the SDP (Software Development Plan) General Contents A. Project Organization B. Project Deliverables C. Environment D. Reviews, measurements, payments, V&V E. Odds and Ends We will review these items involving the SDP

Table of Contents for the SDP (Software Development Plan) 1. Introduction 2. Resources and Scheduling 3. Organization and Staffing 4. WBS 5. Technical Management and Control Here begins the sections of the SDP There will be an interoduction A section on the resources for this project – thats your team resources The scheduling when what deliverables have to be turned in What your organization looks like What the WBS looks like The technical management control

Table of Contents for the SDP (Software Development Plan) 6. Standards and Procedures Reviews, Audits, and Walkthroughs Development Environment Technical Performance Measurements 10. Documentation

Table of Contents for the SDP (Software Development Plan) 11. Verification and Validation 12. Maintenance 13. Human Factors 14. Delivery, Installation and Acceptance 15. Appendices and References

Table of Contents for the SDP I. Introduction Summary of Contents of SDP document Scope and Purpose of SDP Document System Level Project Description System Description

Table of Contents for the SDP Summary of Contents of SDP document TOC Scope and Purpose of SDP Document This document will be used to plan project …. Or get funding….. Or write the RFP System Level Project Description This project will……. System Description This system will Note: the project description has to do with the project not the system The system description describes the system

Table of Contents for the SDP 2. Resources and Scheduling How many people needed? What type of people? How long will it take to do this project? How long will each person be needed?

Table of Contents for the SDP 2. Resources and Scheduling This project will need x# users, y# dp staff There will be one communications specialist, one data specialist, one unix specialist, one capacity manager, one xxxxx user 4 managers, ….. This project will begin …. And end ….. Person A needed during weeks of etc

Table of Contents for the SDP 3. Organization and Staffing Who are the people needed? How will the Staffing be organized How are the users organized? Who pays? Who knows?

Table of Contents for the SDP 3. Organization and Staffing The organizational chart for the project will be as follows: Contractor will pay for travel, meeting rooms…...

Table of Contents for the SDP 4. WBS Week by week, who will be needed when? How much time will be devoted? How much will this cost?

Table of Contents for the SDP 5. Technical Management and Control How will change management be done? How will risk be managed? How will cost be contained? How will issues be resolved?

Table of Contents for the SDP 5. Technical Management and Control Changes to specification will be done by submitting a change report, approval of change by xyz committee, and scheduling of change. Risk will be reviewed by the xyz committee each month. Formal risk reports are due to jkl committee quarterly. Cost reports will be given to mno committee each week for review by xxx manager. All issues will be reviewed at the project management meeting. Issues which delay development schedules will be resolved by the rst committee.

Table of Contents for the SDP 2. Risk Models Approach to Risk Assessment 1. Identify areas of potential risk 2. Partition each risk area into manageable factors 3. Examine the Consequences of Failures 4. Determine Management Strategy to Manage Risk Avoidance Prevention (control) Transfer Knowledge and Research

Table of Contents for the SDP 6. Standards and Procedures What deliverable standard will be used What development methodology? What is the deliverable acceptance standard?

Table of Contents for the SDP 6. Standards and Procedures Deliverables will be prepared according to the Summit methodology. All deliverables will be submitted using standard UML. Deliverables will be reviewed by the developers and upon approvals users, management committee, steering committee and final signature by project sponsor.

Table of Contents for the SDP 7. Reviews, Audits, and Walkthroughs How will deliverables be reviewed? Who will perform auditing? Who will perform walkthroughs? What is the approval process?

Table of Contents for the SDP 7. Software Reviews Design Reviews Design and Coding Checks Management Reviews Project Checkpoints concerned with costs, plans, schedules Quality Reviews Technical reviews of quality of deliverable products, standards adherence, documentation End Product of Reviews No Action, Refer for Repair, Reconsider overall product

Table of Contents for the SDP (Software Development Plan) 8. Development Environment The system will be developed using the IBM 3090 mainframe running AIX and Dell Pentium micro computers running windows NT. The development environment will be the same except micros will run windows 95.

Table of Contents for the SDP 9. Technical Performance Measurements How fast will response time be? How fast will database access be? How many transactions per sec? How many terminals on at one time? What is the MTBF?

Table of Contents for the SDP Performance Evaluation Number of simultaneous users Number of Connections Number of Files Size of Tables Number of Open Files Number of Records Number of Transactions per interval Response Time Amount of data processed in a time unit Database Accesses per time unit Reliability Availability Backup/Recovery CPU Utilization Memory Utilization I/O Channel Utilization Software Utilization Terminals Supported External Devices Supported Table of Contents for the SDP

Table of Contents for the SDP 9. Technical Performance Measurements Each transaction will have < 10 sec response time. Each database will be completed within 10 ms. The system will process 600 transactions per sec with 4500 terminals on line. MTBF will be > 1 hour on the average.

Table of Contents for the SDP (Software Development Plan) 10. Documentation Documentation of existing system Documentation of attempts to do this Documentation of all letters, memos Documentation of deliverables

Table of Contents for the SDP (Software Development Plan) 11. Verification and Validation Deliverables will be verified for conformance with standards using by the QA group. Deliverables will be validated by the xxx user and rmm development committees

Table of Contents for the SDP 12. Maintenance Approximately 30 hours per month of maintenance is expected approximately one year after turnover. How much maintenance is expected? The system will need 1 Computer Manager, 1 User Manager, and 5 computer programmers assigned. Maintenance environment will be the same as development.

Table of Contents for the SDP 13. Human Factors There are 3000 users in the group who will need training from computer literacy to usage of the system. A culture change management play will be needed to train the people in the new method of doing business and the computer technology to support this new method.

Table of Contents for the SDP 14. Delivery, Installation and Acceptance What is considered delivered? How will we install? What is considered accepted?

Table of Contents for the SDP 14. Delivery, Installation and Acceptance The system will be considered delivered when each of applications is validated by the user group. We will roll out installation by each congressional district. The system will be considered accepted when 4 districts are installed and when one billing cycle has been completed.