SYNOPSIS

VIRTUAL SHOPPING MALL

Objective:

Using this application the Customers can buy the products using internet by sitting at home.
Usually the customers if they want to buy a products they should visit the shopping malls, go
through the prodcuts and they wish to purchase the products they does the payment and gets the
products to the home. To overcome this manual visit to the shopping malls we can use this
application to visit the shopping malls virtually and make the payment of purchase.

Existing System:

For the purchase of any items the customer needs to went to the store. He has to spend his time
there and check the items and then purchase those items. This is the manual process there is no
involvement of online process there

Disadvantages:

 This system is a manual system which doesn’t provide secure registration as well as
profile management facilities customers

 This system doesn’t provide online purchasing

 This system can’t maintain most purchased items and least purchased items

 Existing system can’t update the recent items for customers.

Proposed System:
 The development of this new system contains the following activities, which try to
develop on-line application by keeping the entire process in the view of database integration
approach.

Advantages:

 Secure registration and profile management facilities for customers

 Browsing through the email to see the items that are there in each category of
products like apparel, kitchen accessories, bath accessories, food items etc.

 Creating a shopping mart so that customer can Shop ‘n’ no of items and checkout
finally with the entire shopping cart .

 Customers should be able to mail the shop about the items they would like to see in
the shop.

 Secured mechanism for checking out from the shop.

 Updates to customers about the recent items in the shop.

 Uploading most purchased items in each category of products in the shop like
apparel, kitchen accessories, bath accessories, food items etc.

Modules:

1 Administrator

2 Customers

3 General Users

4 Web Registration

5 Search
 7 Authentication

Users

a. Administrator
b. Customer.

KEYWORDS:

Generic Technology Keywords: Database, User Interface, Programming

Specific Technology Keywords: Python ,sqlite

Project Keywords: Presentation, Business Object, Data Access Layer

SDLC Keywords: Analysis, Design, Implementation, Testing

ENVIRONMENT:

Servers:

Operating System Server: Windows

Database Server: Sqlite

Client: Google Chrome

Tools: Pycharm

Code Behind: Python

Hardware Specification:

Processor: Intel Pentium or More

RAM: 2 GB

Hard Disk: 80 GB
 SYSTEM REQUIREMENT SPECIFICATIONS FOR

BOOK SUPER STORES

PURPOSE OF THE SYSTEM

The project is fully integrated with Customer Relationship Management (CRM) solution and
developed in a manner that is easily manageable, time saving and relieving one form semi automated.

Using this application the Customers can buy the products using internet by sitting at home. Usually the
customer if they want to buy a product they should visit the shopping malls, and they wish to purchase the
product they does the payment and gets the product to the home. To overcome this manual visit to the
shopping malls we can use this application , virtually and make the payment of purchase.

In this system an Administrator is going to add a New product. The Administrator will receive the
request from the Customer as Purchase of a product. The Administrator will receive the payment from
Customer for the delivery of the product through Credit Card and reserves the product for the Customer.
Using the Courier delivery system the Administrator dispatches the product to the Customer.

The Customer at another end will register to the site, login into the system and go through the virtual
shoppingmall. He/she will select a product based on its quality and quantity of product. If the Customer
would like to purchase the product, he/she will place an order of the product. The product will delivery
status can be captured by this system. If the product courier found in a bad position, the Customer can
also raise a complaint to the Administrator for the action.

EXISTING SYSTEM

1 The existing system is a manual system. In this system user needs to save his information in the
form of excel sheets or Disk Drives.

2 There is no sharing is possible if the data is in the form of paper or Disk drives.

2 The manual system gives us very less security for saving data; some data may be lost due to
mismanagement.

3 There is no rich user interface.

4 In this system user manually visit the shopping malls to buy the products.
 5 Searching of particular information is very critical it takes lot of time.

6 There is no communication facility between users of this system.

7 The users cannot able to restrict the information.

8 There is no report generation.

PRPOSED SYSTEM

The development of the new system objective is to address the solutions for the drawbacks of existing
problem domain.

The development of this new system contains the following activities, which try to automate the entire process
keeping in the view of database integration approach.

1 User Friendliness is provided in the application with various controls provided by system Rich User
Interface.

2 The system makes the overall project management much easier and flexible.

3 It can be accessed over the Intranet.

4 It provides email facility between users of this system.

5 The customers, orders and books information files can be stored in centralized database which can be
maintained by the system.

