Power Point Presentation (PPT) for Project for "COVID Tracking digital app" base on attached documents

After reviewing the different methodologies determine which one your group will follow by identifying the phases and how they will help to define the information system.

Our team has collectively decided to utilize the Waterfall Development methodology. The Waterfall method is typically used for project analysts and users to proceed sequentially from one phase to the next. The first phase is the planning phase. This phase is crucial as the project team needs to know and understand what they must design. In our team project, there will need to be a lot of planning. Planning out the development, requirements, processes, functionality, potential bugs, and feature addition are only a few things that will make this project successful. The team needs to keep in mind that this phase is going to determine the entire outcome of the project. Providing this information and similar information will allow the team to study, finalize, and mark this phase.

The second phase is the analysis phase. Analysis usually results in designing models, schema, and business rules. This requirement is divided into two parts: requirement gathering and requirement specification. Requirement gathering and analysis is the gathering of information and requirements from the customer for product development. This is where the project team will collect all the project requirements and flaws. From there we will eradicate any inconstancies and incompleteness from the systems development. In the requirement specification part, the project team will analyze all of the requirements that were documented in the last part. An SRS (Software Requirement Specification) document will then be made to settle any disputes in the future.

The third phase of the model is the Design phase. In this phase, the project team will study the requirements for the product design. Studying this will help the overall structure of the system design. Requirement specifications will mostly be studied and verified in this phase. We will make the utmost effort to understand what the final product will look like, along with actions that will need to be taken from there.

The fourth phase is the implementation phase. Now that system design is fully verified our project team can start the implementation phase. In this stage, the system inputs from the system are taken and developed into smaller programs called units. These units will then be set to test for the desired functionality. Each unit will then undergo development. The full functionality will be tested. Maintenance in this phase should be minimal if the previous phases were well executed. Our team will work vigorously in this phase to ensure that there are no known bugs and implementation goes flawlessly.

The fifth and final stage is the system phase. This phase is to ensure that the system is fully functional and performs optimally until the system reaches the end of life. For this phase, our team will ensure all aspects of the project are properly and consistently defined, executed, and functional. The team will craft a closing deliverable proving that the original scope has been met and all the SRS requirements have been met. In this phase, we will go above and beyond on showing the end-users how to operate this new system and show how it is more effective than the last method. We will answer any questions and put all concerns to rest.

Carefully determine and identify the tools that you will use to create the information system.

This project will require many tools. This list will cover a lot of the tools (The team is not limited or required to use all these tools): Network Diagrams, Gantt Charts, Work Break Down Structures, Project Documentation, Productivity Software (Notion, Asana, etc.), Microsoft Office (Access, Excel, Word, PowerPoint, etc.), Reporting software (Wrike, Hive, etc.), app development software (Creatio, Skuid, etc.), Cloud services for databases (Azure, AWS, etc.). These tools are just a few necessary options, which are going to improve the quality of our project. During the planning phase, we will narrow down the software list and best utilize it across our team.

Once you have identified the methodology and tools you will be able to determine the techniques that you will use to determine and create the deliverables.

After carefully examining the project and the available techniques, Work Breakdown Structure (WBS) is the best option. Most projects seem overwhelming at first, but the Work Breakdown Structure seems to organize the work into smaller more manageable pieces. This will allow our team to execute smaller tasks faster and create a highly desired product. In the late stages of the planning phase, we will create a list. This list will have the final product at the top and a line that goes down the page to box(s) that represent the larger tasks that lead to completing the project. Each of these boxes is then attached with lines that go under it with smaller tasks.