Professional Documents
Culture Documents
2. ANALYSIS
It is a formal, approved document used to guide both project execution and project
control. The primary uses of the project plan are to document planning
assumptions and decisions, facilitate communication among stakeholders, and
document approved scope, cost, and schedule baselines.
The Project Plan is a relatively brief document that is addressed to a diverse
audience. It must communicate scope and resources to software management,
technical staff, and the customer. It defines risks and suggests risk aversion
techniques. Also define cost and schedule for management review. It provides an
overall approach to software development for all people associated with the project
and outline how quality will be ensured and change will be managed.
For our college time table project the project plan phase comprises of the
identification of different tasks.
All the work needed to perform the project is analyzed and organized. The problem
and value proposition addressed by the project is described. Task performed to
complete the work is divided in the group of five, where each individual has to
perform their own task and later we have integrated the all the task. The timeline of
the project is also decided from the beginning.
It comprises of different modules of our project. Each module determines the
following task respectively as follows:Module I: Registration
Fill all the entries such as email id, password, phone no and address. Then, after
filling all the details correctly and press the submit button. All the entries stored in
the database
Module II: Insertion of Details
College details
Teacher details
Subjects, labs, seminar, project lab details
Branch and shift details
Module III: Change password
Here, the user can change his password by entering the email id, old password
and new
2.2FEASIBILITY STUDY
The technical issues usually raised during the feasibility stage of the investigation
include the following- Does the necessary technology exist to do what is
suggested, Will the proposed system provide the adequate response to the inquires
and perform all the expected functions, Can the system be upgraded if it is
developed more in later and are they have technical guaranty of accuracy,
reliability, ease of access and data security.
The current system developed is very much technically feasible. It is web based
systems which provide the easy access to the users. The purpose of the database is
to create, establish and maintain a workflow among different entities like teachers,
subjects and labs. Permission to the users would be granted based on the roles
specified. Therefore, it provides the technical guarantee of accuracy, reliability and
security.
The software and hardware requirement for the development of this project are
not many and they are available as free as open source. The work for this project is
done with current and existing web designing technology as PHP, MySql and tools
like Dreamweaver. At the user end, the need of good web browser that supports
PHP5 and the fast internet connection is required.
Any system is beneficial if they can be turned out into information system. This
will helps in meeting the operating requirements of the organization. Operational
feasibility aspects of the project are to be taken as an important part of the project
implementation.
Some of the important issues raised are to test the operational feasibility of a
project includes the following- Is there is sufficient support of the management
from the users, will the system be used and work properly if it is being developed
and implemented and will there be any resistance from the user that will undermine
the possible application benefits.
Our system college time table management is in accordance with the above
mentioned issues. Beforehand, the management issues and user requirements have
been taken into consideration. So there is no question of resistance from the users
that can undermine the possible application benefits.
The well planned design will ensure the user for the optimal utilization of the
computer resources and will help in the improvement of performance status. Our
system follows all the standards given above. So, our system is operational
feasible.
A system can be developed technically and that can be used if installed but it will
be beneficial for the organization when it is financial feasible.
In the economic feasibility, the development cost in creating the system is
evaluated against the ultimate benefit derived from the new systems. Economical
benefits must equal or exceed the costs. Our system is economical feasible.
Our project does not need any high cost software and hardware. As our system
is an online based system. So the user needs only user friendly web browser and
the high speed internet and he should have good knowledge about how to use the
internet services. There is a normal expenditure and economic feasibility on the
project.
This module is financially feasible because we are using existing tools and
software to develop it. We do not need to buy any other software. We are going to
use following tools and software.
CHAPTER 3
3. DESIGN
The design of the project specifies the overall implementation of the project in
terms of Software Requirement Specification, UML diagrams, Sequence
Diagrams, Activity Diagrams. All these specify the overall functionality of the
system which is being developed.
3.1 SOFTWARE REQUIREMENT SPECIFICATION
3.1.1 INTRODUCTION
3.1.1.1 PURPOSE
The purpose of this document is to present a detailed description of the Web based
college time table management system. It will explain the purpose and features
of the system, the interfaces of the system, what the system will do, the constraints
under which it must operate and how the system will react to external stimuli. The
document also describes the nonfunctional requirements such as the user
interfaces. It also describes the design constraints that are to be considered when
the system is to be designed, and other factors necessary to provide a complete and
comprehensive description of the requirements for the software. The software
requirement specification captures the complete software requirements for the
system, or a portion of the system. Requirements described in this document are
derived from the vision document prepared for timetable management system.
3.1.1.2 SCOPE
It describes the scope of the software application to be produced. The description
identifies the software product; describe its functionality and application of the
software. It includes the description of the benefits, objectives and goals of the
software. The scope of the system is to generate time table for different branches
according to the data entered. Forms are filled according to the data. If anyone
wants to view teacher load then also he can able to see. If the user wants to print
then also he can do.
3.1.1.4 REFERENCES
Core PHP programming, Pearson edition
Internet
www.w3school.com
3.1.1.5 OVERVIEW
Describe the general factors that affect the product and its requirements.
3.1.2.1PRODUCT PERSPECTIVE
The whole document contains the following in the mentioned order:
The user will login through their login id and password otherwise he will
register himself.
The user fill all the details related to college, subjects and teacher.
The user can see the teacher load and subject load.
The user can change its password after login through their email id and old
password.
Time table generates according to the semester and branch.
The user can print the time table.
3.1.2.2PRODUCT FUNCTION
Print button
Login
Submit
Print option
Log out
Constraints
It describes the factors that limit the scope and functionality of the software.
As our project, is a web based system so its main requirement is the high
speed internet connection and latest version of the web browser that supports
PHP5.
3.4UML DIAGRAM
3.4.1 USE CASE DIAGRAM
Use Case Diagram 1
Actor: Administrator
Object: 1. Maintain Login Id and Password
2. Maintain Database
3. Maintain College Details
System
MAINTAIN DATABASE
CHECK VALIDATION
System
HOD
GENERATE TIMETABLE
COLLEGE
+NAME
1..*
DEPARTMENT
+NAME
1
1
HAS
HAS
1..*
TEACHER
+ID
+NAME
+QUALIFICATION
+TYPE
+LECTURE
+ADD()
+DELETE()
+ASSIGN()
HAS
COURSE
*
TEACH
1..*
1..*
1..*
ROOM
+CCODE
+NAME
+LECT_PER_WEEK
+ROOM_ID
+LOCATION
+CAPACITY
+ADD()
+DELETE()
+ASSIGN()
+ADD()
+DELETE()
+ASSIGN()
1..*
1..*
ASSIGN
ASSIGN
ASSIGN
1
TIMETABLE
1
READER
PROFESSOR
LECTURER
GRADUATE
POST GRADUATE
OTHERS
+SID
+INSTRUCTOR
+ROOM
+MID
+CREATE()
+MODIFY()
+DELETE()
+SEARCH()
LOGIN
VALIDATE(USER,PASSWORD)
DISPLAY LOGIN ERROR MESSAGE
VALIDATE
[FAILURE]
[SUCCESS]
(LECTURER/STUDENTS)
Figure above shows the activity diagram for Log-in. First, the lecturers, students
and administrator need to log in using the username and password that was created
during registration. The system will validate the username and password. If the
password or username is invalid, an error message will be displayed and the
lecturer or student oradministrator can try to log in again. If log in is successful, the
system will identify theuser as a lecturer, student or an administrator.
(FAILURE)
(ADD CLASS)
READ INPUT
ADD SUBJECT
(SUCCESS)
REGISTER SUBJECT
Above figure shows the activity diagram for add subject and class. Both screens
are the same. If the administrator wants to add the subject or the class, he or she
has to fill in the form the subject or the class information. Then click on the next
button. Validation of the form will be carried out before the data is stored in the
database. Upon successful adding the subject or class, a successful application
page will be display. If validation failed, an error message window will pop up.
READ INPUT
DISPLAY SUCCESS RESULT
(AVAILABLE)
BOOKING CLASS
READ INPUT
(SUCCESS)
(NOT AVAILABLE)
(NOT SUCCESS)
DISPLAY NOT AVAILABLE CLASS MESSAGE
USER/ADMIN
LOGIN
DATABASE
1 : USER NAME/PASSWORD()
2 : CHECK VALIDATION()
3 : VERIFY USER()
4 : MDI SCREEN()
5 : UNSUCCESSFUL VALIDATION()
6 : UNSUCCESSFUL VALIDATION()
Figure above shows a sequence diagram for the user validation. In order to log in,
the lecturer/student/administrator need to key in their username and password.
Then the browser will sendthe information to the web server and validate the
information with the database.Successful validation will be sent to the web server,
and the server will display the Main Menu page according to the user type. As for
unsuccessful validation, the server will send an error login page to the monitor.
ADMINISTRATOR
FRONTEND
DATABASE
4 : SENDS FIELD()
7 : UNSUCCESSFUL()
8 : ERROR MESSAGE()
Figure above shows a sequence diagram for Adding teacher. The browser
will send a request to the web server and it will return the teacher information
page. The teacher will have to fill information form. If validation is successful, the
query will be passed to the database and after the data is stored successfully, the
message will be displayed. If the form validation failed, a window with the error
message will pop out.
ADMINISTRATOR
FRONTEND
DATABASE
1 : SELECT COURSE()
2 : SELECT WORKLOAD()
3 : ENTER TEACHER,ROOM AND COURSE()
4 : SENDS FIELD()
7 : UNSUCCESSFUL()
8 : ERROR MESSAGE()
Figure above shows a sequence diagram for adding Timetable. The browser will
send a request to the web server and it will return the information page which
include information to be filled related to teacher,subject, class,labs. After filling
these fields it is been send for validation. If validation is successful, the
information will be passed to the database and after the data is stored successfully,
the message will be displayed. If the page validation failed, a window with theerror
message will pop out.
LEVEL 0
Level 0
Administrator
College Time
Table
Management
Database
LEVEL 1
Level 1
Administrator
Database
Admin
Administrator
Login Id
and
Password
Login
Validation
College Time
Table System
Faculty
Detail
Subjects
Detail
Faculty database
Subject Database
LEVEL 2
Level 2
New faculty
Faculty or
HOD
Faculty database
Login
id
User validation
Passwor
d
Time table
management
system
CHAPTER 4
4.1 CONCLUSION