PROJECT REPORT

ON
( PEHLAY AKSHAR )

SUBMITTED IN PARTIAL FULFILMENT OF REQUIREMENT FOR

THE AWARD OF DEGREE OF
MASTER OF COMPUTER APPLICATION (MCA)
UNIVERSITY OF MUMBAI
2022-2023

SUBMITTED BY
Ms. SMITA JAILKAR
Roll No: MC2122050

UNDER THE GUIDANCE OF

PROF. MAHESH MAHAJAN

DEPARTMENT OF MASTER OF COMPUTER APPLICATION

ASM’s Institute of Management & Computer Studies, Thane
Batch 2021-2023
Clearance Certificate
Internship Certificate
 ACKNOWLEDGEMENT

Project development requires commitment from all the people who are
involved in it. And also, I would like to share the credit for the success of my
project with all the people who extended their valuable support to me.
I am grateful to my project guide Mrs. Pooja Danke, Project Head, who
helped me to schedule my project and taught me practically systematic way
of developing a project. I am immensely thankful for the patience with which
she stood by me till the end of my project.

As well as our Managing Director of Igmite Solutions Pvt LTD. Mr.

Makarand Deshpande Who gave me the golden opportunity to do this
wonderful live project on the topic PEHLAY AKSHAR which also helped
me in doing a lot of Research and I came to know about so many new things
I am really thankful to them.

Smita Jailkar
 INSTITUTE OF MANAGEMENT & COMPUTER
STUDIES
(IMCOST)

Certificate of Approval
This is to certify that the project report titled
“PEHLAY AKSHAR”
Is a Bonafede record of the work done by
Ms. Smita Jailkar
Under the Guidance of
Prof. Mahesh Mahajan

Internal Guide Course Coordinator

Name & Sign Name & Sign

Date: Date:
 Table of Content

Sr. No Topic Page No.

1. INTRODUCTION 1

1.1 Synopsis of the project 2

1.2 Objective & Scope of Project 3
1.3 Problem Definition 5
1.4 Theoretical Background 6
2. SYSTEM ANALYSIS 8

2.1 Feasibility Study 9

2.2 Cost Benefit Analysis 10
3. SYSTEM DESIGN 11

3.1 Software Requirement Specification 12

3.2 Methodologies Adapted 13
3.3 Detailed life Cycle of the Project 14
3.3.1 Modules 16
3.3.2 Object Oriented Analysis & Design Diagrams 17
3.3.2.1 UML Diagrams 18
3.3.4 Database Tables 25
3.3.4 ER Diagram 32
3.3.5 I/O Screen Layouts 33
4. TESTING 45

4.1 Methodologies used for Testing 46

4.2 Types of Testing used to test Portal 47
4.3 Test Cases 51
4.4 Test Report 55
5. SYSTEM IMPLEMENTATION 56

5.1 Hardware required at Client side 57

5.2 Software required at Client side 57
5.3 Testing done as End User 58
6. SYSTEM MAINTANANCE AND EVALUATION 59

6.1 Maintenance 60
6.2 Evaluation 61
7. USER/OPERATIONAL MANUA 62

7.1 Security Aspects, Access Rights 63

7.2 Backup & Recovery 64
8. FUTURE ENHANCEMENTS 65

9. LIMITATIONS 67

10. CONCLUSION 69

11. BIBLIOGRAPHY 71
CHAPTER 1 INTRODUCTION

1
1.1 Synopsis of the project:

1.1.1 About the Organization:

Pehlay Akshar is running an initiative to train and up skill the teachers to improve the
overall quality and effectiveness of education in government schools. Pehlay Akshar
trainings are conducted thrice a year for a large group of teachers. The aspect that sets
these trainings apart from other regular teacher trainings is that we discuss unusual
ideological concepts in a very interactive and participative way so as to ensure we create
a behavioral change in the teachers. The trainings are followed up by consistent weekly
coaching/ psychological counseling sessions to further facilitate the internalization and
implementation of the learning. Our Facilitators training coaches visit each teacher on a
weekly basis to discuss the new techniques that are utilized in the classroom to make the
overall classroom management better by motivating, appreciating and engaging the
students in learning activity. The Facilitators discussions among teachers group so as to
bring out the best teaching practices among them. The training coaches also help the
teachers in resolving numerous issues that they face with their students. The interactions
are made in groups so as to foster better relations between teachers and create cohorts
amongst themselves that are safe spaces for learning and sharing. To manage the Pehlay
Akshar Training initiative we are looking for a digital support which will provide the
certain functionalities. The solution is aimed at helping Teachers, Facilitators, Location
Managers and Program Leads.

