Master thesis – Requirements elicitation 1


Be careful when copying information from this article! The paper is already published and you will be charged with plagiarism!

We already covered the proposed general usage scenario and particular use cases of a Brainstorming system. In order to evaluate their implementation, in this section the application requirements will be presented. They are split into functional and non-functional ones. The first refers to all the features needed to be implemented, while the second category refers to performance, extensibility and scalability of the system.

Functional requirements
  Description
FR.1 The system will allow multiple users to interact with the system simultaneously
FR.2 The system will allow multiple devices to interact with the Microsoft Surface simultaneously
FR.3 The users will be able to send ideas to the tabletop using mobile clients
FR.4 The users will be able to generate and input ideas in the system
FR.5 The Contributors will be able to input Brainstorming items directly on the tabletop
FR.6 The Contributors will be able to Group Brainstorming items
FR.7 The Contributors will be able to Edit Brainstorming items
FR.8 The Contributors will be able to Relate Brainstorming items
FR.9 The Contributors will be able to Print Screen
FR.10 The Contributors will be able to promote Twitter or Flickr items to  Brainstorming items
FR.11 The Session Master will be able to login into its BSCW account
FR.12 The Session Master will be able to Save a Brainstorming Session
FR.13 The Session Master will be able to Load a Brainstorming Session
FR.14 The Session Master will be able to set Session Goal
FR.15 The Session Master will be able to start the application using his Tag
FR.16 The Session Master will be able to search on Flickr using a keyword
FR.17 The Session Master will be able to search on Twitter using a keyword

 

Non-Functional requirements
  Description
NR.1 The application will be designed to be extensible and maintainable
NR.2 The application will be highly responsive
NR.3 The application will be reliable
NR.4 The application will use responsibly hardware resources

Now let’s move to the Architecture of the application!

Leave a comment

Your email address will not be published. Required fields are marked *