“Mini Project Title”

A MINI PROJECT REPORT

SUBMITTED TO

UNIVERSITY OF PUNE, PUNE

FOR THE PARTIAL FULFILLMENT OF AWARD OF DEGREE

Of

BACHLOR OF ENGINEERING
In
INFORMATION TECHNOLOGY
By

MANKAR ABHISHEK
NIMBALKAR PRASAD
NIRWAN ROHAN
PATANGE SANTOSH

DEPARTMENT OF INFORMATION TECHNOLOGY

Vidya Pratishthan’s College of Engineering, Baramati-413133.
2018-19
 Contents of Mini Project Report

1. Title page…………………………………………………………………………........…..0

2. Index ………………………………………………………………………………...….1

3. Abstract ……………………………………………………………………………..….2

3. Introduction………………………………………………………………………….....3

4. Scope and Limitations………………………………………………………………....5

5. Requirement Analysis…………………………………………………………………....6

6. Feasibility study…………………………………………………………………………..8

7. System Requirement……………………………………………………………………...9

8. Design (ER Diagram)…………………………………………………………………....10

9. Schema Diagram………………………………………………………………………...11

10. Software Engineering Model…………………………………………………….……10

11. HCI Concepts used for GUI Design ………………………………………………….19

13. Screenshots……………………………………………………………………….…….22

14. Future scope / enhancement……………………………………………………..……24

15. Conclusion………………………………………………………………………….…..25

16. References………………………………………………………………………………26

2
 PROJECT TOPIC

REMUNERATION FORM

BREIF ABSTRACT:

Remuneration is considered the pay or other compensation provided in exchange for

the services performed; not to be confused with giving (away), or donating, or the act of
providing to. A number of complementary benefits, however, are increasingly popular
remuneration mechanisms.] Remuneration is one component of reward management.
Reward for employment in the form of pay, salary, or wage, including allowances, benefits
(such as company car, medical plan, and pension plan), bonuses, cash incentives, and
monetary value of the noncash incentives.
Remuneration paid to a management company which manages mutual funds, unit trusts,
hotels, resorts, and offshore companies on behalf of investors/owners. This fee usually
consists of a fixed monthly, quarterly, or annual amount plus a percentage of the revenue or
income generated by the managed enterprise.

The term "remuneration" means compensation or pay, but it has a broader meaning than
pay because it can include not just base salary or bonuses but commissions and other
payments or benefits paid under the terms of an employment contract as well.

The management of all the payment for various procedures in the remuneration is a
difficult job. Worst case comes when there are like a hundred of applications to be
managed in an hour, while the company is currently short of workers to find each
customer document to be updated.

As a result, a system needs to be developed to replace the current system and enhance
the system's performance of management.

The system is developed to handle the process of secured login, new registerations,
generate remuneration form bills etc. In this Project we have used HTML/PHP in front
end and MySQL in back end.

The expected result from this system is to get the correct output for each
function and system free of error

3
 INTRODUCTION
Computer is the Backbone of Today’s Industry or organizations and
plays an important role in its development. Now a day each
organization prefers the computerized version of their existing
system that helps themselves to be with challenging and rapidly
growing organization.

The proposed system is for “REMUNERATION FORM “.The system

provides user to get output in the form of softcopy of a bill that
includes all the essential entries taken from the user for allowing to
pay bills to respective people which includes all teaching and non-
teaching staff.

Software include:
Our project includes login of the user or as an admin login, user fills the
required areas in the form that basically includes brief information about
practical/oral sessions which took place in college. After entering all
appropriate information a payable sum of amount in rupees is calculated
using TA (Travel Allowance) and DA (Dearness Allowance) or only DA
which is based on factors like number of batches evaluated, fixed pay rate
etc.

Input Forms:

 Registered/Admin login
 Exam Detail
 External Examiner Information
 TA(Travel Allowance) Table External Examiner
 Internal Examiner Information

4
Advantages:

Time Saving

It is much easier to just fill the required information and view any record at any
time with just few clicks.

Convenient:

It is very easy to handle i.e. user friendly. It also enables the administrator to get
the details of a particular Practical Remuneration payments.

User friendly:

The software System has user-friendly Interface. Thus the users will feel very
easy to work on it. The software provides accuracy along with a pleasant
Interface. Make the present manual system more interactive, speedy and user
friendly.

Calculation simplicity:
User has to only fill required fixed pay rates and Net payable amount is
calculated efficiently

Less paper work issues

The software will reduce/minimize paper work and stuffs.

5
 SCOPE OF THE PROJECT

It may help collecting perfect management in detail. In a very short time the collection will be very
obvious, simple and sensible.

Our project aims at office process works i.e. we have tried to computerize various process of Billing
Systems

 In computer system the person has to fill the forms and number of copies of the form can be
printed easily

 The system generates types of information that can be used for various purposes.

 It satisfies the user requirements.

 It is easy to understand

 It is easy to operate.

 Have a good user interface

 Reduce office billing loads

6
 REQUIREMENT ANALYSIS

• Windows 10, Windows 8.1 (32- and 64-bit versions of each operating system),
• At least a Pentium 1.5 GHz or faster processor
• Minimum 1 GB of RAM
• WXGA or higher resolution video adapter and monitor
• Minimum 1 GB Hard Drive space to install*
• Microsoft's .Net Framework 4. This may be installed on your computer if all updates are
current.
• Microsoft's MDAC component. This may be installed on your computer if all updates are
current.
• Laser or ink-jet printer to use some of the program capabilities; such as generation of
various tax forms and MICR checks**.

7
 FEASIBILITY STUDY

ECONOMIC:

The economic feasibility study evaluates the cost of the software development against
the ultimate income or benefits gets from the developed system. There must be scopes
for profit after the successful Completion of the project.

