Software Engineering with an Agile Development Framework/Iteration Two/Good requirements

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 examplesRequirement The system shall:DescriptionFR1Allow museum object data entryThe users will need to add new data to the system when items are donated to the museum.FR2Enable public access to stored museum dataResearchers may wish to access stored genealogical, shipping and local history information. Non-Functional Requirements (what the system has)A. Data RequirementsNumberexamplesRequirementThe system shall:DescriptionD1Store object acquisition data As objects are acquired by the museum, data relating to the object must be capturedD2Store object location dataEnables the staff to quickly locate any museum object.B. Security RequirementsNumber examplesRequirementThe system shall:DescriptionS1Prevent unauthorised changes to museum dataPublic using the system must not be able to delete files.C. Interface RequirementsNumber examplesRequirementThe system shall:DescriptionI1Provide an administration interfaceAdministrators will need to access the system directly for editing.I2Provide an interface which reflects the Maritime Heritage theme This is important to ensure public and government support for the new buildingsD. ConstraintsWhat might limit the development of the systemNumber examplesRequirementThe system shall:'Description'C1Cost less than $20,000Little funding available for software.C2Be completed by January 2004 'This allows the system to be running in time for the new school year'