ROUTINE MANAGEMENT SYSTEM
A MINI SEMESTER PROJECT REPORT
SUBMITTED IN PARTIAL FULFILLMENT OF THE REQUIREMENTS FOR THE AWARD OF
THE DEGREE OF
BACHELOR OF TECHNOLOGY
NATIONAL INSTITUTE OF TECHNOLOGY,AGARTALA
Laxmi Kant Yadav
Gauri Shankar Bharti
Jai Singh Meena
This project would not have taken shape, but for the guidance provided
by Mrs. Lolita kumari Assistant Professor, NIT Agartala and . Mr.
KishorSir and Muni mam has helped me so much.I express my profound
gratitude to Dr. paritoshbhattacharji [HOD, CSE] and all staff members
of the Department of Computer Science &Engg. for their endless help
The guidance andsupport received fromall the members who
contributed and who are contributing to this project, was vital for the
success of the project. I am grateful for their constant support and help.
Above all, I wish to express my heartfelt gratitude to my family &
God, who has always been the singular source of inspiration in all my
ventures I have undertaken.
Laxmi Kant Yadav
Gauri Shankar Bharti
Jai Singh Meena
Students and Faculties of NIT Agartala by administrators, for updating &
maintainingThe College Time Table Generation System is designed &
developed for the time-table details. It is to build a secure, flexible, easy to
maintain environment for creating and maintainingacademic records for
B.Tech students. In the meanof this goal services for faculties and students
will be improved and the new environment will be created.When new
student will take admission in B.Tech. then its time table records will be
inserted in Database & the time table of each semester student will be
updated to the Database according to needs(i.e.how the syllabus is going on
for each semester).One &most important objective is to make the system
1. Administrator Activities
1) Create the new user (Student & Faculty)
2) Update the timeablet of Students.
3) Remove the student.
4) Update the subject allocated to faculties.
2. Faculty activities
1) Only view the owns schedule not others
2) Can’t update its Schedule,its responsibility only to
3. Student activities
1) Only view his/her time-schedule information not to others.
2) Can’t update its Schedule, its responsibility only to
Processor: Pentium III or higher.
RAM: 256 Mb or more.
Web Server: Apache Tomcat 5.5.
Operating System: Windows
Rational Rose (IBM Enterprises)
2.SOFTWARE QUALITY ASSURANCE PLAN
Management:-A description of each major element of the organization
and a description of the SQA tasks and their relationships.
Documentation:-Identification of the documents related to
development,verification, validation, use and maintenance of the
Develop requirement specification and cost estimation for the
Develop the design plan and test plan for testing the tool.
Implement and test the application and deliver the application
along with the necessary documentation.
Give a formal presentation to the client on completion of the
analysis, design and testing phases. The client reviews the work
and provides feedback/suggestions.
Planning, coordinating, testing and assessing all aspects of
2.3:-DOCUMENTATION :In addition to this document, the essential documentation will
include:The Software Requirements Specification (SRS), which
Prescribes each of the essential requirements of the
Objectively verifies achievement of each requirement by a
Facilitates traceability of requirements specification to
Gives estimates of the cost/effort for developing the
product including a project
The Software Design Document(SDD)
Depicts how the software will be structured.
Describes the components and sub-components of the
software design, including various packages and
frameworks, if any.
Gives an object model the essential classes that would
make up the product.
Gives a sample interaction diagram, showing the key
interactions in the application.
2.3SOFTWARE DEVELOPMENT PROCESS :The software development process involves three stages:Requirements phase.
Implementation and testing phase.
During each phase, the client will review the deliverable documents.
The developer would incorporatemodifications suggested by the
committee. This would ensure quality of the software product.
2.3 TESTING AND QUALITY CHECK :Testing will be carried out in accordance with the Software Testing
Plan (STP). Testing documentation will be sufficient to demonstrate
that testingobjectives and software requirements have been met. Test
results willbe documented anddiscussed in the final phase of the
SYSTEM ANALYSIS:-System analysis is the process of gathering and
interpreting facts, diagnosing problems and using the facts to improve the
system. System specifies whatsystemshoulddo. A system is a set of
components that interact to accomplish some purpose
Identifying the drawback of the existing system.
Identify the need for conversion.
Perform feasibility study.
Identify hardware, software and database requirements.
Create a system definition that forms the foundation for
3.1 SYSTEM STUDY:The College - Time-Table generation System is designed & developed by
Administrators for faculties, students of NIT Agartala in order to create,
update the time table informational. The objective of College Time Table is
to provide quality data in a timely fashion through systems that are
Objectives of Student Information System
1) The objective of College Time Table System is to provide quality
data in a timely fashion through systems that are completely
2) By collecting data at the source and providing wider electronic
access (particularly to students and faculty), the intention of
CTT system is to reduce the paper driven aspects of the existing
3) The objective of this System is to provide facilities for
authorized users to enter information into the system directly,
instead of passing the information (usually on paper) to another
individual at another location to enter into the system.
The problem is analyzed and feasibility study is also performed for making
sure that it is feasible for creating such a web site. The feasibility report is
created and mainly three types of feasible studies are performed.
3.2.1 Technical Feasibility:Technical feasibility centers on the existing computer and to what
extend it cansupport the proposed addition. In technical feasibility
both software and hardwarefeasibilities are checked. In the case of
hardware the created software can be executed on any configurations
in which Microsoft windows operation system works.
3.2.2 Functional Feasibility:All functional and non-functional requirements have been analyzed.
Functionalrequirements are the one the minimum things the system
should support.Nonfunctional requirements are mainly to avoid
external events that can affect the system performance. The proposed
system isbeneficial only if they can be turned into information
system that will meet the organization’s functional requirements.
3.2.3 Time Feasibility:Will the proposed project be completed within the stipulated time
frameeffectively? As the analysis shows, the projecthas a scope for a
long period of time . The stipulated time for this project is three
months and it can be completed within that span of time.
As this project is technically, functionally, timely feasible,
the system is judged feasible. Viewing thecollected information,
recommendation and justification,conclusions is made of the
4 .SYSTEM REQUIREMENT SPECIFICATION
4.1 :User Interface Requirements
Three types of users are allowed in this system, one is the
student second is thefaculty other one is the administrator. On
providing the correct login name andpassword the users can get
into the website.
4.2: Database Requirements
MySQL is used as the Back end. The tables are designed using
5 .Architectural Design
Large system can be decomposed into sub-systems that provide some
related setof services. The initial design process includes, identifying
these sub-systems andestablishing a framework for sub-system
control and communication.
5.1 :Data Flow Diagram
A DFD or data flow diagram is a graphical representation that depicts
the information flow and the transformation that are applied to data
it moves from input to output. Data Flow Diagram (DFD) is used to
define the flow of the system and its resources such as information.
Data Flow Diagrams are a way ofexpressing system requirements in a
graphical manner . DFS represents one of the most ingenious tools
used for structured analysis. A DFD is also known as a bubble chart.
It has the purpose of clarifying system requirements and identifying
major transformations that will become programs in system design.
5.2 :PROTOYPING MODEL :Working of Prototype model can be described as :
Implementation and Unit Testing
Integration and System Testing
Operation and Maintenance
Requirements as per
6 .SYSTEM IMPLEMENTATION
A crucial phase in system development is the successful
implementation of the newsystem design. Implementation includes
all those activities that take place to convert from the old system to
the new system to the new system. The new system may becompletely
new replacing an existing manual or automated system or it may be
major modification to an existing system.
In either case proper implementation becomes necessary so that a
reliable system based on the requirement of the organization can be
provided. Successful implementation may not guarantee
improvement in the organization using the new system, but improper
installation will prevent this improvement.
It has been observed that even the best system cannot show good
results if the analysts managing the implementation do not attend
every important detail. This is the area where the system analysts
need to work with utmost care.
7 .SYSTEM MAINTENANCE
System maintenance is the modification of a software product after
delivery to correct faults, to improve performance or other attributes,
or to adapt the product to amodified environment. Maintenance is
thus a very broad activity often defined as including all work made on
a software system after it becomes operational.
Maintenance covers large number of activities like the correction of
errors, the enhancement, deletion and addition of capabilities, the
adaptation to changes in data requirements and operation
environments, the improvement of performance, usability, or any
other quality attribute. Maintenance accounts for 50-80 percent of
total system development. To put maintenance in its proper
perspective requires considerable skill and experience and is an
important and ongoing aspect of system development. Maintenance
demands more orientation and training than any other programming
activities. The environment must recognize the needs of the
maintenance programmer for tools, methods and training.
Maintenance is done after the successful implementation of the
software and is continued till the product is reengineered or deployed
to another platform. Maintenance is also done based on fixing the
problems reported, changing the interface with other software or
hardware enhancing the software.
From a proper analysis of positive points and constraints on the
component, it can be safely concluded that the product is a highly
efficient GUI based component. Thisapplication is working properly
and meeting to all user requirements. This component can be easily
plugged in many other systems.