Digital Tunes

1. INTRODUCTION
1.1 Introduction & Objective
The “Digital-Tunes” application is web application. It is a virtual showcase of audio and
video CDs for any customer in different categories like GHAZHAL, FILM, POP,
DEVOTIONAL, ROCK, CLASSICAL and FOLK etc. The main aim of this project is to
make Online shopping very easy.

1.2 Purpose Of the Project

It provides online interface to the public to purchase audio cassettes through online Based up on
its categories what they are interested.

1.3 Existing System

In general, whenever any customer wants to purchase audio or video CDs, he/she has to go to
outlets (cd shops), but there is no compulsion that every customer will find all the cd’s what they
want, in that case they have to go to the other shops for those products. It will increase the round
trips between each and every outlet. To avoid above problem and to give more services to the
customer we have introduced an internet-based application regarding online purchase of audio and
video CDs.

1.4 Proposed System

The “Digital-Tunes” application is an online website. It is a virtual showcase of audio and video
CDs for any customer in different categories like GHAZHAL, FILM, POP, DEVOTIONAL,
ROCK, CLASSICAL and FOLK etc. The main aim of this project is to make Online shopping
very easily. The Special thing about this project is that provides different types of cds to purchase.
User can communicate with administrator of this portal for any enquiries are complains about
products by using message service which is provided to him/her, at the same time administrator
also can send messages to the customers. The purpose of this project is as follows:

 To present the variety of items category wise to the customer.

 To get member information and collect order information from the customer to display the
list of ordered items to the administrator.

1
 Digital Tunes

2. SYSTEM OVERVIEW
2.1 Study Of the System
To provide flexibility to the users, the interfaces have been developed that are accessible through
a browser. The GUI’S at the top level have been categorized as 1. Administrative user interface 2.
The operational or generic user interface.
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.
These interfaces help the administrators with all the transactional states like Data insertion, Data
deletion and Date updating along with the extensive data search capabilities.

The ‘operational or generic user interface’ helps the end users of 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 in a customized manner as per the included flexibilities

2.2 Input & Output Representation

Input design is a part of overall system design. The main objective during the input design is as
given below:
 To produce a cost-effective method of input.
 To achieve the highest possible level of accuracy.
 To ensure that the input is acceptable and understood by the user.

Input Stages
The main input stages can be listed as below:
 Data recording
 Data transcription
 Data conversion
 Data verification
 Data control
 Data transmission
 Data validation

2
 Digital Tunes

 Data correction

Input Types
It is necessary to determine the various types of inputs. Inputs can be categorized as follows:
 External inputs, which are prime inputs for the system.
 Internal inputs, which are user communications with the system.
 Operational, which are computer department’s communications to the system.
 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;
 Type of input
 Flexibility of format
 Speed
 Accuracy
 Verification methods
 Rejection rates
 Ease of correction
 Storage and handling requirements
 Security
 Easy to use
 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 the directly
keyed in by the user, the keyboard can be considered to be the most suitable input device.

3
 Digital Tunes

Output Design
In general, are:
 External Outputs whose destination is outside the organization.
 Internal Outputs whose destination is with in organization and they are the User’s main
interface with the computer. 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
 Operational outputs whose use is purely with in the computer department.
 Interface outputs, which involve the user in communicating directly with the system.
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.
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:
 The suitability for the device to the particular application.
 The need for a hard copy.
 The response time required.
 The location of the users
 The software and hardware available.

4
 Digital Tunes

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

5
 Digital Tunes

3. LITERATURE SURVEY

Preliminary investigation examines 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
systems are feasible if they are given unlimited resources and infinite time. There are aspects in
the feasibility study portion of the preliminary investigation:
 Technical Feasibility
 Operation Feasibility
 Economic Feasibility

3.1 Technical Feasibility

The technical issue usually raised during the feasibility stage of the investigation includes the
following:
 Does the necessary technology exist to do what is suggested?
 Do the proposed equipment’s have the technical capacity to hold the data required to
usethe new system?
 Will the proposed system provide adequate response to inquiries, regardless of the
number or location of users?
 Can the system be upgraded if developed?
