Vous êtes sur la page 1sur 17



Web Portal for GDGRDC

[Courese Name: PROJECT WORK]

[Course Code: CAP3501/ITL3501]

Submitted by: Submitted to: Dr Sakshi Babbar,

Nitin Gera, BCA, 160020212014 Associate Prof,Department of
Ankit kumar,BSC.IT,160020213001 Computer Science and Engineering
Sandeep RawatBSC.IT,160020213004 Dr Ganga Sharma, Assistant Prof,
Abhishek,BCA,160020212002 Department of Computer Science
and Engineering

Department of Computer Science and Engineering,

School of Engineering, G D Goenka University
Nov, 2018

I hereby declare that the project work entitled “Web portal for GDGRDC”
submitted to the GD GOENKA UNIVERSITY, is a record of an original work
done by us under the guidance of Dr Sakshi Babbar and Dr Ganga Sharma.

Nitin Gera 160020212014

Sandeep Rawat 160020213004
Ankit Kumar 160020213001
Abhiskek 160020212002

KUMAR students of GD GOENKA UNIVERSITY has taken this project on
“Web portal of GDGRDC”. The work for preparing the project has been carried
out by the students in partial fulfilment of the requirement, under my supervision
& guidance.

Dr Sakshi Babbar Dr.Ganga Sharma

Associate Professor Assistant Professor


This project work has been an enriching source for me. It helped me to enhance my knowledge
and learn new things which I am sure will be a lot of importance to my career. I sincerely thank
my faculty mentor, Dr. Ganga Sharma and Dr. Sakshi Babbar for her continuous guidance and
encouragement in carrying out this project work. I am thankful they have been a constant source
of advice, motivation and inspiration. I am also thankful for giving suggestions and
encouragement throughout the project work.
I would here by, make most of the opportunity by expressing my sincere thanks to all the
faculty members whose teachings gave me conceptual understanding and clarity in
comprehension. I offer my sincere thanks and humble regards to The GD Goenka university,
for imparting me very valuable education.

I perceive this opportunity as a big milestone in my career development. I will strive to use
gained skills and knowledge in the best possible way, and I will continue to work on their
improvement, in order to attain desired career objectives.


S.NO. CONTENT Page Number

1. Introduction and problem background 6

2. Problem Statement 7

3. Requirement Analysis 8

4. Detailed Design 12

5. Implementation 13

6. Conclusion 15

7. Data Tables 16

8. References 17

1. Introduction and Problem Background

Research and development refer to innovative activities undertaken by corporations or

governments in developing new services or products, or improving existing services or
products Research and development constitutes the first stage of development of a potential
new service or the production process.
R&D activities differ from institution to institution. This R & D web portal gives additional
feature for the academic. R&D differs from the vast majority of corporate activities in that it is
not intended to yield immediate profit, and generally carries greater risk and an uncertain return
on investment. This R&D Web Portal manages all the work related to the research papers
within the different schools of the university.

2. Problem Statement
The project aims to develop a web portal based on the work processes of GDGRDC.
The application part of the portal will provide access to various databases maintained
by GDGRDC like publication database etc. It will help in maintaining the performance
tracker database for various schools/departments and will provide targeted information
for different users of the portal. The project will follow the basic project development
lifecycle consisting of planning, analysis, design and implementation. Tools and
technologies to be used will be identified during the analysis phase while pinning down
on requirements.

3. Requirements Analysis

3.1 Software Requirements Specification (SRS)

A Software Requirements Specification (SRS) is a complete description of the

behavior of the system to be developed. It includes a set of use cases that describe all
the interactions the users will have with the software. Use cases are also known as
functional requirements. In addition to use cases, the SRS also contains non-functional
(or supplementary) requirements. Non-functional requirements are requirements
which impose constraints on the design or implementation (such as performance
engineering requirements, quality standards, or design constraints).

SRS for Web Portal for GDGRDC

1. GENERAL DESCRIPTION – GDGRDC is the System for managing the records of the
Research and Development activities of the university (Students and Faculty).

1.1 Purpose – The purpose for developing this type of Web Portal or introducing this
GDGRDC Portal is to facilitate everyone who is concerned with the university.

