ProDOC: Uma Proposta de Processo de Desenvolvimento Orientado a Comportamento

• Yury Lima UNIPAMPA
• Juliana Medeiros UNIPAMPA
• Luciano Marchezan UNIPAMPA
• Elder Rodrigues UNIPAMPA
• Maicon Bernardino UNIPAMPA

Abstract

Due to the difficulties of understanding the requirements in the Software Engineering scenario, this work addresses a proposed development process, which aims to improve the understanding of the system requirements, impacting the implementation and creation of the test cases, according to behavior of the software. The Behavior Oriented Development Process (ProDOC) uses specifications for the elicitation and elaboration of use scenarios for each functionality, in order to increase understanding of the requirements and improve the validation of the final system. To evaluate ProDOC, a questionnaire was carried out with researchers and / or professionals of the area, thus showing the acceptance and relevance of the proposal.

References

Astels, D. (2003). Test driven development: A practical guide. Prentice Hall Professional Technical Reference.

Beck, K., Beedle, M., Van Bennekum, A., Cockburn, A., Cunningham, W., Fowler, M., Grenning, J., Highsmith, J., Hunt, A., Jeffries, R., et al. (2001). Manifesto for agile software development.

Cucumber (2018a). BDD Overview. Disponível em: https://docs.cucumber.io/bdd/overview/. Acesso em: 07.07.2018.

Cucumber (2018b). Gherkin Reference. Disponível em: https://docs.cucumber.io/gherkin/reference/, addendum. Acesso em: 07.07.2018.

North, D. (2006). Introducing behaviour driven development. Better Software Magazine.

Schwaber, K. and Beedle, M. (2002). Agile software development with Scrum, volume 1. Prentice Hall Upper Saddle River.

Schwaber, K. and Sutherland, J. (2011). The scrum guide. Scrum Alliance, 21.

Souza, G., Nunes, J., Oliveira, J., Araújo, N., Gorgônio, F., and Vale, K. (2015). Diretrizes para uma metodologia de desenvolvimento de software aplicada a startups de tecnologia da informação.