For more information on Pehlay Akshar Visit

http://www.pehlayakshar.org/

2
 1.1.2 About the Project:

Pehla Akshr Project is based on teachers student and Admin. Pehla Akshar project use for
student teaching and teacher training. Pehla Akshr is a running Live Project. Pehla Akshar is have
Google Play Store App also for download and using daily in some school by teacher or student.

1.2 Objective & Scope of Project:

Objective

 To manager this initiative and better involvement of teachers, PA Foundation considered

a software solution.

 The objective of the "Pehlay Akshar" project is to improve teacher involvement and
enhance the management of educational programs. The project aims to achieve this by
implementing a software solution that includes a mobile app for field teams and a web-
based application for program administration and management. The primary goal is to
streamline program activities, capture detailed information about the activities, track
progress, and generate reports for initiative leaders..

3
 Scope

Scope of this project has been identified as follows:

The scope of the "Pehlay Akshar" project initially includes the development and implementation of a
mobile app for the field team. This app will allow the team to manage the program smoothly and
efficiently. It will enable them to capture activity details, such as attendance, lesson plans, and
assessments. The app will also provide a means of communication and collaboration among the field
team members.

In addition to the mobile app, the project scope encompasses the creation of a web-based application.
This application will serve as the administrative and management platform for the program. It will
provide features to track the progress of various initiatives, generate reports, and facilitate effective
communication between the field team, program leaders, and other stakeholders.

As the project progresses, the scope expands to include additional functionalities that cater to the
needs of students. This may involve incorporating various classroom activity sections within the
software solution to enhance student engagement and participation. Additionally, the project scope
may include the integration of learning management system (LMS) modules to provide a
comprehensive educational platform.

The scope of the project also involves continuous improvement and adaptation based on feedback
and evolving requirements. It aims to create a scalable and flexible software solution that can
accommodate future enhancements and modifications as needed.

Overall, the scope of the "Pehlay Akshar" project encompasses the development and implementation
of a mobile app, web-based application, and associated functionalities to improve teacher
involvement, program management, and student engagement in educational initiatives.

4
 1.3 Problem DefinitionExisting System
(PEHLAY AKSHAR) is a systematic approach to do a CURD Create Update Delete on the
Content management system capture,

Store, Process & Retrieve division wise land related documents at tenure level.

Proposed System

 The proposed system is broken down into two sections:

 the goals of the redesign

 the functionality that must be added to the new site to meet these goals.

 The primary objectives of Pehlay Akshar redesign are migrating to a web

enabled system, improving navigation paths on the front end of the site, and
implementing a responsive and modern design

Salient Features of Proposed Website

 Content Management System

 Timely report of data

 Notice Generation

 Migrating data from RDBMS data to MYSQL database

5
1.4 Theoretical Background:

1.4.1 Overview of Front End:

Angular js
AngularJS is a structured, JavaScript framework used for dynamic one-page applications.
Being a framework it uses code templates written in HTML in order to perform particular
function or command. The data binding and dependency functionalities of Angular JS
saves time invested in writing lengthy codes. All these features are packaged in a browser
that makes it a suitable server technology.
There is a considerable difference between the Static documents and dynamic
applications. Dynamic applications typically use a library and a framework that supports
creating web apps. While the library contains a number of functions used to perform
certain operations, framework automatically takes the data and calls the functions when
needed. However Angular JS creates new HTML constructs that eventually eliminates
this mismatch effectively. It creates new syntax with the help of directives.

1.4.2 Overview of Back End:

MySQL
MySQL is a very popular open-source relational database management system
(RDBMS).
Database Management is the most important part when you have humungous data
around you. MySQL is one of the most famous Relational Database to store & handle
your data.

 Database Management System & Types of DBMS

A Database Management System (DBMS) is a software application that interacts with
the user, applications and the database itself to capture and analyze data. The data stored
in the database can be modified, retrieved and deleted, and can be of any type like
strings, numbers, images etc.

6
Apache 2

Introduction

Apache HTTP Server is a free and open-source web server that delivers web content through the
internet. It is commonly referred to as Apache and after development, it quickly became the most
popular HTTP client on the web. It’s widely thought that Apache gets its name from its development
history and process of improvement through applied patches and modules but that was corrected back
in 2000. It was revealed that the name originated from the respect of the Native American tribe for its
resiliency and durability.

Now, before we get too in depth on Apache, we should first go over what a web application is and the
standard architecture usually found in web apps.

How does Apache Web Server Work?

Apache functions as a way to communicate over networks from client to server using the TCP/IP
protocol. Apache can be used for a wide variety of protocols, but the most common is HTTP/S. HTTP/S
or Hyper Text Transfer Protocol (S stands for Secure) is one of the main protocols on the web, and the
one protocol Apache is most known for.

HTTP/S is used to define how messages are formatted and transmitted across the web, with instructions
for browsers and servers on how to respond to various requests and commands. Hypertext Transfer
Protocol Secure is usually through port 443 with the unsecured protocol being through port 80.

The Apache server is configured via config files in which modules are used to control its behavior. By
default, Apache listens to the IP addresses configured in its config files that are being requested. This
is where one of Apaches many strengths come into play.

7
CHAPTER 2: SYSTEM ANALYSIS

8
2.1 Feasibility Study

2.1.1 Technical Feasibility

It deals with Hardware and Software requirements.

The technical feasibility issues raised during stage of investigation includes:

 Is the software running properly on windows/Linux operating system?

 Hardware requirement.

 We analyse the technical and capabilities of the software development team members.

 We determine whether the relevant technology is stable and established.

 We ascertain that the technology chosen for software development has large number of user
so that they can be consulted when problems arise, or when improvements are required.

2.1.2 Economic Feasibility

This feasibility study present tangible and intangible benefits by comparing the development and
operational cost.

The technique of cost benefit analysis is often used as a basis for assessing economic feasibility.

2.1.3 Operational Feasibility

 Operational feasibility is to gain an understanding of whether the proposed system will

likely to solve the business problems, or take advantage of the opportunities or not.
 The result of our operational feasibility Study clearly outline that the proposed system is
operationally workable and conveniently solves our problems.

9
2.2 Cost Benefit Analysis

Economic feasibility determines whether there are sufficient benefits in creating to make the cost
acceptable, or is the cost of the system too high.

As this signifies cost-benefit analysis and savings.

On the behalf of the cost-benefit analysis, the proposed system is feasible and is economical
regarding its pre-assumed cost for making a system.

As we know that the system development costs are usually one-time costs that will not recur after
the project has been completed.

10
CHAPTER 3: SYSTEM DESIGN

11
 3.1 Software Requirement Specification:

3.1.1 Introduction:

CPU : 2 vCPUs

Disk Space : 10 GB of HDD

Processor : Dual Core or higher

RAM : 4 GB

3.1.2 Selection of Technology/Specific Requirement:

Software to be used:

Microsoft Edge release 84, Google Chrome release 80, Mozilla

Browser :
Firefox release 73 and above on client.

Application Server : Apache 2.4.43

Technology : Angular js, dot net core

Database Server : MySQL version 5.7.26

Tools to be used:

Database Server : MySQL version 5.7.26

IDE : Visual studio , VS code

Application Server : Apache 2.4.43

12
 3.1 Methodologies Adapted:

The methodology adapted for software development is Spiral Model. The spiral model combines
the idea of iterative development with the systematic, controlled aspects of the waterfall model.

This Spiral model is a combination of iterative development process model and sequential linear
development model i.e. the waterfall model with a very high emphasis on risk analysis.

3.2 Detailed life Cycle of the Project:

Software Development Life Cycle (SDLC)

The following approach is used to design this system, which is called “Spiral Model” or “Meta
Model”. Spiral Model is a combination of a waterfall model and iterative model. Each phase in
spiral model begins with a design goal and ends with the client reviewing the progress.

Advantages of using Spiral Model

The advantage of spiral lifecycle model is that it allows elements of the product to be added in,
when they become available or known. This assures that there is no conflict with previous
requirements and design.

This method is consistent with approaches that have multiple software builds and releases which
allows making an orderly transition to a maintenance activity. Another positive aspect of this
method is that the spiral model forces an early user involvement in the system development
effort.

Changing requirements can be accommodated. Allows extensive use of prototypes.

Requirements can be captured more accurately. Users see the system early.

13
 Spiral Model – Design
The following illustration is a representation of the Spiral Model, listing the activities in each

Phase-
The spiral model has four phases. A software project repeatedly passes through these phases
in iterations called Spirals.

Identification-

This phase starts with gathering the business requirements in the baseline spiral. In the
subsequent spirals as the product matures, identification of system requirements, subsystem
requirements and unit requirements are all done in this phase.

Design-
The Design phase starts with the conceptual design in the baseline spiral and involvesarchitectural
design, logical design of modules, physical product design and the final design inthe subsequent spirals.

14
Construct or Build

The Construct phase refers to production of the actual software product at every spiral.
In the baseline spiral, when the product is just thought of and the design is being
developed a POC (Proof of Concept) is developed in this phase to get customer
feedback.

Then in the subsequent spirals with higher clarity on requirements and design details a
working model of the software called build is produced with a version number. These
builds are sent tothe customer for feedback.

Evaluation and Risk Analysis

Risk Analysis includes identifying, estimating and monitoring the technical feasibility
and management risks, such as schedule slippage and cost overrun. After testing the
build, at the end of first iteration, the customer evaluates the software and provides
feedback.

15
 3.3.1 Modules:

Admin Module:

This module provide a whole admin side functionality.

Admin Module add all the content or a any document for the students and teachers.

Content Management System Using Admin Module Uses to add the all resources, content or a
document.

 Admin Module add :

Resources

Lesson Plan

Class Room Activity

Worksheet

Assessment

Teacher Module:

In the Teacher module Teacher only have to watch a module or a content of the Admin which
updated in the Pehlay Akshar Application.

Teacher Module done with the Content management system present in the see uploaded
document .

Student Module:

In the Pehlay Akshar Project Which Based on the Content Management system.

In this Student Module student are login or a register and watch their session or a lesson plan,
assessment or a daily updated videos watch for study.

16
3.3.2 Object Oriented Analysis & Design Diagrams:

Object Oriented Analysis:

 Object-oriented analysis and design (OOAD) are a software engineering

approach that models a system as a group of interacting objects.

 Each object represents some entity of interest in the system being modelled,
and is characterized by its class, its state (data elements), and its behaviour.

 Various models can be created to show the static structure, dynamic behaviour,
and run-time deployment of these collaborating objects. There are a number of
different notations for representing these models, such as the Unified
Modelling Language (UML).

 Object-oriented analysis (OOA) is the process of analysing a task (also

known asa problem domain) to develop a conceptual model that can then be
used to complete the task.

 A typical OOA model would describe computer software that could be used to
satisfy a set of customer-defined requirements.

17
 3.3.2.1 UML Diagrams:
1) Pehlay Akshar Use Case Diagram

Interaction Diagram’s

Sequence Diagram

18
Sequence Diagram for Login

Sequence Diagram for Admin

19
Sequence Diagram for Student

Sequence Diagram for Teacher

20
Activity Diagrams

21
Activity Diagram for Admin

22
 Data Flow Diagrams:
Level 0: Data Flow Diagram of Pehlay Akshar

Level 2: Data Flow Diagram for Admin

23
Class Diagram
Class Diagram for Admin

24
3.3.4 Database Tables

25
26
27
28
29
30
31
3.3.5 ER Diagram

32
 3.3.6 I/O Screen Layouts
Screenshots
5.1 Steps involving for starting the project
1. Open browser by double clicking Google Chrome or Mozilla Firefox. The
icons for the same will be present on desktop or on Task bar.
2. Enter http://pehlayakshar.igmite.in in the address bar of the browser. The
following screen would appear.

Then in next step

33
 Login The Admin Dashboard open

Then the clicking on location foe adding a location:

34
Then click on Program which have to add or update for student and a teacher

Then click on school for showing list of all school

35
Then open teacher to add teacher or show a teacher list

Then that click the ward for the adding a Ward

36
Then the click on cohort for adding a cohort list

Now we want to download a data by download a config file in the clicking on the
download button with show the popup message also of file downloaded or not

37
Then clicking on program location mapping its show a program mapping location
list

Then show video list for adding a video for the teacher or a student as well as
motivation video also

38
On its click on content then open a student content list for which admin add a
content for a student for study material.

Now in this also show a content of the all of the data

39
In that show a quize of the student which student have to do for a study purpose

Session training list shows a list of the traing session of the teacher which done the
traning or not to done training

40
Category list shows a list of all category In the Application by Admin add or
updated a category

In that have the access control of the list add or update for the content

41
In that show a sub category of the student

42
Byline list show in th click on byline button item

In that we have updated a content response list of the content

43
In that category list admin add by APi Call to get the list of version updated in
the column

44
CHAPTER 4 TESTING

45
4.1 Methodologies used for Testing

In a software project, errors can be injected at any stage during development. Because
code isthe only product that can be executed frequently & whose actual behaviour can
be observed, testing is the phase where the remaining errors from all the previous
phases must be detected. Testing performs a critical role for quality assurance & for
ensuring the reliability of software. During testing, the program to be tested is executed,
with a set of test cases, & the output of the program for the test cases is evaluated to
determine if the program is performing as expected.

Due to this approach, dynamic testing can only ascertain the presence of errors in the
program;the exact nature of errors is not usually decided by testing.

Testing a large system is a complex activity, so for a project, incremental testing is

generally performed, in which components & subsystems of the system are tested
separately before integrating them to form the system for system testing.

Testing is a procedure to execute a program with the intent of finding errors. Testing
is an important part of the software development process, to detect bugs, improve
software design and to reduce usability problems. There are a number of test techniques
such as the traditionalunit, system, integration and acceptance tests, and a large number
of software tools, which support testing in different ways. Testing flow proceeds from
left to right and from top to bottom, user visible elements of the web application design
are tested first followed by infrastructure design element.

Testing Objectives

Testing is a process of executing a program with the intent of finding errors. A good
test case is one that has a high probability of finding an as yet undiscovered error. A
successful test is one that uncovers an undiscovered error.

Testing Principle

 All tests should be traceable to the customer’s requirements.

 Tests should be planned long before the testing begins.

 Testing should begin “in the small” & progress towards “the large”.

 Exhaustive testing is not possible.

46
4.2 Types of Testing used to test Portal:

Interface Testing / Unit Testing

The overall strategy for interface testing is to:

 Uncover errors related to specific interface mechanisms. For e.g. errors in the
properexecution of a menu link or the way the data is entered in the form.
 Uncover in the way the interface implements the semantics of navigation, web
application functionality, or content display.
 To accomplish this strategy, a number of objectives must be achieved:

 Interface features are tested to ensure that design rules, aesthetics and related
visualcontent are available for the user without error.
 Individual interface mechanisms are tested that are equivalent to unit testing.

 Each interface is tested to ensure that it performs the requisite task.

 The interface is tested within a variety of environments to ensure that it

will becompatible.

Navigation Testing

The job of this testing is:

 To ensure that the mechanisms that allow the web application user to travel
through theweb application are all functional and
 To validate that each navigation semantic unit can be achieved by the
appropriate user category.
The first phase of navigation testing actually begins during Interface Testing.
Navigation mechanisms are tested to ensure that each performs its intended function.
Following navigationmechanisms should be tested:

1) Navigation links: Internal links within the web application, external links to
other web application should be tested to ensure that proper content or
functionality is reached when the link is chosen.

