Mercer University · Fall 2026 Capstone

Network Outage Coordination and Automated Notification System

A system for signing in by role, selecting a network node, reviewing downstream outage impact, coordinating approval, and showing approved site notices.

Malcom Daggett · B.S. Information Technology and Informatics

Working Prototype

Browser version available

Try the expanded outage system in your browser. It includes 31 fictional sites, a central WAN core, five regional hubs, role-based accounts, approval decisions, and simulated site notices. No Python installation or PythonAnywhere account is needed to try it.

Demo password: CapstoneDemo!26 for the preconfigured accounts below. On the sign-in screen, expand Use a fictional demo account, choose an account, and select Sign in. Sign out before changing roles.

Demo accounts for the main workflow
RoleEmailWhat to try
Network admin / engineer
Jordan Reed
jordan@example.testSelect a node, review downstream impact, and submit an outage request.
Approver
Aisha Grant
aisha@example.testReview a submitted request and approve or reject it.
Site contact
Elena Torres
elena@example.testRead approved, released notices for Site Alpha.
Suggested walkthrough
  1. Sign in as Jordan and select Create outage.
  2. Choose a complete node outage and select node 20. Its expanded branch includes nodes 21–25. Node 30 belongs to another region.
  3. Enter the work details and UTC window, review the affected services and recipient groups, then submit.
  4. Sign out and sign in as Aisha. Open the request and record an approval or rejection with a comment.
  5. After approval, sign in as Elena to read the Site Alpha notice. A rejected request does not release a site notice.

The demo clock is fixed at November 1, 2026, 1200 UTC. For a routine example, use November 15, 2026, 2200–2300 UTC. Work under 240 hours away requires urgent selection and a reason; it still needs approval.

All network data and notices are fictional. Visitors share the hosted demo database. The map follows configured required dependencies; it does not monitor a live WAN or calculate redundant-path failover. The planning PDFs retain the smaller illustrative network; this prototype expands it to 31 sites.

01 / Project Planning

Due October 19, 2026

Planning documents establish the problem, represented stakeholders, project boundaries, weekly schedule, and acceptance criteria. The available files below form the current planning baseline.

Evaluation approach: I am the developer and a primary intended user. This capstone uses a practitioner case study, scripted functional tests, and structured self-walkthroughs. No interviews, recruited prototype testers, or participant questionnaires are planned. Other operational stakeholders are represented roles.

Weekly progress archive

Keep each update so changes to the original plan remain visible. Planned hours are estimates; actual hours have not yet been logged here.

November 8, 2026 · Midterm demo recorded

Recorded a product demonstration lasting approximately 14 minutes 26 seconds and prepared a short midterm progress report. This page includes a video player and direct links for the recording and report.

Next: Upload the MP4 to the videos folder and the report to the documents folder, then verify playback and submit the public video URL.

November 8, 2026 · Expanded browser prototype available

Built an expanded fictional WAN with 31 sites, a central core, five regional hubs, site-contact accounts, and full-network and regional map views. The application now runs on PythonAnywhere and can be opened through this page.

The hosted application was opened and tried successfully. Automated checks covered role access, saved outage impact, approvals, urgency, and site-notice privacy. Formal practitioner evaluation and final reporting remain separate deliverables.

Next: Record structured walkthrough results, capture evidence, document any issues, and continue preparing the evaluation and user-help materials.

November 8, 2026 · Account and branch-map design revised

Updated the planning and design PDFs for Network admin, Approver, and Site-contact accounts. Each role has its own home screen. Added a selectable-node design that predicts downstream impact from saved required dependencies.

The sample complete outage at node 20 affects nodes 21 and 22; unrelated node 30 remains unaffected. Updated the database plan, success checks, simple user tasks, and the timeline to 136 estimated hours. The illustrated personas remain consistent with the stories.

Next: Upload this page and the revised PDFs, then implement and test the account and map features. These documents describe planned behavior, not a finished application or completed tests.

November 8, 2026 · Personas and storyboards revised

Revised the design documents following instructor feedback. The personas now show fictional people with AI-generated portraits. The illustrated storyboards use those same people to show what happens during a routine product outage and an urgent entire-SSP request.

The scenes explain each person's action, concern, and the system response. Internal updates happen before an approved customer notice. The rejected urgent request does not produce a customer notice.

Next: Upload the revised PDFs and this landing page, then use the stories and task list to guide prototype development and self-testing.

October 29, 2026 · Project design documents prepared

Prepared personas, stories and storyboards, a user task list, the application structure and its rationale, and database diagrams with table descriptions and normalization notes. Revised the scope, stakeholder map, and success measurements in simpler language. The stakeholder link now opens the PDF.

