The world’s Largest Sharp Brain Virtual Experts Marketplace Just a click Away
Levels Tought:
Elementary,Middle School,High School,College,University,PHD
| Teaching Since: | Apr 2017 |
| Last Sign in: | 103 Weeks Ago, 3 Days Ago |
| Questions Answered: | 4870 |
| Tutorials Posted: | 4863 |
MBA IT, Mater in Science and Technology
Devry
Jul-1996 - Jul-2000
Professor
Devry University
Mar-2010 - Oct-2016
Assignment Instructions
Assignment 2—Class and State Diagram
In this assignment you will create a class diagram for all of the classes you identified in Assignment 1 and a state diagram for two of your classes.
Directions
1. Create a UML class diagram with attributes and associations using your CASE tool. Add your name and course number directly on your diagram.
1.1 Use the classes you identified from Assignment 1 and create a UML class diagram that includes all of your classes. Add attributes to each class and relationships between classes. Attributes are properties of classes and indicate the type of data expected like text, numbers, etc.. For example, a name attribute would be text type data. Relationships establish some linkage between classes and can include associations, generalization, aggregation, and composition . Associations are the most common relationships.
1.2 Include at least 10 named relationships with multiplicity constraints on associations to other classes. Names and multiplicity constraints are required on all associations. The shape of the line used indicates the type of relationship for generalization, aggregation, and composition relationships so you do not need names here. Association names are often verb phrases like “enrolls in” from “A Student enrolls in a Seminar”.
1.3 Add multiplicity constraints to each end of a relationship between classes. UML multiplicity constraints include the pairs 1..1, 1..*, *..*, 0..1, as well as others.
1.4 Add your class diagram to Section 4.1 of your Analysis Specification. Make certain that you continue from your Assignment 1 submission. Each week we will add to the Analysis Specification document until we finally complete it. So just take your previous assignment and add to it.
1.5 Complete Section 4 of the Analysis Specification with a brief introduction to the contents of the section. You can now include this since you have completed your class diagram.
1.6 Make any necessary adjustments to Section 4.2 that you completed in Assignment 1 and discuss your changes in Section 4.2. Section 4.2 should agree with and support Section 4.1.
1.7 Complete Section 4.3 of the Analysis Specification with a discussion of your class diagram.
2. Choose two of the significant classes from your UML class diagram above and create a UML state diagram for each with your CASE tool. Add your name and course number directly on your diagram. Do not use a class that is insignificant for this application like Supply, etc. Do not use Student.
2.1 Add your UML state diagrams along with a discussion to Sections 5.1 and 5.2 of your Analysis Specification.
2.2 Complete Section 5 of your Analysis Specification with an introduction the section contents.
Submission Instructions
1. Submit your updated Analysis Specification as a Word file.
2. When you submit your Word file, use your name as part of the file name, e.g., ENTD321Assignment2_FirstNameLastName. Also make certain that your name and course number is at the top of your document.
Your assignment will be graded with the following rubric:
|
Rubric for Assignments |
Points |
|
Content & Development 50% |
50/50 |
|
Organization 20% |
20/20 |
|
Format 10% |
10/10 |
|
Grammar, Punctuation, & Spelling 15% |
15/15 |
|
Readability & Style 5% |
5/5 |
|
Timeliness (late deduction 10 points) Optional |
|
|
Total |
100/100 |
Quick Resources
Use the following for examples and guidelines for class and state diagrams but make certain that you put names on your associations.
1. See Ambler, Scott (n.d.). UML2 Class Diagrams: An Agile Introduction. Retrieved from http://www.agilemodeling.com/artifacts/classDiagram.htm, This provides examples of a class diagrams.
2. See Ambler, Scott (n.d.). UML2 Class Diagramming Guidelines. Retrieved from http://agilemodeling.com/style/classDiagram.htm. This style guide includes the guidelines for drawing and naming for class diagrams including general guidelines, class style guidelines, interfaces, relationships, inheritance, aggregation and composition.
3. See step by step instructions for drawing class diagram from the VP User Guide article "Drawing class diagrams" at https://www.visual-paradigm.com/support/documents/vpuserguide/94/2576/7190_drawingclass.html
4. Ambler, Scott (n.d.). UML2 State Machine Diagrams: An Agile Introduction. Retrieved from http://www.agilemodeling.com/artifacts/stateMachineDiagram.htm
5. Ambler, Scott (n.d.). UML2 State Machine Diagramming Guidelines. Retrieved from http://agilemodeling.com/style/stateChartDiagram.htm. This style guide provides guidelines for general issues, state, substates, transitions and actions, and guards.2
6. See step by step guidelines for creating state machine diagrams with Visual Paradigm in the VP User Guide article "Creating State machine Diagrams" at https://www.visual-paradigm.com/support/documents/vpuserguide/94/2579/6714_creatingstat.html
7. See the video for drawing state diagrams with VP at Visual Paradigm. (2011 November 4). 5 Steps to Draw a State Machine Diagram. Retrieved from https://www.youtube.com/watch?v=UzUUZRK_Q6Y