Statement of Work

Here is an example of a simple statement of work.

STATEMENT OF WORK: TUTORING DATABASE PROJECT
HISTORY
For a long time the tutoring program has used a paper schedule to sign students up for tutoring. Tutors identify their schedule for a two week period and then a schedule is printed and placed in the computer lab. Students look through the schedule for sessions that match courses they are taking and the times they have available. This system has worked and continues to work, but it has several significant problems. For one, it can be difficult for students to find appropriate tutoring sessions. The paper forms are difficult to navigate and understand. Additionally, it is very difficult for the tutoring program to track the students using the tutoring. It is difficult or impossible to track demographic information. It is also difficult to assure that students are enrolled in the courses they receive tutoring in. Even tracking tutors’ hours can be difficult.
A database with a client application could significantly improve the situation, by providing a flexible, searchable schedule for students, better tracking of demographics and eligibility, and better tracking of hours tutored.
SCOPE
The tutoring database will manage data for the tutoring program at the college. It will track available tutors and the courses they can tutor. It will also track each tutor’s tutoring schedule. The database will store demographic information for students who register for tutoring. This information will be private and used only generate general reports which include no personal information. Students, who have registered, will be able to sign up for available tutoring sessions for courses in which they are enrolled. The database will track whether students attended their scheduled sessions. It will also track student requests for tutoring in additional course and subjects.
Constraints
The database can be used to get the hours worked for each tutor, but it will not process pay or payroll information. The database will not validate student information against the school’s registration database.
OBJECTIVES
• Streamline the process by which the tutors enter their schedules and students sign up for them
• Improve tracking of demographic data of students using the tutoring program
• Improve tracking of tutor’s hours and students use of tutoring sessions
• Track Student requests for additional tutoring
TASKS AND TIMELINE
1. Gathering Data: This task will consist in a number of interviews, questionnaires and observations. Time allotted 3 weeks.
Deliverable: A list of scheduled interviews and observations, text of the questionnaires.
2. Analyzing Data: The data gathered will be analyzed to determine business rules and preliminary data modeling. Time allotted 2 weeks.
Deliverable: List of business rules to be reviewed, basic entities and attributes.
3. Normalization: the data model will be completed with entities and relationships normalized. Time allotted 1 week.
Deliverables: Entity Relation Diagram for Review.
4. Building the physical database: The data model will be translated to the Relational Database Management system. Tables, Columns with specific data types and Relational and other constraints created. Time allotted 3 days.
Deliverables: The Schema of the database for review.
5. Testing and security; Sample data will be entered and each of the business rules and requirements will be tested. General database security and security related to business rules will also be tested. Time allotted 3 weeks.
Deliverables: Documented test results.
6. Database Completion and installation: final changes and corrections are made. Sample data will be removed and the database installed on a server. Final testing for server access and connections. Time allotted 2 weeks.
Deliverables: The working database.
Total time between beginning of project and end: 11 weeks, 3 days.