Este trabalho, apresenta uma anális

Este trabalho, apresenta uma análise da avaliação do processo de rastreabilidade de Software, em uma aplicação, com base, no programa de Melhoria de Processo de Software Brasileiro, o modelo MPS.BR. Neste modelo, é apresentado, como é rastreado os requisitos de um sistema. Foi definido, por padrões e tipos a serem seguidos, deixando em evidência, os benefícios gerados, e esperados, da rastreabilidade de software, na gerência de requisitos no MR-MPS.BR. Foram definidos os artefatos a serem utilizados, e os resultados obtidos, foram apresentados, através de uma avaliação da rastreabilidade de requisitos, comparando a rastreabilidade em um projeto que utilize Metodologia Ágil (Scrum) de projetos que utilizem Metodologia Tradicional (RUP) em uma empresa certificada em nível C do MPS.BR. É evidenciado a diferença da matriz de rastreabilidade de cada metodologia, a relevância de seguir o processo e de manter a rastreabilidade para chegar à um resultado da entrega do produto final com qualidade. Os riscos que se corre e afetam o projeto, ao não seguir o processo, e não mantendo a rastreabilidade do mesmo. Por fim, será apresentado o resultado das diferenças existentes, a preferência, o porquê de se trabalhar com cada metodologia e seus prós e contras, que serão obtidos através de um questionário, aplicado aos colaboradores, que trabalham na empresa.

Resultados (Inglês) 1:

This work presents an analysis of the evaluation of the process of traceability of Software in an application, on the basis of the program of Brazilian Software process improvement, the MPS.BR. model in this model, is presented, as is traced a system requirements. Was defined, for patterns and types to be followed, leaving in evidence, the benefits generated, and expected, the traceability of software requirements management in the MR-MPS.BR. Were set the artifacts to be used, and the results were presented, through an assessment of requirements traceability, comparing the traceability in a project that uses Agile (Scrum) projects that use Traditional Methodology (RUP) in a company certified in level C of the MPS.BR. Is evidenced by the difference of the traceability of each methodology, relevance to follow the process and to maintain the traceability to arrive at a result of the delivery of the final product quality. The risks they run and affect the project, to not follow the process, and not keeping the traceability of the same. Finally, the result of the differences, the preference, why work with each methodology and its pros and cons, that will be obtained through a questionnaire, applied to employees, who work at the company.

Resultados (Inglês) 2:

This paper presents an assessment of the analysis of software traceability process in an application, based on the Brazilian Software Process Improvement program, MPS.BR. model In this model it is displayed as is tracked requirements of a system. Was defined by standards and types to be followed, leaving evidence, the benefits generated, and expected, software traceability, management requirements in MR-MPS.BR. the artifacts were defined to be used, and the results were presented through an assessment of the traceability requirements, comparing traceability on a project using Agile methodology (Scrum) projects using traditional methodology (RUP) in a company certified level C MPS.BR. It is evident the difference traceability matrix of each methodology, the importance of following the process and maintain traceability to get to the result of the delivery of the final product quality. The risks we run and affect the project, by not following the process, and not maintaining the traceability of it. Finally, the result of the differences will be presented, preference, why working with each methodology and its pros and cons, which will be obtained through a questionnaire applied to employees working in the company.

Resultados (Inglês) 3:

This work presents a review of the evaluation of the traceability process of software in an application, on the basis, in the program of Brazilian software process improvement, the model mps.br. In this model, is presented, as is tracked the requirements of a system. It was defined by standards and types to be followed, leaving evidence of the benefits generated, and as expected, the traceability of software in the management of the requirements in the mr-mps.br. Have defined the artifacts to be used, and the results obtained were presented through an assessment of the traceability of requirements, comparing the traceability in a project that uses the agile methodology (scrum) projects that use traditional methodology (RUP) in a company certified to level C of the mps.br. It is shown the difference of the traceability matrix of each methodology, relevance to follow the process and maintain traceability to arrive at a result of the delivery of the final product quality. The risks they run and affect the project, by not following the process, and not maintaining the traceability of the same. Finally, it will be presented the result of differences, the preference, why to work with each methodology and its pros and cons, which will be obtained through a questionnaire, applied to the employees, who work in the company.