ON

ON LINE MUSIC

THE ONLINE MUSIC

Submitted under partial fulfillment of the requirement for the award of degree of Three year full time

Master of Computer Application

Submitted To: Sanjay Kumar Singh Reader , RSMT, U.P. College Varanasi

Submitted By:Hrishi Kesh Tiwari Enrl. No. 062622184 Prog: MCA (4th Sam)

ABSTRACT
The Online Music is a web based application intended for online users. The main objective of this application is to make it interactive and its ease of use. It would make searching, viewing and selection of a song easier. It contains a sophisticated search engine for user's to search for specific to their needs. The search engine provides an easy and convenient way to search for music where a user can search for music interactively and the search engine would refine the music available based on the users input. The user can then view the complete specification of each music. The application also provides a drag and drop feature so that a user can add a music to the music cart by dragging the item in to the music cart. The main emphasis lies in providing a user-friendly search engine for effectively showing the desired results and its drag and drop behavior.

PREFACE
This project on Online Music is recommended by us as. The proposed system for the above discussed existing system easily provides a solution to the biggest problem of going global and still not opening the stores in all parts of the world with the local music through the sites website. Maintenance and addition of further features are also cost effective in terms of the profits obtained. This project e-Music developed to provide the enhancement to the music website. This project helps in making the e-Music facility very easy and comfortable to the website visitors. In this project all the necessary and required facilities are available which makes it convenient to the customers to make music on the website. There are very good number of music websites available on the internet, but it has some extra, different important features which make this music website different from other websites. In addition the site also provides several features for the administrators and for the Newsletters of the new music.

Acknowledgement
Apart from the efforts of us, the success of any project depends largely on the encouragement and guidelines of many others. At the outset, we take the privilege

to convey our sincere gratitude to those whose co-operation; suggestions and support helped me to accomplish the project work successfully. I would like to show my greatest appreciation to Lecturer Mr.Sanjay Singh, RSMT. I cant say thank you enough for his tremendous support and help. I feel motivated and encouraged every time through his guidance. Without his encouragement and guidance this project would not have materialized. Our efforts in accomplishing this project are a result of constant motivation and patient listening support by them. The knowledge provided by them have been a great value for us and will go a long way in shaping our promising careers. Also we would like to express our special thanks to our Co-coordinator Mr. Gunjan Srivastava and all the faculty members for their constant help for the completion of the project. Their ever available encouragement and enlightening guidance has been of immense help towards the successful completion of the project. Lastly, I offer my regards and blessings to our family & friends and all of those who supported and provided us the moral support without which it was impossible to complete the project Date...........................

PROJECT
Before starting the project we should fully know about the meaning of project. There are seven letters in the word PROJECT each character has its own technical meaning.

Planning

This deal with the idea at thinking and which are required for the project.

Resource Operating

The money problem will be solved and resources from which collected.

The procedure from which the getting job is prepared in a systematic way is known as operation.

Joint effort

This is directly proper to a operation output is made of several person working sincerely is known as JOINT EFFORT.

Engineering

A well-educated engineer can do this work in a better way to find out better result. Hence the project is as engineering function.

Co-operation

To make the project successfully, it is necessary for its success and completion of project.

Technique

It must as it gives a better shape. It is not possible to complete the project without technique. The project is a system that gives the systematic way of planning and working.

Table of Contents
1) INTRODUCTION......9-11 i) INTRODUCTION..10 ii) OVERVIEW OF EMART..11 2) OBJECTIVES...12-14 3) SOFTWARE DEVELOPMENT LIFE CYCLE...15-23 i) SDLC ....16

ii) SDLC WATERFALL MODEL.....18 iii) SDLC STAGES......19 4) MODULAR ANALYSIS.....24-26 5) SYSTEM ANALYSIS......27-31 i) FUNCTIONAL REQUIREMENTS......29 ii) NON FUNCTIONAL REQUIREMENTS....31 6) HARDWARE & SOFTWARE SPECIFICATION .32-34 i) DESIGN CONSTRAINTS.....33 ii) SECURITY CONSTRAINTS....34 7) SOFTWARE REQUIREMENT SPECIFICATION(SRS)...35i) SOFTWARE REQUIREMENT SPECIFICATION(SRS).35 ii) DEVELOPMENT ENVIRONMENT....36 (1) ABOUT MISCROSOFT .NET FRAMEWORK. 36 iii) OVERVIEW .NET FRAMEWORK..37 (1) MICROSOFT.NET FRAMEWORK.......38 iv) COMMON LANGUAGE RUNTIME...39 v) .NET FRAMEWORK CLASS LIBRARY ...40 vi) CLIENT APPLICATION DEVELOPMENT....41 vii) SERVER APPLICATION DEVELOPMENT...42 viii) INTRODUCTION TO ASP.NET.....43 ix) ORACLE DATABASE......45 8) FEATURES ...48 9) FEASIBILITY ANALYSIS..50-58 i) FEASIBILITY ANALYSIS INTRO.51 ii) ECONOMICAL FEASIBILITY ..56 iii) TECHNICAL FEASIBILITY ..56 iv) OPERATIONAL FEASIBILITY .57 v) BEHAVOURIAL FEASIBILITY ....58 10) DATA FLOW DIAGRAM..59-58 i) DFD...60 ii) 0 LEVEL DFD..........64 iii) EXPLAINATION OF 0 LEVEL DFD..65 iv) 1 LEVEL DFD MODULE 1 .67

v) 1 LEVEL DFD vii) 2 LEVEL DFD viii)

MODULE 2..68 MODULE 1.....71 MODULE2.72

vi) EXPLAINATION OF 1 LEVEL DFD ...69-70 2LEVEL DFD

ix) EXPLAINATION OF 2 LEVEL DFD.73 11) ER DIAGRAM74-78 i) ER DIAGRAM.79 ii) EXPLAINTION OF ER DIAGRAM80 12) DATABASE DESIGN ...65-71 i) DATABASE DESIGN.....81 ii) OBJECTIVE OF DATABSE...83 iii) DATA DICTIONARY....84-87 13) PROBLEM STATEMENTS88-74 i) DEMERITS OF THE EXISTING SYSTEM89 ii) MERITS OF THIS APPLICATION.90 14) FUTURE ENHANCEMENT91 i) FUTURE SCOPE....92-93 15) CONCLUSION94-95 16) BIBLIOGRAPHY96-97

