FotoGazmic Software Project Plan Senior Project: CS 425 Spring 2003.

Slides:



Advertisements
Similar presentations
Anatomy of a Multimedia Project
Advertisements

Test Automation Success: Choosing the Right People & Process
Enterprise Resource Planning
McGraw-Hill/Irwin © 2006 The McGraw-Hill Companies, Inc. All rights reserved BUSINESS DRIVEN TECHNOLOGY Chapter Nineteen: Building Software to Support.
BUSINESS DRIVEN TECHNOLOGY
Transforming Organizations
 Every stage from phase DESIGN in Software Development Process will have “design document” especially in analysis and design phases.  “Design document”
Software Configuration Management
Project Integration Management Sections of this presentation were adapted from A Guide to the Project Management Body of Knowledge 4 th Edition, Project.
CS 501: Software Engineering
CS 221/ IT 221 Lecture 14 Software Engineering Dr. Jim Holten.
Nov. 13, 2003CS WPI1 CS 509 Design of Software Systems Lecture #11 Thursday, Nov. 13, 2003.
CS Techniques Supporting Project Management (Part 4) Bilgisayar Mühendisliği Bölümü – Bilkent Üniversitesi – Fall 2009 Dr.Çağatay ÜNDEĞER Instructor.
Supplement 02CASE Tools1 Supplement 02 - Case Tools And Franchise Colleges By MANSHA NAWAZ.
Using UML, Patterns, and Java Object-Oriented Software Engineering Chapter 3, Project Organization and Communication.
Systems Development (SD) Presentation Michael Webb IT Director for Medicaid Utah Department of Health UDOH Informatics Brownbag August.
Introduction to Systems Analysis and Design
Planning. SDLC Planning Analysis Design Implementation.
CHAPTER 19 Building Software.
Project Management and Scheduling
CEN Fourth Lecture Introduction to Software Engineering (CEN-4010) Instructor: Masoud Sadjadi Project Organization.
SDLC Phase 2: Selection Dania Bilal IS 582 Spring 2009.
This chapter is extracted from Sommerville’s slides. Text book chapter
Software Configuration Management (SCM)
CSI315 Web Technology and Applications
INFORMATION SYSTEM APPLICATIONS System Development Life Cycle.
Introduction to RUP Spring Sharif Univ. of Tech.2 Outlines What is RUP? RUP Phases –Inception –Elaboration –Construction –Transition.
1 Phase Implementation and Test Plan. Making your implementation plan First Steps  Consider your use case diagram and your prioritization of use cases.
Transaction Processing Systems and System Development Life Cycle
Page 1 MODEL TEST in the small GENERALIZE PROGRAM PROCESS allocated maintenance changes management documents initial requirement project infrastructure.
SIUE Injury Tracking System Project Plan. Team Members: Robbie Marsh Robbie Marsh –Project Manager/Webmaster Ken Metcalf Ken Metcalf –Lead Programmer.
Project Management : Techniques and Tools (60-499) Fall 2014 / Winter 2015.
Final Presentation – CS 425 Aaron O'Banion Todd Astroth Chris Cobb Matt Stowe Mark Williams.
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
Team Members David Haas Yun Tang Robert Njoroge Tom Kerwin Clients Facilities Management Don Anderson Rick Klein.
CS351/ IT351 Modeling and Simulation Software Engineering Dr. Jim Holten.
Boston University Project Management Association Website Development Group 3 Team3 CS632 Dr. Vijay Kanabar Team Members Mario Soto Emily Ziegler Kevin.
FotoGazmic Software (From left to right: Chad Zbinden, Josey Baker, Rob Mills, Myra Bergman, Tinate Dejtiranukul)
May05-36: Boone Cemetery Management Software Boone Cemetery Management Software May05-36 Greg Thede, Director, Boone Parks Department Dr. Kothari Joseph.
ISM 5316 Week 3 Learning Objectives You should be able to: u Define and list issues and steps in Project Integration u List and describe the components.
1 R.O.M.P Robot Orientation Mapping Project (Project Plan) Team Evolution Peri Subrahmanya: Lead Designer Michael Lazar: Project Manager Sean Hogan: Lead.
KS3 Phase4 Client Server Monitoring System October 1, 2008 by Stephen, Seema, Kam, Shpetim.
FreeShell Live Final Presenation Jonathan Birch | Greg Chabala | Bryan Kimbro | Mark Sparks.
IS Analysis and Design. SDLC Systems Development Life Cycle Break problems into management review stages Control cost and time Works best with well understood.
Bernd Bruegge & Allen Dutoit Object-Oriented Software Engineering: Conquering Complex and Changing Systems 1 Software Engineering November 7, 2001 Project.
SE503 Advanced Project Management
Software Engineering 1 Object-oriented Analysis and Design Applying UML and Patterns An Introduction to Object-oriented Analysis and Design and Iterative.
PRJ566 Project Planning & Management Software Architecture.
Scott Wilson Shaun Moats Arjun Shrestha Andrew Garrison.
Connecting with Computer Science2 Objectives Learn how software engineering is used to create applications Learn some of the different software engineering.
Lecture 2 System Development Lifecycles. Building a house Definition phase Analysis phase Design phase Programming phase System Test phase Acceptance.
Overview of Socio-cognitive Engineering General requirements Theory of Use Design Concept Contextual Studies Task model Design space System specification.
Timesheet training Version: Introduction Duration: 1.5 hours Purpose: Guide on how to use Timesheet.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
1 CP586 © Peter Lo 2003 Multimedia Communication Multimedia Development Team.
Matt Tempia Chris Thomas Thomas Taylor Jeffrey Tansey.
Project Plan Document By: Aaron O’Banion Mark Williams Chris Cobb Todd Astroth Matt Stowe.
Project Life Presented by Chuck Ray, PMP ITS Project Manager.
CS646: Software Design and Architectures Introduction and Overview †  Definitions.  The general design process.  A context for design: the waterfall.
Configuration & Build Management. Why Software Configuration Management ? The problem: Multiple people have to work on software that is changing More.
IS&T Project Reviews September 9, Project Review Overview Facilitative approach that actively engages a number of key project staff and senior IS&T.
Managing the Project Lifecycle
Transforming Organizations
Engineering Processes
Course: Module: Lesson # & Name Instructional Material 1 of 32 Lesson Delivery Mode: Lesson Duration: Document Name: 1. Professional Diploma in ERP Systems.
Introduction to Software Engineering (CEN-4010)
Engineering Processes
Project Integration Management
System Analysis and Design:
Presentation transcript:

