THAKUR POLYTECHNIC
DIPLOMA IN COMPUTER ENGINEERING
SYCO B
SEMESTER 4 [2019-2020]
(GROUP 23)
SUBJECT: SOFTWARE ENGINEERING
112. ABHISHEK VISHWAKARMA
113. ASHISH VISHWAKARMA
114. PRITISH WANI
115. AKSH YADAV
116. ANKUSH YADAV
GUIDED BY: - MS. VAISHALI RANE
Maharashtra State Board of Technical Education
Certificate
This is to certify that GROUP 23 from Roll no 112 – 116 of Third Semester of
Diploma in Computer Engineering (CO) of institute, Thakur Polytechnic (CODE:
- 0522) has completed the micro-project satisfactorily in course Software
engineering (22413) for the Academic year 2019 to 2020 as prescribed in the
Curriculum.
Place: Enrolment No:
Date: Seat No:
Subject Teacher Head of the Department Principal
Seal of
Institution
ACKNOWLEDGEMENT
We would like to express our special thanks of gratitude to our institute Thakur
Polytechnic our principal Dr. S.M Ganechari, our head of the Department Ms.Vaishali
Rane and our subject teacher Ms. Vaishali Rane who gave us the opportunity to make
this micro project on the topic: Automated Time-Table Generator. This has greatly
helped us in expanding our core of knowledge. We are thankful to each other because
every one of us aided to complete this project within the limited frame of time.
PROPOSAL
Name of Micro-Project :- Automated time-table generator
1.0 Aim of the Micro-project
To develop a software for automated time-table generator.
2.0 Course Outcomes addressed
1. Select suitable Software Process model for software
development.
2. Prepare software requirement specifications.
3. Use Software modelling to create data designs.
4. Estimate size and cost of software product.
5. Apply project management and quality assurance principles
in software development.
3.0 Proposed Methodology
1. Writing of problem statement and scope of the project.
2. Choosing Appropriate software model.
3. Requirement Gathering.
4.0 Action Plan
Planned Name of
Sr. Details of Planned
Finish responsible
No Activity Start Date
Date team member
Abhishek
Vishwakarma
Proposal Ashish
1 of Micro 16/12/2019 24/12/2019 Vishwakarma
project Pritish Wani
Aksh Yadav
Ankush Yadav
Abhishek
Vishwakarma
Ashish
Problem
2. 07/01/2020 25/01/2020 Vishwakarma
Statement Pritish Wani
Aksh Yadav
Ankush Yadav
Software Abhishek
Requirem Vishwakarma
Ashish
ent
3. 06/02/2020 20/02/2020 Vishwakarma
Specificati Pritish Wani
on Aksh Yadav
(SRS) Ankush Yadav
Abhishek
Vishwakarma
Ashish
Use case
4. 24/02/2020 29/02/2020 Vishwakarma
diagram Pritish Wani
Aksh Yadav
Ankush Yadav
Abhishek
Vishwakarma
Ashish
Data flow
5. 02/03/2020 10/03/2020 Vishwakarma
diagram Pritish Wani
Aksh Yadav
Ankush Yadav
Abhishek
Vishwakarma
Micro Ashish
6. project 12/03/2020 19/03/2020 Vishwakarma
Report Pritish Wani
Aksh Yadav
Ankush Yadav
5.0 Resources Required
Sr. Name of
Specification Quantity
No Resource/material
Any
configuration
1. Personal Computer 1
with support of
4GB RAM
2. Microsoft Word Office 365 1
Minimum 32
3. Internet 1
Mbps
Microsoft
Windows or
4. Operating System 1
any other
higher
Roll no. of the team members:
Name of team members:
112. Abhishek Vishwakarma
113. Ashish Vishwakarma
114. Pritish Wani
115. Aksh Yadav
116. Ankush Yadav
Vaishali Rane
__________________
REPORT
1.0 Problem statement and scope:
Problem statement:
Detailed Problem Statement for Automated Timetable Generator our
Basic function is to create a Timetable for an institute including different
branches and Semester. The main problem that occurred during the project is to
create and maintain the databases of different utilities involved in this process.
The database contains the information about the various semester, subjects, lab,
teachers, etc so maintain such a large database is a big challenge for us. The
problem we face during our project is how the collision of two subjects or the
teachers can be avoided. Every project have some drawbacks. There is a chance
when the collision will occur when we generate more timetables for different
branches. So, these are some problem which we face in our project.
Scope:
The objective of the project is to create a web base timetable management
system to be used by any institute. It’s main function is to perform the basic
requirements of the college and to maintain the databases of subjects, branches,
semester more efficiently.
As it is a computer based system, the maintaince and working is
somehow difficult from the manual made of approach. Till now, the timetable
making process is manual work. So because of this the teacher has some
difficulty to work on this. They have to first login through their email id and
then they have to fill all the details then timetable will be generated. But we
have tried hard to make this system very user friendly and easy to understand.
As this is a computer based project, it is easier to fetch the data from the
database and remove the unwanted data by just clicking delete function button.
This project will limit the time and management system. The maintaince of this
computer based system is much easier and accurate than the existing manual
system. As this is computer based, the security features or somehow higher than
manual system.
In this system, there is less chance of mishandling of data because only
administrator will login through is I’d and password and upload or related data
and generate the timetable so there is no misuse of data.
Software Requirements Specification
For
Automated Time-Table Generator
Prepared by
SR NAME ROLL.NO EMAIL
no.
1. Abhishek Vishwakarma 112 [email protected]
2. Ashish Vishwakarma 113 [email protected]
3. Pritish Wani 114 [email protected]
4. Aksh Yadav 115 [email protected]
5. Ankush Yadav 116 [email protected]
Instructor : Vaishali Rane
Course : Computer Engineering
Lab section : Computer Lab 2
Teaching assistant : Siddharth Gupta
Date : 30/12/2019
Pg : 1/ 13
Contents
ABSTRACT ..............................................................................................................................3
Existing System: ........................................................................................................................3
Proposed System: .......................................................................................................................3
MODEL ....................................................................................................................................4
RUP Model (Rational Unified Process Model) .........................................................................4
Advantages of RUP Software Development..............................................................................4
Other Models .............................................................................................................................5
Waterfall model .........................................................................................................................5
Incremental model .....................................................................................................................5
RAD model ................................................................................................................................5
Prototype model .........................................................................................................................5
Spiral model ...............................................................................................................................6
FUNCTIONAL & NON-FUNCTIONAL REQUIREMENTS ............................................6
Functional Requirements: ..........................................................................................................6
Non-Functional Requirements: ..................................................................................................6
TESTING ..................................................................................................................................7
Unit Testing: ..............................................................................................................................7
Module Testing: .........................................................................................................................7
Sub-system Testing: ...................................................................................................................7
System Testing:..........................................................................................................................7
Acceptance Testing: ...................................................................................................................7
UML DIAGRAMS ...................................................................................................................8
ER Diagram ...............................................................................................................................8
Flow Diagram ............................................................................................................................8
User-case Diagram……………………………………………………………………………………………………………………….9
Data flow diagrams.......................................................................................................................10
Activity diagram………………………………………………………………………………..11
Class diagram……………………………………………………………………………………12
Time Line Chart............................................................................................................................13
Pg : 2/13
Automated Time-Table Generator
1. INTRODUCTION
The Automatic Timetable Generator is a Java based software used to generate timetable
automatically. Currently timetable is managed manually. It will help to manage all the
periods automatically and also will be helpful for faculty to get timetable in their phone by
using application. It will also manage timetable when any teacher is absent, late coming or
early going. Maximum and minimum workload for a Faculty for a day, week and month will
be specified for the efficient generation of timetable. By using this software users can apply
for leave by providing leave required date, reason and also with substitute faculty.When
selecting a faculty as substitute it allows to view timetable of that faculty for ensure that the
faculty is free at that particular period. Substitute can approve or reject request. Principal
can also view the request and send by faculty and can also view substitute response.
Principal can approve reject request.It is a comprehensive timetable management solutions
for colleges which help to overcome the challenges in manually setting the timetable. By
using this software it will be very easy for faculty to get timetable in their phones.
1.1 PURPOSE
Automatic Timetable is a java based software is used to generate timetable Automatically.
Will help you to manage all the periods Automatically and also will be helpful for faculty
who will get timetable in their phone as a notification. It will also manage timetable when
any teacher is absent is late coming and early going. Proposed system will help to generate
it automatically also helps to save time. There is no need for faculty to worry about period
details and maximum workload. By using this software user can apply for leave required
date, reason and also with substitute faculty. When selecting a faculty as substitute it allows
viewing timetable of that faculty for ensure that the faculty is free at that particular period.
Substitute can approved or reject request. Principal can also view the request send by
faculty can also view substitute response. Principal can approved\reject request. It is a
comprehensive timetable management solutions for Colleges which help to overcome the
challenges in current system.
1.2 SCOPE
The objective of the project is to create a web base timetable management system to be used
by any institute. It’s main function is to perform the basic requirements of the college and to
maintain the databases of subjects, branches, semester more efficiently.
Pg : 3/ 13
MODEL
RUP Model (Rational Unified Process Model)
For the implementation of the system the RUP Model (Rational Unified Process Model) is
used. Its goal is to ensure the production of the high-quality software that meets the needs
of its end users within a predictable schedule. It is easily customized and useful for web
based implementations.
RUP methodology has a highly flexible development path. It uses the some of the industry’s
best practices. These are known as six best practices of RUP methodology. The reasons why
we are using RUP model for developing this system are also these best practices.
Develop Iteratively: The software requirements specification (SRS) keeps on evolving
throughout the development process and loops are created to add them without affecting
the cost of development.
Manage Requirements: The business requirements documentation and project
management requirements need to be gathered properly from the user in order to reach the
targeted goal.
Use Components: The components of large project which are already tested and are in use
can be conveniently used in other projects. This reuse of components reduces the production
time.
Model Visually: Use of Unified modelling language (UML) facilitates the analysis
and design of various components. Diagrams and models are used to represent various
components and their interactions.
Verify Quality: Testing and implementing effective project quality management should be
a major part of each and every phase of the project from initiation to delivery (aka the
project management life cycle).
Control Changes: Synchronization of various parts of the system becomes more
challenging when the parts are being developed by various teams working from different
geographic locations on different development platforms. Hence special care should be
taken in this direction so that the changes can be controlled.
Pg : 4/ 13
Advantages of RUP Software Development
1. This is a complete methodology with an emphasis on accurate documentation
2. It is proactively able to resolve the project risks associated with the client's
evolving requirements requiring careful change request management
3. Less time is required for integration as the process of integration goes on
throughout the software development life cycle.
4. The development time required is less due to reuse of components.
Other Models
Waterfall model
The waterfall model can be used for the development of the system but we are not using it
because the requirements must be known at the start otherwise it would be a disaster as the
requirements are frozen before the designing of the system. In our system we need the
testing at every phase but in waterfall model there is only Big Bang testing which is done at
the end of the completion of all the phases.
Incremental model
The incremental model is not used by us just because the RUP (Rational Unified Process)
Model is the best version of Incremental and Iterative model as it contains all the best
features of both models. Incremental model is somehow costly as compared to RUP model
and when we are getting the best features of two models in one single model then why
would we not choose it?
RAD model
The reason we are not using this process model is that the requirements cannot be changed
at later stages as, if the requirements are not well understood at the start then it would be
very difficult. This process model, is no doubt for small scale projects like ours but work
force is needed as number of teams are working parallel and that can be risky and costly.
Prototype model
The prototype model is not used by us because the risk factors are very high in this model.
If our system is not accepted by the user then it will remain in an unending loop which will
cause a lot of financial drop.
Pg : 5/ 13
Spiral model
The spiral model is used by us in development our system as it is not suitable for low risk
systems. In this model, it is hard to define objective, verifiable milestones and doesn’t
work well for our type of smaller projects. Similarly, it can be a costly model to use and
risk analysis requires highly specific expertise.
FUNCTIONAL AND NON-FUNCTIONAL REQUIREMENTS :
Functional Requirements :
The major functional requirements of the system are as follows.
1. To classify the data on a single site
2. To implement an User interface on the system
3. User friendly front end design using Cascading Style Sheets.
4. Strong authentication while performing various operations
5. Java script validations and alerts where ever needed.
Non Functional Requirements :
1. The major non functional Requirements of the system areas follows
2. Secure access of confidential data (user's details). SSL can be used.
3. Better component design to get better performance at peak time
4. Flexible service based architecture will be highly desirable for future extertsion.
Pg : 6/ 13
TESTING :
At the end, the software testing is done to point out the defects and errors that were made
during the development phases. It’s essential since it makes sure of the Customer’s reliability
and their satisfaction in the system. Here we just mentioned that how the testing is related to
this system and in which way we have test the software? In our project we have used 5 types
of testing these are listed below.
Unit Testing: Unit testing where individual program units or object classes are tested. Here
by using this testing we have focused on testing the functionality of methods.
Module Testing: Where this is the combination of unit program is called module. Here we
tested the unit program (5-6 programs) is where the module programs have dependency.
Sub-system Testing: Then we combined some module for the Preliminary System Testing in
our Project.
System Testing: It is the combination of two or more sub-system and then it is tested. Here
we tested the Entire system as per the requirements.
Acceptance Testing: Normally this type of testing is done to verify if system meets the
customer specified requirements. After submitting the project to user, they test it and
determine whether to accept the system or not. It is the system testing performed by the
customer(s) to determine whether they should accept the delivery of the system.
Pg : 7/ 13
2.7 E.R DIAGRAM
2.8 FLOW DIAGRAM
Pg : 8/ 13
3.0 Use-case diagram:
Pg : 9/ 13
4.0 Data flow diagram:
Pg : 10/ 13
5.0 Activity Diagram:
Pg : 11/ 13
6.0 CLASS DIAGRAM :
Pg : 12/ 13
7.0 TIMELINE CHART :
Pg : 13/ 13