Are there technical guarantees of accuracy, reliability, ease of access and data security?

3.2 Operational Feasibility

User-friendly: Customer will use the forms for their various transactions i.e., for adding new
routes, viewing the routes details. Also, the Customer wants the reports to view the various
transactions based on the constraints. These forms and reports are generated as user-friendly to the
Client.

Reliability: The package wills pick-up current transactions on line. Regarding the old transactions,
User will enter them in to the system.

Security: The web server and database server should be protected from hacking, virus etc.

6
 Digital Tunes

Portability: The application will be developed using standard open-source software (Except
Oracle) like Java, tomcat web server, Internet Explorer Browser etc. this software will work
both on Windows and Linux o/s. Hence portability problems will not arise.

Availability: This software will be available always.

Maintainability: The system called the wheels uses the 2-tier architecture. The 1st tier is the
GUI, which is said to be front-end and the 2nd tier is the database, which uses My-Sql, which
is the back-end. The front-end can be run on different systems (clients). The database will be
running at the server. Users access these forms by using the user-ids and the passwords.

3.3 Economic Feasility

The computerized system takes care of the present existing system’s data flow and procedures
completely and should generate all the reports of the manual system besides ahost of other
management reports.
It should be built as a web-based application with separate web server and database server.
This is required as the activities are spread throughout the organization customer wants a
centralized database. Further some of the linked transactions take place in different locations.
Open-source software like TOMCAT, JAVA, MySQL and Linux is used to minimize the cost
for the Customer.

7
 Digital Tunes

4. SYSTEM ARCHITECTURE
Architecture flow
Below architecture diagram represents mainly flow of requests from users to database through
servers. In this scenario overall system is designed in three tires separately using three layers
called presentation layer, business logic layer and data link layer. This project was developed
using 3-tier architecture.

User

Request Response

Data
Base

Fig.4.1ArchitectureFlow

8
 Digital Tunes

URL Pattern

Presentation
Layer

Response sent URL Request

from the sent through the
servlet browser

Reply from the Verifying or

database updating the
according to the database through a
statement statement

Fig.4.2 URL Pattern

URL pattern represents how the requests are flowing through one layer to another layer and how
the responses are getting by other layers to presentation layer through server in architecture
diagram.
9
 Digital Tunes

4.1 Functional Requirements Specification

This application consists following modules.
1. User Module
2. Admin Module
3. Shopping cart Module
4. Reports Module
1. User Module
This module tells all about customers and their responsibilities while accessing Digital-
Tunes Music Store portal, whenever user wants to get access of this portal he must register and by
using login-id, password he can enter in to this portal. Here user can search for different categories
of CDs. This module consists following categories.
Film: By using this functionality any user can search for different types of film CDs based on
price wise and singer wise.
Ghazal: By using this functionality any user can search for different types of Ghazal CDs based
on price wise and singer wise.
Pop: By using this functionality any user can search for different types of POP CDs based on price
wise and singer wise.
Devotional: By using this functionality any user can search for different types of Devotional CDs
based on price wise and singer wise.
Rock: By using this functionality any user can search for different types of Rock CDs based on
price wise and singer wise.
Classical: By using this functionality any user can search for different types of Classical CDs
based on price wise and singer wise.
Folk: By using this functionality any user can search for different types of folk CDs based on price
wise and singer wise.
These categories represent different types of audios and video CDs which are available in this
portal. In this module any user can view all the products but they can’t do other operations like
add, modify and deleting items and they can purchase those items by using credit card.

10
 Digital Tunes

Credit Card Interface:

Through this interface, application will validate credit card. “Digital-Tunes” application will
allow three types of credit card. They are Visa Card, Master Card, and Amex card (American
Express).

2. Admin Module

This module is belonging to administrator, he/she can do any operations on user accounts and
they will control all users in the portal like they can give access permeations to them by
providing username and password at the same time they can add products list, modify products
list and delete products list from the portal. Any customer can’t view the products until unless
administrator will add the product details in the portal through this module. Administrator can
get any messages from the customers and at same time he/she can give reply for those messages
also.

