MGV’s

M. S. G. ARTS, SCIENCE AND COMMERCE COLLEGE

(Affiliated to SavitribaiPhule Pune University, Pune)
Malegaon Camp

A Project Report

on

To Help Student After Registration Process

Project report submitted in partial fulfillment of the requirement for the award of the
degree of Bachelor of Science in Computer Science in
SavitribaiPhule Pune University

Submitted by

AhireYogitaBhagavan (Roll No. 26)

BhamareJagruti Sunil (Roll No. 29)

JadhavBhagyeshriNandu (Roll No. 30)

Under the guidance of

Dr. Amit D. Kasliwal

(Assistant Professor, Comp. Sci. Department)

 2021 - 2022

CERTIFICATE

This is to certify that, the project entitled To Help Student After

Registration Process submitted to Computer Science Department, is a

bona fide record of work done by Ahire Yogita B., Bhamare Jagruti S.,

Jadhav BhagyashriN., Roll No. 26 , 29 , 30 Uni. Seat No. _______ under

my supervision for the partial fulfillment of CS3611 – Project Course in T.

Y. B. Sc. (C. S.) during academic year 2021 - 2022.

 ACKNOWLEDGEMENT

We take this opportunity to thank all those openhanded persons who rendered

their full support to our work.

We express our gratitude to Principal Dr.D. F. Shirude for the cooperation

extended to the successful completion of the project. In addition, with a lot of

happiness, we are expressing gratitude to Mr. D. J. Deore, Head of the Computer

Science department, for his timely and kind help. Also, his inspiration up to the last

moment had made things possible in a planned manner. We also thank our teachers for

their guidance and for providing us with the most essential materials required for the

completion of this project. We are very thankful to our guide for his timely guidance.

Finally, we thank each and everyone who helped to complete our project work

with their cordial support.

Project Team Members

AhireYogitaBhagavan (Roll No. 26)

BhamareJagrutiSunil (Roll No. 29)

JadhavBhagyeshriNandu (Roll No. 30)

 INDEX

Title Page No

Abstract

1 Introduction to proposed System 1–2

a. Motivation

b. Problem Statement

c . Objective

d. Project scope

e. Limitations

2 System Analysis 3-4

a. Existing System

b. Scope And Limitations Of Existing System

c. Stokeholders

3 Requirement Analysis 4-7

a. FunctionalRequrements

b. Performance Requirements

c. Social Requirements

d. Data Collection

e. Software/ Hardware Specification

4 System Design 7 – 16

a. Data Dictionary

b. System Diagram
 1. Entity Relationship Diagram

2. Class Diagram

3. UseCase Diagram

4. Activity Diagram

5. Sequence Diagram

6. Component Diagram

7. Deployment Diagram

5 System Implemantation 17 - 26

a. User Input Interface

b. Output Screen

c. Reports

6 System Testing 27 – 35

a. Defining Test Plan

b. Implementing Testing Strategy

1.Unit Testing

2.Black Box Testing

3. Alpha Testing

7 Conclusion And Future Plans 33

8 Bibliography And Reference 34

 Abstract :

PROJECT TITLE :- Student Help After Registration System.

ABSTRACT :-

TO help student after registration process targetes for the college students Who
have no idea about the process of college after registration.

The goal of our system is to help the student information about their department . First
of all they have to register online then they can acess if free online from any where
.They do not need to go college and also need not any paperwork. And their time is also
save.It is a web base application, and student acess if from any device .

Project Development Specification :-

Fronted:- PHP(Version 7.4),HTML,CSS,BOOTSTRAP,JQuery.

Backend :-Postgresql(version 8)

PROJECT MEMBERS:-

1. BhagyashriNanduJadhav.(30)
2. AhireYogitaBhagavan.(26)
3. Jagruti Sunil Bhamare.(29)
 Introduction to Proposed System
