Professional Documents
Culture Documents
PROJECT REPORT
ON
Shinde Pramod
Mr.Rushikesh Sandip &
Ghodake
Thorat AjitRode
Mr.Aksshay Baban
IN
OF
BACHELOR IN COMPUTER APPLICATION
IN
B.B.A.(C.A.) DEPARTMENT
TYBBA(CA) Exam Seat No --------------- --. During the academic year 2020-21 who carried out the project work
under my supervision.
Guide HOD
BBA(CA).,BSc.(Comp.Sci)
& Msc.(Comp.Sci.)
Internal Examiner External Examiner
ACKNOWLEDGEMENT
I wish to thank the Principal Prof. Jadhav P.G. of my college for permitting me to
use all the facilities available in the institution for my project work. I would also like to thank
the Head of the BBA(CA). department Prof.Smt.Joshi N.P. the teaching faculty and all the
non- teaching staff of my college for their support in completing the work successfully.
guidance and supervision of my project work during the year. I express my thankfulness to
them. I must acknowledge the support given to this project by Prof. Hakim Sir without which
My classmates have been of great help to me during the project work. My ideas were
shaped and refined progressively through my discussions with them time to time. I cannot miss
to thank them all. There were some persons who were not directly but indirectly but indirectly
them too.
Class : TYBBA(CA)
Sign :
Prepare By
Rushikesh and Akshay
Guide
Prof. Hakim Sir
1
Sr. No Title Page
No
1. Abstract Introduction 5
Motivation
Purpose/Objective
Introduction to system
Literature Survey
Project Scope
Project Limitaton
2. System Analysis 8
Existing System
Scope Of Existing System
Limitations Of Existing System
Project Perspective/Feautures
Stackholders
Fact Finding Techniques
Requirment Analysis
Feasibility Study
3. System design 11
Design Goals and Constraints
UML Diagrams 13
Data Flow Diagram 16
User Interface
4. Implementation Details
s/w / h/w Spcification
5. Outuput And Report Testing 19
Testing Results (System Preview) 20
6. File Design
7. Form Design
Customer Enquiry Form
Customer Detail Form
Manager Form
Worker Form
8. Advantage/ Disadvantage Of System 24
9. Conclusion 26
10. Future Enhancement
11. Bibliography 27
INTRODUCTION
3
MOTIVATION :-
Motivation Within the framework of sustainable development the
energy supply system is a crucial topic. Spurred on by the Kyoto
Protocol the attention for the definition of energy saving
programs and the promotion of environment-friendly
technologies as renewable energy is increasing. In the longer
term however additional alternatives have to be found. Especially
for the Belgian context the combination of a further decrease of
emissions (CO2, NOX,…) with a faze-out of nuclear energy is a
major challenge. At the international level hydrogen as an energy
carrier is one of the major topics in the discussion on pathways
towards a future sustainable energy society. It is expected to
contribute both to the reduction of air pollution, CO2-reduction
and energy supply stability. The reason for this is that hydrogen
offers a long term potential for energy systems with almost zero-
emission level; it can be based on local and renewable energy
sources. In the USA a ‘Roadmap to hydrogen’ has been
developed already and on the European level recently the policy
paper ‘Hydrogen Energy and Fuel Cells, a vision of our future’
has been presented. Within the Belgian energy policy the
knowledge on hydrogen is rather limited and this project intends
to be the first step in a scientific assessment of hydrogen in the
Belgian context.
PURPOSE/OBJECTIVE :-
Objectives Actually the governments of the USA, Japan and the
EU are defining energy policies based on hydrogen as energy
carrier and the resources for research and development will
significantly increase in the coming years. If Belgium wants to
play a role in the European discussion and research on
hydrogen it will be essential to develop national/regional
activities on hydrogen, being complementary to the European
activities. This project is the start of such a Belgian initiative. It
gives the Belgian policy makers the necessary international
information on hydrogen knowledge and experiences, and tools
to evaluate the possibilities of hydrogen in the Belgian energy
supply on a scientific way. The results of the project can be
summarized as follows: * databases with international knowledge
and experiences on hydrogen * hydrogen module within
MARKAL-TIMES, illustrated by a scenario calculation * initial
technology assessment on hydrogen, focussed on the scenario *
translation of the progress in foreign legislation and licence
procedures on hydrogen * definition of relevant policy issues
concerning hydrogen
• Introduction to System
4
• LITERATURE SURVEY:-
• Scope Of Project:-
6
system as follows:
• Provide useful coding structure as per category with proper
Recognition.
• Maintaining various master tables like Manager, Customers,
worker etc.
• PROJECT LIMITATION:-
➢ Invoices can go into spam folders due to flagging by email servers; that
process difficult.
8
.
System Analyses.
10
• SYSTEM ANALYSIS:-
Existing System
For retrieving the detailed information about the customers visiting
wedding hole for booking purpose or for keeping track of those
customers, the manager has to search a long register which is very
complicated and tedious job to do.
For checking whether the room is available or not for a specified
date or those many days, the manager has to undergo a long
search regarding the date of booking of dates and departure dates,
which need a long time and doing all these calculations manually is
very tough task.
For updating the staff details incase of assigning any new staff
member its details of existing staff members, needs a long
verification and manipulating all the corresponding data which very
lengthy procedure as per the doing it manually.
The Wedding Hall Management system is totally menu driven and uses
clearly formatted screen displays to enter and process data generates
reports
All the rules and requirements of the Wedding Hall taken into consideration
while developing this system. The scope of the system as follows:
➢ Invoices can go into spam folders due to flagging by email servers; that
➢ Reaching offline customers who do not access the internet makes the
process difficult.
• PROJECT PERSPECTIVE/FEATURES :-
The project is a fairly recent phenomenon in history. Earlier, most
tasks in society were handled by designated permanent
organizations – be it the construction of a bridge or a road,
arranging a cultural or a sports event, developing a new industrial
product, solving a research problem or testing a new drug. Over
the last decades, however, projects have become increasingly
important as a way to organise work. More than ever before,
projects are used to solve big tasks of public utility. They operate
across organisations, and are terminated when the planned task
is completed. There has been a significant increase in the amount
of such major projects – not least in sectors such as offshore,
infrastructure and information technology. But projects are also
14
organised within individual organisations. This means that their
value added and profitability increasingly depend on successful
projects.
• PROJECT STAKEHOLDERS:-
• REQUIRMENTS ANALYSIS:-
Requirements analysis is critical to the success or failure of a systems or
software project. The requirements should be documented, actionable,
measurable, testable, traceable, related to identified business needs or
opportunities, and defined to a level of detail sufficient for system design.
Conceptually, requirements analysis includes four types of activity:
1. Eliciting requirements: the task of communicating with customers and
users to determine what their requirements are. This is sometimes also
called requirements gathering.
16
2. Analyzing requirements: determining whether the stated requirements
are unclear, incomplete, ambiguous, or contradictory, and then resolving
these issues.
3. Requirements modeling: Requirements might be documented in
various forms, such as natural-language documents, use cases, user
stories, or process specifications.
4. Review and retrospective: Team members reflect on what happened
in the iteration and identifies actions for improvement going forward.
18
Through such invaluable techniques, it is possible to find much of the quality
information and also some options and underlying problems.
Feasibility Study
Technical Feasibility
The study of resources availability that may affect the ability to achieve to
acceptable system. The technical feasibility is frequently the most difficult
area to assure because objectives, functions, and performance somewhat
anything seems possible with technical feasibility includes resources
availability of the origination for which the project is developed.
20
System
Design.
12
System Design:
Performance:
No more than a 5-percent degradation in average query response is allowed while all
concurrent user are using the system.
Availability:
Because the system is accessed by sales representative to book the order and print
the invoice, and their should not be any single point of failure.
Reliability:
Because of the need no single point failure, automatic failover will be required. In
addition, existing disaster recovery and backup plans and procedures must be revised
to incorporate the eBilling and Invoicing System.
24
Scalability:
eBilling and Invoice System an average load of 50 concurrent users after the system is
fully operational, and expects that to grow by 5 percent each year for the next five
years.
Security:
For the sensitive customer and order data, all users will need to log on the system with
their user id and password. Every resource in the system are defined by the role and
privileged. System administrator assigned user role and privileged for their access
rights.
Interoperability:
In Version 1.0 of the eBilling and Invoice System, there are no requirements for
interoperability with other systems.
Location:
The eBilling and Invoice System are used in the company office only.
Setup/Installation:
Setup and installation must not interrupt the sales staff’s daily tasks and work flow.
26
28
29
30
31
32
USER INTERFACES :-
• Form-based user interface: Used to enter data into a program or
application by offering a limited selection of choices. For example, a
settings menu on a device is form-based.
• Graphical user interface: A tactile UI input with a visual UI output
(keyboard and monitor).
• Menu-driven user interface: A UI that uses a list of choices to
navigate within a program or website. For example, ATMs use
menu-driven UIs and are easy for anyone to use.
• Touch user interface: User interface through haptics or touch.
Most smartphones, tablets and any device that operates using a
touch screen use haptic input.
• Voice user interface: Interactions between humans and machines
using auditory commands. Examples include virtual assistant
devices, talk-to-text, GPS and much more
33
IMPLEMENTATION DETAILS:-
❖ S/W and H/W Specification :
34
• Output And Report Testing:-
Testing:
Specified in the designing stage into source code. Careful study and
observation about system designing were made and accordingly the system
was coded to convert from designing to source code, where PHP and
System was developed such that it should be used for the future enhancement,
All the module of the system is combined and is put to the
operational use, This means that the new and old system are run in the
parallel for sometimes, errors are identified and the corresponding errors
The set of working programs and initialized tables are also provided for
• The time lag between the cause and appearance of the problem
• The effect of system errors on files and records within the system.
36
Testing results:
Login Screen:
(to Authenticate user)
37
.File Design.
18
38
39
40
41
42
.Form Design.
23
1] Customer Enquiry Form
44
2]Customer Detail Form
45
3]Manager Form
46
4] Worker Form
47
Advantages Of The System:
Security of data.
Ensure data accuracy’s.
Proper control of the higherofficials.
Reduce the damages of the machines.
Minimize manual data entry.
Minimum time needed for the various
processing.
Greater efficiency.
Better service.
User friendliness and interactive.
48
Minimum time required .
49
Conclusion:
This project was developed to full fill user and business requirement; however
there are lots of scope to improve the performance of the eBilling and Invoice
System in the area of user interface, database performance, and query
processing time. Etc.
So there are many things for future enhancement of this project. The future
enhancements that are possible in the project are as follows.
51
• Electronic Data Interchange (EDI) system between banks, other credit
verification agency and their vendors
• In the area of data security and system security
• Provide more online tips and help
• To optimize the query which is embedded in the system
52
Future Enhancement
The system does not currently have a “Help” module since the
targeted users are fully aware of the hiring process. Future
53
enhancement can include preparing an up-to-date help menu
with relevant contents to guide the users of the system.
This is including the display Hall booking of date
54
BIBLIOGRAPHY:-
1. Visual Basic 6 Programming (Black Book)
Steven Holzner
2.
Mastering in visual basic Evangelos Petroutsos
3.
MS-Access
55
56