6 In this system customer can visit the book stalls virtually and select the books.

8 Authentication is provided for this application only registered users can access.

10 There is no risk of data management at any level while the project development is under process.

11 Report generation feature is provided to generate different kind of data reports.

Advantages for Customers

For Customer of this application, advantages primarily concern access, time, and cost factors compared to
those incurred from attending as manual.

Customer can able to search the products. Mails can be archived in this application for instant reviewing,
which is another advantage to Customer.
STUDY OF THE SYSTEM

In the flexibility of uses the interface has been developed a graphics concepts in mind, associated through
a browser interface. The GUI’s at the top level has been categorized as follows

1. Administrative User Interface Design

2. The Operational and Generic User Interface Design

The administrative user interface concentrates on the consistent information that is practically, part of
the organizational activities and which needs proper authentication for the data collection. The Interface helps
the administration with all the transactional states like data insertion, data deletion, and data updating along with
executive data search capabilities.

The operational and generic user interface helps the users upon the system in transactions through the
existing data and required services. The operational user interface also helps the ordinary users in managing their
own information helps the ordinary users in managing their own information in a customized manner as per the
assisted flexibilities.

NUMBER OF MODULES

The system after careful analysis has been identified to be presented with the following modules:

2 Administrator

3 Customers

4 General Users

5 Web Registration

6 Search

7 Reports

8 Authentication
Administrator

Administrator is treated as a super user in this system. He can have all the privileges to do anything in this
system.

1 He is the person who can Add the product s and courier services.
2 He can Manage the prouct details.
2 He has a facility to communicate with other Customers using email.
3 He can take care of Backup of Customers, Order details and maintain history.
4 He is able to generate the reports of Customers and Orders.

Customers

5 They have a facility to register to the site with their Personal data.
6 Being a Customer (after registration) should able to Order products

7 They have a facility to communicate with Admin through email.

9 They are able to see their orders status and delivery status.

General Public

9. General Public (i.e. Guest visitors) are able to access the site Home page, Registration Page, etc. common
pages of the site.

10. This user can able to see the product details in different Categories.

11. They are able to search the products.

Web Registration

The system has a process of registration. Every User need to submit his complete details in the form of
registration. Whenever a User registration completed automatically he/she can get a user id and password. By
using that user id and password he/she can log into the system.

Search:
 This system provides search facility to the users. Users can search for the products

Reports

Different kind of reports is generated by the system.

1 Customers Report

2 Orders Report

Authentication:

Authentication is nothing but providing security to the system. Here every must enter into the
system throw login page. The login page will restrict the UN authorized users. A user must provide his credential
like user Id and password for log into the system. For that the system maintains data for all users. Whenever a
user enters his user id and password, it checks in the database for user existence. If the user is exists he can be
treated as a valid user. Otherwise the request will throw back.

INPUTS AND OUTPUTS

The major inputs and outputs and major functions of the system are follows:

Inputs:
 1 Admin enter his user id and password for login

2 Admin enter the product details.

3 User enters his user id and password for login.

4 User Registration to order products.

5 New user gives his completed personnel, address and phone details for registration.

6 Administrator gives information to generate various kinds of reports.

Outputs:

2 Admin get all Customers details.

3 Admin can view all order details.

4 Users can view their orders.

5 User can search the products based on categories.

7 Admin get the search details of different criteria.

8 Different kind of reports is generated by administrator.

SDLC METHDOLOGIES

This document play a vital role in the development of life cycle (SDLC) as it describes the complete
requirement of the system. It means for use by developers and will be the basic during testing phase. Any
changes made to the requirements in the future will have to go through formal change approval process.

SPIRAL MODEL was defined by Barry Boehm in his 1988 article, “A spiral Model of Software Development
and Enhancement. This model was not the first model to discuss iterative development, but it was the first
model to explain why the iteration models.

As originally envisioned, the iterations were typically 6 months to 2 years long. Each phase starts with a
design goal and ends with a client reviewing the progress thus far. Analysis and engineering efforts are
applied at each phase of the project, with an eye toward the end goal of the project.
The steps for Spiral Model can be generalized as follows:

1 The new system requirements are defined in as much details as possible. This usually involves
interviewing a number of users representing all the external or internal users and other aspects of the
existing system.

2 A preliminary design is created for the new system.

3 A first prototype of the new system is constructed from the preliminary design. This is usually a
scaled-down system, and represents an approximation of the characteristics of the final product.

