3.

DESIGN/MODELING IN UML (ALL THE DIAGRAMS)

This stage has been responsibility of the student: Name: Surname: ID:

Designing and modeling the UML diagrams, undoubtedly is one of the most important fazes, which weights a lot in the well-doing of the project that is being developed. Under way, we hope to concentrate deeper in the diagrams in Unified Modeling Language (UML). Use Case Diagram

This diagram shows from higher site, what in fact have to do with. There are mentioned general actors and the general processes around which are placed all the others Activity Diagram

As we know, activity diagram represent the business and operational workflow of a system. An activity diagram is a dynamic diagram that shows the activity and the event that causes the object to be in the particular state. In our case, the activity diagram describes the situation of requesting certificate. First, the user requests a certificate, and employee will have to log-in to system by typing username and password... Sequence Diagram A sequence diagram depicts the sequence of actions that occur in a system. The invocation of methods in each object, and the order in which the invocation occurs is captured in a sequence diagram

Collaboration Diagram

A collaboration diagram is very similar to a sequence diagram, and a distinguished feature of collaboration diagram is that it shows the objects and their association with other objects in the system apart from w they interact with each other . Class Diagram Class diagram consists of group of classes and interfaces reflecting important entities of the business domain of the system being modeled, and the relationships between these classes and interfaces. Object Diagram An object diagram shows relations between the instantiated classes and the defined class, and the relation between these objects in the logical view of the system. State Diagram State diagrams are used to describe the behavior of a system, and describes all of the possible states of an object as event occur

Component Diagram Component diagram represent different high level reusable parts of a system, also captures the interrelationships between these parts. Also represent the implementation perspective of a system. 14 Deployment Diagram Deployment diagram captures the configuration of the runtime elements of the application and more useful when a system I built and ready to be deployed.

4. FORMAL SPECIFICATION OF THE SYSTEM IN Z -ZED

This stage has been responsibility of the student: Name: Student4 Surname ID: 104877

The mathematical representation of project things, sounds of a kind to this tables you see.