In our proposed system students registers themselves on the portal . Another
advantage of the system is that it is very easy to students to finding the information
they need. The name of the teacher is added in the database and so students can
view the information about teacher whenever they want. Our proposed system has
several advantages

Ø User friendly interface

Ø Fast access to database

Ø Less error

Ø More Storage Capacity

Ø Search facility

Ø Web base application

The proposed System overcomes the problems in the existing system. Also
there is possibility of errors while entering the information.So we have tried to
implements a proposed system which is automated. In which all information
available to student online which was very difficult for student to getting
information in the manual .

Motivation :-

All the manual difficulties in searching the teachers in a school or college

have been rectified by implementing web base application. Student cannot get
information offline easily ,so we add the functionalities on the portal.

Problem Statement :-

Students face many problem to get information about perticular process .That
process is very time consuming and student get harassted.And find a particular
teacher for a particular process is very difficult.

Objective :- In this system student can get information for the next process easily
from the portal.Student can get information online.At the end of this project student.

1
Project Scope:-

Since this system will play a key role in the organization. The system gives us
all the necessary information about the teacher and the process that student want .
We can check the information of college and whenever required at times.

This system developed for linux platform. PHP is an Integrated Development

Environment that can be used for this system.

This s/w is used as a code generator and creating interface. This system
requires small database for keeping data. Therefore, PostgreSQL is used as the
database for this System.

Limitations:-

These system need internet if there not internet connection then this system will
not work.Our system requires mobilephone,laptop and tabs.If student are register
first then only doing these process.

2
System Analysis
Existing System

Information is getting manually in the existing system then student not get
proper information of the college.This will take the student some few seconds to
accomplish .

In existing system the process is very slow and time consuming . Students are
harrashted from this process.

In that system if any big university there is not easy to find teacher easily and
student no get information on time.

Scope And Limitations Of Existing System :-

The scope of existing system is not very effective student can not get
information easily .

The reason why this method less effective is that the data are not collected
completely .In manually there is very time consuming process .And if students
have to know any information they need to come college in that the process is very
time consuming.

Stackholders:-

Team Members :-

1. Ahire Yogita Bhagawan(26)

2. Bhamre Jagruti Sunil (29)
3. Jadhav Bhagyshri Nandu(30)
4. College.
5. Seniour college Student.

3
Requirement analysis

Functional Requirements :-

The functional requirements of the system are to the implement the solution for
finding the teacher details and route information in the large existing system.

1. Input / Output:

The students select the type of course and enter then information

about the teacher and process is get on them portal.

2. Processing:

The information regarding process details are retrieved from the database.

3. Storage Requirements:

The information will be retrieved from the database.

4. Control Requirements:

Alerts when any errors are there and when any of the field is not selected.

Performance Requirements:-

software's speed of response:-

Response Time measures the server response of every single transaction or

query.The time taken for one system node to respond to the request of another. It is
the time a system takes to reach a specific input until the process is over. Our system
give response very fast to the enduser.

Execution time is very fast of this system.System storage is large this system store
large data. storage capacity is more.

4
Social Requirements :-

These system is helpful for the students getting all information of the college . If any
problem occurs during the completing then they do not need to ask

anyone .And also the time of the students save.

Data Collection:-

To study any system the analyst needs to collect facts and all relevant
information. The facts when expressed in quantitative from termed as data.
The success of any project is depended upon the accuracy of available
data. Accurate information can be collected with the help of certain
methods/techniques.
We used four fact finding methods in our system analysis.

 Interview
 Questionnaire
 Record Review
 Observation

1. Interview:-

We used this technique frequently in the system analysis after

questionnaires. The interview were unstructured. We choose some students in
the colleges who were either decision maker or operator or uses some activity
related with the project. As we interviewed them many helped us to
understand all stages involved.

2. Questionnaire:-

We used this technique in the initial and final phases of our project. In the
initial phase we prepared some questionnaire to get some basic information
about the current system. Then we used the questionnaire to get some
numerical data that was required or missing after all the observation.