Place the CDs to the shop: By using this functionality administrator can add all different
types of CDs related to films, Ghazal’s, pop, Devotional, Classical, Devotional, Rock and
folk songs to the portal.

Handling Messages: By using this functionality administrator can send messages to any
user or they can view messages from other users also

3. Shopping cart Module

Shopping cart module contains the items that a user has selected for purchasing. The shopping cart
page of the “Digital-Tunes” application will display a list of products selected by the user. User
can add the items to that list by clicking the check box next to the items and then clickingon the
add to wish list button, they can also specify the quantity of the items. This interface is having
following sub functionalities
Add Products to Shopping cart: By using this functionality customer can add different no.of
CDs to the cart.
Modify Products to shopping cart: By using this functionality customer can modify all product
details which are available in shopping cart before purchasing CDs.
Delete Products from the Shopping cart: By using this functionality customer can delete any
CD which are added to the shopping cart before purchasing only.

11
 Digital Tunes

4. Reports Module:
In this module administrator will get different types of reports regarding customers like Number
of customers of this portal, daily selling reports and no. of messages he/she is getting etc. And this
module is controlled by administrator only.
Reports On total available Users: By using this functionality administrator can view all
customers who are registered in this portal.
Reports On total Placed Orders: By using this functionality administrator can view all order
details from different no. of customers.
Reports On Available of CDs: By using this functionality administrator can view all available
CDs in this portal.

4.2 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 with 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.

4.3 Software Requirements

Operating System : Windows
Technology : Java/j2ee (JDBC, Servlets, JSP)
Web Technologies : Html, JavaScript, CSS
Web Server : Tomcat

12
 Digital Tunes

Database : Oracle
Software’s : J2SDK1.5, Tomcat 5.5, Oracle 9i

4.4 Hardware Requirements

Hardware : Pentium based systems with a minimum of P4
RAM : 256MB (minimum)

4.5 Data Flow Diagrams

USER Digital Tunes ADMINISTRATOR

DB

Fig.4.5.1 DFD Level-0 For E-Music World

Forgot User login info

Visitor Password

Fig.4.5.2 DFD level-0 for Forgot Password

13
 Digital Tunes

Search
Regd:User CDs to Prod info
Order

Fig.4.5.3 DFD level-0 for Search CDs to buy

Shipping Details

Buy Now Bill Shopping Cart

Transaction

Fig.4.5.4 DFD level-0 for Billing Process

14
 Digital Tunes

Regd: User Change User login info

Password

Fig.4.5.6 DFD level-0 for Change Password of the Red: User

Number
Validation
Credit Card Credit check

Type Validation

Fig.4.5.7 DFD Level –1 for Credit Card Interface

15
 Digital Tunes

5. UML DIAGRAMS

Unified Modeling Language:

The Unified Modeling Language allows the software engineer to express an analysis model
using the modeling 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 diagrams, which is as follows.
 User Model View
This view represents the system from the user’s perspective.
The analysis representation describes a usage scenario from the end-user’s perspective.
 Structural model view
In this model the data and functionality are arrived from inside the system.
This model view models the static structures.
 Behavioral Model View
It represents the dynamic of behavioral 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 behavioral as parts of the system are represented as they are to
be built.
 Environmental Model View
In these the structural and behavioral aspects of the environment in which the system is to
be implemented are represented.
UML is specifically constructed through two different domains they are:
 UML Analysis modeling, this focuses on the user model and structural model views of
the system.
 UML design modeling, which focuses on the behavioral modeling, implementation
modeling and environmental model views.
Use case Diagrams represent the functionality of the system from a user’s point of view. Use cases
focus on the behavior of the system from external point of view. Actors are external entities that
interact with the system.

16
 Digital Tunes

Fig.5.1 use case diagram

17
 Digital Tunes

Fig.5.2 State Diagram for Searching

18
 Digital Tunes

Fig.5.3 State Diagram for modifying searched Attributes

19
 Digital Tunes

Fig.5.4 Class Diagram

20
 Digital Tunes

5.5 Sequence Diagram

Fig.5.5.1 Customer

Customer

21
 Digital Tunes