4 A second prototype is evolved by a fourfold procedure:

1. Evaluating the first prototype in terms of its strengths, weakness, and risks.

2. Defining the requirements of the second prototype.

3. Planning an designing the second prototype.

4. Constructing and testing the second prototype.

1 At the customer option, the entire project can be aborted if the risk is deemed too great. Risk factors
might involved development cost overruns, operating-cost miscalculation, or any other factor that
could, in the customer’s judgment, result in a less-than-satisfactory final product.

2 The existing prototype is evaluated in the same manner as was the previous prototype, and if
necessary, another prototype is developed from it according to the fourfold procedure outlined
above.

3 The preceding steps are iterated until the customer is satisfied that the refined prototype represents
the final product desired.

4 The final system is constructed, based on the refined prototype.

5 The final system is thoroughly evaluated and tested. Routine maintenance is carried on a continuing
basis to prevent large scale failures and to minimize down time.
The following diagram shows how a spiral model acts like:
 Fig 1.0-Spiral Model

ADVANTAGES:

1 Estimates(i.e. budget, schedule etc .) become more relistic as work progresses, because important
issues discoved earlier.

2 It is more able to cope with the changes that are software development generally entails.

3 Software engineers can get their hands in and start woring on the core of a project earlier.

INPUT DESIGN

Input design is a part of overall system design. The main objective during the input design as given below:

1 To produce cost-effective method of input

2 To achieve the highest possible level of accuracy.

3 To ensure that the input is acceptable and understood by the user.

Input States:

The main input stages can be listed as below:

1 Data recording

2 Data transcription

3 Data conversion

4 Data verification

5 Data control

6 Data transmission

7 Data validation
 8 Data correction

Input Types:

It is necessary to determine the various types of input. Inputs can be categorized as follows:

1 External Inputs which are prime inputs for the system.

2 Internal Inputs, which are user communications with the systems.

3 Operational, which are computer department’s communications to the system?

4 Interactive, which are inputs entered during a dialogue.

Input Media:

At this stage choice has to be made about the input media. To conclude about the input media consideration has
to be given to:

1 Type of Input

2 Flexibility of Format

3 Speed

4 Accuracy

5 Verification methods

6 Rejection rates

7 Ease of correction

8 Storage and handling requirements

9 Security

10 Easy to use

11 Portability

Keeping in view the above description of the input types and input media, it can be said that most of the inputs are
of the form of internal and interactive. As input data is to be directly keyed in by the user, the keyboard can be
considered to be the most suitable input device.

OUTPUT DESIGN:
Outputs from computer systems are required primarily to communicate the results of processing to users. They
are also used to provide a permanent copy of the results for later consultation. The various types of outputs in
general are:

1 External Outputs, whose destination is outside the organization,.

2 Internal Outputs whose destination is within organization and they are the
 User’s main interface with the computer.

3 Operational outputs whose use is purely within the computer department.

4 Interface outputs, which involve the user in communicating directly with User Interface.
Output Definition:

The outputs should be defined in terms of the following points:

 Type of the output

 Content of the output

 Format of the output

 Location of the output

 Frequency of the output

 Volume of the output

 Sequence of the output

It is not always desirable to print or display data as it is held on a computer. It should be decided as which form of
the output is the most suitable.

For Example

1 Will decimal points need to be inserted

2 Should leading zeros be suppressed.

Output Media:

In the next stage it is to be decided that which medium is the most appropriate for the output. The main
considerations when deciding about the output media are:
 1 The suitability for the device to the particular application.
2 The need for a hard copy.
3 The response time required.
4 The location of the users
5 The software and hardware available.

Keeping in view the above description the project is to have outputs mainly coming under the category of
internal outputs. The main outputs desired according to the requirement specification are: The outputs were
needed to be generated as a hot copy and as well as queries to be viewed on the screen. Keeping in view these
outputs, the format for the output is taken from the outputs, which are currently being obtained after manual
processing. The standard printer is to be used as output media for hard copies.

TEST CASES

A test case is a set of input data and an expected result that exercises the
component with the purpose of causing failures and detecting faults. Test cases are
classified into black box test and white box test. Black box test focus on
input/output behavior of the component. White box test focus on internal structure
of the components.

TEST CASE EXECUTION AND ANALYSIS

ADMIN Login:

TEST CASE CONDITIONS BEING EXPECTED OBSERVED STATUS

CHECKED BEHAVIOUR BEHAVIOUR
User Check validation Display a Display a Pass
name=”XYZ” message message
 wrong user wrong user
name name
Password=” “ Existence of Display a Display a pass
mandatory fields message to fill message to fill
all empty man all empty man
datary fields datary fields
User Existence of man If valid user it If valid user it pass
name=”XYZ” datary fields displays home displays home
page else page else error
Password=”123”
error message message

NORMAL USER REGISTRATION

TEST CASE CONDITIONS BEING EXPECTED OBSERVED STATUS

CHECKED BEHAVIOUR BEHAVIOUR
First name=” “ Existence of Display a Display a Pass
mandatory fields message to fill message to fill
all empty man all empty man
datary fields datary fields
Fax Check validation Enter values Enter values pass
number=”abc” according to according to
their data their data
types types
First Check the validation Gets Gets pass
name=”abc” and form is completely registration registration
filled or not
Fax
number=”123”

NORMAL USER LOGIN:

TEST CASE CONDITIONS BEING EXPECTED OBSERVED STATUS

CHECKED BEHAVIOUR BEHAVIOUR

User name=”abc” Check validation Display a Display a Pass

message message
wrong user wrong user
name name
Password=” “ Existence of mandatory Display a Display a pass
fields message to fill message to fill
all empty man all empty man
datary fields datary fields
User name=”abc” Existence of mandatory If valid user it If valid user it pass
fields displays home displays home
Password=”777”
page else page else
error message error message

INTRODUCTION
 Software testing is a critical element of software quality assurance and represents the ultimate review of
specification, design and coding. In fact, testing is the one step in the software engineering process that could be
viewed as destructive rather than constructive.

A strategy for software testing integrates software test case design methods into a well-planned series of
steps that result in the successful construction of software. Testing is the set of activities that can be planned in
advance and conducted systematically. The underlying motivation of program testing is to affirm software quality
with methods that can economically and effectively apply to both strategic to both large and small-scale systems.

STRATEGIC APPROACH TO SOFTWARE TESTING

The software engineering process can be viewed as a spiral. Initially system engineering defines the role of
software and leads to software requirement analysis where the information domain, functions, behavior,
performance, constraints and validation criteria for software are established. Moving inward along the spiral, we
come to design and finally to coding. To develop computer software we spiral in along streamlines that decrease the
level of abstraction on each turn.

A strategy for software testing may also be viewed in the context of the spiral. Unit testing begins at the
vertex of the spiral and concentrates on each unit of the software as implemented in source code. Testing progress
by moving outward along the spiral to integration testing, where the focus is on the design and the construction of
the software architecture. Talking another turn on outward on the spiral we encounter validation testing where
requirements established as part of software requirements analysis are validated against the software that has been
constructed. Finally we arrive at system testing, where the software and other system elements are tested as a whole.

UNIT TESTING

MODULE TESTING

Component Testing
SUB-SYSTEM TESING

Integration Testing SYSTEM TESTING

ACCEPTANCE TESTING
User Testing
UNIT TESTING

Unit testing focuses verification effort on the smallest unit of software design, the module. The unit testing we
have is white box oriented and some modules the steps are conducted in parallel.

1. WHITE BOX TESTING

This type of testing ensures that

 All independent paths have been exercised at least once

 All logical decisions have been exercised on their true and false sides
 All loops are executed at their boundaries and within their operational bounds
 All internal data structures have been exercised to assure their validity.
To follow the concept of white box testing we have tested each form .we have created independently to
verify that Data flow is correct, All conditions are exercised to check their validity, All loops are executed on their
boundaries.

2. BASIC PATH TESTING

Established technique of flow graph with Cyclomatic complexity was used to derive test cases for all the functions.
The main steps in deriving test cases were:

Use the design of the code and draw correspondent flow graph.

Determine the Cyclomatic complexity of resultant flow graph, using formula:

V(G)=E-N+2 or

V(G)=P+1 or

V(G)=Number Of Regions

Where V(G) is Cyclomatic complexity,

E is the number of edges,

N is the number of flow graph nodes,

P is the number of predicate nodes.

Determine the basis of set of linearly independent paths.

3. CONDITIONAL TESTING

In this part of the testing each of the conditions were tested to both true and false aspects. And all the resulting paths
were tested. So that each path that may be generate on particular condition is traced to uncover any possible errors.