Integration Testing

The purpose of unit testing is to determine that each independent module is correctly
implemented. This gives little chance to determine that the interface between modules

47
is also correct, and for this reason integration testing must be performed. One specific
target of integration testing is the interface: whether parameters match on both sides as
to type, permissible ranges, meaning and utilization.

The individual modules were aggregated one by one and functional testing was
performed. The integrated product was considered as a black box and the output (report)
is generated dependingupon the data present in the flat files.

System Testing

Software is to be incorporated with other system components (e.g. new hardware,

information), and thus a series of special tests are to be conducted. Many times,
software products are designed to run on a variety of hardware configurations. The
software should actually be testedon much different hardware set – ups, although the
full range of memory, processor, operatingsystem, and peripheral possibilities may be
too large for complete testing. There are many typesof specifications and we should be
aware of those as we perform system testing. During systemtesting, we should evaluate
a number of attributes of the software that are vital to the user. These attributes
represent the operational correctness of the product. Some of the attributes tested are:

 Usable: The product is convenient and easy to use. A naïve user can also
compare the flat files by browsing the files from their computer and selecting
the corresponding interface. User can also add the new interface and can also
make modifications in the existing interface.
 Secure: Only the authorized user is able to use this tool.

 Compatible: The product runs correctly using YUI_EXT Library, works

correctly in conjunction with existing software.

Performance Testing

Performance testing is used to uncover performance problems that can result from lack
of server-side resources, inappropriate network bandwidth, inadequate database
capabilities, faulty or weak operating system capabilities, poorly designed web
application functionality, and other hardware and software issues that can lead to
degraded client-server performance.

48
4.2.1 White Box Testing

White box testing is a test cases design method that uses the control structure
of theprocedural design to derive test cases. Test cases can be derived that

 Guarantee that all independent paths within a module have been exercised
at least once,
 Exercised all logical decision on their true and false sides,

 Execute all loops at their boundaries and within their operational bounds,

 Exercise internal data structure to ensure their validity.

 White box tests require knowledge of the internal program structure

and arederived from the internal design specification of the
code.
 They will not detect missing function (i.e. those described in the functional

design specification but not supported by the internal specification

or code) Following are the white box techniques which are used for ‘Expenses’
testing,
 Branch coverage

Branch coverage exclusively considers the logical value of the result

of a condition (true or false). This application contains many conditions like
doing repost, adding to my wish list, doing really. Such cases are tested in
branch coverage.

 Path coverage

Path coverage requires the execution of all different paths through

the test object. This is important with respect to mobile application.
Application should execute all the paths and should not crash in between.

49
4.2.2 Black Box Testing
Black box testing attempts to drive set of inputs that will fully exercise all the
functionalrequirements of a system. It is not an alternative to white box testing.

This type of testing attempts to find errors in the following categories:

 Errors,

 Incorrect or missing function.

 Interface errors in data structure or external database access,

 Performance errors,

 Initialization and termination errors.

Tests are designed to answer the following questions:

 How is the functions validity tested?

 What classes of inputs will make good test cases?

 Is the system particularly sensitive to certain input values?

 How are the boundaries of the data class isolated?

 What data rates and data volume can the system tolerate?

White box testing should be performed early in the testing process, while black box
testing tends to be applied during later stages. Test cases should be derived which
reduces the number of additional test cases that must be designed to achieve
reasonable testing, and tell us something about the presence or absence of classes of
error rather than an error associatedonly with the specific test at hand.

Following are the black box techniques which were used for ‘Mobile Social Network’ testing

 Equivalence class partitioning

Test case for input fields such as start date, end date, amount etc. are
preparedand tested. Equivalence class partitioning helps to reduce total time
in testing by dividing valid and invalid test cases.

50
  Boundary value analysis
Faults often occur at the boundary of equivalence classes, because
boundariesare not often defined clearly or misunderstood by programmers.
Application having range fields such as amount, date ranges are tested using
this technique.

 State transition testing

In many cases, not only current input, but also the history of
execution or events or inputs, influences the outputs. Application has many
fields such as date, project, category which has different effects on overall
application. Minor change ineach of them triggers changes in lot of input
methods. These fields are tested under state transition testing.