Fig.5.5.2 Admin

22
 Digital Tunes

5.6. Normalization
A Database is a collection of interrelated data stored with a minimum of redundancy to serve many
applications. The database design is used to group data into a number of tables and minimizes the
artificiality embedded in using separate files. The tables are organized to:

Reduced duplication of data.

Simplify functions like adding, deleting, modifying data etc..,
Retrieving data
Clarity and ease of use
More information at low cost

Normalization is built around the concept of normal forms. A relation is said to be in a particular
normal form if it satisfies a certain specified set of constraints on the kind of functional
dependencies that could be associated with the relation. The normal forms are used to ensure that
various types of anomalies and inconsistencies are not introduced into the database.
First Normal Form
A relation R is in first normal form if and only if all underlying domains contained atomic values
only.

Second Normal Form

A relation R is said to be in second normal form if and only if it is in first normal form and every
non-key attribute is fully dependent on the primary key.
Third Normal Form:
A relation R is said to be in third normal form if and only if it is in second normal form and
every non key attribute is non transitively depend on the primary key.

23
 Digital Tunes

6. TESTING

6.1 Testing

Testing is the debugging program is one of the most critical aspects of the computer programming
triggers, without programming that works, the system would never produce an output of which it
was designed. Testing is best performed when user development is asked to assist in identifying
all errors and bugs. The sample data are used for testing. It is not quantity but quality of the data
used the matters of testing. Testing is aimed at ensuring that the system was accurately an
efficiently before live operation commands.
Testing objectives
The main objective of testing is to uncover a host of errors, systematically and with minimum
effort and time. Stating formally, we can say, testing is a process of executing a program with
intent of finding an error.
1.A successful test is one that uncovers an as yet undiscovered error.
2.A good test case is one that has probability of finding an error, if it exists.
3.The test is inadequate to detect possibly present errors.
4.The software more or less confirms to the quality and reliable standards.
Levels of Testing
In order to uncover present in different phases we have the concept of levels of testing.
Specification Testing
Executing this specification starting what the program should do and how it should perform under
various conditions. Test cases for various situation and combination of conditions in all the
modules are tested.
Unit Testing
In the unit testing we test each module individually and integrate with the overall system. Unit
testing focuses verification efforts on the smallest unit of software design in the module. This is
also known as module testing. The module of the system is tested separately. This testing is carried
out during programming stage itself. In the testing step each module is found to work satisfactorily
as regard to expected output from the module. There are some validation checks for

24
 Digital Tunes

fields also. For example, the validation check is done for varying the user input given by the
userwhich validity of the data entered. It is very easy to find error debut the system.
Each Module can be tested using the following two Strategies:
1.Black Box Testing
2. White Box
Testing

6.2 Black Box Testing

What is Black Box Testing?
Black box testing is a software testing technique in which functionality of the software under
test (SUT) is tested without looking at the internal code structure, implementation details and
knowledge of internal paths of the software. This type of testing is based entirely on the software
requirements and specifications. In Black Box Testing we just focus on inputs and output of the
software system without bothering about internal knowledge of the software program. The above
Black Box can be any software system you want to test. For example: an operating system like
Windows, a website like Google, a database like Oracle or even your own custom application.
Under Black Box Testing, you can test these applications by just focusing on the inputs and outputs
without knowing their internal code implementation.
Black box testing - Steps Here are the generic steps followed to carry out any type of Black Box
Testing. Initially requirements and specifications of the system are examined.
Tester chooses valid inputs (positive test scenario) to check whether SUT processes them
correctly. Also, some invalid inputs (negative test scenario) are chosen to verify that the
SUT is able to detect them. Tester determines expected outputs for all those inputs.
Software tester constructs test cases with the selected inputs. The test cases are executed.
Software tester compares the actual outputs with the expected outputs. Defects if any
are fixed and re-tested.
Types of Black Box Testing
There are many types of Black Box Testing but following are the prominent ones -
Functional testing – This black box testing type is related to functional requirements
of a system; it is done by software testers.
Non-functional testing – This type of black box testing is not related to testing of a
specific functionality, but non-functional performance, scalability, usability.

