Requirements Specification
for an Electronic Calendar Tool
Version 0.2
12 October 2001
Editorial Note: This milestone example and the others to follow provide concrete examples of roughly what 205 class milestones should look like. Throughout the examples, there are editorial notes interjected to explain important points. The notes are set off from the rest of the text in indented italics to indicate that they should not be considered part of the document itself.This first example illustrates roughly what your Milestone 2 should look like. The numbered sections in the document are based on the sections outlined in requirements specification document outline distributed in the first week of class.
This is a very preliminary document draft, so things can be expected to change a good deal by the time the final project report is completed. However, the basic sections of the report provide a working framework for organizing our initial ideas.
Contents
1. Introduction
1.1. Problem Statement
1.2. System Personnel
1.3. Operational Setting
1.4. Impacts
1.5. Related Systems2. Functional Requirements
2.1. User Interface Overview
2.2. Scheduling an Individual Appointment
2.3. Browsing an Individual Calendar
2.3.1. Viewing by Day, Week, Month, and Year
2.3.2. Viewing Lists of Scheduled Items
2.3.3. Viewing a Specific Calendar Date
2.3.4. Filtered Viewing
2.3.5. Viewing Recently Displayed Windows
2.3.6. Viewing Other Users' Calendars
2.3.7. Receiving Reminders
2.4. More Individual User Scheduling
2.4.1. Scheduling an Individual Meeting
2.4.2. Scheduling Tasks
2.4.3. Scheduling a Plain Event
2.4.4. Data Entry Details
2.5. Scheduling Group Meetings
2.6. Administrative Functions
2.6.1. User Database
2.6.1.1. Adding a User
2.6.1.2. Deleting a User
2.6.1.3. Changing a User
2.6.1.4. Finding a User
2.6.2. Group Database
2.6.2.1. Room Database
2.6.2.2. Global Options
2.7. Individual User Options
2.8. Details of File and Edit Operations