Small.World

We are more connected than ever.

System Requirements

Posted on April 27, 2015 by Miroslaw Jaroszak

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.

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.

System Modeling

Posted on April 26, 2015 by Muna Al Abri

The system requirements that have been collected from team members (since the permission for an ethical approvement got delayed) and feasibility study have been modelled using textual use cases for the most outstanding functions and that make the core of the small.world application. This gives a better understanding of what the system is expected to do and how the user is expected to use it.

is an example of the developed use cases. for a detailed view, read use cases.