# ER: Requirements Specification Component

> Project vision
Facebook’s corporate mission is “to give people the power to build community and bring the world closer together.”

BrainShare's mission is to create a community of FEUP students that allows them to easily obtain an answer to their questions regarding their curricular subject.

## A1: BrainShare

This project intends to specify, develop and promote a information system with a web interface.

> Goals, business context and environment.
// Tipo de navegação; Categorização; Organização da informação; especificar que é para toda a comunidade.

This project consists in a web application that allows FEUP students to ask, answer and search for questions according to the course, curricular units and specific topics.

> Motivation.
Nowadays, the students use many platforms to obtain and share information about course subjects. By centralizing this knowledge, our project intends to create a community that allows students to ask questions regarding a subject, search for common questions or even helping others by answering their questions.

> Main features.
// Adicionar valor para cada uma das features.

Asking and answering questions are the core features of our application. In order to give easy access to those, questions are organized by course and curricular subjects. Furthermore, questions can be associated with tags to improve specification.
Each answer can be evaluated by the community as useful or not. The author of the question will also be able to mark an answer as valid, highligthing the answer that solved the enunciated problem.
So as to complement the reliability of the system, each user has an associated score, which is calculated by the number of votes for each answer given.
Each answer will have an associated comment section, allowing the community to discuss details about that specific answer.

- Place questions [OK]
- Answer questions [OK]
- Search for questions: tag,... [OK]
- Upvote/Downvote system [OK]
- Best answer selection by the user that made the question [OK]
- User reliability system [OK]
- Comments to user answers [OK]
- Questions/Answers on user profile [OK]
- Categorization of questions in course, curricular units and tags [OK]

> User profiles.
This application promotes two kinds of user profiles: the users and administrators.
Each user can ask and answer questions. The users can also edit the details of their own questions. The administrator is able to execute everything that a normal user can do and also change categories, tags and delete the users questions.

> Users should have a registered account

Users are separated into groups with different permissions. There must be administration usage profiles, with all the privileges of access and modification. There also must be registered users usage profiles, with privileges to enter information, request and return of individual items, consult the information, register comments for the items, and evaluate the items.

This application promotes three kinds of user profiles: the guests, users and administrators. Guests can only search and see answers and questions. In order to ask and answer questions it is necessary to log in as user. The users can also edit the details of their questions. The administrator can execute everything that a normal user can do and also change categories, tags and delete the users' questions.

---

## A2: Actors and User stories

> Brief presentation of the product.
> Brief presentation of the artefact goals.

### 1. Actors

> Diagram identifying actors and their relationships.
> Table identifying actors, including a brief description and examples.

### 2. User Stories

> User stories organized by actor.
> For each actor, a table containing a line for each user story, and for each user story: an identifier, a name, a priority, and a description (following the recommended structure).

#### 2.1. Actor 1

#### 2.2. Actor 2

#### 2.N. Actor n

### 3. Supplementary Requirements

> Annex including business rules, technical requirements, and restrictions.
> For each subsection, a table containing identifiers, names, and descriptions for each requirement.

#### 3.1. Business rules

#### 3.2. Technical requirements

#### 3.3. Restrictions

---

## A3: User Interface Prototype

> Brief presentation of the product.
> Brief presentation of the artefact goals.

### 1. Interface and common features

> Screenshots highlighting the main elements of the interface, for desktop and mobile.

### 2. Sitemap

> Sitemap presenting the overall structure of the web application.
> Each screen must be identified in the sitemap.
> Multiple pages of the same screen (e.g. student profile in SIGARRA) are presented as page stacks.

### 3. Storyboards

> Storyboards for the main use cases of the system.
> Do not include trivial use cases.

### 4. Interfaces

> Screenshots, structured in subsections, including a reference, a description and a URL to the working version.

#### UI01: Home

#### UI02: About

### 4. Hand-made materials

> Include digitization of the hand-made materials, particularly the wireflows.

---

## Revision history

Changes made to the first submission:
1. Item 1
1. ...

***
GROUP21gg, DD/MM/2021

* Group member 1 name, email (Editor)
* Group member 2 name, email
* ...