PART A1. Explain class stereotypes; include the boundary class, entity class, and control class. BOUNDARY CLASS DEFINITION A "boundary class" is a class that lies at the periphery of a system, but within it. It interacts with actors external to the system and with objects of all three types of analysis classes within the system. Boundary classes are used to model the interaction between a system and its surrounding environment, i.e. its actors. The following aspects of interaction are captured in boundary classes: • coordinating the actor's behavior with the "internals" of the system; • receive input from the actor to the system, for example information or requests; • provide output from the system to the actor, for example, store information or derived results. Boundary classes can then be used to capture requirements on a user interface. Building an object model of the user interface is normally very useful, since many user interfaces created today are object-oriented, and the trend is towards even more object-orientation for its advantages in terms of natural and efficient use. While many UI design decisions are best made during prototyping and rapid development of the UI itself, thinking about the structure and usability requirements of the UI is natural to do in terms of an object model. It can be shown as a regular class rectangle with the "border" stereotype or as the following special icon: ENTITY CLASS DEFINITION As described in the previous section, entity classes are combined key/value classes managed by entity associations. In this example, the Part, Supplier, and Shipment classes are entity classes. These classes contain fields that are a union... half of the sheet...) must have on the system and/or the effect the system must have on the external surroundings. o The Requirements Analyst acquires and validates the environmental requirements in the Context Analysis and in the Rest of the Scenario Analysis, conducted iteratively with the Functional Analysis.PART BA. Develop a UML use case diagram for the WayPay online business and payment system (WOBPS) described in the previous narrative.B. Draw a UML class diagram for Online Business and Payment System (WOBPS). The class diagram should represent all the classes, their attributes, operations, relationships between classes, multiplicity specifications, and other model elements you deem appropriate.C. Draw an activity diagram for a WOBPS member to register a new product and purchase a productREGISTER A NEW PRODUCTBUY A PRODUCT