1. Biosolid Project Brief Requirement Spec February 24, 2005

2. Overview Introduction Project Overview Requirements Elicitation Functional Requirements Non-Functional Requirements Requirements Modeling Summary

3. Introductions Clients –Jianpeng Zhou (Jim) Ph.D. U Of British Columbia Civil Engineering –Shunfu Hu Ph.D. Arizona State Geography Biosolid Team –Dan McAfee (Project Lead) –John Stephen –Erik Rottier –Chris Middleton

4. Project Overview Wastewater Biosolid Information –Wastewater Biosolids? –Information collection mandated by federal regulation –Recording & Reporting - Current Limitations Manual paper-based systems Limited computer systems –Excel/Access Direct –Simple stand-alone systems using Access Manual collection of data (paper or computer media)

5. Project Overview Cont… Analysis of Wastewater Biosolid Information –Current Limitations Manual Compilation of Data Limited System Analysis beyond off-the- shelf products –Geographic Information System (GIS) Links Spatial (Geographic) data with Attribute Data (e.g. soil composition, topology, building info) Not Currently Available for Biosolid Information

6. Project Overview Cont… Wastewater Biosolids Information Management System (WBIMS) –System Prototype: “Proof-of-Concept” for Clients Goal 1: Automate data collection of wastewater biosolid information for distributed users Goal 2: Provide GIS analysis capabilities for collected data –Link Wastewater Biosolid Information to Regional Geography

7. Requirements Elicitation Meeting #1 with Drs Hu and Zhou – Qualify Assumptions – Answer Questions Meeting #2 with Dr Hu –ArcView Demonstration and Introduction –Follow Up To Cover Requirements Meeting #3 with Dr Zhou – Follow Up To “Fill In The Gaps”

8. Functional Requirements Credential Verification Ability to Input Biosolid Information Analysis Capability Ability to draw (as illustrated on following 3 slides ) –Buildings –Topology –Biosolid Views

9. Digital Area Orthophoto Locations of Collinsville wastewater treatment facility (displayed as green anchor) and sites of Biosolid land applications (displayed as red outline) superimposed on digital orthophoto for the area.

10. Digital Soil Map Locations of Collinsville wastewater treatment facility (displayed as green anchor) and sites of Biosolid land applications (displayed as red outline) superimposed on digital soil map.

11. Land Use/Cover Map Locations of Collinsville wastewater treatment facility (displayed as yellow anchor) and sites of Biosolid land applications (displayed as red outline) superimposed on the land use and land cover map

12. Non-Functional Requirements Usability - keep typing to a minimum, On-Line Users Manual Reliability - minimal data loss/system downtime Performance - concurrent users Supportability - EPA office, federal system, other OS support Interface – Web Access

13. Non-Functional Requirements Cont… Implementation –Biosolids Data Management System (BDMS) EPA approved system Mandated by client for wholesale inclusion into this project Will provide the ‘SubmitInfo’ structure to the new system Drafts adherence from those who presently use the BDMS –ArcView topology drawing application Geography Department uses Mandated by the client Will provide the ‘ViewInfo’ structure to this project Keeps current topology and building drawing capability Supports demonstration capabilities to IEPA representatives

14. Use Case Model Graphical/Biosolid System Treatment Plant Personnel EPA Personnel Public Health Education Researchers SubmitInfo ViewInfo 1 1 1 1 1 2 2 2 2 3 3 3 3 3 3 3 3 BDMS System ArcView System Includes Login

15. Use Case - ViewInfo Participating actor: EPA, Treatment Plant, Public Health and Education personnel will need to view Biosolid information along with topology. Entry condition: Actor selects ‘ViewInfo’ selection from the main menu screen. Flow of events: 1.Data Categories Menu Appears on Screen. 2.Actor selects category of information to view 3.Actor clicks on ‘draw’ icon/button. 4.Categories selected appears on screen. 5.Actor can zoom in, zoom out, change map center from function keys 6.Actor can exit back to Menu Menu Screen of system 7.Actor can exit application (logout) Exit Condition: Actor can exit at any point in the application

16. Use Case - SubmitInfo Participating actor: Treatment Plant / EPA Actors will be able to submit Biosolid information. Entry condition: Actor is logged into the WBIMS system. Flow of events: 1.Actor selects SubmitInfo 2.System displays data entry form. 3.Actor enters data required by form, and clicks submit 4.System validates entries – checks all required fields present, any formatted entries (e.g. dates) are in proper format 5.Actor selects to save data. 6.System challenges actors choice 7.Actor responds yes and data is saved to database, no and no data is saved yet. 8.System displays result notification. If additional forms exist for info being submitted, system displays form, go to step 3. 9.Once all forms have been completed and registered system puts Actor back at first BDMS screen. 10.Actor selects option to put more information in, goes to step 4 11.Actor selects to exit back to main menu screen, system puts back main menu screen 12.Actor selects exit, system exits. Exit condition: Actor logged into the WBIMS system. Submitted data saved in database. Special requirements: Application will need to keep track of the number of forms, the current form, current information on that form and be able to delete all information input by Actor if Actor requests that option.

17. Object Model – Class Diagram + Login () - UserId: string ( idl ) : - UserType: string ( idl ) : - FacilityAgency: string ( idl ) User + Submit () + Cancel () - FormId: long ( idl ): - DataElements: object ( idl ) : DataForm + Validate () : boolean ( idl ) + SaveUpdate () : boolean ( idl ) + Get() : object ( idl ) - ElementId : long ( idl ): - Caption : string ( idl ): - Value : string ( idl ): - Format : string ( idl ): DataElement + UpdateView() - ViewId : long (idl ) : - DataElements : object ( idl ): - GeoCoordinates : object ( idl ): DataView 1 * C o n s i s t s of 1*Consists of Uses 1* U s e s * 1 C o n s i s t s o f 1 * + Get () : object ( idl ) - ElementId : long ( idl ) - Description : string ( idl ): GeoData

18. Dynamic Model – Activity Diagram Log In SubmitInfoViewInfo Main Menu ArcView SystemBDMS EPA Personnel Waste Water Treatment Personnel Educators and Public Health Main Menu SubmitInfo ViewInfo BDMSArcView System ViewInfo ArcView System

19. Dynamic Model – State Diagram SubmitInfo RetrieveForm SubmitForm ModifyDB Complete? No Yes DisplayConfirm SubmitInfo Termination SubmitInfo Initialization ValidateForm Valid? No

20. Dynamic Model – State Diagram ViewInfo DisplayMap ZoomMap ViewInfo Initialization QueryLocationAnalysis Analysis: it contains many statistical analysis functions – not yet defined. Query: it involves searching for specific locations on the map. AdjustLayer Dependent on the current displayed map. (Analysis may need to be INSIDE DisplayMap). ViewInfo Termination

21. Summary Reason for Project Requirements Elicitation Functional Requirements Non-Functional Requirements Requirements Models

22. Questions?