Project Doc3
Project Doc3
Project Doc3
On
Submitted By:
Prathmesh Jadhav(A-53)
&
Aarti Tarde(A-14)
Submitted to:
1
Index
Sr. No Particulars Page No.
1 Abstract 4
2 Introduction 4
2.1 Motivation 4
2.2 Problem statement 4
2.3 Purpose/Objectives/goals 5
2.4 Literature survey 5
2.5 Project Scope and Limitations 6
3 System Analysis 6
3.1 Existing System 6
3.2 Scope and Limitation of existing system 7
3.3 Project perspective, features, stakeholders 7
3.4 Requirement Analysis 7
3.4.1 Functional Analysis 7
3.4.2 Performance Analysis 8
3.4.3 Security Analysis 8
4 System Design 9
4.1 Design constraints 10
4.2 System Model 10
4.2.1 Data Flow Diagram 11
4.2.2 Data Model 12
4.3 User Interface 13
5 Implementation Details 27
5.1 Software and hardware specifications 27
6 Output and Report Testing 28
6.1 Test Plan 28
6.2 Black Box Testing/Data validations Test 28
cases
6.3 White Box Testing/functional validations 29
Test cases and results
7 Conclusion and Recommendation 30
8 Future Scope 31
9 Bibliography and References 32
2
Acknowledgement
We would like to express our sincere and heartfelt gratitude to our institution” Indira
College of Commerce and Science” which provided us with excellent opportunity to achieve
our most cherished goal in life to become Bachelor degree in BBA-CA.
We are extremely grateful to our respected Vice Principal and HOD Prof, Shivendu
Bhushan for providing excellent academic environment which has made this endeavour
possible.
We take this opportunity to express our deep sense of gratitude to our guide Prof. Divya
Chitre for their resplendent idea and constant encouragement in making this project
unmitigated success. Their thoughtfulness and understanding was vast and thoroughly helpful
in successful completion of project. Our sincere thanks to all our faculties and non-teaching
staff for their at most co-operation.
Finally we proudly thank our parents and friends for their constant support and priceless
guidance in throughout this endeavour.
2) Introduction:
2.1) Motivation:
First of all it’s all free; user can register totally free and can avail
all of the web portal features for FREE. This Web Portal is available for every type of plants.
4
2.3) Purpose/Objectives/goals:
✓ Reduced entry work
✓ Easy retrieval of information
✓ Reduced errors due to human intervention
✓ User friendly screens to enter the data
✓ Portable and flexible for further enhancement
✓ Web enabled.
✓ Fast finding of information request
1)Data validation
2)Performance
3)Reliability
4)Scalability
5)Portability
6)Performance
7)Time Constraint
8)Cost Constraint
5
3) System Analysis:
3.1) Existing System :
This existing system is not providing secure registration and
profile management of all the users properly. This system is not providing on-line Help. This
system doesn’t provide tracking of users activities and their progress. This manual system gives
us very less security for saving data and some data may be lost due to mismanagement. This
system is not providing event management through internet. This system is not providing proper
events information. The system is giving manual information through the event management
executerp
• This System has many unique features of its own. The main feature is that it is very
user friendly and not complicated like many other systems that are used today.
• This feature becomes a selling point of this system as many other systems tend to feel
complicated to use and ordering plants isn’t supposed to be complicated.
• The Stakeholders of this project are the Users of the system and the administrators who
control and manage the system.
• The buyer registers themselves with their details and can login with the same
credentials. He is then redirected to the homepage of the system. From there he can
browse the items that are listed, check out the prices and choose them and add to cart
to purchase them later.
• The buyer is then redirected to the checkout page where he is to enter his personal
details into the given fields and place an order. The data he enters is saved into the
database and can be used later too.
6
• The admin is another stakeholder of the system. He can access the admin page and edit
or delete the products from there. He has a separate admin registration portal where he
can enter his email and name and become an admin.
• He can then Login using his credentials and modify, view and even delete the products
he wishes to. The system is even easy for the admin to use as it has been designed to
be simple yet effective.
• The models that depict information, function and behavior must be partitioned in a
• The analysis process must move from essential information to implementation detail.
7
3.4.2) Performance Analysis :
• Performance analysis looks at how a specific program is performing
on a daily basis and chronicles what slows down performance and
causes errors now and what could pose a problem into the future.
• In this systems analysis, there are some minor drawbacks that have
been noted.
• The system, while fast and simple, has a small responsiveness issue
that occurs when we resize the window now and then. The problem
hasn’t occurred many times but nevertheless, it still exists.
• The system generates a bill when an order is placed, but the bill isn’t
very user-friendly or useful as it only shows the basic information
needed but cannot be saved either.
• There are many minor glitches in the system which appear
sometimes such as images not loading properly or carts being
duplicated sometimes.
8
4) System Design :
4.1) Design constraints :
• System design is transition from a user oriented document to programmers or data base
personnel. The design is a solution, how to approach to the creation of a new system.
This is composed of several steps. It provides the understanding and procedural details
necessary for implementing the system recommended in the feasibility study. Designing
goes through logical and physical stages of development, logical design reviews the
present physical system, prepare input and output specification, details of implementation
plan and prepare a logical design walkthrough.
• The database tables are designed by analyzing functions involved in the system and
format of the fields is also designed. The fields in the database tables should define their
role in the system. The unnecessary fields should be avoided because it affects the
storage areas of the system. Then in the input and output screen design, the design should
be made user friendly. The menu should be precise and compact.
9
4.2) System Model :
4.3) 1.) Entity RelationshipDiagram: -
1) Data Flow Diagram:-
11
Class Diagram :
12
Object Diagram: -
Use case diagrams:
Use case diagram consists of actors, use cases and their relationships. These diagrams are
especially important in organizing and modelling the behaviours of a system.
Visit
Website
View Service
Detail
Enquiries
Book DJ
USER
13
Sign in
Dashboard
My Profile
Change
Password
Manage Services
(Add / Delete)
Manage Event
Type
(Add / Delete)
Admin
Manage Bookings
(Approved /
Cancelled)
Manage Queries
Search
Booking/Queries
Generate Report
14
1. A) File Design/Normalized Database: -
15
tblpage: This table about us and contact us detail.
17
Contact Us
18
Book Services
Sign In
Change Password
Sample code:
Login_page :
<?php
session_start();
error_reporting(0);
include('includes/dbconnection.php');
if(isset($_POST['login']))
$username=$_POST['username'];
$password=md5($_POST['password']);
19
$sql ="SELECT ID FROM tbladmin WHERE UserName=:username and
Password=:password";
$query=$dbh->prepare($sql);
$query-> execute();
$results=$query->fetchAll(PDO::FETCH_OBJ);
if($query->rowCount() > 0)
$_SESSION['odmsaid']=$result->ID;
if(!empty($_POST["remember"])) {
} else {
if(isset($_COOKIE["user_login"])) {
setcookie ("user_login","");
if(isset($_COOKIE["userpassword"])) {
setcookie ("userpassword","");
20
}
$_SESSION['login']=$_POST['username'];
} else{
?>
<!doctype html>
<head>
</head>
<body>
<main id="main-container">
21
<div class="hero-static col-md-6 col-xl-8 d-none d-md-flex align-
items-md-end">
</p>
</p>
</div>
</div>
<div class="hero-static col-md-6 col-xl-4 d-flex align-items-center
bg-white invisible" data-toggle="appear" data-class="animated fadeInRight">
<span class="font-size-xl">ODMS</span>
</a>
</div>
22
<form class="js-validation-signin px-30" method="post">
<div class="col-12">
<label for="login-username">Username</label>
</div>
</div>
</div>
<div class="col-12">
<label for="login-password">Password</label>
</div>
</div>
</div>
23
<label for="keep_me_logged_in">Keep me signed in</label>
</div>
</div>
<div class="form-group">
</button>
<div class="mt-30">
</a>
</div>
</div>
</form>
</div>
</div>
</div>
</div>
</main>
24
<!-- END Main Container -->
</div>
<script src="assets/js/core/jquery.min.js"></script>
<script src="assets/js/core/popper.min.js"></script>
<script src="assets/js/core/bootstrap.min.js"></script>
<script src="assets/js/core/jquery.slimscroll.min.js"></script>
<script src="assets/js/core/jquery.scrollLock.min.js"></script>
<script src="assets/js/core/jquery.appear.min.js"></script>
<script src="assets/js/core/jquery.countTo.min.js"></script>
<script src="assets/js/core/js.cookie.min.js"></script>
<script src="assets/js/codebase.js"></script>
<script src="assets/js/plugins/jquery-
validation/jquery.validate.min.js"></script>
<script src="assets/js/pages/op_auth_signin.js"></script>
</body>
</html>
25
5.IMPLEMENTATION
Database : MySQL
Server : Apache
Frontend : HTML
IDE : Sublime
Technology : PHP
b) Hardware Requirements: -
RAM : 1GB
27
6.) Output and Report Testing:
Black Box Testing is testing the software without any knowledge of the inner workings,
structure or language of the module being tested. Black box tests, as most other kinds of tests,
must be written from a definitive source document, such as specification or requirements
document, such as specification or requirements document. It is a testing in which the software
under test is treated, as a black box. you cannot “see” into it. The test provides inputs and
responds to outputs without considering how the software works
28
6.3) White Box Testing/functional validations Test cases and results:
White Box Testing is a testing in which in which the software tester has knowledge of the inner
workings, structure and language of the software, or at least its purpose. It is purpose. It is used to
test areas that cannot be reached from a black box level.
29
7) Conclusion and Recommendation:
The “Online DJ Management System” was successfully designed and is tested for accuracy
and quality. During this project we have accomplished all the objectives and this project
meets the needs of the organization. The developed will be used in searching, retrieving
and generating information for the concerned requests.
GOALS ACHIVIED
✓ Reduced entry work
✓ Easy retrieval of information
✓ Reduced errors due to human intervention
✓ User friendly screens to enter the data
✓ Portable and flexible for further enhancement
✓ Web enabled.
✓ Fast finding of information request
8) Future Scope :
• The objective of this application is to develop a system that effectively manages all the data
related to the various DJ events that take place in a function. The purpose is to maintain a
centralized database of all DJ event related information. The goal is to support various
functions and processes necessary to manage the data efficiently.
2.www.apache.org
30
31