Requirements Gathering Survey

A study of what Small.World should include was planned using one of the fact finding techniques which is a questionnaire. Survey is the most common technique for gathering user requirements. Please find the survey the team designed for this purpose here.

Screen Shot 2015-04-30 at 22.01.59The survey was planned to be distributed online using Google Forms and to a population sample of 50 people. Due to certain complications with Ergo which is the Ethical Committee in Southampton, the survey didn’t get the approval to be distributed. The team is recommending to use the survey as a future step to gather user requirements.

System Requirements

In order to determine what is needed from our online social network, we conducted requirements gathering and elicitation which are the vital parts of every software analysis process. The requirements usually refer to what software does (functional) and what are its qualities (non-functional). They usually have their unique IDs, are prioritised and in more detailed approach – have appropriate metrics.

Two tables below present some of the functional and non-functional requirements for Small World. Each one is assigned a priority level indicated by colour scheme.

Selected System Requirements

For full and detailed requirements list, refer to the Full Requirements Document.

Background reading

Pressman, R. (2010). Software engineering. Boston, Mass.: McGraw-Hill.

Sommerville, l. (2011). Software Engineering. 9th ed. London: Pearson Education.