TECHNICAL:

The technical feasibility study compares the level of technology available in the
software development firm and the level of technology required for the development of
the product. Here the level of technology consists of the programming language, the
hardware resources, other software tools etc.

OPERATIONAL:

It assesses the extent to which the required software performs a series of steps to
solve business problems and user requirements. This feasibility is dependent on human
resources (software development team) and involves visualizing whether the software will
operate after it is developed and be operative once it is installed. Operational feasibility also
performs the following tasks.

Determines whether the problems anticipated in user requirements are of high priority

Determines whether the solution suggested by the software development team is

acceptable

Analyzes whether users will adapt to a new software

Determines whether the organization is satisfied by the alternative solutions proposed by

the software development team.

8
 SOFTWARE ENGINEERING MODEL
WATERFALL MODEL: =

Waterfall Model is also known as Liner Sequential Life Cycle Model. Waterfall
Model followed in the sequential order and so we move to next step of development or testing
if the previous step completed successfully. Waterfall Model is very successful approach for
the small projects and if the requirements are very clear. In Waterfall Model, testing starts at
the end when development work is completed. The name Waterfall describes that testing or
development is carried out in downward mechanism like water falls towards down. Waterfall
Model is very popular strategy for SDLC.

PHASES IN WATERFALL MODEL :

• Requirements Analysis
• Design
• Implementation
• Testing
• Deployment
• Maintenance
• Requirements: This is the first phase of development where all the requirements
gathered and documented.
• Analysis: In this phase we analyse all the gathered requirements whether the
requirements are valid or invalid.

9
 • Design: In this phase all the system design is analysed and specified like hardware,
system configuration and architecture or the system.
• Implementation: In this phase all the development works are performed and
development components or units handed over to testing team.
• Testing: Once the development completed, testing phase starts and in this phase we test
the each unit or component and make sure the developed components are working as
expected. All the testing activities are performed in this phase.
• Deployment: Once testing is completed and make sure there is no bug or defect or any
kind of issue, then project is deployed to production. Once product is deployed to
production the end users start using the product.
• Maintenance: We always keep eye on the product and provide the entire necessary bug
or issue fixes if occurs in production or reported by end users. Also time to time we keep
updated the product with new updates or patches if developed or available.

Advantages of Waterfall Model:

• Very good approach for small projects.
• Easy to use and follow.
• Cost effective.
• Each phase completely developed.
• Development processed in sequential manner so very less chance to rework.
• Easy to manage the project.
• Easy documentation.

Applications of Waterfall Model:

• This model is used only when the requirements are very well known, clear and fixed.
• Product definition is stable.
• Technology is understood.
• There are no ambiguous requirements
• Ample resources with required expertise are available freely
• The project is short.

Disadvantages of waterfall model:

• No working software is produced until late during the life cycle.
• High amounts of risk and uncertainty.
• Not a good model for complex and object-oriented projects.
• Poor model for long and on-going projects.
• Not suitable for the projects where requirements are at a moderate to high risk of
changing.

10
 HCI CONCEPT USED FOR GUI DESIGN
Good user interface design facilitates finishing the task at hand without drawing unnecessary
attention to itself. Graphic design and typography are utilized to support its usability,
influencing how the user performs certain interactions and improving the aesthetic appeal of the
design; design aesthetics may enhance or detract from the ability of users to use the functions
of the interface.[1] The design process must balance technical functionality and visual elements
(e.g., mental model) to create a system that is not only operational but also usable and adaptable
to changing user need

Interface design is involved in a wide range of projects from computer systems, to

cars, to commercial planes; all of these projects involve much of the same basic human
interactions yet also require some unique skills and knowledge. As a result, designers tend to
specialize in certain types of projects and have skills centred on their expertise, whether that be
software design, user research, web design.

Processes
User interface design requires a good understanding of user needs. There are several
phases and processes in the user interface design, some of which are more demanded upon
than others, depending on the project.

Requirements
The dynamic characteristics of a system are described in terms of the dialogue
requirements contained in seven principles of part 10 of the ergonomics standard, the ISO
9241. This standard establishes a framework of ergonomic "principles" for the dialogue
techniques with high-level definitions and illustrative applications and examples of the
principles.

Research
User interface design has been a topic of considerable research, including on its aesthetics.
Standards have been developed as far back as the 1980s for defining the usability of software
products. One of the structural bases has become the IFIP user interface reference model. The
model proposes four dimensions to structure the user interface:
• The input/output dimension (the look)
• The dialogue dimension (the feel)
• The technical or functional dimension (the access to tools and services)

11
ER DIAGRAM

12
SCHEMA DIAGRAM

13
 FUTURE / SCOPE OF THE PROJECT

If the PROJECT is approved by the college authorities and respective teachers,

it could made in real use for the college administration/office billing and thus
help them to reduce the loads while preparing Remuneration Forms.

It must have following aspects verified:

 The system generates types of information that can be used for various purposes.

 It satisfies the user requirements.

 It is easy to understand

 It is easy to operate.

14
 CONCLUSION OF THE PROJECT
At the end of the project it is concluded that we have made efforts on following points:-

 a description of the background and context of the project and its relation to work
already done in the area.

 Made statement of the aims and objectives of the project.

 Description of purposes, scope and applicability.

 We define problem on which we are working in the project.

 We describe the requirement specification of the system.

 We include features and operations in detail.

 We design user interface related to the project.

 Finally the system is implemented and tested according to test cases.

15
 REFERENCE:

 GOOGLE FOR PROBLEM SOLVING

 https://www.w3schools.com/HTML
 https://www.w3schools.com/MYSQL
 https://www.w3schools.com/PHP

16