1. Biosolid Project Plan Brief March 22, 2005

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

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

4. 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

5. 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

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

7. 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

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

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

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

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

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

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

14. 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

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

16. Efforts and Schedule

17. Efforts & Schedule cont…

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

19. 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

20. 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

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

22. Questions?