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

• 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

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

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

Life Cycle Model

• Saw Tooth Model

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

Basic Organization

Organization Plan

David HaasProject Manager

Don AndersonMain client contact

Tom KerwinLead Analyst/Designer

Yun TangLead Tester

Robert NjorogeLead 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

Erin HarrisUpper Management

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

ScheduleCS425 Timeline

CS499 Timeline

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

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

Testing Plan (cont.)

• Testing Tools• Microsoft Visual Studio. NET

• Microsoft Access

• Microsoft ASP.NET

• Responsibility • David Haas, Tom Kerwin, Robert Njoroge, Yun Tang

• Internal Reviews• Definition Process

• Preliminary Design

• Design Process

• Programming Process

• System Test Process

• Postmortem

Review and Reporting Plan

• External Reviews• Preliminary Design

• Design

• Acceptance

• Manager Reports• Status Reports

• Meeting Agenda

Review and Reporting Plan

• Non-Manager Reports• Progress

• Individual Status

• Meeting Minutes

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

Risks

RISK DESCRIPTION PROBABILITY OF OCCURENCE

DELAY IN DAYS

POSSIBLE SOLUTIONS

Loss of team member 5% 10 days Other members will take on the responsibilities of the gone team member

Learning Curve for ASP.NET 20% 15 days Reading literature and programming manuals about ASP.NET

Feature Creeps 15% 10 days Only add appropriate changes that will fit into our schedule and not effect the development of the rest of the system.

Personnel Problems 10% 5 days If disagreement arises between group members the project manager will make the final decision.

• 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

?

Prototype Testing

• 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