Progress Report 9/22/2011-10/25/2011 Prepared by Matthew Rasler, Andrew Habegger, Mark Parker The Egg Flow Communicator Group.

Slides:



Advertisements
Similar presentations
Calyxinfo Walking through Calyx Info The Organisation.
Advertisements

Requirements Management & Communication Chapter 4
PROCESS FRAMEWORK Lecture - 3. Topics covered PROCESS FRAMEWORK PROCESS MODELS DIFFERENCE.
The Egg Flow Communicator Matthew Rasler Andrew Habbeger Mark Parker.
Ch 3: Unified Process CSCI 4320: Software Engineering.
Welcome and Questions?. Agenda: Component 6: Procedures for Record Keeping and Decision Making Plan for roll-out Team Presentations Completion of Workbook.
1 Marvel Electronics and Home Entertainment e-Commerce System Final Status Report April 12, 2005 (Tuesday)
UML Static diagrams. Static View: UML Component Diagram Component diagrams show the organization and dependencies among software components. Component:
Improving Process for Better Software. Who We Are An experiential learning program that provides technology solutions for our partners, and real- world.
Chapter 15 Design, Coding, and Testing. Copyright © 2005 Pearson Addison-Wesley. All rights reserved Design Document The next step in the Software.
4. 2Object-Oriented Analysis and Design with the Unified Process Objectives  Explain the elements of project management and the responsibilities of a.
1 REQUIREMENTS ENGINEERING and SYSTEMS ANALYSIS Elements and Definitions.
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
CSC230 Software Design (Engineering)
IS&T Project Management: How to Engage the Customer September 27, 2005.
Project Management and Scheduling
Chapter 6– Artifacts of the process
PMP® EXAM PREPARATION COURSE – DAY ONE 1 Based on PMBOK® Guide 4th Edition + Revisited August 30th of 2011 “PMI”, “PMP”, “Project Management Professional”
Miguel Nunes Information Systems Project Management IS Project Resources.
CMM Level 3 KPA’s CS4320 Fall Organizational Process Focus (Goals) Software process development and improvement activities are coordinated across.
Project Management: Madness or Mayhem
Distributed Monitoring and Mining Advisor: Dr. Stuart Faulk Team: Ahmed Osman, Isaac Pendergrass, Shail Shimpi, Tom Mooney OMSE-555/556 Software Engineering.
Module 8: Risk Management, Monitoring and Project Control We would like to acknowledge the support of the Project Management Institute and the International.
Project Management Process Overview
Roles and Responsibilities
Unified Software Development Process (UP) Also known as software engineering process SEP describes how requirements are turned into software Defines who,
CSI315 Web Applications and Technology Overview of Systems Development (342)
RUP Fundamentals - Instructor Notes
Software Testing Life Cycle
SIUE Injury Tracking System Project Plan. Team Members: Robbie Marsh Robbie Marsh –Project Manager/Webmaster Ken Metcalf Ken Metcalf –Lead Programmer.
Multimedia & Communications ATMEL Bluetooth Background information on Bluetooth technology ATMEL implementation of Bluetooth spec.
Rational Unified Process Fundamentals Module 4: Disciplines II.
Foundations of Geospatial System Development Todd S. Bacastow Professor of Practice for Geospatial Intelligence John A. Dutton e-Education Institute The.
Resources Performance time. resources Performance time 2.
Computers Are Your Future © 2006 Prentice Hall, Inc.
RUP Design RUP Artifacts and Deliverables
Software Requirements Engineering CSE 305 Lecture-2.
IT Requirements Management Balancing Needs and Expectations.
September 3, 2013 Project on Inventory Control System (PICS) P.I.C.S
T Project Review X-tremeIT I1 Iteration
Webster Visualize Webster Financial Team Visual Scrumware Joe Andrusyszyn Mark Bryant Brian Hannan Robert Songer.
These materials are prepared only for the students enrolled in the course Distributed Software Development (DSD) at the Department of Computer.
SYSTEMS ANALYSIS AND DESIGN LIFE CYCLE
Nick Small, Shawn Boughey, Karolina Latkoska SPQM / SEP 1.
PMCenter Project SPRING 2004 MOSP Team GEO. 2 Agenda Introduction Semester Goal Project Management ­Iteration Plan ­Risk Management ­Process Handbook.
Develop Project Charter
These materials are prepared only for the students enrolled in the course Distributed Software Development (DSD) at the Department of Computer Science.
Introduction A strategy was required to be able to maintain desktop configuration and reduced support cost. Hardware and software capabilities continually.
Reconfigurable Communication Link Between FASTER and RTSim Interface Matthew McCollum Mark Krause Derek Keibler.
J. Scott Hawker p. 1Some material © Rational Corp. Rational Unified Process Overview See and use the RUP Browser on lab machines.
MNP1163 (Software Construction).  SDLC and Construction Models  Construction Planning  Construction Measurement.
Phase 3 The Software Requirements Specification. After review of the customer’s System Spec. After educated analysis Preliminary design A technical, software.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Chapter 3 Managing the Information Systems Project 3.1.
PPTTEST 12/26/ :41 1 IT Ron Williams Information Technology Management Project Management.
Project Management Project Integration Management Minder Chen, Ph.D. CSU Channel Islands
ACS 560 M ICROBLOG 911 P ROJECT S TATUS Kassie M. Bowman November 29, 2011.
Team X Review. The members of Team X propose to develop a therapeutic activity system using a Microsoft Surface unit and a Windows 7 desktop. By working.
Rational Unified Process (RUP)
Foundations of Geospatial System Development Todd S. Bacastow Professor of Practice for Geospatial Intelligence John A. Dutton e-Education Institute The.
Monica Gloudemans Ekaterina Schwartz Gloudemans/Schwartz ACS 560 CMAP.
1 Sean Aluoto Anthony Keeley Eric Werner. 2 Project Plan Overview Project Lifecycle model Time line Deliverables Organization plan Risk management Design.
Milestone Two – Reach Across Houston (RAH) Tuesday, June 14, Team:Matthew Edwards Thomasina Coates Michelle Graham James Henrydoss James McNicholas.
Review of Definitions Software life cycle: –Set of activities and their relationships to each other to support the development of a software system Software.
The Software Development Process. Contents  Product Components  Software project staff  Software development lifecycle models.
Roles and Responsibilities
Important info Assessment Semester 1: Coursework 1 (Component 1, 2)
Serial Data Hub (Proj Dec13-13).
Chapter 1 (pages 4-9); Overview of SDLC
Integration project Dynamics 365.
NOTICE! These materials are prepared only for the students enrolled in the course Distributed Software Development (DSD) at the Department of Computer.
Presentation transcript:

Progress Report 9/22/ /25/2011 Prepared by Matthew Rasler, Andrew Habegger, Mark Parker The Egg Flow Communicator Group

Project Management Plan V1.0 Internal Structure Sponsor/ Customer/ Tim Habegger, Proprietor of Hardware Developer- Habegger Poultry Project Supervisor-Professor Tanik Project Manager/ Low Level Programmer/ Assistant Application Architect/ System Analyst Backup-Matthew Rasler Assistant Project Manager System Designer/ Hardware Developer/ Customer Interface-Andrew Habegger Assistant System Designer System Analyst/ Programmer-Mark Parker

DeliverableRecipientsDelivery DateDelivery MethodComments Module Driver SoftwareDevelopment Team and Sponsor November, 2012Software provided Includes both on Module PBASIC software and PC communication driver Programmed Hardware Module PrototypeDevelopment Team and Sponsor November, 2012Hardware provided Pre-Requisite is Module Driver Software Programmed Hardware ModulesCustomer/SponsorMay, 2012Integrate into existing components Pre-Requisites are Module Driver Software and Module Prototype Application ArchitectureProject Team/Program Manager 9/7/2011 /CmapAssigned to Andrew Habegger/ Backups: Mark Parker and Matthew Rasler GUICustomer/SponsorMay, 2012Integrate into existing components Pre-Requisite is Module Driver Software Vision DocumentProject Team/Program Manager 9/16/2011 /CmapSections Distributed amongst team members by Project Manager SRS V1.0Project Team/Program Manager 9/23/2011 /CmapAssigned to Matthew Rasler/Mark Parker SRS v2.0Project Team/Program Manager 9/25/2011 /CmapSections Distributed amongst team members by Project Manager FR-DP DecompositionProject Team/Program Manager 9/29/2011 /CmapSections Distributed amongst team members by Project Manager Design MatrixProject Team/Program Manager 9/29/2011 /CmapAssigned to Project Manager FMEA/RISK ReportProject Team/Program Manager 10/3/2011 /CmapAccomplished by group during team meeting PMP V1.0Project Team/Program Manager 10/10/2011 /CmapAssigned to Matthew Rasler/Andrew Habegger Project Management Plan V1.0 Deliverables

Project Management Plan V2.0 Deliverables Version 2 PMP V2.0(this) Project Team/Program Manager 10/19/2011 /CmapAssigned to Matthew Rasler/Andrew Habegger IEEE 1016 Project Team/Program Manager 10/31/2011 /CmapAssigned toMatthew Rasler/Mark Parker UML Diagram Project Team/Program Manager 10/25/2011 /CmapAssigned to Andrew Habegger/Matthew Rasler House Of Quality Project Team/Program Manager 10/25/2011 /CmapAssigned to Mark Parker/Matthew Rasler Type of CommunicationCommunication Schedule Typical Communication Mechanism Who InitiatesRecipient Status Reportevery Fridayteam meeting face to faceProject ManagerProject Team Schedule and Effort Tracking Report weekly /CMap/BasecampProject ManagerProgram Manager Project ReviewAt infrequent intervalsIn class and via Program Manager/Project Sponsor Project Team Requirement Changesas changes are approvedVia client interfaceProject SponsorProject Team Information or Knowledge Collected When information or knowledge is collected Team meeting face to face and Team MemberOther Team Members Communication, Tracking, and Reporting Plan

FMEA/RISK

Hardware Constraining Software Specifications Why? Specific Hardware Requires Specific Software Specific Software Requires Specific Staff-Training, Staffing to Appropriate, and Factors in to Feasibility Assessment Factors: Microcontroller runs PBASIC Communication Channel to UART driven by C Communication Standards are defined by Communication Protocols RS232, RS485, USB Elaborating: Revisit and Revise Application Architecture Revisit and Revise Design Matrix Revisit and Revise SRS, involving newly defined constraints Dedicate Training Time for Software Education

Hardware Constraining Software Specifications

House Of Quality (QFD)

Application Architecture V3.0 With Refined Functional Requirements

Systems Architecture

UML