3. Record View:-

The information related to the system is published in the source

like computer, tablet, mobilephones , tabs etc…

5
 This record review helps the analyst to get valuable information about
the system and the organization.

4. Observation:-

While finding the facts we keenly observed all the activities and
finding tachers usage of files and document. Observation helped us in finding
out the actual way functioning apart from the ideal.

Software/Hardware Specification:

1. Hardware Requirements:-

 Standard color Monitor

 Standard Keyboard and Mouse

2. Software Requirements:-

1: Operating system: Linux

2. Software:

HTTP server 2.2 is recommended. Include in XAMPP window as front end

PHP.

A database server postgresqlsever 5.0 is recommenced.include

in XAMPP window as back end.

System design is the process of designing the elements of a system such as the
architecture, modules and components, the different interfaces of those components
and the data that goes through that system.

6
System Analysis is the process that decomposes a system into its component pieces
for the purpose of defining how well those components interact to accomplish the
set requirements.

The purpose of the System Design process is to provide sufficient detailed data and
information about the system and its system elements to enable the implementation
consistent with architectural l entities as defined in models and views of the system
architecture.

Elements of a System

Architecture - This is the conceptual model that defines the structure, behavior
and more views of a system. We can use flowcharts to represent and illustrate the
architecture.

Modules - This are components that handle one specific tasks in a system. A
combination of the modules make up the system

Components - This provides a particular function or group of related functions.

They are made up of modules.

Interfaces - This is the shared boundary across which the components of a the
system exchange information and relate.

Data - This the management of the information and data flow.

7
System Design :-

Data Dictionary

Student :

Field Data Type Size Constraint

Sprno Int 10 Primary key
Spass Text 20 Not Null
Sname Text 20 Not Null
Sad Text 20 Not Null
Sgmail Text 20 Not Null
Smobno Text 20 Not Null
Sclgid Text 20 Not Null

Course :

Field Data Type Size Constraint

cid Int 10 Primary Key
Cname Text 20 Not Null
Cqual Text 20 Not Null
Cqual Text 20 Not Null

Teacher :

Field Data Type Size Constraint

Tid Int 10 Primary key
Tname Text 20 Not Null
Tmobno Text 20 Not Null
Tgmail Text 20 Not Null

8
Work:

Field Data Type Size Constraint

Tid Int 10 Foren Key
cid Int 10 Foren Key

b. System Diagram

The Unified Modeling Language (UML) is used to specify, visualize, modify,

construct and document the artifacts of an object-oriented software-intensive system
under development. UML offers a standard way to visualize a system's architectural
blueprints, including elements such as:

Activities

Actors

Business processes

Database schemas

(Logical) components

Programming language statements

Reusable software components.

UML combines techniques from data modeling (entity relationship diagrams),

business modeling (work flows), object modeling, and component modeling It can
be used with all processes, throughout the software development life cycle, and
across different implementation technologies UML has synthesized the notations of
the Booch method, the Object-modeling technique (OMD) and Object-oriented
software engineering (OOSE) by fusing them into a single, common and widely
usable modaling language UML aims to be a standard modeling language which can
model concurrent and distributed systems UML is a de facto industry standard and
is evolving under the auspices of the Object Management Group (OMG)

9
ER Diagram :-

1 1
stud get register

sent
get

1
login teacher intro
search get

m M M

from

work M

10
 Class Diagram :- Teacher

Tid : number

Tname : String
Student
Tgmail : String
Userprno: number

help Tmobno : String

Spass : string

Sname : string
Inform()
Sadd : string

Smobno : string work

Sgmail : string

Sclgid : string sentCou Work

Tid : number
Course
Verification()
Cid : number
cid : number
Login()
cname : string
Viewteacher()
Help()
cqual : string

cdual : string informatin

coursedur()

