7/29/2019 mod3stud

1/12

G.YOUSUF IBRAHIM

110081101064

MODULE- III

SOFTWARE REQUIREMENT ANALYSIS

STUDENT MARK ANALYSIS SYSTEM

USE CASE DIAGRAM:

A UML Use Case diagram is a type of behavioral diagram defined by and created from a Use

Case analysis. Its purpose is to present a graphical overview of the functionality provided by

a system in terms of actors, their goals (represented as use cases), and any dependencies

between those use cases.

Brief Description:

This use case describes about the login and result generation of both student and staff in the

student mark analysis system.

Flow of Events:

This use case allows the administrator to add faculty in to the system, allows faculty to

manage test, student groups, generate result and allows student to login, create profile and

view result

Special Requirements:

The student should have an account, user id and password

PreConditions:

The student should login and view the result and the same for the staffs to update the result

PostConditions :

Have to logout after update or viewed the result

7/29/2019 mod3stud

2/12

G.YOUSUF IBRAHIM

110081101064

student registration

appear for test

administrator

add faculty

login

user profile

extend

manage student groups

manage test

include

system

logout

faculty

include

student

result generation

include

view result

extend

7/29/2019 mod3stud

3/12

G.YOUSUF IBRAHIM

110081101064

CLASS DIAGRAM:

The class diagram is the main building block of object oriented modelling. It is used both for

general conceptual modelling of the systematic of the application, and for detailed modelling

translating the models into programming code. Class diagrams can also be used for data

modelling. The classes in a class diagram represent both the main objects, interactions in the

application and the classes to be programmed.

In the diagram, classes are represented with boxes which contain three parts.

The upper part holds the name of the class The middle part contains the attributes of the class The bottom part gives the methods or operations the class can take or undertake

In the design of a system, a number of classes are identified and grouped together in a class

diagram which helps to determine the static relations between those objects. With detailed

modeling, the classes of the conceptual design are often split into a number of subclasses.

In order to further describe the behavior of systems, these class diagrams can be

complemented by uml state diagram. Also instead of class diagrams object role

modelling can be used if you just want to model the classes and their relationships.

7/29/2019 mod3stud

4/12

G.YOUSUF IBRAHIM

110081101064

7/29/2019 mod3stud

5/12

G.YOUSUF IBRAHIM

110081101064

SEQUENCE DIAGRAM:

The first interaction diagram is the sequence diagram. A sequence diagram, in the context of

UML, represents object collaboration and is used to define event sequences between objects

for a certain outcome. A sequence diagram is an essential component used in processes

related to analysis, design and documentation.

A sequence diagram is also known as a timing diagram, event diagram and event scenario.

Brief Description:

The following sequence diagram shows the sequence of events happening while generating

result and login

Flow of Events:

The faculty logs in creates group, adds student to the group, the system invites the students

for taking the test, the staffs creates the test and the student writes the test, and the staffs

evaluate marks and update in the system and the system generates the result

Special Requirements:

The staff and student should have account, userid and password for updating marks and

viewing result

PreConditions:

The student and staff should login

PostConditions :

The student and staff should logout

7/29/2019 mod3stud

6/12

G.YOUSUF IBRAHIM

110081101064

SEQUENCE DIAGRAM OVERVIEW:

student faculty system

login

verify login

create group

add student

invites for test

create test

logout

register

retrieve register group

login

verify login

select test

answer question

compute result

display result

7/29/2019 mod3stud

7/12

G.YOUSUF IBRAHIM

110081101064

LOGIN SEQUENCE:

user system

enter details

verify login

home page

start session

7/29/2019 mod3stud

8/12

G.YOUSUF IBRAHIM

110081101064

COLLABORATION DIAGRAM:

The second interaction diagram is collaboration diagram. It shows the object organization as

shown below. Here in collaboration diagram the method call sequence is indicated by some

numbering technique as shown below. The number indicates how the methods are called one

after another. We have taken the same order management system to describe the

collaboration diagram. The method calls are similar to that of a sequence diagram. But the

difference is that the sequence diagram does not describe the object organization where as the

collaboration diagram shows the object organization

Brief Description:

The following collaboration diagram shows the sequence of events happening while

generating result and login

Flow of Events:

The faculty logs in creates group, adds student to the group, the system invites the students

for taking the test, the staffs creates the test and the student writes the test, and the staffs

evaluate marks and update in the system and the system generates the result

Special Requirements:

The staff and student should have account, userid and password for updating marks and

viewing result

PreConditions:

The student and staff should login

PostConditions :

The student and staff should logout

7/29/2019 mod3stud

9/12

G.YOUSUF IBRAHIM

110081101064

OVERVIEW COLLABORATION:

LOGIN COLLABORATION:

student

faculty

system

1: login

2: verify login

3: create group4: add student

5: invites for test

6: create test7: logout

8: register

9: retrieve register group

10: login

11: verify login

12: select test

13: answer question

14: compute result

15: display result

user system

1: enter details

2: verify login

3: home page

4: start session

7/29/2019 mod3stud

10/12

G.YOUSUF IBRAHIM

110081101064

ACTIVITY DIAGRAM:

Activity diagrams are graphical representations of workflows of stepwise activities and

actions with support for choice, iteration and concurrency. In the Unified Modelling

Language, activity diagrams can be used to describe the business and operational step-by-step

workflows of components in a system. An activity diagram shows the overall flow of control.

Brief Description:

This activity describes about the activity of student mark analysis system in this login activity

and display result activity is described

Flow of Events:

First the user enters the userid and password and then sbmits. The user id and password is

verified if valid enters into the homepage if invalid goes to the enter userid and password

page and then in display result activity the answer is compared marks are given result is

generated and mailed

Special Requirements:

The student should have a account userid and password

PreConditions:

The student should login

PostConditions :

The student should logout

7/29/2019 mod3stud

11/12

G.YOUSUF IBRAHIM

110081101064

LOGIN ACTIVIY:

7/29/2019 mod3stud

12/12

G.YOUSUF IBRAHIM

110081101064

DISPLAY RESULT: