Biosolid Project Plan Brief March 22, 2005. Overview Stakeholders Project Organization Development Process Hardware and Software Requirements Deliverables.

Slides:



Advertisements
Similar presentations
Principles of Information Systems, Tenth Edition
Advertisements

Scrum Team Management System (Scream) Christopher Jolly Alexander Kivaisi Cliff Siyam.
1 Information Systems Development (ISD) Systems Development Life Cycle Overview of Analysis Phase Overview of Design Phase CP2236: Information Systems.
Software Engineering CSE470: Process 15 Software Engineering Phases Definition: What? Development: How? Maintenance: Managing change Umbrella Activities:
Systems Analysis & IT Project Management Pepper. System Life Cycle BirthDeathDevelopmentProduction.
Systems Development Life Cycles. The Traditional Systems Development Life Cycle.
8/28/2005ECEN5543 Req Elicitation1 Targets of Requirements Engineering ECEN 5543 SW Engineering of Standalone Programs University of Colorado, Boulder.
Database Administration
Fundamentals of Information Systems, Second Edition
Chapter 5: Project Scope Management
Principles of Information Systems, Sixth Edition 1 Systems Investigation and Analysis Chapter 12.
8 Systems Analysis and Design in a Changing World, Fifth Edition.
MSIS 110: Introduction to Computers; Instructor: S. Mathiyalakan1 Systems Investigation and Analysis Chapter 12.
Defining the Activities. Documents  Goal Statement defines why helps manage expectations  Statement of Work what gets delivered defines scope  Software.
Project Management and Scheduling
Database Administration Chapter 16. Need for Databases  Data is used by different people, in different departments, for different reasons  Interpretation.
Chapter 13 Organizing Information System Resources MIS Department Centralization and Decentralization Outsourcing Computer Facilities and Services.
CryptKeeper Project Plan 1 CryptKeeper Project Plan.
Project Management Chapter 5, PG 92. Introduction Why is software management particularly difficult?  The product is intangible Cannot be seen or touched.
RUP Requirements RUP Artifacts and Deliverables
Module 12 Installing and Upgrading to SharePoint 2010.
STREAM LINING CROSS CONNECTION SURVEYS USING POCKETPCs
2Object-Oriented Analysis and Design with the Unified Process Objectives  Explain the purpose and various phases of the traditional systems development.
Dillon: CSE470: SE, Process1 Software Engineering Phases l Definition: What? l Development: How? l Maintenance: Managing change l Umbrella Activities:
Maintaining Information Systems Modern Systems Analysis and Design.
Software Testing Life Cycle
Software Project Planning CS470. What is Planning? Phases of a project can be mostly predicted Planning is the process of estimating the time and resources.
Incell Phonium Processor Project Plan Document Dale Mansholt Aaron Drake Jon Scruggs Travis Svehla.
SIUE Injury Tracking System Project Plan. Team Members: Robbie Marsh Robbie Marsh –Project Manager/Webmaster Ken Metcalf Ken Metcalf –Lead Programmer.
The Systems Development Methodologies. Objectives  Describe the information Systems Development Life Cycle (SDLC)  Explain prototyping  Explain Rapid.
Requirements Information and data which need to be displayed or accessible to the user Sitemapping (Site Map) Flow Chart models of site structure displaying.
Team Members David Haas Yun Tang Robert Njoroge Tom Kerwin Clients Facilities Management Don Anderson Rick Klein.
Introduction to Interactive Media The Interactive Media Development Process.
Principles of Information Systems, Sixth Edition Systems Design, Implementation, Maintenance, and Review Chapter 13.
TestFiles Life Cycle Architecture Chris Byszeski Ooi Hsu Han Amir Kouretchian Sachin Pradhan Quang Tran Peter Turschmid Nick Walker.
Project Scope Management Project management Digital Media Department Unit Credit Value : 4 Essential Learning time : 120 hours.
Project Plan for nSite Central Michael Dunn Ryan Sessions Kyle Kerrigan.
1 R.O.M.P Robot Orientation Mapping Project (Project Plan) Team Evolution Peri Subrahmanya: Lead Designer Michael Lazar: Project Manager Sean Hogan: Lead.
Chapter 7 Applying UML and Patterns Craig Larman
Slide 1 Project Management Chapter 4. Slide 2 Objectives ■ Become familiar with estimation. ■ Be able to create a project workplan. ■ Become familiar.
Principles of Information Systems, Sixth Edition Systems Design, Implementation, Maintenance, and Review Chapter 13.
KS3 Phase4 Client Server Monitoring System October 1, 2008 by Stephen, Seema, Kam, Shpetim.
Physics Project Management Chin-Sung Lin Eleanor Roosevelt High School.
2 Information Systems Chapter 12 Systems Development: Investigation and Analysis.
Principles of Information Systems, Sixth Edition Systems Investigation and Analysis Chapter 12.
Fundamentals of Information Systems, Second Edition 1 Systems Development.
Database Administration
Chapter 6 CASE Tools Software Engineering Chapter 6-- CASE TOOLS
Principles of Information Systems, Sixth Edition Systems Investigation and Analysis Chapter 12.
Microsoft Project Reporting with Reporting Services.
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.
Principles of Information Systems, Sixth Edition 1 Systems Design, Implementation, Maintenance, and Review Chapter 13.
Software Project Management (SEWPZG622) BITS-WIPRO Collaborative Programme: MS in Software Engineering SECOND SEMESTER /1/ "The content of this.
Facilimange Dynamics aka “Facilies” CS 425 Final Presentation Curtis McKay Manneet Singh Brad Vonder Haar.
Lesson 3-Multimedia Skills. Overview Members of a multimedia team. Roles and responsibilities in a multimedia team.
Your Online Exchange for buying and selling remnants or odd sizes of production materials Trina L. Anderson UC College of Applied Science December 2003.
Project Manager:PATS Project Manager Estimator:Peter Project Manager Start Date:1/1/2010 PATS Software PATS Project Team.
Week 7 Lecture Part 2 Introduction to Database Administration Samuel S. ConnSamuel S. Conn, Asst Professor.
Biosolid Design Spec Brief April 21, Overview Design Overview Proposed System Architecture User Interface Subsystem Interfaces Package & File Organization.
Biosolid Project Brief Requirement Spec February 24, 2005.
Biosolid Project Brief May 3, Overview Introduction Requirements Project Plan Design.
Biosolid Project Presentation Dec 12, 2005 The Team Programmers Dan McAfee Chris Middleton Erik Rottier John Stephen Clients Dr Shunfu Hu Dr Jianpeng Zhou.
1 Sean Aluoto Anthony Keeley Eric Werner. 2 Project Plan Overview Project Lifecycle model Time line Deliverables Organization plan Risk management Design.
Schedule. ArcIMS/GIS - Chris Accomplishments –Research on Google Maps API –Research on ArcIMS SDE (Spatial Database Engine) direct connect Next Steps.
Milestone Two – Reach Across Houston (RAH) Tuesday, June 14, Team:Matthew Edwards Thomasina Coates Michelle Graham James Henrydoss James McNicholas.
Fundamentals of Information Systems, Sixth Edition
CASE Tools and Joint and Rapid Application Development
Project management 102 – PLANNING
Chapter 12 Systems Development: Investigation and Analysis
Presentation transcript:

