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.