Requirements Management Plan

---

Version 0.4

Version History

Version	Author	Modification	Date
0.1	João Paulo	Document created	25/03
0.2	João Paulo	Added requirements traceability	29/03
0.3	João Paulo	Added missing Use Cases	31/03
0.4	João Paulo	Added attributes, marks and workflow	01/05

1. Introduction

1.1. Goal

This document goal is to describe the requirements management of the TechVet project, stablishing the attributes, requirements traceability and elicitation methods to act and prevent impact on requirements changes.

2. Requirements Management

2.1 Responsabilities and Organization

The responsabilities upon requirement artifacts are described above:

Management/Development Team: Responsable of elicitation and keep track or update the requirements if there is a change.

Client: Responsable for participation on elicitation meetings and to provide information to the team.

2.2 Tools

2.2.1 Elicitation tools

Interview: Simple and straight forward technique that uses no-context question to reach understanding of the project goal. As a result, the primary requirements are achieved.

Brainstorm: This technique generate ideas and generates creative solutions as a result of multiple combinations of ideas that appears not related.

2.2.2 Management tools

The following tools will be used to effectively manage the requirements:

Google drive to the initial documentation of the elicitated requirements.

Github Wiki to the version based documentation. This will allow all stakeholders to see the requirements and changes.

3. Requirements Management Program

3.1 Requirements Identification

3.1.1 Problem Description

ID	The problem of	Affects	Which impact is	A good solution would be
P1	Uneffective Management of Veterinary Clinic	The clinic employees and clients	Lack of agility on attendances and loss of data	A tool that allow manage multiple veterinary clinics

3.1.2 Necessity identification

ID	Necessity	Priority	Concerns	Current Solution	Suggested Solution
P1N1	Effectively and efficiently manage the records on the clinic	High	Inefficience on keeping track of records	Legacy System with many unused features	An optimized system that keeps track of all records and gives easy acess to edit/view and create them.
P1N2	To provide management tools that helps on daily work on the clinic	Medium	Inefficience on daily work and documentation of the work on the clinic	Paperwork and features on the legacy system	A well tailored system that fulfills the needs on work processes on the clinic

3.1.3 Characteristic definition

ID	Characteristic
N1C1	Manage Clinic's clients
N2C2	Manage Clinic's work procedures
N2C3	Manage outer procedures
N1C4	Manage patient's vaccination information
N2C5	Manage Financial related topics

3.1.4 Use Cases Definition

ID	Use Case
C1UC1	Maintain Owner
C1UC2	Maintain Patient
C2UC3	Maintain Clinical Record
C2UC4	Maintain Bath and Grooming Record
C2UC5	Maintain Appointment Record
C2UC6	Login
C2UC7	View Hospitalization
C3UC8	Generate Medical Prescription
C3UC10	Generate Complete Report
C3UC9	Generate Exam Routing
C3UC11	Load Exam File
C4UC12	View Vaccine Card
C4UC13	View Vaccination Schedule
C5UC14	Generate Financial Report
C5UC15	Register Costs
C5UC16	Evaluate Owner
C4UC17	Maintain Vaccination Record
C2UC18	Maintain User

3.2 Requirements traceability

3.2.1 Traceability tree

3.2.2 Requirement dependency matrix

More information in Boards of Requirement

3.2.3 Requirement traceability matrix

More information in Boards of Requirement

3.3 Attributes

3.3.1 Functional Requirements Attributes (Use Cases)

Requirementes attributes are the properties bind to them. The properties capture crucial information and we can use to a better management practice. The defined attributes to this project are:

Attribute	Description
Status	Gives the idea of how complete is the requirement
Priority	Declares the relative importance of the requirement to the stakeholders
Complexity	Indicate the effort level needed to the requirement implementation

3.3.1.1 Requirement Attributes values

For each of the requirement attributes defined there are some values they can assume. As the tables show:

Status

Level	Description
Complete	Indicates that the requirement was finished and implemented
In Progress	Indicates that the requirement is in process of implementation
Not Started	Indicates that the requirement was identified and waits to be started

Priority

Level	Description
High	Indicates that the requirement is highly important, with great value to the user
Medium	Indicates that the requirement has some importance, and it can be implemented when its needed or priorized
Low	Indicates that the requirement has low importance, representing an optional feature of the system

Complexity

Level	Description
High	Indicates that the requirement has high level of difficult, demanding great effort to be implemented
Medium	Indicates that the requirement has a certain level of difficult, demanding moderate level of effort to be implemented
Low	Indicate that the requirement has low level of difficult, demanding low effort to be implemented

3.3.2 Requirement Attributes matrix

ID	Requirement	Status	Priority	Complexity
C1UC1	Maintain Owner	Completed	High	Low
C1UC2	Maintain Patient	In Progress	High	Medium
C2UC3	Maintain Clinical Record	In Progress	High	High
C2UC4	Maintain Bath and Grooming Record	Completed	Medium	Low
C2UC5	Maintain Appointment Record	In Progress	High	High
C2UC6	Login	Not Started	Low	High
C2UC7	View Hospitalization	Not Started	Medium	Medium
C3UC8	Generate Medical Prescription	Not Started	Medium	Low
C3UC10	Generate Complete Report	Not Started	High	High
C3UC9	Generate Exam Routing	Not Started	Low	Medium
C3UC11	Load Exam File	Not Started	Medium	Medium
C4UC12	View Vaccine Card	Not Started	Low	Low
C4UC13	View Vaccination Schedule	Not Started	Low	Low
C5UC14	Generate Financial Report	Not Started	High	High
C5UC15	Register Costs	Not Started	High	Low
C5UC16	Evaluate Owner	Not Started	Low	Low
C4UC17	Maintain Vaccination Record	In Progress	High	High
C2UC18	Maintain User	Completed	High	Low

More information in Boards of Requirement

3.4 Requirement change management and workflow

The elicited requirement will be documented by the team after the application of elicitation techniques. After the documentation the requirements will be visible to all teammates who will help to describe the requirements till the development level. After the features description the requirements must be validated to be implemented.

When changes occurr the team is obligated to communicate to stakeholders and update the documents, this will help to all stakeholders to view what is happening in the project.

4. Mark

This document must be reviewed after the sprints, this plan must be accurated with other documents on this project and the sources of information.

More reviews are scheduled to be performed after every sprint from now on.