Um estudo de caso utilizando framework Scrum com artefatos UML para apoio ao desenvolvimento de software

• Autor(a) principal: Salomão, Diego
• Data de Publicação: 2016
• Outros Autores: Silva, Maria Luiza da
• Tipo de documento: Trabalho de conclusão de curso
• Idioma: por
• Título da fonte: Repositório Universitário da Ânima (RUNA)
• Texto Completo: https://repositorio.animaeducacao.com.br/handle/ANIMA/10958
• topic: Metodologias de desenvolvimento; Metodologias ágeis; Scrum; Scrum com UML

Software Engineering applies different methods of software development processes. We can list among them the classic or waterfall model and the agile model: the classic model is strict when it comes to software documentation and makes use of the Unified Modeling Language (UML) for the preparation of different diagrams which provides different views of the system. The agile model priorizes the interaction with people even more than documentation, what doesn´t mean that documentation is not important. Actually, it is really difficult to maintain a up to date documentation in this method due to the several changes during the system development phase. Besides that, user¿s involvment is imperative. It is over the processes. This paper presents an applied research that documents and conduces the development of a software which makes use of the Scrum Framework as its characteristics (computer's users stories and acceptance criterias). Also it presents some UML diagrams as the use case diagram, the class diagram and the sequence diagram in a case study. The addition of some UML diagrams in a development process using Scrum can add up a lot even though its a project using agile principles. It helps the project in a way it contains the minimum documentation necessary to develop and it also values the process. All of that without losing the agile focus . To test the objective of this work was carried out a development of a management software for a school canteen with its simple functionalities, following the Scrum. Their UML diagrams and expected characteristics of Scrum were prepared at the end. The software was developed on time and the acceptance criterias have been met, which shows a positive result of the methodology used in the scenary.