Dream Buzz prj doc

Dream Buzz

1. INTRODUCTION “Dream Buzz” is a project for student/youngster who would like to achieve

their goals. Dream buzz is to build a bridge between youngster’s and their dreams.

Dreams are uneven, but generations fixing the goals to present youngsters’, which

leads to mechanical life. Youngsters should build their career as per their dreams

by using this website.

The dream buzz is a web application that is dedicated to provide the

Information regarding student’s goals. So people who would like to know the

Information related to dream and the complete details about the dream it must be

done through some steps. We will provide some articles and videos about the

dream which student chosen. Web application consists of two users, they are User

and Administrator, The main theme of the administrator is to update dreams and

add News & updates into database.

This Web application provides different features like if user wants his

parents to know complete details about his/her dream then they can request for an

email to send their parents. Any user can upload Motivational articles through

Guest Post, these posts are published after checked by the admin. Admin will send

the exam notifications to student’s emails. Dreams consists of different categories

and sub-categories. The user can select the dream by choosing category and sub-

category. According to his Dream, Step By Step process and News & Updates are

placed in his/her Dashboard. The main moto of this project is students should

succeed in their own dreams and being ideal to next generations.

ADMINISTRATOR MODULES1. Login

2. Add Category

3. Add Sub-category

4. Add Dream

5. Add News & Updates

6. Register

7. Guest Post

1

Dream Buzz

USER MODULES1. Login

2. Define Dream

3. Step By step process

4. Register

5. Motivational Articles and videos

6. Parent Confirmation Request

7. Registration Approvals

1.1EXISTING SYSTEM In the present system, there are many existence systems like sakshi education

and eenadu education but none of the them have the clear information about the

system dreams and these websites are very clumsy it is very difficult to search for

the students what they really need to set their Dream and achieve them.

Problems in the existing system

Time consuming.

Irrelevant data presented all over the webpage.

It leads to user confuse to set his goal

1.2PROPOSED SYSTEM The proposed web Application performs like a bridge between the students

and their dreams. Parents who were struggling to choose the career options for

their children by considering only job security and financial status of their

children in the future. This leads to kill passion and own thoughts of their

children. To accomplish these difficulties, we providing information regarding the

dreams and a portal namely ‘Define Your Dream’ for choosing their dreams.

After choosing the dream, his/her dashboard contains step by step process to

achieve their dream. In addition to that providing News & updates related to their

dream.

2

Dream Buzz

The website will show all information in a categorized manner. User can

View Dreams and Define them and can send feedback .Data can be managed by

operators from admin panel. Administrator can view user feedback.

Advantages of the proposed system

The development of the new system contains the following activities, which

try to automate the entire process keeping in view of the database integration

approach.

User friendliness is provided in the application with various controls.

The application should support the case of intermittent network

connectivity i.e. the student should be able to submit the feedback

form in multiple sessions (one or more responses at a time).

(Reliability and Supportability)

The form should load within 2 seconds. (Performance)

Flexible service based architecture will be highly desirable for future

extension (Supportability)

The system should be available 24 X 7. (Reliability/ availability)

3

Dream Buzz

2. REQUIREMENTS ANALYSIS

2.1 System Requirement Specification

This project is a web-based application. The hardware and software

requirements of the system are mentioned below

2.1.1 Hardware requirements

PIV 2.8 GHz Processor and Above

RAM 512MB and Above

HDD 1 GB Hard Disk Space and Above

2.1.2 Software requirements

WINDOWS OS (XP / 7 / Vista)

XAMPP Server

MYSQL

2.1.3 Working platform

Operating System: WINDOWS XP, WINDOWS 7.

2.2Software Requirements Specification

2.2.1 Vision

“Living and Dreaming are two different things but you can’t do one without

the other” said by Malcolm Forbes. The process of helping the youngsters among their

dreams by building, motivating, preparing them with outmost guidance to achieve

their dreams of all they want to be.

4

Dream Buzz

The main Purpose of Dream-Buzz is to define the Dream and achieve by

making aware what the dream really to the Youngsters. The present scenario of

Youngster’s career is in uneven way because lack of guidance, information and the

truth behind the success and failure. All these are given up by this website and

supporting to their parents which results “To Dream a Dream and Succeed”.

Example:

Generally, Parents have some dreams and they want their children to full fill

their dreams. And also every Individual have some dreams to achieve in their

life

But Most of them can’t full fill their dreams and they don’t become what they

want to be. We think this is because of lack of information and guidance.

For Such parents and Students our website build bridge to their career to

achieve their dreams

Unlike paper – based mechanism, this on-line application facilitates effective and

efficient communication, easier and informed decision making, automates and speeds

up information retrieval and report generation.

2.2.2 Glossary

Table 2.1:

AdministratorHe is the super user of the system and has all privileges.

Web User A user accessing the application using any standard web

browser and Internet Connection

Table 2.1 Glossary

2.2.3Scope

Mainly students and the present youngsters who were seeking to be success in

their dreams, are interact through GUI with the website.

As there are too many dreams, we categorized according to the present

passion, education and trend towards it. As we name it as Defining-Dream.

5

Dream Buzz

This Supporting towards the Students will be like virtual and motivational

support to their parents about their Dreams and comparison to the present

world.

We will provide the statistical information about the success and failure stories,

according to that the student/Youngster will define their own dream according

to their passion. Motivational support like Articles, videos, stories all are

submitted by anyone of the actor but approved by the Administrator.

2.2.4 System Functions

Registering every User with verified Email address and phone number.

Every user authenticated by using OTP at time of registration and every

time they logged into the website.

Defining the Dream of a User cannot be disclose to anyone until his

approval.

Only after request by Student/Youngster for Parent Confirmation, they

should provide valid contact details and the parent should registered in our

website.

The user can check his performance table every time which can upgraded

daily as per his growth.

Their will open discussions among the student, parent and admin.

The following list was proposed functionalities in this web application as shown below.

Registration

Basic information with valid E-mail address and Phone number

Unique Registration ID

Basic guidance over the Dream

Parent’s/Student’s contact information

Cancel the registration

Define Dream

6

Dream Buzz

Unique Dream ID

According to that choose his/her Dream category

Finalize his/her Dream

Modify Dream

Proper explanation to change the dream

Assistance from admin at serval stages

Although he/she want to change the dream then proceed

Modifying the unique Dream ID

Dream is Locked until it succeed

Parent conformation Request

Enter parent Registration ID

Explain the problem your facing about your dream

Get instant unique request ID

Check status of Request at any time.

Final Decision

Student Registration ID

Parent Registration ID (if any)

