Class Stereotypes: Entity Class, Entity Class And Control Class?

PART A
QUESTION 1
Explain class stereotypes; include the boundary class, entity class and control class.
Stereotypes is a class that defines how an existing Meta Class (or other stereotype) may be extended, and enables the use of platform or domain specific terminology or notation in addition to the ones used for the extended Meta class. Certain stereotypes are predefined in the UML, other may be user defined.
Analysis class stereotypes differentiate the roles objects can play:
1. Boundary objects model interaction between the system and actors (and other systems)
2. Entity objects represent information and behaviour in the application domain
3. Control objects co-ordinate and control other objects
Boundary Class
A boundary class is a class that used to show the interaction between system and object. The interaction includes transforming and translating activity and noted changes in the system presentation such as interface. The boundary class is a class that is the boundary of the system and other system or user (which is actor in the use case diagram). The followings are the feature of the boundary class:
1. This class is more easy to be changed that the entity and control class.
2. The attribute of this class and screen layout are defined at the basic design.
3. In a class diagram, there are cases that the stereotype <> is added.
4. In a class diagram, there are cases that is shown by the following icon:

Entity Class
An entity class is a class used to show the information and associated behaviour that must be stored. Entity objects are used to hold and update information about some phenomenon, such as an event, a person, or some real-life object. They are usually persistent, having attributes and relationships ne...

... middle of paper ...

...ctors, and acceptance criteria for the working system. The prototyping is the last stage that must we follow before we implement the real system. From that, we can identify the strong and weaknesses of the system, so it will give the chance for us to improve the system before we implement the real system.

PART B
a) Develop a UML Use Case Diagram for the We Pay Online Business and Payment System (WOBPS) described in the above narrative.

b) Draw a UML class diagram for the Online Business and Payment System (WOBPS). The class diagram should represent all of the classes, their attribute, operations, relationships between the classes, multiplicity specifications, and other model elements that you find appropriate.

c) Draw an activity diagram for a member of WOBPS to register a new product and buy a product.
Register a new product

Buy product