Biosolid Design Spec Brief April 21, 2005

Overview Design Overview Proposed System Architecture User Interface Subsystem Interfaces Package & File Organization Class Interfaces

Design Overview GeographicallyDistributed Users Operating System - ( Windows XP Web Server DBMS System GIS Server System S Q L / S t o r e d P r o c s INTERNET EPA Personnel Wastewater Treatment Facility Personnel General Public(e.g.Public Health, Researchers,Interested People) Web Browser WBIMS Web App Server Web Browser High-level approach to implementing WBIMS – Proof-of-concept Prototype – Single Hardware Server ▪ Web Server, DBMS, GIS, & WBIMS custom software Database (GIS & Biosolid Data) Wastewater Biosolids Information Management System (WBIMS)

System Architecture Style –3-Tier System Architecture A Logical vs. Physical Distinction –User Services (1) »Client script & Html served up by ASP.Net –Business Services (2) »Code-behind (C#) & GIS scripting –Data Services (3) »Stored Procedures, SQL –4 Primary Functional Areas Web Front End “Submit Info” Sub-system (BDMS) “View Info” Sub-system (ArcGIS) Database Back End Design Overview Continued…

Design Goals –Performance As a “Selling Point” (e.g. Not “Noticeably Slow”) Long-term Concurrent User Requirements Beyond Scope –Dependability Move from MS Access to MS SQL Server Goal of “Mature System” –Cost Minimal – Take Advantage of Existing Resources Final Prototype May Be Used in Pursuing Grants/Funding –Maintenance Seek to be User-Admin Maintainable –End User Criteria Existing Systems (BDMS, ArcGIS, Windows) –Ease of Use Within Known Context “CS321 Wisdom” Design Tradeoffs –Feature Set vs Delivery Time Time Inflexible: Feature Set LOSES! Document Feature Reductions for Future System Evolution Design Overview Continued…

Proposed System Architecture Subsystem Decomposition Hardware / Software Mapping Persistent Data Management Access Control & Security Global Software Control Boundary Conditions

Subsystem Decomposition Web Front End Biosolid Input System Graphical Display System MS SQL Server Database Back End Login Web Access System Main Menu Graphical Display Capability Topological & Biosolid Database Biosolid Input Capability Exit 1 – Front End 2 - BDMS 3 – ArcIMS/ ArcGIS 4 – Combined DB

Concurrency –Full concurrency Coupling –Loose coupling Cohesion –Uncertain cohesion Subsystem Decomposition Cont.

Hardware/Software Mapping Routing Subsystem runs on the Server Biosolid Login & Main Menu runs on the Web Server BDMS System runs on the Web Server ArcGIS System runs on the Web Server Consolidated Database is housed on the SQL Server

Windows Server 2003 Operating System is the software platform for the routing subsystem Microsoft IIS system provides the web accessibility to the Login/Main Menu, BDMS system and ArcGIS system ArcGIS is supported by the ArcIMS web display system BDMS is supported by.ASP Web forms Hardware/Software Mapping

Persistent Data Management This project uses a relational database for all persistent data instantiation. BDMS system uses forms with fields that can be saved directly to the database. ArcGIS uses tables to determine the topology and means to graphically portray the display. Each data access system will be shifting from direct data access (Microsoft Access) to an indirect access via Microsoft SQL Server DBMS. –This layering will protect the data from concurrent users, system shutdowns and other various data risk activities.

Access Control and Security

Global Software Control Event Driven System –User access –User selections In Time, Procedure Driven Functions –Analysis coding –Alert processing

Boundary Conditions Web Front End –Configuration 2 Forms: Login, System Main Menu –Startup and Shutdown Validate Username and Password Exit Selection Option –Error User has to Relink and Relogin BDMS Subsystem –Configuration Main BDMS Menu form, 5 Initial Forms, Rest of BDMS –Startup and Shutdown User can select to Exit User can navigate back to System Main Menu –Error User can save at any point (Form pointers is saved) User has to Relink and Relogin User will be able to go back to last saved point

ArcGIS Subsystem –Configuration Standalone Program Web Interfaced via ArcIMS –Startup and Shutdown Accessed through System Main Menu User Can Navigate back to System Main Menu via back arrow User can Exit with Exit Selection Option –Error User has to Relink and Relogin Database Subsystem –Configuration Same Table Names as previous Access Database Installed in MS SQL Database –Startup and Shutdown None –Error Weekly Backups to Prevent Data Corruption Boundary Conditions Continued..

User Interface Graphical/Biosolid System Treatment Plant Personnel EPA Personnel General Public SubmitInfo ViewInfo BDMS System ArcView System Includes Login Log In Submit Info ViewInfo Main Menu ArcView System BDMS EPA Personnel Waste Water Treatment Personnel Educators and Public Health Main Menu Submit Info ViewInfo BDMS ArcView System ViewInfo ArcView System Navigation PathsActors and Actions

User Interface - Login

User Interface – System Main Menu

User Interface – BDMS Data Entry

User Interface - BDMS Data Entry

User Interface – BDMS Data Entry

User Interface – ArcIMS Top View

UI – ArcIMS Drill County View

UI – ArcIMS Drill Map View

UI – ArcIMS Drill Area View

User Interface – ArcGIS View3

Subsystem Interfaces User’s Browser interfaces with Web Front End Web FrontEnd interfaces –To BDMS subsystem –To ArcGIS subsystem BDMS Subsystem Interfaces with SQL DB ArcGIS Subsystem Interfaces with SQL DB

Packages & File Organization Section 2.2 provides a package representation of the system The packages WBIMS requires are: –Database –Web Content –ArcGIS (including ArcIMS) File organization of code will center around Web Front-End –File organization of the database is handled internally. –The web content is managed by the team –The web content will be organized in the ‘www’ folder on the server in hierarchical structure separating the authentication pages from the BDMS modeled pages from the ArcGIS interface. The ArcGIS file structure is being investigated. –Early speculation suggests that ArcGIS will be running in the background and will simply make the requests and interpretations required of the ArcIMS interface.

Class Interfaces Attributes Methods User Class 1 * Methods Attributes Form Class A c c e s s e s ArcGIS System + Submit () + Cancel () + Challenge () + Exit () - FormId : int (n) (PK) - FormField : string (s20) + Login () + ViewInformation () + InputBiosolidInfo () + UpdateBiosolidInfo () - UserId : string (s15) (PK) - UserPass : string (s15) - UserPermit : int (n) - UserAgency : string (s30) - FormId : int (n) (FK) A c c e s s e s BDMS System

Summary Design Overview Proposed System Architecture User Interface Subsystem Interfaces Package & File Organization Class Interfaces

Questions?