FotoGazmic Software Project Plan Senior Project: CS 425 Spring 2003

Overview Objective Objective Easily Correct Color and Density of TIFF Images Easily Correct Color and Density of TIFF Images Two Main Features: Two Main Features: Automatic Density Correction Automatic Density Correction Color Correction Color Correction Discussion Discussion Client – Bernard Waxman Client – Bernard Waxman SIUE SIUE Photographer Photographer Wants a system that would allow users to easily correct the color and density of TIFF images Wants a system that would allow users to easily correct the color and density of TIFF images

Process Plan Evolutionary Delivery w/Risk Management Spiral (beginning) Evolutionary Delivery w/Risk Management Spiral (beginning) Client – Early Prototype Client – Early Prototype Early Discovery Early Discovery Difficulties with Specific Features Difficulties with Specific Features Delivery Delivery Product with the Most Important Functionality Product with the Most Important Functionality

Process Plan (cont.)

Definition Process Timeline

Process Plan (cont.) Design Process Timeline

Process Plan (cont.) Acceptance Tesitng Timeline

Process Plan (cont.) Installation Testing Timeline

Process Plan (cont.) System Release Timeline

Organization Plan Dr. Xudong Yu Upper Management Dr. Bernard Waxman Client

Test Plan Module Testing Module Testing Each Code Module Each Code Module Integration Testing Integration Testing Individual Components Individual Components Modules that are Dependent or Related to One Another Modules that are Dependent or Related to One Another

Test Plan (cont.) System Testing System Testing Ensure Functional and Nonfunctional Requirements Ensure Functional and Nonfunctional Requirements Includes Functional and Performance Testing Includes Functional and Performance Testing Acceptance Testing Acceptance Testing Internal Acceptance Test Internal Acceptance Test Team Members Team Members Acceptance Test with Client Acceptance Test with Client

Change Management Plan Baselines Baselines Problem Specification – Requirements Analysis Doc. Problem Specification – Requirements Analysis Doc. Design Specification – Project Design Doc. Design Specification – Project Design Doc. Who May Propose Changes? Who May Propose Changes? Fotogazmic Members Fotogazmic Members Rob Mills, Josey Baker, Myra Bergman, Tinate Dejtiranukul, and Chad Zbinden. Rob Mills, Josey Baker, Myra Bergman, Tinate Dejtiranukul, and Chad Zbinden. Client Client Bernard Waxman Bernard Waxman Upper Management Upper Management Professor Xudong Yu Professor Xudong Yu

Change Management Plan (cont.) All team members must review the proposed change and make recommendations before adoption All team members must review the proposed change and make recommendations before adoption Decisions will be based on the impact on Decisions will be based on the impact on Project Goals Project Goals Timelines Timelines All change requests will be documented All change requests will be documented

Change Management Plan (cont.) Investigators Report: Investigators Report: A summary of the proposed changes A summary of the proposed changes The name of the person requesting the change The name of the person requesting the change Classification of the change Classification of the change Impact on schedules Impact on schedules Recommendations for the proposed change Recommendations for the proposed change

