Document the design for your application project.

Use a Visio Software application to develop the design employing the following computer$-$aided software engineering $($CASE$)$ modeling tools:

Mock$-$up or storyboard of the high$-$level user interface screens

Choose two of the following to complete along with your mock$-$up or storyboard:

Use case to represent the application as a whole.

Functional decomposition diagram that shows all of the functions that the system or application will support.

Entity$-$relationship $($E$-$R$),$ data flow diagram $($DF$),$ or class diagram that effectively represents the data that are required for your application or system.

Sequence diagram to represent the timing of various activities within the application or system.

Use the information below and create a mockup in Microsoft Visio.

Development Model

The System Development Life Cycle $($SDLC$)$ was chosen due to its structured approach, ensuring thorough planning, robust testing, and scalable design.

Project Suitability

The SDLC$\text{'}$s systematic framework is ideal for the complex requirements of school systems, ensuring operational efficiency, scalability, and robust communication.

Project Overview

Timeline: Six$-$month development phase; deployment aligned with the next academic year.

Customer Requirements: Simplify administration, enhance communication, and provide centralized performance tracking.

System Scope: Educational institutions requiring centralized student and administrative process automation.

Key Elements: Database management, role$-$based access, communication tools, reporting, and integration with IT infrastructure.

Suitability: The system addresses common educational and administrative challenges, complying with privacy and educational standards.

Capabilities: Automates processes, improves communication, ensures real$-$time data access, and maintains scalability and security.

Intended Users: Teachers, students, parents, administrators.

Stakeholders: School board, IT department, school staff.

Requirement Specification

Functional Requirements: Grade management, attendance reporting, secure messaging, role management, scheduling, and notifications.

Nonfunctional Requirements: Multi$-$device accessibility, data security, scalability $(500$ concurrent users$),$ user$-$friendly interface, compliance with FERPA.

Tools by Phase

Planning: Microsoft Project, Trello.

Analysis: Lucidchart, Visio.

Design: Figma, Adobe XD$,$ Visual Paradigm.

Implementation: Visual Studio, GitHub.

Testing: Selenium, TestRail.

Deployment: Docker, Jenkins.

Maintenance: Splunk, Jira.