1.2 Scope – The scope of this project is global i.e. it should be able to be accessed from
anywhere through internet i.e. registered users must be able to login to their accounts by
directly accessing the university’s website and then signing in with their username and
password anytime and anywhere.

1.3 Abbreviation – GDGRDC G D Goenka Research and Development Center.

1.4 Overview – As the GDGRDC is able to have a user interface. It should have a drop down
boxes and if we drag mouse on any control at our welcome screen information regarding that
the control should be displayed. Help menu should be there. As a Faculty it should provide
them to upload the various Research Paper’s details. As a developer it should make a user
interface which is user friendly. He should make the GDGRDC as simple as he can.


2.1 Product Perspective –This Portal should be able to provide a basic and easy interface
for submitting and fetching the information i.e. it should be able to remove the
communication gaps between faculties. It should be compatible with all the operating

2.2 Product Functions - The following are the product functions of the GDGRDC:

• The GDGRDC login box should on the official website of the university.
• The password field should be secured.
• After signing in all updates and new announcements for users should be displayed.

• By clicking on the dropdown box of the options the user should be able to view
progress reports and results.
• User should be able to change the passwords.
• Records can be printout.

2.3 User Characteristics – A user can only have his/her specific username so he/she can

2.4 Use case – A use case is a methodology used in system analysis to identify, clarify, and
organize system requirements. The use case is made up of a set of possible sequences of
interactions between systems and users in a particular environment and related to a particular

2.5 Class Diagram – A class diagram is an illustration of the relationships and source
code dependencies among classes in the Unified Modeling Language (UML). In this context,
a class defines the methods and variables in an object, which is a specific entity in a program
or the unit of code representing that entity.

2.6 General Constraints –Server capacity is how many users can access or can be online at
once. More is the number of users more will be the network traffic and hence the server comes
in a down state. Personal firewall and updating is a tough task, it should be such that it should
not block the network traffic, making the system slower. Firewall of the GDGRDC should
not collide with the firewall of the user system.

2.7 Assumptions and Dependencies – GDGRDC should work even at when the network
traffic is high. Server should have a power backup as well as a database backup. The
GDGRDC should be compatible with most of the operating systems i.e. previous and latest


3.1 External Interface Required

3.1.1 User Interfaces – The external users are the faculties of the university. The faculty can
have an access to their accounts for their Research and Development activities. The concerned
faculty have also an account to access their account for uploading documents.

3.1.2 Hardware Interfaces – The external hardware interface used for accessing the UMS is
the personal computers of the teachers and the students. The PCs may be laptops with wireless
LAN as the internet connections provided will be wireless.

3.1.3 Software Interfaces – The Operating Systems can be any version of Windows, Linux,
Unix or Mac which supports TCP/IP protocols.

3.1.4 Communication Interfaces – The communication interface is a local area network

through wireless network routers.

3.2 Performance Requirements – The PCs used must be at least Pentium 4 machines so that
they can give optimum performance of the product.

3.3 Design Constraints – The constraints at the designing time are that the needs of the
university concerned faculty and the faculty may keep on changing so the designers must
keep this in view and design the product in this way that it is easily updatable.

3.4 Attributes – The following are the attributes of this Web Portal:

• It should be equipped with current and archive database.

• All records can easily be updated.
• It should facilitate faculty with updating his/her account, downloading or uploading
R&D documents from anywhere.

3.5 Other Requirements – The software is such that as the time goes by the need of the
university management, faculty may keep on changing thus it is made to change from time to

3.2 Hardware/ Software Requirements

Hardware: Computer System with 64-bit OS (windows 10) ,8GB RAM ,Intel(R) Core (TM)
i7 -6700 CPU @3.40GHz

3.3 Use Case Diagram

4. Detailed Design

4.1 System Design

4.1.1 Class Diagram

5. Implementation

In a nutshell, this Project work has been an excellent and rewarding experience. We can
conclude that there have been a lot we have learnt from our work. Needless to say, the technical
aspects of the work We’ve done are not flawless and could be improved provided enough time.

We learnt the real meaning of teamwork, punctuality, work compilation, authority and
responsibility during our projects. We built a great skill of working and coordinating with team
members and gave my best to the work allotted to me. We gained technical, as well as soft
skills, which are very important in every domain of life.

7. Data Tables

8. References