4. DATA FLOW TESTING

This type of testing selects the path of the program according to the location of definition and use of variables. This
kind of testing was used only when some local variable were declared. The definition-use chain method was used in
this type of testing. These were particularly useful in nested statements.

5. LOOP TESTING

In this type of testing all the loops are tested to all the limits possible. The following exercise was adopted for
all loops:

All the loops were tested at their limits, just above them and just below them.

All the loops were skipped at least once.

For nested loops test the inner most loop first and then work outwards.

For concatenated loops the values of dependent loops were set with the help of connected loop.

Unstructured loops were resolved into nested loops or concatenated loops and tested as above.

Each unit has been separately tested by the development team itself and all the input have been validated.

TEST CASES

1 Test Case 1 – Login

Test 1:

 Incorrect input: An empty requirement field. (user name and password)

 Pass criteria: An appropriate error message should be displayed and the user shouldn’t be
allowed to login.
 Correct input: Right user name and password.
 Pass criteria: The user should be directed to the secure web page which the user is
requested.
Test 2:

 Incorrect input: Wrong user name and/or wrong password.

  Pass criteria: The user shouldn’t be allowed to login to the system and an appropriate error
message should be displayed.
 Correct input: Right user name and password.
 Pass criteria: The user should be login to the system and directing to the requested secure
web page.

2 Test Case 2 – New User Register

 Incorrect input: An empty requirement field. (first name, last name, middle name, Photo,
address, Date Of Birth, phone number, user name, password, e-mail address)
 Pass criteria: An appropriate error message should be displayed and the user shouldn’t be
allowed to create an account.
 Correct input: Fill in all requirement fields in correct format.
 Pass criteria: The user information should be added into the database.

Test Case 3 – Generate Report (Customer)

Test 1:

 Incorrect input: An empty requirement field. (Select Date)

 Pass criteria: An appropriate error message should be displayed and the user should not be
able to generate a report.
 Correct input: Enter(Select) Correct Date
 Pass criteria: The user (admin) should be allowed to generate the report.

State Chart Diagrams:

State chart for Login Form:

 Click On Login Form

Login form
With Empty Fields

Enter details

Login form
Form with Fields

Click On Login Button

Validation

State chart for Registration Form:

 Click on Registration Form
Registration Form
With Empty Fields

Enter Details of the Form

Registration Form
Form with Data

Click On Submit
Save

Click On Home
 CONTEXT LEVEL DIAGRAM

USERS ADMINISTRATOR

eCommerce

REGISTRATION
REPORTS ,
AUTHENTICATION

APPLICATION DEVELOPMENT:
N-Tier Applications:

N-Tier Applications can easily implement the concepts of Distributed Application Design and Architecture. The N-
Tier Applications provide strategic benefits to Enterprise Solutions. While 2-tier, client-server can help us create
quick and easy solutions and may be used for Rapid Prototyping, they can easily become a maintenance and
security night mare

The N-tier Applications provide specific advantages that are vital to the business continuity of the enterprise.
Typical features of a real life n-tier may include the following:

1 Security

2 Availability and Scalability

3 Manageability

4 Easy Maintenance

5 Data Abstraction

The above mentioned points are some of the key design goals of a successful n-tier application that intends to
provide a good Business Solution.

Definition:

Simply stated, an n-tier application helps us distribute the overall functionality into various tiers or layers:

1 Presentation Layer

2 Business Rules Layer

3 Data Access Layer

4 Database/Data Store

Each layer can be developed independently of the other provided that it adheres to the standards and
communicates with the other layers as per the specifications.

This is the one of the biggest advantages of the n-tier application. Each layer can potentially treat the other layer
as a ‘Block-Box’.
In other words, each layer does not care how other layer processes the data as long as it sends the right data in a
correct format.

Fig 1.1-N-Tier Architecture

1. The Presentation Layer:

Also called as the client layer comprises of components that are dedicated to presenting the data to the
user. For example: Windows/Web Forms and buttons, edit boxes, Text boxes, labels, grids, etc.

2. The Business Rules Layer:

This layer encapsulates the Business rules or the business logic of the encapsulations. To have a separate
layer for business logic is of a great advantage. This is because any changes in Business Rules can be easily
handled in this layer. As long as the interface between the layers remains the same, any changes to the
functionality/processing logic in this layer can be made without impacting the others. A lot of client-server
apps failed to implement successfully as changing the business logic was a painful process.