Dream ID

Accept of parent conformation request ID

Statement given by parent and student

Authorization given and locked the dream by administrator.

Motivational Portal

Categorized Article’s in present generation towards their successful

and failure Dreams.

Video Lectures to increase their capabilities and potential in their work

7

Dream Buzz

by authorized people.

Every Article or video have their unique id’s as per their category and

type of format

Request for Guest/user Post in the Motivational Portal

Guest/User Post

Authenticate with Email address and name (if Guest)

Authenticate through Registration ID

Setup category and write the post with proper precautions and

submitted to admin

Admin will approve after scrutiny the post and finalize to publish in

the motivational portal

2.2.5 Detailed Software Requirements

2.2.5.1 Use case model

Parent/Guardian interface to the Website provides the present world technology

and their standards, which makes their children to succeed in their Career.

Students interface consists wide varieties of courses and their details and

possibilities as per their financial support and build up their dreams. Also build

their timeline to place in good companies according their resume

Through Admin panel, admin can upload new articles, motivational videos

required information.

Actors

Actor Name Administrator

Actor Id ACT-01

Description Handles all admin related tasks throughout the application

Main ActivitiesUses the system to setup initial data, define access control,

approving student request and any posts etc.

Frequency of Use Medium

8

Dream Buzz

Work Environment /

LocationBrowser

Number of Users 1 to 3

Table 2.2Usecase model for administrator

Actor Name Student/Youngster

Actor Id ACT-03

Description Any student at any level or youngster

Main Activities

Defining his own dream related to his passion to the present

world, getting full support to make it true, request for parent

conformation on any decision, motivating at high level

towards their Dream etc.

Frequency of Use High

Work Environment /

LocationBrowser

Number of Users Any number

Table 2.3 Use case Model for Student

Actor Name Parent/Guardian

Actor Id ACT-06

DescriptionAny parent whose children want to be successful in their career in

best way.

Main ActivitiesThey get aware about the present digital world, get some important

guidelines to take care of his children career, request for post etc.,

Frequency of Use High

Work Environment /

LocationBrowser

Number of Users Any Number

Table 2.4 Use case Model for Parent

9

Dream Buzz

2.2.5.2 List of Use case

• Student/youngster

• Parent

• Admin

Use case Diagrams

Fig 2.1: Use Case Diagram for User

Use case Diagram for administrator

Fig 2.2: Use case diagram for admin

Administrator logins to the system, can add items, view items, delete

items, view orders, view feedback, logout.

10

Dream Buzz

Use case Diagram for Student

Fig 2.3: Use case diagram for Student

The above use case diagram specifies the procedure followed by student to register

and login to our website. First, the student has to Registered in website and login to our

website. He has to define the dream and follow the step by step process to achieve the dream.

After login to our website we provide some motivation articles and videos. If the student is

not satisfied with dream he/she have a option to modify a dream. If student want to take the

permission of parent then he/she made a request of parent, Then the admin can approval by

the parent.

2.2.6 Brief Use case descriptions

Use Case Name Registration

Use Case ID UC1

Actor(s) User

Goal To register the User.

Summary Customer has to register by giving his details.

Preconditions

11

Dream Buzz

Main Flow 1. The user enters the use

case.

2. User selects one of the

options: S1 or S2 or S3.

1.1Home page will be displayed.

S1. Click on registration.

S2. Complete the registration process by

entering details.

S3. Submit details.

2.1 The selected option is executed.

Sub flows 1. User selects S1. 1.1 Registration page is opened.

2. User selects S2. 2.1 Enter details.

3. User selects S3. 3.1 Submit the details.

3.2 Registration process completed.

Alternate Flows

Post Conditions Details are stored in database

Cross References S1.1,S1.2

Assumptions User must have an email id which can be used as user id.

Business Rules Only registered user can Define Their dreams.

System Sequence

Diagram

Sequen

ce diagram for registration

Table 2.5 Use case description for registration

12

Dream Buzz

Use Case Name Login

Use Case ID UC2

Actor(s) User Administrator

Goal To provide authentication for users.

Summary 1. User has to login to view step by step process of his dream.

2. Administrator has to login to manage inventory.

Preconditions

Main Flow 1. The actor enters the use

case.



1.1Actor views login page.

S1. Actor enters id and password.

S2. Actor submits credentials.


Sub flows 1. Actor selects S1. 1.1 Actor has to enter details.

2. Actor selects S2. 2.1 Actor submits credentials.

Alternate Flows

Post Conditions

Cross References S2.1,S2.2

Assumptions

Business Rules Registered user can login into the system.

13

Dream Buzz

System Sequence

Diagram

Sequence diagram for Administrator Login

Sequence diagram for user login

Table 2.6 Use case description for login

Use Case Name Inventory Management

Use Case ID UC3

Actor(s) Administrator

Goal To manage inventory.

Summary Administrator can modify inventory.

Preconditions

14

Dream Buzz

Main Flow 1. The administrator enters

the use case.

2. Administrator selects one

of the options: S1 or S2 or

S3.

1.1Administrator sees inventory

page.

S1. Add category

S2. Add sub category.

S3. Add news and updates.

S4. Add Guest Post.


Sub flows 1. User selects S1. 1.1 User can define dream in

inventory.

2. User selects S2. 2.1 User can add product details

such as product name, price,

category, image etc.

3. User selects S3. 3.1User can update details.

Alternate Flows

Post Conditions

Cross References S3.1,S3.2,S3.3

Assumptions

Business Rules

15

Dream Buzz

System Sequence Diagram

Sequence diagram for inventory management

Table 2.7 Use case description for inventory management

Use Case Name Define Dream

Use Case ID UC5

Actor(s) User

Goal To complete payment procedure.

Summary Only once it will available for every registered user

Preconditions

Main Flow 1. The user enters the use 1.1 Define Dream Procedure Starts

16

Dream Buzz

case.



by Filling the details

a. Select Category

b. Select Sub-category

c. Select Dream

d. Give Declaration


Sub flows 1. User selects S1. 1.1 Define Dream is displayed and

user selects cannot go to his

Dashboard until and unless he

entered his dream.

2. User selects S2. 2.1 User submit details.

Alternate Flows Actor can go back to home page.

Post Conditions

Cross References S5.1,S5.2,S5.3,S5.4

Assumptions

Business Rules He/she must be a registered user.

System Sequence Diagram Define Dream

17

Dream Buzz

Sequence diagram for Define Dream

Table 2.8 Use case description to Define dream

Use Case Name Feedback by User

Use Case ID UC8

Actor(s) User

