Computer Science and Engineering SOFTWARE ENGINEERING

WEEK-1

Course management system (CMS)

1.INTRODUCTION

A course management system (CMS) is a collection of software tools providing an online

environment for course interactions. A CMS typically includes a variety of online tools and
environments, such as:
1. An area for faculty posting of class materials such as course syllabus and handouts
2. An area for student posting of papers and other assignments
3. A grade book where faculty can record grades and each student can view his or her grades
4. An integrated email tool allowing participants to send announcement email messages to the
entire class or to a subset of the entire class
5. A chat tool allowing synchronous communication among class participants
6. A threaded discussion board allowing asynchronous communication among participants
In addition, a CMS is typically integrated with other databases in the university so that
students enrolled in a particular course are automatically registered in the CMS as participants in
that course. The Course Management System (CMS) is a web application for department
personnel,
Academic Senate, and Registrar staff to view, enter, and manage course information
formerly submitted via paper. Departments can use CMS to create new course proposals, submit
changes for existing courses, and track the progress of proposals as they move through the stages
of online approval.

Purpose of the system

The Course management system is an Intranet based application that can be accessed
throughout the organization or a specified group/Dept. This system can be used to automate the
workflow of courses. The Lab experiment will explain the purpose and features of the system,
the interfaces of the system will do the constraints under which it must operate and how the
system will react to external stimuli.

MRIET Page 1
Computer Science and Engineering SOFTWARE ENGINEERING

Existing system

 The current system is a manual one where in the organization maintains all the information in
the form of records. There by collecting necessary information which require a manual
search in the record(s).
 Transfer of information between different sections of the enterprise is in the form of
documents.
Proposed system

 The information of the entire organization will be maintained at a centralized data base any
Changes made known to the higher or lower level members.
 Provide Interactive interface through which a user can interact with different areas of
application
 Easily Deploy the application on a single system and make is available on all the systems
within the network, thereby reducing the maintenance cost of software.

2. SCOPE OF THE PROJECT

CMS will perform a lots of functions which includes the uploading of the results of
quizzes, assignments and session by the instructor, instructor’s comments about the students,
viewing of various results and attendance by students and parents, students’ and parents’
feedback for the teachers, etc. Moreover, the CMS will not do any calculation for computing the
total result of the session including the results of assignments and quizzes. The system will not
maintain the attendance. It will just show the attendance of the students. The system will also not
offer the memberships to the external internet users. And it will also not the official resource, e.g.
results, etc.

Study of the system

In the flexibility of the uses the interface has been developed keeping a graphics concept in
mind, associated through a browser interface. The GUI’S at the top level have been categorized
as

 Administrative user interface

 The operational or generic user interface

MRIET Page 2
Computer Science and Engineering SOFTWARE ENGINEERING

The administrative user interface concentrates on the consistent information that is

practically, part of the organizational activities and which needs proper authentication for the
data collection. The interfaces help the administrations with all the transactional states like Data
insertion, Data deletion and Data updating along with the extensive data search capabilities.

The operational or generic user interface helps the users upon the system in transactions
through the existing data and required services. The operational user interface also helps the
ordinary users in managing their own information helps the ordinary users in managing their own
information in a customized manner as per the assisted flexibilities.

3. NUMBER OF MODULES
The system after careful analysis has been identified to be presented with the following
modules:
The modules involved are:

 Administration
 Student
 Search
 Report
 Authentication

Administrator:-

In this module the Administrator has the privileges to add all the students and register
them in the organization and check the information of the student and search is done based on
the student and course and report is generated for individual student.

Search:-

This module contain complete search like course search, faculty based on the course they
are taking.

Student-

In this module the student has the privileges to use his username and password for login
and he can see the .Use the login id for submitting assignments and taking courses and enter the
problems while he is undergoing a course.

MRIET Page 3
Computer Science and Engineering SOFTWARE ENGINEERING

Reports:-

This module contains all the information about the reports generated for the students

based on the Performance by them for a specific course.

