Deliverables
What we've shipped
Formal Deliverables
The five major documents and code we hand in over the semester.
- D1Delivered
Specifications→
User stories, functional and non-functional requirements, and interfaces for Nora.
- D2Planned
Design Document→
A guide for future developers: architecture diagram, code repository and module structure, data definitions, and the reasoning behind our design decisions.
- D3Planned
Test Plan→
What we would test with unlimited time and exactly what we will test: automated unit tests, integration and system tests, acceptance testing, environments, and who tests when.
- D4Planned
User Manual→
Our documentation plan, plus guides for researchers using Nora and administrators deploying and managing it, with how-to videos for our client.
- D5Planned
Code→
Nora's source code on GitHub, consistently styled and documented, with a README explaining how to install and run it.
Milestones
Smaller checkpoints along the way, several of which feed into the formal deliverables.
- M1Delivered
Project Web Site→
This site: our team, schedule, meeting notes, and every deliverable in one place.
- M2Delivered
Team Rules & Coding Practices→
How we communicate, meet, and share work, plus our style guides and review rules.
- M3Delivered
Project Concept→
What Nora is and the problem it solves for UNC researchers, on our overview page.
- M4Delivered
User Stories→
What researchers and administrators need to do with Nora, from our specification.
- M5Delivered
System Metaphor→
A shared mental model of how Nora works, for the team and our client.
- M6In Progress
Platform Selection→
The alternatives we evaluated for each part of Nora's stack, and what we chose and why.
- M7In Progress
Architecture Diagram→
How Nora's frontend, backend, database, and external services fit together.
- M8Planned
Client Handoff Plan→
How Nora's code, hosting, and accounts pass to UNC Research at the end of the semester.