Goal Users gives feedback which can be viewed by administrator

Summary Administrator views feedback list given by the user

Preconditions

Main Flow 1. The customer enters the

use case.

2. User selects the option:

S1

1.1 Customer clicks contact page

S1. Customer submits feedback

along with his/her details.


Sub flows 1. User selects S1. 1.1 User needs to fill the following

fields

a. User Name

b. Email

c. Subject

d. Rating

e. Message

Alternate Flows

Post conditions

Cross References S8.1, S8.2

18

Dream Buzz

Assumptions Registered user can give feedback

Business Rules


Sequence for user giving feedback

Table 2.9 Use case description for user feedback

Use Case Name Logout

Use Case ID UC10

Actor(s) Administrator and Customer

Goal To logout of the website

Summary Actor logs out of the system

Preconditions

Main Flow 1. The user enters the use

case.

2. User selects the option:

S1

S1. Actor clicks on logout.

2.1 The selected option is

executed.

Sub flows 1. User selects S1. 1.1 Session expires and user logs

out of website.

19

Dream Buzz

Alternate Flows

Post conditions

Cross References S9.1

Assumptions

Business Rules


Sequence diagram for admin logout

Sequence diagram for user logout

Table 2.10 Use case description for logout

2.2.7 Functional Capabilities

The administrator should be able to provide services to the user request.

These are the functions used in our project available both on back office and

front office:

Registration: User can register in to define their dreams.

Login: Both customer and administrator has to login to the system.

20

Dream Buzz

E-mail Conformation: Conformation Email also be sent to the email

address, after conforming from these two services the registration ID is

approval by the administrator.

Define Dream: After login the user have to define the dream.

Update Dream: The user can update his dream.

Motivational Port: The user and Admin can post the stories, Article

and etc..

Feedback: Feedback given by user can be viewed by administrator.

Logout: When actor clicks on “ Logout ” the session expires.

Registration only conforms after entering the OTP which was sent to his/her

registered valid phone number.

Conformation Email also be sent to the email address, after conforming from

these two services the registration ID is approval by the administrator.

Anyone can subscribe for the information provided in the website .who can

directly access the information from their email.

2.2.8 Business Rules / Validations

Administrator only approval’s the guest post, parent conformation request or

access any unrelated information all are done after validating from the

administrator.

2.2.9 Security Requirements

User Authentication:

Every user should be authenticated every time of login by sending OTP to

their registered mobile number

Access control:

For Approvals like guest post, parent conformation request, modify the dream

these should done only approval by administrator.

Non-functional requirements

The application should support the case of intermittent network connectivity

i.e. the student should be able to submit the feedback form in multiple sessions

(one or more responses at a time). (Reliability and Supportability)

21

Dream Buzz

The form should load within 2 seconds. (Performance)

Flexible service based architecture will be highly desirable for future

extension (Supportability)

The system should be available 24 X 7. (Reliability/ availability).

3. SYSTEM DESIGN

SYSTEM DESIGN phase follows analysis phase. Design is maintaining record

of proof design divisions and providing a blueprint for the implementation phase.

Design is the bridge between system analysis and system implementation.

System design is transition from a user oriented, document oriented to programmers.

The design is a solution, a “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. Design

22

Dream Buzz

goes through logical and physical stages of development; a logical design review the

present physical system, prepare input and an output specification, detail the

implementation plan, and prepares a logical design walkthrough.

Design methodology The design process for software system has two levels:

System design or Top level design

Detailed design or Logical design.

System Design In the system design the focus is on deciding which modules are needed for the

system, the specification of these modules and how these modules should be

interconnected.

Detailed Design In detailed design the interconnection of the modules or how the specification

of the modules can be satisfied is decided. Some properties for a software system

design are

1. Verifiability

2. Completeness

3. Consistency

4. Traceability

5. Simplicity / Understand ability

3.1 DATA DICTONARY

After carefully understanding the requirements of the client the the entire

data storage requirements are divided into tables. The below tables are normalized to

avoid any anomalies during the course of data entry.

23

Dream Buzz

FIELD NAME DATA TYPE DESCRIPTION CONSTRAINT

Id Number Unique Id Number

For every User

Unique

Type Enumerated Type of User

Whether Student

or Parent

Not Null

Name Text User Full Name Not Null

User Text Unique User Name

For User

Not Null

pwd Text User Define

Password

Not Null

Gen Enumerated User Define Male

or Female

Not Null

dob Date User Date of Birth Not Null

mob Number User Mobile

Number

Not Null

Email Text User Email Adders Not Null

Des Long Text Description About

User

Not Null

Str Long Text Strength Of User Not Null

wek Long Text Weakness of User Not Null

Table 3.1: Registered User

24

Dream Buzz

FIELD NAME

DATA TYPE DESCRIPTION CONSTRAINT

User Text Name of the Administrator

Unique

pwd Text Password of the Administrator

Not Null

Table3.2: Administrator Login


User Text User Name Unique

pwd Text User Password Not Null

Table3.3: User, parent Login


Did Number Unique Id Number For every New Dream

Unique

Cid Number Dream Category Foreign Key

Sid Number Dream Sub- Foreign Key

25

Dream Buzz

Category

Name Text Dream Name Not Null

Pss Long Text Step By Step Process Of Dream

Not Null

Table3.4: Dreams


Nid Number Unique id Number for every News

Unique

Dream Id Number Unique Id Number For every

Foreign Key

Title Text News Update Title Not Null

Info Long Text Detailed News Not Null

Date and Time Date and Time Date and Time Of News

Not Null

Table3.5: News Updates


Dream Id Number Unique Id Number For every User

Unique

Author Name Text Author Name Of Stories

Not Null

Title Text Stories Title Not Null

26

Dream Buzz

Info Long Text Information Regarding Stories

Not Null

Table3.6: Success and Failure Stories


Name Varchar(30) Name of the customer Not Null

phone no Varchar(30) Phone no of the customer Null

Email Varchar(30) Email id of the customer Not Null

title Varchar(30) Subject of the message Not Null

Msg Varchar(30) Feedback given by

customer

Not Null

Table3.7: Feedback


Id Number Unique Id Number For every User

Unique

uid Number Student Id Foreign Key

did Number Id of the Dream Foreign Key

Table3.8: Student and Dream


cid Number Unique Id Number For every new

Category

Unique

cname Varchar(56) Category Name Not null

Table 3.9: Category

27

Dream Buzz


sid Number Unique Id Number For every New Subcategory

Unique

cid Number Category ID Foreign Key

sname Varchar(32) Sub category Name

Not null

Table 3.10: Sub-category