25
 Digital Tunes

Regression testing – Regression testing is done after code fixes, upgrades or any
other system maintenance to check the new code has not affected the existing code.

6.3 White Box Testing

White Box Testing is the testing of a software solution's internal coding and
infrastructure. It focuses primarily on strengthening security, the flow of inputs and
outputs through the application, and improving design and usability. White box testing
is also known as clear, open, structural, and glass box testing.
It is one of two parts of the "box testing" approach of software testing. Its counter-part,
Blackbox testing, involves testing from an external or end-user type perspective. On the
other hand, Whitebox testing is based on the inner workings of an application and
revolves around internal testing. The term "Whitebox" was used because of the see-
through box concept. The clear box or Whitebox name symbolizes the ability to see
through the software's outer shell (or "box") into its inner workings. Likewise, the "black
box" in "black box testing" symbolizes not being able to see the inner workings of the
software so that only the end-user experience can be tested.
What do you verify in White Box Testing?
 White box testing involves the testing of the software code for the following:
 Internal security holes
 Broken or poorly structured paths in the coding processes
 The flow of specific inputs through the code
 Expected output
 The functionality of conditional loops
 Testing of each statement, object and function on an individual basis
The testing can be done at system, integration and unit levels of software development. One of the
basic goals of Whitebox testing is to verify a working flow for an application. It involves testing a
series of predefined inputs against expected or desired outputs so that when a specific input does
not result in the expected output, you have encountered a bug.

26
 Digital Tunes

How do you perform White Box Testing?

To give you a simplified explanation of white box testing is of two basic steps.
Step 1) Understand the Source Code
The first thing a tester will often do is learn and understand the source code of the
application. Since white box testing involves the testing of the inner workings of an
application, the tester must be very knowledgeable in the programming languages used
in the applications they are testing. Also, the testing person must be highly aware of
secure coding practices. Security is often one of the primary objectives of testing
software. The tester should be able to find security issues and prevent attacks from
hackers and naive users who might inject malicious code into the application either
knowingly or unknowingly.
Step 2) Create Test Cases and Execute
The second basic step to white box testing involves testing the application’s source code
for proper flow and structure. One way is by writing more code to test the application’s
source code. The tester will develop little tests for each process or series of processes in
the application. This method requires that the tester must have intimate knowledge of
the code and is often done by the developer. Other methods include manual testing, trial
and error testing and the use of testing tools as we will explain further on in this article.

6.4 System testing:

Once the individual module testing is completed, modules are assembled and integrated
to perform as a system. The top-down testing, which began from upper levelto lower-
level module, was carried out to check whether the entire system is performing
satisfactorily.
1. Alpha Testing: This refers to the system testing that is carried out by the test team with the
Organization.
2. Beta Testing: This refers to the system testing that is performed by a selected group of friendly
customers
3. Acceptance Testing: This refers to the system testing that is performed by the customer to
determine whether or not to accept the delivery of the system

27
 Digital Tunes

7. SCREENSHOTS

28
Digital Tunes

29
Digital Tunes

30
Digital Tunes

31
Digital Tunes

32
Digital Tunes

33
Digital Tunes

34
Digital Tunes

35
Digital Tunes

36
Digital Tunes

37
Digital Tunes

38
 Digital Tunes

8. REFERENCES
1. https://www.youtube.com/watch?v=ZVTpKCgFmAA
2. https://1000projects.org/digital-tunes-java-project-abstract.html
3. https://en.wikipedia.org/wiki/Online_music_store

39
 Digital Tunes

9. BIBLIOGRAPHY

 Java Technologies

 Java Complete Reference

 Java Script Programming by Yehuda Shiran

 Mastering Java Security

 Java2 Networking by Pistoria

 Java Security by Scotl Oaks

 Head First Ejb Sierra Bates

 J2ee Professional by Shadab Siddiqui

 Java Server Pages by Larne Pekowsley

 Java Server Pages by Nick Todd

 Html Black Book by Holzner

 Software Engineering by Roger Pressman

 Java Database Programming with Jdbc by Patel Moss.

40