Sprint #1 - Daily Scrum #13
Product: CMS API
Sprint Summary
Daily Objectives
- hey
Notes
I want to make a few more Use Case diagrams
Actors:
- Developer/Freelancer Owner
- manageProject
- manageUsers
- Clients
- Public User/Client Sites
This ties in well to the API design
API Reference
- HTTP Responses
- JSON Error Responses
- References
- ResourceName *EndpointPath
- Requests + Parameter + Description
- Ex: /anime/{id}/(/request)
/anime/{id}/episodes - Remarks
- Examples
Make a ‘DESIGN CONSIDERATIONS’ for the architecture portion
I think I should go through all my notes and copy paste everything I’ve written down and all the reasonings
[note: this was originally written in Google Docs: here’s the original with all the important snippets from other notes]
Objectives Completed
-
added a ‘design considerations’ section for different parts of the sdd
-
started writing the API Design/Reference portion of the sdd
-
created data design chart/graph for the content management service using the LucidCharts webapp