ENTD321 ​Assignment 2—Class and State Diagrams

timer Asked: Jun 12th, 2018
account_balance_wallet $10

Question description

Assignment 2—Class and State Diagrams


The purpose of this assignment is to continue building our ITOT case study models by using the classes and their properties from Assignment 1 and creating a class diagram and Class and Relationship Analysis table for the relationships among classes. In addition, we will build a state diagram for the ShopppingCart class.

Assignment Instructions

In this assignment you will create a class diagram and the Class and Relationship Analysis table for all of the classes you identified in Assignment 1 and a state diagram for your ShoppingCart class. Make certain that you include all of the classes and any additional classes or corrections to your Assignment 1.

For the Analysis Specification you will add the following completed sections:

Sections 4, 4.1, 4.2 (adjustments if necessary), 4.3, 5, 5.1, 5.2


1. Read and review the Quick Resources at the end of this Assignment.

2. Create a UML class diagram with attributes, associations, multiplicity constraints, and operations using your CASE tool. Add your name and course number directly on your diagram.

2.1 Section 4.1. Use the classes you identified from Assignment 1 and create a UML class diagram that includes all of your classes. Place your class diagram in Section 4.1. 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. See the example class

diagram http://www.uml-diagrams.org/examples/online-shopping-domain-uml-diagram-example.html for an example of a ShoppingCart class diagram similar to our model. As you add a class using the CASE tool, if you right click on the class and choose the option to Add attributes with getter and setter methods. Your CASE tool will automatically add them as methods. This saves considerable time and effort.

2.2 Section 4.1. 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 “purchases” from “A Customer purchases a ScheduledCourse”. To determine the associations, you can also use the same technique as the noun analysis, but do verb analysis instead. To help you discover the associations and multiplicity constraints complete the Class and Relationship Analysis table below and add it to Section 4.1 with your class diagram.

Identify the relationships among the classes. Associations are bidirectional and so we must consider them in both directions with multiplicity constraints as well. Using a table for the initial analysis will make it easier to create a class diagram. For each class ask the question "What other classes is the class related to?" or "What is the relationship between these two classes?" Once you identify the classes, then for each class pair ask "What is the relationship?" Multiplicity constraints are needed on both ends of the association and may be zero or one (0..1), one and only (1), zero or more (0..*), or many (*) ,etc. As you can see below there are two sentences with the multiplicity constraints describing the association in both directions. In this example the two classes are Instructor and Course. The relationship is "teaches". On our diagrams we usually only show the relationship name in one direction and mentally revers the verb phrase in the other direction. See Figures 3.12 and 3.15 in your textbook for an example of a class diagram with named associations and multiplicity constraints.

2.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.

2.4 Section 4.1. Add your class diagram and the Class and Relationship Analysis table 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 this assignment to it.

2.5 Section 4. 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.

2.6 Sections 4.2 and 4.3. Make any necessary adjustments to Section 4.2 that you completed in Assignment 1 and discuss your changes in Section 4.2 which should agree with and support Section 4.1.

2.7 Section 4.3. Complete Section 4.3 of the Analysis Specification with a discussion of your class diagram.

3. Create a UML state diagram for the ShoppingCart class with your CASE tool. Add your name and course number directly on your diagram. Make certain that you name the transitions and add guards as necessary.

3.1 Sections 5.1 and 5.2. Add your UML state diagram along with a discussion to Sections 5.1 and 5.2 of your Analysis Specification. See the article, ENTD321 Lesson 2 State How to Create a State Diagram.pdf, below on creating a state transition diagram before you start your diagram.

3.2 Section 5. 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.

Please use APA formatting and in text cititation

Please No Plagiarism

Tutor Answer

School: University of Maryland




I.T Online Training Project



The IT online training is one of the current trends in the I.T field. It is aimed at providing
scheduled and new self-spaced online courses to the customers. This specific assignment is
aimed at modelling the specified requirements by the use of the noun analyses technique in order
to identify the specific domain classes, operations, attributes and requirements.
By the use of the Analysis Specification Template, this assignment will endeavor to
develop an online service both scheduled and that which is self-spaced in reference to the diverse
technical architecture.
In accordance with the document, the IT online training has to endeavor to come up with
an online platform where training can take place together with other self-spaced courses. The
first training activity will be based on the web. However, the architecture must include a
different option of front-end implementation. They include the applications, SaaS among others.
The IT platform is aimed at providing the IT courses to the already existing customers and the
potential ones. Moreover, this specific application must be able to cover other areas such as the
customer management, system access, and course management among others.
Purchase Courses
REQ 1.1: That the customers should be in a position to purchase the available

IT courses

through the online application shopping cart.
REQ 1.2: the online shopping cart should be easy to access such that the customers may be able
to add courses.



REQ 1.3: in the same easier manner, the online customers must be in a position to remove the
unwanted courses from their list with ease.
REQ 1.4: The application should be easy such that the customers can be in a position to cancel
an order.
REQ 1.5: The IT app should be purchasable even by the credit card.
REQ 1.6: The created application system should be able to create and disseminate certificates to
the customers who have successfully completed their courses.
REQ 2.1: the purchasing customers must be in a position to create their own customer accounts
with ease.
REQ 2.2: The IT online application must be in a position to store important customer data and in
an encrypted form.
REQ 2.3 The online application should be able to match the customers’ private information with
the right identifications like the passcodes.
REQ 2.4; the server must only give access to customer information to the ...

flag Report DMCA

Excellent job

Similar Questions
Hot Questions
Related Tags

Brown University

1271 Tutors

California Institute of Technology

2131 Tutors

Carnegie Mellon University

982 Tutors

Columbia University

1256 Tutors

Dartmouth University

2113 Tutors

Emory University

2279 Tutors

Harvard University

599 Tutors

Massachusetts Institute of Technology

2319 Tutors

New York University

1645 Tutors

Notre Dam University

1911 Tutors

Oklahoma University

2122 Tutors

Pennsylvania State University

932 Tutors

Princeton University

1211 Tutors

Stanford University

983 Tutors

University of California

1282 Tutors

Oxford University

123 Tutors

Yale University

2325 Tutors