This component groups the artefacts related to the Requirements Specification of the system to be developed during the project. These artefacts are usually included in the Requirements Document of a system [IEEE98] developed in the initial phase of analyses, by a team that includes all project stakeholders.
This artefact introduces the context and motivation and briefly describes the web information system to be developed. It includes the goals of the project and lists the features that should be supported, together with the identified access groups.
This artefact contains the specification of the actors and their user stories, serving as agile documentation of project requirements.
An Actor models a type of role played by an entity that interacts with the system being specified. This may include persons (not just the end-user), and other entities external to the system. Actors are always external to the system being modelled; they are never part of the system [Ambler04] .
A User Story is a high-level definition of a requirement containing only the necessary information so that the developers can produce a reasonable estimate of the effort required to implement it [Ambler04] . A user story, a brief description of a potential interaction with the system by one of its users, focuses only on interaction requirements and not on the technical aspects of the design of the system. The user stories have a priority (high or essential, medium or conditional, and low or optional) indicating the need to be included in the design implementation stages and project. A team of expert analysts also includes an estimate of the effort required for its implementation.
Each user story must follow the template [Dennis10] :
“As a [user], I want [function], so that [value]”
The Supplementary requirements are also presented in an Annex to A2.
This annex contains business rules, technical requirements and other restrictions on the project:
This User Interface Prototype has the following objectives:
Since an User Interface Prototype (or horizontal prototype) allows for a much faster implementation than the final product, it allows to easily test and validate the design at an early stage of the development, enabling empirical testing, such as usability testing and in situ observations of the design being used by real users. It also permits to quickly iterate on the design of the interface, implementing the results from the initial tests.
This artefact should include three elements:
The user interfaces must be implemented using HTML, CSS, JS. The overview of the interface elements must include a presentation of the behavior of the interfaces in small screen devices such as smartphones. This artefact includes screenshots of the interfaces, alongside with a link to a web page for each interface implemented.