Class-Based Component Design: Principles & Process
Practical Application for Software Engineering: Component-Level Design
Practical Application for Software Engineering: User Interface Design
You may also refer to the course material for supporting evidence. You may use primary and secondary sources as needed and cite them using APA format.
If you use any Study.com lessons as sources, cite them in APA format, including lesson title and instructor’s name.
Primary sources are first-hand accounts such as interviews, advertisements, speeches, company documents, statements, and press releases published by
the company in question.
Secondary sources come from peer-reviewed scholarly journals, such as the Journal of Computer and System Sciences. You may use sources like JSTOR,
Google Scholar, and Scopus to find articles from these journals. Secondary sources may also come from reputable websites with .gov, .edu, or .org in the
domain. (Wikipedia is not a reputable source, though the sources listed in Wikipedia articles may be acceptable.)
If you’re unsure about how to use APA format to cite your sources, please see the following lessons:
Your project will be graded based on the following rubric:
Category Unacceptable (0-2) Needs Improvement (3-6) Good (7-8) Excellent (9-10) Total Possible Points
Explanations & Justifications (x1) Explanations are incomplete or missing; no sources used to justify the decision Explanations are incomplete; justifications
are semi-logical, but not supported with evidence Explanations are provided and correct; justifications are logical and but not fully supported with evidence
Explanation and use of diagrams is correct; justification of decisions is logical and fully supported with evidence 10
System Diagrams (x1) Diagrams are incomplete, sections missing Components present but missing descriiptions and logical flow Diagrams complete but
missing notations or difficult to read or follow Diagrams are fully complete with notations, logical flow, and are easy to follow 10
User Interface (x1) Interface is not intuitive; missing labels or indication of the purpose of functions Interface is complete but missing more than two of the
interface design process, or design requires unnecessary amount of clicks/interactions) Interface is complete, but missing one or two steps in the process
Interface is complete and all steps outlined (map the flow, minimal clicks, exception handling, and screen design) 10
Testing Plan (x1) Testing plan incomplete; missing key definitions and methods of testing Plan covers only one type of software testing; examples missing
Multiple methods of testing provided but lacking in definition and completion Full analysis of software testing, including dynamic and static testing;
examples provided and analyzed 10