First Thesis II document draft
- Due Apr 3, 2020 by 3:30pm
- Points 20
- Submitting a file upload
- File Types pdf, doc, and docx
Update your Thesis I document to conform to the sections required in the Thesis II Document. Roll in the changes I requested to your Thesis I document at the end of last semester.
You should submit a PDF or Word document. You will perform a peer edit with a partner the day this is due, so you may find it helpful to bring a printed copy of your document to class.
Rubric
Find RubricKeep in mind that 12 students have already been assessed using this rubric. Changing it will affect their evaluations.
| Criteria | Ratings | ||||
|---|---|---|---|---|---|
|
Includes a title page
|
|
||||
|
Includes a table of contents at the beginning.
|
|
||||
|
Contains an abstract on its own page at the beginning of the document (after the title page and table of contents)
|
|
||||
|
Contains an introduction and background
|
|
||||
|
The abstract and introduction give the reader a feel for what the project is about and why it is interesting.
|
|
||||
|
Related work is discussed; the connection between the project and related work is clear and how the project compares.
|
|
||||
|
Contains information about client requirements, features, and assumptions
|
|
||||
|
The requirements and logical components are described without referencing specific technologies or design decisions.
|
|
||||
|
Includes user interface design graphics (wireframes, mockups, etc.) and a discussion of them
|
|
||||
|
Discusses the system architecture and component design of the project.
|
|
||||
|
Discusses the data design of the project
|
|
||||
|
Discusses system analysis and testing
|
|
||||
|
Testing: You sufficiently describe how you are ensuring the project works as expected.
|
|
||||
|
There are screenshots of the implemented program.
|
|
||||
|
Includes a conclusion
|
|
||||
|
Conclusions: the conclusions summarize the major points of the project and indicate future directions.
|
|
||||
|
Important design decisions are discussed and make it clear what choices were available and why one in particular was settled on.
|
|
||||
|
Overall, the writing is grammatically correct and free of spelling mistakes. Sentences are easy to parse and not overly complex and/or run-ons.
|
|
||||
|
The implementation details are discussed in sufficient detail that another programmer could replicate the project.
|
|
||||
|
There is no unnecessary jargon. Terms, products, and acronyms are all defined the first time they are used in the document.
|
|
||||
|
|
|||||