Change Management Board Membership Membership All members of the FotoGazmic Team All members of the FotoGazmic Team When It Meets When It Meets When each member has been notified of the change request When each member has been notified of the change request How it operates How it operates Discuss request and it’s impact Discuss request and it’s impact Vote Vote Tie vote – Project Manager decides Tie vote – Project Manager decides

Documentation Plan One member will be responsible for writing each assigned document One member will be responsible for writing each assigned document All members review and edit document together All members review and edit document together Completed documents placed on FotoGazmic website Completed documents placed on FotoGazmic website Upper Management receives copy of document Upper Management receives copy of document Revisions will be made based on recommendations from Upper Management Revisions will be made based on recommendations from Upper Management

Commercial Break

Training Plan C++ C++ Microsoft Foundation Class (MFC) Microsoft Foundation Class (MFC) Open Source TIFF libraries Open Source TIFF libraries

Training Plan (cont.) Internal Training Internal Training Training team members – as needed Training team members – as needed Group Group Individual Individual Coding Languages Coding Languages C++ C++ Reading code and consulting books or online sources Reading code and consulting books or online sources Visual Basic Visual Basic Not planned, but possible choice for front-end interface Not planned, but possible choice for front-end interface

Training Plan (cont.) Non-Technical Training Non-Technical Training Management techniques Management techniques Upper Management will train team leader in how to oversee their particular project responsibilities Upper Management will train team leader in how to oversee their particular project responsibilities External Training External Training Installing Software Installing Software Standard Setup Package Standard Setup Package Using the System Using the System Online Help System Online Help System User Manual User Manual

Review and Reporting Plan Internal Reviews Internal Reviews Definition Process Review Definition Process Review At the end of the definition process At the end of the definition process Review the RAD and Project Plan Review the RAD and Project Plan Design Process Review Design Process Review At the end of the design process At the end of the design process Review the SDD and ODD Review the SDD and ODD Programming Process Review Programming Process Review At the end of the programming process At the end of the programming process Analyze program integration results Analyze program integration results

Review and Reporting Plan (cont.) Internal Reviews Internal Reviews System Test Process System Test Process At the end of the system test process At the end of the system test process Review all documentation produced Review all documentation produced Review system test results Review system test results Postmortem Review Postmortem Review When the project has been successfully completed When the project has been successfully completed Discuss overall project Discuss overall project Review project steps Review project steps

Review and Reporting Plan (cont.) External Reviews External Reviews Preliminary Design Review Preliminary Design Review Midway in Design Process, after internal review Midway in Design Process, after internal review Review and analyze validity of design approach Review and analyze validity of design approach Design Review Design Review At the end of the Design Process At the end of the Design Process Review the design specification and Project Plan Review the design specification and Project Plan Acceptance Review Acceptance Review At the end of the Acceptance Process At the end of the Acceptance Process Review acceptance test results Review acceptance test results

Review and Reporting Plan (cont.) Reports Generated by Non-managers Reports Generated by Non-managers Frequency: When needed. Frequency: When needed. To: Section Manager To: Section Manager Format: Technical Status Report. Format: Technical Status Report. Scope: A report at the end of any major task as needed. Scope: A report at the end of any major task as needed. Reports Generated by Section Managers Reports Generated by Section Managers Frequency: When needed. Frequency: When needed. To: Project Manager To: Project Manager Format: Technical Status Report Format: Technical Status Report Scope: A report at the end of each completed milestone by the manager responsible for that phase. Scope: A report at the end of each completed milestone by the manager responsible for that phase. Reports Generated by Project Manager Reports Generated by Project Manager Frequency: Bimonthly. Frequency: Bimonthly. To: Upper Management. To: Upper Management. Format: Technical Status Report. Format: Technical Status Report. Scope: Two reports a month to keep upper management updated on the status of the project. Scope: Two reports a month to keep upper management updated on the status of the project.

Installation and Operation Plan Installation Installation Standard setup package Standard setup package Installation Responsibility Installation Responsibility FotoGazmic team – development phase FotoGazmic team – development phase Client – after client accepts product Client – after client accepts product Schedule Schedule Meeting with client Meeting with client Demonstrate installation Demonstrate installation

Installation and Operation Plan (cont.) Operation Responsibility Operation Responsibility FotoGazmic team – currently FotoGazmic team – currently User – after software release User – after software release Maintenance and Tuning Responsibility Maintenance and Tuning Responsibility The development team The development team Duration of Responsibilities Duration of Responsibilities FotoGazmic team – until the release of the system FotoGazmic team – until the release of the system Client – after the release of the system Client – after the release of the system

Questions?