TOD.U : aplicativo de lembretes

Abstract

O presente trabalho de conclusão de curso apresenta o processo de desenvolvimento e documentação de um software com o fim de mostrar como usar a tecnologia para ajudar na organização dos compromissos e eventos dos usuários a fim de facilitar e auxiliá-los em seu dia-a-dia. O tema do projeto foi escolhido a fim de ajudar trabalhadores comuns que usam horários em suas profissões e usuários que têm dificuldades em se ajustar com aplicativos de alarmes que os forçam a seguir uma fórmula pré-programada. O trabalho foi feito através de uma entrevista aberta com stakeholder que levou a todo desenvolvimento da documentação inicial, desenvolvimento de um protótipo e planos futuros, métodos como o Business Model Canvas, Levantamento de Requisitos contendo Elicitação e especificação dos Requisitos, BPMN, Requisitos Funcionais, Requisitos funcionais e Não Funcionais, Regras de Negócio, Casos de Uso e Diagramas Entidade-Relacionamento. O resultado alcançado foi o desenvolvimento de um aplicativo com toda documentação necessária concluída para uma aplicação funcional e um protótipo que cumpre seu objetivo de mostrar como a aplicação seria em seu estado final. Assim, conclui-se que apesar do desenvolvimento de um software em prática ser muito diferente da sua teoria, com disciplina, paciência e experimentação, uma ideia nova pode ser refinada até se tornar um produto viável.

This final course project presents the development and documentation process of a software program with the purpose of showing how to use technology to help organize users' appointments and events in order to facilitate and assist them in their daily lives. The theme of the project was chosen in order to help ordinary workers who use schedules in their professions and users who have difficulty adjusting to alarm applications that force them to follow a pre-programmed formula. The work was done through an open interview with stakeholders that led to the development of the initial documentation, development of a prototype and future plans, methods such as Business Model Canvas, Requirements Gathering containing Requirements Elicitation and Specification, BPMN, Functional Requirements, Functional and Non-Functional Requirements, Business Rules, Use Cases and Entity-Relationship Diagrams. The result achieved was the development of an application with all the necessary documentation completed for a functional application and a prototype that fulfills its objective of showing what the application would be like in its final state. Thus, it is concluded that although the development of software in practice is very different from This final course project presents the development and documentation process of a software program with the purpose of showing how to use technology to help organize users' appointments and events in order to facilitate and assist them in their daily lives. The theme of the project was chosen in order to help ordinary workers who use schedules in their professions and users who have difficulty adjusting to alarm applications that force them to follow a pre-programmed formula. The work was done through an open interview with stakeholders that led to the development of the initial documentation, development of a prototype and future plans, methods such as Business Model Canvas, Requirements Gathering containing Requirements Elicitation and Specification, BPMN, Functional Requirements, Functional and Non-Functional Requirements, Business Rules, Use Cases and Entity-Relationship Diagrams. The result achieved was the development of an application with all the necessary documentation completed for a functional application and a prototype that fulfills its objective of showing what the application would be like in its final state. Thus, it is concluded that although the development of software in practice is very different from.