INTRODUCTION

INTRODUCTION
Title of the Project: OnLine Music System Music is probably more familiar than we might at first imagine. Indeed, nowadays it is all around us, whether it be in restaurants, supermarkets, lifts, for advertising or as theme and incident a music on television. Hearing live music is one of the

most pleasurable experiences available to human beings. The music sounds great, it feels great, and you get to watch the musicians as they create it. No matter what kind of music you love, try listening to it live. There are lots of things to enjoy at a concert, lots of things to pay attention to. Your job is to be affected by the music, but you can be affected by what most appeals to you, or by whatever grabs your interest. Here are a few choices for what to listen to. Choose whatever you like, switch as often as you want, and feel free to add to the list.

Some things to enjoy in classical music Moods and feelings Loudness and softness Different speeds Instrument sounds Melodies Rhythms Changes and transformations Beautiful performing Memories that get triggered Recognition of something heard earlier Visual images that come to mind

OBJECTIVES

Objective
Music Online is a one stop hangout for movies. At Music Online , we believe and swear by the term Filmy and we have tried to live up to its true spirit. Music Online is designed for people like you - the hard core movie buffs, enthusiasts and even those who claim that they dont have a filmy bone in their body. Dont miss our special attempts to focus on regional and bollywood movies!

There are various reasons for you to hangout at Music Online Besides becoming a member of Indias largest movie rental service and renting good quality movies from Music Online , you can just sign in and indulge by taking the quiz or creating one, rating movies, starting a club, testing your movie compatibility with your friends or simply read more about the movies and review them. Now, enjoy movies and a lot more at your finger tips!. Music Online Hangout is your space, you can decide on who to let in and who not to, what to put up there and what not to. You are the leading person in your hangout, so get set - wear the Directors cap! Music Online is shaping (or shaking) up a couple of things around here. We thought that it was about time we indulged in movies, rather than just watching them. And so we have just expanded our canvas and we invite you to discover, enjoy, share and indulge in the world of movies! We have scrubbed, shined and polished our website and filled it with as much color and content to keep you watching and indulging. If you are not at Seventymm, you are not rolling. We have mapped out the best laid plans, and the red carpet welcome so have you arrived yet?

SOFTWARE DEVELOPMEN T LIFE CYCLE

SDLC
The Software Development LifeCycle (SDLC) for small to medium database application development efforts. The objective of developing models is providing more steps to improve the software. The linear sequential model is the oldest and the most widely used paradigm for software engineering. SDLC is the process of developing information systems through investigation, analysis, design, implementation and maintenance. SDLC is also known as information systems development or application development. SDLC is a systems

approach to problem solving and is made up of several phases, each comprised of multiple steps:

The software concept - identifies and defines a need for the new system A requirements analysis - analyzes the information needs of the end users The architectural design - creates a blueprint for the design with the necessary specifications for the hardware, software, people and data resources Coding and debugging - creates and programs the final system System testing - evaluates the system's actual functionality in relation to expected or intended functionality.

To manage this, a number of system development life cycle (SDLC) models have been created: waterfall, fountain, spiral, build and fix, rapid prototyping, incremental, and synchronize and stabilize. The oldest of these, and the best known, is the waterfall: a sequence of stages in which the output of each stage becomes the input for the next. These stages can be characterized and divided up in different ways, including the following:

Project planning, feasibility study: Establishes a high-level view of the intended project and determines its goals. Systems analysis, requirements definition: Refines project goals into defined functions and operation of the intended application. Analyzes enduser information needs. Systems design: Describes desired features and operations in detail, including screen layouts, business rules, process diagrams, pseudo code and other documentation.

Implementation: The real code is written here. Integration and testing: Brings all the pieces together into a special testing environment, then checks for errors, bugs and interoperability. Acceptance, installation, deployment: The final stage of initial development, where the software is put into musicion and runs actual business. Maintenance: What happens during the rest of the software's life: changes, correction, additions, moves to a different computing platform and more. This, the least glamorous and perhaps most important step of all, goes on seemingly forever.

THE SDLC WATERFALL

The classic life cycle or THE WATERFALL MODEL, the linear sequential model suggests a systematic, sequential approach to software development that begins at the system level and progresses through analysis, design, coding, testing, and support.Small to medium database software projects are generally broken down into six stages :-

The relationship of each stage to the others can be roughly described as a waterfall, where the outputs from a specific stage serve as the initial inputs for the following stage. During each stage, additional information is gathered or developed, combined with the inputs, and used to produce the stage deliverables. It is important to note that the additional information is restricted in scope; new ideas that would take the project in directions not anticipated by the initial set of high-level requirements are not incorporated into the project. Rather, ideas for new capabilities or features that are out-of-scope are preserved for later consideration. After the project is

completed, the Primary Developer Representative (PDR) and Primary End-User Representative (PER), in concert with other customer and development team personnel develop a list of recommendations for enhancement of the current software.

SDLC STAGES
The six stages of the SDLC are designed to build on one another, taking the outputs from the previous stage, adding additional effort, and producing results that leverage the previous effort and are directly traceable to the previous stages. This top-down approach is intended to result in a quality music that satisfies the original intentions of the customer.

PLANNING STAGE The planning stage establishes a bird's eye view of the intended software music,and uses this to establish the basic project structure, evaluate feasibility and risks associated with the project, and describe appropriate management and technical approaches. The most critical section of the project plan is a listing of high-level music requirements, also referred to as goals. All of the software music requirements to be developed during the requirements definition stage flow from one or more of these goals. The minimum information for each goal consists of a title and textual description, although additional information and references to external documents may be included. The outputs of the project planning stage are the configuration management plan, the quality assurance plan, and the project plan and schedule, with a detailed listing of scheduled activities for the upcoming Requirements stage, and highlevel estimates of effort for the out stages. REQUIREMENTS DEFINITION STAGE The requirements gathering process takes as its input the goals identified in the high-level requirements section of the project plan. Each goal will be refined into a set of one or more requirements.These requirements define the major functions of the intended application, define operational data areas and reference data areas, and define the initial data entities.

