Transcript ppt - SIUE
Biosolid Design Spec Brief April 21, 2005 Overview • Design Overview • Proposed System Architecture • User Interface • Subsystem Interfaces • Package & File Organization • Class Interfaces Design Overview Wastewater Biosolids Information Management System (WBIMS) Geographically Distributed Users Web Browser Web Browser EPA Personnel Web Browser Wastewater Treatment Facility Personnel General Public (e.g. Public Health, Researchers, Interested People ) INTERNET Operating System ( - Windows XP GIS Server System Web Server DBMS System WBIMS Web App Database (GIS & Biosolid Data) Server • High-level approach to implementing WBIMS – Proof-of-concept Prototype – Single Hardware Server ▪ Web Server, DBMS, GIS, & WBIMS custom software Design Overview Continued… • 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 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 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 2 - BDMS Biosolid Input Capability Web Access Login System Main Menu Graphical Display Capability 3 – ArcIMS/ 1 – Front End Exit ArcGIS Topological & Biosolid Database 4 – Combined DB Subsystem Decomposition Cont. • Concurrency – Full concurrency • Coupling – Loose coupling • Cohesion – Uncertain cohesion 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 Biosolid System Mapping Client Browser ( Internet ) : Web Server : BDMS System : Server : Web Server : Routing Subsystem : Biosolid Login : SQL Server / : Consolidated DB Main Menu : Web Server : ArcGIS System Hardware/Software Mapping • 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 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 Biosolid Access Control Matrix ACTORS OBJECTS EPA viewBiosolids viewTopology alterBiosolidInformation inputBiosolidInformation Waste Water Treatment Plant Personnel viewBiosolids viewTopology inputBiosolidInformation General Public – Other Interested Parties (e.g. Public Health, Educators, Researchers) viewBiosolids viewTopology 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 Boundary Conditions Continued.. • 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 User Interface Log In Waste Water Treatment Personnel Main Menu Treatment Plant Personnel 1 EPA Personnel Main Menu Educators and Public Health Main Menu Graphical/Biosolid System BDMS System 2 3 Includes EPA Personnel 2 1 2 SubmitInfo 2 3 1 Login General Public 3 1 Submit Info ViewInfo Submit Info ViewInfo ViewInfo 3 3 3 ViewInfo Includes ArcView System BDMS ArcView System BDMS ArcView System Navigation Paths ArcView System Actors 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 – 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 User Class Form Class Attributes Attributes - UserId : string (s15) (PK) - UserPass : string (s15) - UserPermit : int (n) - UserAgency : string (s30) - FormId : int (n) (FK) - FormId : int (n) (PK) - FormField : string (s20) 1 * Methods + Submit () + Cancel () Methods + Challenge () + Login () + ViewInformation () + InputBiosolidInfo () + Exit () A cc e s ses ArcGIS System A cce sses + UpdateBiosolidInfo () BDMS System Summary • Design Overview • Proposed System Architecture • User Interface • Subsystem Interfaces • Package & File Organization • Class Interfaces Questions?