3. The Data Access Layer:

This layer comprises of components that help in accessing the Database. If used in the right way, this layer
provides a level of abstraction for the database structures. Simply put changes made to the database,
tables, etc do not affect the rest of the application because of the Data Access layer. The different
application layers send the data requests to this layer and receive the response from this layer.
 4. The Database Layer:

This layer comprises of the Database Components such as DB Files, Tables, Views, etc. The Actual
database could be created using SQL Server, Oracle, Flat files, etc.
In an n-tier application, the entire application can be implemented in such a way that it is independent of
the actual Database. For instance, you could change the Database Location with minimal changes to Data
Access Layer. The rest of the Application should remain unaffected

PERFORMANCE REQUIREMENTS:

Performance is measured in terms of the output provided by the application. Requirement specification plays an
important part in the analysis of a system. Only when the requirement specifications are properly given, it is
possible to design a system, which will fit into required environment. It rests largely in the part of the users of the
existing system to give the requirement specifications because they are the people who finally use the system.
This is because the requirements have to be known during the initial stages so that the system can be designed
according to those requirements. It is very difficult to change the system once it has been designed and on the
other hand designing a system, which does not cater to the requirements of the user, is of no use.

The requirement specification for any system can be broadly stated as given below:

 The system should be able to interface with the existing system

 The system should be accurate
 The system should be better than the existing system
The existing system is completely dependent on the user to perform all the duties.

FEASIBILITY REPORT:

Preliminary investigation examine project feasibility, the likelihood the system will be useful to the
organization. The main objective of the feasibility study is to test the Technical, Operational and Economical
feasibility for adding new modules and debugging old running system. All system is feasible if they are unlimited
resources and infinite time. There are aspects in the feasibility study portion of the preliminary investigation:

1 Technical Feasibility
2 Operation Feasibility
3 Economical Feasibility

Technical Feasibility

The technical issue usually raised during the feasibility stage of the investigation includes the following:
 1 Does the necessary technology exist to do what is suggested?
2 Do the proposed equipments have the technical capacity to hold the data required to use the new
system?
3 Will the proposed system provide adequate response to inquiries, regardless of the number or location of
users?
4 Can the system be upgraded if developed?
5 Are there technical guarantees of accuracy, reliability, ease of access and data security?
Earlier no system existed to cater to the needs of ‘Secure Infrastructure Implementation System’. The current
system developed is technically feasible. Thus it provides an easy access to the users. The database’s purpose is to
create, establish and maintain a workflow among various entities in order to facilitate all concerned users in their
various capacities or roles. Permission to the users would be granted based on the roles specified. Therefore, it
provides the technical guarantee of accuracy, reliability and security. The work for the project is done with the
current equipment and existing software technology. Necessary bandwidth exists for providing a fast feedback to
the users irrespective of the number of users using the system.

Operational Feasibility

Proposed projects are beneficial only if they can be turned out into information system. That will meet the
organization’s operating requirements. Operational feasibility aspects of the project are to be taken as an
important part of the project implementation. Some of the important issues raised are to test the operational
feasibility of a project includes the following: -

1 Is there sufficient support for the management from the users?

2 Will the system be used and work properly if it is being developed and implemented?
3 Will there be any resistance from the user that will undermine the possible application benefits?
This system is targeted to be in accordance with the above-mentioned issues. Beforehand, the management issues
and user requirements have been taken into consideration. So there is no question of resistance from the users
that can undermine the possible application benefits.

The well-planned design would ensure the optimal utilization of the computer resources and would help in the
improvement of performance status.

Economic Feasibility

A system can be developed technically and that will be used if installed must still be a good investment for the
organization. In the economical feasibility, the development cost in creating the system is evaluated against the
ultimate benefit derived from the new systems. Financial benefits must equal or exceed the costs. The system is
economically feasible. It does not require any addition hardware or software. Since the interface for this system is
developed using the existing resources and technologies. There is nominal expenditure and economical feasibility
for certain.

Component Diagram

Component diagram is a special kind of diagram in UML. The purpose is

also different from all other diagrams discussed so far. It does not describe the
functionality of the system but it describes the components used to make those
functionalities.

So from that point component diagrams are used to visualize the physical
components in a system. These components are libraries, packages, files etc.

Component diagrams can also be described as a static implementation view

of a system. Static implementation represents the organization of the components
at a particular moment.