Major functions include critical processes to be managed, as well as mission critical inputs, outputs and reports. A user class hierarchy is developed and associated with these major functions, data areas, and data entities. nEach of these definitions is termed a Requirement. Requirements are identified by unique requirement identifiers and, at minimum, contain a requirement title and textual description. DESIGN STAGE The design stage takes as its initial input the requirements identified in the approved requirements document. For each requirement, a set of one or more design elements will be produced as a result of interviews, workshops, and/or prototype efforts. Design elements describe the desired software features in detail, and generally include functional hierarchy diagrams, screen layout diagrams, tables of business rules, business process diagrams, pseudocode, and a complete entity-relationship diagram with a full data dictionary. These design elements are intended to describe the software in sufficient detail that skilled programmers may develop the software with minimal additional input. DEVELOPMENT STAGE The development stage takes as its primary input the design elements described in the approved design document. For each design element, a set of one or more software artifacts will be produced. Software artifacts include but are not limited to menus, dialogs, data management forms, data reporting formats, and specialized

procedures and functions. Appropriate test cases will be developed for each set of functionally related software artifacts, and an online help system will be developed to guide users in their interactions with the software. INTEGRATION & TEST STAGE During the integration and test stage, the software artifacts, online help, and test data are migrated from the development environment to a separate test environment. At this point, all test cases are run to verify the correctness and completeness of the software. Successful execution of the test suite confirms a robust and complete migration capability. During this stage, reference data is finalized for musicion use and musicion users are identified and linked to their appropriate roles. The final reference data (or links to reference data source files) and musicion user list are compiled into the Musicion Initiation Plan. INSTALLATION & ACCEPTANCE STAGE During the installation and acceptance stage, the software artifacts, online help, and initial musicion data are loaded onto the musicion server. At this point, all test cases are run to verify the correctness and completeness of the software. Successful execution of the test suite is a prerequisite to acceptance of the software by the customer. After customer personnel have verified that the initial musicion data load is correct and the test suite has been executed with satisfactory results, the customer formally accepts the delivery of the software.

The structure imposed by this SDLC is specifically designed to maximize the probability of a successful software development effort. To accomplish this, the SDLC relies on four primary concepts: Scope Restriction Progressive Enhancement Pre-defined Structure Incremental Planning These four concepts combine to mitigate the most common risks associated with software development efforts.

MODULAR ANALYSIS

MODULAR ANALYSIS
Each module has different requirements from the others:-

Control module-dispatches requests to business logic, controls screen flow, coordinates component interactions, and activates user sign on and registration. Customer module-the customer module represents customer information: addresses, credit cards, contact information, and so on. Shop Musics catalog Module-This module starts when the user visits the home page or when a user searches for a music by entering a search term. This part of the application includes displaying all the musics that are available or the musics that match the search term entered by the user. The user can then filter these musics

based on various parameters like manufacturer, music type etc. The user browse through the musics and each would be displayed with an image and its features. A user can add a music to the cart either by dragging the music and dropping it into cart or by clicking a button. The user would be able to see the music cart summary. Music Description Module-This module starts when a user visits the music description page. A user can view various images of the music of different sizes. The user can see an enlarged image in a popup window. The user can view the complete specification of the music like its features, operating system supported, system requirements etc. A user can also view the manufacturer information and also information about rebates, exchange policies etc. A user can also view the reviews of the music. Music Cart Module -This module starts when the user views the music cart. All the musics that have been added to the music cart by the user are listed along with their price and the quantity. The total price of all the musics added to cart is displayed. A user can edit the quantity of each music or remove the music from the music cart. A user can remove the music from the cart by clicking a button or by dragging the music and dropping it outside the cart. The total price changes accordingly when a user edits the quantity of a music or when a music is removed from the cart. Messaging module- asynchronously transmits purchase orders from the store to the OPC (Online Public Catalog).

SYSTEM ANALYSIS

System Analysis
As the goal of the application is ease of use and to provide an interactive interface. There are two groups of users in our software system; they are General Users (customers or visitors) and Administrators. They have different authorities in our systems which are shown as follows:

General users They can be either registered users (customers) or nonregistered (guest users). They can view the detailed music information and their music history. Besides, they are able to create download songs

Administrator He is the authorized staffs to control the system. They are assigned with different level uploading the latest songs.In addition, administrator can execute summary reports and be responsible to maintain database.

System Analysis
Functional Requirements of General Users Registration/Login

Music cart editing and updating View music history Search information of music

Receive invoice

Change password Main functions for General users :

Going music The system provides a searching function on goods based on the music types andbrand names, and shows the inventory state to members. Members can make purchase orders on different musics using the online music cart.

Music history Members can check their music history, ordering history and existing invoices and cancel their orders any time.

Change password It allows the members to change their passwords by themselves. Contact us Member can get the contact information of the system administrators. Logout To purchase musics in our online music

Functional Requirements for Administrator Login

Update information of music

Update information of member Update information of administrator Print Report Change password Main Functions for Administrator The seven main functions provided to administrator as follows:

Member setting Administrator can view, modify and delete the personal information and passwords of members if necessary. Administrator can search the information of members by using member ID or member type..

Music setting Administrator can view, modify and delete the information of songs.. Change password It allows the administrators to change their passwords by themselves.

Logout

Non-functional Requirements Non-functional requirements define the operational requirements and project schedule Operational Requirements : The system can be viewed by Microsoft Internet Explorer.

HARDWARE & SOFTWARE SPECIFICATIO N

System Requirement Analysis

DESIGN CONSTRAINTS: The proposed project is to be developed on the following hardware and software platforms:

HARDWARE REQUIREMENT (MINIMUM): Intel based PC running Windows XP or upgraded version. Pentium4 or higher processor 1 GB RAM Hard-disk requirements: 80 GB minimum Tft monitor

Minimum color depth :32 bit

A dvd writer Printer Scanner Keyboard Mouse

 SOFTWARE REQUIREMENT:

FRONT END BACK END OPERATING SYSTEM

: ASP .NET 2008 : ORACLE : Microsoft Window Xp and other higher version.

