# ER: Requirements Specification Component > Project vision ## A1: Project Name > Goals, business context and environment. > Motivation. > Main features. > User profiles. --- ## 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 * ...