A single component diagram cannot represent the entire system but a

collection of diagrams are used to represent the whole.
 Registration Login Get Product
Details

Bill Payment Get Request Status Request for Product

DFD Diagrams
Context Level Diagram (O Level)
Login DFD

UserRegistration

Enter User User Home

Open Login Yes Yes
Name and Check User Page
form
Password

No

Verify Data

Admin Activities DFD

1st Level

2nd Level
Customer Activities

1st Level
2nd Level

Mails Master
Mails Master

Display Inbox Display Outbox

1.4.2 1.4.3

Manage Mails
1.4.1

Compose Mails Mails Master

1.4.4

Log out
UML DIAGRAMS
Use Case Diagrams :

SYSTEM NAME

Use case 1

Use case 2
Actor
Actor

Use case n
Over All System Use Case Diagram:

Activity Diagrams:

Registration Activity Diagram:

 [Enter
Registration
Get Details
Details]

[submit]

Validate Data

Accepted

[Success Fully Registered]

Login Activity Diagram:

 [Enter User Name and Password]

Get Details

[Submit]

Validate Data

Rejected No yes Accepted

Admin Activity Diagram:
Customer Activity Diagram
General User Activity
State Chart Diagrams:
State chart for Login Form:

Click On Login Form

Login form
With Empty Fields

Enter details

Login form
Form with Fields

Click On Login Button

Validation
State chart for Registration Form:

Click on Registration Form

Registration Form
With Empty Fields

Enter Details of the Form

Registration Form
Form with Data

Click On Submit
Save

Click On Home
Sequence Diagrams
User Registration Sequence

frmRegistration BL:cls_User DAL:cls_SqliteHelper Database

User

Response()
Login Sequence

User LoginPage AuthenticationService() DAL:SqliteHelper() Database

Open Login Form

ValidateUser()
Admin Sequence to Add Products Categories

Admin frm Products BAL:cls DAL:clsSqliteHelper DataBase

Categories Products

Response()

Show Result()
Admin Sequence to Add ProductDetails

Admin frm Products Details BAL:cls Products DAL:clsSqliteHelper DataBase

: Enter Products Details

: Insert Products Details()

: Response()

: Show Result()
Customer Sequence to View Products

Customer frm Products List BAL:cls DAL:clsSqlITEHelper DataBase

Products

: Select Category

: Get Products ()

: Response()

: Show Result()
Customer Sequence to Order Products

Customer frmOrder BAL:cls DAL:clsSqliteHelper DataBase

Products

: Select Products

: Order Products ()

Response()

6: Show Result()
General User Sequence to Search Products

User frmHome BAL:cls DAL:clsSqliteHelper DataBase

Products

Show Result()
Collaboration Diagrams

Login

4 : ExecuteStoredProcedure()

DAL:clsSqliteHel DB
per

3 : ExecuteNonQuery()

BAL:clsLogin

2 : Insert Data()

5 : Response()
frmLogin

1 : Enter UserId,Pwd()

User
Admin Collaboration to Add Categories

4 : ExecuteStoredProcedure()
DB DAL:clsSqliteHelpe
r

3 : ExecuteNonQuery()

BAL:cls Products

2 : Insert Category()

frm Products Categories

5 : Response()

1 Enter Data

Admin
Admin Collaboration to Add Product Details

4 :Execute StoredProcedure()

DAL:clsSqliteHelpe
DataBase r

3 : ExecuteNonQuery()

BAL:cls Products

2 : Insert ProductsDetails()

frm Products Details

5 : Response()

1 : Enter Book Details

Admin
Customer Collaboration to View Products

4 : ExecuteStoredProcedure()

DAL:clsSqliteHel DB
per

3 : ExecuteDataset()

BAL:cls Products

2 : Get Products ()

5 : Response()
frm Products List

1 : Select Category

Customer
Customer Collaboration to Order Products

4 : ExecuteStoredProcedure()
DAL:clsSqliteHelp DB
er

3 : ExecuteNonQuery()

5 : Response()

BAL:cls Products

2 : Order Products()

frmOrder

1 : Select
Products

Customer
General User Collaboration to Search Products

DB

4 : ExecuteStoredProcedure()

DAL:clsSqliteHelpe
r

5 : Response()
3 : ExecuteDataset()

BAL:clsProducts

2 : Get Products()

FrmHome

1 : Enter Title/Author/Publisher

User