1 / 20

Team Members David Haas Yun Tang Robert Njoroge Tom Kerwin

Team Members David Haas Yun Tang Robert Njoroge Tom Kerwin. Clients Facilities Management Don Anderson Rick Klein. Introduction of the System. The purpose of our project is to develop web-based interfaces to access records in a Microsoft Access database

mayten
Download Presentation

Team Members David Haas Yun Tang Robert Njoroge Tom Kerwin

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Team Members • David Haas • Yun Tang • Robert Njoroge • Tom Kerwin Clients • Facilities Management • Don Anderson • Rick Klein

  2. Introduction of the System • The purpose of our project is to develop web-based interfaces to access records in a Microsoft Access database • The interfaces will be used for adding, editing and deleting records in the database tables. • Specific queries of multiple tables will also be created • The system’s main purpose is to keep track of the usage of rooms at all four SIUE campuses

  3. Database Tables • User • Campus • Non-Assignable Structure • Assignable Structure • Usable-Area Rooms • Floor • SFC Cross Ref • Department • Class Room Equipment • Multi-Use Classroom • Ownership Status • Hourly Lease • Owner • Tenant

  4. Queries • Department Ownership of a Usable Area • Square Footage of a Usable Area • Total Square Footage of Usable Areas Used by a Department • Times of Use of a Multi-Use Class Room • Square Footage of an assignable Structure • Interior and Exterior Square Footage of a Floor

  5. Life Cycle Model • Saw Tooth Model

  6. Process Plan • -Understanding the customer and the customer’s needs • -Choosing the most appropriate project tools • -Clarifying requirements with the customer • -Plan the design of the system • -Prepare for testing • -Prepare for programmer training

  7. Organization Plan • Basic Organization Erin Harris Upper Management David Haas Project Manager Don Anderson Main client contact Tom Kerwin Lead Analyst/Designer Yun Tang Lead Tester Robert Njoroge Lead Programmer • Project Manager – Organizes most aspects of the project • Lead Analyst – Proper definition of the system from the client • Lead Designer – Leads the design phase of the project • Lead Programmer – Assigns programming assignment to others • Lead Tester – Coordinates the testing of the entire system

  8. Change Management Plan • Baselines • -Requirements Analysis Document • -System Design Document • Proposing a Change • -Team Members • -Clients • Proposed Changes Will Be Investigated • Change Management Board • Implementing a Change

  9. Schedule CS425 Timeline

  10. CS499 Timeline

  11. Testing Plan • Unit Testing – • Tries to find faults in participating component (i.e. objects and /or subsystems) • Testing on the individual module to make sure it performs its function correctly before they are integrated with other modules • Unit testing should be done on chunks that are as small as possible • Those small chunks are most of the time implementation-specific • Integration Testing – • To make sure that the tested components work properly together • Use either top-down or bottom-up or some combination to combine the tested modules into groupings • Using black box and white box testing, each module will be tested with the modules with which they interface

  12. Testing Plan (cont.) • System Testing – • Testing all the components together; • Testing the entire system as a whole , with all modules included, and insure it functions work properly; • Testing through a combination of black box and white box testing. • This will be done in an environment as close as possible to that of the client’s. • Acceptance Testing & installation testing – • Testing the system under the condition, which are agreed by the client • To check the requirements against the project agreement • It should be done by client, if necessary with support by the developers

  13. Testing Plan (cont.) • Testing Tools • Microsoft Visual Studio. NET • Microsoft Access • Microsoft ASP.NET • Responsibility • David Haas, Tom Kerwin, Robert Njoroge, Yun Tang

  14. Review and Reporting Plan • Internal Reviews • Definition Process • Preliminary Design • Design Process • Programming Process • System Test Process • Postmortem • External Reviews • Preliminary Design • Design • Acceptance

  15. Review and Reporting Plan • Manager Reports • Status Reports • Meeting Agenda • Non-Manager Reports • Progress • Individual Status • Meeting Minutes

  16. Installation and Operation Plan • The application (Space Allocation) will be installed on the Facilities Management servers on or before April 22, 2004 • Client is responsible for all aspects of operating the software. • The administrator will assign users and permissions as needed • The client is responsible for all maintenance of the software upon its installation

  17. Risks

  18. Reviewed RAD and SDD with the clients Contract complete and ready for client’s final approval Developed preliminary ASP web interfaces Current Status of Project

  19. ? ?

  20. Login screen Correct username and password Assignable Structure Interface Edit and update Valid input Updated datagrid correctly Adding a record Valid input Record added to database and datagrid Query Information from the correct record is displayed Prototype Testing

More Related