This is the full stack application for the EMURR: Exhibit Marker Uniform Resource Router unit. This project features a WYSIWYG editor where you can edit, save, and download tours built and compiled to be hosted on a Raspberry Pi.
[ ] 2. Executive summary (Section 1)
An administrative and technical abstract, which includes a brief description of the project, the project objectives, and the technical approach. This is really an overview of 3A, 3B, 3C, and 3D. This is page number 1. (Should be one full page)
[ ] Brief description of the project
[ ] Project objectives
[ ] Technical approach
[ ] 3. Technical content
[x] A. Identification of the project and its significance, motivation
[x] What is EMURR? (2.1-3)
[x] Personal motivations (Section 3)
[x] Broader impacts (2.4)
[x] Legal, Ethical, and Privacy Issues (Section 4)
[ ] B. Technical objectives, goals, specifications, and requirements (mostly text and numbers)
[ ] Technical objectives (5.1)
e.g. We want to make interactive tours possible at physical locations with poor reception
[x] Goals/Intended features (5.2)
e.g. Our goal is to create tour sites that can be exported to a Pi for offline tours
[x] Specifications (Section 6)
MySQL, Router, Raspberry Pi, NFC tags
[x] Requirements (Section 6)
e.g. a WYSIWYG website editor, admin portal, export functionality, garden sticks
[x] C. Research and investigations (text, numbers, tables, charts, figures, diagrams) (Section 8)
[x] D. Explicit Design Summary with diagrams (Section 9)
omosa
commented
2 years ago
Requirements:
[x] 1. Cover page
[ ] 2. Executive summary (Section 1) An administrative and technical abstract, which includes a brief description of the project, the project objectives, and the technical approach. This is really an overview of 3A, 3B, 3C, and 3D. This is page number 1. (Should be one full page)
[ ] 3. Technical content
[x] 4. Administrative content
[ ] 5. Project Summary and conclusions (should be ~1 page) (Section 17)
[x] 6. References (Section 18)
[ ] 7. Appendices