Creating a Domain Model Class Diagram
In this assignment, the RMO CSMS marketing subsystem diagram is proposed as a solution based on the complete available diagram available for RMO CSMS systems, concepts of domain class modeling, as well as assumptions on potential marketing approach executed by company marketing executives. It is a narrative that describes the diagram and provides an analysis of different classes used in diagram. Marketing subsystem is a problem domain defined as specific business area which appears within the scope of new system. Precisely defining a design pattern helps to avoid complexities with defining an appropriate problem domain (Kim & El Khawand, 2007).
Problem domain is defined by requirements encapsulated in data entities or domain classes. It is also a step from a more general system design to some special elements requiring extra attention for analysts (Kiyoki, 2006). Things in problem domain could be identified either by brainstorming or by noun approach (Satzinger, Jackson & Burd, 2015). Noun approach was used to develop the diagram presented in Figure 1 and was followed by the idea of identifying all nouns through system description and determining whether nouns are equal to a definition of domain class, attribute of the class or it is out of the scope of the given project (Satzinger et al., 2015). Some of the nuns were initially taken from the original diagram since they are already incorporated into the proposal on other subsystems and thus require having a similar design to build a cross-system entity relationship.The problem domain assumes that product items will be marketed to potential customers through a separate user interface where products available for sale will be rated and commented by both customers and promotion partners.
Promotion partners are contracted employees which have an agreement with the company and are assigned to particular product categories. They are assigned to specific product only, and thus manage the promotions via allocated product group to their responsibilities. Customers are contacted through account verification in order to build on the loyalty and offer targeted products which are relevant to the customer profiles indicated in their accounts. In this way, problem domain attempts to make sure that customers are differentiated and will not be contacted purely by the principle of mass promotion.The domain model class diagram consists of nine classes, each having from two to five attributes. Attributes are marked with dots and circles, representing whether an attribute could or could not have a null value. Null values refer to missing or unknown values, since it is hypothesized that certain product categories could be either changes or lack description at the initial step of their offerings.
ProductItem is the main domain class which is a central element used to construct additional elements and aligns existing ones. It has five attributes; all replicated from the general model and include gender, description, supplier name, manufacturer name and picture of the item. It has one-to-many relationship with Promotion domain class with the description attribute identifying the relationship of one product …