WEB SERVER

: IIS Web Server to serve as ASP.NET engine. : ASP.NET Server pages (ASP.NET) : HTML , Internet Explorer 6.0

SERVER SIDE APPLICATION SOFTWARE CLIENT SIDE APPLICATION SOFTWARE

SECURITY CONSTRAINTS: In the present system the work domain of each employee of the organization is clearly specified and the rules and regulations are strictly followed. So it is necessary to design such a system which is capable to withstand with the complexities of the existing system.

Software Requirement Specialisation(SRS)

Software requirement specification (SRS) is the starting point of the software development activity. Little importance was given to this phase in the early days of software development. The emphasis was first on coding and then shifted to design.

As systems grew more complex, it became evident that the goals of the entire system cannot be easily comprehended. Hence the need for the requirement analysis phase arose. Now, for large software systems, requirements analysis is perhaps the most difficult activity and also the most error prone. Some of the difficulty is due to the scope of this phase. The software project is initiated by the clients needs. In the beginning these needs are in the minds of various people in the client organization. The requirement analyst has to identify the requirements by talking to these people and understanding their needs. In situations where the software is to automate a currently manual process, most of the needs can be understood by observing the current practice. The SRS is a means of translating the ideas in the minds of the clients (the input), into formal document (the output of the requirements phase). Thus, the output of the phase is a set of formally specified requirements, which hopefully are complete and consistent, while the input has none of these properties.

DEVELOPMENT ENVIORNMENT
ABOUT MICROSOFT .NET FRAMEWORK Microsoft announced the .NET initiative in July 2000. The .NET platform is a new development framework with a new programming interface to Windows services and APIs, integrating a number of technologies that emerged from Microsoft during the late 1990s. Incorporated into .NET are COM+ component services; the ASP web development framework; a commitment to XML and object-oriented design; support for new web services protocols such as SOAP, WSDL, and UDDI; and a focus on the internet.The platform consists of four separate music groups: Development tools A set of languages, including C# and VB.NET; a set of development tools, including Visual Studio.NET; a comprehensive class library for building web services and web and Windows applications; as well as the Common Language Runtime to execute objects built within this framework. Specialized servers A set of .NET Enterprise Servers, formerly known as SQL Server 2000, Exchange 2000, BizTalk 2000, and so on, that provide specialized functionality for relational data storage, email, and B2B commerce. Web services An offering of commercial web services, recently announced as project Hailstorm; for a fee, developers can use these services in building applications that require knowledge of user identity.

Devices New .NET-enabled non-PC devices, from cell phones to game boxes. Microsoft is devoting considerable resources to the development and success of .NET and related technologies: their bets are on .NET as the next big thing in computing.

OVERVIEW OF .NET FRAMEWORK

Microsoft .NET Framework

The .NET Framework is a new computing platform that simplifies application development in the highly distributed environment of the Internet. The .NET Framework is designed to fulfill the following objectives:

To provide a consistent object-oriented programming environment whether object code is stored and executed locally, executed locally but Internetdistributed, or executed remotely.

To provide a code-execution environment that minimizes software deployment and versioning conflicts.

To provide a code-execution environment that guarantees safe execution of code, including code created by an unknown or semi-trusted third party.

To provide a code-execution environment that eliminates the performance problems of scripted or interpreted environments.

To make the developer experience consistent across widely varying types of applications, such as Windows-based applications and Web-based applications.

To build all communication on industry standards to ensure that code based on the .NET Framework can integrate with any other code.

The .NET framework provides the compulsory compile time and run-time foundation to build and .NET based applications. It has also provide two main components: the common language runtime and the .NET Framework class library. Platform Substrate The .NET platform must run on an operating system. Currently the.NET framework is built to run on Microsoft Win32 operating systems. In the future,

the .NET framework will be extended to run on other platforms, such as Microsoft Windows CE. Application Services When running on windows, application services, such as Component Services, Message Queuing, Windows Internet Information Server (IIS), and Windows Management Instrumentation (WMI), are available to the developer.

Common Language Runtime

The CLR simplifies application development, provides a robust and secure execution environment, supports multiple languages, and simplifies application deployment management. It is also referred to as managed environment. The common language runtime manages memory, thread execution, code execution, code safety verification, compilation, and other system services. These features are intrinsic to the managed code that runs on the common language runtime.

.NET Framework class library

The .NET Framework class library is a collection of reusable types that tightly integrate with the common language runtime. The class library is object oriented, providing types from which your own managed code can derive functionality. This not only makes the .NET Framework types easy to use, but also reduces the time associated with learning new features of the .NET Framework. In addition, thirdparty components can integrate seamlessly with classes in the .NET Framework.

.NET Framework to develop the following types of applications and services:

Console applications. Scripted or hosted applications. Windows GUI applications (Windows Forms). ASP.NET applications. XML Web services. Window services.

ADO.NET ADO.Net is the next generation of Microsoft ActiveX Data Objects (ADO) technology. ADO.NET provides improved support for the disconnected programming model. It also provides rich XML support.

ASP.NET Microsoft ASP.NET is a programming framework that is built on CLR. ASP.NET can be used on a server to build powerful web applications. XML Web Services XML Web Services are programmable web components that can be shared among applications on the internet or the intranet. The .NET framework provides tools and classes for building, testing, and distributing XML Web services. User Interfaces The .NET framework supports three types of user interfaces:

1. Windows Forms, which run on Win32 client computers. 2. Web Forms, which work through ASP.NET. 3. Console application, which, for simplicity are used for most of the labs in this course.

Client Application Development

Client applications are the closest to a traditional style of application in Windowsbased programming. These are the types of applications that display windows or forms on the desktop, enabling a user to perform a task. Client applications include applications such as word processors and spreadsheets, as well as custom business applications such as data-entry tools, reporting tools, and so on. Client applications usually employ windows, menus, buttons, and other GUI elements, and they likely access local resources such as the file system and peripherals such as printers.

Server Application Development

