- Username
- Password
forgot?

iRubric: Alice Project 2 - Software Development Cycle rubric

edit print share Copy to my rubrics Bookmark test run assess... delete Do more...
Alice Project 2 - Software Development Cycle Alice Project 2 - Software Development Cycle Students will create a new Alice World based on the Software Development Cycle, top-down design, and bottom-up development. They will develop their design before they will be allowed to start coding. They will have to turn in all design changes discovered as a result of the debugging stage of the cycle. A student can receive up-to the point amount in each category. Rubric Code: X2348BW By subalzero Ready to use Public Rubric Subject: Computers Type: Project Grade Levels: 9-12

Software Cycle
	Poor 5 pts	Fair 10 pts	Good 15 pts	Excellent 20 pts
Design	Poor Design specifications 25% or less complete.	Fair Design specifications 26% - 50% complete.	Good Design specifications 51% - 75% complete.	Excellent Design document contains specifications for starting scene, the initial position of objects, placement and orientation of cameras. It contains descriptions of the necessary objects, the methods associated with each object and the initial state of the world.
Implementation	Poor Implementation coding 25% or less complete.	Fair Implementation coding 26% - 50% complete.	Good Implementation coding 51% - 75% complete.	Excellent Alice world contains 10 methods with at least 5 lines of code. The main method (World.myfirst.method) contains only the calls to the 10 methods. All objects from the design document are added.
Test	Poor Testing 25% or less complete.	Fair Testing 26% - 50% complete.	Good Testing 51% - 75% complete.	Excellent All 10 methods are unit tested. Integration testing performed to make sure single methods work with each other.
Debug	Poor Debuggin 25% or less complete.	Fair Debugging 26% - 50% complete.	Good Debugging 51% - 75% complete.	Excellent Corrected mistakes found in the testing phase. Re-submitted design document with change in design as a result of the debugging phase. Made changes to code in implementation phase. Retested new changes.
Documentation	Poor Documentation 25% or less complete.	Fair Documentation 26% - 50% complete.	Good Documentation 51% - 75% complete.	Excellent All methods contain comments describing the author, the date, and what the method is used for. Methods contain notes that appear when the program is running. An instruction manual that describes what the program does and how the software works.