Essay On Boundary Class

PART A

1. Explain class stereotypes; include the boundary class, entity class and control class.

BOUNDARY CLASS

DEFINISION

A "Boundary Class" is a class that lies on the periphery of a system, but within it. It interacts with actors outside the system as well as objects of all three kinds of analysis classes within system.

Boundary classes are used to model the interaction between a system and its surroundings, i.e., its actors. The following aspects of the interaction are captured on boundary classes:

• coordinating the actor's behavior with the "internals" of the system;

• receiving input from the actor to the system, for example is information or requests;

• providing output from the system to the actor, for example is stored information or derived results.

Boundary classes can thus be used to capture the requirements on a user interface. Making an object model of the user interface is normally very worthwhile, since many user interfaces created today are object-oriented, and the trend is towards even more object orientation, because of its benefits with regard to natural and efficient use. Although many of the user-interface design decisions are best made during prototyping and rapid development of the user interface itself, reasoning about the structure and usability requirements on the user interface is natural to do in terms of an object model.

It can be shown as a regular class rectangle with stereotype of "boundary", or as the following special icon:

ENTITY CLASS

DEFINITION

As described in the prior section, entity classes are combined key/value classes that are managed by entity bindings. In this example the Part, Supplier and Shipment classes are entity classes. These classes contain fields that are a union ...

... middle of paper ...

...) is to have on the system, and/o the effect that the system is to have on the external enveloping environment. o The Requirements Analyst captures and validates environmental requirements in Context Analysis and in Rest-of-Scenario Analysis, conducted iteratively with Functional Analysis.

PART B

A. Develop a UML Use Case Diagram for the WayPay 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

REGISTER NEW PRODUCT

BUY A PRODUCT