Next: Review the design choices, upload the updated files, and prepare the midterm report and recording due November 2. Prototype building and test execution remain future work.

Actual effort: Not recorded. This update does not claim an October 26 submission or completed FTP publication.

October 20, 2026 · Planning materials prepared

Prepared the revised proposal, scope, weekly timeline, and success-measurement PDFs. Prepared the stakeholder map and added the supplied Figma design link. The evaluation plan now reflects practitioner self-testing.

Next: Publish this package, verify document links and Figma viewer access, and complete the design deliverables due October 26.

Actual effort: Not recorded. This entry does not claim that FTP publication or testing has been completed.

Future weekly update format

Date; original planned task; actual work; actual hours; evidence/version link; schedule variance; blockers; next action. Append a new dated entry each week rather than overwriting earlier entries.

02 / Project Design

Due October 26, 2026

These PDFs record the design and the checks planned for evaluation. The working browser prototype is linked above. The documents use a smaller illustrative network, while the prototype includes an expanded 31-site WAN.

Design approach: I am a primary intended user and will test the prototype myself. The personas are fictional examples of project roles, with AI-generated portraits. The same people appear in the storyboards. They are not interview subjects or recruited testers. All scenarios use fictional information and simulated notices.

How the design connects to the project goal

Users register, request a role, and sign in after verification. The engineer selects a node and chooses a product or complete-node outage. The map shows configured downstream dependencies before the engineer reviews services, UTC times, urgency, recipients, and the notice preview. A separate approver decides. Only then, after internal approval updates, are site-specific simulated notices released to authorized site contacts.

The proposed database stores accounts, site access, nodes, required dependencies, and submitted outage impact alongside decisions and site-specific notices. The first map uses fictional single-parent dependencies, without live monitoring or alternate-route calculations. The earlier Entire SSP choice is now defined as a complete outage of the selected node and its dependent branch; sharing a group name alone does not mean a node is affected.

03 / Midterm Product Demo

Recorded demo available

A recorded walkthrough of the network outage system and its design, including role-based access, the WAN map, outage requests, approvals, and site contact notices.

Video length: approximately 14 minutes 26 seconds. Use the player controls to pause, adjust the volume, or view full screen.

04 / Project and Prototype Development

Due November 23, 2026

The expanded working prototype is available in the browser. It uses HTML, CSS, JavaScript, Python with Flask, and SQLite, and is hosted on PythonAnywhere. Supporting development documents and formal evaluation records will be added as they are completed.

Open Working PrototypeTry the 31-site WAN, three login roles, outage requests, approval decisions, and simulated site notices.Open application ↗
System SpecificationFunctional requirements, roles, validation rules, workflow states, and notification behavior.Planned
Software, Languages, and PlatformFinal technology selections, environment, dependencies, and setup details.Planned
Prototype Versions and Testing EvidenceVersion 1.0 onward, screenshots, test records, defects, and revisions.Planned

05 / Usability Testing and Practitioner Evaluation

Due November 30, 2026

Evaluate prototype version 3.0 or 4.0 against the design task list and success measurements through structured self-walkthroughs and scripted tests.

Evidence to collect

  • Test ID, requirement, version, date, and fictional inputs.
  • Expected versus actual results and pass/fail status.
  • Login roles, site access, downstream node impact, UTC, urgency, recipients, and approval checks.
  • Defects, design reflections, revisions, and retest evidence.

Interpretation

Report technical correctness and case-specific findings. Self-recorded task times describe my own performance. Developer familiarity and confirmation bias limit claims about unfamiliar users or broader usability.

The practitioner evaluation approach is documented for instructor review against the course's usability-testing requirement.

Evaluation Report and ReflectionActual results, limitations, prioritized findings, final changes, and regression checks.Planned
Preliminary coworker feedback retained as project context

Earlier feedback identified confusion between a product outage and an entire-SSP outage. I added explanations to the initial Create Outage popup. Other comments concerned UTC entry, urgent selection within the 10-day waiting period, and internal approval notifications before planned-outage customer notices.

This historical feedback informs requirements. It does not establish measured usability results or commit this capstone to further participant testing.

06 / Final Prototype Release and User Help

Due December 7, 2026
Final PrototypeVersioned source, fictional seed data, setup instructions, release notes, and known limitations.Planned
User-Help DocumentsAccount access, node selection and downstream impact, scope choices, UTC, urgency, approvals, and site notices.Planned

07 / Capstone Report and Final Presentation

Due December 10, 2026
Final Capstone ReportBackground, planning, design, implementation, actual evaluation findings, reflection, and appendices.Planned
Final Presentation and Recorded VideoFinal workflow demonstration, design decisions, evidence, limitations, and outcomes.Planned