Server-side applications in the managed world are implemented through runtime hosts. Unmanaged applications host the common language runtime, which allows your custom managed code to control the behavior of the server. This model provides you with all the features of the common language runtime and class library while gaining the performance and scalability of the host server. The following illustration shows a basic network schema with managed code running in different server environments. Servers such as IIS and SQL Server can perform standard operations while your application logic executes through the managed code.

INTRODUCTION OF ASP.NET
ASP.NET is the hosting environment that enables developers to use the .NET Framework to target Web-based applications. However, ASP.NET is more than just a runtime host; it is a complete architecture for developing Web sites and Internet-distributed objects using managed code. Both Web Forms and XML Web services use IIS and ASP.NET as the publishing mechanism for applications, and both have a collection of supporting classes in the .NET Framework.

ASP.NET is a technology that Microsoft created to ease the development of interactive Web applications and dynamic websites.

ASP.NET is a compiled, .NET-based environment.

 ASP.NET supports building HTML-based applications with Web forms, and web services. ASP.NET is a server side scripting technology that enables scripts (embedded in web pages) to be executed by an Internet server. ASP.NET is a program that runs inside IIS .IIS (Internet Information Services) is Microsoft's Internet server as a free component with Windows servers, part of Windows 2000 and XP Professional. An ASP.NET file is just the same as an HTML file & can contain HTML, XML, and scripts. Scripts in an ASP.NET file are executed on the server and have the file extension ".aspx".

How Does ASP.NET Work? When a browser requests an HTML file, the server returns the file .When a browser requests an ASP.NET file, IIS passes the request to the ASP.NET engine on the server .The ASP.NET engine reads the file, line by line, and executes the scripts in the file .Finally, ASP.NET file is returned to the browser as plain HTML.

Database is the most important thing in this universe as database gives identity to a thing. It provides us with a repository where we can store ample amount of data, at one place. Without a database, existence of a thing is impossible. What is a database?

Data Base is a collection of tables and table is a collection of records in a tabular form i.e. in row and columns format. Data Base can be divided into two parts: RDBMS DBMS

We will be using RDBMS (Relational Database Management System) in our project i.e. Oracle .

Oracle Database
The Oracle Database (commonly referred to as Oracle RDBMS or simply as Oracle) is a relational database management system (RDBMS) produced and marketed by Oracle Corporation. An Oracle database is a collection of data treated as a unit. The purpose of a database is to store and retrieve related information. Oracle Database is the first database designed for enterprise grid computing, the most flexible and cost effective way to manage information and applications. Structured Query Language (SQL) is the set of statements with which all programs and users access data in an Oracle database. Application programs and Oracle tools often allow users access to the database without using SQL directly. Oracle provides security ,maintains ,reliability and distributed computing (allow applications and data to run anywhere in the network.)

Oracle is a database that responds very well with excellent performance in demanding environments. Oracle is a major database is important in insuring the integrity of data. This is very important because data is the heart of any system in organization. A reliable and adequate database system has the following properties: Atomicity: That is Results of a transaction's execution are either all committed or all rolled back. Consistency: The database is transformed from one valid state to another valid state. Illegal transactions aren't allowed and, if an integrity constraint can't be satisfied then the transaction is rolled back. Isolation: The results of a transaction are invisible to other transactions until the transaction is complete thus increasing the security on data.

Durability: Once committed (completed), the results of a transaction are permanent and survive future system and media failures and thus ensuring maintenance and protection of data. One of the main advantage of oracle over other databases is in its recent version oracle has the concept of Flashback technology. That is we all know that data is the heart of any application or organization and thus this requires careful maintenance. But sometimes application outage can occur and mostly DBA claim the reasons for

this as hardware failure and apart from this the reason would be human errors like accidental deletion of valuable data, deleting the wrong data, or dropping the wrong table. So it is very essential to take care of such situation and this is done in oracle's latest technology called flash introduced in its latest version. By Flash technology it helps in recovery by working just on the changed data. Thus Flashback provides

Faster database recovery Helps in simplifying the management and administration processes Efficient recovery from human errors

And so on. Thus oracle has many advantages and features that give security, protection, maintenance, reliability and performance on operation of data and with this in addition its main popularity and stability is because it keeps on adding new features which makes it user friendly for users and popularly used database among organizations.

Software Requirement Specification(SRS)

The purpose of Software Requirement Specification is to bridge the communication gap between the client and the user. SRS is a medium through which the client and the user needs are accurately specified. SRS forms the basis of software development. Software Requirement Specification (SRS) is a fundamental document, which forms the foundation of software development process. SRS not only lists the requirements of the system it also has the description of the major features.

Features
Complete music description: Full order history and details are available to

the customer.
Uploading latest movie and album songs

controls: to prevent ordering of items once they're out of stock. Password Reminder feature for Customers. Advanced search and music filter tool.

FEASIBILITY ANALYSIS

FEASIBLITY ANALYSIS INTRO

A feasibility study is conducted to select the best system that meets performance requirement. This entails an identification description, an evaluation of candidate system and the selection of best system for he job. The system required performance is defined by a statement of constraints, the identification of specific system objective and a description of outputs. The research has been done and your head is aching from building an organizational chart and bare bones financial model of your first year in business. Now what? Now plan how to market your start-up to your customers, the fifth and final step of a feasibility analysis. Those demographics you researched earlier are going to become tremendously useful in this step. Further, the costs of marketing should be factored into your financial planning in step four. In this step though, the focus is on how to market. No piece on marketing is complete without describing the

advertising/marketing mediums first. The first and perhaps most important promoter is simple word of mouth. The easiest way to win good press in this aspect

is to please your customers. While it can make for a hard-to-ignore testimonial, word of mouth can also be turned against a business. A single disappointed customer will generally talk to more people about their disappointment rather than any good experience they had. Unfortunately, theres no way to control word-of-mouth marketing save for impersonating (or having someone else impersonate) an ordinary customer and painting a positive picture of your business. Before the world started to swirl around electronic media like television, radio, and especially the internet, the one standard for communication was the written word. While it is true that much electronic media has replaced some of the value of written media, it is still the most affordable and easiest way for you to get the word out about your business to a massive audience quickly. Focus your efforts on specific publications that are likely to be picked up by your potential customers. Focus on papers deal with local affairs or trade specific journals. You want to view every person who picks up that advertisement as a potential customer. Electronic mediums, such as radio and television, are a tricky affair. Though they can be effective, theyre also painfully commonplace, meaning that youll need something that grabs an audiences attention very effectively if you want to get anything for advertising dollar. It will be a significant investment on your part to get a radio advertising spot, and television even more so.

