Innopolis University MAP Project

Context

This project consists of handling traceability links between requirements and development artifacts.

Figure 1. Example of traceability in the Dronology project (source here)

Requirements

Since you have seven weeks to develop this project by applying the Scrum method, here is the planning:

• a first version (V1.0) at the end of the 4th Sprint

• a second version (V2.0) at the end of the 7th Sprint

ℹ️	No special instructions on the GUI (model and prototypes welcome) No instructions on techno (java is not mandatory)

Initial Product Backlog (last update: TBA)

Initial Client Features for V1

The initial functionalities requested are as follows:

1. Define the requirements

   1. Create / Delete / Modify a requirement

   2. List the requirements

2. Traceability links

   1. Display all the artifacts

   2. Allow navigating from one artifact to the related ones

   3. Add a missing dependability link between 2 artifacts manually

3. Tools API

   1. Use GitHub API to extract dependability links automatically

   2. Use external APIs (e.g., Google) to manage dependability links with some existing set of requirements

ℹ️	For V1, the requirements (and artifacts) will have minimal attributes (e.g., ID, Description, Status).

Initial User Stories examples

⚠️	These USs are only examples to start your Product Backlog, but the above customer requirements should be translated into USs. Do not hesitate to speak with the client (me!) for clarification.

• As a stakeholder, I want to manage requirements - business priority MUST.

• As a developer, I want to link User Stories to requirements - business priority MUST.

• As a project leader, I want to get access to all the artifacts (requirements, US, code, tests, …​) with their traceability links - business priority MUST.

• As a project leader, I want to get access to some supervision dashboard (see examples below) - business priority SHOULD.

• As a coder, I want to have as much automated links as possible - business priority SHOULD.

Additional functionalities (Product Backlog) V2

All the features of version V1, plus:

• Stakeholders can define additional attributes for requirements

• Project leader can define new kinds of artifacts

• Traceability links can be refined to more than just "father/son"

Illustrations from an existing application

A dataset example is available:

• as a JSON file here

• as an interactive view of the data http://sarec.nd.edu/dronology/datasets/01/

Figure 2. Example of an interactive view of the data (source here)

Figure 3. Example of dashboard (source here)

Assessment and rating

Here is the provisional scale:

Heading	weight
Respect for the Scrum method	20%
"Professional" character of dev	20%
Successive deliveries	20%
Tests / Documentations / Readme / wiki	20%
Code and application quality	10%
Final Customer Satisfaction	10%
Bonus (usability aspects)	+10%

Each Sprint (week) will be evaluated by the TD teacher who had you at your last TP slot. The evaluation will relate to 6 criteria and will take the following form:

Figure 4. Example of weekly evaluation

These six criteria are taken from a course on software quality from my Bordeaux colleague Xavier Blanc (https://github.com/xblanc33/QualiteDev):

⚠️

Sorry for the French in the following explanations: issues the way the goals have been captured (more details here) tasks the development tasks related to the issues and how easy it is to get from one to the other here) tests verification activities (more details here) source code quality attributes (more details here) documentation technical and user documentations (more details here) release build, automated testing, deploy (more details here)

Useful links

• The materials for the course: http://bit.ly/innopolis-map

• The inspiring project: Dronology