Milestones
List view
Link to Page: https://capstone.cse.sc.edu/form/peer-reviews-f24/ Deliverables: - [ ] Fill out the form.
Due by December 9, 2024Link to the Page: https://capstone.cse.sc.edu/milestone/poc-demo/#due-date Deliverables: - [ ] Create an Issue in your repo titled "PoC Demo" and add your video to it. Assign the Issue to @josemvidal You will create a short video that shows off what you have accomplished so far. It should be no longer than 5 minutes. In the video you will cover: - [ ] What your app is meant to do? What problem does it solve? (1 slide, or equivalent) - [ ] What technologies are you using? Why? (1 slide, o equivalent) - [ ] A quick demo of what you have working so far. (0 slides) - [ ] What features you will be implementing next semester.
Due by December 6, 2024Link to Page: https://capstone.cse.sc.edu/milestone/proof-of-concept/ Deliverables: - [ ] Create a git tag named v0.1 on the commit that marks the release: git tag v0.1 - [ ] Push tags to GitHub: git push --tags. Once pushed to GitHub you will find a Release page called v0.1 in your GitHup repo page. You can rename it to Proof of Concept if you like. We will look for either. If you can't get tags to work just create the Release called Proof of concept with GitHub. If you have an Android mobile app you will: - [ ] Upload your binary (.apk .exe, etc.) to that Release. To do this on GitHub you just click on the Release, then click "Edit Tag", then click where it says "Attach binaries by dropping them here or selecting them".
Due by December 6, 2024•13/13 issues closedLink to Page: https://capstone.cse.sc.edu/milestone/ethical/ Deliverables: - [ ] Ethical Issues in the wiki page - [ ] Legal Issues in the wiki page - [ ] Security Issues in the wiki page
Due by November 3, 2024Link to Page: https://capstone.cse.sc.edu/milestone/source-control/ Deliverables: You must be able to - [ ] pull from the team repo, - [ ] build, - [ ] run application locally (laptop or emulator) - [ ] commit to team repo, - [ ] push to the team repo, - [ ] merge your branch into master, via pull request or regular merge, - [ ] and resolve a merge conflict.
Due by October 27, 2024Link to page: https://capstone.cse.sc.edu/milestone/architecture/ Deliverables: - [ ] List all the languages/frameworks/libraries/services/APIs you plan to use. Explain how they will tie together. For example: This will be a native Android app written in Kotlin, using the android.graphics library, using firebase real-time database for cloud data, and firebase authentication for user accounts. - [ ] What package/build manager will you use? npm, gradle, yarn, flutter, pipenv, etc. - [ ] List what each person will work on. Everyone must make significant code contributions, or they will fail the class, see Syllabus. - [ ] Make sure all the images (if any) are embedded in the wiki page and hosted at GitHub. - [ ] Make sure the wiki page is easy to read. If you are building a mobile app: - [ ] Release: How will you create and deliver a binary to testers? Explain. Note that the testers include us (the teachers of this class, when we grade your app). You must deliver a simple to install app: double-click to install. - [ ] Are you using Virtual Machines (vmware, vbox, etc) or Containers (docker) for development? If so, explain. - [ ] The Models for your app. These could be UML class diagrams, or just models with attributes (with type) and descriptions (in English). - [ ] How will your app maintain state? in memory? or database? or both? Note this in your Model Classes. - [ ] If you are using a db-backend (say firebase) then include the Database schema: set of tables/documents with list of attributes and their types. - [ ] List of common queries you expect will be needed. Do any of then need to join tables? - [ ] The Views of your app: name, describe. Embed the images from your Design Milestone. Typically, one page in the app is composed of multiple View elements.
Due by October 20, 2024•1/1 issues closedLink to page: https://capstone.cse.sc.edu/milestone/research/ Deliverables: - [ ] Each person must create their personal repo by following this link at GitHub. Your repo will have the name research-yourusername. - [ ] In that repo you will place your sample project built using your team's chosen framework. It will have multiple commits, all by you. You might want to link to it in your Weekly Report. - [ ] The project will be more than just "hello word", or cut-n-paste from a tutorial. You can start with the tutorial code, but you must add your own code to their code. The app should have some minimal interactivity: user enters some data,program does something with it and shows the user. - [ ] Make a short video demonstrating how you start your app (say, from your IDE or command-line) and then use your app. Add the video to the research-repo ans an Issue, or to youtube, or similar. Add a link to your video in your Readme.md file or @instructors in the Issue.
Due by October 13, 2024Link to page: https://capstone.cse.sc.edu/milestone/requirements/ Deliverables: - [ ] Make a Requirements wiki page and list your requirements there. - [ ] Each item should succinctly explain a feature. - [ ] Each one will have a number. You can add sub-numbering, 1.1, 1.2, 1.2.1, etc. if you want. - [ ] Each one will be marked as either: Required, Desired, or Aspirational. - [ ] Add all the Proof of Concept Issues to your GitHub Issues with label:enhancement, milestone:Proof Of Concept. These are what you will implement by the end of this semester. I will approve them or ask for more/less. I will do so in your GitHub Issues.
Due by October 13, 2024•6/6 issues closedLink to page: https://capstone.cse.sc.edu/milestone/design/ Deliverables: - [ ] Add one page to your wiki called "Design" and add the images of your design here, along with some textual description of each screen and what it is used for. You can split it into multiple pages but, if you do, make sure the "Design" page has links to all of them (so, it works as an index page). Do not make any changes to the wiki pages used for this milestone after the deadline. Wait until after you receive the grade for the milestone to make any further changes to these pages.
Due by September 29, 2024•2/2 issues closedLink to page: https://capstone.cse.sc.edu/milestone/personas/ - [ ] Add at least three personas to your wiki. Three distinct user types, and each persona must have a name, photo, and personal history. - [ ] Add a "User Stories" wiki page with at least 9 user stories covering the most common use cases for the app. Should be in the form: As \<the name of one of your personas> I want a <feature> so that I can \<satisfy a need>.
Due by September 15, 2024•4/4 issues closedLink to page: https://capstone.cse.sc.edu/milestone/form-teams/ Deliverables: - [X] Add all of this semester's milestones to the GitHub issues. - [X] Add a "Team Organization" wiki page with details on the time for team meetings, chat service, and minimum frequency for message checking. - [X] Add a "Project Description" wiki page with details on the description of the project, the technologies, and the client.
Due by September 8, 2024•3/3 issues closed