will be the page about structuring requirements

Requirements template

Requirements Specification

===Functional Requirements === (What the system does, 10 –12 of these, this is the important bit. Think about how the users will use the system – what will they need it to do? Be specific to your project.

Number examples	Requirement The system shall:	Description
FR1	Allow museum object data entry	The users will need to add new data to the system when items are donated to the museum.
FR2	Enable public access to stored museum data	Researchers may wish to access stored genealogical, shipping and local history information.

Non-Functional Requirements edit (what the system has)
A. Data Requirements
Numberexamples	Requirement The system shall:	Description
D1	Store object acquisition data	As objects are acquired by the museum, data relating to the object must be captured
D2	Store object location data	Enables the staff to quickly locate any museum object.

B. Security Requirements
Number examples	Requirement The system shall:	Description
S1	Prevent unauthorised changes to museum data	Public using the system must not be able to delete files.

C. Interface Requirements
Number examples	Requirement The system shall:	Description
I1	Provide an administration interface	Administrators will need to access the system directly for editing.
I2	Provide an interface which reflects the Maritime Heritage theme	This is important to ensure public and government support for the new buildings

D. Constraints What might limit the development of the system
Number examples	Requirement The system shall:	'Description'
C1	Cost less than $20,000	Little funding available for software.
C2	Be completed by January 2004	'This allows the system to be running in time for the new school year'