“Things” in the Problem Domain

The problem domain are the parts that eventually must be handles, administered or controlled by the information system will be built. Things on the problem domain refers to the objects that would have to be recorded, dioleh, stored and distributed to those interested parties to the information contained in these things. Things can be anything that can be seen or felt and has unique characteristics, which differentiate between the one thing with another. These kinds of things are as follows:

1. Tangible things, is something that is real and can be seen plastered forms are quite different.
2. The Roles played, the roles that are held by a person as a result of her position or functions work he does in an information system.
3. Organizational units, the parts or divisions or units that exist in an organization.
4. Devices, can be in the form of equipment involved, which supports an information system.
5. Sites/locations, can be either a location or place that is involved in the implementation of the information systems function.
6. Incidents, events, or financial transactions, is a tapestry that is either intentional or not, should be handle by information systems that were to be built.

These things can be identified from the business processes supported by the company's information systems. But not all things are found in the business processes will be elected that will be on things-handle by the system. Here are the procedures that must be observed:

1. Use the event table as a reference in deciding things. Identification of any verb that exists for each of his events.
2. Use of reference of information-related information system is running, the procedure that exists, as well as forms or reports that are used, to enrich the list of things that exist.
3. Check back list of things that have been generated by answering the question, "are these things need to be handle by a system?", if it is, "important information on what can be given by such things, is associated with the execution of business process?". In the end, things that remains consists only of things that actually have an important role in the business process, which has important information that need to be handle by the system.

In any event, things involved in them interact with one another. Therefore, things that need to be linked with the other things associated with the use of a relationship. Relationship is a relationship that occurs naturally in between things in regard the implementation of an event, such as an order requested by a customer and an employee working on a Department. The kinds of relationships that exist are as follows:

1. Binary relationship, a relationship between two different kinds of things, such as a customer with an order.
2. Unary (recursive) relationship is a relationship between one thing and another thing of the same kind, e.g. one person getting married with one other person.
3. Ternary relationship, a relationship between three (3) different types of things.
4. N-ary relationship, a relationship between n different types of things.

The relationships between things is also known for the term cardinality and multiplicity. Cardinality is the number of events (minimum and maximum likelihood) that may occur in the relationship between things, for example a customer can order a lot of orders and an employee works only in one Department. Meanwhile, the multiplicity is the term used in the object-oriented approach, which has a meaning like cardinality.

Cardinality Notation

Share :

Tweet

More

Related Post