Biosolid Project Plan Brief March 22, 2005

Overview Stakeholders Project Organization Development Process Hardware and Software Requirements Deliverables and Deadlines Efforts and Schedule Measurements Risk Management Ethical Considerations

Stakeholders EPA Personnel Wastewater Treatment Facility Personnel Public Health Personnel Educators Management Biosolid Team

Project Organization John Stephen [Web Master] Front End (Primary) BDMS (Alt) Erik Rottier BDMS (Primary) Front End (Alt) Chris Middleton ArcGIS (Primary) Database (Alt) Dan McAfee [Project Leader] Database (Primary) ArcGIS (Alt) Team Organized to SubProjects Team Organized for SubProject Backup

Project Organization Cont… Login Web Access System Main Menu Graphical Display Capability Topological & Biosolid Database Biosolid Input Capability Roles – Taken on By All - SubProject Attack –Analyst –Documenter –Designer –Coder –Tester Exit 1 – Front End 2 - BDMS 3 – ArcGIS 4 – Combined DB

Development Process (DP) Process Model Development Issues –Methodologies –Policies –Standards –Tools Configuration Management Test Plan –Unit Testing –Integration Testing –System Testing

DP – Process Model Waterfall Model with SubProjects Problem Statement Requirements Elicitation Architectual Design System Testing Detailed Design WBIMS Front End Detailed Design WBIMS Database Detailed Design WBIMS BDMS Restructure Detailed Design WBIMS ArcGIS Upgrade Code/Debug WBIMS Front End Code/Debug WBIMS Database Code/Debug WBIMS BDMS Restructure Code/Debug WBIMS ArcGIS Upgrade Subsys Testing WBIMS Front End Subsys Testing WBIMS Database Subsys Testing WBIMS BDMS Restructure Subsys Testing WBIMS ArcGIS Upgrade

