SOFTWARE REQUIREMENT ANALYSIS PROCESS.

This part will be charged to the requirement analysis team, which will be composed of specialised workers in software engineering, and once the requirement analysis is finished the team should send it to the Software design team.

• Art1- Once a document with a textual description of the software is received, the team should divide it into sections and work separately on them.

• Art2- Once the first iteration on the document is made a full review should be made obtaining at least the functional requirements.

• Art3- Every functional requirement should be written in a .docx taken into account the name policies.

3.1- The name of the functional requirements should follow the next rules:
3.1.1- The first two letter should be FR (functional requirement)
3.1.2- After establishing that it is a functional requirement a hyphen splitting the FR and the next property.
3.2.3- Then we need FR-P000 corresponding P000 to the Project identificator
3.2.4- After that another hyphen should be written
3.2.5- Finally the number of the functional requirement FR-P000-000 being 000 the incremental number of the requirement

• Art4- Once the first analysis of the document is made, the team should precced to repeat the analysis and find deeper requirements.

• Art5- Every non-functional requirement must be written in a .docx taken into account the name policies in the Art 3.1 just taking into account that the preffix now should be NFR instead of FR. (e.g: NFR-P321- 003)

• Art6- Since the functional and non functional requirements should have been correspondently documentated and analysed the team can continue looking for non-functional requirements.

6.1- The name of the document for the functional requirement must be of this type: FR000.pdf, being 000 the ID of the Project.
6.2- The name of the documentatio for the non fucntional requirement must be of this type: NFR000, being 000 the ID of the Project.

• Art7- Once that all the requirements have been concreted, both documents, the one with the functional requirements and the other one with the non-functional requirements should be sent to the design team.