Scribd
Upload
96 views

Practical Lab List

The document describes the process of developing a student mark analysis system using UML diagrams. It involves problem analysis and defining requirements, identifying use cases and actors, developing activity and class diagrams, and generating code from the UML models. The key steps are: 1. Analyzing the problem statement and objectives of creating a system to efficiently analyze student marks. 2. Identifying use cases like login, entering student details, mark calculation, and generating results reports. 3. Developing activity diagrams and class diagrams to model the system. 4. Using UML models to generate Java code for the student class.

Uploaded by

Ponnusamy Ramalingam
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
96 views

Practical Lab List

The document describes the process of developing a student mark analysis system using UML diagrams. It involves problem analysis and defining requirements, identifying use cases and actors, developing activity and class diagrams, and generating code from the UML models. The key steps are: 1. Analyzing the problem statement and objectives of creating a system to efficiently analyze student marks. 2. Identifying use cases like login, entering student details, mark calculation, and generating results reports. 3. Developing activity diagrams and class diagrams to model the system. 4. Using UML models to generate Java code for the student class.

Uploaded by

Ponnusamy Ramalingam
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 7

1.

Problem Analysis and Project Planning: Thorough study of the problem -Identify Project
Scope, Objectives, and Infrastructure.
2. Software Requirement Analysis: Describe the Individual Phases/Modules of the project and
Identify deliverables.
3. Data Modelling: Use work products – Data dictionary, use case diagrams and activity
diagrams, build and test class diagrams, sequence diagrams and add interface to class
diagrams.
4. Software Development and Debugging: Implement the design by coding.
5. Software Testing: Prepare test plan, perform validation testing, coverage analysis, memory
leaks, develop test case hierarchy, site check and site monitor.

Academic Domain

1. Course Registration System


2. Student Marks Analysis System

Railway Domain

3. Online Ticket Reservation System


4. Platform Assignment for the trains in a railway System

Medicine Domain

5. Experts System to prescribe the medicines for the given symptoms.


6. Remote Computer Monitoring.

Finance Domain

7. ATM System
8. Stock Maintenance

Human Resource Management

9. Quiz System
10. E-mail Client System
Experiment No. 2: STUDENT MARK ANALYZING SYSTEM

Aim: To study and draw the UML diagram for student Mark analysis system using Star UML
software.

1. Problem analysis and project planning

1.1 Introduction

Student mark analysing system has been designed to carry out the mark analysis process in an
educational institution. The results of respective departments can be efficiently computed without
much of manual involvement.

1.2 Objectives

The purpose of this document is to define the requirements of mark analysis system. This system
reduces manual work to great extent. The mark analysis is carried out by the system in an efficient
manner.

1.3 Scope

This system is very essential for every educational institution as it reduces manpower. This system
can be used for all kinds of educational institutions to evaluate and analyse the marks and generate
reports of specified criteria.

1.4 Problem Statement

For analysing the marks obtained by students in an educational institution. We are tasked to build up
student mark analysing system. This is done to replace the manual entering and processing of marks
which are error prone and tedious. This system also maintains information about student. The system
will have a Windows based desktop interface to allow the faculty to enter marks obtained by the
students, update them and generate various reports.

For security reasons, the administrator and faculty only can update the marks and other information.
First the user needs to login to the system for accessing it. The system will retain information on all
the students and the institution. The system analyses the marks and generate the result reports. The
marks and information about the students are stored in a database and the system works with the
database.
The faculty can enter the marks and student information through a visual environment. The updated
details are stored in the database. The system generates the overall result by analysing the marks.
Mark analyser monitors this process. The application in run by the mark analyser. The trial for illegal
updating would render the system to be locked.

One of the most important features of the system is creating reports based on the given criteria. The
user can create the following reports:

Overall Class, Department result, Individual student result, Toppers list, Arrears list and Improvement
rate for the academic year report must be generated by entering the register number of the student.
These reports can also be viewed by the management and placement officers. The administrator is
responsible for adding, deleting student details form the system and updating the marks to the system
with the external queries. So, the system design will generate reports automatically and there will be
no need for manual intervention.

2. Problem Statement (Use case) analysis

2.1 Identified use cases

i Login:
This use case describes how a user logs in to the mark analysing system.

ii Student Details:
This use case allows faculty to enter the marks into the student table.

iii Mark Calculation:


This use case describes how the system generates the overall result by analysing the marks.

v Result :
This use case allows the system to generate various reports based on the criteria specified by the user.

2.2 Identified Actors

i Faculty:
The person responsible for entering and updating the marks obtained by the students.

ii Administrator:
The person responsible for maintaining student information in the system.

iii Database:
The database that contains all the information about the student and their marks.

iv Mark analyzer:
The person responsible for monitoring the mark analyzing process.

v Student:
Details about the students are entered into the system so that the student can view the results and
reports.

vi Placement Officer:
The placement officers can also view the reports based on the criteria specified.
ACTIVITY DIAGRAMS:

CLASS DIAGRAM:

SEQUENCE DIAGRAM:
OUTPUT:
UML to Java V5.0

public class student {


private Object name;
public Object getName() {
// begin-user-code
return name;
// end-user-code
}
public void setName(Object theName) {
// begin-user-code
name = theName;
// end-user-code
}
private Object collegecode;
public Object getCollegecode() {
// begin-user-code
return collegecode;
// end-user-code
}public void setCollegecode(Object theCollegecode) {
// begin-user-code
collegecode = theCollegecode;
// end-user-code
}
private Object regno;

public Object getRegno() {


// begin-user-code
return regno;
// end-user-code
}
public void setRegno(Object theRegno) {
// begin-user-code
regno = theRegno;
// end-user-code
}

public void displayresult() {


// begin-user-code
// TODO Auto-generated method stub

// end-user-code
}
}

RESULT: Thus the analysis design activity for Student Marks Analyzing System is
Completed Successfully.

You might also like