3.1.1 LOGICAL DATABASE DESIGN

3.1.2.1 Normalization

It is a process of converting a relation to a standard form. The process is used

to handle the problems that can arise due to data redundancy i.e. repetition of data in

the database, maintain data integrity as well as handling problems that can arise due to

insertion, updation, deletion anomalies.

Decomposing is the process of splitting relations into multiple relations to

eliminate anomalies and maintain anomalies and maintain data integrity.

Insertion anomaly: Inability to add data to the database due to absence of other data.

Deletion anomaly: Unintended loss of data due to deletion of other data.

Update anomaly: Data inconsistency resulting from data redundancy and partial

update

3.1.2.2 Normal Forms: These are the rules for structuring relations that eliminate

anomalies.

First normal form

A relation is said to be in first normal form if the values in the relation are atomic

for every attribute in the relation. By this we mean simply that no attribute value can

be a set of values or, as it is sometimes expressed, a repeating group.

28

Dream Buzz

Second normal form

A relation is said to be in second Normal form is it is in first normal form and it

should satisfy any one of the following rules.

1) Primary key is a not a composite primary key

2) No non key attributes are present

Third normal form

A relation is said to be in third normal form if their exits no transitive

dependencies.

Transitive Dependency: If two non key attributes depend on each other as well as on

the primary key then they are said to be transitively dependent.

3.2 UML DIAGRAMS

Unified Modelling Language is the language used to visualize, specify,

construct and document any component of software engineering.

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 user’s perspective.

ii. The analysis representation describes a usage scenario from the endusers

perspective.

Structural model view

29

Dream Buzz

i. In this model the data and functionality are arrived from inside the system.

ii. 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 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

i. UML analysis modelling, which focuses on the user model and structural

model views of the system.

ii. UML design modelling, which focuses on the behavioural modelling,

implementation modelling and environmental model views.

Every complex system is best approached through a small set of

nearly independent views of a model; no single viewer is sufficient. Every

model may be expressed at different levels of fidelity. The best models are connected

to reality.

The UML includes nine such diagrams:

Static Diagrams includes

Class diagram

Object diagram

Component diagram

30

Dream Buzz

Deployment diagram

Dynamic diagrams include

Use case diagram

Sequence diagram

Collaboration diagram

State chart diagram

Activity diagram

Class diagram

A class diagram shows a set of classes, interfaces, and collaborations and their

relationships. These diagrams are the most common diagram found in modelling

object-oriented systems. Class diagrams address the static design view of a system.

Class diagrams that include active classes address the static process view of a system.

Object diagram

An object diagram shows a set of objects and their relationships. Object

diagrams represent static snapshots of instances of the things found in class diagrams.

These diagrams address the static design view or static process view of a system as do

class diagrams, but from the perspective of real or prototypical cases.

Component diagram

A component diagram shows the organizations and dependencies among a set

of components. Component diagrams address the static implementation view of a

system. They are related to class diagrams in that a component typically maps to one

or more classes, interfaces, or collaborations.

Deployment diagram

A deployment diagram shows the configuration of run-time processing nodes

and the components that live on them. Deployment diagrams address the static

deployment view of an architecture. They are related to component diagrams in that a

node typically encloses one or more components.

31

Dream Buzz

Use case diagram

A use case diagram shows a set of use cases and actors (a special kind of class)

and their relationships. Use case diagrams address the static use case view of a system.

These diagrams are especially important in organizing and modelling the behaviours

of a system.

Sequence diagram

A sequence diagrams an interaction diagram that emphasizes the time ordering

of messages. A sequence diagram shows a set of objects and the messages sent and

received by those objects. Sequence diagrams are useful design tools because they

provide a dynamic view of the system behaviour which can be difficult to extract from

static diagrams or specifications.

Collaboration diagram

Collaboration diagram is an interaction diagram that emphasizes the structural

organization of the objects that send and receive messages. Sequence diagrams and

collaboration diagrams are isomorphic, meaning that you can take one and transform it

into the other.

State chart diagram

A state chart diagram shows a state machine, consisting of states, transitions,

events, and activities. State chart diagrams address the dynamic view of a system.

They are especially important in modelling the behaviour of an interface, class, or

collaboration and emphasize the event-ordered behaviour of an object, which is

especially useful in modelling reactive systems.

Activity diagram

An activity diagram is a special kind of a state chart diagram that shows the

flow from activity to activity within a system. Activity diagrams address the dynamic

32

Dream Buzz

view of a system. They are especially important in modelling the function of a system

and emphasize the flow of control among objects.

3.3.1 Use case Diagram

Use case diagrams are created to visualize the relationships between actors

and use cases. A use case is a pattern of behaviour the system exhibits. Each use case

is a sequence of related transactions performed by an actor and the system.

Diagrammatically actor and use case are represented by the following diagrams.

Fig 3.1: Use case diagram for Admin

The above use case diagram specifies the procedure followed by

Administrator. Administrator should update the dreams, by this student can choose the

better option. He should receive the acceptance of student.

33

Dream Buzz

Fig 3.2: Use case diagram for Student

The above use case diagram specifies the procedure followed by student to

register and login to our website. First, the student has to Registered in website and

login to our website. He has to define the dream and follow the step by step process to

achieve the dream. After login to our website we provide some motivation articles and

videos. If the student is not satisfied with dream he/she have a option to modify a

dream. If student want to take the permission of parent then he/she made a request of

parent, Then the admin can approval by the parent.

Fig 3.3: Use case diagram for Parent

The above use case diagram specifies the procedure followed by parent to

login to our website. Admin should provide the motivation articles and videos to the

parent, same provide to the student too.

3.2.2Class Diagrams

A Class diagrams describe the static structure of a system, or how it is

structured rather than how it behaves. Class diagram gives an overview of a system

by showing its classes and the relationships among them. UML class is a rectangle

divided into: class name, attributes, and operations. Our class diagram has three kinds

of relationships.

Association -- a relationship between instances of the two classes. There is an

association between two classes if an instance of one class must know about

the other in order to perform its work.

34

Dream Buzz

Aggregation -- an association in which one class belongs to a collection. An

aggregation has a diamond end pointing to the part containing the whole. In

our diagram, Motivation portal has a collection of successful and failure

stories.

Generalization -- an inheritance link indicating one class is a super class of the

other

Class diagrams are widely used to describe the types of objects in a system and

their relationships. Class diagrams model class structure and contents using design

elements such as classes, packages and objects. Class diagrams describe three

different perspectives when designing a system, conceptual, specification, and

implementation. These perspectives become evident as the diagram is created and help

