ONLINE NOTICE BOARD

A PROJECT REPORT
Submitted by

ANITA GOHEL (160033107009)

Under the guidance of

Prof.Jaydeep Tadhani

Computer Engineering Department

A Report submitted to Gujarat Technological University in partial fulfillment

for the award of the degree
of
BACHELOR OF ENGINEERING
in

Computer Engineering

Atmiya Institute of Technology & Science

YogidhamGurukul, Kalawad Road,
Rajkot-360005.
Gujarat Technological University, Ahemdabad
MAY-2019
 CANDIDATE’S DECLARATION

I hereby declare that the work presented in this project entitled “online notice
board” submitted towards completion of project in eighth semester of B.E.
(Computer) at aits ,Rajkot , is an authentic record of my original work carried
out under the guidance of Prof. Jaydeep Tadhani.

Name: Gohel Anita D.

Semester: 8th
Place: Rajkot
 INDEX
No Title Page no.

Acknowledgement I

Abstract II

List of figures III

List of tables IV

Certificate From College V

Completion Certificate From PMMS Portal VI

Plagiarism Certificate VII

Undertaking Of Originality Of Work Certificate VIII

1.0 Introduction 1

1.1 Purpose 1

1.2 Scope 1

1.3 Objective 1

1.4 Technology and Tools 1

2.0 Project Management 2

2.1 Project Planning 2

2.2Project Scheduling 3

2.3 Risk Management 4

2.4 Estimation 5

3.0 System Requirements Study 6

3.1 User Characteristics 6

3.2 Hardware and Software Requirements 6

3.3 Constraints 6

3.4 Assumptions and Dependencies 7

4.0 System Analysis 8

 4.1Study of Current System 8

4.2Problem and Weaknesses of Current System 8

4.3 Requirements of New System 8

4.4 Feasibility Study 8

4.5 Requirements Validation 9

4.6 Features Of New System 9

4.7 Data Flow Diagram 9

4.8 ER Diagram 11

4.9 Selection Of Hardware and Software and 11

Justification

5.0 System Design 13

5.1Database Design 13

5.2Input/output Design 16

5.3Interface DesignDiagram 26

5.4System Structural Design 27

6.0 Code Implementation 29

6.1 Implementation Environment 29

6.2 Program/Module Specification 29

6.3 Coding Standards 29

7.0 Testing 30

7.1Testing plan 30

7.2Testing Strategy 30

7.3Testing Methods 31

7.4Test Cases 33

8.0 Limitations and Future Enhancement 34

8.1 Limitations 34
 8.2 Future Enhancement 34
9.0 Conclusion and Discussion 35

9.1 Self analysis and Project viabilities 35

9.2 Problem encountered and possible solutions 35

9.3 Summary of project work 37

14 References 38

15 Appendix 38

A.1 Business Model Canvas (BMC) and its report 38s

