(L) - denotes subgroup leader
|
Name |
Roles |
Email Address |
|
Tori Bowman |
Project Manager Requirements Analyst |
|
|
Danielle Claxton |
Requirements Analyst User documentation specialist (L) |
|
|
Andy Cooper |
Designer (L) Implementer Configuration |
|
|
Kyle Gossman |
Designer Implementer (L) |
mailto:Kyle.Gossman@rose-hulman.edu |
|
Brandon Invergo |
Implementer Tester |
|
|
Hardy Spry |
Configuration (L) User documentation specialist |
|
|
Micah Taylor |
Designer Tester (L) |
The ability to accurately project the enrollment of students in classes during a given quarter is decreasing. This has lead to the need to add additional sections extremely close to registration. Because of this inability to forecast the necessary data, technical electives and other classes have been canceled. If there were to be a system that could collect the data provided by each individual student’s four-year plan, these problems would be averted. We would like to build such a system.
We are assuming that students will begin using our software during their sophomore year. Our conjecture is that professors will be inclined to use our product because it will allow them to do their job better, easier, and more efficiently. We believe that if advisors require students to supply them with a degree plan made with our product before they are given their registration PIN, all students will participate. Also, our initial goal is to have the first use and set up for the student to only take 45 minutes or less. From that point on, updates and maintenance will take between ten and fifteen minutes.
We envision, based on your login, that our software will know if the user is a professor or a student. Students will have the option to import their web transcript from banner to use as inputs. We intend to evade security problems by not importing grade results. Students will also be able to print a graphical representation of their four-year plan showing the backbone of their schedule.
If the user is a professor, they will be able to view the input of their advisees. Also, they will be able to pull various statistics. They will be able to view how many of their advisees have completed their four-year plan, how many students in the department have completed a four-year plan, and the number of students planning on taking a specified course during a specified quarter and each students level, i.e. sophomore, junior, etc. Since the students will be able to access and update their data whenever they need or want to do so, the statistics gathered on the data will be very timely.
Since IAIT will be taking over this project upon our conclusion, we are writing most of our software in Perl and using an Apache server in accordance with IAIT approval. Because we will most likely have less than 1000 entries, we intend to use flat files instead of database software. We feel that this will decrease the overhead and increase speed. Should we decide that a database would be necessary, we will either use MySQL or Oracle. IAIT will be providing a server on which our software will run. We will be using the data backup methodology of IAIT.
|
Work Package ID |
Resource Names |
Role |
Task |
Start |
Finish |
% Work Completed |
|
0a |
Tori |
|
Write project proposal to bring to Dr. Ferguson |
12/18/2002 |
12/20/2002 |
100% |
|
0b |
Tori |
|
Revise project proposal |
12/20/2002 |
1/5/2003 |
100% |
|
1 |
Hardy – software |
|
Make the configuration plan |
12/16/2002 |
12/20/2002 |
100% |
|
2 |
Tori |
|
Write feasibility report |
12/17/2002 |
12/20/2002 |
100% |
|
3 |
Danielle Tori |
|
Work on the requirements specification |
12/18/2002 |
1/27/2003 |
33% |
|
4 |
Kyle Andy Brandon |
|
Work on an interface to show the client |
12/20/2002 |
1/15/2003 |
10% |
|
5 |
Andy Kyle Micah |
|
Work on the design document |
1/6/2003 |
2/3/2003 |
0% |
|
Week Starting |
On/Off Schedule |
Reason Off Schedule |
Corrective Actions To Take |
|
12/16/2002 |
On |
|
|
|
1/13/2003 |
Off |
UI prototypes not completed |
Done by Wednesday |
|
|
|
|
|
|
Items |
|
Work on UI prototypes |
|
Date |
Name |
Revision |
|
12/18/2002 |
Tori Bowman |
Initial pass |
|
12/19/2002 |
Tori Bowman |
Added project proposal |
|
1/12/2003 |
Tori Bowman |
Updated project proposal, schedule, and work packages |