11
Use Case :-

Teacher

student available

help

Work
search

login

12
Activity Diagram : - start

Student is register

Student enter login

prn and password

Invalid login password

N
Correct
login andY
password

Student successfully
login

Student gets teacher

information properly

13
Sequence Diagram:-

student Login screen teacher course

Click on login button get information

Course informationlogou

logout

14
 Component Diagram :-

student

encryption
student
Data acess

Student acess control

website
course encryption
student
Data acess

website of student acess control

teacher

Data acess

work

Data acess postgresql

15
 deployment Diagram :-

Admin/comp
uter postgresql
Web server

16
System Implemantation :-

17
18
19
20
21
22
23
24
SYSTEM TESTING

System design is the process of designing the elements of a system such as the
architecture, modules and components, the different interfaces of those components
and the data that goes through that system.

System Analysis is the process that decomposes a system into its component pieces
for the purpose of defining how well those components interact to accomplish the
set requirements.

The purpose of the System Design process is to provide sufficient detailed data and
information about the system and its system elements to enable the implementation
consistent with architectural entities as defined in models and views of the system
architecture.

Elements of a System Architecture –

This is the conceptual model that defines the structure, behavior and more views of a
system. We can use flowcharts to represent and illustrate the architecture. Modules -
This are components that handle one specific tasks in a system. A combination of the
modules make up the system. Components - This provides a particular function or
group of related functions. They are made up of modules.

Interfaces - This is the shared boundary across which the components of a the system
exchange information and relate. Data - This the management of the information and
data flow.

A Test Plan refers to a detailed document that catalogs the test strategy, objectives,
schedule, estimations, deadlines, and the resources required for completing that
particular project. Think of it as a blueprint for running the tests needed to ensure
the software is working properly – controlled by test managers.

A well-crafted test plan is a dynamic document that changes according to

progressions in the project and stays current at all times. It is the point of reference,
based on which testing activities are executed and coordinated among a QA team.

The test plan is also shared with Business Analysts, Project Managers, Dev teams,
and anyone else associated with the project, This mainly offers transparency into QA
activities so that all stakeholders know how the software will be tested.

25
The plan is built by QA managers or leads based on input from QA (and sometimes,
non-QA) team members. Creating it should not take more than 1/3rd of the time
allocated for the entire project.

Steps to Start Creating a Test Automation Strategy

Now that you understand the value, purpose, and look of a test automation strategy,
let’s dive into the actual steps to get started on one.

Step 1:

Define your high business value tests The first step is to define what’s most
important to test by defining what we call the “high business value tests” – ie, the
flows that could potentially cause the business to fail if they stopped working.
Consider Knight Capital Group, the trading company that went from fully
functional to belly up in just 45 minutes and lost $485 million due to the failure of a
single software book (ie, a high business value test that wasn’t considered). Be sure
to work with your business to understand what your high business value tests are
because it will allow you to understand if the solution you’re proposing fits your
critical scenarios. It will also help you demonstrate true business value with your
automation framework, which will dovetail nicely into the ROI conversations.

Step 2:

Identify your risk A key part of any test automation strategy is knowing what the
test first and what to test last. You should use a risk-based approach to determine
this testing automation priority. You can determine the risk, or priority, of each
thing you want to test by figuring out its business impact and adding that to the
probability of it failing. Obviously, the things with the highest business impact and
highest probability of failure should be highest on your priority list, while the things
with the lowest business impact and lowest probability of failure should be at the
bottom. This will also help quite a lot with the aforementioned testing squeeze and
knowing what you want to cut first.

Step 3:

Understand your technology, tools, and resources You need to understand how
your overall testing automation solution will affect your overall environment. Do
you have the proper accounts to run this? Do you have the proper environmental
access? Do you have the right libraries and APIs and other pieces you may need to
have your testing automation solution talk to your applications? You need to have a