A.2 Periodic Progress Reports (PPR
A.3 Patent Drafting Exercise (PDE).
 ACKMOWLEDGEMNT
We are happy to submit our idea of “online notice board” in Gujarat Technology University,
Ahmadabad for Bachelor Engineering degree in computer branch.

The institute Atmiya Institute Technology and Science, which is due to the Param Pujya
Hariprasad Swamiji and his blessings. We are so thankful to them that he has given us such
a supportive institute and its environment .He is so supportive and spiritual and
continuously inspiring to give our best.

We are highly obliged to Param Pujya Tyagvallabh Swamiji to give us continuous

motivated environment and such a nice management.

This dissertation has been prepared under the most supporting guide Prof. Jaydeep Tadhani
of Department of Computer Engineering, Atmiya Institute of Technology and Science,
Rajkot.
Due to her continuous support, guidelines, her helping nature, and very thankful to her to
any time resolving our queries and provides all necessary facilities during our work. Also
thankful for giving us such new directions. Without her keen interest and knowledge of the
subject and constant encouragement we cannot complete our dream.

We are also grateful to Prof. T.M.Kodinariya Head of the Department and all the faculty
members of the Department of Computer Engineering for their kind support throughout this
journey.

We also take the privilege to acknowledge the elite authors of numerous books and papers
and blogs which we have referred during progress of this.

i
 ABSTRACT
The main aim of this free online notice board project is make information much easier in a
paperless community as the world tends to interact with the online notice board facility as an
project, Online notice board people can send the notification to the particular students
regarding fee payments, results, any new activity happen in college campus or college fest
participation, libraries dues, hostel room payments, any workshop registrations, warnings and
reminders and also send the notification to faculty regarding salary payment, time table.
Online notice board is fully capable of passing relevant notices and announcements keeping
the user update from time to time student and faculty are up to date what are going on
college

ii
 LIST OF FIGURE

Figure no Title Page no.

Fig 2.2.1 Shows timeline chart of this project 3

Fig 4.7.1 DFD Level-0 9

Fig 4.7.2 DFD Level-1(Admin) 10

Fig 4.7.3 DFD Level-1(USER} 10

Fig 4.8.1 ER-Diagram 11

Fig 5.2 Input/output Design 15

Fig.5.3.1 Interface DesignDiagram 25

Fig.5.3.3 System Structural Design 26

Fig a.1 BMC 37

iii
 LIST OF TABLES

Table no. Title Page no.

2.1.2.1 Milestones and Deliverables

2.1.3.1 Roles And Responsibilities 3

2.4.2.1 Distribution of Effort 5

7.4.1.1 Login Test 31

7.4.1.2 Signup Test 31

7.4.1.1 Admin Login Test 32

iv
 ATMIYA
INSTITUTE OF TECHNOLOGY & SCIENCE
RAJKOT

This is to certify that the project entitled “ONLINE NOTICE BOARD” is a bonafied report
of the work carried out by Ms. Gohel Anita D. under the guidance and supervision for the
work of Project-II at Atmiya Institute of Technology and Science - Rajkot, Gujarat.

To the best of my knowledge and belief, this work embodies the work of candidate herself,
has duly been completed, fulfills the requirement of the ordinance relating to the Bachelor
degree of the university and is up to the standard in respect of content, presentation and
language for being referred to the examiner.

SIGNATURE SIGNATURE
PROF.TOSAL BHALODIA MR. JAYDEEP TADHANI
HEAD OF THE DEPARTMENT ASST PROF
C. E. DEPARTMENT C. E. DEPARTMENT

v
 UNDERTAKING CERTIFICATE

We hereby certify that we are the sole authors of this IDP/UDP project report and that neither any part
of this IDP/UDP project report nor the whole of the IDP/UDP Project report has been submitted for a
degree by other student(s) to any other University or Institution.

We certify that, to the best of our knowledge, the current IDP/UDP Project report does not infringe
upon anyone’s copyright nor violate any proprietary rights and that any ideas, techniques, quotations
or any other material from the work of other people included in our IDP/UDP Project report,
published or otherwise, are fully acknowledged in accordance with the standard referencing practices.
Furthermore, to the extent that we have included copyrighted material that surpasses the boundary of
fair dealing within the meaning of the Indian Copyright (Amendment) Act 2012, we certify that we
have obtained a written permission from the copyright owner(s) to include such material(s) in the
current IDP/UDP Project report and have included copies of such copyright clearances to our
appendix.

We have checked the write up of the present IDP/UDP Project report using anti-plagiarism database
and it is in the allowable limit. In case of any complaints pertaining to plagiarism, we certify that we
shall be solely responsible for the same and we understand that as per norms, University can even
revoke BE degree conferred upon the student(s) submitting this IDP/UDP Project report, in case it is
found to be plagiarised.

Team:

Enrolment number Name Signature

160033107009 Anita dhnajibhai gohel

Place: Date:

MR. JAYDEEP TADHANI

ASST PROFFESOR
C. E. DEPARTMENT

vi
 CHAPTER 1. INTRODUCTION

1.1 PURPOSE
The purpose of this Document is to present the detailed description of the Online notice board. It
will explain the purpose, features, scope and interface of the system.

1.2 SCOPE:
Our application has wide range of scope below:
 School
 College
 University

1.3 OBJECTIVE:
The goal of this project a notice board gives the complete control over all hard or paper notice so
easy to student know what going on college, it gives details of event, fee schedule etc. it
became portable.

1.4 TECHNOLOGYAND TOOLS:

Back End :. SQL:
INTRODUCTION SQL (Structured Query Language) is a special-purpose programming
language designed for managing data held in a relational database management system
(RDBMS). Originally based upon relational algebra and tupple relational calculus, SQL consists
of a data definition language and a data manipulation language. The scope of SQL includes data
insert, query, update and delete, schema creation and modification, and data access control.
Although SQL is often described as, and to a great extent is, a declarative language (4GL), it also
includes procedural elements. SQL was one of the first commercial languages for Edgar F.
Codd's relational model, as described in his influential 1970 paper "A Relational Model of Data
for Large Shared Data Banks". Despite not entirely adhering to the relational model as described
by Codd, it became the most widely used database language. SQL became a standard of the
American National Stand ards Institute (ANSI) in 1986, and of the International Organization for
Standards (ISO) in 1987. Since then, the standard has been enhanced several times with added
features. But code is not completely portable among different database systems, which can lead
to vendor lockin. The different makers do not perfectly follow the standard, they add extensions,
and the standard is sometimes ambiguous.

Front End:
PHP is a server-side scripting language designed for web development but also used as a
general-purpose programming language. PHP is now installed on more than 244 million websites
and 2.1 million web servers. Originally created by Rasmus Lerdorf in 1995, the reference
implementation of PHP is now produced by The PHP Group. While PHP originally stood for
Personal Home Page, it now stands for PHP: Hypertext Preprocessor, a recursive acronym PHP
code is interpreted by a web server with a PHP processor module which generates the resulting
web page

1
CE(8046)
 CHAPTER 2. PROJECT MANAGEMENT
2.1 PROJECT PLANNING:
project planning is concerned with identifying and measuring the activities, milestone and
deliverables product by the project. Project planning is undertaken and completed sometimes
even before any development activity starts. Project planning consists of following essential
activities:
 Scheduling manpower and other resources needed to develop the system. 
 Staff organization and staffing plans.
 Risk identification, analysis, and accurate planning.

2.1.1 Project Development Approach And Justification

A software process model is simplified abstract representations of a software process which is
presented from a particular perspective. A process model for software engineering is chosen
based on the nature of the project and application, the method and tools to be used and the
controls and deliverables that are required. All software development can be characterized as a
problem solving loop which in four distinct stages is encountered 
 Requirement analysis
 Design
 Coding
 Testing
 deployment

2.1.2 Milestones and Deliverables:

Milestone is an end point of the software process activity. At each milestone there should be
formal output such as report that can be represented to the management. Milestones are the
completion of the outputs for each activity. Deliverables are the requirements definition and the
requirements specification. Milestone represents the end of the distinct, logical stage in the
project. We have divided the software process into activities for the following milestone that
should be achieved

Software Process Activity Milestone

Project Plan Project schedule
User requirements, System
Requirement Collection Requirements
Data flow analysis DFD, System flow
Design
1. database
2. face design System Design Document
Implementation Access rights
1. Code for giving security Report generation
2. Code for reports
Testing Setting validations and error messages

2
CE(8046)
2.1.3 Roles and Responsibilities:
This phase defines the role and responsibilities of each and every member involved in
developing the system. To develop this system there was only one group with one members
working on the whole application. Each member was responsible for each and every part of
developing the system.
Task Person Name

Analysis, Anita Gohel

Analysis review

Design, Anita Gohel

Design Review

Implementation Anita Gohel

Testing And Debugging Anita Gohel

Documentation Anita Gohel

Table 2.1.3.1 Roles And Responsibilities

2.1.4 Group Dependencies:

the structure chosen for the system is the chief programmer structure.in this system chief
programmer team structure is used because in the organization a senior engineer provides the
technical leadership and is designated as the chief programmer. The chief programmer partitions
the task into small activities and assign them to the team members. He also verifies and
integrates the products developed by different team members and they work under the constant
supervision of the chief programmer. For this system reporting entity represents myself and the
role of chief programmer is played by my internal guide.

2.2 PROJECT SCHEDUING:

Scheduling is the culmination of a planning activity that is primary component of software
project management. When combined with estimation methods and risk analysis, scheduling
establishes a road map for the project management. Scheduling begins with the process
decomposition. The characteristics of the project are used to adapt an appropriate task set for the
work to be done. The task network is used to compute the critical project path, a time line chart
and a variety of project information.

3
CE(8046)
2.3RISK MANAGEMNTD:
Risk management consists of a series of steps that help a software development team to
understood and manage uncertain problems that may arise during the course of software
development and can plague a software project. Risks are the dangerous conditions or potential
problems for the system which may damage the system functionalities to very high level
which would not be acceptable at any cost. so in order to make our system stable and give its
100% performance I must have identify those risks, analyze their occurrences and effects on our
system and must prevent them to occur.

2.3.1 Risk Identification

Risk identification is a first systematic attempt to specify risks to project plan, scheduling
resources, project development. It may be carried out as a team process using brainstorming
approach.

Technology Risk:
 Database corruptness
 Garbage collection
People Risk
 Leaking important data
 Lack of knowledge
 Technical staff conflict
Tools Risk:
 Tool containing virus
General Risk:
 Rapidly changing requirement
 Decision making conflict
 Insufficient planning and task identification

2.3.2 Risk Analysis “risk analysis=risk assessment +risk management +risk communication”
Risk management Evaluates which risks identified in the risk assessment process require
management and selects and implements the plans or actions that are required to ensure that
those risks are controlled. Precautions taken to make risks minimal are as under: Periodical
backups are taken to avoid major loss in case of system crash. Risk communication Involves an
interactive dialogue between stakeholders and risk assessors and risk managers which actively
informs the other processes.

4
CE(8046)
2.4 ESTIMATION
2.4.1 Effort Estimation

COUNT Average
No. Of External Inputs 7 4 28
No. Of External Outputs 4 5 20
No. Of External Inquiries 2 4 8
No. Of Internal Logical Files 4 10 40
No. Of External Interface Files 0 7 0
Count = Total 96.00
Table 2.4.1.1 Distribution of Effort

2.4.2 Cost Analysis

LOC = FP * Programming Language (Object Oriented =30)
= 95.04* 30 =
2851.2

Project Type ab bb cb db
Organic 1.8 1.01 1.7 0.25
Table 2.4.2.1Cost Analysis

5
CE(8046)
 CHAPTER 3. SYSTEM REQUIREMNT STUDY
3.1 USER CHARACTERISTICS:
Admin:
 Keep In the online notice board project all the updates like, add, delete, view are done by
admin, so that user will get the updated current information through notice board online
 To keep and track down the total number of users in the system.
 Can add, activate and deactivate any user.
 Add New Notice and send notice to Registered users
 Display Old Notice and Manage Old notice
 Update Password

User:
 The user to be registered and log in into the system before he/she carries out their
functions.
 Registration
 Login
 Check Notification sent by admin
 Update Profile
 Update Password
 Log out the whole system

3.2 HARDWARE AND SOFTWARE SPECIFICATIONS:

Hardware :
Processor : intel core i5
Ram: 1gb

Software:
Operating System: windows 8,8.1,9,10
Database: mysql
Programming language: php, html

3.3 CONSRAINS:
3.3.1 Hardware limitations:
 If the appropriate hardware is not like processor, RAM, hard disk
 The problem in processing request of client
 If appropriate storage is not there our whole database will be crash

3.3.2 Interfacing with other system

There should be compatible browser to perfectly run our portal.

6
CE(8046)
3.3.3 Reliability Requirement:
Since many user can access the server simultaneously, load on the server become very high. The
server should be of enough high configuration. There should be high back up storage and
management of huge data for overall idea, videos, images, multiple countries, and multiple user
profile.

3.3.4 Safety and Security considerations:

Safety:
The safety of the system is about organization part of concern as the system is going to be used
in there but the solution for the safety of the system, the source of this website will be kept at
more than one place with user id, password and also in the developer’s backup in case of system
crash.

Security:
As a developer of the system I are responsible for providing the system a higher level of security
as I all know that either it is application or any android application, system must be given a great
level of security so that system will be used long last.
User’s information will be kept confidential and hence security was a great part to concentrate
for us. I have tried to secure the system from any unauthorized access by providing different user
id as per his or her designation.

3.4 ASSUMPTIONS AND DEPENDENCIE:

Dependencies: The entire project de pends on end-user’s operation. They should possess enough
knowledge to work with the system.
Assumptions:
 End user is the person having enough knowledge for the project operation.
 Only administrator person has all the privileges.
 The database is correct and up-to date every time.
 The user of the system must beware about the various functionalities of the system and
all the operation of it.

7
CE(8046)
 CHAPTER 4. SYSTEM ANALYSIS:
4.1 STUDY OF CURRENT SYSTEM:
Currently our college has manual system of putting notices on notice board system it is outdated
now as nobody has a time to stand in rush in order to read the notice on notice board

4.2PROBLEMS AND LACKNESS OF CURRENT SYSTEM

 Order of data
 Complexity
 Inconsistency of data
 Damage
 Editing and communication

4.3 REQUIREMENT OF NEW SYSTEM:

4.3.1 User Requirement :

Here two type of user can use this Admin: Keep In the online notice board project all the updates
like, add, delete, view are done by admin, so that user will get the updated current information
through notice board online
 To keep and track down the total number of users in the system
 Can add activity
 Update password
User:
 Update password
 Login
 Logout
 View activity.

4.3.2 System requirement:

Usability: The interface should use terms and concept which are drawn from the experience of
the people who will make most of the system for example basic networking concept are ID.

4.4 FEASIBILITY STUDY:

An important outcome of the notice board that the system is feasible or not the main aim of the
feasibility study activity is to determine whether it would be financially and technically feasible
to develop a project the feasibility study activity involves the analysis of the problem and
collection of all relevant information relating to the product such as the different data items
which would be input to the system.

4.4.1 Does the system contribute to overall objectives of the organization?

The main aim of behind development of this system is to provide a online notice board that can
provide the notice to the students, faculty to know about college. And also provide simplicity of
design and ease of implementation that shows and help to collect most of information about
event going on in college premises.

8
CE(8046)
4.4.2 can the system be implemented using the current technology and within the given cost
and schedule constraints? The system can be easily implemented using existing technology.
The technology used is php which is user friendly and freeware. After seeing the functionality
that system provides the cost of developing the application does not matter. Taking the schedule
constrains in consideration the time available is approximately 9 months

4.4.3 can the system be integrated with other system which is already in place?
Yes the system can be integrated with other system which is already in place. If other system
wants to use our functionality it can be easily integrate.

4.5REQUIREMENT VALIDATION:
Requirement validation is concerned to check whether the requirement actually define the system
which the customer wants? Requirement validation is important because error in requirements
document can lead to extensive rework costs when they are subsequently discovered.

4.6 FEATURE OF NEW SYSTEM:

 To element wastage of time and energy.
 To avoid duplication and overlapping
 To ensure due attention of student to each and every notice
 To bring system into college life
 Searching a particular notice
 Prevent crowd in college
 Anytime anywhere service

4.7DATA FLOW DIAGRAM

REQUEST

0.0

ONLINE NOTICE
ADMIN RESPONSE REQUEST USER
BOARD

RESPONSE

Fig 4.7.1 DFD Level-0

9
CE(8046)
 give details of notice

0.1.1

ADMIN manage notice Category_notice

update notice info

delete notice info

add notice

0.1.2 0.1.3 0.1.4

Delete _notice Add_notice Update_notice

updated notice
delete notice add notice

Info_table
Info_table Info_table

Fig 4.7.2 DFD Level 1(admin)

10
CE(8046)
 give details of notice

0.1.1

user view notice View_notice

list of notice

0.1.3
give feedback 0.2.2
List_notice
feedback

listofnotice

feedback

feedback Info_table

Fig.4.7.3 DFD Level1(user)

give details of notice

1.1

ADMIN manage notice Category_notice

events details

attendance details

fees details

1.1.1 1.1.2 1.1.3

attendane Fees schedule events

Events_details
Att_table fees

Fig.4.7.3 DFD Level1.1.0

11
CE(8046)
4.8 ER DIAGRAM:
Descryption Notice_Date Id Name

Notice-id

NOTICE Add Notice Admin

View Choose

Id Student/others Choose Categoty C_name

name C_id

4.9 SELECTIOM OF HARDWARE AND SOFTWARE AND

JUSTIFICATION:
 Computer/Laptop
 Database Programming Language
 Platform to develop upon Web browsers Frameworks to code like Eclipse, Net
Beans etc
 Designing software like photoshop, Autocad etc  Gathered Information my
project
 Bluetooth / Wifi

12
CE(8046)
 CHAPTER 5. SYSTEM DESIGN
5.1 DATABASE DESIGN

As a system data model is derived, many named entities, relationships and so forth will be
identified. The names given to the entities should be chosen to give the reader some clues to
their meaning. However, further description of the named entities is usually needed to make
the model understandable. The description can be informal of the formal, whether which
approach is used. It is always worth collecting all the descriptions in a single repository or
data dictionary.

Admin:

ATTRIBUTE VALUES

ADMIN_ID INT(10)

USER EMAIL

PASS VARCHAR2(10)

LOGIN:

ATTRIBUTE VALUES

ID INT(10)

PASS VARCHAR2(20)

13
CE(8046)
NOTICE:

ATTRIBUTE VALUES

NOTICE_ID INT(10)

USER VARCHAR2(50)

SUBJECT VARCHAR2(50)

DESCRIPTION VARCHAR2(50)

DATE VARCHAR2(50)

USER:
ATTRIBUTE VALUES

ID INT(10)

NAME VARCHAR2(50)

EMAIL EMAIL

PASS VARCHAR2(50)

MOBILE VARCHAR2(50)

GENDER VARCHAR2(50)
HOBBIES VARCHAR2(50)

DOB DATE

REGID VARCHAR2(50)

14
CE(8046)
Forget password:

Attributes: values

uname Varchar(10)

email Varchar(10)

Contact us:
attribute values

name Varchar(50)

city Varchar(100)

sub Varchar(50)
msg Varchar(50)

15
CE(8046)
5.2 INPUT / OUTPUT DESIGN
HOME PAGE:

ABOUT PAGE:

16
CE(8046)
CONTACT PAGE:

REGISTRATION:

17
CE(8046)
LOGIN:

18
CE(8046)
ADMIN :

LOGIN:

UPLOAD IMAGE:

19
CE(8046)
UPDATE PASSWORD:

MANAGE USERS:

20
CE(8046)
ADD-NOTICE:

DELETE_NOTICE:

21
CE(8046)
UPDATE_NOTICE:

MANAGE NOTIFICATION:

22
CE(8046)
FORGOT PASSWORD:

USER:

PROFILE:

23
CE(8046)
NOTIFICATION:

UPDATE IMAGE:

24
CE(8046)
Update password:

25
CE(8046)
5.3 INETERFACE DESIGN:

5.3.1 State-Transition Diagram

Register

Enter pwd/id

Login

Admin Student

Insert,delete,update
View notice
notice

View notice feedback

Logout

26
CE(8046)
5.4 System Structural design:
Admin Register Login manage notice manage category

Enter Details

Generate id/pwd

Enter id/pwd

Authentication

insert,update,delete

access on notice

insert,update ,delete category

access on category

FIGURE 5.4 SEQUENCE DIAGRAM(ADMIN)

27
CE(8046)
 User Register Login View Notice View Result Feedback

Enter Details

Generate id/pwd

Enter id/pwd

Authentication

View Notice

give detalis of notice

view Result

generate result

GIve feedback

FIGURE 5.4 SEQUENCE DIAGRAM(USER)

28
CE(8046)
 Chapter 6 CODE IMPLEMENTATION

6.1 IMPLEMENTATION ENVOIREMENT:

Challenges identified for successful design and implementation of this project are dominated by:
complexity, reliability/availability, transparent data access while respecting security. The project
was a result of a group consensus. The team was having two members. The team was guided by
project manager. The team structure depends on the management style of the organization, the
no. of people in the team, their skill levels and the problem difficulty. After the completion of
each module, a module testing was performed on each. When the development was completed,
System testing was performed to test the system.

6.2PROGRAM/MODULE SPECIFICATION:

 System GUI must be as simple and user friendly as any one can use it. At front side we
implemented registration form for access the system
 Authentication is necessary to enter into the system only if one require to start his/her
own project. This is required to prevent unauthorized access to the system
 If someone steals the password of the administrator or any regular user then he can able
to change the database or misuse the system and can enter in restricted area so for this
purpose system will provide encrypted password storage format in the database. Option
to change the Password.
 A Session is maintained throughout the system when a particular user enters into the
system. The Session is regularly checked whenever it is required.
 Proper validation is placed as and when it is required.

6.3 CODING STANDARDS

Normally, good software development organization requires their programmers to adhere to

some well defined and standard style of coding called coding standard.

6.3.1 Variable Standards:

 We have used meaningful variables name.

6.3.2 comment standard

The comment should describe what is happening, how it is being done, what parameters mean,
which global are used and which are modified, and any registration or bugs. The standards I have
followed
.Every script should begin with a comment block, which describes the scripts purpose; any
argument used (if applicable), and return values (if applicable), inputs-outputs, and name of
script.

Comment may also be used in the body of the script to explain individual sections or lines of
codes.


29
CE(8046)
 CHAPTER 7:TESTING
7.1 TESTING PLAN
Testing is carried out at the following three stages :
 Design
 Implementation
 Coding
7.1.1 Design Testing:
The design errors are to be rectified at the initial stage. Such errors are very difficult to repair
after the execution of software.

7.1.2 Implementation Testing:

The errors occurred at this stage can’t be overlooked because such errors do not allow the further
process.

7.1.3 Coding Testing:

The coding procedure plays significant role in software designing. The improper coding of any
software can generate inconsistent results. Such errors may occur due to incorrect syntax or false
logic. If the errors at coding stage remain unnoticed may give rise to grave failure of the system

7.2 TESTING STATEGY:

A strategy for software testing integrates software test case design method into a well-planned
series of steps that result in the successful construction of the software.
The strategy provides the roadmap that describes the steps to be conducted as a part of testing,
then these steps are planed and then undertaken, and how much effort, time and resource will be
required.

 We have tested our whole system using bottom up testing strategy.

 Bottom up testing involves integrating and testing the modules to the lower levels in the
hierarchy, and then working up hierarchy of modules until the final module is tested.
 Bottom up testing strategy shows how actual testing is to be done with whole system but
it does not show any detail about each module testing.
 For each module testing we have decided to test each lower level module with white box
testing strategy.
 When all modules are tested successfully then I will move to one step up and continue
with white box testing strategy.

 When all modules will be tested successfully then I will integrate those modules and try
to test integrated system using black box testing strategy.
Why Black Box Testing in my Project?

In my project whatever I have implemented was going to be tested by external guide Mr.Jaydeep
tathani without knowing our code, so there was a black box testing involve directly.

30
CE(8046)
Why White Box Testing in my Project?
During the project we were making the applications, we knew how it should proceed internally;
we needed to Debugging also for testing our small functionalities.

Why interface Testing in our Project?

We examined the code to be tested and explicitly list each call to an external component. In the
system, standards tests for GUIs have been performed, which are as follows.
 Testing the screen control for its position and side.
 The position and the related labels for all controls were checked.
 Name of the form in system is given appropriately. All menu functions and sub functions
were verified for correctness.
 Validations for all input were done.
 Whether the system prompts the user with appropriate message as and when invalid
information is entered.
 All required fields aren’t left blank.


7.3 TESTING METHOD
7.3.1 Unit testing:
The unit testing is meant for testing smallest unit of software. There are two approaches namely
bottom-up and top-down.
In bottom up approach the last module is tested and then moving towards the first module while
top down approach reverses the action. In present work we opt for the first one.
The bottom up approach for the current project is carried out as shown in.

7.3.2 Integration Testing

The integration testing is meant to test all the modules simultaneously because it is possible that
all the modules may function correctly when tested individually. But they may not work
altogether and may lead to unexpected outcome.
7.3.3 Validation Testing
After the integration testing software is completely assembled as a package, interfacing error
have been uncovered and corrected, and then validation testing may begin. Validation can be
defined in many ways but a simple definition is what a validation succeeds when software
functions in a manner that can be reasonably accepted by the user.

7.3.4 Storage Testing

The database of the system has to be stored on the hard disk. So the storage capacity of the hard
disk should be enough to store all the data required for the efficient running of the system.

31
CE(8046)
7.4 TEST CASES
The purpose of this application is to reduce overhead in paper work and all the records are
maintained such that the user as well as administrator can easily segment them into desired
properties so it is easy for any novice user to have access to the application.

Login test:

Test Case Test Data Test Result Test Report

Blank Email Email Invalid Fill given detail
password Password
Invalid Email Email:- Invalid Email is
user@mail.com incorrect
Invalid Password Password : user Invalid Password is incorrect
Valid Email and Email:- valid email Valid Welcome to our site
password id
Password:-valid
password

Table 7.4.1.1 Login test

Register test:

Test Case Test Data Test Result Test Report

Blank name ,email, Name:- Invalid Fill given detail
password Email:-
Password :-
Invalid name , email , Name:abc Invalid User already
password Email : register
user@gmail.com
password:1253
Valid name , email , name:-test Valid Welcome message
password email :-
test@test.com
Password:-test

Table 7.4.1.2 Signup test

32
CE(8046)
Admin login test:

Test Case Test Data Test Result Test Report

Blank Email Email Invalid Fill given detail
password Password
Invalid Email Email:- Invalid Email is
incorrect
user@mail.com
Invalid Password Password : user Invalid Password is
incorrect
Valid Email and Email:- Valid Welcome to our
password admin@gmail.com site
Password:-admin

Table 7.4.1.3 Admin login test

33
CE(8046)
CHAPTER 8. LIMITATIONS AND FUTURE ENHANCEMENT

8.1 LIMITATIONS:
Though we tried our best in developing this system but as limitations are mere parts of
any system so are of our system. Some limitations of ―Innovator to
Investors portal are as under
 Multiple Language support
 Multiple stories can be added
 Multiple rewards can be added
 Sub categories can be added
 Multicurrency suppo

8.2 FUTURE ENHANCEMENT:

There is always a scope for enhancements in any developed system, especially when our nature
of the project is iterative waterfall which allows us to rethink on the method of development to
adopt changes in the project. Below mentioned are some of the changes possible in the future to
increase the adaptability, and efficiency of the system.
 Multiple Language support
 Multiple stories can be added
 Multiple rewards can be added
 Sub categories can be added
 Multicurrency support

34
CE(8046)
 CHAPTER 9. CONCLUSION AND DISCUSSION

9.1 SELF ANALYSIS AND PROJECT VIABILITIES

As a trainee, working in Skywebtech company was a very enrich experience.

During the period of training in Skywebtech, We have great experience of working as
professional web developer.
They will provide such a friendly environment such that many problems that we are not able to
solve before this our mind gives the answer.
Our logical power, database interaction power and dealing with the web development has
improved largely.
Our guide Niralimadam is so supported. Any query related to project ,she is always there to
guide us any time anywhere.
Our college take the time to time update regarding to our project ,such a environment make us
more punctual.

9.2 PROBLEM ENCOUNTERED AND POSSIBLE SOLUTIONS:

9.2.1 Resource Availability:
It is the most important requirement that you have powerful and useful tools to develop proper
and useful product.

9.2.2 To get the knowledge of Company:

To work with the organization and fit ourselves in that situation was very much difficult task but
with the support of my colleagues and faculty of college we manage to work and enriched our
knowledge.

9.2.3 Requirement Understanding:

The most important to build the user required and user friendly portal we have to understand
what are the needs of users those should be fulfilled by our portal.

9.2.4 Problem Encountered and Possible Solutions:

Problem:
To generate the dynamic size pictures

Solution:
Apply Image Transformation which automatically adjusts the size.

35
CE(8046)
9.3 SUMMARY OF PROJECT WORK
After doing this project work, we learn many things those we cannot learn as student as we all
know that academic work and real industrial work has big difference.

 First, we learn to analyze the problem for that we have taken the many opinions.
 Then we are in designing phase so learn to make the design user friendly.
 Then We develop the project which has the fully database communication.
 In testing phase, we think and update our portal accordingly.
 We are so lucky that in this way we can help many people and we provide the way to live
the creativity and such a projects which may helpful in environment and enhancement of
human beings and human society.
 Still learning process has never die, We will learn and improve this project in many ways.

36
CE(8046)
REFERENCE:

BOOKS:
  Database system by C.J. Date
 Software Engineering by Roger Pressman


 WEB SITES:
  Wikipedia for all topics
  DFD Diagrams from Internet
 www.w3schools.com

 www.php.net

 http://stackoverflow.com/

 www.thebetterindia.com

 www.ijcsmc.com

 www.google.in

 www.worldwidejournals.com

37
CE(8046)
 APPENDIX
A.1 BUSINESS MODEL CANVAS:

This canvas teaches us to view our project as business. Which are our partners, activities,
value propositions, customer relationship, cost structure and revenue.

38
CE(8046)
 BUSINESS MODEL CANVAS REPORT:
KEY PARTNERS:
 Finance partner:
 Marketing partner:
 Institute:
 User:
 Classes:

KEY ACTIVITIES:
 Searching for new things:
 Online fee payment:
 All details about seminar,workshop

VALUE PROPOSITIONS
 Providing social media connectivity
 Student can see all information about college
 Student can payment online fees
 Multi language support
 User friendly
 FAQS

CUSTOMER SEGMENT:
 Students
 Director
 Principle
 Professor
 Innovator
 Investors
 Faculty:

KEY RESOURES:
 PHP
 SQL database
 Html
 Browser
 Xampp

CHANNELS:
 LAPTOP
 PC

39
CE(8046)
  IPAD
 MOBILE
 TABLETS:

COST STRUCTURES:
 Buy a domain
 Web design
 Net usage
 Advertainment
 Software pushing cost
REVENUE STREAMS:
 Low cost then other website
 Trending project
 Sponsorship
 Advertainment

40
CE(8046)