Project Report
On
Online Notes Sharing System
REPORT INDEX
S. no. Description
1 ACKNOWLEDGEMENT
2 ABSTRACT
3 INTRODUCTION
4 FEASIBILITY STUDY
4 SCOPE OF THE PROJECT
5 SOFTWARE & HARDWARE REQUIREMENTS
6 SYSTEM DESIGN (ER, Use Case, DFDs and Class Diagram)
7 DATABASE DESIGN
8 SYSTEM TESTING
9 OUTPUT SCREEN OF PROJECT
10 CONCLUSION
11
BIBLIOGRAPHY
ACKNOWLEDGEMENT
I am are over helmed in all humbleness and gratefulness to acknowledge my depth to all
those who have helped me to put these ideas, well above the level of simplicity and into
something concrete.
I would like to express my special thanks of gratitude to my esteemed guide, Mr. XYZ who
gave me the golden opportunity to do this wonderful project 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.
Any attempt at any level can't be satisfactorily completed without the support and guidance
of MY parents and friends.
I would like to thank my parents who helped me a lot in gathering different information,
collecting data and guiding me from time to time in making this project, despite of their busy
schedules ,they gave me different ideas in making this project unique.
----------------------
ABSTRACT
“Online Notes Sharing System” is a web based technology which manages user
and notes database and provides rights to update their details and notes.
This project manage user information and notes which is provided by him/her.
User’s also have rights to update their details and notes. In this web application
user must be registered. The aim of this web application is to manage user and
notes database.
INTRODUCTION
“Online Notes Sharing System” is a web based technology which manages user and
notes database and provides rights to update their details and notes. In this web
application user must be registered. This web application provides a way to
effectively control record & track the user details who himself/herself registered
with us.
Online Notes Sharing System provides functionality to manage personal profiles
and manages notes which are provided by them. Personal profiles contain
information such as profile contact number, email, first and last name, etc. and
notes details contains notes title, notes subject , notes descriptions etc. In order to
access personal profile for reading and modification password is used for
authentication. User information contains username, password and session for
authentication.
In this project we use PHP and MySQL database and it has one module i.e. User
Advantages:
It helps the to handle and manage user data and their notes.
Reduce time consumption.
Reduce error scope.
All system managements are automated.
Centralized database management.
Easy operations for operator of the system.
No paper work requirement.
Disadvantages:
The system can only handle single user.
FEASIBILITY STUDY
Whenever we design a new system, normally the management will ask for a feasibility report
of the new system. The management wants to know the technicalities and cost involved in
creation of new system.
- Technical feasibility
- Economic feasibility
- Physical feasibility
Technical feasibility:
Technical feasibility involves study to establish the technical capability of the system being
created to accomplish all requirements to the user. The system should be capable of handling
the proposed volume of data and provide users and operating environment to increase their
efficiency.
For example, system should be capable of handling the proposed volume of data and provide
users.
Economic feasibility:
Economic feasibility involves study to establish the cost benefit analysis. Money spent on the
system must be recorded in the form of benefit from the system. The benefits are of two types:
Tangible benefits:
- Saving man labor to do tedious tasks saves time.
-
Intangible benefits:
- Improves the quality of organization.
Physical feasibility:
It involves study to establish the time responses of the new system being created. For e.g., if
the new system takes more than one day to prepare crucial finance statement for the
management, wherever it was required in an hour, the system fails to provide the same.
It should be clearly establish that the new system requirements in the form of time responses
would be completely met with. It may call for increase in cost. If the required cost is sacrificed
then the purpose of the new system may not be achieved even if it was found to be technically
feasible.
SCOPE OF THE PROJECT
The proposed system provides a simple user and notes management pages that lets you view
users and notes details, create new user accounts, edit existing ones and manage notes
which is share by them. Also provides tools to disabled or delete users, manage permission
and issue password reset.
The system works and fulfills all the functionalities as per the proposed system.
It will provide reduced response time against the queries made by different users.
All possible features such as verification, validation, security, user friendliness etc have been
considered.
In this project there is one module user
User:
1. Dashboard: This is welcome page of registered users, user can briefly view total
number of notes uploaded.
2. Notes: In this section, user can add, update and delete the notes which they want to
share.
3. Profile: User can update his/her profile.
4. Change Password: User can update/his/her account password.
SOFTWARE AND HARDWARE REQUIREMENTS
Any Version of browser after Mozilla Firefox 4.0, Internet Explorer 6.0,chrome
Hardware requirements:
Any processor after Pentium 4.
Any version of Windows XP or later.
Processor speed: 2.0 GHz
RAM : 1GB
Hard disk: 40GB to 80 GB
Software requirements:
Database : MySQL
Server : Apache
Frontend : HTML
Scripting Language : JavaScript
IDE : Sublime
Technology : PHP
SYSTEM DESIGN
Design is the first step in the development phase for any techniques and principles for the
purpose of defining a device, a process or system in sufficient detail to permit its physical
realization.
Once the software requirements have been analyzed and specified the software design
involves three technical activities - design, coding, implementation and testing that are
required to build and verify the software.
The design activities are of main importance in this phase, because in this activity, decisions
ultimately affecting the success of the software implementation and its ease of maintenance
are made. These decisions have the final bearing upon reliability and maintainability of the
system. Design is the only way to accurately translate the customer’s requirements into
finished software or a system.
Design is the place where quality is fostered in development. Software design is a process
through which requirements are translated into a representation of software. Software
design is conducted in two steps. Preliminary design is concerned with the transformation of
requirements into data
Unified Modelling Language Diagrams (UML):
The unified modelling language allows the software engineer to express an analysis
model using the modelling notation that is governed by a set of syntactic semantic and
pragmatic rules.
A UML system is represented using five different views that describe the system from
distinctly different perspective. Each view is defined by a set of diagram, which is as
follows.
User Model View
i. This view represents the system from the users perspective.
ii. The analysis representation describes a usage scenario from the end-users perspective.
Structural model view
In this model the data and functionality are arrived from inside the system.
This model view models the static structures.
Behavioural Model View
It represents the dynamic of behavioural as parts of the system, depicting the
interactions of collection between various structural elements described in the user
model and structural model view.
Implementation Model View
In this the structural and behavioural as parts of the system are represented as they
are to be built.
Environmental Model View
In this the structural and behavioural aspects of the environment in which the system is to be
implemented are represented.
UML is specifically constructed through two different domains they are
UML Analysis modelling, which focuses on the user model and structural model
views of the system?
UML design modelling, which focuses on the behavioural modelling,
implementation modelling and environmental model views.
Use Case Diagrams User
Create Account
Sign in
Dashboard
Add Notes
Update Notes
Delete Notes
Update Own Profile
Change Password
Password Recovery
ENTITY-RELATIONSHIP Diagrams
E-R (Entity-Relationship) Diagram is used to represents the relationship between entities in
the table.
The symbols used in E-R diagrams are:
SYMBOL PURPOSE
Represents Entity sets.
Represent attributes.
Represent Relationship Sets.
Line represents flow
Structured analysis is a set of tools and techniques that the analyst.
To develop a new kind of a system:
The traditional approach focuses on the cost benefit and feasibility analysis, Project
management, and hardware and software selection a personal considerations.
Data Flow Diagrams
A Data Flow Diagram (DFD) is a traditional visual representation of the information flows
within a system. A neat and clear DFD can depict the right amount of the system requirement
graphically. It can be manual, automated, or a combination of both.
It shows how data enters and leaves the system, what changes the information, and where
data is stored.
The objective of a DFD is to show the scope and boundaries of a system as a whole. It may be
used as a communication tool between a system analyst and any person who plays a part in
the order that acts as a starting point for redesigning a system. The DFD is also called as a data
flow graph or bubble chart.
The following observations about DFDs are essential:
1. All names should be unique. This makes it easier to refer to elements in the DFD.
2. Remember that DFD is not a flow chart. Arrows is a flow chart that represents the order
of events; arrows in DFD represents flowing data. A DFD does not involve any order of
events.
3. Suppress logical decisions. If we ever have the urge to draw a diamond-shaped box in a
DFD, suppress that urge! A diamond-shaped box is used in flow charts to represents
decision points with multiple exists paths of which the only one is taken. This implies an
ordering of events, which makes no sense in a DFD.
4. Do not become bogged down with details. Defer error conditions and error handling
until the end of the analysis.
Standard symbols for DFDs are derived from the electric circuit diagram analysis and are shown
in fig:
Circle: A circle (bubble) shows a process that transforms data inputs into data outputs.
Data Flow: A curved line shows the flow of data into or out of a process or data store.
Data Store: A set of parallel lines shows a place for the collection of data items. A data store
indicates that the data is stored which can be used at a later stage or by the other processes
in a different order. The data store can have an element or group of elements.
Source or Sink: Source or Sink is an external entity and acts as a source of system inputs or
sink of system outputs.
Zero Level DFD
Login
Management
Password User
Management Management
ONSS
Notes Changing
Password
Management
Management
Authorization
Management
First Level DFD
Changing
Password Password
Management Management
Notes
ONSS
User
Management
Management
Authorization Login
Management Management
Second Level DFD
Login/Signu Check
User p to system Roles of
access
Forgot Check View Dashboard
Password Credenti
al
Add Notes
Manage
Module Update Notes
s
Delete Notes
Update Profile
Change Password
DATABASE DESIGN
The data in the system has to be stored and retrieved from database. Designing the database
is part of system design. Data elements and data structures to be stored have been identified
at analysis stage. They are structured and put together to design the data storage and retrieval
system.
A database is a collection of interrelated data stored with minimum redundancy to serve many
users quickly and efficiently. The general objective is to make database access easy, quick,
inexpensive and flexible for the user. Relationships are established between the data items and
unnecessary data items are removed. Normalization is done to get an internal consistency of
data and to have minimum redundancy and maximum stability. This ensures minimizing data
storage required, minimizing chances of data inconsistencies and optimizing for updates. The
MySQL database has been chosen for developing the relevant databases.
Online Notes Sharing System (ONSS) contains 2 MySQL tables) :
User table Structure : This table store the login and personal Details of users.
Notes table Structure : This table store the details of notes which is share by users.
Class Diagram:
The class diagram shows a set of classes, interfaces, collaborations and their relationships.
SYSTEM TESTING
SOFTWARE TESTING TECHNIQUES:
Software testing is a critical element of software quality assurance and represents the
ultimate review of specification, designing and coding.
TESTING OBJECTIVES:
1. Testing is process of executing a program with the intent of finding an error.
2. A good test case design is one that has a probability of finding an as yet
undiscovered error.
3. A successful test is one that uncovers an as yet undiscovered error.
These above objectives imply a dramatic change in view port.
Testing cannot show the absence of defects, it can only show that software errors are
present.
There are three types of testing strategies
1. Unit test
2. Integration test
3. Performance test
Unit Testing:
Unit testing focuses verification efforts on the smallest unit of software design module. The
unit test is always white box oriented. The tests that occur as part of unit testing are testing
the module interface, examining the local data structures, testing the boundary conditions,
execution all the independent paths and testing error-handling paths.
Integration Testing:
Integration testing is a systematic technique or construction the program structure while at
the same time conducting tests to uncover errors associated with interfacing. Scope of testing
summarizes the specific functional, performance, and internal design characteristics that are
to be tested. It employs top-down testing and bottom-up testing methods for this case.
Performance Testing:
Timing for both read and update transactions should be gathered to determine whether
system functions are being performed in an acceptable timeframe.
OUTPUT SCREEN OF PROJECT
Home Page
Notes Details
User Signup
User Sign in
Forgot Password
Dashboard
Profile
Change Password
Add Notes
Manage Notes
Update Notes
Update File1
Update File2
Update File3
Update File4
CONCLUSION
The project titled as Online Notes Sharing System was deeply studied and analyzed to design
the code and implement. It was done under the guidance of the experienced project guide. All
the current requirements and possibilities have been taken care during the project time.
Computer has got clear advantage over the manual system. The computerized system is
more reliable, efficient and fast at the end of the project, I can say that computer play a very
crucial role in the development of firm. All the daily reports generated by the system are to
be checked by the concerned official so as to ensure that all the transactions have been put
through in appropriate accounts and this is tallied with the new vouchers. Computer does
maximum work with in minimum time. Because it is used in every field so that it provides
comfort and suitability to everyone. Providing maximum facilities and comfort to customers
to customers is main goal of the firm. To achieve this goal, other modern facilities relating to
computer should have to be provided.
BIBILIOGRAPHY
For PHP
https://www.w3schools.com/php/default.asp
https://www.sitepoint.com/php/
https://www.php.net/
For MySQL
https://www.mysql.com/
http://www.mysqltutorial.org
For XAMPP
https://www.apachefriends.org/download.html