Requirements

=Requirements Template= Follow this template as a guide to completing requirements. There is no magic number in the amount of requirements needed. Try to not leave any out, but if it get repetitive, then look for ways of breaking them down or limit some. Its probably a good idea to have more requirements than too few. You can always modify this list later on before moving on to next stage.

The second row is an example that looks at the requirement for a //community centre//.

way of frequently updating community information ||= Will help better integration with community events to foster community building, people sharing ideaså ||= Should have ||= - calendar of events,news -member and community news ||= a user generated note that indexes to a calendar system ||
 * ~ Requirement ||~ Rationale ||~ Priority ||~ Content ||~ Function ||
 * //The nature of the requirement// || //Why is this requirement needed? How does it support the user activities?// || //MoSCoW rules// || //What information/media needed to fulfill requirement?// || //What is the behaviour of the system to access the content/perform the activity?// ||
 * = A simple and easy