Guia de metodologias e boas práticas em Engenharia de requisitos

Abstract

The requirements are a basis for the software. A requirement that is not well understood, well written and well managed can have major impacts on the project. This is when the company takes requirements engineering activities into account in its processes. Some companies that have a hard time establishing a quality process in the requirements engineering area and are often lost and not knowing which method to use best, end up starting to do projects without using a quality process, starting directly for programming and processing this is a habit in the company leaving the product with the quality well below what its customers wanted. Thus, this work proposes a guide that selects a requirements engineering process, based on the number of members in the teams, the experience of the team members in relation to the requirements engineering areas, whether it is an IT company, or with IT sector, or is Startup, or a group of faculty. In addition to taking into account the development time that projects require, or whether it is focused on making software to order or software as a service.