Explanation of Class Stereotypes

An analysis class can be classified into one of the three stereotypes, which are entity, boundary or control. An entity class is a class that the primary focus is to hold the data. Meanwhile, the boundary class is a class that the objects are used by the actors to communicate with the system. On the other hand, a control class is a class which provides coordinating behavior in the system. (Joey F. George, 2004)

As mentioned, the class of the entity class focus on holding the data. The objects hold most of the data of the application. An entity class does not interactions on its own. Object on the entity classes are persistent which exist beyond the life of a session and sometimes for the life of the system. Note of the special notation for the entity class stereotype is a horizontal line as a tangent on the bottom of a circle.

A boundary class are used by actors to interact with the system, such as forms, dialog boxes, menus, and the other screens. It can serve to establish interaction with another application. Actors are allowed to interact with the system only through boundary classes. It is important to identify responsibilities and not get enmeshed in user interface details and issues regarding the number of boundary classes.

Coordinates the task and captures the main application logic in a use case is about the function of a control class. A control class can act as the controller for the sequencing of events such as transactions, as the enforcer of business rules and policies. Business rules is a statement that defines or constrains some aspect of business and a policy is a guiding principle or procedure. Note the notation for a control class is a circular arrow that points back to its beginning.

2. Compare and ...

... middle of paper ...

...o WOBPS account as service charge.

Besides approving applications, ADMIN also responsible to ban any MEMBER caught doing scamming activities, and then move their data to a scammers list.

a) Develop a UML Use Case Diagram for the WePay 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 attributes , 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.

WePay Online Business and Payment System

Activity Diagram

Works Cited

object oriented system analysis and design