Creating a Domain Model Class Diagram

Ridgeline Mountain Outfitters (RMO) works on developing an information system for automating the work of different departments and integrating organizational data. There are several subsystems within the company – reporting, sales, customer account, and marketing. Every subsystem relates to a specific organizational unit and has specific use cases. The purpose of this paper is to analyze a domain class model diagram for RMO CSMS marketing subsystem.

RMO CSMS marketing subsystem includes two types of actors – merchandising and marketing (Satzinger, Jackson & Burd, 2015). The representatives of these departments are involved in the following marketing use cases: adding and updating product information, adding and updating promo information, adding and updating accessory packages, and adding/updating business partner links (Satzinger, Jackson & Burd, 2015).

For developing the information system for RMO, object-oriented approach is chosen because the business environment is dynamic and it will be more efficient to develop the new system step by step instead of using a traditional “waterfall” approach to development. In the case of object-oriented approach, RMO can develop parts of the system early, test the effectiveness of the system for different organizational units and make changes during the next iterations (Halpin, 2009). Hence, object-oriented approach is optimal for developing RMO CSMS.

In object-oriented approach, one of the most common ways to modeling system requirements and planning system development is using domain model class diagrams. The domain model in general is a conceptual representation of the domain associated with the new information system (Rosenberg, 2007). A domain model is typically developed to incorporate both system data and typical user behaviors (Rosenberg, 2007). A domain model class diagram represents different business activities and use cases identified within the system (Bowen & Hinchey, 2012). The domain class diagram for RMO CSMS marketing subsystem is shown on Fig. 1. This diagram reflects the use cases associated with the marketing subsystem, the relevant data and transactions.

Both merchandising and marketing RMO users can work with product information in RMO CSMS marketing subsystem. The relevant classes in the domain model class diagram are ProductItem and ProductComment. ProductItem class contains basic information about the product, such as product description, product photo, supplier and manufacturer information. Every ProductItem can have associated product comments described by ProductComment class. Product comments have the following characteristics: the comment itself, comment date and comment rating.

Marketing users also work with promotions that are represented by Promotion and PromoOffering classes of the domain model class diagram. The primary class is Promotion that holds records pertaining to different promotions and their characteristics such as promotion description, date, season, year, and date range of the promotion (start and end dates). Promotions might relate to different products, and one product might be listed in different promotions. This relationship is shown by the class PromoOffering that lists regular product price and promo price of the associated product item listed in a particular promotion. Merchandising users can add or update accessory packages. This use case is represented by the class AccessoryPackage with such characteristics as category and description. Every product item might have zero, one or multiple accessory packages.

Finally, marketing users can add or update business partner links. Business partners and the information about their credits are represented by the objects PromoPartner and CustPartnerCredit accordingly. The main class in this context is PromoPartner that lists major information about the partner (name, contact person, address, phone) and the description of the business agreement. Partner credits are linked to the relationship between partners and their customers. One customer might be associated with many partners, and one partner, naturally, might be linked with many customers. The relationship between the business partner and the customer is represented by the class CustPartnerCredit which lists the amount of RMO credits and partner credits. The Customer class which is included into the diagram is not directly mentioned in the use cases for the marketing subsystem but it is linked to the product classes and to the business partner subsystem, so it is indirectly involved into marketing subsystem.

Figure 1. RMO CSMS marketing subsystem – domain model class diagram

 

References

Bowen, J.P. & Hinchey, M. (2012). High-Integrity System Specification and Design. Springer Science & Business Media.

Halpin, T. (2009). Innovations in Information Systems Modeling: Methods and Best Practices. IGI Global.

Rosenberg, D. & Stephens, M. (2007). Use Case Driven Object Modeling with UMLTheory and Practice. Apress.

Satzinger, J., Jackson, R. & Burd, S. (2015). Systems Analysis and Design in a Changing World. Cengage Learning.

 

The terms offer and acceptance. (2016, May 17). Retrieved from

[Accessed: March 28, 2024]

"The terms offer and acceptance." freeessays.club, 17 May 2016.

[Accessed: March 28, 2024]

freeessays.club (2016) The terms offer and acceptance [Online].
Available at:

[Accessed: March 28, 2024]

"The terms offer and acceptance." freeessays.club, 17 May 2016

[Accessed: March 28, 2024]

"The terms offer and acceptance." freeessays.club, 17 May 2016

[Accessed: March 28, 2024]

"The terms offer and acceptance." freeessays.club, 17 May 2016

[Accessed: March 28, 2024]

"The terms offer and acceptance." freeessays.club, 17 May 2016

[Accessed: March 28, 2024]
close
Haven't found the right essay?
Get an expert to write you the one you need!
print

Professional writers and researchers

quotes

Sources and citation are provided

clock

3 hour delivery

person