You are on page 1of 23

The Story Keeper

L.J. Institute of Computer Application

Under the Guidance of :


Krupa Shah

Developed by :

Patel Darsh M. 205190686052


Patel Vishwa V. 205190686005
Patel Vishwa K. 205190686061
Kalathiya Jenisha R. 205190686010

Submitted To :
L J Institute of Computer Application
Acknowledgement

It is our privilege to express our sincerest regards to our faculty and project guide,
Krupa Shah for their valuable inputs, able guidance, encouragement, whole-
hearted cooperation and constructive criticism throughout the duration of our
project. We deeply express our sincere thanks to our Head of Department
Dr. Meetu Joshi for encouraging and allowing us to present the project on the
topic “The Story Keeper” at our department premises for the partial fulfillment of
the requirements leading to the award of Integrated Master of Computer
Application (IMCA) degree. We take this opportunity to thank all our lecturers
who have directly or indirectly helped our project. Last but not the least we express
our thanks to our friends for their cooperation and support.
TABLE OF CONTENTS

1.
Introduction 4

1.1 Existing System 4


1.2 Need for the New System 4
1.3 Objective of New System 4
1.4 Problem Definition 5
1.5 Core Components 5
1.6 Project Profile 6
1.7 Advantages and Limitations of the Proposed System 6
1.8 Proposed Time Line Chat 7

2.Requirement Determination & Specification 8


2.1 Requirement Determination 8
2.2 Targeted Users 9
2.3 Feasibility Analysis 9

3. System Design
3.1 Use Case Diagram 11
3.2 Class Diagram 12
3.3 Interaction Diagram 13
3.4 Activity Diagram 14
3.5 Data Dictionary 15
3.6 User Interface Design 16
3.7 Report Design 17

4 Development
4.1 Coding Standards 18
Introduction

1.1 Existing System

1.2 Need for the New System

1.3 OBJECTIVE OF THE NEW SYSTEM


The system manages information about customer’s purchase.
The customer can check his/her order history, through his/her
account. When customer login in the system they can see all the
previous data.

1.4 PROBLEM DEFINITION

The Story Keeper is a website in which we sell books through


internet. The website contains different category of books. The website
also provides preview of the book to customer. It also gives combo
offers on books .

1.5 CORE COMPONENTS

 Display books

 Search books
 Add books to cart
 Modify cart

 Remove books from cart

 Payment
1.6 PROJECT PROFILE
Project title/Definition The Story Keeper

Front-End Tools Wordpress


Back-End Tools Wordpress
Mode Online

External Project Guide Krupa Shah

Group Information Name Division- Enrollment


Roll No. number
Patel Darsh M. IMS-30 205190686052
Patel Vishwa V. IMS-40 205190686005
Patel Vishwa K. IMS-39 205190686061
Kalathiya Jenisha R. IMS-21 205190686010

1.7 ADVANTAGES AND LIMITATION OF THE


PROPOSED SYSTEM

 Advantages Of The Proposed System:-

(1) We can easily Access system Any time, Any where.

(2) We provide earliest delivery .

(3) We provide two payment option :- online and Cash on


Delivery(COD).
(4) We can see previous order History.

 Limitation Of The Proposed System:-

(1) We can’t Access System without Internet.

(2) If we forget the username and password than we can’t access the
account.

(3) The customer must have balance in the amount more then the
amount of purchase in online payment.

1.8 Proposed Time Line Chart

Week tasks Week 1 Week 2 Week 3


1. Requirement
Gathering
2. Analysis
3. Planning and
desigining
4. Coding
5. Testing
6. Documentation
Requirement Determination &
Specification

2.1 REQUIRMENT DETERMINATION


There are many available ways for requirement gathering like,

1. User Interaction
2. Similar website study
3. Questionnaire / Survey

For our system we have choose similar website study. By which,


we observed and decide the necessary requirements.
1.2 Targeted Users

1. We expect that teenagers and the people who like to read books of
different fields. So in the website we provide different categories of books.

2.3 Feasibility Analysis

1. Economic Feasibility

 Developed system is user friendly and interactive so that user


doesn’t require any training to use the system.

2. Technical Feasibility

 We have the facilities which satisfy the hardware and the software
requirements

3. Operational Feasibility
System Design

3.1 Use Case Diagram

Manage User and


Application

Manage Registration

Manage books and


new editions

Manage Login and


Logout the system

Admin
Manage Passwords

Manage Customers

Manage Payments

Use case for Admin


Various categories of
books

Book preview

Offers on Books

Wishlist and Cart


Customer

Payment Options

Manage Passwords

Use Case for Customer

3.2 Class Diagram


3.3Interaction Diagram
3.4 Activity Diagram
The Story Keeper

Start

Various categories of
Books

Add Apply for


Add to Go for
books to Offers
Cart Payment
Wishlist

Manage
Manage Books Manage Cart Manage Offers Payment

Logout

End

3.5 Data Dictionary


Field Name Data Type Constraint Description

Book_id Varchar(255) Primary key identification

Customer_firstname Varchar(50) Null First Name of customer

Customer_lastname Varchar(50) Null Last name of customer

mobile Int null Mobile number

Address Varchar(200) null Address of customer

Order Int null Amount of order

Payment_type Varchar(25) null Mode of payment

Bank_name Varchar(100) null Name of Bank


3.6 User Interface Design
3.7 Report Design
Development

4.1 Coding Standards

1. It can be used without causing harm.

2. It is reliable as it functions well and good.

3. The website is tested at the code level.

4. We used template for better design.

You might also like