explanations and can logout. Administrator has the privilege to

explanations on the design decisions. Derive detailed use case diagram,
class diagram & a sequence diagram. Whenever necessary document the
relevant assumptions you made. (9 Marks)

UML is a visual software diagram that is object –oriented
design and used to develop diagrams by developers and can be used for modeling
a system independently. It is also a graphical language to construct and
visualize information about the software.

We Will Write a Custom Essay Specifically
For You For Only $13.90/page!


order now

UML diagrams are of many types

1.     
Use
Case Diagram

2.     
Class
Diagram

3.     
Sequence
Diagram      

  

Use Case Diagram.

 

Use case diagrams are diagrams used to describe a
set of actions named use cases. Some
system should perform with one or more external actors of the system. There are five users that can access in this system.

The benefits of using use cases are that
they can help to define the scope and used to plan the development process and
develop and validate the requirements.

 

·        
Administrator has a username and password to
login and can logout. Administrator has the privilege to create, modify, delete
and search details of projects and users including manager, client, employee,
and coordinator. Administrator also can view User list and project list and
receive all the reports of the above details.

·        
Manager has a username and password to login and
can logout. Manager can view user list and project list and receive all the
reports of the above details and check status of the project and search details
of project. Manger can send newsletters to clients to update with the latest
news.

·        
Coordinator has a username and password to login
and can logout. Coordinator has the privilege to create, modify, delete and
search details of projects and users including client and employee. Coordinator
can view user list and project list, receive all the reports of the above
details and allocate projects to the employees and check project status.

·        
Client has a username and password to login and
can logout. Client get newsletters by the manager and sends feedback about the
project.

·        
Employee has a username and password to login
and can logout. Employee can check the allocated project using project list and
update status of the project.

 

Class Diagram.

Class Diagram is the most popular UML diagram which is used to
model the static view and can be directly mapped with object-oriented
languages.

The main symbols used in the class diagram are:

·        
Classes
which show the types of data

·        
Associations
which show connection between the classes

·        
Attributes
where simple data is seen in classes

·        
Operations
which represent the functions performed by the classes

·        
Generalizations
where clustered classes are shown in inheritance hierarchies

 

Figure 1- Class Diagram

 

There are 4 classes used in the above diagram. User class is
further divided into 5 sub classes. The user class contains attributes such as
userid, name, contactno, email and etc. and can add, update and delete details.
The Administrator creates new projects from the project class which has
attributes such as projected, name, description, startdate and etc. The project
class can add, update and delete project details. The manager views the project
report and sends newsletters to the clients. The coordinator allocates projects
to the employees. The newsletter class has id, subject and message as attributes.
The manager can add, update or delete newsletter details. The coordinator gets
project feedback from the clients. The feedback class has attributes of id,
projectid, description and clientid. Each user performs the functions available. The user can only login when
the details are authenticated. Details are then stored or altered once the
details are validated and then stored in the database.

In the above diagram there are some visibility markers which
signifies the access of the information in a class. Private visibility is shown
with a – sign which hides information from anything outside. Public visibility
is shown with a + sign allowing all other classes to see the information. Multiplicity
signs are also used near the ends of the association to show the number of chances
of one class connected to the other class. Constraints are used inside curly
braces {}. Composition is also used to denote a strong ownership between the
few classes. In the user class, composition is used.

 

Sequence Diagram.

A sequence
diagram is a UML diagram that shows the order and process of the object arranged
in time sequence.

Figure 2- Sequence Diagram

 

The sequence diagram usually uses class roles, activation, lifelines,
and messages such as synchronous message, asynchronous message, reply and self-message.

In the above diagram, 7 objects named Database,
System, Employee, Client, Manager, Coordinator, and Administrator are used in
the diagram. The administrator adds, modifies or deletes user to the system.
The system further requests it to operate to the database. Once the request is
approved, the response is given by the database to the system and user is added
or modified or deleted successfully. The administrator adds, modifies or
deletes project details to the system. The system further requests it to
operate to the database. Once the request is approved, the response is given by
the database to the system and project detail is added or modified or deleted
successfully. The manager adds, modifies or deletes project details to the
system. The system further requests it to operate to the database. Once the
request is approved, the response is given by the database to the system and
project detail is added or modified or deleted successfully. The manager sends
the request to send newsletter to the system. The system further requests it to
operate to the database. Once the request is approved, the response is given by
the database to the system and newsletter is sent successfully. The coordinator
allocates projects to employee and send a request to the system. The system
further requests it to operate to the database. Once the request is approved,
the response is given by the database to the system and the given project is
allocated to the respective employee successfully. The client adds a feedback
to the system. The system further requests it to operate to the database. Once
the request is approved, the response is given by the database to the system
and the feedback is added successfully. The employee updates the status of the
project to the system. The system further requests it to operate to the
database. Once the request is approved, the response is given by the database
to the system and the project status is updated successfully.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

x

Hi!
I'm Kara!

Would you like to get a custom essay? How about receiving a customized one?

Check it out