solidify the design. This example is only meant as an introduction to the UML and

class diagrams. If you would like to learn more see the Resources page for more

detailed resources on UML.

Classes are composed of three things: a name, attributes, and operations.

Below is an example of a class.

Fig: 3.3.2.1 Class Icon

Fig 3.3.2.2Sample Class Diagram

Class diagrams are the mainstay of object-oriented analysis and design. UML

class diagrams show the classes of the system, their interrelationships (including

inheritance, aggregation, and association), and the operations and attributes of the

35

http://atlas.kennesaw.edu/~dbraun/csis4650/A&D/UML_tutorial/resources.htm

Dream Buzz

classes. Class diagrams are used for a wide variety of purposes, including both

conceptual/domain modelling and detailed design modelling.

Fig 3.4 Class Diagram for Admin and User

The above class diagram specifies the procedure followed by user to have

functionalities and attributes of define dream, step by step process as shown in above

figure. Admin have the updating the dreams and their categories.

3.2.2 Interaction Diagrams

A type of interaction diagram, a sequence diagram shows the actors of the object

participating in an interaction and the events they generate arranged in a time

sequence. Often a sequence diagram shows the events that results from a particular

instance of a particular instance of a use case but a sequence diagram can also exist in

a more generic form. The vertical dimension in a sequence diagram represents time,

with time proceeding down the page the horizontal dimension represents different

actors.

Sequence Diagrams

Admin Login Sequence

36

Dream Buzz

Fig 3.5 Sequence diagram for admin login

Admin Inventory Management Sequence

Fig 3.6 Sequence diagram for admin inventory management

Admin View feedback Sequence

37

Dream Buzz

Fig 3.7 Sequence diagram for admin to view user feedback

Admin Logout Sequence

Fig 3.8 Sequence diagram for admin logout

User Registration Sequence

Fig 3.9 Sequence diagram for user registration

User Login Sequence

38

Dream Buzz

Fig 3.10 Sequence diagram for user loginStudent Sequence

Fig 3.11 Sequence diagram for Student

Parent Sequence

Fig 3.12 Sequence diagram for Parent

39

Dream Buzz

User Feedback Sequence

Fig 3.13 Sequence diagram for user feedback

User Logout Sequence

Fig 3.14 Sequence diagram for user logout

Collaboration Diagrams

User Logout

Fig 3.15 Collaboration Diagram for user logout

Admin feedback collaboration

40

Dream Buzz

Fig 3.16 Collaboration Diagram for admin feedback

4. MODULES4.1 MODULE DESCRIPTION

41

Dream Buzz

Informative interaction system includes two basic modules. They are

1. Admin

2. User

4.1.1 Admin

1. Login

Admin has to login to the system by giving his username and password. If the

user name is correct then admin’s home page is to be opened.

2. Administrator home

After successful login admin is redirected to home page where he/she can

perform operations which he/she wish to perform.

3. Add category

Admin can add category, the category Name is stored in the database.

4. Add Sub category

Admin can add Sub category, the Sub category Name is stored in the database.

5. Add Dream

Admin can add Dream, the Dream Name is stored in the database.

6. Add News & Updates

Admin can add News & Updates, the News & Updates is stored in the

database.

7. Register

It is the initial stage of the users. In this users can have the usernames and

passwords. In registration form there is email text field. The details are stored

in database.

4.1.2 User

1. Register

42

Dream Buzz

It is the initial stage of the users. In this users can have the usernames and

passwords. In registration form there is email text field. The details are stored

in database.

2. Login

In this users are login with the usernames and passwords which had generated

in the registration process.

3. Home

When user enters our website then home page is opened first.

4. Define Dream

User can view Dreams according to category and subcategory listed in the

website along with their details, and he/she will define their Dream.

5. Dashboard

User can view His Dashboard according to options provided listed in the

website along with their details. He also view Step By step Process to achieve

his Dream through the website

6. Guest Post

User can write the Guest Post according to category and subcategory listed in

the website along with their details.

7. Motivational Portal View

User can view all Success and failure stories of any dream, according to

category and subcategory listed in the website along with their details.

8. View News and Updates

User can view News and Updates according his Dream. Listed in the website

along with their details.

9. Send Feedback

User can send feedback regarding the Dreams along with his details.

5. SYSTEM IMPLEMENTATION

5.1Selected Software

43

Dream Buzz

PHP

PHP stands for PHP: Hypertext Pre-processor. PHP is a server-side scripting

language. PHP scripts are executed on the server. PHP supports many databases

(MySQL, Informix, Oracle, Sybase, Solid, PostgreSQL, Generic ODBC, etc.). PHP is

an open source software. PHP is free to download and use.

PHP files can contain text, HTML tags and scripts. PHP files are returned to

the browser as plain HTML. PHP files have a file extension of ".php", ".php3", or

".phtml" . PHP combined with MySQL are cross-platform we can develop in Windows

and serve on a Unix platform. PHP runs on different platforms (Windows, Linux,

Unix, etc.). PHP is compatible with almost all servers used today (Apache, IIS, etc.).

PHP code is executed on the server, and the plain HTML result is sent to the browser.

Basic PHP Syntax

A PHP scripting block always starts with <?php and ends with ?>. A PHP

scripting block can be placed anywhere in the document. Each code line in PHP must

end with a semicolon. The semicolon is a separator and is used to distinguish one set

of instructions from another. There are two basic statements to output text with PHP:

echo and print

Comments in PHP

In PHP, we use // to make a single-line comment or /* and */ to make a large

Comment block.

Variables in PHP

Variables are used for storing a values, like text strings, numbers or arrays.

When a variable is set it can be used over and over again in your script. All variables

in PHP start with a $ sign symbol.

PHP automatically converts the variable to the correct data type, depending on

how they are set .In a strongly typed programming language, you have to declare

(define) the type and name of the variable before using it. In PHP the variable is

declared automatically when you use it.

44

Dream Buzz

Strings in PHP

String variables are used for values that contains character strings. In this

tutorial we are going to look at some of the most common functions and operators

used to manipulate strings in PHP. After we create a string we can manipulate it. A

string can be used directly in a function or it can be stored in a variable.

The Concatenation Operator

There is only one string operator in PHP.The concatenation operator (.) is used

to put two string values together. To concatenate two variables together, use the dot (.)

operator.

PHP Looping

In PHP we have the following looping statements:

· while - loops through a block of code if and as long as a specified

condition is true

· do...while - loops through a block of code once, and then repeats

the loop as long as a special condition is true

· for - loops through a block of code a specified number of times

· foreach - loops through

PHP Sessions