An effective commercial will be expensive, so make sure you do it right, no matter what media you choose to use. Professional help in making commercials will go a long way, unless you yourself are a professional. Direct mail, wherein a business printed advertisements to people directly, is another solid advertising medium. It can work wonders for small businesses catering to a local area, but its also a scattershot approach, in that the advertising is being thrown around all over an area, with no certainty that it will strike a cord with even a single customer. As with electronic medium, youll need to be clever about distinguishing your business mail with the rest of the junk mail your intended audience gets on a daily basis. Other than sinking more money into advertising than it earns back, the other major mistake of marketing is allowing your business to overexposed, so be careful how much you advertise. Additionally, if youre clever about it, you can even get yourself some free advertising. Once you have finished planning your marketing and factoring it into your financial planning, then you should have pretty clear idea of whether or not your business has chance of succeeding. If things looks rosy for your business, then youre on the right track. If they look grim, remember that your plan can be changed to adapted, and that the right ideas can turn any business into a success. The first concern for many would-be business owners is a creeping fear that whatever business they start, it will end up failing miserably and leave the

companys founder with a lot less than what they started with. Given that few small business owners can call upon massive resources, this is an understandably frightening prospect. however there is way, called feasibility analysis, to gauge your chances of success. The first and most important rule of feasibility analysis is to be honest with yourself. If youre not sure of something, find the truth of the matter, and dont forget to question assumptions. The second, equally important rule is to assume the worst when youre dealing with uncertain factor. These two rules can not be stressed enough. There are two basic steps that need to be complete in beginning a feasibility analysis. The idea that you originally had for a business in the first place needs to be fleshed out and defined. As you expand this idea, you will naturally be lead to ask a series of questions about the business itself. Ask yourself questions about your long term goals and post experiences which may help or hinder you. Use these questions to form a checklist that you can use to honestly assess yourself and your capabilities, skills, desire, and commitment. The second step is research. Youll want to research as many aspects of your potential start up as you can reasonably manage beforehand. Still. There are a few fields of particular importance for any business owner. The first is researching the demand for your business at the time and place youre planning to found it. A low demand is not necessarily something that should

stop you entirely (unless youre trying to sell something with so little demand that its obvious you cant form a business), and you will want to consider the low demand for the future. Youll also want to research he competition in your start-ups industry, as well as research ways that you can do better than your competitors. youll also want to look into other factors that make an impact on the general setting your business will be in (called the business environment), such as distribution matters (for retail-based businesses), supplier issues, and other effects that might help or harm your business. Finally, youll want to get a clear picture of your industrys demographics (statistics showing your potential customers are). Congratulations-youve reached the end of the pure research phase of your feasibility analysis. from here on out though, youll be combining both research and theoretical decision-making to get you through the final three steps of the analysis. In the meantime, gather what you learned and prepare to put it to use.

The system feasibility can be divided into the following sections:

Economic Feasibility The project is economically feasible as the only cost involved is having a computer with the minimum requirements mentioned earlier. For the users to access the application, the only cost involved will be in getting access to the Internet. It looks at the financial aspects of the project. It determines whether the management has enough resources and budget to invest in the proposed system and the estimated time for the recovery of cost incurred. It also determines whether it is worth while to invest the money in the proposed project. Economic feasibility is determines by the means of cost benefit analysis.The proposed system is economically feasible because the cost involved in purchasing the hardware and the software are within approachable. The personal cost like salaries of employees hired are also nominal, because working in this system need not required a highly qualified professional. The operating-environment costs are marginal. The less time involved also helped in its economical feasibility. It was observed that the organization has already using computers for other purpose, so that there is no additional cost to be incurred for adding this system to its computers. Technical Feasibility Technical feasibility center around the existing computer system hardware etc. and to what extent it can support the proposed addition. For example, if the current computer is operating at 80% capacity - an arbitrary ceiling then running another application could over load the system or require additional hardware. This involves financial consideration to accommodate technical enhancements. If the budget is a serious constraint then the project is judged not feasible.

To deploy the application, the only technical aspects needed are mentioned below: Operating Environment Win 2000/XP Platform .Net Framework & IIS Database Oracle 2005 For Users: Internet Browser Internet Connection Operational Feasibility The system will be used if it is developed well then be resistance for users that undetermined No major training and new skills are required as it is based on DBMS model. It will help in the time saving and fast processing and dispersal of user request and applications.

New music will provide all the benefits of present system with better performance.

Improved information, better management and collection of the reports. User support. User involvement in the building of present system is sought to keep in mind the user specific requirement and needs. User will have control over there own information. Important information such as pay-slip can be generated at the click of a button. Behavioral Feasibility

The application requires no special technical guidance and all the views available in the application are self explanatory. The users are well guided with warning and failure messages for all the actions taken. People are inherent to change. In this type of feasibility check, we come to know if the newly developed system will be taken and accepted by the working force i.e. the people who will use it.

DATA FLOW DIAGRAM

After carefully analyzing the requirements and functionality of the web application, we have the two important diagrams by the end of the analysis phase. They are the ER diagram and data flow diagram which were the basis for finding out entities and relationships between them, the flow of information.

DFD

The Data flow Diagram shows the flow of data. Data Flow Diagramming is a means of representing a system at any level of detail with a graphic network of symbols showing data flows, data stores, data processes, and data sources/destination. The data flow diagram is analogous to a road map. It is a network model of all possibilities with different detail shown on different hierarchical levels. This processes of representing different details level is called leveling or partitioning by some data flow diagram advocates. Like a road map, there is no start point or stop point, no time or timing, or steps to get somewhere. We just know that the data path must exist because at some point it will be needed. A road map shows all existing or planned roads because the road is needed.

It is generally made of symbols given below:

A square shows the Entity. A Circle shows the Process An open Ended Rectangle shows the data store.

 An arrow shows the data flow.