Authentication:-

This module contains all the information about the authenticated user. User without his
username and password can’t enter into the login if he is only the authenticated user then he can
enter to his login.

4. FUNCTIONAL AND NON FUCTIONAL REQUIREMENTS

 Creating Courses
Integration with Registration System: The System Shall periodically Upload the Latest
Registrar’s Classes List to Determine Courses That Offered in the Current Semester. The
System Shall Generate Course For Each Class That Registered And Determine The
Current Set Of Students That Enrolled In That Class. The System Shall Allow Course
Instructor To Update Course Content.

 Grade Management
Allow Grades To Be Entered Online: The System Shall Allow Instructors To Enter And
Modify Grades Online. Allow Students To Access Their Grades Online: The System
Shall Allow Student To Log In Their Account And Check Their Grades At Any Time.
The System Shall Provide Statistical Information Such As Averages, Standard Deviation,
and Median About Students Grades. Track And Handle Re-Grade Requests: The System
Shall Be Able To Track And Handle Requests For Re- Grades, And All Information
About Re-Grades Shall Be Available To The Student, And The Course Instructor.
Homework Submission:

MRIET Page 4
Computer Science and Engineering SOFTWARE ENGINEERING

Non functional requirements

Performance Requirements
If there are performance requirements for the product under various circumstances, state
them here and explain their rationale, to help the developers understand the intent and make
suitable design choices. Specify the timing relationships for real time systems. Make such
requirements as specific as possible. You may need to state performance requirements for
individual functional requirements or features
Safety Requirements
Specify those requirements that are concerned with possible loss, damage, or harm that
could result from the use of the product. Define any safeguards or actions that must be taken, as
well as actions that must be prevented. Refer to any external policies or regulations that state
safety issues that affect the product’s design or use. Define any safety certifications that must be
satisfied.
Security Requirements
Specify any requirements regarding security or privacy issues surrounding use of the
product or protection of the data used or created by the product. Define any user identity
authentication requirements. Refer to any external policies or regulations containing security
issues that affect the product. Define any security or privacy certifications that must be
satisfied.
5. DATA DESIGN
DATAFLOW DIAGRAMS

Fig 1: LEVEL 0 DFD FOR COURSE REGISTRATION SYSTEM

MRIET Page 5
Computer Science and Engineering SOFTWARE ENGINEERING

Fig 2: LEVEL 1 DFD FOR COURSE REGISTRATION SYSTEM

MRIET Page 6
Computer Science and Engineering SOFTWARE ENGINEERING

UML DIAGRAMS

Class Diagram

Fig 3

MRIET Page 7
Computer Science and Engineering SOFTWARE ENGINEERING

Use Case for Faculty

Fig 4

MRIET Page 8
Computer Science and Engineering SOFTWARE ENGINEERING

Use Case for Student

Fig 5

MRIET Page 9
Computer Science and Engineering SOFTWARE ENGINEERING

Sequence Diagram

Fig 6

MRIET Page 10
Computer Science and Engineering SOFTWARE ENGINEERING

Activity Diagram for Admin

Fig 7

MRIET Page 11
Computer Science and Engineering SOFTWARE ENGINEERING

Activity Diagram for Student

Fig 8

MRIET Page 12
Computer Science and Engineering SOFTWARE ENGINEERING

Activity Diagram for Faculty

Fig 9

MRIET Page 13
Computer Science and Engineering SOFTWARE ENGINEERING

DATA DICTIONARY

Table name : student details

Fields Data type size Description

NAME text 20 Name of the student
Dob text 30 Date of birth of the student
ssssssssssssssssssssssssssssssssssstudent
MARK integer 30 Marks of the student
MARK Course of the student can choose the any
course text 10
course
studentststtstudent
Address of the student it can allow the text
ADDRESS varchar 10
allowing with numbers
Email(primary key) text 10 Email id of the student
gender text 10 Gender of the student

Table name: Admin details

Fields Data type size description