4.3 Test Cases:

Pehlay Akshar
Prepared By Vishwajeet No. of Test Cases 9
Reviewed By vishwajeet Testcases Pass 9
Prepared Date 10/06/2023 Testcases Fail 0
Reviewed Date 10/06/2023 Testcases NA 0

51
52
53
54
4.1 Test Report:
4.4.1 Testing & Result:

Entire website is tested at all testing levels and its working correctly.
This software has been tested by NIC Scientists.

55
CHAPTER 5 SYSTEM IMPLEMENTATION

56
5.1 Hardware required at Client side

CPU : 64 Bit CPU

Disk Space : 2 GB of HDD

Processor : Dual Core or higher

RAM : 2 GB

5.2 Software required at Client side

Software to be used:
Operating System : ubuntu-bionic-18.04-amd64-server-20180522-dotnetcore-
2018.07.11 (Ubuntu)

Microsoft Edge release 84, Google Chrome release 80, Mozilla

Browser : Firefox release 73 and above on client.

Application Server : Apache 2.4.43

Front End : Technology - Angular js

Back End : Technology - dotnet core

Tools to be used:

Database Server : MySQL version 5.7.26

IDE : Visual studio , VS code

Application Server : Apache 2.4.43

57
5.3 Testing done as
End User Acceptance
Testing
Acceptance testing, a testing technique performed to determine whether or not the software
system has met the requirement specifications. The main purpose of this test is to
evaluate the system's compliance with the business requirements and verify if it is
having met the required criteria for delivery to end users.

There are various forms of acceptance testing:

 User acceptance Testing

 Business acceptance Testing

 Alpha Testing

 Beta Testing

Beta Testing

Beta testing also known as user testing takes place at the end users’ site by the end users
to validate the usability, functionality, compatibility, and reliability testing.

Beta testing adds value to the software development life cycle as it allows the "real"
customer an opportunity to provide inputs into the design, functionality, and usability of a
product.
These inputs are not only critical to the success of the product but also an investment into
future products when the gathered data is managed effectively.

58
CHAPTER 6: SYSTEM MAINTANANCE AND
EVALUATION

59
6.1 Maintenance

Software maintenance in software engineering is the modification of a software

product after delivery to correct faults, to improve performance or other attributes.
A common perception of maintenance is that it merely involves fixing defects.
However, one study indicated that the majority, over 80%, of the maintenance effort
is used for non-corrective actions.
This perception is perpetuated by users submitting problem reports that in reality are
functionality enhancements to the system.
Maintenance is really evolutionary development and that maintenance decisions are
aided by understanding what happens to systems (and software) over time.
Lehman demonstrated that systems continue to evolve over time. As they evolve,
theygrow more complex unless some action such as code refactoring is taken to
reduce thecomplexity.
The key software maintenance issues are both managerial and technical. Key
management issues are: alignment with customer priorities, staffing, which
organization does maintenance, estimating costs.

Following are the different ways of software maintenance:

 Adaptive – modifying the system to cope with changes in the software
environment

 Perfective – implementing new or changed user requirements which concern

functional enhancements to the software

 Corrective – diagnosing and fixing errors, possibly ones found by users

Software maintenance is a very broad activity that includes error corrections,

enhancements of capabilities, deletion of obsolete capabilities, and optimization.

Because change is inevitable, mechanism must be developed for evaluation,

controlling and making modifications

60
6.2 Evaluation

Aspects of the system evaluation process:

Ensure that necessary, adequate data are acquired and analysed to determine and
assess theadvisability, adequacy and effectiveness of the management system in the
areas of quality, environment and occupational health and safety, including the
Policy and Objectives, as well as identifying and establishing guidelines and
actions for improvement.

Integration:
In all cases, the requirements point out the need to analyse the data to obtain
relevant information and the use of this information by Management for review
of the management system.

Therefore, it may be said that, regardless of the area, this process always has
the samestructure

Another aspect that promotes integration in this process is precisely the fact
that the Management, as shown by its commitment, must assume the
responsibility for systemreview.