When it comes to conveying how information data flows through systems (and how that data is transformed in the process), data flow diagrams (DFDs) are the method of choice over technical descriptions for three principal reasons. 1. DFDs are easier to understand by technical and nontechnical audiences 2. DFDs can provide a high level system overview, complete with boundaries and connections to other systems 3. DFDs can provide a detailed representation of system components1 DFDs help system designers and others during initial analysis stages visualize a current system or one that may be necessary to meet new requirements. Systems analysts prefer working with DFDs, particularly when they require a clear understanding of the boundary between existing systems and postulated systems. DFDs represent the following: 1. External devices sending and receiving data 2. Processes that change that data 3. Data flows themselves 4. Data storage locations The hierarchical DFD typically consists of a top-level diagram (Level 0) underlain by cascading lower level diagrams (Level 1, Level 2) that represent different parts of the system. DFDs consist of four basic components that illustrate how data flows in a system: entity, process, data store, and data flow.

Entity An entity is the source or destination of data. The source in a DFD represents these entities that are outside the context of the system. Entities either provide data to the system (referred to as a source) or receive data from it (referred to as a sink). Entities are often represented as Rectangles Process The process is the manipulation or work that transforms data, performing computations, making decisions (logic flow), or directing data flows based on business rules. In other words, a process receives input and generates some output. Processes can be drawn as circles or a segmented rectangle on a DFD, and include a process name and process number.

Data Store A data store is where a process stores data between processes for later retrieval by that same process or another one. Files and tables are considered data stores. Data store names (plural) are simple but meaningful, such as customers, orders, and musics. Data stores are usually drawn as a rectangle with the right hand side

missing and labeled by the name of the data storage area it represents, though different notations do exist. Data Flow Data flow is the movement of data between the entity, the process, and the data store. Data flow portrays the interface between the components of the DFD. The flow of data in a DFD is named to reflect the nature of the data used (these names should also be unique within a specific DFD). Data flow is represented by an arrow, where the arrow is annotated with the data name. The DFD can be up to several levels. The 0 level DFD states the flow of data in the system as seen from the outward in each module.The first level DFD show more detail, about the single process of the 0 level DFD.The second level DFD can show even more details and so on.

0 Level DFD
First the context of the system is established with a context diagram.(also known as a level 0 (zero) DFD).A context diagram, using generic names for the entities and the processes involved. Here, at first, the Web Administrator will monitor the website activities and take care management of the website. Meanwhile, the user can assess the website for

buying, selling or to get music information, and personal details etc through only process Emart music application.

project

Manage and create Administrator

Users

Searches and play musicOnline Music

Music Search

Music information Database

EXPLANATION OF 0 LEVEL DFD

Zero level DFD is an abstract description of the system for handling the primary individual process in the system at the highest possible level. It uses function-based decomposition while modeling the problem.

The agent that performs the flow of data from one state to another is called a process. So this DFD shows the movement of data through the different transformations or processes in the system. The processes are shown by named circles and data flows are represented by named arrows entering or leaving the process. A rectangle represents sources or sinks and is not originator or consumer of data. A source or sink is typically outside the main system of study. It focuses on the functions performed in the problem domain and the data consumed and produced by these functions. It is the top-down refinement approach which was originally called structured analysis and specification and was proposed for producing the specifications. The 0-level DFD aims to capture the transformations that take place within a system to the input data so that eventually the output data is produced. There are no detailed procedures that can be used to draw DFD for a given problem. Only some directions can be provided.One way to construct a DFD by identifying the major inputs and outputs. Then starting from the inputs, work toward the outputs, identifying the major transformations in the way. Here, in our Online Music, user interacts with the automated mall system process by giving a command to the automated E-Mart system and after on the basis of command given by the admin/client to automated E-Mart system, the appropriate response will be given by the Admin to the automated E-Mart system process to the admin/client. A 0-level DFD represents a pure abstracted view of our overall structure of the system. In 0-level DFD basically there is no data flows between admin/client and automated E-Mart system, only fetching of data occur which is not to be shown at this level because it is a pure abstracted level.

1 Level DFD

Search For Search For Music Music

Applying Searching Criteria

Showing Showing Search Search Results Results and Play and Play Music Music

Database

EXPLANATION OF 1 LEVEL DFD

Level-1 DFD shows the sub-processes of one of the processes in the Level-0 DFD. A 1-level DFD has a starting DFD which is a very abstract representation of the system, identifying the major inputs and outputs of the processes in the system. Then each process is refined and DFD is drawn for the processes. For the hierarchy to be consistent it is important that the net inputs and outputs of a DFD for a process are the same as the inputs and outputs of a DFD for a process in the higher level DFD. This refinement stops if each bubble or process is considered to be atomic in that each bubble can be easily specified or understood. It should be pointed out that during refinement though the net input and output are preserved, a refinement of the data might also occur. First level DFD clears the first level of abstraction by showing the process of the system. First level represents the basic process of the system. It is the first extended form of system which moves from where and how the data flows and how user interact with the system.

In our E-Mart, the First Level DFD shows the various flow of data and how the response is given by the system. Our E-Mart basically perform main processes which named as Customer Registration/Login entry , Purchase detail ,Music Cart, Order Generated, Transaction and last one is Credit Card Identification on the basis of administrator. There are one entity administrator and five tables like User Detail, Music Master, General User , Music Cart, Credit Card Detail. All the information updated by an entity administrator.

As in module 2 ,the Web Administrator will monitor the websites activities and the management of the website. The web administrator will have the full access into the website. Once the user add item to sell list in website, administrator will receive the items details to take into consideration. Only after administrator approve, the item will only be allowed to go into sell list of the Online Music Store Website. So, our website is act as a medium between the seller and customer (buyer). Beside that, our website will serve to provide the details of all music listed there, if a user intend to buy, he/she has to contact the seller and make payment through the website Meanwhile, as in module 1, the user can access the website for buying, selling or to get music information. As only a registered user can buy or sell items in Online Music Online Store Website, he/she must agree to the terms and conditions of the system. Once register, he/she will receive a verification mail to his/her email, which have a link to our website. By clicking on the link then will direct verify the users registration and then he/she will become a official member in Online Music Store.