A PHP session variable is used to store information about, or change settings

For a user session. Session variables hold information about one single user, and are

available to all pages in one application. The correct way to store and retrieve session

variables is to use the PHP $_SESSION variable.

MYSQL

45

Dream Buzz

MySQL is the most popular open-source database system. MySQL is a

database. The data in MySQL is stored in database objects called tables. A table is a

collections of related data entries and it consists of columns and rows. Databases are

useful when storing information categorically.

Create a Connection to a MySQL Database

Before you can access data in a database, you must create a connection to the

Database. In PHP, this is done with the mysql_connect() function.

Syntax:

mysql_connect(servername, username, password);

The connection will be closed automatically when the script ends. To close the

connection before, use the mysql_close() function

Syntax:

mysql_close($con);

Example syntax

<?php

$conn=mysqli_connect("localhost","root","","db");

if(! $conn)

{

die('oops connection problem ! --> '.mysql_error());

}

?>

Sample Code

Index.php

46

Dream Buzz

<?php

session_start();

include_once 'dbconnect.php';

if(isset($_SESSION['user'])!="")

{

header("Location: dash.php");

}

if(isset($_POST['btn-login']))

{

$g = $_POST ['user'];

$c = $_POST['pwd'];

$res=mysqli_query($conn,"SELECT * FROM reg WHERE user='$g'");

$row=mysqli_fetch_array($res);

if($row['pwd']==md5($c))

{

$_SESSION['user'] = $row['id'];

$x=$row['id'];

$sql="SELECT * FROM udream WHERE id='$x'";

$quer = mysqli_query($conn,$sql);

if (mysqli_num_rows($quer) != 0)

{

header("Location: dash.php");

47

Dream Buzz

}

else

{

header("Location: home.php");

}

}

else

{

?>

<script>alert('wrong details');</script>

<?php

}

}

?>

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"

"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

<html xmlns="http://www.w3.org/1999/xhtml">

<head>

<meta name="viewport" content="width=device-width, initial-scale=1">

<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />

<title>DreamBuzz- Login & Registration System</title>

<link rel="shortcut icon" type="image/png" href="/1.png">

<link rel="stylesheet" href="style.css" type="text/css" />

48

Dream Buzz

</head>

<body>

<div id="header">

<div id="left">

<label>Dream-Buzz</label>

</div>

<div id="right">

<div id="content">

<a href="default.php?Home">Home</a> <a href="about.php?about

us">About us</a> <a href="contact.php?Contact us">Contact Us</a>

</div>

</div>

</div>

<center>

<div id="login-form">

<h1> Login Form</h1>

<form method="post">

<table align="center" width="30%" border="0">

<tr>

<td><input type="text" name="user" placeholder="Your UserName" required /></td>

</tr><tr><td><input type="password" name="pwd" placeholder="Your Password"

required /></td>

</tr><tr><td><button type="submit" name="btn-login">Sign In</button></td>

49

Dream Buzz

</tr><tr><td><a href="register.php">Sign Up Here</a></td>

</tr>

</table>

</form>

</div>

</center>

<div id="footer">

<span class="smallfont">



<br />Copyright© 2016 Dream-buzz.com. All Rights Reserved.Powered by vBulletin

Version 3.8.4 Copyright ©2000 - 2016, Dream-Buzz Enterprise Ltd.

</span>

</div>

</body>

</html>

Register.php

<?php

session_start();

if(isset($_SESSION['user'])!="")

{

header("Location: home.php");

}

include 'dbconnect.php';

50

Dream Buzz

if(isset($_POST['btn-signup']))