It is a common practice to hold periodic meetings for this activity. Seeking

integration of the quality, environmental and occupational health and safety
management systems implies that these scheduled meetings must permit joint,
simultaneous analysis and review.

This simultaneous analysis and review of the three areas further promotes the
understanding of the interrelationships between them so that decisions and
guidelines taken are more compensated and balanced.
Indicators:
The indicators that are proposed are the same regardless of the area in which
they are to be applied, and can be calculated for the three systems together or
independently.

61
CHAPTER 7: USER/OPERATIONAL MANUAL

62
7.1 Security Aspects, Access Rights:

1. Authentication based on token generated for each login with Username, Password

2. Access rights based on location, program code etc

Security is maintainable through reaching following factors:

a) To restrict unauthorized access

b) To keep control over S/W flaws

c) Clear identification for privilege allotment
d) Data and resources should be protected

The system will be prevented against any damage, accidentally or otherwise as far
as possible. The system will be accessible to authorized persons only.

Standard Database functions may be utilized for this purpose or this functionality
may be provided through the software.

The access to the system will be controlled through security system, which will
provide thefollowing layers of security.

User Access restriction- There will be restricted access to the system. Username
and passwords will be defined for the users having permission to access the system.
There willbe mainly two types of users.

 Administrator- This user will act as a super user. The main privileges for
this user will be to manage other users, alter any master information. The
user who is having administrator privilege can also grant administrative
privileges to another user.
 Other user- This user that is not an administrator will be normal user who
can perform data entry.

 LR – Normal user who can perform management of property details.

 TAB- Normal user who can perform assessment and reassessment of properties.

63
7.2 Backup & Recovery
Application Backup - Daily basis with retention is 3 days

Database Backup- Daily basis with retention is 3 days

Periodical backup of the data is suggested. Facility will be provided for

the same. Backup of the data should be done by the system
Administrator.

Backup for Land and Revenue Management System includes:

 Application Backup
 Database Backup

Recovery for Land and Revenue Management System covers the control
measures forthe following types of failures:

64
CHAPTER 8: FUTURE ENHANCEMENTS

65
Future Enhancement:
The project “PEHLAY AKSHAR” can further elaborate for the following:

Notice Generation: Currently the generation of notice to print out is done for each individual
lease holder manually. In future, this can be implemented to generate notice automatically for
all lease holders on single click.

Tenure Issue: Currently the tenure payment module focuses mainly on Land Tenure Abolition.
In future, all other tenures can be implemented into the system.

Development issue: The project has been developed on Plain PHP. It is adopted to reduce
complexity of application and to make it web based. In future, this can be implemented using
PHP framework like Laravel, CakePHP or Codeigniter for better utilization of web resources,
authentication and authorization.

66
CHAPTER 9: LIMITATIONS

67
Limitations:

Currently offline content management with complete directory structure is not possible
due to technical limitations but going forward this can be achieved

There are not many limitations of the project but any of these limitations will affect the
wholesystem. But anyhow it includes some limitations, which are listed below:

Followings are the limitations in this system:

 Interest Calculation is not feasible in case of compound interest of pending dues.

 Loss of data while migration from .dbf to MYQL database due to filtering of
datasuch as invalid or incomplete details.

68
CHAPTER 10: CONCLUSION

69
Conclusion:
The project named as “PEHLAY AKSHAR” is an internal project developed for
the RPF Foundation, to the school for student or a teaching faculties(teachers).

This system offers great flexibility for future expansion. It requires maintenance
on dailybasis.

This project has been developed to cater the demands of department users to enter
date or period to generate reports daily/monthly basics.

This project is still under up gradations as per the requirement of user. It is too an
ongoingwhich needs maintenance and changes.

70
CHAPTER 11: BIBLIOGRAPHY

71
Bibliography
 https://ubuntu.com/server/docs/web-servers-apache

 https://dev.mysql.com/downloads/mysql/5.7.html

 https://www.w3schools.com

 https://angular.io/

 https://learn.microsoft.com/en-us/aspnet/core/introduction-to-aspnet-
core?view=aspnetcore-7.0

72