1. Class stereotypes applied by default with the parsing template template. Stereotypes roughly correspond to the parts of the Model-View-Controller (MVC) design pattern, where Boundary represents the view, Entity is the model, and Control is the controller. Boundary class is a stereotyped class or object that represents a system boundary that is a user interface screen, system interface, or device interface object. Additionally, it could be used in the analysis or design phase of development to capture users or external systems interacting with the system under development. It is often used in sequence diagrams that demonstrate user interactions with the system. Next comes the entity class which is a stereotyped class or object that represents information or data, usually but not necessarily persistent. Feature also drawn as a circle with a line attached to the bottom of the circle. The last is the control class; control is a stereotyped class or object used to model the flow of control or some coordination of behavior. One or more control classes can describe the realization of a use case. System controls represent the dynamics of the designed system and generally describe “business logic”. The control is drawn as a circle with an arrow embedded at the top.2. The system requirement is to gather information about what the system should do from many sources. Methods of collecting or determining system requirements, which are a traditional method and a modern method, as well as five main approaches to determining system requirements. The traditional method has 5; questionnaires, interviews, group interviews, direct observations and documents. A questionnaire is more cost effective than interviews and can be administered over the phone......in the middle of a sheet of paper......captured data, even in a medium sized project can be difficult to manage and to evaluate with the client team. To facilitate this process, requirements should be specified in a uniform and structured manner to facilitate management and evaluation. For non-functional requirements, there are platform requirements. The platform requirement is to support the solution. It is anticipated that in many cases the solution will be an extension of an existing IT service and therefore the requirements of the technology platform will already be known. Current IT architecture standards must also be taken into account during this activity. The last one is process requirements. These are specific methods used during process control to ensure that a finished product meets product requirements. Understanding product requirements and process requirements helps prevent coating defects from occurring.