E-Mail
course instructors: Ryan
Nelson or Dave Smith.COMM 768/9 Project Tasks & Deliverables
Tasks/Deliverables |
"Customers" | ||
| Ryan Nelson | Dave Smith | Client(s) | |
| Application System | 1 | 1 | 1 |
| Lifecycle Planning | 2 | ||
| Risk Management | 2 | ||
| Team Structure | 2 | ||
| Estimation | 2 | ||
| Scheduling | 2 | ||
| Requirements Specification | 1 | 1 | |
| OOA&D | 3 | 1 | |
| OO Application Architecture | 1 | ||
| RDBMS Implementation Architecture | 1 | ||
| GUI Design | 1 | 1 | |
| Testing | 1 | 1 | |
| Training | 2 | 2 | |
| On-line Help | 3 | 2 | |
| Documentation | 2 | 2 | 2 |
Note: The numbers within the table cells indicate the relative priority assigned to the project tasks/deliverables by the respective customer (1 = extremely high, 2 = high, 3 = moderate).
Note: This table describes the set of tasks and deliverables each team should strive to complete via the COMM 768/9 project this semester. These tasks and deliverables represent a "wish list" to the extent that their attainment may prove to be infeasible based on various resource constraints (e.g., schedule, technology, and/or team member skills). In an "ideal project" all tasks and deliverables will be completed at an appropriate level (i.e., within the context of the specific application being developed). As depicted in this table, there are three primary "customers" for the project tasks and deliverables: the two course instructors and the application system client(s). Secondary customers/stakeholders (e.g., end users and administrators) should also be considered throughout the course of the project.
Remember: The primary goal of this project is to provide an "experiential laboratory" for students to acquire the set of knowledge and skills set forth by the course instructors. A secondary, albeit important, goal of the project is to produce a high-quality, operational application system for use by the client(s).
Description of Tasks & Deliverables
An operational application system which will be evaluated using the following criteria:
Note: A client survey will be administered at the end of the project.
A brief narrative description of the lifecycle model used on the project.
A narrative description of project-related risk identification, analysis and mitigation.
A narrative description of team structure, including individual team member roles and responsibilities.
A narrative description of how project size & effort was estimated; e.g., function point counting.
Comprehensive and continuous use of project scheduling tool (Gantt chart developed in Microsoft Project). Please keep a project management log (i.e., hours per person by task).
A "minimal specification" of project requirements including:
The requirements specification should be presented to, and "signed off" by, the client(s). It will serve as the "contract" between you and your client(s).
Object-Oriented Analysis and Design
An object model(s) depicting application objects, attributes and relationships.
Object-Oriented Application Architecture
The extent to which OOP techniques are used in the development of your application system (both Client/Server and Web-based); for example:
RDBMS Implementation Architecture
A test plan and description of test results. Use of automated testing tool (e.g., SQA Teamtest).
A training plan and description of training results.
Development of an on-line help module(s) within application system (help file developed using tool such as Forehelp and/or hypertext linked Web pages).
Documented source code and necessary hardcopy documentation of application system for use in operation and maintenance. In addition, each team should supply documentation of task/deliverable completion to instructors as appropriate (please include a one-page "learning statement" from each team member).
E-Mail
course instructors: Ryan
Nelson or Dave Smith.
Date last modified: Tuesday, May 23, 2000