26
robust working solution that you can easily build into your overall framework
without bogging anything down or creating broken or fragile tests.

How to select Automation Testing Tools?

Step 4: Make sure your data is good A lot of test automation projects fail due to data
failures. What if you could ensure the data is correct right at the start using another
script in your automation framework or by running pre-scripts to validate or load
the data, thereby saving you hours and hours of rewriting or redoing your tests? For
each release and big framework iteration, you should deeply examine how you’re
handling your data, how you’re storing your data, where your data is coming from,
what your retry logic is, and if you have to worry about masking or de-identifying
data.

Step 5:

Define your DevSecOps A lot of testers can now work directly with Jenkins servers
or other build-anddeploy tools, so you need to define that in your testing
automation strategy.

You need to ask:

• Where is the code stored?

• How are you deploying it?

• What environments are you running it on and are they safe?

• Are the libraries and open source code you’re using secure?

• You need to be doing some level of security scanning and have a process for how
that scanning is done for your test automation framework.

Step 6:

Consider your testing environment There are a lot of things to document around
environmental conditions. Do you need certain tokens or VPNs? Do you need a
launch box? How does that work and where does that live and who is responsible
for it? How is the patching done on those systems? You need to document all of this,
as it will also help greatly with onboarding new testers to your organization and
getting the logins set up. In short, you need to understand where your code is
running at all times and have it fully documented.

27
Step 7:

Tag your tests Having the ability to tag your tests and group them logically will
allow you to say, “It doesn’t matter whether we have 20,000 or 50,000 test
automation scripts because I know these are for my check-out, these are for my
login, these are for smoke tests, etc…” If you don’t have those tags in place, you may
be left doing a lot of groundwork trying to figure out the purpose of certain tests and
figuring out which tests to run. Set a tagging agreement right up front to ensure
consisten.

Step 8:

Look for testing efficiencies As you do more and more testing, you can start to apply
the same testing logic in different areas to create efficiencies and shave off testing
time and resources. For example, if you’re doing the same thing with the unit
testing, manual testing, and automation testing, you probably don’t need three
people running the exact same test. You can save a lot of time by fully
understanding your overall testing automation strategy, all the way from the unit
test down to the UI test.

Step 9:

Embrace agile tools Embrace your agile and DevOps tools and really work on your
documentation. Your testing automation strategy should become a living document
that’s updated and reviewed each sprint to make sure you’re sticking to your visions
and goals. Embrace this process and use cloud-based tools such as GitHub to make it
a success. That said, you don’t need to document everything. You should, however,
have regular check-ins and micro-strategy sessions.

i. Unit Testing

Unit testing involves the testing of each unit or an individual component of the
software application. It is the first level of functional testing. The aim behind unit
testing is to validate unit components with its performance.

A unit is a single testable part of a software system and tested during the
development phase of the application software.

The purpose of unit testing is to test the correctness of isolated code. A unit
component is an individual function or code of the application. White box testing
approach used for unit testing and usually done by the developers.

28
Whenever the application is ready and given to the Test engineer, he/she will start
checking every component of the module or module of the application
independently or one by one, and this process is known as Unit testing
orcomponents testing.

ii. Black Box Testing

Black box testing is a type of software testing in which the functionality of the
software is not known. The testing is done without the internal knowledge of the
products.

Black box testing can be done in following ways:

1. Syntax Driven Testing – This type of testing is applied to systems that can be
syntactically represented by some language. For example- compilers,language that
can be represented by context free grammar. In this, the test cases are generated so
that each grammar rule is used at least once.

2. Equivalence partitioning– It is often seen that many type of inputs work

similarly so instead of giving all of them separately we can group them together and
test only one input of each group. The idea is to partition the input domain of the
system into a number of equivalence classes such that each member of class works in
a similar way, i.e., if a test case in one class results in some error, other members of
class would also result into same error.

The technique involves two steps:

