18 Mar In this assignment, you will develop a full UML suite.
About this Assignment
In this course, we’ve used the Unified Modeling Language (UML) for the requirements modeling phase of a project. UML is a standard language used to both visualize elements within a system and provide a picture of the software’s design.
In this assignment, you will develop a full UML suite. You will be designing an in-home smart thermostat, creating a UML case diagram, a sequence diagram, and a deployment diagram for this system.
Upon completion of this project, you will be able to:
Design a UML case diagram
Create a UML sequence diagram
Develop a UML deployment diagram for this system
Scenario
You are the IT lead in a start-up company that has started marketing smart thermostats for residential heating and cooling systems. Leadership has tasked you with designing a system that consumers can install in their homes. These systems should be easy to install and user-friendly.
Before you can start writing any code for these devices, you will need to come up with a design that both the business and your IT staff can understand. In order to keep the project organized, each flowchart will be developed separately.
Here is what you will need to deliver for this assignment:
A UML case diagram for an in-home smart thermostat system
A UML sequence diagram for the thermostat system
A UML deployment diagram for the thermostat system
A written report that defines each type of diagram, explains their importance and use, and justifies the design decisions in your diagrams
Please use an online program such as Microsoft Visio which you need a Microsoft 365 subscription for, Balsamiq, LucidChart or diagrams.net which are free to create your UML diagrams. You should write your report in Microsoft Word or another word processor.
Formatting & Sources
This assignment covers material presented in the chapters:
UML Models: Design & Examples
Practical Application for Software Engineering: UML Case Diagram
Practical Application for Software Engineering: UML Deployment Diagram
You may refer to the course material for supporting evidence. You may also 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:
What is APA Format? Style & Definition
How To Format APA Citations
Grading Rubric
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
Definitions, Explanation & Justification (x1) Definitions are incomplete or missing; Lacking description of each diagram and its importance; No justification for design decisions Diagrams definitions are incomplete; explanation of diagram importance and use exists but is incomplete; design decisions explained, but not supported with evidence Definitions are correct; explanation and use of diagrams is correct; justification of design decisions is logical but not fully supported with evidence Definitions are correct; explanation and use of diagrams is correct; justification of design decisions is logical and fully supported with evidence 10
Case Diagram (x1) Diagram is missing Diagram is too simple, is missing critical components, and/or is too difficult to follow Diagram shows components and is relatively easy to follow, but does not clearly identify all relationships and interactions All components present (actors, boundaries, scenarios, and interactions); diagram is easy to follow 10
Sequence Diagram (x1) Diagram is missing Diagram is too simple, is missing critical components, and/or is too difficult to follow Diagram shows components and is relatively easy to follow, but does not clearly identify all relationships and interactions All components present (classes, interactions and executions, controls and constraints); diagram is easy to follow 10
Deployment Diagram (x1) Diagram is missing Diagram is too simple, is missing critical components, and/or is too difficult to follow Diagram shows components and is relatively easy to follow, but does not clearly identify all relationships and interactions All components present (nodes and stereotypes, artifacts and devices, communication); diagram is easy to follow 10
