ProjectDeliverables.CEN6016.Fall2007.Del5

ProjectDeliverables.CEN6016.Fall2007.Del5 -...

Info iconThis preview shows pages 1–8. Sign up to view the full content.

View Full Document Right Arrow Icon
Project Project     Deliverables Deliverables Deliverable 5 Posted (revised 11/12/2007) Version Numbers will reflect added Deliverable numbers.  
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Overview of Guidance Overview of Guidance I shall try to upgrade / refine guidance for  each deliverable as we progress.   Please view this file often as it will change. Suggestions for clarity and/or consistency  are always  welcome.
Background image of page 2
Format of Deliverables Format of Deliverables All Deliverables will be via CD.   Outside :  Surface of CD is to clearly indicate  your course number and the team number, as              CGS 4308 - Team 1 or CIS 4327 – Team 1.   Also include the project title. Inside : Each deliverable will be in a separate  folder on the  same CD , so when I access the  CD, all I should see are individual folders with  labels such as Deliverable n, as in Deliverable 4. This way, I can also see enhancements to previous  deliverables. 
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Contents of Folder  Contents of Folder  Each Folder (i.e., Deliverable) is to  contain  Management Folder: a number of Word files discussed ahead Artifacts Folder Contents discussed ahead.
Background image of page 4
Management Folder Documents (1 of 3) 1. Team Num file In this file, you are to simply (may be a single Word file) : List the names of the team members  Indicate who is team leader with phone number . Indicate who is the software quality analyst and phone List individual email accounts.   2.  Iteration Plan  (Include for CIS second semester  deliverables) Note that the Iteration Plan will change for each  deliverable, that is, it will be refined and ‘extended .’  Each successive deliverable will contain a ‘revised’  Iteration Plan. 
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Management Folder Documents (2 of 3) 3.  Executive Summary   Single page document;  Summarizes the contents of this  folder.  What ‘activities’ were undertaken What ‘artifacts’ were changed and rationale Note:  revising artifacts is the norm  in an iterative  approach to software development.  What  new  ‘artifacts’ were produced   Must include signatures  of EACH team member that  he/she has reviewed and has ‘bought off’ on the contents  of this deliverable.  (signatures may be virtual) If you have not read and personally reviewed the contents  of the deliverable, do not sign this form !
Background image of page 6
Management Folder Documents  (3 of 3)  4.  Team Activities : Team Software Process (TSP), and  Personal Software Process (PSP) Forms 5.  Software Quality Analyst Report This will address in narrative or graphic form (your choice) the 
Background image of page 7

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Image of page 8
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 52

ProjectDeliverables.CEN6016.Fall2007.Del5 -...

This preview shows document pages 1 - 8. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online