Identification of equivalence class – Partition any input domain into minimum two
sets: valid values and invalid values. For example, if the valid range is 0 to 100 then
select one valid input like 49 and one invalid like 104. Generating test cases – (i) To
each valid and invalid class of input assign unique identification number. (ii) Write
test case covering all valid and invalid test case considering that no two invalid
inputs mask each other.

To calculate the square root of a number, the equivalence classes will be:

29
(a) Valid inputs:

Whole number which is a perfect square- output will be an integer. Whole

number which is not a perfect square- output will be decimal number. Positive
decimals

(b) Invalid inputs:

Negative numbers(integer or decimal). Characters other that numbers like

“a”,”!”,”;”,etc.

3. Boundary value analysis –

4. Boundaries are very good places for errors to occur. Hence if test cases are
designed for boundary values of input domain then the efficiency of testing
improves and probability of finding errors also increase. For example – If valid range
is 10 to 100 then test for 10,100 also apart from valid and invalid inputs.

4. Cause effect Graphing– This technique establishes relationship between

logical input called causes with corresponding actions called effect. The causes and
effects are represented using Boolean graphs. The following steps are followed:

Identify inputs (causes) and outputs (effect). Develop cause effect graph. Transform
the graph into decision table.

Convert decision table rules to test cases.

iii. White Box Testing

White box testing techniques analyze the internal structures the used data structures,
internal design, code structure and the working of the software rather than just the
functionality as in black box testing. It is also called glass box testing or clear box
testing or structural testing.

Working process of white box testing:

Input: Requirements, Functional specifications, design documents, source code.

Processing:

30
Performing risk analysis for guiding through the entire process.

Proper test planning: Designing test cases so as to cover entire code. Execute rinse-
repeat until error-free software is reached. Also, the results are

Output: Preparing final report of the entire testing process. Testing techniques:

Statement coverage: In this technique, the aim is to traverse all statement at least
once. Hence, each line of code is tested. In case of a flowchart, every node must be
traversed at least once. Since all lines of code are covered, helps in pointing out
faulty code.

iv. Alpha Testing

Alpha Testing is a type of software testing performed to identify bugs before

releasing the product to real users or to the public. Alpha Testing is one of the user
acceptance testing.

This is referred to as an alpha testing only because it is done early on, near the end of
the development of the software. Alpha testing is commonly performed by
homestead software engineers or quality assurance staffs. It is the last testing stage
before the software is released into the real world. Following are the objectives:

The objective of alpha testing is to refine the software product by finding the bugs
that were not discovered during the previous tests.

The objective of alpha testing is to refine the software product by fixing the bugs that
were not discovered during the previous tests.

The objective of alpha testing is to involve customer deep into the process of
development.

The objective of alpha testing is to give better insight into the software’s reliability at
the early stages of development. Alpha Testing Process:

• Review the design specification and functional requirements.

• Develop comprehensive test cases and test plan.

• Execute test plan

• Log defects

• Retest once the issues have been fixed

31
CONCLUSION & FUTURE PLAN
In conclusion, project management software is a crucial tool in developing a project
and thus every college should implement in it in their system. Project managers also
need to takeadvantage of the effectiveness of project management software to ensure
that the project they arecarrying out become successful. The employees and other
stakeholders who are assigned so tasksshould also utilize the software in order to
complete their tasks on or before the set deadlines. IT Pro administrationAll
operational maintenance

is handled through the ProjectOnline service. You no longer have to commit IT

resources to tasks such as updates,disaster recovery, and maintenance. Also,
preventive maintenance scripts are run on yourdatabases to prevent problems before
they happen. EasystartupThere are no upfront infrastructure costs and users are on
a simple peruser licensing basis.

32
Biography And references:-

i. Websites :
ii. http://www.google.com http://www.wikipedia.org
http://www.oracle.com http://www.spring.io
http://www.apache.org http://h2database.com
http://www.vaadin.com

33