- •1.4Project Scope
- •This order form and a cover letter are mailed by Dr. David Kluge to the 55 school district superintendents and private school principals in the two-county area.
- •1.5References
- •2.Overall Description
- •2.1Product Perspective
- •2.2Product Features
- •2.3User Classes and Characteristics
- •2.4Operating Environment
- •2.5Design and Implementation Constraints
- •2.6User Documentation
- •2.7Assumptions and Dependencies
- •3.System Features
- •3.1Adding an Organization to the System – Phase 1
- •3.2Managing Contact Lists – Phase 1
- •3.3Mailing Update Requests – Phase 1
- •3.4Managing Cover Letters – Phase 1
- •3.5Manually Updating an Organization – Phase 1
- •3.6Viewing the Update Summary – Phase 1
- •3.7Organizational Updating of Information – Phase 1
- •3.8Text File Creation from Database – Phase 2
- •3.9Page Layout Template Download From Web Site – Phase 2
- •3.10Text File Import Into Page Layout Template – Phase 2
- •3.11Directory Editing – Phase 2
- •3.12Directory Publishing – Phase 2
- •4.External Interface Requirements
- •4.1User Interfaces
- •4.2Hardware Interfaces
- •4.3Software Interfaces
- •4.4Communications Interfaces
- •5.Other Nonfunctional Requirements
- •5.1Performance Requirements
- •5.2Safety Requirements
- •5.3Security Requirements
- •5.4Software Quality Attributes
- •Copyright © 2002 by Karl e. Wiegers. Permission is granted to use, modify, and distribute this document.
2.7Assumptions and Dependencies
It is assumed that the system will be developed using the ASP.NET technology.
It is assumed that the system will be able to interface with an email server in order to send an update email to contacts in the system.
It is assumed that the system will interface with a SQL Server 2000 database.
It is assumed that organizations included in the directory will have an email address for transmitting updated information. A work around capability (Manual Update feature) shall be provided for the STEP Council to update organizations that do not have email.
It is assumed that the page layout technology utilized will be Adobe InDesign 2.0.
It is assumed that the method for importing database records into Adobe InDesign 2.0 documents will be a product known as EmSoftware’s InData 2.0.
3.System Features
3.1Adding an Organization to the System – Phase 1
3.1.1 Description and Priority
This feature pertains directly to adding an organization’s information into the online Directory database. The priority of this feature is high, because the system would be relatively useless if not for the data it manages.
Stimulus/Response Sequences
The user will click on the button to add an organization from the main Directory web page.
The user will fill in the information fields with the new organization information.
The user will submit the information to the system.
The system will display a page that allows the user to select the type of the organization from a drop down list.
The user will select the type of organization they are adding.
The system will display the forms appropriate to that type of organization.
The user will fill in the fields that are valid for the particular organization being entered and click Submit.
The system will validate, and then accept the entry.
The system will return the display to the main Directory web page.
3.1.3 Functional Requirements
REQ-1: The system shall provide a method for manually entering organization information into the system database via an interactive webpage.
REQ-2: The system shall provide to the user the ability to enter the following information about the organization:
The name of the organization
The name of the contact person for the organization
The email address of the contact person
The mailing address of the organization
The voice phone number of the organization
The fax phone number of the organization
The website associated with the organization
REQ-3: The system shall enforce the requirement that each organization have an organization name and contact person all times and the system shall not allow the organization to be entered into the database without this required information.
REQ-4: All other organization information listed in REQ-2, but not in REQ-3 will be considered optional information types.
REQ-5: The system shall validate the following information types based purely on the formatting of the data:
Email addresses
Phone numbers
States and zip codes
REQ-6: The system shall provide a method for submitting the proposed organization information to the system database.
REQ-7: The system shall allow the user to enter specific information based on the type of organization being entered.