DP – Development Methodologies Some Object Oriented Design Re-Engineering of Existing Systems Mostly Relational Database Backend

DP – Development Policies Minimum Policy Position Focus is on Communication Informal Review Primary Area Expertise Alternate Area Interest/Help

DP – Development Standards/Tools Programming Standards –Naming Conventions –Source File –Function Header –Code Comments Tools –Visual Studio.NET

Configuration Management Change Initiators Deliverable Documentation Project Website Content Source Code Database Artifacts Informal Notes

Test Plan Unit Testing –SubProject Dependent –Involve Primary Programmer Integration Testing –Between SubProjects –Between SubProject Primarys System Testing –Total System Testing –Involving Entire Team

HW/SW Requirements Server ArcIMS 9.0 ArcGIS 9.0 Microsoft SQL Server 2000 Microsoft IIS BDMS System Digitized Map Database of Illinois

Deliverables & Deadlines Initial Prototype – 29 April 2005 –Web Accessible –NonExclusionary Login –Simple Main Menu Screen –Limited BDMS Input Capability –Limited Topology/Biosolid Display Capability Full-Featured Prototype – 5 December 2005 –Challenge Login –Complete BDMS Input Capability –Complete Topological/Biosolid Display Capability

Measurements Team Meeting Minutes Individual Time Logs MS Project of Schedule –Task Breakdown –Resource Assignments –% Complete Checking

Efforts and Schedule

Efforts & Schedule cont…

Risk Management Upfront Learning Curve Inadequate Design/Base Systems Overly Optimistic Schedule Feature Creep Personnel Issues Hardware and Software Issues

Risk Management Table Early acquisition; Configuration Management; Schedule Changes Low Hardware/Software Issues Re-assignment of work; reduce feature set; managerial guidance ModeratePersonnel Issues Further analysis; adherence to specificationsModerateFeature Creep Include time buffers; reduce feature setModerate Overly Optimistic Schedule Review and re-designHigh Inadequate Design or Base Systems Seek guidance; reduce feature set; revert to known technologies HighUpfront Learning Curve Risk Resolution Risk Probability Potential Risk

Ethical Considerations Licensing with Use of BDMS System –Licensing assumes ownership –University of Florida developed BDMS –SIUE may get challenged on licensing/ownership Money for System –Money for Maintenance is Sound –Profit Could be Challenged by U of F –Any Money Could Be Seen as Profit

Summary Stakeholders Project Organization Hardware and Software Requirements Deliverables and Deadlines Efforts and Schedule Measurements Risk Management Ethical Considerations

Questions?