{

$user = $_POST['user'];

$query = mysqli_query($conn,"SELECT * FROM `reg` WHERE ùser` LIKE

'$user'");

if (mysqli_num_rows($query) != 0)

{

echo '<script type="text/javascript">alert("username already exists");</script>';

}

else

{

$a = $_POST['type'];

$b = $_POST['name'];

$c = md5($_POST['pwd1']);

$d = $_POST['gen'];

$e = $_POST['dob'];

$f = $_POST['mob'];

$g = $_POST['email'];

$h = $_POST['des'];

$i = $_POST['str'];

$j = $_POST['wek'];

51

Dream Buzz

$sql = "INSERT INTO `reg` (ìd`,`type`, `name`, ùser`, `pwd`, `gen`, `dob`,

`mob`, èmail`, `des`, `str`, `wek`) VALUES (NULL,'$a','$b','$user','$c', '$d','$e', '$f',

'$g', '$h','$i','$j')";

$qry=mysqli_query($conn,$sql);

if($qry)

{

echo '<script type="text/javascript">alert(" registration succesfull");</script>';

header ("location: index.php");

}

else

{

echo '<script type="text/javascript">alert("Registration failed");</script>';

}

}

}

?>




<head>



<title>Dream Buzz-Login & Registration System</title>

52

Dream Buzz



</head>

<body>

<div id="header">

<div id="left">


</div>

<div id="right">

<div id="content">

<a href="default.php?Home">Home</a> <a href="post.php?Guest

Post">Guest Post</a> <a href="post2.php?Motivational Portal">Motivational

Portal</a> <a href="index.php?Sign in">Sign In</a> <a

href="about.php?about us">About us</a> <a href="contact.php?Contact

us">Contact Us</a>

</div>

</div>

</div>

<center>

<div align="center">



<table align="center" width="30%" border="0">

53

Dream Buzz

<h1>User Registration</h1>

<tr><td><select id="select" name="type" required><option value=""> Choose your

type</option><option value="student" name="type"> Student</option>

<option value="parent" name="type"> Parent</option></select></td>

</tr>

<tr>

<td><input name = "name" type = "text" placeholder="Enter your Name" id = "name"

required></td>

</tr>

<tr>

<td><input name = "user" pattern="\w+" placeholder="Enter User Name" type =

"text" id = "name" required></td>

</tr>

<tr>

<td><input type="password" required placeholder="Enter password" title="// at least

one number, one lowercase and one uppercase letter// at least six characters that are

letters, numbers or the underscore" pattern="(?=.*\d)(?=.*[a-z])(?=.*[A-Z]).{6,}"

name="pwd1" onchange=" this.setCustomValidity(this.validity.patternMismatch ?

this.title : '');if(this.checkValidity()) form.pwd2.pattern = this.value;"></td>

</tr>

<tr>

<td><input type="password" required placeholder="Again enter password"

title="please enter password as above" pattern="(?=.*\d)(?=.*[a-z])(?=.*[A-Z]).{6,}"

name="pwd2" onchange="this.setCustomValidity(this.validity.patternMismatch ?

this.title : ''); "></td>

54

Dream Buzz

</tr>

<tr>

<td><select id="select" name="gen" required><option value=""> Your

Gender</option><option value="male" name="gen"> Male</option>

<option value="female" name="gen"> Female</option></select></td>

</tr>

<tr>

<td>Date of Birth<input name = "dob" type ="date" id = "dob" required/></td>

</tr>

<tr>

<td><input type="text" maxlength="10" placeholder="mobile number" name="mob"

pattern="[0-9]{10}" title="enter your mobile number" required></td>

</tr>

<tr>

<td><input type="email" name="email" placeholder="Email address" required></td>

</tr>

<tr>

<td><textarea rows="1" cols="30" minlength="10" placeholder="write about

yourself..." name="des" required></textarea></td>

</tr>

<tr>

<td><textarea rows="1" cols="30" minlength="10" placeholder="write your

strengths..." name="str" required></textarea></td>

55

Dream Buzz

</tr>

<tr>

<td><textarea rows="1" cols="30" minlength="10" placeholder="write your

weakness..." name="wek" required></textarea></td>

</tr>

<tr>

<td><button type="submit" name="btn-signup">Sign Me Up</button></td>

</tr>

<tr>

<td><a href="index.php">Sign In Here</a></td>

</tr>

</table>

</form>

</div>

</center>

</div>

</body>

</html>

Home.php

<?php

session_start();

include_once 'dbconnect.php';

if(!isset($_SESSION['user']))

56

Dream Buzz

{

header("Location: index.php");

}

$g=$_SESSION['user'];

$res=mysqli_query($conn,"SELECT * FROM reg WHERE id='$g'");

$userRow=mysqli_fetch_array($res);

if(isset($_POST['btn-login']))

{

$sql="SELECT * FROM udream WHERE id='$g'";

$quer = mysqli_query($conn,$sql);

if (mysqli_num_rows($quer) != 0)

{

echo '<script type="text/javascript">alert("Dream alredy defined");</script>';

}

else

{

$a = $_POST['drm'];

$b = $_POST['dec'];

$query="INSERT INTO ùdream` (ìd`, `did`, `dec`) VALUES ('$g', '$a', '$b')";

$qrry=mysqli_query($conn,$query);

if($qrry)

{

57

Dream Buzz

echo '<script type="text/javascript">alert(" Dream Defined succesfull");</script>';

header ("location: dash.php");

}

}

}

?>




<head>



<title>Welcome - <?php echo $userRow['name']; ?></title>



<script language="JavaScript" src="myminiAJAX.js"></script>

<script language="JavaScript" src="functionsjq.js"></script>

<script language="JavaScript"

src='http://ajax.googleapis.com/ajax/libs/jquery/1.7.2/jquery.min.js'></script>

<script>

jQuery().ready(function($){

$('#loading')

.hide() // hide it initially

58

Dream Buzz

.ajaxStart(function() {

$(this).show();

})

.ajaxStop(function() {

$(this).hide();

});

// Ajax Called When Page is Load/Ready (Load cat)

jQuery.ajax({

url: 'man_list.php',

global: false,

type: "POST",

dataType: "xml",

async: false,

success: populateComp

});

//Ajax Called When You Change Manufaturer

$("#cat").change(function ()

{

resetValues();

var data = { cid :$(this).attr('value') };

jQuery.ajax({

url: 'type_list.php',

59

Dream Buzz

type: "POST",

dataType: "xml",

data:data,

async: false,

success: populateType

});

});

//Ajax Called When You Change Type of Printer

$("#scat").change(function ()

{

var data = {

cid :$('#cat').val(),

sid : $(this).attr('value')

};

jQuery.ajax({

url: 'model_list.php',

type: "POST",

dataType: "xml",

data:data,

async: false,

success: populateModel

});

60

Dream Buzz

});

//Do What You Want With Result .......... :)

$("#drm").change(function ()

{

//'you select Model='+$('#cat').val()+'type='+$('#scat').val()+'And Model='+$

('#drm').val()

//alert('you select Model = '+$('#cat option:selected').text()+' ,type= '+$('#scat

option:selected').text()+' And Model = '+$('#drm option:selected').text());

});

});

</script>

</head>

<body>

<div id="header">

<div id="left">


</div>

<div id="right">

<div id="content">

hi' <?php echo $userRow['name']; ?> <a href="default.php?

Home">Home</a> <a href="about.php?about us">About us</a> <a

href="contact.php?Contact us">Contact Us</a> <a href="logout.php?

logout">Sign Out</a>

</div>

61

Dream Buzz

</div>

</div>

<div>

<center>



<table align="center" width="auto" border="0">

<h1>Define your Dream</h1>

<tr>

<td> </td>

</tr>

<tr>

<td><select name="cat" id="cat">

<option value="">category</option>

</select>

</td>

</tr>

<tr>

<td><select name="scat" id="scat">

<option value="">sub-category</option>

</select>

<td>

62

Dream Buzz

</tr>

<tr>

<td><select name="drm" id="drm">

<option value="">Dream</option> </select></td>

</tr>

<tr>

<td><textarea rows="1" cols="30" minlength="10" placeholder="Declaretion"

name="dec" required></textarea></td></tr><tr>

<td><button type="submit" name="btn-login">Submit</button></td>

</tr></table></form>

</div>

</center>

</div>

<div id="footer">

<span class="smallfont">



<br />Copyright© 2016 Dream-buzz.com. All Rights Reserved.Powered by vBulletin

Version 3.8.4 Copyright ©2000 - 2016, Dream-Buzz Enterprise Ltd.

</span>

</div>

</body>

</html>

6. TEST CASES

63

Dream Buzz

6.1 Software testing

In any software development, testing is a process to show the correctness of

program and it needs the design specifications. Testing is needed to prove correctness

completeness, to improve the quality of the software and to provide the maintenance

aid. Some testing standards are therefore necessary to ensure completeness of testing,

improve the quality of software and reduce the testing costs and to reduce study needs

and operation time.

6.1.2 Goals of testing

The following are goals of testing…

a. Testing is a process of executing a program with the intent of finding error.

b. A good test case is the one that has a high probability of finding an as at

undiscovered error.

c. A successful test is one that uncovers an as at undiscovered error.

6.1.3 Testing Methodologies

1. Black box testing: Black Box Testing is the testing process in which tester

can perform testing on an application without having any internal structural

knowledge of application. Usually Test Engineers are involved in the black

box testing.

2. White box testing: White Box Testing is the testing process in which tester

can perform testing on an application with having internal structural

knowledge. Usually the developers are involved in the white box testing.

3. Gray box testing: Grey Box Testing is the process in which the

combination of black box and white box techniques is use.

6.1.4 Levels of testing Unit testing: Individual components are tested to ensure

that they operate correctly. Each component is tested independently without other

system components.

64

Dream Buzz

1. System testing: The sub-systems are integrated to make up the entire

system. The testing process is concerned with finding errors, which result

from un-anticipated interactions between subsystem components.

2. Integration testing: sometimes global data structures can represent the

problems to uncover errors that are associated with interfacing the

objective is to make unit test modules and built a program structure that

has been detected by design.

3. Acceptance testing: This is the final stage in the testing process before

the system is accepted for operational use. Acceptance testing may reveal

errors and omissions in the system requirements definition because real

data exercises the system in different ways from the test data.

4. Regression testing: Regression testing is actually that helps to ensure

changes that don’t introduce unintended behaviour as additional errors.

Regression testing may be conducted manually by executing a subset of

all test cases or using automated capture play back tools.

6.2 Unit Test Cases

User name and password values

65

Dream Buzz

Test case ID Input Description Expected result Pass/Fail

TC01

TC02

TC03

TC04

TC05

Username Blank

Password Blank

Username Blank

Password filled

Username filled

Password Blank

Username filled

Password filled

Username filled

Password filled

A blank Username and

password given by the

User.

A blank Username

given by the user

A blank Password

given by the user

Username and password

filled by the

Administrator

Username and password

filled by the

Administrator

Enter Correct name

Enter Correct name

Enter Correct Password

Goes to home page of the

administrator

Goes to cart page of the

customer

Fail

Fail

Fail

Pass

Pass

Table6.1: User name and password values

Registration Form

66

Dream Buzz

Test case ID

Input Description Expected result

Pass/Fail

TC01 Blank first name, last name, email, password, phone number, address.

Blank first name, last name, email, password, phone number, address is given by user

Enter correct first name

Fail

TC02 User first / last name with spaces

User id with spaces are given by user

Enter correct first / last name

Fail

TC03 User first / last name with special characters and operations like !,@,#,$,%,^,&,*,() ,_,+,.,=,- etc.

User name with special characters like !,@,#,$,%,^,&,*,() ,_,+,.,=,- by the user


Fail

TC04 User first / last name with numbers (0-9)

User name with numbers (0-9) by the user


Fail

TC05 User name characters followed by the digits

User name characters followed by the digits given by the user

Valid Pass

TC06 Blank Password Blank Password given by the user

Enter Correct Password

Fail

TC07 Password with less than 6 characters

Password with less than 6 characters given by the user

Enter correct Password

Fail

TC08 Valid Email id ,password ,first name, last name and address

Valid user name ,password ,full name and address given by the user

Valid user and registered

Pass

Table6.2: Registration form

67

Dream Buzz

7. SCREENS AND REPORTSAdmin Login

Screen7.1: Admin login

Admin Registration

Screen 7.2: Admin Registration

68

Dream Buzz

Add Category By Admin

Screen 7.3: Dream Updatation

About Us

Screen 7.4: About Us

69

Dream Buzz

Contact us

Screen 7.5: Contact Us

Feedback Form

Screen 7.6: Feedback Form

70

Dream Buzz

Motivational Portal

Screen 7.7: Motivational Portal

User Registration

Screen 7.8: User Registration

71

Dream Buzz

User Login Form

Screen 7.9: User Login Form

Define Your Dream

Screen 7.10: Define Your Dream

72

Dream Buzz

Guest Post

Screen 7.11: Guest Post

User Dashboard

Screen 7.12: My Dash Board

73

Dream Buzz

Add News & Updates

Screen 7.13:Add News

Add Dream

Screen 7.14:Add Dream

74

Dream Buzz

REPORTS

User name and password values

Test case IDInput Description Expected result Pass/Fail

TC01

TC02

TC03

TC04

Username Blank

Password Blank

Username Blank

Password filled

Username filled

Password Blank

Username filled

Password filled

A blank Username and password given by the User.

A blank Username given by the user

A blank Password

given by the user

Username and password filled by the user

Invalid Username and password

Invalid Username

Invalid Password

Goes to home page of the respective user

Fail

Fail

Fail

Pass

Table7.1: User name and password values

Email ID, Phone no values

Test case ID Input Description Expected result Pass/Fail

TC01

TC02

TC03

TC04

Email ID Blank

Email ID filled

Blank Phone no

Phone no filled

A blank Email ID field is

left by the user

Valid email ID given by

the user

A blank phone no field is left

by the user

Valid phone no given by

the user

Display that invalid Email ID

Valid Email ID

Invalid address

Valid Address

Fail

Pass

Fail

Pass

75

Dream Buzz

Table7.2: Email ID, Phone no values

8. CONCLUSION & FUTURE SCOPE

8.1 Conclusion

It has been a great pleasure for me to work on this exciting and challenging

project. The dream buzz is a web application that is dedicated to provide the

Information regard to their goal’s.so the people who would like to know the

Information related to dream and. To know the complete details about they dream it

must be done according some steps. We will provide some articles and videos about

your dream.

8.2 Limitations &Future Scope

Due to limited time, there are some limitations for the current system to which

solutions can be provided as a future development:

1. The system is not configured for multi-users at this time. The concept of transaction

can be used to achieve this.

2. The Website is not accessible to everyone. It can be deployed on a web server so

that everybody who is connected to the Internet can use it.

As for other future developments, the following can be done:

1. The Administrator of the web site can be given more functionalities, like

looking at a specific customer’s profile, maintaining the inventory of products

etc.,.

2. Choosing multiple dream not available.

76

Dream Buzz

9. BIBILOGRAPHY

S.No Book Name Author Publication Edition

1. Programming

world wide

web

Robert W.

Sebesta

Pearson

publication

8th edition

2. PHP Cook

book

Sklar, David

F.,

Trachtenberg,

Adam

O'Reilly

Media, Inc,

USA

3rd edition

Table 9.1 Books referred

S.No Site Name URL

1. MySQL Tutorial http://www.mysqltutorial.org/

2. Tutorials Point http://www.tutorialspoint.com/php/

3. W3Schools www.w3schools.com

Table 9.2 websites referred

77

http://www.w3schools.com/

http://www.amazon.com/Robert-W.-Sebesta/e/B00HTB7QPK/ref=dp_byline_cont_book_1

http://www.amazon.com/Robert-W.-Sebesta/e/B00HTB7QPK/ref=dp_byline_cont_book_1

Documents

Dream Buzz prj doc