Docsity
Docsity

Prepare for your exams
Prepare for your exams

Study with the several resources on Docsity


Earn points to download
Earn points to download

Earn points by helping other students or get them with a premium plan


Guidelines and tips
Guidelines and tips

Online Course Reservation System Development, Thesis of Communication

The project aims to introduce automated student's course reservation using computer. The system will have three main interfaces - student interface (web-based), faculty interface (web-based), and register interface (windows-based + web-based). The system will have four types of users: students, register, advisors, and administrators. The key functional requirements include checking course prerequisites, maintaining course data, and meeting technical requirements for enrollment service. The system will be developed using a process model and will go through phases like requirement analysis, design, implementation, testing, and deployment. Details on the project team, cost and budget, and the various modeling techniques used in the design phase.

Typology: Thesis

2022/2023

Uploaded on 01/29/2023

PavanpraneethaKunuku
PavanpraneethaKunuku 🇮🇳

5 documents

1 / 36

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
Online Course Reservation
System Development
pf3
pf4
pf5
pf8
pf9
pfa
pfd
pfe
pff
pf12
pf13
pf14
pf15
pf16
pf17
pf18
pf19
pf1a
pf1b
pf1c
pf1d
pf1e
pf1f
pf20
pf21
pf22
pf23
pf24

Partial preview of the text

Download Online Course Reservation System Development and more Thesis Communication in PDF only on Docsity!

Online Course Reservation

System Development

Team Members

Name Roll No

K. Poojitha Sai

K. Akshay

K. Lakshmi Narayana

K. Pavan Praneetha

M. Tharun

21071A66F

21071A66F

21071A66F

21071A66F

21071A66F

Outline

First meeting with Customer and Devoloper

Customer Requirements

Feasibility Anylysis

Take dicision whether we will take the job or

not.

Soft Team

Required Resources

User Interface

Use a process Model

System Design

Testing & Quality Assurance

Requirement analysis and specification

The goal of this phase is to understand the exact requirements

of the customer and to document them properly

Three interfaces to the system

Student Interface (web based)

Faculty Interface (web based)

Register Interface (windows based + web

base )

Four types of users:

Students

Register

Advisors

Functional Requirement

Requirement

number:

F

Requirement

title:

Check Course Prerequisites

Requirement

text:

Describes the logic to be implemented to ensure that students have the proper prerequisites to take a given course.

Requirement

type:

Functional - Processing

Requirement

details and

constraints:

The University has a set of rules that determine whether a student is eligible to take a given class. One rule is that in order to take a class,

students are sometimes required to take other classes that give them the required foundation for the class. These rules must be enforced

during the student enrollment process. The specific prerequisites to be implemented for each course can be found in the University calendar.

During the enrollment process, the system will:

Retrieve the course the student wishes to enroll in

Retrieve the students course completion history to determine the courses taken and completed successfully by the student

Retrieve the prerequisites for the desired course

Determine if the student has the appropriate prerequisites for the course

If the student has the required prerequisites:

Flag the course as OK, allow course to move to next step in the process (check enrollment)

If the student does not have the appropriate prerequisite courses:

Retrieve override information

Determine if instructor has given student permission (through override) to enroll in the course

If yes, allow course to move to check enrollment step

If no, end message to student that enrollment not allowed.

Revision date

and reversion

number:

Criticality:

Must

Functional Requirements

Requirement

number:

F

Requirement

title:

Course data

Requirement

text:

Describes required system-maintained course data

Requirement

type:

Functional - Data

Requirement

details and

constraints:

A course is an educational offering of the University. The system must maintain the following
information regarding courses:
Course Title.
Course description
Program of study. Each course is assigned to a given program (e.g., Biology, Information Systems,
Business Administration)
Prerequisites. A prerequisite is another course that a student must take to be eligible to for a given
course. Each course may have zero, one or many prerequisites
Etc………….

Revision date

and reversion

number:

Criticality:

Must

After analysis the requirement we decide that we

need to create following web pages

Home Page

Login Page

My Page

Registration page

Change Password

Edit Profile

FAQ

Contact Us

Page for advisor

Page for register

Page for student

About subject

Student list

Student information

Notification

Schedule

Item Item Count Item price

Computers (laptop) HP Probook 4540 4 600$ for each

one

Africom Internet provider - 50$ in

month

Electricity Generator 2 300$ for each

one

Office - 200$ in month

External Hard Drive 2 100$ for each

one

Team salary 6 500$ per month

(5500$)

MS project 5 100$

Office 2007 5 100$

ASP.NET 2 100$

Monitors program 1 100$

Upload services - 72$ in

year

Anti-virus (avira) 5 30$

Foods and drinks for 6 10$ for each

BUDGET

This model contains 6 phases

  1. Design

The goal of this phase is to transform the requirement specification into a

structure that is suitable for implementation in some programming language.

4.Implementation and unit testing

During this phase the design is implemented. Initially small modules are

tested in isolation from rest of the software product.

  1. Integration and system testing

In this all the modules are integrated and then tested altogether.

  1. Operation and maintenance.

Release of software inaugurates the operation and life cycle phase of the

operation.

The phases always occur in this order and do not overlap

1. Use Case Diagram

2. Class Diagram

4. Collaboration Diagram

5.Activity diagram: