-
Notifications
You must be signed in to change notification settings - Fork 1
Milestones
List view
https://capstone.cse.sc.edu/milestone/release1.0/ It will have all the features implemented and have fixed all the bugs in your issues list.
Due by April 22, 2024•19/19 issues closedhttps://capstone.cse.sc.edu/milestone/website/ You will use github pages (click on "Project Site" and follow the directions, your site's URL will look like http://sccapstone.github.io/demo/, for my 'demo' repo) to create a website for marketing your app. The site must have: 1. Embed the video from the Final Demo. Use a placeholder if video is not ready. 2. Some other text explaining how and why to use the app. 3. Images. Use screenshots of your app. You might want to also use free stock images: compfight. stockvault. 4. An about page, listing your names. Linking to your linkedin profile might help your personal marketing. 5. Link to your github repo, even if private. Make your github repo public if you want more exposure. This is a marketing website. Your target audience are the possible users of your app.
Due by April 18, 2024•1/1 issues closedhttps://capstone.cse.sc.edu/milestone/quality-assurance/ Each team will get a copy of another team's project and do extensive testing of it. You will be added to the other team's github project as a read-only member which will let you create new Issues on their repo. Add all the bugs you find on the project as github issues. The other team will label them.
Due by April 14, 2024https://capstone.cse.sc.edu/milestone/rc1/ As with all Releases, you will set up a set of Issues in your GitHub which list all the features you will implement by the deadline. Associate these Issues with the RC1 Milestone. We will use these features for grading. This release has implemented all the features of your app and has no bugs. At least, no bugs that have been detected by your careful testing. Basically, you believe that this release is the final one: no more coding is required. You might, or might not, be proven correct by your customers. We call it a feature freeze, because no more features will be added after this, not even small ones.
Due by March 31, 2024•12/12 issues closedhttps://capstone.cse.sc.edu/milestone/testing/ For this milestone you will implement and run both unit and behavioral tests. You will likely use third-party libraries and tools for creating and running your unit tests. Typically, the official documentation for your platform will have a section on "Testing" which tells you how they recommend you do automated tests. You will also devise a method for automating some of this testing and making it part of your workflow. The first part of the milestone requires you to research these testing tools, chose some, learn to use them, and create and add to your repo one simple unit and one behavior test to demonstrate your progress. The second part, due at the end of the semester, requires you to have added multiple tests to your repo. You should add the unit tests as you write the code.
Due by April 22, 2024•4/4 issues closedFor this milestone you will implement and run both unit and behavioral tests. You will likely use third-party libraries and tools for creating and running your unit tests. Typically, the official documentation for your platform will have a section on "Testing" which tells you how they recommend you do automated tests. You will also devise a method for automating some of this testing and making it part of your workflow. The first part of the milestone requires you to research these testing tools, chose some, learn to use them, and create and add to your repo one simple unit and one behavior test to demonstrate your progress. The second part, due at the end of the semester, requires you to have added multiple tests to your repo. You should add the unit tests as you write the code.
Due by January 28, 2024•5/5 issues closedhttps://capstone.cse.sc.edu/milestone/beta/ As with all Releases, you will set up a set of Issues in your GitHub which list all the features you will implement by the deadline. Associate these Issues with the Beta Milestone. We will use these features for grading. For a beta release we want all, or almost all, of the main features to be implemented. Your app should be usable: no show-stopper bugs, no major crashes. It is OK if smaller features have not been implemented or bugs remain to be fixed. Cosmetic problems are OK. That is, it should a minimum viable product (MVP). You will give this release to your prospective users or client, and ask them for feedback. You will be happy to implement any new critical features they want, and fix all the bugs they find, before the RC1. To say organized, add as GitHub Issues any feedback you receive from the users or client. That is, for every feature request they make you will add a new enhancement Issue, for every bug they report add one bug issue. You can later decide if you will implement/fix these or not.
Due by February 25, 2024•17/17 issues closedhttps://capstone.cse.sc.edu/milestone/poc-demo/
Due by December 8, 2023https://capstone.cse.sc.edu/milestone/proof-of-concept/
Due by December 8, 2023•10/10 issues closedhttps://capstone.cse.sc.edu/milestone/ethical/
Due by November 5, 2023•1/1 issues closedhttps://capstone.cse.sc.edu/milestone/source-control/
Due by October 29, 2023•1/1 issues closedhttps://capstone.cse.sc.edu/milestone/architecture/
Due by October 22, 2023•1/1 issues closedhttps://capstone.cse.sc.edu/milestone/research/
Due by October 15, 2023https://capstone.cse.sc.edu/milestone/requirements/
Due by October 15, 2023•3/3 issues closedhttps://capstone.cse.sc.edu/milestone/design/
Due by October 1, 2023•1/1 issues closedhttps://capstone.cse.sc.edu/milestone/personas/
Due by September 17, 2023•1/1 issues closedhttps://capstone.cse.sc.edu/milestone/form-teams/
Due by September 10, 2023•6/6 issues closed