Requirement Repository

The following table list all the requirements for this project.

functional

id	v.	intent	title	description
RQ0	1.1	MUST	System Security	The system shall prevent un-authorised access.
type:functional status:proposed package:security				trace to:RQ3 stakeholder:Security stakeholder:Marketing
RQ1	1.1	MUST	Username	The system shall identify users via a unique username.
type:functional status:proposed package:model				trace to:Logon [UC1] stakeholder:Security
RQ2	1.0	MUST	Password	The system shall store passwords against each username.
type:functional status:proposed package:model				trace to:RQ4 trace to:Logon [UC1]
RQ3	1.0	MUST	Authentication	Authentication shall be established based on the correct username and password combination.
type:functional status:proposed package:security				trace from:RQ0 trace to:Logon [UC1]
RQ5	1.0	MUST	Failed Logons	If a logon attempt is unsuccesful the system shall inform the user, however specfic reasons for the failure shall not be communicated as this information can prove useful for malicious authentication attempts.
type:functional status:proposed package:security				trace to:Logon [UC1]
RQ7	1.0	MUST	Authorisation	The system shall store permissions against each user such that their level of access to the system can be controlled.
type:functional status:proposed package:security				trace to:Logon [UC1]
RQ8	1.0	MUST	Personal Information	The system shall store certain personal information about each user on the system.
type:functional status:proposed package:model				trace to:RQ9 trace to:RQ10 trace to:RQ11 trace to:RQ12 trace to:Change Personal Details [UC2] stakeholder:User stakeholder:Marketing
RQ9	1.0	MUST	First Name	The system shall store a first name against each user.
type:functional status:proposed package:model				trace from:RQ8 trace to:Change Personal Details [UC2]
RQ10	1.0	MUST	Last Name	The system shall store a last name against each user.
type:functional status:proposed package:model				trace from:RQ8 trace to:Change Personal Details [UC2]
RQ11	1.0	MUST	Address	The system shall store an address against each user.
type:functional status:proposed package:model				trace from:RQ8 trace to:Change Personal Details [UC2]
RQ12	1.0	MUST	Names fields	Name fields should be at least one character in length.
type:functional status:proposed package:model				trace from:RQ8 trace to:Change Personal Details [UC2]

non-functional

id	v.	intent	title	description
RQ4 michael; 2006-05-23 RQ4: This requirement needs validating with the security team to validate that they are happy with the minimum expected password strength.	1.1	MUST	Password Structure	The system shall only allow passwords greater than eight characters long being a mixture of alpha-numerics.
type:non-functional status:proposed release 3 package:security				trace from:RQ2 stakeholder:Security stakeholder:User
RQ6 odlingsmee; 2006-05-23 RQ6:TLS should probably be used in preference to SSL - this is still under investigation.	1.1	SHOULD	SSL Encryption	The system's website should support SSL Encryption to prevent data being sniffed by malicious parties.
type:non-functional status:proposed package:security				trace to:Logon [UC1]
RQ13	1.0	MUST	Web UI	The user interface shall be a web (HTTP) user interface to ease deployment and accesibility.
type:non-functional status:proposed package:gui				trace to:Logon [UC1]