| The Short Term Project Plan | |
 |
RWL |
| The Short Term Project Plan | |
|
RWL |
The intent of this project is to provide an information system for the data collected from these devices. The system will be flexible, allowing for many types of devices. The system will also be modular; new devices can be added at any time. Furthermore, the system will provide an interface to the data. The interface presents instantaneous status information and historical data for each device. The parameters of the system, such as user access and device properties, will be configurable. Finally, the system will be redundant.
This semester we have several goals to accomplish: create use cases, setup laptops, fix the E-R diagram, finalize design of and implement database, test database, create a web-based user interface, and test the usability of that user interface.
Descriptions of goals
Study Project and Determine Group Roles
Starting on an existing project requires the team to learn about the project and the current status of it. We must evaluate the past semester's work and critique it. Afterwards, once each group member gets a feel of what part of the project they would like to work on the most this semester, team roles must be assigned.
Learn CVS
Configuration management will need to be used in the development of the process to ensure that work is not lost or duplicated. We must therefore learn about CVS and how to use it.
Contact Lockheed
Before beginning on the project, we must meet our clients and work with them throughout the semester to make sure that we are all on the same wave length and striving toward the same goals. Our requirements must meet the clients needs in the manner they desire.
Develop Use Cases
At this point, it is not clear to us what functionality this end system will have. The use cases will help us to define the abilities of our end system. The use cases must be clear and testable.
Obtain and Setup Laptops
Lockheed has provided us with two laptops. However, these laptops have not come equipped with the software required to develop this system. Firstly, we must determine what software is needed. Factors in this decision include specific requests that may be made by the client. Secondly, we need to install the decided software into each laptop.
Finalize Design of and Implement Database with Database Iteration Implementation
The current database design cannot be considered complete because it is a bunch of cow manure. We will review the current database with the client to determine any additions/modifications that are needed. Once the design is complete, we will use the laptops and the decided Relational Database Management System (RDMS) to implement the database. While implementing the database, the design will have to be revised (database iteration implementation).
Test Database
The database must be robust and flexible. We must manifest tests that judge the robustness and flexibility of this RDMS setup. Testing requires designing test cases and running tests to satisfy the test cases.
Design and Implement User Interface
We need to design and implement a front end to this system. We plan to have a simple prototype of the front end by the end of this semester. This prototype will be web based.
Test the Usability of the UI (if time)
Before the front end is hooked up to the back end, we need to test the usability of the front end. Usability tests will be designed and completed by volunteers. Participants will match the expected end users as much as possible.
Description: Read all existing web documents from last semester. Learn software created and meet with past group members.
Roles: Group (5 hours per person)
Setup Configuration Management and Directory Structures (12 hours)
Description: Setup environment on CoC accounts for this semester and move out last semesters' work for history purposes. Setup CVS as revision control and learn how to use.
Roles: Group (2 hours per person)
Determine group roles (6 hours)
Description: After learning the project solo and seeing what areas each would like to work on this semester, team roles will be dealt.
Roles: Group (1 hour per person)
Group Stuff (180 hours)
Description: Status reports, meetings
Roles: Group (2 hours per week per person)
Contact Lockheed - Introductions (6 hours)
Description: Introduce ourselves to our clients and have an overview talk about this semester.
Roles: Group (1 hour per person)
Use Case Designing Meeting (24 hours)
Description: Setup a meeting with Lockheed clients to design specific use cases. These use cases will be guidelines into defining the database specifications. Use cases decide what the end user should be able to accomplish with the software once completed.
Roles: Michael Emard (8 hours - established outline and describe use cases in detail), Group (Meeting with Lockheed to go over the use cases - 2 hours per person), Jeff Hicks (4 hours - evaluate/critique Michael's work)
Laptop Setup (40 hours)
Description: Setup two laptops (client & server) for the software environment. Meet with Lockheed clients to decide on software specifications and what needs to be on the laptops. Use laptops for project implementation.
Roles: Michael Emard (7 hours - server setup), Brett Keenan (9 hours - client setup and receiving client laptop), Eric Krambler, Jeff Hicks, Levi Smith (8 hours per person - putting project software on laptops - merging)
Documentation (115 hours)
Description: Real World Lab required web documentation - all deliverables. Group meetings will be held prior to deliverables.
Roles: Group (7 hours per person - revision, critique of documentation, contact page), Tamrah Snyder (57 hours - production and revision of majority of the documentation), Brett Keenan, Michael Emard (8 hours per person - Short and Long Term Plans)
Test Software (36 hours)
Description: Setup test cases and test the software toward the end of the semester (DB and UI).
Roles: Brett Keenan (2 hours - creation of test cases), Michael Emard (2 hours - creation of test cases), Jeff Hicks (2 hours - creation of test cases), Levi Smith (2 hours - creation of test cases), Eric Krambler (28 hours - creation of test cases and full testing/analysis)
Redesign Database (46 hours)
Description: Meet with Lockheed clients to decide what changes need to be made in order to up the Access DB to an SQL DB.
Roles: Brett Keenan (3 hours - schedule & attend meeting with client), Tamrah Snyder (3 hours - meeting with client), Michael Emard (3 hours - meeting with client), Jeff Hicks (3 hours - meeting with client), Levi Smith (15 hours - database redesign, meeting with client), Eric Krambler (15 hours - database redesign, meeting with client)
Implement Database and Database Iteration Implementation (126 hours)
Description: Implement the database in SQL according to the requirements. Training in SQL. Make upgrades and fixes as testing progresses.
Roles: Levi Smith (49 hours - SQL training, database implementation, upgrades/fixes), Jeff Hicks (45 hours - SQL training, database implementation, upgrades/fixes), Eric Krambler (32 hours - SQL training, database implementation)
DB GUI Design (46 hours)
Description: Meet with Lockheed clients to decide what to code the db interface in and what it needs to accomplish/perform. Create sample UI for clients.
Roles: Brett Keenan (13 hours - sample UI, meet with client, UI brainstorming), Tamrah Snyder (12 hours - sample UI, meet with client, UI brainstorming), Michael Emard (12 hours - sample UI, meet with client, UI brainstorming), Jeff Hicks (3 hours - meet with client), Levi Smith (3 hours - meet with client), Eric Krambler (3 hours - meet with client)
Implement DB GUI (91 hours)
Description: Implement the UI and train in whatever software is necessary.
Roles: Michael Emard (35 - UI training and Implementation), Brett Keenan (35 - UI training and Implementation), Tamrah Snyder (21 - UI training and Implementation)
Final Presentation (69 hours)
Description: Evaluate semester progress and accomplishments based on allotted time. Review estimated and actual schedules. Create presentation slides and information.
Roles: Brett Keenan (19 hours - future semester work, evaluate semester work, create final presentation slides, actually present), Tamrah Snyder (4 hours - future semester work, evaluate semester work, actually present), Michael Emard (19 hours - future semester work, evaluate semester work, create final presentation slides, actually present), Jeff Hicks (9 hours - create documentation for next semester's systems manager, produce slides for presentation, actually present), Levi Smith (9 hours - presentation slides, documentation for next semester's project developer, actually present), Eric Krambler (9 hours - presentation slides, documentation for next semester's tester, actually present)
Current Milestones and Times
Updated progress of short term goals
Week 1:
Michael Emard: Familiarize with project (3 hours), Determine roles
(.5 hours), Setup and learn CVS and directories (2 hours)
Brett Keenan: Familiarize with project (3 hours), Determine roles (.5
hours), Setup and learn CVS and directories (2 hours),
Contact customer (1 hour)
Tamrah Snyder: Familiarize with project (3 hours), Determine roles
(.5 hours), Setup and learn CVS and directories (2 hours)
Levi Smith: Familiarize with project (3 hours), Determine roles (.5
hours), Setup and learn CVS and directories (2 hours)
Jeff Hicks: Familiarize with project (3 hours), Determine roles (.5
hours), Setup and learn CVS and directories (2 hours)
Eric Krambler: Familiarize with project (3 hours), Determine roles
(.5 hours), Setup and learn CVS and directories (2 hours)
Week 2:
Michael Emard: Brainstorm about use cases (2 hours), Enter contact
info on web and learn about editing web pages (2 hours),
Speak with past group (2 hours), Familiarize with project (1 hour), Start
use cases (4 hours)
Brett Keenan: Brainstorm about use cases (2 hours), Enter contact info
on web and learn about editing web pages (2 hours),
Speak with past group (2 hours), Familiarize with project (1 hour), Obtain
laptop (2 hours)
Tamrah Snyder: Brainstorm about use cases (2 hours), Enter contact
info on web and learn about editing web pages (2 hours),
Speak with past group (2 hours), Familiarize with project (1 hour), Setup
status reports and meeting minutes web pages (1 hour)
Levi Smith: Brainstorm about use cases (2 hours), Enter contact info
on web and learn about editing web pages (2 hours),
Speak with past group (2 hours), Familiarize with project (1 hour)
Jeff Hicks: Brainstorm about use cases (2 hours), Enter contact info
on web and learn about editing web pages (2 hours),
Speak with past group (2 hours), Familiarize with project (1 hour)
Eric Krambler: Brainstorm about use cases (2 hours), Enter contact
info on web and learn about editing web pages (2 hours),
Speak with past group (2 hours), Familiarize with project (1 hour)
Week 3:
Michael Emard: Meet with customer (2 hours), Short Term Plan (5 hours),
Long Term Plan (3 hours), Finish use cases (4 hours)
Brett Keenan: Meet with customer (2 hours), Short Term Plan (5 hours),
Long Term Plan (3 hours),
Tamrah Snyder: Meet with customer (2 hours), Short Term Plan (5 hours),
Long Term Plan (3 hours), Use cases to web (2 hours),
update main project and history web pages (1 hour)
Levi Smith: Meet with customer (2 hours), Train in SQL (4 hours)
Jeff Hicks: Meet with customer (2 hours), Finish use cases (4 hours)
Eric Krambler: Meet with customer (2 hours), Train in SQL (4 hours)
Week 4:
Michael Emard: Meet with customer about DB design (2 hours), Setup
server laptop (4 hours), Connect server and client laptops (3 hours)
Brett Keenan: Meet with customer about DB design (2 hours), Setup client
laptop (4 hours), Connect server and client laptops (3 hours)
Tamrah Snyder: Meet with customer about DB design (2 hours), Create
Requirements, Design, and Process web pages (8 hours)
Levi Smith: Meet with customer about DB design (2 hours), Design new
DB setup (5 hours)
Jeff Hicks: Meet with customer about DB design (2 hours), Redo E-R
Diagram (6 hours)
Eric Krambler: Meet with customer about DB design (2 hours), Design
new DB setup (5 hours)
Week 5:
Michael Emard: Update client on progress and discuss UI design (2 hours),
Brainstorm UI design (4 hours)
Brett Keenan: Update client on progress and discuss UI design (2 hours),
Brainstorm UI design (4 hours)
Tamrah Snyder: Update client on progress and discuss UI design (2 hours),
Brainstorm UI design (4 hours)
Levi Smith: Update client on progress and discuss UI design (2 hours),
Start creation of DB (8 hours)
Jeff Hicks: Update client on progress and discuss UI design (2 hours),
Start creation of DB (8 hours)
Eric Krambler: Update client on progress and discuss UI design (2 hours),
Start creation of DB (8 hours)
Week 6:
Michael Emard: Sample UI for customer (4 hours), UI design meeting
with customer (2 hours)
Brett Keenan: Sample UI for customer (4 hours), UI design meeting with
customer (2 hours)
Tamrah Snyder: Sample UI for customer (4 hours), UI design meeting
with customer (2 hours)
Levi Smith: DB implementation (8 hours), Meet with customer for DB
critique (2 hours)
Jeff Hicks: DB implementation (6 hours), Meet with customer for DB
critique (2 hours)
Eric Krambler: DB implementation (6 hours), Meet with customer for
DB critique (2 hours)
Week 7:
Michael Emard: UI Design (4 hours), Necessary software training (2
hours)
Brett Keenan: UI Design (4 hours), Necessary software training (2 hours)
Tamrah Snyder: UI Design (2 hours), Necessary software training (2
hours)
Levi Smith: DB implementation (7 hours)
Jeff Hicks: DB implementation (7 hours)
Eric Krambler: DB implementation (7 hours)
Week 8:
Michael Emard: UI implementation (7 hours), Meet with customer for
final UI revisions (3 hours)
Brett Keenan: UI implementation (7 hours), Meet with customer for final
UI revisions (3 hours)
Tamrah Snyder: UI implementation (7 hours), Meet with customer for
final UI revisions (3 hours)
Levi Smith: DB implementation (7 hours), Meet with customer for final
DB revisions (3 hours)
Jeff Hicks: DB implementation (7 hours), Meet with customer for final
DB revisions (3 hours)
Eric Krambler: DB implementation (7 hours), Meet with customer for
final DB revisions (3 hours)
Week 9:
Michael Emard: UI Implementation (9 hours)
Brett Keenan: UI Implementation (9 hours)
Tamrah Snyder: Update project plans (8 hours)
Levi Smith: DB Implementation (9 hours)
Jeff Hicks: DB Implementation (8 hours)
Eric Krambler: DB Implementation (8 hours)
Week 10:
Michael Emard: UI Implementation (10 hours)
Brett Keenan: UI Implementation (11 hours)
Tamrah Snyder: Reviews document (8 hours)
Levi Smith: DB Implementation - Final (6 hours)
Jeff Hicks: DB Implementation - Final (6 hours)
Eric Krambler: DB Implementation - Final (6 hours)
Week 11:
Michael Emard: UI Implementation (5 hours), Create test cases (2 hours)
Brett Keenan: UI Implementation (5 hours), Create test cases (2 hours)
Tamrah Snyder: User Manual (8 hours)
Levi Smith: Create test cases (2 hours), DB connections - setup on
laptop - DB and UI (8 hours)
Jeff Hicks: Create test cases (2 hours), DB connections - setup on
laptop - DB and UI (8 hours)
Eric Krambler: Create test cases (2 hours), DB connections - setup
on laptop - DB and UI (8 hours)
Week 12:
Michael Emard: UI finish with customer (2 hours), Future semester work
creation (4 hours)
Brett Keenan: UI finish with customer (2 hours), Future semester work
creation (4 hours)
Tamrah Snyder: UI finish with customer (2 hours), Testing documentation
(3 hours)
Levi Smith: Upgrades and fixes (6 hours)
Jeff Hicks: Upgrades and fixes (6 hours)
Eric Krambler: DB Testing (3 hours), UI Testing (5 hours)
Week 13:
Michael Emard: Outline next semesters' work (2 hours), Evaluate semester
progress (4 hours)
Brett Keenan: Outline next semesters' work (2 hours), Evaluate semester
progress (4 hours)
Tamrah Snyder: Testing documentation (3 hours), Outline next
semesters' work (1 hours), Evaluate semester progress (2 hours)
Levi Smith: Upgrades and fixes (8 hours)
Jeff Hicks: Upgrades and fixes (8 hours)
Eric Krambler: DB Testing (3 hours), UI Testing (5 hours)
Week 14:
Michael Emard: Presentation design (8 hours)
Brett Keenan: Presentation design (8 hours)
Tamrah Snyder: End of Semester document (8 hours)
Levi Smith: Presentation design (8 hours)
Jeff Hicks: Presentation design (8 hours)
Eric Krambler: Presentation design (8 hours)
Week 15:
Michael Emard: Finalize documentation - web (5 hours), Present Project
(1 hour), Last meeting with customer - evaluation (2 hours)
Brett Keenan: Finalize documentation - web (5 hours), Present Project
(1 hour), Last meeting with customer - evaluation (2 hours)
Tamrah Snyder: Finalize documentation - web (5 hours), Present Project
(1 hour), Last meeting with customer - evaluation (2 hours)
Levi Smith: Finalize documentation - web (5 hours), Present Project
(1 hour), Last meeting with customer - evaluation (2 hours)
Jeff Hicks: Finalize documentation - web (5 hours), Present Project
(1 hour), Last meeting with customer - evaluation (2 hours)
Eric Krambler: Finalize documentation - web (5 hours), Present Project
(1 hour), Last meeting with customer - evaluation (2 hours)
Note: Each week we will meet as a group either by ourselves or
with our customer. Status reports will be email and web based done
by Friday of each week.
Deliverables and Web Pages
Short Term Plan
This document describes the goals for the current semester, the specific activities to be completed, and the timeline for the activities to be completed.
Long Term Plan
This document gives a broad layout of the goals needed to complete the project as well as a projected semester by semester activity list.
Configuration Management Check
Two checks are preformed throughout the semester. We will need to make sure our directory structure is in order and our CM process is in place and being used.
Main Project Page
Opening to the project web pages - gives links to deliverables, last semester's work, Lockheed home page, contact information, etc.
History Page
Last semester's documents for reference.
Requirements
Requirements for the project, based on Lockheed clients' needs.
Status Reports
Individual team weekly status reports noting weekly actions.
Meeting Minutes
Minutes from meetings held - group and with clients.
User Manual
For the end user - how to run and work the software.
Peer Review
Review with another group the projects that the two groups worked on through the course of the semester.
End of Semester Documentation
This document will outline problems
encountered throughout the semester, accomplishments, as well as plans
for next semester's group.