Unique
ID(primary key) int 20 identification of
the admin
password text Min 8 Security for login

Table name: course details

Fields Data type size description

Unique
ID(primary key) int 20 identification for
course
Name of the
Course name Text 20
course

MRIET Page 14
Computer Science and Engineering SOFTWARE ENGINEERING

6. IMPLEMENTATION
import javax.swing.*;
import java.awt.*;
import java.sql.*;
import java.awt.event.*;
class RegistrationForm1 extends JFrame{
JTextField text1,text2,text3,text4,text5;
JPasswordField pass1;
JLabel label1,label2,label3,label4,label5,label6;
JPanel panel;
JButton button;
RegistrationForm1() {
text1=new JTextField(15);
text2=new JTextField(15);
text3=new JTextField(15);
pass1=new JPasswordField(15);
text4=new JTextField(15);
text5=new JTextField(15);
label1=new JLabel("First Name");
label2=new JLabel("Last Name");
label3=new JLabel("User Name");
label4=new JLabel("Password");
label5=new JLabel("Address");
label6=new JLabel("Phone No");
button=new JButton("Register");
panel=new JPanel(new GridLayout(7,2));
panel.add(label1);
panel.add(text1);
panel.add(label2);
panel.add(text2);
panel.add(label3);
panel.add(text3);
panel.add(label4);
panel.add(pass1);
panel.add(label5);
panel.add(text4);
panel.add(label6);
panel.add(text5);
panel.add(button);
button.addActionListener(new ActionListener(){

MRIET Page 15
Computer Science and Engineering SOFTWARE ENGINEERING

public void actionPerformed(ActionEvent ae){

String value1=text1.getText();
String value2=text2.getText();
String value3=text3.getText();
String value4=pass1.getText();
String value5=text4.getText();
String value6=text5.getText();
Connection con = null;
String url = "jdbc:mysql://localhost:3306/";
String db = "mallika";
String driver = "com.mysql.jdbc.Driver";
String user = "root";
String pass = "root";
String user1="";
String pass1="";
try{
Class.forName(driver);
con = DriverManager.getConnection(url+db, user, pass);
Statement st = con.createStatement();
System.out.println("connected");

int k=st.executeUpdate("insert into

login1(firstname,lastname,username,password,address,contactno)
values('"+value1+"','"+value2+"','"+value3+"','"+value4+"','"+value5+"','"+value6+"')");
JOptionPane.showMessageDialog(null,"Data is successfully saved");
}
catch(Exception e){}
}
});
add(panel);
setSize(300,400);
setVisible(true);
}
}
class RegistrationForm {
public static void main(String args[]) {
RegistrationForm1 form = new RegistrationForm1();
System.out.println("Registration Form");
}
}

MRIET Page 16
Computer Science and Engineering SOFTWARE ENGINEERING

MRIET Page 17
Computer Science and Engineering SOFTWARE ENGINEERING

7. TESTING
Test case ID: Test_01
Test priority
(Low/Medium/High):Medium
Module name: student login
Test title :verify login with valid username and password
Precondition: student has invalid username and password
S.NO TEST STEPS EXPECTED ACTUAL STATUS NOTES
RESULTS RESULTS
1 Provide valid Student should The user is able Success User can login
Student name Be able to to move to next successfully
login Entry
2 Provide valid Student should be The user is able Success Incase of wrong
password Able to To login Password was
Login Successfully given an error
Message box
was
displayed
3 Invalid pwd User should be password is in failure user gives
able to navigate to validated and wrong entry the
next page after next page is not sign in page
validation displayed remains active
4 Click signup User should be User navigates to success User can sign up
able to navigate to the signup page successfully
next page where where his user
user enters his name and
credentials password is
validated

VIVA QUESTIONS:

1. what is modeling?
2. what is prototype?
3. what is the scope of the project?
4. what is use case and actor?
5. what is class diagram ?
6. How many phases are their in developments of the product?
7. How we can specify the data dictionary?

MRIET Page 18