USE CASE DIAGRAM

Use case diagram is a graph of actors, a set of use cases, association between the actors
and the use cases and generalization among the cases. Use case diagram is a list of actions or
events. Use case diagram was drawn to represent the static design view of the system. Steps
typically defined the interactions between a role and a system to achieve a goal. The use case
diagram consists of various functionality performed by the actors like student, staff, system,
DBA and server. The use case diagram consists of various functionality like login, display,
enter profile, enter mark, view details, update details, allow access, request access, store details,
logout.

login

<< actor >>

display projection of
student
information

enter profile

enter mark

student
view details
staff

update details

allow access
server
DBA

request access

store data

logout
CLASS DIAGRAM
The class diagram is the graphical representation of all classes used in the system. The
class diagram is drawn as rectangular box with three components or compartments like class
name, attributes and operations. The student information system makes use of the following
classes like student, staff, system, DBA and server.
SEQUENCE DIAGRAM
A Sequence diagram represent the sequence and interaction of a given usecase or
scenario. Sequence diagram capture most of the information about the system. Here the
sequence starts between the student and the system. The second half of interaction takes place
between staff and system then by police and followed by database. The student first login to
the system and then view the details of the details. Staff login to the system enter mark and
enter the details of the student. DBA store and update the details of the student

student staff system server DBA

login
request access

allow access

display

view details
logout

login
request access
allow access
display

enter profile

enter mark

provide data
store data
update data

logout
STATE CHART DIAGRAM
A State chart diagram is also called as state machine diagram. The state chart contains
the states in the rectangular boxes and the states are indicated by the dot enclosed. The state
chart diagram describes the behavior of the system. The state chart involves six stages such as
login, enter mark, enter profile, view details, provide details, update details, store details and
logout.

login enter enter

marks profile

view details

logout store update

details details

COMPONENT DIAGRAM
Component diagram carries the major living actors of the system. The component
diagram main purpose is to show the structural relationship between components of the
system.The main component of the system is student information system and the other
components of the system are student, staff and DBA.

student information
system

student staff DBA

COLLABORATION DIAGRAM
A Collaboration diagram represents the collaboration in which is a set of objects
related to achieve a desired outcome. In collaboration, the sequence is indicated by numbering
the message several numbering schemes are available. Login, request access, allow access,
display, view details, logout, login, request access, allow access, display, enter profile, enter
mark, provide data, logout, store data, update data.

staff
student
1: login
5: view details 10: display
6: logout

7: login
4: display 11: enter profile
12: enter mark
system 16: logout

14: store data

2: request access
8: request access 15: update data

13: provide data

server DBA
3: allow access
9: allow access
DEPLOYMENT DIAGRAM
Deployment diagram shows the configuration of runtime processing elements and the
software components processes and objects that live in them. Component diagram are used in
conjunction with deployment diagram to show how physical modules code are distributed on
various hardware platform. The processor node in the system is student information system and
the execution environment nodes or device nodes are student, staff and DBA.
ACTIVITY DIAGRAM
Activity diagram are graphical representation of stepwise activities and actions with
support for choice, interaction and concurrency. Here in the activity diagram the student login
to the system and view the details of the student. The staff login to the system for entering the
student details and update the details in the database. The final interaction is the DBA store
the details of the student