2/21/2006 SaintSoft: Detailed Design 1 Environmental Monitoring System Detailed Design by Saint Soft

2/21/2006SaintSoft: Detailed Design2 Welcome Mr. Kenneth Swarner Computer Science System Administrator, Siena College & Dr. Timoth Lederman Dr. Timoth Lederman Professor of Computer Science, Professor of Computer Science, Siena College Siena College

2/21/2006SaintSoft: Detailed Design3 Saint Soft Team Organization David Moore – Team LeaderDavid Moore – Team Leader Hannah Palmer – Project ManagerHannah Palmer – Project Manager Daniel Schuldt – Development ManagerDaniel Schuldt – Development Manager Christian Damberg – Testing ManagerChristian Damberg – Testing Manager Lioubov Mikhailova – Development EngineerLioubov Mikhailova – Development Engineer Tina Ting – Testing EngineerTina Ting – Testing Engineer

2/21/2006SaintSoft: Detailed Design4Agenda Introduction – David Moore Introduction – David Moore Prototypes – Daniel Schuldt / Hannah Palmer Prototypes – Daniel Schuldt / Hannah Palmer Data Structures – David Moore Data Structures – David Moore Test Plan – Christian Damberg Test Plan – Christian Damberg Conclusion and Questions – David Moore Conclusion and Questions – David Moore

2/21/2006SaintSoft: Detailed Design5 Prototypes Hannah Palmer / Daniel Schuldt

2/21/2006SaintSoft: Detailed Design6 Log In Screen

2/21/2006SaintSoft: Detailed Design7 Password Recovery

2/21/2006SaintSoft: Detailed Design8 First Registration Screen

2/21/2006SaintSoft: Detailed Design9 Second Registration Screen

2/21/2006SaintSoft: Detailed Design10 Third Registration Screen

2/21/2006SaintSoft: Detailed Design11 Initial Sensored User Screen

2/21/2006SaintSoft: Detailed Design12 Register Sensor Screen

2/21/2006SaintSoft: Detailed Design13 Sensored User Screen

2/21/2006SaintSoft: Detailed Design14 Sensored User Screen Continued

2/21/2006SaintSoft: Detailed Design15 Sensor Alert Screens

2/21/2006SaintSoft: Detailed Design16 Device Options Screens

2/21/2006SaintSoft: Detailed Design17 User Profile Screen

2/21/2006SaintSoft: Detailed Design18 Remote User Screens

2/21/2006SaintSoft: Detailed Design19 Remote User Screens Continued

2/21/2006SaintSoft: Detailed Design20 Administrator Screens

2/21/2006SaintSoft: Detailed Design21 Administrator Screens Cont.

2/21/2006SaintSoft: Detailed Design22 Admin Location Screen

2/21/2006SaintSoft: Detailed Design23 Change Screen

2/21/2006SaintSoft: Detailed Design24 Change Password Screen

2/21/2006SaintSoft: Detailed Design25 Disable/Enable Sensor Screen

2/21/2006SaintSoft: Detailed Design26 Query Result Screen

2/21/2006SaintSoft: Detailed Design27 Data Structures David Moore

2/21/2006SaintSoft: Detailed Design28 Data Structures User Info Table  This table will store the personal information from the registration page during the new user registration process. The personal information will include the user’s assigned username, name, password and the primary telephone number

2/21/2006SaintSoft: Detailed Design29 Data Structures Location Info Table  This table will store the information related to the users’ various locations, the table will use the combination of user id and location name to identify the correct row and will store address information, the IP address and the phone number and address related to that location as well as the last time the user logged in from that location

2/21/2006SaintSoft: Detailed Design30 Data Structures Sensor Information  This table will store the information received from the sensors and will be stored based on the combination of user id and location name. The table will include the most recently received readings for temperature, smoke, light, humidity, water, sound, air flow, and the most recently received snapshot captured from the camera. The table will also store the user-defined thresholds related to each reading.

2/21/2006SaintSoft: Detailed Design31 Relationship Diagram

2/21/2006 SaintSoft: Detailed Design 32 Test Plan Christian Damberg

2/21/2006SaintSoft: Detailed Design33 What Will Be Tested  The graphical user interfaces will be tested to assure functionality.  The relationship between the software and database will be tested, ensuring that information transfers correctly.  The relationship between the software and sensors will be tested, ensuring that information is retrieved correctly.  The ability of the software to respond in the appropriate manner to the information delivered from the sensors.

2/21/2006SaintSoft: Detailed Design34 Unit Test Example

2/21/2006SaintSoft: Detailed Design35 Test Plan Overview  Approach We have appointed a Testing Manager as well as a Testing Engineer who’s main responsibilities will be to carry out the testing process. We have appointed a Testing Manager as well as a Testing Engineer who’s main responsibilities will be to carry out the testing process.  Deliverables We will deliver the Acceptance Test, including completed Unit Tests as well as Error Reports and Resolutions. We will deliver the Acceptance Test, including completed Unit Tests as well as Error Reports and Resolutions.  Pass / Fail Criteria The minimum goal is to meet all functional requirements set by the client. The minimum goal is to meet all functional requirements set by the client.  Schedule The Acceptance Test/Testing Process is scheduled to be completed by May 1 st. The Acceptance Test/Testing Process is scheduled to be completed by May 1 st.

2/21/2006 SaintSoft: Detailed Design 36 Conclusion David Moore

2/21/2006SaintSoft: Detailed Design37 Development Schedule Fall Semester

2/21/2006SaintSoft: Detailed Design38 Development Schedule Spring Semester

2/21/2006SaintSoft: Detailed Design39 Project Plan Software Plan Analysis Preliminary Design Detailed Design Development And Testing Acceptance Test - Completed - In Progress - Incomplete Fall 2005 Spring 2006

2/21/2006SaintSoft: Detailed Design40 Thank You! Any Questions?