A seller can advertise the item he/she willing to sell with the personal detail. If the item advertise is not approve by administer, he will receive a message from administer regarding it. The user still can review the detail about the item he/she willing to sell which is still waiting for administrator consideration. To the user who wants to buy an item, he/she can access to contact detail of the seller. He/she can contact the seller regarding the item.

2 Level DFD

EXPLANATION OF 2 LEVEL DFD

The 2 level DFD is just the extension of the previous two levels. Here this level comprises of the two module(1,2). Module 1 represent the complete data flow information to the general user through various process till the music is delivered to the customer after the payment is done.

Report Generation & Print

Module 2 ,shows the administrator part as how the administrator manages the websites and provide information for easy interface to users .differebt process involve as music setting ,member setting ,administrator update, invoice and report generation together with their printout. It also involve checking out process.

ENTITY RELATIONSHIP DIAGRAM

ENTITIES RELATIONSHIP DESIGN

The data-modeling phase involves modeling the databases structure using a data modeling method each of these modeling method provides a mean of visually representing various aspect of the database structure, such as the table, table relationship, and relationship characteristics.

VARIOUS SYMBOLS OF E-R DIAGRAM : The rectangle represent entity such as ,tables

The diamond represents a relationship between two tables(entity)

Circles represent attributes associated with each entities.

 Double rectangles weak entities.

An entity relationship diagram is a graphical representation of an organisation's data storage requirements. Entity relationship diagrams are abstractions of the real world which simplify the problem to be solved while retaining its essential features.it estabhlishes the relationship between the two or more entities. Entity relationship diagrams are used to identify the data that must be captured, stored and retrieved in order to support the business activities performed by an organisation; and identify the data required to derive and report on the performance measures that an organisation should be monitoring. Entity relationship diagrams have three different components: 1. ENTITIES 2. ATTRIBUTES 3. RELATIONSHIPS

Entities These are the people, places, things, events and concepts of interest to an organization. In short, anything which an organization needs to store data about. Entities represent collections of things. For example, an EMPLOYEE entity might represent a collection of all the employees that work for an organization. Individual members (employees) of the collection are called occurrences of the EMPLOYEE entity. Because the available space for naming the entity is restricted to the size of the box, Entities should always have detailed descriptions. These detailed descriptions are usually short paragraphs of text describing the entity in more detail but for some important entities, a lengthy description may be required. Attributes Entities are further described by their attributes (sometimes called data elements). These are the smallest units of data that can be described in a meaningful manner. Relationships Frequently, a meaningful relationship exists between two different types of entity. For example: Employees work in a DEPARTMENT Lawyers advise Clients EQUIPMENT is allocated to Projects TRUCK is a type of VEHICLE

There are potentially three types of relationship which can exist between two different entities: 1. One-to-One Relationships 2. One-to-Many Relationships 3. Many-to-Many Relationships

One-to-One Relationships This type of relationship takes place when a single occurrence of an entity is related to just one occurrence of a second entity. For example, a ROOF covers one BUILDING; a BUILDING is covered by one ROOF. One-to-Many Relationships This type of relationship takes place when a single occurrence of an entity is related to many occurrences of a second entity. For example, An EMPLOYEE works in one DEPARTMENT; a DEPARTMENT has many Employees.

Many-to-Many Relationships This type of relationship takes place when many occurrences of an entity are related to many occurrences of a second entity. For example, EQUIPMENT is allocated to many PROJECT; A PROJECT is allocated many items of EQUIPMENT.

ER-DIAGRAM

password email Contact no. lname

User id

fnam e type

Security ques cid

User id*

bank Credit card Cart no. Product pnam e ptype category city pid

User detail
Security ans

User credit card detail

Order place bookid pid

Book date

offer delivery cid Cart buy qty amt

P qty

Pid*

Order

Shopping cart id User to purchase

User id* Cart id*

Order id*

qty des c Pid*

Prod name

Order deliverd

Sale id sale Prod sale amt qty

Product detail

Pid* Sale date

amt

EXPLANATION OF ER DIAGRAM
ER Diagram also called a entity relationship diagram. It is graphical representation of entity and their relationship with one another it can express the overall logical structure of the database graphically. In ER Diagram an entity set is shown as a rectangle. The diamond represent the relationship among the no of entity, which are connected to the diamond by line. The attribute shown oval, are connected to the entity or relationship by line. Diamond from a oval & relationship leveled. The type of relationship existing between entities is represented by giving the cardinality ratio of relationship or the line joining the relationship to the entity. In this project ER Diagram represents five entities, User Detail, Music Detail General User, Music Cart, and Credit Card Detail.

DATABASE DESIGN

Database design
Database files are the key source of information into the system. It is the process of designing database files which are the key source of information to the system. The files should be properly designed and planned for collection, accumulation, editing the required information. The objectives of the file design are to provide effective auxiliary storage and to contribute to the overall the efficiency of the computer program component of the system. In concepts of database design, there are two types of data physical data and logical data. Physical data is that which is written on those pieces of paper. Logical data are those, which are calculated based on some of the retrieved data in a certain sequence in summary form. In a computer-based data processing system, separation of physical and logical data provides the same advantages.

OBJECTIVE OF DATABASE

Reduced Redundancy: Redundant data occupies space and therefore is wasteful.

More information at low cost: Using storing and modifying at low cost are important. Although hardware prices are falling, software programming is on the rise.

Accuracy and integrity: The accuracy of database ensures that data quality remain constant. Integrity controls and detects data in accuracy where they occur.

Normalization: Refinement of the E-R model. Segregation of data over many entities or tables. Normalized model converted to physical database tables. Normalization is a process of refining the data model built by the Entity-

Relationship diagram. The normalization technique logically groups the data over a number of tables, which are independent and contain no unnecessary data. The entities or tables resulting from normalization contain simple data items, with relationships being represented by replication of key data item(s).

DATA DICTIONARY

Database Design In Music Site about 6 database tables are used such as

Table Name: UserLogin Description: used to store user information.

Table Name: UserInfo

Description: used to store user information.

Table Name:

Singer_Master

Description: used to store Singer information.

Table Name: Music_Master Description: used to store all Music

information.

Table Name: File_Master