Running head: CREATING A DOMAIN MODEL CLASS DIAGRAM

Assignment 3: Creating a Domain Model Class Diagram

(Student’s Name)

(Professor Name)

(Course)

(Date)
CREATING A DOMAIN MODEL CLASS DIAGRAM 2

Introduction

Many of the current approaches to system development utilize the term class rather than

data entity and as well utilize the concepts and notations based on UML so as to model the things

in the problem domain. The concepts are derived from the object oriented approach to systems

where a class is a category or classification that is utilized to describe a collection of objects. The

classes that describe things in the problem domain are referred to as domain classes (Prieto-Díaz,

2010). The RMO CSMS involves various domain classes and various complex association as

well as specialization/generalization relationships.

For the case of any information system, the domain model class diagram evolves as the

project proceeds. There is eventually only one domain model class diagram; this is unlike use

case diagrams where many diagrams are created. Domain model class diagram is not just

developed for presentation which is the case of use case diagrams, the process of developing as

well as refining the domain model class diagram allows the system analyst to learn and explore

the problem domain. Moreover, the information that is depicted in the domain model class

diagram is rich for specific meaning and very detailed (Prieto-Díaz, 2010).

The Ridgeline Mountain Outfitters domain model class diagram consists of variations of

customer, product, and promotion, order, and order item. Most of the domain classes in the RMO

Consolidated Sales and Marketing Subsystem (CSMS) are derived from the list of nouns that are

consisted in the system. Since the domain model for RMO is complex, a system analyst may start

by focusing on one of the subsystem for example the Marketing Subsystem at a given time in

order to reduce the complexity. Ultimately, all the subsystems may be combined together into

one domain model (sdiwc.us, 2014).

 CREATING A DOMAIN MODEL CLASS DIAGRAM 3

RMO Customer Marketing Subsystem domain model class diagram

Promotion PromoOffering AccessoryPackage

Season RegularPrice Category

Year PromoPrice Description

0….* 0…*
Description

StartDate

EndDate

0…* 1…*
ProductComment ProductItem

Date Gender

Rating Description
0….* 1 1
Comment Supplier
1
Manufacturer
Picture

InventoryItem

Size 0…..*
Color

Options

QualityOnHand

AverageCost
CREATING A DOMAIN MODEL CLASS DIAGRAM 4

Overview of the Diagram

The Marketing Subsystem mainly involves products, accessories, and promotions. This is

a good starting point but of course there are additional domain classes. Moreover, association

relationships are equally as important as the classes, and they must be identified. Each customer

may be associated with one or more products. It is worth noting that products can be marketed at

different platforms which include online marketing, in-store marketing, and telephone marketing

(sdiwc.us, 2014). Therefore, the scope of the Marketing Subsystem includes in-store, telephone,

as well as online marketing processes. A customer can be associated with an online marketing

for the case of online products.

Each product is associated with one promotion, one product comment and an accessory

package such that the subclasses inherit the association the same way they inherit the attribute of

inventory. An individual marketing strategy is associated with one or more product items. In the

case of online marketing, it is associated with one or more product items. The online marketing

involves various product items with specific promotion offering. When a promotion transaction

is created, it is associated with the product (sdiwc.us, 2014)

An Analysis of the Different Classes in the Diagram

A product can have one or more product items, but what is each item? An association

between each item and an inventory item answers the question. Each product item is for a

specific inventory item, which means that a specific size and color of the item, such as a trouser

or jacket. An inventory item has attributes for the quantity at hand of that color and size. Since

there are various sizes and colors, each with its own quantity, each inventory item is therefore

associated with a product item that describes the item in general. This may include the attributes

of gender, supplier, picture, manufacturer, and description. Each product item is associated with
CREATING A DOMAIN MODEL CLASS DIAGRAM 5

many inventory items and each inventory item is associated with many promotion offerings (Lu,

R., & Jin, Z, 2012).

A product item may be part of various promotions, and may therefore include many

product items, which makes a many-to-many association. This allows the addition of an

association class so as to store information about the prices of each item in each specific

promotion. A product item may have many accessories and an accessory can therefore apply to

many product items. In this case there is no specifically defined association class for the many-

to-many association. It is worth noting that this association may also be modeled as a recursive

(Unary) association. To conclude, each product item may have lots of customer comments that

can be reviewed during marketing analyses (Lu, R., & Jin, Z, 2012).
CREATING A DOMAIN MODEL CLASS DIAGRAM 6

References
(sdiwc.us) 2014 Domain Modeling: Retrieved From:

http://sdiwc.us/eyas/wp-content/uploads/2013/09/BookChapter_4.pdf

Prieto-Díaz, R., & Arango, G. (2010). Domain analysis and software systems modeling. Los

Alamitos, Calif: IEEE Computer Society Press.

Lu, R., & Jin, Z. (2012). Domain modeling-based software engineering: A formal approach.

Boston, MA: Kluwer Academic.