PART AQUESTION 1 Explain class stereotypes; include boundary class, feature class, and control class. Stereotypes are a class that defines how an existing meta-class (or other stereotype) can be extended and allows the use of platform- or domain-specific terminology or notation in addition to those used for the extended Meta class. Some stereotypes are predefined in the UML, others can be defined by the user. Analysis class stereotypes differentiate the roles that objects can play:1. Boundary objects model the interaction between the system and the actors (and other systems)2. Entity objects represent information and behaviors in the application domain3. Control objects coordinate and control other objectsBoundary ClassA boundary class is a class used to show the interaction between the system and the object. The interaction includes transformation and translation activity and noted changes in the presentation of the system, such as the interface. The boundary class is a class that constitutes the boundary of the system and another system or user (who is an actor in the use case diagram). The following are the characteristics of the limit class:1. This class is easier to modify than the entity and control class.2. The attribute of this class and the screen layout are defined during basic design.3. In a class diagram, there are cases where the stereotype is added.4. In a class diagram, some cases are illustrated by the following icon: Entity class An entity class is a class used to display information and associated behavior that must be stored. Entity objects are used to store and update information about a phenomenon, such as a real event, person, or object. They are generally persistent, having attributes and relationships close to the middle of the paper, as well as acceptance criteria for the working system. Prototyping is the last step to take before implementing the actual system. From here we can identify the strengths and weaknesses of the system, which will give us the opportunity to improve the system before implementing the actual system. PART Ba) Develop a UML use case diagram for We Pay online business and payment. System (WOBPS) described in the story above.b) Draw a UML class diagram for the Online Commerce and Payment System (WOBPS). The class diagram should represent all classes, their attributes, operations, relationships between classes, multiplicity specifications, and other model elements that you deem appropriate. c) Draw an activity diagram for a WOBPS member to register a new product and purchase a product.Register a new productPurchase a product