Rahul Project Music@Video

MusicManza-Online Music and Video Portal
INDEX
S. No. NAME OF TOPICS PAGE NO.
1. Certificate of Originality 3
2. Acknowledgment 4
3. Synopsis 5
4. Introduction of the Project 37
5. Objectives of the Project 38
6. Tools/Platform to be used 39
7. System Analysis 40
(a) Feasibility Study 41
(b) Fact Finding 43
(c) Software Requirements Specification (SRS) 46
(i) Functional Requirement 54
(ii) Non-Functional Requirements 56
(d) Life Cycle Model (Waterfall model) 58
(e) COCOMO Model 62
(f) Scheduling Techniques 66
(i) GANT CHART 68
(ii) PERT CHART 71
(g) Risk Analysis and Management 73
8. System Design 77
(a) Modular Design 79
(b) Modular Description 80
(c) Entity Relationship Diagram 81
Page
1
(d) Class Diagram 82
(e) Use case Diagram 83
(f) Data Flow Diagram (DFD) 84
(i) Zero level DFD 84
(ii) One level DFD 85
(iii) Two level DFD 86
(g) Data Dictionary 89
9. TESTING 92
(a) Test Plan 95
(b) Testing type 98
(c) Test Cases 110
(d) Test/Bug Report 112
(e) Debugging 115
10. Implementation of Security 116
(a) Database Security 117
(b) Data Security 122
(c) Users & access rights 127
11. Limitations of the Project 128
12. Future Scope of the Project 129
13. Bibliography 130
14. Input and Output Screens 131
15. Coding with Comments and Error Handling 150
Page
2
CERTIFICATE OF ORIGINALITY
This is to certify that the project report entitled MUSIC & VIDEO
POTALS Submitted to Indira Gandhi National Open University in
partial fulfilment of the requirement for the award of the degree of
MASTER OF COMPUTER APPLICATIONS ( MCA), is an original
work carried out by Mr. RAHUL SONI, Enrolment No.: 137882650 under
the guidance of Mr. ALIND SAXENA.
The matter embodied in this project is a genuine work done by the student
and has not been submitted whether to this University or to any other
University / Institute for the fulfilment of the requirement of any course of
study.
Signature of the Student Signature of the

Guide
Name and Address Name,

Designation and
of the student : Address of the
Guide:
Page
3
ACKNOWLEDGEMENT
It gives me immense pleasure to put forward this practical venture. But
surely, it would not have been possible without proper guidance and
encouragement. So I would like to thank all those people without whose
support this project would not have been a success.
I take great pride and privilege to express my gratitude to my guide, Mr.
ALIND SAXENA for expert planning, peerless guidance and untiring and
bountiful help which inspired me to complete my desired dissertate
work. My indebtedness is reserved for her good will and patience
during the project.
I have benefited a lot from the constructive critics and suggestion given
to me by all of my teachers and Lab instructors of my study centre KSM.
I am grateful to my entire Faculty and Programmers and all my friends
for helping me prepare my project.
My Parents, being earthly Gods in my life deserve much more than what
I can weigh in words. Their silent prayers, aesthetic love and affection
and steel belief in my capabilities have enabled me to make this
endeavor see the light of success and unending support from my is
always cherished.
Page
4
SYNOPSIS
Page
5
INDEX
S. No. NAME OF TOPICS PAGE NO.
1. Introduction of the Project. 7

2. Object of the Project. 8
3. System Analysis 9
4. Fact finding. 10
5. Life Cycle Methodology 12
6. Sampling 13
7. Feasibility study. 14
7.1 Technical Feasibility 14
7.2 Economical Feasibility 15
7.3 Operational Feasibility 15
8. Hardware Requirement 16
9. Software Requirement 16
10. Modular Description 17
11. Input/Output 18
12. Entity Relationship Diagram 22
13. Data Flow Diagram 23
13.1 Zero level DFD 23
13.2 One level DFD 24
13.3 Two level DFD 25
14. Class Diagram 27
15. Use Case Diagram 28
16. Data Dictionary 29
17. System Security 33
18. Future Scope of the Application 34
Page
6
19. Bibliography 35
Introduction Of The Project
The Music and video Portal is work on manual process.

And It is working on old technology Therefore very difficult of maintain
record. There in possible of mistake in record where all record of music
and video cd is not possible. There in make possible human error. And
very difficult to search music and video cd in Portal and very difficult of
indexing of all music and video cd.
The music and video digital Portal of the future will

provide electronic access to information in many different from recent
technological advances make the Transmission of digital music and
video information possible This paper will describe the design of a
music and video Portal suitable for storing, indexing, searching and
retrieving music and video information and providing that information
across the internet or the evolving information infrastructure to be an
effective Portal user need to be able to find the music and video
segment.
They want realizing this goal will require ground –

breaking research into automatic content based indexing of video that
will significantly improved the user ability to access specific segment of
interest with video and transcript will be digitized and information
from the sound track and transcript will be used to automatically
index music and video in a frame by frame manner. It will search and
alert information of music and video cd in Portal. It will repair all error
in data in Portal the non textual information such as sound, images,
video and scientific data require considerably more storage per item
the music and video software work fast process.
Page
7
Objective
 Music and video Portal system consist of processing program to
manipulate compress , compact and analyze the music and video
component of a segment
 Information retrieval engine the(IRE) is used to store indices

extracted from music and video segment
 Improve and extend Portal service through software
 Construct and maintain a web site that is useful to staff and the
community
 Monitor and evaluate the demand and supply for technology related
Portal service
 Maximum source of technology finding consistent with the

technology plan
 Maintain a process to evaluate technology for the music and video

Portal
 It will be maintain fast process and more suitable
 It will be user friendly
 It will error free and correct mistake record
 It will be keep all record of Portal
 It keep record all music and video cd purchase
 It keep all receipt record of music and video cd
 It generate automatic sales and purchase record
 It will show all music and video cd automatically in Portal
 It show date of purchase music and video cd in Portal
Page
8
System Analysis
System analysis then is the process of gathering and interpreting

facts, diagnosing problem and using the information to recommend
improvement to the system. It is fairly well – established fact that
errors in a system are more easily and inexpensively rectified.
Customer problem
The most difficult task of keep all customer record in manual

process. If any new customer registration in Portal then not gives
proper information of customer. And There in is mistake customer fill
up form and very difficult to bill calculate process. And waiting for
receiving bill of customer. There in very difficult of save record in
Portal. Many staff member not care of customer. If any customer want
to purchase cd then waste many time of customer. Many staff worker
forget given rent slip of customer and taken extra charge to customer.
Many music and video cd have different place in Portal where with very
difficult search CD/DVD. And fill up form separate counter in Portal
wherewith problem of customer for fill up form.
Page
9
Fact Finding
Fact finding is an extremely important component of the

communication process which presents its own special set of problems and
opportunities to people working to increase the constructiveness of
intractable conflicts. Facts are pieces of information about the world that can
be independently verified by generally accepted research methods as reliable
and a sound bases for decision making and dispute resolution.
Interviews
Interview allows analysis to learn more about the nature of project.
Interview should provide detail that further explain the project and show
whether assistance is economically, operationally and technically.
I went near music and video Portal the analyst confidently

schedule interview with key personal involved with the system I went
conduct a detail interview with all the staff who actually operate the music
and video Portal software I know about Portal software how did this is work. I
conduct a detail interview from staff worker who did actually operate the
system. I know about the customer problem in Portal. The following question
asked from staffs who work in Portal.
o What is the process of maintain record?
o How do you bill calculate in Portal?
o Do you have suggestions for change?
o What is process of bill Generate?
o How are you maintaining stock in Portal?
Page
10
Onsite observation
I went self music and video Portal and meet staff in

Portal and observation the staff to verify understanding of
the software analysis. The main purpose of on-site
observation is to get as choose as possible to real software
studied. I see the office environment, work load of software
and user. I asked the method of work style and asked the
process of bill generate in software. I asked the method of
maintain music and video cd in Portal and asked many
customer problem. How much customer satisfies your work
service. Customer problem like mostly customer receipt slip
did not meet immediately something mistake customer
name wherewith those give extra charge. Mostly forget
generate rent slip of customer and Portal card did not issue
of customer wherewith very difficult to search record of
customer. Many music and video cd did not indexing in
Portal wherewith very difficult to search cd.
Questionnaires
I went music and video Portal I asked customer
requirement and prepare many question from staff and
collect all customer requirement like facilities, easy to
purchase music and video cd. Question is short, easy to
understand, unbiased and specific. I have prepared many
multiple type questions and asked from Portal staff.
Page
11
Life Cycle Methodology
Waterfall Model:-
The Waterfall Model was first process Model to be
introduced. It is also referred to as a linear-sequential life cycle model. It is
very simple to understand and use. In a waterfall model, each phase must
be completed fully before the next phase can begin. This type of model is
basically used for the project which is small and there are no uncertain
requirements. At the end of each phase, a review takes place to determine
if the project is on the right path and whether or not to continue or discard
the project. In this model the testing starts only after the development is
complete. In waterfall model phases do not overlap.
 This model is used only when the requirements are very well known,
clear and fixed.
 Product definition is stable.
 Technology is understood.
 There are no ambiguous requirements.
 Ample resources with required expertise are available freely.
 The project is short.
Page
12
Sampling
I went music and video Portal and I saw all customer

fill up form to separate. Wherewith very difficult to search
form and very time wastage process. Therefore I collect all
daily uses form like registration form, Portal card form, CD
purchase form, CD rent form, documentation etc. and put in
computer software. Where with customer easily fill up own
requirement form on same place. It is very useful facilities
for customer and very time consuming process. It is better
then for customer and staff. It is more compatibility.
Page
13
Page
14
Feasibility Study
Feasibility is the determination of whether or not a

project is worth doing. The process followed in making this
determination is called feasibility study. This type of study
determines if a project can and should be taken. Generally
feasibility studies are undertaken within tight time
constraints and normally written feasibility report.
Types of Feasibility
1. Technical feasibility
It concerned with specifying equipment and

software that will successfully satisfy the user requirement.
The technical needs of the system may very considerably.
It is visual studio (.net) project. therefore purchase

Microsoft visual studio 2005 , SQL server 2005 and
therefore need of 512MB RAM , 160 GB hard disk , mouse,
keyboard and monitor for installation in system.
Page
15
2. Economical feasibility
Economical feasibility is the most frequency used

technique for evaluating the effectiveness of a proposed
system. More commonly known as cost / benefit analysis.
It is a cost / benefit analysis there are use of

Gantt chart and part chart produce to determine the benefits
and savings that are accepted from proposed software and
compare them with costs.
3. Operational feasibility
The proposed projects are beneficial only if

they can be turned into information system that will meet
the operating requirement of the human organization.
It is easy to use and determine the software will work

when is develop. It is easy to operate. It is menu driven and
specifies command button, text box, and level, in software.
There are many shortcut use in software wherewith easily
access to topic. If you enter wrong bill this is show proper
error message on screen. There are uses of simple language
wherewith easy to understand.
Page
16
Hardware Requirenment
 CPU :- AMD 4GB
 Motherboard :- 1GB
 RAM :- 4GB
 Hard Disk :- 500 GB
 Moniter :- 15.6inch
 Keyboard :- Qwerty
 Mouse :- Optical
Software Requirenment
 Front End :- Asp.Net using C#
 Back End :- SQL server 2012
 OS :- Windows 8.1
 Web server :- IIS 8.0
Page
17
Modular Description
Registration customer / canceling

When customer purchase\rent CD\DVD then first fill
up registration form and after that give a registration number and pay
payment of CD\DVD any customer ant time register in Portal and if
customer want canceling registration from Portal then fill up canceling
form and cancel registration.
Registration CD/DVD
The registration department registers all music and video CD.
Customer give a registration number and customer register own
favorite CD/DVD in Portal registration department. And this CD/DVD
not given will be other customer.
Stock
Stock department main work of keep extra music and
video CD/DVD in Portal. And fulfill all customer requirements in Portal.
Many customer purchase/rent music and video CD/DVD.
Billing
The billing department is main work of billing all sale/
purchase music and video CD/DVD. It make billing sale music and
video CD, purchase music and video CD. Billing department maintain
all customer record. And every day billing all purchase music and video
CD, all rent music and video cd and how many balance on customer.
Page
18
Input/output
Customer Registration process
Input Output
Customer Name Registration Number
Age
Sex
Address
Phone no
Email id
Page
19
Registration CD/DVD
Input output
Customer detail music and video

CD/DVD
CD/DVD name
CD/DVD id
CD/DVD number
Registration price
Page
20
Stock
Input output
Stock id fulfill requirement
Stock available music cd
Stock available video cd
Page
21
Billing
Input output
Customer name generate customer bill
Address bill report
Phone no
Purchase item CD/DVD
Rent item CD/DVD
Bill amount
Page
22
Entity Relationship Diagram (E-RD)
Customer _id
CD/DVD price
CD/DVD name
Customer Purchas CD /DVD

e /rent
CD/DVD _number
Customer
Address
Pays
Supplied
By
Bill issue_ date & time
User _ id
Supplier_ id Bill id
User_ password
Supplier name Supplier Bill

User
Supplier address Bill amount
User_ name Bill number
Generate
Page
23
Data Flow Diagram(DFD)
‘0’ LEVEL DFD
Cancellation
Registration make payment

Billing
Customer
Audio
Customer _id
Video
Transaction ID
Portal
Admin
Registration manages
CD_NO search
CD/DVD
CD _NO
Availability
Stock
Cancellation
Page
24
1ST LEVEL DFD
Customer Request
For
Return cd
Request
Request
For
For Canceling
Fill up Cd issue
form
Calculate
Check Issue date
Pay amount Registration Return date

CD _stock
Check Detail
Yes The No
Error
Amount Yes
Message Diff > 2 days
No
Generate Check
Cancel No
Registration Cd available
Registration Yes Yes

Number
Charge
Issue
Fine
Cd
Customer _ detail
CD_ stock
Admin Return
Cd
Page
25
2ND LEVEL DFD
New registration process
Fill up Pay Generate
Customer Form Amount Registration
Number
Customer _ detail Admin
Canceling of registration process
Request Check Pay

For Due Yes
Customer Amount
Canceling Amount
No
Canceling
Admin
Registration
Customer_ detail
Page
26
2ND LEVEL DFD

Issue CD
Check Error
Request Check
Yes CD available no
Customer For Registration Message
detail
Cd _issue
Yes
Issue
CD
CD_stock
Admin
Return CD
Request
Customer Calculate Diff > Charge
To
Return
Issue date 2 days Yes Fine
Return date No
Cd
Return
CD
CD _ stock
Admin
Page
27
Class Diagram
Registration Customer Registration CD & DVD

Customer_ID : int CD/DVD Name : char
Customer_Name : char CD/DVD_ID: int
Customer_Age : int
CD/DVD_Price: int
Customer_Sex : har
Register () Purchase CD/DVD()
Login ()
Payment
Search ()
Payment_ID : int
Payment_date : int
Payment_mode : char
Do_Payment()
Page
28
Use Case Diagram

Make Payment
Sign IN
Sign out
Search
User
Report generate
New CD entry
User name &
password
Admin
Login
Select check password
` Enter old password
New password
Confirm password
User
Change
Data Dictionary
Page
29
1. Customer detail
Field Data Type Description
Customer _id integer it show customer id
Customer name char it store customer name
Customer address char it store customer address
Customer age number it show customer age
Customer sex char it show customer sex
2. CD/ DVD Detail
Page
30
CD/DVD name char it show CD/DVD name
CD/DVD id number it is store CD/DVD id
CD/DVD price char it store CD/DVD price
CD/DVD number number it store CD/DVD number
3. User Detail
Page
31
User_id integer it show user id
User password number
User name char it store user name
4. Supplier Detail
Supplier id integer it show supplier id
Supplier name char it store supplier name
Supplier address number it store supplier address
5. Bill detail
Page
32
Bill_id integer it store bill id of customer
Bill issue date & time number it show bill issue date & time
Bill number number it store bill number of CD/DVD
Bill amount number it store bill amount
Page
33
System Security
System security is the most important asset any

organization holds. It does not matter what form the
information takes, either electronic, or a person’s
knowledge. Whichever way the information is stored, the
need for protection is of paramount importance of system.
System security must be accurate and complete, and
requires protection from unauthorized, unanticipated or
unintentional modification. It also deals with ensuring that
computer programs are changed in a specified and
authorized manner.
 It must be username and password wherewith system

protected and avoid substantial losses.
 Ensuring that data is modified only in authorized ways,

whether by users or by the system.
 It must be data base security. Triggers use of save

unauthorized use data in system and secure database.
 It must be secure enter data in text box if any enter

wrong entry in textbox then show error message.
 It deals with assuring that system users have

uninterrupted access to information and system resources
such as data, programs, and equipment.
Page
34
Future Scope of the Application
The Portal technology will be used to enhance

communication parson’s delivers Portal services. It will
capture storage and management of audio and video are
quite similar and considered together. The music and video
Portal future will provide online information wherewith
possible to information transmission. It will provide online
registration form of customer it will automatic maintain all
customer information. In future you will online purchase and
rent music and video cd through internet. It will be provide
suitable indexing, sorting, searching and retrieving audio
and video information across the internet.
In this future music and video Portal software

very flexible it will improve user ability. It will improve and
extend Portal service through information technology. It will
be automatic index music and video in a line by line manner
and it wills automatically content-based indexing of audio-
video. It will be automatic bill calculate, bill generate of
customer and solve problem and if you purchase audio and
video cd on rent it will automatic generate bill. In the future
music and video Portal most fundamental mission,
knowledge, creation and dissemination. In future you will
touch own Portal card in computer and you will enter in
Portal.
Page
35
Bibliography
Microsoft visual studio 2005
 Visual studio 2005 by Andrew person
 Microsoft visual studio 2005 unleashed by Lars powers
SQL server 2005
 Professional SOL server 2005 high availability by aiian Hirt
 Professional SOL server 2005 programming by Derek

commingore
Software Engineering
 Software Engineering practical paper by Hans van vilet
 Software Engineering (update) (6th edition) (international

computer science) series by LAN Somerville
Page
36
PROJECT
REPORT
Page
37
Introduction Of The Project

The Music and video Portal is work on manual process.
And It is working on old technology Therefore very difficult of maintain
record. There in possible of mistake in record where all record of music
and video cd is not possible. There in make possible human error. And
very difficult to search music and video cd in Portal and very difficult of
indexing of all music and video cd.
The music and video digital Portal of the future will

provide electronic access to information in many different from recent
technological advances make the Transmission of digital music and
video information possible This paper will describe the design of a
music and video Portal suitable for storing, indexing, searching and
retrieving music and video information and providing that information
across the internet or the evolving information infrastructure to be an
effective Portal user need to be able to find the music and video
segment.
They want realizing this goal will require ground – breaking

research into automatic content based indexing of video that will
significantly improved the user ability to access specific segment of
interest with video and transcript will be digitized and information
from the sound track and transcript will be used to automatically
index music and video in a frame by frame manner. It will search and
alert information of music and video cd in Portal. It will repair all error
in data in Portal the non textual information such as sound, images,
video and scientific data require considerably more storage per item
the music and video software work fast process.
Page
38
Objective
 Music and video Portal system consist of processing program to
manipulate compress , compact and analyze the music and video
component of a segment
 Information retrieval engine the(IRE) is used to store indices

extracted from music and video segment
 Improve and extend Portal service through software
 Construct and maintain a web site that is useful to staff and the
community
 Monitor and evaluate the demand and supply for technology

related Portal service
 Maximum source of technology finding consistent with the

technology plan
 Maintain a process to evaluate technology for the music and

video Portal
 It will be maintain fast process and more suitable
 It will be user friendly
 It will error free and correct mistake record
 It will be keep all record of Portal
 It keep record all music and video cd purchase
 It keep all receipt record of music and video cd
 It generate automatic sales and purchase record
 It will show all music and video cd automatically in Portal
 It show date of purchase music and video cd in Portal
Page
39
TOOLS/PLATFORM TO BE USED
Software Requirenment
 Front End :- Asp.Net using C#
 Back End :- SQL server 2012
 OS :- Windows 8.1
 Web server :- IIS 8.0
Hardware Requirenment
 CPU :- AMD 4GB
 Motherboard :- 1GB
 RAM :- 4GB
 Hard Disk :- 500 GB
 Moniter :- 15.6inch
 Keyboard :- Qwerty
 Mouse :- Optical
Page
40
System Analysis
System analysis then is the process of gathering and interpreting

facts, diagnosing problem and using the information to recommend
improvement to the system. It is fairly well – established fact that
errors in a system are more easily and inexpensively rectified.
Customer problem
The most difficult task of keep all customer record in
manual process. If any new customer registration in Portal then
not gives proper information of customer. And There in is
mistake customer fill up form and very difficult to bill calculate
process. And waiting for receiving bill of customer. There in very
difficult of save record in Portal. Many staff member not care of
customer. If any customer want to purchase cd then waste
many time of customer. Many staff worker forget given rent slip
of customer and taken extra charge to customer. Many music
and video cd have different place in Portal where with very
difficult search CD/DVD. And fill up form separate counter in
Portal wherewith problem of customer for fill up form.
Page
41
(a) FEASIBILITY STUDY
Feasibility study looks at the viability of an idea with an emphasis on
identifying potential problems and attempts to answer one main
question: Will the idea work and should I proceed with it? It provides
in-depth details determine if and how it can succeed, and serve as a
valuable tool for developing a winning business plan. The information
gathered by feasibility study helps in listing all the things needed,
identify logical and other business-related problems and solutions, and
serve as a solid foundation for developing business plan. There are
three types of feasibility study:
3 Types :-
(i) Economical feasibility
(ii) Technical feasibility
(iii) Operational feasibility
Page
42
(i) ECONOMICAL FEASIBILITY
Economic feasibility analysis is the process of determining whether the
cost and time investment is worth or not. It is also known as cost
benefit analysis. The procedure is to determine the benefits and
savings that are expected from Music & Video Universe and compare
them with the total costs. Gantt & PERT Charts are useful tools in Cost
Benefit Analysis. If the benefits outweigh costs, a decision is taken to
design and implement the system otherwise further justification or the
alternative measure will have to be made if it is to have a chance of
being approved.
(ii) TECHNICAL FEASIBILTY
Technical feasibility analysis analyses the availability of technology
and resources. A large part of determining resources has to do with
assessing technical feasibility. It considers the technical
requirements and then it is compared with the technical capability
of the organization. I have chosen Microsoft Windows 7, ASP.NET
using C#, and MS SQL Server. Microsoft SQL Server is a feature rich
database compared to MySQL
Page
43
(iii) OPRATIONAL FEASIBILITY
The questions that help in testing operational feasibility are:
Whether there will be resistance from users that will affect the possible
application benefits?
Whether the system will operate when installed?
Whether the system will be used?
Operational feasibility is dependent on human resources available for
the project and involves projecting whether the system will operate
and be used once it is installed. The reason Music & Video Universe is
easy to operate is because of a rather user-friendly layout & interface,
and also features such as graphics and search to make navigation
easier.
(b) FACT FINDING

Fact Finding is the formal process of using research,
interviews, questionnaires, and other techniques to collect
information about systems, requirements, and preferences. It
is also called information gathering or data collection. Facts
and all relevant information are needed to be collected to
study any system. These facts when expressed in quantitative
form are termed as data.
Page
44
(i) Interviewing:
Interviewing is a very important method of fact finding. Analysts
can use interviews to collect information about the current system
form the potential users. Here the analysts discover the areas of
misunderstanding, unrealistic exception and descriptions of
activities and problems along with resistance.
I have personally interviewed a number of (regular) users of
different Music & video websites about the features they like in such
websites, their limitations, and which are the new features that they
would like to see.
(ii) On-site Observation:
On-site observations are one of the most effective tools with the
analyst where the analyst personally goes to the site and discovers
the functioning of the system. It is a process which involves
observing, recording, and interpreting the expert's problem-solving
process while it takes place.
Compared to the process of interviewing, on-site observation brings
the knowledge developer closer to the actual steps, techniques, and
procedures used. To gather some facts, I have visited and observed
a few websites currently dedicated to the coverage of Cricket such
Page
45
as www.MusicManza.com and have observed their features
carefully.
(III) Questionnaires:
Here the analysts can collect data from large groups. The
Questionnaire consists of series of questions framed together in
logical manner. The questions are simple, clear and to the point.
Questionnaires could be Open- ended or Close questionnaires.
Open-ended questionnaires are used to learn feelings, opinions,
general experiences on process detail or problem. In it, questions
are answered in their own words; whereas in closed questionnaires
a set of prescribed answers are used and specific response have to
be selected.
Page
46
SOFTWARE REQUIREMENTS SPECIFICATIONS (SRS)
A Software Requirements Specification (SRS) - a requirements
specification for a software system - is a complete description of the
behavior of a system to be developed. It includes a set of use cases that
describe all the interactions the users will have with the software. Use
cases are also known as functional requirements. In addition to use
cases, the SRS also contains non-functional (or supplementary)
requirements. Non-functional requirements are requirements which
impose constraints on the design or implementation (such as
performance engineering requirements, quality standards, or design
constraints).
The software requirement specification (SRS) document generates all
necessary requirements for project development. To derive the
requirements we need to have clear and thorough understanding of the
products to be developed. This is prepared after detailed
communications with project team and the customer.
An SRS clearly defines the following:
1. External interfaces of the system: They identify the information
which is to flow 'from and to' the system.
Page
47
2. Functional and non-functional requirements of the systems. They
stand for the finding of run-time requirements.
3. Design constraints
The SRS outline is given below:
1. Introduction
(i) Purpose :- This software is implemented to automate the
daily Update Music and Movie.
(ii) Scope :- This Software will maintain all the data related to
Latest Music, Video and Album Details.
(iv) References :- Software Engineering approach/By Roger S.
Pressman, Pro Asp.Net using C#-APress, Microsoft SQL
Server, Wrox.
(v) Overview :- This Software will manage the Latest Music
Updates and Latest Movies Released. This Software will also
maintain the Music Records details.
Page
48
2. Overall Descriptions
2.1 Product perspective :- This is web based Software Which
can be accessed from any Record of music and video around the world.
2.1.1 System interfaces

(Context Diagram)
1.1.2 User interfaces
(i) User login
(ii) User Logout
(iii) Music & Video
(iv) Latest Movies
(v) Old Movies & Music
(vi) Add Product
Page
49
1.1.3 Hardware interface
1. CPU :- AMD A6 4GB
2. Motherboard :- 1GB
3. RAM :- 4 GB
4. Hard Disk :- 500 GB
5. Moniter :- 15.6’ HD Display
6. Keyboard :- Qwerty
7. Mouse :- Optical
1.1.4 Software interfaces
(i) Frontend - Asp.Net using C#
(ii) Backend - SQL Server 2012
(iii) Operating System - Windows 8.1
Page
50
1.1.5 Memory Constraints
This Software will have many transactions in its daily
Oprations. Hence, Large memory space is required
and Periodic backup and Cleanups are also required.
1.2 Product functions
(i) User :- This Software will record the
Multiple users, They users can login or logout.
(ii) Music & Video :- This Software will
maintain the details of all Music & Video, and They
also shown a whose Music & Movie released on
today.
(iii) Movies :- This Software will provide for
the users which Movie Released that day and
Available or Place.
(iv) Add Product :- This Software will
provide for the users they Many Product they added
by Admin.
Page
51
1.3 User characteristics
2.4 Constraints :- This Software will provide the
payment facility. This Software will maintain the sale
purchase the Movies and Albums.
Page
52
2. Specific requirements
2.1 Specific requirements
3.1.1 Sequence diagram
2.1.2 Classes for Classification
2.2 Performance requirements :- This is a web
based software , hence a very good performance and
quick response time required.
2.3 Software system attributes
3.3.1 Reliability :- This software will have proper backup
and recovery implementation and Error messages on
invalid inputs.
3.3.2 Availability :- This software will be available to
Singer and singer records who are already registered in
the software.
3.3.3 Security :- This software will have both types of
security implemented that is client side security, server
side security.
Page
53
3.3.4 Maintainability :- This software will be
implemented using the concepts of oops which make it easy
maintain & extend.
3.3.5 Other requirements :- This software must be
more user friendly so that any technical or non-technical
user use it easily.
Page
54
FUNCTIONAL REQUIREMENTS
In software engineering, a functional requirement defines a function of a
software system or its component. A function is described as a set of
inputs, the behaviour, and outputs.
Functional requirements may be calculations, technical details, data
manipulation and processing and other specific functionality that define
what a system is supposed to accomplish. Behavioural requirements
describing all the cases where the system uses the functional
requirements are captured in use cases. Functional requirements are
supported by non-functional requirements (also known as quality
requirements), which impose constraints on the design or
implementation (such as performance requirements, security, or
reliability).
This proposed system will automate all the details related to Music and
Video at a single portal. Any user can get any information, record,
announcements etc. by just a single click.
This portal will achieve the following objectives:
 It will have an user-friendly interface.
Page
55
 Registered users can see Latest Movie, music and Albums.
 It will maintain records of Music from different countries as well
as different clubs.
 Users can view records of previous Albums and music.
 It will also provide the information about the upcoming Latest
Movies and music.
 This portal will provide videos, images & wallpapers of Movies,
songs, Albums etc.
 It also contains a built-in search feature, which helps users find
information quicker.
 This portal will provide user management facility i.e. every user
will get a unique user name & password for authorized access.
Page
56
NON-FUNCTIONAL REQUIREMENT
In systems engineering and requirements engineering, a non-functional
requirement is a requirement that specifies criteria that can be used to
judge the operation of a system, rather than specific behaviours. This
should be contrasted with functional requirements that define specific
behaviour or functions. The plan for implementing functional
requirements is detailed in the system design. The plan for
implementing non-functional requirements is detailed in the system
architecture.
Non-functional requirements are often called qualities of a system.
Other terms for non-functional requirements are "constraints", "quality
attributes", "quality goals", "quality of service requirements" and "non-
behavioural requirements". Qualities, that is non-functional
requirements, can be divided into two main categories:
1. Execution qualities, such as security and usability, which are
observable at run time.
2. Evolution qualities, such as testability, maintainability,
extensibility and scalability, which are embodied in the static structure
of the software system.
Page
57
Attributes of Quality-
1. Compatibility- The ability of two or more system to perform their
required functions on same hardware.
2. Correctness- A program is functionally correct it behaves
according to the specifications it should provide.
3. Reliability- It is the ability that the s/w will operate as expected
over a specified time.
4. Robustness – It is the degree to which the s/w can function
correctly in the presence of invalid inputs.
5. User friendly- A s/w is said to be user friendly if it is easy to use &
a user can easily use it.
6. Portability- It is the ease with which a s/w can be transferred
from one H/W or S/W environments.
7. Maintainability- It is the ease with which a s/w system can be
modified to correct faults & improve.
8. Reusability – It is the degree to which a s/w module can be used
in more than one computer program or a s/w system.
Page
58
Life Cycle Methodology
Waterfall Model:-
The Waterfall Model was first process Model to be
introduced. It is also referred to as a linear-sequential life cycle model. It is
very simple to understand and use. In a waterfall model, each phase must
be completed fully before the next phase can begin. This type of model is
basically used for the project which is small and there are no uncertain
requirements. At the end of each phase, a review takes place to determine
if the project is on the right path and whether or not to continue or discard
the project. In this model the testing starts only after the development is
complete. In waterfall model phases do not overlap.
 This model is used only when the requirements are very well known,
clear and fixed.
 Product definition is stable.
 Technology is understood.
 There are no ambiguous requirements.
 Ample resources with required expertise are available freely.
 The project is short.
Page
59
Stage 1: Requirement Phase
Whether you design a small program to add two numbers or you are
into developing a software system for the automation of an entire
airline company, this is the first stage which can never be overridden.
Unless you know what you are going to design, you cannot approach the
problem. Here, the specifications of the output or the final product is
studied and marked. If the software that is going to be designed should
not contain certain features, for reasons like security, then it is also
mentioned in this stage.
Stage 2: Specification Phase
With all the requirements and constraints in hand, a final view of how
the product should exactly be, is decided. The exact way in which the
software should function is mentioned in this stage.
Stage 3: Design Phase
Well, here the actual work begins. Every type of resource which will be
required for the smooth designing of the software is mentioned here in
this phase. What type of database will be required, what type of data
should be supported, etc. are some of the important aspects that are
decided in this phase. The algorithm of the process in which the
Page
60
software needs to be designed is made in this phase. This algorithm
forms the backbone for the actual coding part in the next phase.
Stage 4: Implementation and Testing Phase
Now starts the coding part. Here, the software is designed as per the
algorithm. Hence it becomes very important that the algorithm should
be properly designed. The software designed as per the algorithm needs
to go through constant software testing and error correction processes
to find out if there are any flaw or errors. The output of this stage should
be a well designed software which is at par with the algorithm designed.
Stage 5: Integration and Testing Phase
Here the various codes designed by different programmers are
integrated together and is tested if the software works as per the
specifications provided. The setup of the final software which needs to
be installed at the clients system is also designed and tested so that the
client does not face any problem during the installation of the software.
The product is then handed over to the client.
Stage 6: Maintenance Phase
The work of software development does not end with the handing of the
software to the client. The software designers may have to constantly
Page
61
provide support to the client to resolve any of the issues which may
arise. There may be some flaws which get detected during the actual
implementation of the project. During the maintenance phase, support
and debugging is provided for all such problems.
Stage 7: New Requirements Phase
Changing times may require that the product requirements be changed.
The client company may be expanding into other fields and it may want
new features to be added over to the existing software. Hence, it is very
important that the updated requirements be taken from the client. This
requires the entire product life cycle to start all over again.
Advantages of Waterfall Model
The waterfall model is the oldest and most widely used model in the
field of software development. There are certain advantages of the
waterfall model, which causes it to be the most widely used model as
yet. Some of them can be listed as under.
• Needless to mention, it is a linear model and of course, linear
models are the most simple to be implemented.
• The amount of resources required to implement this model is
very minimal.
Page
62
COCOMO MODEL
The Constructive Cost Model (COCOMO) is an algorithmic software cost
estimation model developed by Barry Boehm. The model uses a basic
regression formula, with parameters that are derived from historical
project data and current project characteristics.
COCOMO was first published in 1981 Barry W. Boehm's Book Software
engineering economics as a model for estimating effort, cost, and
schedule for software projects. It drew on a study of 63 projects at TRW
Aerospace where Barry Boehm was Director of Software Research and
Technology in 1981. The study examined projects ranging in size from
2,000 to 100,000 lines of code, and programming languages ranging
from assembly to PL/I. These projects were based on the waterfall
model of software development which was the prevalent software
development process in 1981.
References to this model typically call it COCOMO 81. In 1997 COCOMO
II was developed and finally published in 2000 in the book Software
Cost Estimation with COCOMO II. COCOMO II is the successor of
COCOMO 81 and is better suited for estimating modern software
development projects. It provides more support for modern software
Page
63
development processes and an updated project database. The need for
the new model came as software development technology moved from
mainframe and overnight batch processing to desktop development,
code reusability and the use of off-the-shelf software components. This
article refers to COCOMO 81.
COCOMO consists of a hierarchy of three increasingly detailed and
accurate forms. The first level, Basic COCOMO is good for quick, early,
rough order of magnitude estimates of software costs, but its accuracy is
limited due to its lack of factors to account for difference in project
attributes (Cost Drivers). Intermediate COCOMO takes these Cost
Drivers into account and Detailed COCOMO additionally accounts for the
influence of individual project phases.
Basic COCOMO
Basic COCOMO computes software development effort (and cost) as a
function of program size. Program size is expressed in estimated
thousands of lines of code (KLOC).
COCOMO applies to three classes of software projects:
• Organic projects - "small" teams with "good" experience working
with "less than rigid" requirements
Page
64
• Semi-detached projects - "medium" teams with mixed experience
working with a mix of rigid and less than rigid requirements
• Embedded projects - developed within a set of "tight" constraints
(hardware, software, operational, ......)
The basic COCOMO equations take the form
Effort Applied = ab(KLOC)bb [ man-months ]
Development Time = cb(Effort Applied)db [months]
People required = Effort Applied / Development Time [count]
Intermediate COCOMOs
Intermediate COCOMO computes software development effort as
function of program size and a set of "cost drivers" that include
subjective assessment of product, hardware, personnel and project
attributes. This extension considers a set of four "cost drivers",each with
a number of subsidiary attributes:-
• Product attributes
o Required software reliability
o Size of application database
o Complexity of the product
• Hardware attributes
Page
65
o Run-time performance constraints
o Memory constraints
o Volatility of the virtual machine environment
o Required turnabout time
• Personnel attributes
o Analyst capability
o Software engineering capability
o Applications experience
o Virtual machine experience
o Programming language experience
• Project attributes
o Use of software tools
o Application of software engineering methods
o Required development schedule
Detailed COCOMO
Detailed COCOMO - incorporates all characteristics of the intermediate
version with an assessment of the cost driver's impact on each step
(analysis, design, etc.) of the software engineering process 1.
Page
66
SCHEDULING TECHNIQUES
Scheduling is an important tool for manufacturing and engineering,
where it can have a major impact on the productivity of a process. In
manufacturing, the purpose of scheduling is to minimize the production
time and costs, by telling a production facility when to make, with which
staff, and on which equipment. Production scheduling aims to maximize
the efficiency of the operation and reduce costs.
Production scheduling tools greatly outperform older manual
scheduling methods. These provide the production scheduler with
powerful graphical interfaces which can be used to visually optimize
real-time workloads in various stages of production, and pattern
recognition allows the software to automatically create scheduling
opportunities which might not be apparent without this view into the
data. For example, an airline might wish to minimize the number of
airport gates required for its aircraft, in order to reduce costs, and
scheduling software can allow the planners to see how this can be done,
by analyzing time tables, aircraft usage, or the flow of passengers.
Page
67
Companies use backward and forward scheduling to allocate plant and
machinery resources, plan human resources, plan production processes
and purchase materials.
Forward scheduling is planning the tasks from the date resources
become available to determine the shipping date or the due date.
Backward scheduling is planning the tasks from the due date or
required-by date to determine the start date and/or any changes in
capacity required.
The benefits of production scheduling include:
• Process change-over reduction
• Inventory reduction, leveling
• Reduced scheduling effort
• Increased production efficiency
• Labor load leveling
• Accurate delivery date quotes
• Real time information
Scheduling consists several functions:-
1) GANTT Chart
2) PERT Chart
Page
68
GANTT CHART
A Gantt chart is a graphical representation of the duration of tasks
against the progression of time. A Gantt chart is a useful tool for
planning and scheduling projects. It is helpful when monitoring a
project's progress. It helps plan and monitor project development or
resource allocation. The left hand side of the Gant chart is a column with
lists of tasks. The horizontal axis is a time scale, expressed either in
absolute or relative time.
In a Gantt chart, each task takes up one row. Dates run along the top in
increments of days, weeks or months. Rows of bars in the Gantt chart
show the start and end dates of each task in the project. Tasks may run
sequentially, in parallel or overlapping.
A Gantt chart is an excellent tool in the hands of project managers who
wish to visualize, schedule, and track scheduled and actual progress of
projects. Its graphical nature allows executives and non-managers to
readily understand project flow, without a requiring a complete tutorial
in project management.
Page
69
A Gantt chart lets us see immediately what should have been achieved
at any point in time. It also lets us see how remedial action may bring
the project back on course.
Most Gantt charts include "milestones" which are technically not
available on Gantt charts. However, for representing deadlines and
other significant events, it is very useful to include this feature on a
Gantt chart.
Use Gantt chart at project scheduling stage to:-
• Assess time characteristics to a project
• Show the task order
• Define resources involved
• Show links between scheduled tasks
Use Gantt chart at project planning stage to:-
• Monitor project completion
• Display the results of correctional activities
• Show links between scheduled tasks
Page
70
Page
71
PERT CHART
The Program Evaluation and Review Technique (PERT) is a network
model that allows for randomness in activity completion times. It has
the potential to reduce both the time and cost required to complete a
project.
A PERT chart is a project management tool used to schedule, organize,
and coordinate tasks within a project
Complex projects require a series of activities, some of which must be
performed sequentially and others that can be performed in parallel
with other activities. This collection of series and parallel tasks can be
modeled as a network.
In a project, an activity is a task that must be performed and an event is
a milestone marking the completion of one or more activities. Before an
activity can begin, all of its predecessor activities must be completed.
Project network models represent activities and milestones by arcs and
nodes. PERT originally is an activity on arc network, in which the
activities are represented on the lines and milestones on the nodes.
Page
72
Benefits of PERT:-
PERT is useful because it provides the following information:
 Expected project completion time.

 Probability of completion before a specified date.
 The critical path activities that directly impact the completion
time.
 The activities that have slack time and that can lend resources
to critical path activities.
 Activity starts and end dates.
Steps in the PERT Planning Process:-
PERT planning involves the following steps:
1. Identify the specific activities and milestones.

2. Determine the proper sequence of the activities.
3. Construct a network diagram.
4. Estimate the time required for each activity.
5. Determine the critical path.
Page
73
RISK ANALYSIS & MANAGEMENT
What is Risk?
Risk is defined as "The possibility of suffering harm or loss; danger."
Even if we're not familiar with the formal definition, most of us have an
innate sense of risk. We are aware of the potential dangers that
permeate even simple daily activities, from getting injured when
crossing the street to having a heart attack because our cholesterol level
is too high. Although we prefer not to dwell on the myriad of hazards
that surround us, these risks shape many of our behaviors. Experience
(or a parent) has taught us to look both ways before stepping off the
curb and most of us at least think twice before ordering a steak. Indeed,
we manage personal risks every day.
Risks in Software Project Management: -

Unlike the hazards of daily living, the dangers in the young and
emerging field of software engineering must often be learned without
the benefit of lifelong exposure. A more deliberate approach is required.
Such an approach involves studying the experiences of successful
project managers as well as keeping up with the leading writers and
thinkers in the field. One such writer in the area of risk is Dr. Barry W.
Page
74
Boehm. In his article "Software Risk Management: Principles and
Practices" he lists the following top 10 software risk items:
1. Personnel Shortfalls
2. Unrealistic schedules and budgets
3. Developing the wrong functions and properties
4. Developing the wrong user interface
5. Gold-plating
6. Continuing stream of requirements changes
7. Shortfalls in externally furnished components
8. Shortfalls in externally performed tasks
9. Real-time performance shortfalls
10. Straining computer-science capabilities

Risk is the net negative impact of the exercise of vulnerability,
considering both the probability and the impact of occurrence. Risk
management is the process of identifying risk, assessing risk, and taking
steps to reduce risk to an acceptable level. This guide provides a
foundation for the development of an effective risk management
program, containing both the definitions and the practical guidance
necessary for assessing and mitigating risks identified within projects.
Page
75
The ultimate goal is to help organizations to better manage project-
related mission risks.
The objective of performing risk management is to enable the
organization to accomplish its mission(s) (1) by better securing the
systems that store, process, or transmit organizational information; (2)
by enabling management to make well-informed risk management
decisions to justify the expenditures that are part of an project budget;
and (3) by assisting management in authorizing (or accrediting) the
systems on the basis of the supporting documentation resulting from
the performance of risk management.
How to Manage: -
In the same article, Dr. Boehm describes risk management as being
comprised of the following activities:
 Risk Assessment (figuring out what the risks are and what to
focus on)
 - making a list of all of the potential dangers that will affect

the project
 - assessing the probability of occurence and potential loss of
each item listed
Page
76
 - ranking the items (from most to least dangerous)
 Risk Control (doing something about them)
 coming up with techniques and strategies to mitigate the

highest ordered risks
 implementing the strategies to resolve the high order risks
factors
monitoring the effectiveness of the strategies and the changing levels of

risk throughout the project
Page
77
SYSTEM DESIGN
Systems design is the process of defining the architecture, components,
modules, interfaces, and data for a system to satisfy
specified requirements. One could see it as the application of systems
theory to product development. There is some overlap with the
disciplines of systems analysis, systems architecture and systems
engineering. If the broader topic of product development "blends the
perspective of marketing, design, and manufacturing into a single
approach to product development, then design is the act of taking the
marketing information and creating the design of the product to be
manufactured. Systems design is therefore the process of defining and
developing systems to satisfy specified requirements of the user. Until
the 1990s systems design had a crucial and respected role in the data
processing industry. In the 1990s standardization of hardware and
software resulted in the ability to build modular systems. The increasing
importance of software running on generic platforms has enhanced the
discipline of software engineering.Object-oriented analysis and
design methods are becoming the most widely used methods for
computer systems design. The UML has become the standard language
Page
78
in object-oriented analysis and design. It is widely used for modelling
software systems and is increasingly used for high designing non-
software systems and organizations.
The purpose of System Design is to create a technical solution that
satisfies the functional requirements for Music & Video Universe. At
this point in the project lifecycle there should be a Functional
Specification, written primarily in business terminology, containing a
complete description of the operational needs of the various
organizational entities that will use the new system. The challenge is to
translate all of this information into Technical Specifications that
accurately describe the design of the system, and that can be used as
input to System Construction.
The Functional Specification produced during System Requirements
Analysis is transformed into a physical architecture. System
components are distributed across the physical architecture, usable
interfaces are designed and prototyped, and Technical Specifications are
created for the Application Developers, enabling them to build and test
the system.
Page
79
MODULAR DESIGN
Movies HISTORY
Products
ADMIN USER name

Music &Video
CD/DVD _id
SEARCH DETAIL
Page
80
MODULAR DESCRIPTION
 User
 Movies History
 Admin
 Product
 Details
 Search
User: It will maintain the details of all registered users with their
username & passwords so they can login to use various facilities on this
site.
Movie History: This module will maintain the history of all the Movies.
Admin: It will maintain the records of all the Add product music &
video.
Product: This module will show the Stocks of the available products.
Details: It will show the Details related to Particular Movie and Albums.
Search: This module will help in searching various details like Movies,
Albums etc.
Page
81
Entity Relationship Diagram (E-RD)
Customer _id
CD/DVD price
Customer _ name
CD/DVD _id
CD/DVD name
Customer_ sex
Purchase /rent
Customer CD /DVD
CD/DVD _number
Customer
Address
Pays
Supplied
By
Bill issue_ date & time
User _ id
Supplier_ id Bill id
User_ password
Supplier name Supplier Bill

User
Supplier address Bill amount
User_ name Bill number
Generate
Page
82
Class Diagram
Registration Customer Registration CD & DVD

Customer_ID : int CD/DVD Name : char
Customer_Name : char CD/DVD_ID: int
Customer_Age : int
CD/DVD_Price: int
Customer_Sex : har
Register () Purchase CD/DVD()
Login ()
Payment
Search ()
Payment_ID : int
Payment_date : int
Payment_mode : char
Do_Payment()
Page
83
Use Case Diagram

Make Payment
Sign IN
Sign out
Search
User
Report generate
New CD entry
User name &
password
Admin
Login
Select check password
` Enter old password
New password
Confirm password
User
Change
Page
84
Data Flow Diagram(DFD)
‘0’ LEVEL DFD
Cancellation
Registration make payment

Billing
Customer
Audio
Customer _id
Video
Transaction ID
Library
Admin
Registration manages
CD_NO search
CD/DVD
CD _NO
Availability
Stock
Cancellation
Page
85
1ST LEVEL DFD
Customer Request
For
Return cd
Request
Request
For
For Canceling
Fill up Cd issue
form
Calculate
Check Issue date
Pay amount Registration Return date

CD _stock
Check Detail
Yes The No
Error
Amount Yes
Message Diff > 2 days
No
Generate Check
Cancel No
Registration Cd available
Registration Yes Yes

Number
Charge
Issue
Fine
Cd
Customer _ detail
CD_ stock
Admin Return
Cd
Page
86
2ND LEVEL DFD
New registration process
Fill up Pay Generate
Customer Form Amount Registration
Number
Customer _ detail Admin
Canceling of registration process
Request Check Pay

For Due Yes
Customer Amount
Canceling Amount
No
Canceling
Admin
Registration
Customer_ detail
Page
87
2ND LEVEL DFD

Issue CD
Check Error
Request Check
Yes CD available no
Customer For Registration Message
detail
Cd _issue
Yes
Issue
CD
CD_stock
Admin
Return CD
Request
Customer Calculate Diff > Charge
To
Return
Issue date 2 days Yes Fine
Return date No
Cd
Return
CD
CD _ stock
Admin
Page
88
Data Dictionary
1. Customer detail
Customer _id integer it show customer id
Customer name char it store customer name
Customer address char it store customer address
Customer age number it show customer age
Customer sex char it show customer sex
Page
89
2. CD/ DVD Detail
CD/DVD name char it show CD/DVD name
CD/DVD id number it is store CD/DVD id
CD/DVD price char it store CD/DVD price
CD/DVD number number it store CD/DVD number
Page
90
3. User Detail
User_id integer it show user id
User password number
User name char it store user name
4. Supplier Detail
Supplier id integer it show supplier id
Supplier name char it store supplier name
Supplier address number it store supplier address
Page
91
5. Bill detail
Bill_id integer it store bill id of customer
Bill issue date & time number it show bill issue date & time
Bill number number it store bill number of CD/DVD
Bill amount number it store bill amount
Page
92
TESTING
Software Testing is the process of executing a program or system with the
intent of finding errors. Or, it involves any activity aimed at evaluating an
attribute or capability of a program or system and determining that it meets
its required results. Software is not unlike other physical processes where
inputs are received and outputs are produced. Where software differs is in the
manner in which it fails. Most physical systems fail in a fixed (and reasonably
small) set of ways. By contrast, software can fail in many bizarre ways.
Detecting all of the different failure modes for software is generally infeasible.
Unlike most physical systems, most of the defects in software are design
errors, not manufacturing defects. Software does not suffer from corrosion,
wear-and-tear -- generally it will not change until upgrades, or until
obsolescence. So once the software is shipped, the design defects -- or bugs --
will be buried in and remain latent until activation.
Software bugs will almost always exist in any software module with moderate
size: not because programmers are careless or irresponsible, but because the
complexity of software is generally intractable -- and humans have only
limited ability to manage complexity. It is also true that for any complex
systems, design defects can never be completely ruled out.
Page
93
Discovering the design defects in software, is equally difficult, for the same
reason of complexity. Because software and any digital systems are not
continuous, testing boundary values are not sufficient to guarantee
correctness. All the possible values need to be tested and verified, but
complete testing is infeasible. Exhaustively testing a simple program to add
only two integer inputs of 32-bits (yielding 2^64 distinct test cases) would
take hundreds of years, even if tests were performed at a rate of thousands
per second. Obviously, for a realistic software module, the complexity can be
far beyond the example mentioned here. If inputs from the real world are
involved, the problem will get worse, because timing and unpredictable
environmental effects and human interactions are all possible input
parameters under consideration.
A further complication has to do with the dynamic nature of programs. If a
failure occurs during preliminary testing and the code is changed, the
software may now work for a test case that it didn't work for previously. But
its behavior on pre-error test cases that it passed before can no longer be
guaranteed. To account for this possibility, testing should be restarted. The
expense of doing this is often prohibitive.
Page
94
An interesting analogy parallels the difficulty in software testing with the
pesticide, known as the Pesticide Paradox: Every method you use to prevent
or find bug sleeves a residue of subtler bugs against which those methods are
ineffectual. But this alone will not guarantee to make the software better,
because the Complexity Barrier principle states: Software complexity (and
therefore that of bugs) grows to the limits of our ability to manage that
complexity. By eliminating the (previous) easy bugs you allowed another
escalation of features and complexity, but his time you have subtler bugs to
face, just to retain the reliability you had before. Society seems to be unwilling
to limit complexity because we all want that extra bell, whistle, and feature
interaction.
Page
95
TEST PLANS
A test plan documents the strategy that will be used to verify and ensure that
a product or system meets its design specifications and other requirements.
The plan typically contains a detailed understanding of what the eventual
workflow will be. A test plan is usually prepared by or with significant input
from Test Engineers.
Depending on the product and the responsibility of the organization to which
the test plan applies, a test plan may include one or more of the following:
 Design Verification or Compliance test - to be performed during the
development or approval stages of the product, typically on a small
sample of units.
 Manufacturing or Production test - to be performed during preparation
or assembly of the product in an ongoing manner for purposes of
performance verification and quality control.
 Acceptance or Commissioning test - to be performed at the time of
delivery or installation of the product.
 Service and Repair test - to be performed as required over the service
life of the product.
Page
96
 Regression test - to be performed on an existing operational product, to
verify that existing functionality didn't get broken when other aspects of
the environment are changed (e.g., upgrading the platform on which an
existing application runs).
A complex system may have a high level test plan to address the overall
requirements and supporting test plans to address the design details of
subsystems and components.
Test plan document formats can be as varied as the products and
organizations to which they apply. There are three major elements that should
be described in the test plan: Test Coverage, Test Methods, and Test
Responsibilities. These are also used in a formal test strategy.
Test coverage
Test coverage in the test plan states what requirements will be verified during
what stages of the product life. Test Coverage is derived from design
specifications and other requirements, such as safety standards or regulatory
codes, where each requirement or specification of the design ideally will have
one or more corresponding means of verification. Test coverage for different
product life stages may overlap, but will not necessarily be exactly the same
for all stages. For example, some requirements may be verified during Design
Page
97
Verification test, but not repeated during Acceptance test. Test coverage also
feeds back into the design process, since the product may have to be designed
to allow test access.
Test methods
Test methods in the test plan state how test coverage will be implemented.
Test methods may be determined by standards, regulatory agencies, or
contractual agreement, or may have to be created new. Test methods also
specify test equipment to be used in the performance of the tests and establish
pass/fail criteria. Test methods used to verify hardware design requirements
can range from very simple steps, such as visual inspection, to elaborate test
procedures that are documented separately.
Test responsibilities
Test responsibilities include what organizations will perform the test methods
and at each stage of the product life. This allows test organizations to plan,
acquire or develop test equipment and other resources necessary to
implement the test methods for which they are responsible. Test
responsibilities also includes, what data will be collected, and how that data
will be stored and reported (often referred to as "deliverables").
Page
98
TESTING TYPES
White Box Testing:-
White box testing is a security testing method that can be used to validate
whether code implementation follows intended design, to validate
implemented security functionality, and to uncover exploitable vulnerabilities.
It is also called as Structural or Glass box testing.
The purpose of any security testing method is to ensure the robustness
of a system in the face of malicious attacks or regular software failures. White
box testing is performed based on the knowledge of how the system is
implemented. White box testing includes analyzing data flow, control flow,
information flow, coding practices, and exception and error handling within
the system, to test the intended and unintended software behavior. White box
testing can be performed to validate whether code implementation follows
intended design, to validate implemented security functionality, and to
uncover exploitable vulnerabilities
White Box Testing is coverage of the specification in the code:
White box testing involves looking at the structure of the code. White box
testing requires access to the source code. Though white box testing can be
Page
99
performed any time in the life cycle after the code is developed, it is a good
practice to perform white box testing during the unit testing phase.
White box testing requires knowing what makes software secure or insecure,
how to think like an attacker, and how to use different testing tools and
techniques.
 The first step in white box testing is to comprehend and analyze
source code, so knowing what makes software secure is a
fundamental requirement.
 Second, to create tests that exploit software, a tester must think like
an attacker.
 Third, to perform testing effectively, testers need to know the
different tools and techniques available for white box testing.
Benefits:-
There are many benefits to white box testing, including the following:
 Analyzing source code and developing tests based on the
implementation details enables testers to find programming errors
quickly. For example, a white box tester looking at the implementation
Page
100
can quickly uncover a way, say, through an error handling mechanism,
to expose secret data processed by a component.
 Executing some (hard to set up) black box tests as white box tests
reduces complexity in test setup and execution. For example, to drive a
specific input into a component, buried inside the software, may require
elaborate setup for black box testing but may be done more directly
through white box testing by isolating the component and testing it on
its own. This reduces the overall cost (in terms of time and effort)
required to perform such tests.
 Validating design decisions and assumptions quickly through white box
testing increases effectiveness. The design specification may outline a
secure design, but the implementation may not exactly capture the
design intent. For example, a design might outline the use of protected
channels for data transfer between two components, but the
implementation may be using an unprotected method for temporary
storage before the data transfer. This increases the productivity of
testing effort.
 Finding “unintended” features can be quicker during white box testing.
Security testing is not just about finding vulnerabilities in the intended
Page
101
functionality of the software but also about examining unintended
functionality introduced during implementation. Having access to the
source code improves understanding and uncovering the additional
unintended behavior of the software. For example, a component may
have additional functions exposed to support interactions with some
other component, but the same functions may be used to expose
protected data from a third component. Depending on the nature of the
“unintended” functionality, it may require a lot more effort to uncover
such problems through black box testing alone.
For a complete software examination, both white box and black box tests are
required.
Black Box Testing:-
Black Box Testing is testing technique having no knowledge of the internal
functionality/structure of the system. This testing technique treats the system
as black box or closed box. Tester will only know the formal inputs and
projected results. Tester does not know how the program actually arrives at
those results. Hence tester tests the system based on the functional
specifications given to him. That is the reason black box testing is also
considered as functional testing. This testing technique is also called as
Page
102
behavioural testing or opaque box testing or simply closed box testing.
Although black box testing is a behavioural testing, Behavioural test design is
slightly different from black-box test design because the use of internal
knowledge is not illegal in behavioural testing.
Black box testing is also known as functional testing which is a software
testing technique whereby the internal workings of the item being tested are
not known by the tester. For example, in a black box test on software design
the tester only knows the inputs and what the expected outcomes should be
and not how the program arrives at those outputs. The tester does not ever
examine the programming code and does not need any further knowledge of
the program other than its specifications.
The advantages of this type of testing include:
 Efficient when used on Larger systems
 As the tester and developer are independent of each other, test is
balanced and unprejudiced
 Tester can be non-technical.
 There is no need of having detailed functional knowledge of system to
the tester.
Page
103
 Tests will be done from an end user's point of view. Because end user
should accept the system. (This is reason, sometimes this testing
technique is also called as Acceptance testing)
 Testing helps to identify the vagueness and contradiction in functional
specifications.
 Test cases can be designed as soon as the functional specifications are
complete
 The test is unbiased because the designer and the tester are
independent of each other.
 The tester does not need knowledge of any specific programming
languages.
 The test is done from the point of view of the user, not the designer.
 Test cases can be designed as soon as the specifications are complete.
The disadvantages of this type of testing include:
 Test cases are tough and challenging to design, without having clear
functional specifications
Page
104
 It is difficult to identify tricky inputs, if the test cases are not developed
based on specifications.
 It is difficult to identify all possible inputs in limited testing time. So
writing test cases is slow and difficult
 Chances of having unidentified paths during this testing
 Chances of having repetition of tests that are already done by
programmer.
 The test can be redundant if the software designer has already run a test
case.
Testing every possible input stream is unrealistic because it would take
an inordinate amount of time; therefore, many program paths will go
untested.
Page
105
LEVELS OF TESTING
Unit testing refers to tests that verify the functionality of a specific section of
code, usually at the function level. In an object-oriented environment, this is
usually at the class level, and the minimal unit tests include the constructors
and destructors.
These types of tests are usually written by developers as they work on code
(white-box style), to ensure that the specific function is working as expected.
One function might have multiple tests, to catch corner cases or other branches
in the code. Unit testing alone cannot verify the functionality of a piece of
software, but rather is used to assure that the building blocks the software
uses work independently of each other.
Unit testing is also called component testing.
Integration testing is any type of software testing that seeks to verify the
interfaces between components against a software design. Software
components may be integrated in an iterative way or all together ("big bang").
Page
106
Normally the former is considered a better practice since it allows interface
issues to be localized more quickly and fixed.
Integration testing works to expose defects in the interfaces and interaction
between integrated components (modules). Progressively larger groups of
tested software components corresponding to elements of the architectural
design are integrated and tested until the software works as a system.
System testing of software or hardware is testing conducted on a complete,
integrated system to evaluate the system's compliance with its specified
requirements. System testing falls within the scope of black box testing, and as
such, should require no knowledge of the inner design of the code or logic.
As a rule, system testing takes, as its input, all of the "integrated" software
components that have successfully passed integration testing and also the
software system itself integrated with any applicable hardware system(s). The
purpose of integration testing is to detect any inconsistencies between the
software units that are integrated together (called assemblages) or between
any of the assemblages and the hardware. System testing is a more limited
type of testing; it seeks to detect defects both within the "inter-assemblages"
and also within the system as a whole.
Page
107
Regression testing focuses on finding defects after a major code change has
occurred. Specifically, it seeks to uncover software regressions, or old bugs
that have come back. Such regressions occur whenever software functionality
that was previously working correctly stops working as intended. Typically,
regressions occur as an unintended consequence of program changes, when
the newly developed part of the software collides with the previously existing
code. Common methods of regression testing include re-running previously
run tests and checking whether previously fixed faults have re-emerged. The
depth of testing depends on the phase in the release process and the risk of the
added features. They can either be complete, for changes added late in the
release or deemed to be risky, to very shallow, consisting of positive tests on
each feature, if the changes are early in the release or deemed to be of low
risk.
Acceptance testing is black-box testing performed on a system prior to its
delivery. It is also known as functional testing, black-box testing, QA testing,
application testing, confidence testing, final testing, validation testing, or
factory acceptance testing.
Software developers often distinguish acceptance testing by the system
provider from acceptance testing by the customer (the user or client) prior to
Page
108
accepting transfer of ownership. In the case of software, acceptance testing
performed by the customer is known as user acceptance testing (UAT), end-user
testing, site (acceptance) testing, or field (acceptance) testing.
Performance Testing covers a broad range of engineering or functional
evaluations where a material, product, system, or person is not specified by
detailed material or component specifications: rather, emphasis is on the final
measurable performance characteristics. Testing can be a qualitative or
quantitative procedure.
Performance testing can refer to the assessment of the performance of a
human examinee. For example, a behind-the-wheel driving test is a
performance test of whether a person is able to perform the functions of a
competent driver of an automobile.
In the computer industry, software performance testing is used to determine
the speed or effectiveness of a computer, network, software program or
device. This process can involve quantitative tests done in a lab, such as
measuring the response time or the number of MIPS (millions of instructions
per second) at which a system functions. Qualitative attributes such as
reliability, scalability and interoperability may also be evaluated. Performance
testing is often done in conjunction with stress testing.
Page
109
Recovery Testing:- In software testing, recovery testing is the activity of
testing how well an application is able to recover from crashes, hardware
failures and other similar problems.
Recovery testing is the forced failure of the software in a variety of ways to
verify that recovery is properly performed. Recovery testing should not be
confused with reliability testing, which tries to discover the specific point at
which failure occurs. Recovery testing is basically done in order to check how
fast and better the application can recover against any type of crash or
hardware failure etc. Type or extent of recovery is specified in the
requirement specifications. It is basically testing how well a system recovers
from crashes, hardware failures, or other catastrophic problems.
Stress Testing:- It is a form of testing that is used to determine the stability of
a given system or entity. It involves testing beyond normal operational
capacity, often to a breaking point, in order to observe the results. Stress
testing may have a more specific meaning in certain industries, such as fatigue
testing for materials.
Page
110
TEST CASES
A test case is a detailed procedure that fully tests a feature or an aspect of a
feature. Test case description includes preconditions, generic or specific test
inputs, expected results, and steps to perform to execute the test. There are
many definitions and formats for test case description. In general, the intent of
the test case is to capture what the particular test is designed to accomplish.
Risk analysis, test strategy, and the test plan should guide test case
development.
A test case describes how to perform a particular test. We need to develop a
test case for each test listed in the test plan. Figure illustrates the point at
which test case design occurs in the lab development and testing process.
A test case includes:
 The purpose of the test.
 Special hardware requirements, such as a modem.
 Special software requirements, such as a tool.
Page
111
 Specific setup or configuration requirements.
 A description of how to perform the test.
 The expected results or success criteria for the test.
“A test case has components that describe an input, action or event and an
expected response, to determine if a feature of an application is working
correctly”.
Test cases should be written by a team member who understands the function
or technology being tested, and each test case should be submitted for peer
review.
Organizations take a variety of approaches to documenting test cases;
these range from developing detailed, recipe-like steps to writing general
descriptions. In detailed test cases, the steps describe exactly how to perform
the test. In descriptive test cases, the tester decides at the time of the test how
to perform the test and what data to use.
Most organizations prefer detailed test cases because determining pass
or fail criteria are usually easier with this type of case. In addition, detailed
test cases are reproducible and are easier to automate than descriptive test
cases. This is particularly important if you plan to compare the results of tests
Page
112
over time, such as when you are optimizing configurations. Detailed test cases
are more time-consuming to develop and maintain.
BUG REPORTS
Document that records data obtained from an experiment of evaluation
in an organized manner, describes the environmental or operating
conditions, and shows the comparison of test results with test objectives.
TEST REPORT
Tester Name : Rahul Soni Module: LogIn1.aspx
Test Date : 13/05/2017
Objective : To check the functionality of “Log In” button
Description:
1) Run the LogIn1.aspx page

2) Type valid username
3) Type invalid password
Page
113
Expected Result : Error message
Actual Result : Redirect to Home page
TEST REPORT
Tester Name : Rahul soni Module: ChangePassword.aspx
Test Date : 13/05/2017
Objective : To check the functionality of “Change” button
Description:
1) Run ChangePassword.aspx
2) Type valid username & password
3) Click on “Check” button
4) Type Valid new password & confirm password
5) Click on “Change” button
Page
114
Expected Result : Change Password
Actual Result : Error message
TEST REPORT
Tester Name : Rahul Soni Module: ForgotPassword.aspx
Test Date :13/05/2017
Objective : To check the functionality of “Send” button
Description:
1) Run ForgotPassword.aspx
2) Type valid user name
3) Type valid Email id
Page
115
Expected Result : Send password to email inbox
Actual Result : Error Massage
DEBUGGING
In computers, debugging is the process of locating and fixing or
bypassing bugs (errors) in computer program code or the engineering of a
hardware device. To debug a program or hardware device is to start with a
problem, isolate the source of the problem, and then fix it. A user of a program
that does not know how to fix the problem may learn enough about the
problem to be able to avoid it until it is permanently fixed. When someone
says they've debugged a program or "worked the bugs out" of a program, they
imply that they fixed it so that the bugs no longer exist.
Debugging is a necessary process in almost any new software or hardware
development process, whether a commercial product or an enterprise or
personal application program. For complex products, debugging is done as the
result of the unit test for the smallest unit of a system, again at component test
when parts are brought together, again at system test when the product is
used with other existing products, and again during customer beta test, when
users try the product out in a real world situation. Because most computer
Page
116
programs and many programmed hardware devices contain thousands of
lines of code, almost any new product is likely to contain a few bugs.
IMPLEMENTATION
OF SECURITY
Page
117
DATABASE SECURITY
Database security is the system, processes, and procedures that protect
a database from unintended activity. Unintended activity can be categorized
as authenticated misuse, malicious attacks or inadvertent mistakes made by
authorized individuals or processes. Database security is also a specialty
within the broader discipline of computer security.
Traditionally databases have been protected from external connections
by firewalls or routers on the network perimeter with the database
environment existing on the internal network opposed to being located within
a demilitarized zone. Additional network security devices that detect and alert
on malicious database protocol traffic include network intrusion
detection systems along with host-based intrusion detection systems.
Database security is more critical as networks have become more open.
Databases provide many layers and types of information security, typically
Page
118
specified in the data dictionary, including:
 Access control
 Auditing
 Authentication
 Encryption
 Integrity controls
Triggers :- A trigger is a special kind of stored procedure that is
invoked whenever an attempt is made to modify the data in the table it
protects. Modifications to the table are made using INSERT, UPDATE, OR
DELETE statements. Triggers are used to enforce data integrity and business
rules such as automatically updating summary data. It allows to perform
cancelling, delete or update operations. If constraints exist on the trigger
table, they are checked prior to the trigger execution. If constraints are
violated statement will not be executed and trigger will not run. Triggers are
associated with tables and they are automatic. Triggers are automatically
invoked by SQL SERVER. Triggers prevent incorrect, unauthorized, or
inconsistent changes to data.
Page
119
View :- A view is a virtual table that consists of columns from one or
more tables. Though it is similar to a table, it is stored in the database. It is a
query stored as an object. Hence, a view is an object that derives its data from
one or more tables. These tables are referred to as base or underlying tables.
Once you have defined a view, you can reference it like any other table in a
database.
A view serves as a security mechanism. This ensures that users are able to
retrieve and modify only the data seen by them. Users cannot see or access the
remaining data in the underlying tables. A view also serves as a mechanism to
simplify query execution. Complex queries can be stored in the form as a view,
and data from the view can be extracted using simple queries.
USER :- A user is an agent, either human (end-user) or software,
who uses a computer or network service. A user often has a user account and
is identified by a username (also user name), screen name (also screen name),
nickname (also nick), or handle, which is derived from the identical Citizen's
Band radio term.
Users are also widely characterized as the class of people that use a system
without complete technical expertise required to understand the system fully.
In hacker-related contexts, such users are also divided into users and power
Page
120
users. Both are terms of degradation, but the latter connotes a "know-it-all"
attitude.
In projects in which the actor of the system is another system or a software
agent, it is quite possible that there is no end-user for the system. In this case,
the end-users for the system would be indirect end-users.
Privilege :- It enable users to create, delete, or access database
resources. Authority levels provide a method of grouping privileges and
higher-level database manager maintenance and utility operations. Together,
these act to control access to the database manager and its database objects.
Users can access only those objects for which they have the appropriate
authorization, i.e., the required privilege or authority.
A user or group can have one or more of the following levels of authorization
and privileges:
 Administrative authority (SYSADM or DBADM) gives full privileges for a set of
objects.
 System authority (SYSCTRL or SYSMAINT) gives full privileges for managing
the system but does not allow access to the data.
 LOAD authority (LOAD) gives LOAD utility privileges to load data into tables.
Page
121
 Ownership privilege (also called CONTROL privilege in some cases) gives full
privileges for a specific object.
Individual privileges may be granted to allow a user to carry out specific
functions on specific objects.
Implicit privileges may be granted to a user who has the privilege to execute a
package. Although users can run the application, they do not necessarily
require explicit privileges on the data objects used within the package.
Users with administrative authority (SYSADM or DBADM) or ownership
privileges (CONTROL) can grant and revoke privileges to and from others,
using the GRANT and REVOKE statements. It is also possible to grant a table,
view, or schema privilege to another user if that privilege is held with the
WITH GRANT OPTION. However, the WITH GRANT OPTION does not allow
the person granting the privilege to revoke the privilege, once granted. You
must have SYSADM authority, DBADM authority, or CONTROL privilege to
revoke the privilege.
A user or group can be authorized for any combination of individual privileges
or authorities. When a privilege is associated with a resource, that resource
must already exist. For example, a user cannot be given the SELECT privilege
on a table unless that table has previously been created.
Page
122
DATA SECURITY
Data security :- In simple terms, data security is the practice of
keeping data protected from corruption and unauthorized access. The focus
behind data security is to ensure privacy while protecting personal or
corporate data.
Data is the raw form of information stored as columns and rows in our
databases, network servers and personal computers. This may be a wide
range of information from personal files and intellectual property to market
analytics and details intended to top secret. Data could be anything of interest
that can be read or otherwise interpreted in human form.
However, some of this information isn't intended to leave the system. The
unauthorized access of this data could lead to numerous problems for the
larger corporation or even the personal home user. Having your bank account
details stolen is just as damaging as the system administrator who was just
robbed for the client information in their database.
Page
123
There has been a huge emphasis on data security as of late, largely because of
the internet. There are a number of options for locking down your data from
software solutions to hardware mechanisms. Computer users are certainly
more conscious these days, but is your data really secure? If you're not
following the essential guidelines, your sensitive information just may be at
risk.
Encryption:-
Encryption has become a critical security feature for thriving networks and
active home users alike. This security mechanism uses mathematical schemes
and algorithms to scramble data into unreadable text. It can only by decoded
or decrypted by the party that possesses the associated key.
(FDE) Full-disk encryption offers some of the best protection available. This
technology enables you to encrypt every piece of data on a disk or hard disk
drive. Full disk encryption is even more powerful when hardware solutions
are used in conjunction with software components. This combination is often
referred to as end-based or end-point full disk encryption.
Strong User Authentication:-
Authentication is another part of data security that we encounter with
everyday computer usage. Just think about when you log into your email or
Page
124
blog account. That single sign-on process is a form authentication that allows
you to log into applications, files, folders and even an entire computer system.
Once logged in, you have various given privileges until logging out. Some
systems will cancel a session if your machine has been idle for a certain
amount of time, requiring that you prove authentication once again to re-
enter.
The single sign-on scheme is also implemented into strong user
authentication systems. However, it requires individuals to login using
multiple factors of authentication. This may include a password, a one-time
password, a smart card or even a fingerprint.
Backup Solutions:-
Data security wouldn't be complete without a solution to backup your critical
information. Though it may appear secure while confined away in a machine,
there is always a chance that your data can be compromised. You could
suddenly be hit with a malware infection where a virus destroys all of your
files. Someone could enter your computer and thieve data by sliding through a
security hole in the operating system. Perhaps it was an inside job that caused
your business to lose those sensitive reports. If all else fails, a reliable backup
Page
125
solution will allow you to restore your data instead of starting completely
from scratch.
ASP.NET Validation Controls:-These are powerful server controls that
are used for validating user input. These controls provides both server side
and client side validation.
The client side validation features can be used to give your users an improved
UI experience. By using the client side features, your users will not need to
wait for a full page postback to occur only to discover that they have failed to
fill out your form completely. Instead, the client side features can be using to
notify the user immediately (before the page is submitted) about any missing
and/or invalid data.
One of the shortcomings of the validation controls under the 1.1 Framework
was the inability to validate only portions of your form. Whenever the
validators were triggered, all validators on the page were checked even if they
might not be related to the particular button being clicked. With the 2.0
Framework, a new Validation Group property was introduced. By setting the
Page
126
Validation Group property on a button, only those validation controls that
were also set to that same Validation Group will be checked.
The validation can be checked on the server side with the help of the Is
Valid property of the validation control. Additionally, you can use the Is Valid
property of the Page to check the validation result of all validation controls on
the page. Before testing the Is Valid property of the validation control or the
page, it is important that the validation check has already been performed
through the use of the Validate method. You can call Validate on individual
controls and also on the page itself.
Here is a list of the validation controls
 Required Field Validator
 Regular Expression Validator
 Custom Validator
 Validation Summary
 Range Validator
 Compare Validator
Page
127
USER & ACCESS RIGHTS

User – Admin
Rights- An admin user has all the rights related to this portal. He will be the
super user who can Add/View/Delete any information.
An Admin can Add/Update the user records
An Admin can Add/Update the music records
An Admin can View all the Album purchasing details
An Admin can add/update wallpapers
User- Customer
Rights- A customer can avail services after registration only
A customer can search User records
A customer can search music records
A customer can search Movie records
A customer can download wallpapers
A customer can buy CD/DVD online
A customer can change password settings
Page
128
LIMITATIONS OF THE PROJECT
1. This project is limited to Music & Video related updates only.
2. This project does not have real Web Services called to check the validity
of the credit card. The Web Service to verify card details is also
implemented by myself.
This project does not have any type of SMS facility for the users
Page
129
FUTURE SCOPE OF THE PROJECT
There can be several future applications of this project. Some of them
are discussed below:
 This project can be made a three tier application. This will generally
help us in updating ourselves to latest technologies.
 This project is limited to Music & Video related activities only. In future I
can include information related to other sports such as Remix music,
Albums etc. So you can get information regarding any Music & video on
this portal.
 In future a SMS facility can be included for the users.
Page
130
BIBLIOGRAPHY
1. Pro. ASP.NET 4 in C# (WROX): Bill Evjen, Scott Hanselman, Devin Rader
2. Asp.Net AJAX- JOYDID : Sriram Putrevu
3. Pro ASP.NET 4 in C# 2010(Apress): Matthew MacDonald, Adam
Freeman
4. Fundamental Of C# & ASP.NET: Rajesh Pillai & Shiv Prasad Koirala
5. Software Engineering a Practitioner’s Approach: Roger S. Pressman
6. Software Engineering Principal & Practice : Hans van Vilet
7. Software Engineering By New International Publishers: K.K Aggarwal &
Yogesh Singh
8. Microsoft SQL Server 2008 R2 Unleashed (Sams): Ray Rankins, Paul T.
Bertucci, Chris Gallelli, Alex T. Silverstein.
9. http://www.w3schools.com/aspnet/default.asp
10. http://www.sql-server-helper.com/
Page
131
INPUT & OUTPUT

SCREENS
Page
132
INDEXPAGE.ASPX
Page
133
LOGINPAGE.ASPX
Page
134
HOMEPAGE.ASPX
Page
135
Page
136
REGISTER.ASPX
Page
137
CONTACTUS.ASPX
Page
138
CHANGEPASSWORD.ASPX
Page
139
FORGOTPASSWORD.ASPX
Page
140
PRODUCT DESCRIPTION.ASPX
BOLLYWOOD MOVIES.ASPX
Page
141
Page
142
HOLLYWOOD MOVIES.ASPX
Page
143
Page
144
PUNJABI MOVIES.ASPX
Page
145
Page
146
TOLLYWOOD MOVIES.ASPX
Page
147
ALBUMS.ASPX
Page
148
REMIX SONGS.ASPX
Page
149
SEARCH.ASPX
Page
150
VIEWCART.ASPX
Page
151
Page
152
PAYMENT.ASPX
ADMIN ADD PRODUCT.ASPX
Page
153
Page
154
CODING WITH
COMMENTS&
EXCEPTION
HANDLING
LOGIN.ASPX.CS
using System;
using System.Collections.Generic;
using System.Linq;
Page
155
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Data;
using System.Data.SqlClient;
using System.Configuration;
public partial class Login1 : System.Web.UI.Page
protected void Page_Load(object sender, EventArgs e)
protected void ImageButton2_Click(object sender, ImageClickEventArgs e)
SqlConnection con = new

SqlConnection(ConfigurationManager.ConnectionStrings["dbcon"].Connection
String);//Create a connection to DB
con.Open();//open conection
string qry = "select * from Registration where Username=@t1 and

Password=@t2";//SQL Query to pass into the DB
SqlCommand cmd = new SqlCommand(qry, con); //Sending SQL Query to

DB over the Connection
Page
156
cmd.Parameters.AddWithValue("@t1", TextBox1.Text);//Passing
Username with Query
cmd.Parameters.AddWithValue("@t2", TextBox2.Text);// Passing

Password with Query
SqlDataReader dr = cmd.ExecuteReader();//Query Execute in DB &

reading result
if (dr.HasRows)//IF Username and Password matched
dr.Read();
// Session["Login"] = dr["Username"].ToString();//Creating Session for

User
Session["uid"] = dr[0].ToString();
Session["Username"] = dr["Username"].ToString();//Creating Session

to store UserID
Session["user"] = TextBox1.Text;//Create a Session to a pass a User
Response.Redirect("Home.aspx");//Redirect to Homepage after

Successful login
else//Error Message when Invalid UserName & Password
Label1.Visible = true;
Label1.Text = "Invalid Username/Password";
Page
157
dr.Close();
con.Close();
//Code Finish
Response.Redirect("Registration.aspx");
HOME.ASPX.CS
using System;
using System.Linq;
Page
158
using System.Web;
using System.Data;
public partial class Home : System.Web.UI.Page
{ protected void Page_Load(object sender, EventArgs e)
{ Label2.Text = Session["Username"].ToString();
}
{
Response.Redirect("ViewCart.aspx");
}
{ Session.RemoveAll();//After Logout at Index page
Session.Clear();
Response.Redirect("Index.aspx");
}
}
REGISTER.ASPX.CS
using System;
using System.Linq;
Page
159
using System.Web;
using System.Data;
public partial class Registration : System.Web.UI.Page

String);//Create connection to DB
con.Open();//open connection
string qry = "select max(UserId) from Registration";//SQL Query to

Pass into DB
SqlCommand cmd = new SqlCommand(qry, con);//Sending SQL Query

to DB over the connection
SqlDataReader dr = cmd.ExecuteReader();
dr.Read();
int UserId = Convert.ToInt32(dr[0]);//Convert a string value into int
UserId++;//increase a value
txtuser.ReadOnly = true;
Page
160
txtuser.Text = UserId.ToString();//Passing a value
dr.Close();
con.Close();
protected void ImageButton1_Click(object sender, ImageClickEventArgs

e)

string qry = "insert into Registration

values(@t1,@t2,@t3,@t4,@t5,@t6)";//Create a variable
SqlCommand cmd = new SqlCommand(qry, con);
cmd.Parameters.AddWithValue("@t1", txtuser.Text);//add value
cmd.Parameters.AddWithValue("@t2", txtname.Text);
cmd.Parameters.AddWithValue("@t3", txtpass.Text);
cmd.Parameters.AddWithValue("@t4", txtadr.Text);
cmd.Parameters.AddWithValue("@t5", txtmob.Text);
cmd.Parameters.AddWithValue("@t6", txtid.Text);
int i = cmd.ExecuteNonQuery();//Execute the Query
if (i == 1)
Page
161
Label2.Text = "Record Saved Successfully";
CONTACT US.ASPX.CS
using System;
using System.Linq;
Page
162
using System.Web;
using System.Net.Mail;//namespace for send a mail
public partial class ContactUs : System.Web.UI.Page
protected void Button2_Click(object sender, EventArgs e)
TextBox1.Text = "";//Reset TextBox
MailMessage msg = new MailMessage();//Code to Send a Mail
msg.From = new MailAddress(TextBox1.Text);
msg.Subject = TextBox2.Text;
msg.Body = TextBox3.Text;
Page
163
msg.IsBodyHtml = true;
SmtpClient sm = new SmtpClient();
sm.Host = "SmtpClient.gmail.com";
sm.Port = 587;
sm.Credentials = new
System.Net.NetworkCredential("Rsoni7641@gmail.com", "1234567891");
Label lb1 = new Label();
lb1.ID = "lb1msg";
lb1.Text = "Your mail are sent";
lb1.Height = 20;
lb1.Width = 200;
lb1.BackColor = System.Drawing.Color.Green;
Label3.Text = "Thank you for your feedback";
CHANGEPASSWORD.ASPX.CS
using System;
using System.Linq;
using System.Web;
Page
164
using System.Data;
public partial class ChangePassword : System.Web.UI.Page
Label2.Text = Session["Username"].ToString();
protected void btnchange_Click(object sender, EventArgs e)

string qry = "select * from Registration where Username=@t1 and

Password=@t2";//SQL Query to pass into the DB

Page
165
cmd.Parameters.AddWithValue("@t1",
Session["user"].ToString());//Passing Username with Query
cmd.Parameters.AddWithValue("@t2", TextBox1.Text);// Passing

Password with Query

reading result
if (dr.Read())//IF Username and Password matched
Panel3.Visible = true;
else//Error Message when Invalid UserName & Password
Label3.Text = "Invalid Password";
dr.Close();
con.Close();
//Code Finish
protected void btnsave_Click(object sender, EventArgs e)
Page
166

string qry = "update Registration set Password=@t1 where

Username=@t2";//SQL Query to pass into the DB

Username with Query
cmd.Parameters.AddWithValue("@t2", Session["user"].ToString());//
Passing Password with Query
int i=cmd.ExecuteNonQuery();
Label3.Text = "Password Saved Successfully";
Session.RemoveAll();//After Logout at Index page
Session.Clear();
Page
167
FORGOT PASSWORD.ASPX.CS
using System;
using System.Linq;
using System.Web;
Page
168
using System.Data;
using System.Net.Mail;
public partial class ForgetPassword : System.Web.UI.Page
protected void btnsave_Click(object sender, EventArgs e)

string qry = "select * from Registration where EmailID=@t1";//SQL Query

to pass into the DB

Page
169
cmd.Parameters.AddWithValue("@t1", TextBox2.Text);//Take a EmailID

in TextBox

reading result
if (dr.HasRows)//IF Username and Password matched
//Code to send Mail
MailMessage msg = new MailMessage();
msg.To.Add(new MailAddress(TextBox2.Text));
msg.From = new MailAddress("Rsoni7641@gmail.com");
msg.Subject = "Passowrd Recovery";
dr.Read();
msg.Body = "Ur Password is: " + dr["Password"].ToString();
msg.IsBodyHtml = true;
SmtpClient sm = new SmtpClient();
sm.Host = "smtp.gmail.com";
sm.Port = 587;
sm.Credentials = new
System.Net.NetworkCredential("Rsoni7641@gmail.com", "1234567891");
sm.EnableSsl = false;
//sm.Send(msg);
Page
170
Label3.Text = "Password has been sent to your EmailID";
else//Error Message when Invalid EmailID
Label3.Text = "Invalid EmailID";
PRODUCT DESCRIPTION.ASPX.CS
using System;
using System.Linq;
using System.Web;
Page
171
using System.Data;
public partial class ProductDescription : System.Web.UI.Page

string qry = "select * from Product where ProdId=@t1";//SQL Query to

pass into the DB

Session["prid"].ToString());//Passing Username with Query

reading result
if (dr.HasRows)
dr.Read();
Label3.Text = dr[0].ToString();
Page
172
Image18.ImageUrl = dr[4].ToString();
TextBox1.Text = dr[5].ToString();
BOLLYWOOD MOVIES.ASPX.CS
using System;
using System.Linq;
using System.Web;
Page
173
public partial class Bollywoodt : System.Web.UI.Page
protected void Timer1_Tick(object sender, EventArgs e)
protected void Button1_Click1(object sender, EventArgs e)
ShopCart sc = new ShopCart();
sc.addtocart(1004,"HalfGirlfriend", Convert.ToInt32(Session["uid"]),999,
Convert.ToInt32(TextBox1.Text),System.DateTime.Now.ToShortDateString())
;
sc.addtocart(1003, "Bahubali2", Convert.ToInt32(Session["uid"]), 999,

Convert.ToInt32(TextBox2.Text),System.DateTime.Now.ToShortDateString())
;
Page
174
Session["prid"] = 1004;
Response.Redirect("ProductDescription.aspx");
protected void btnviewcart_Click(object sender, EventArgs e)
int q = Convert.ToInt32(TextBox1.Text);
Session["amt"] = 999*q;
Response.Redirect("Payment.aspx");
Page
175
Session["amt"] = 999 * q;
sc.addtocart(1005, "AE DIL HAI MUSHKIL",

Convert.ToInt32(Session["uid"]), 999, Convert.ToInt32(TextBox3.Text),
System.DateTime.Now.ToShortDateString());
Page
176
sc.addtocart(1006, "OK JAANU", Convert.ToInt32(Session["uid"]), 999,

Convert.ToInt32(TextBox4.Text),
Page
177
Session.Clear();
Response.Redirect("/Hollywood/Sukhe Muzical Doctorz

(DjPunjab.Com).mp3");
HOLLYWOOD MOVIES.ASPX.CS
using System;
using System.Linq;
using System.Web;
Page
178
public partial class Hollywood : System.Web.UI.Page
Page
179
sc.addtocart(1007, "UNDERWORLD AWAKINING",

sc.addtocart(1010, "Fate & Furious 8", Convert.ToInt32(Session["uid"]),

999, Convert.ToInt32(TextBox2.Text),
sc.addtocart(1008, "THE BOURNE LEGACY",

Page
180
sc.addtocart(1009, "THEHULK", Convert.ToInt32(Session["uid"]), 999,

Page
181
sc.addtocart(1011, "BATMAN VS. SUPERMAN",

Page
182
sc.addtocart(1012, "THE CONJURING 2", Convert.ToInt32(Session["uid"]),

sc.addtocart(1013, "SNITCH", Convert.ToInt32(Session["uid"]), 999,

sc.addtocart(1014, "HOBBIT", Convert.ToInt32(Session["uid"]), 999,

Page
183
Page
184
protected void ImageButton7_Click1(object sender, ImageClickEventArgs e)
Session.Clear();
Page
185
PUNJABI MOVIES.ASPX.CS
using System;
using System.Linq;
using System.Web;
public partial class Punjabi : System.Web.UI.Page
Page
186
Page
187
sc.addtocart(1015, "CARRY ON JATTA 2",

sc.addtocart(1016, "CHANNO", Convert.ToInt32(Session["uid"]), 999,

Page
188
sc.addtocart(1017, "AMBARSARIYA", Convert.ToInt32(Session["uid"]),

sc.addtocart(1018, "UDTA PUNJAB", Convert.ToInt32(Session["uid"]),

Page
189
Session.Clear();
Page
190
TOLLYWOOD MOVIES.ASPX.CS
using System;
using System.Linq;
using System.Web;
public partial class Tollywood : System.Web.UI.Page
Page
191
Page
192
sc.addtocart(1019, "BAHUBALI 2", Convert.ToInt32(Session["uid"]), 999,

sc.addtocart(1020, "THERI", Convert.ToInt32(Session["uid"]), 999,

Page
193
sc.addtocart(1021, "DABANGAI", Convert.ToInt32(Session["uid"]), 999,

sc.addtocart(1022, "LOVESHUDDA", Convert.ToInt32(Session["uid"]),

Page
194
Session.Clear();
Page
195
ALBUMS.ASPX.CS
using System;
using System.Linq;
using System.Web;
public partial class Albums : System.Web.UI.Page
Page
196
protected void ImageButton1_Click1(object sender, ImageClickEventArgs e)
Page
197
Page
198
sc.addtocart(1024, "BAHUBALI 2", Convert.ToInt32(Session["uid"]), 99,

Page
199
sc.addtocart(1025, "BEGUM JAAN", Convert.ToInt32(Session["uid"]), 99,

sc.addtocart(1026, "FAST @ FURIOUS 8",

sc.addtocart(10027, "MERA HIGHWAY", Convert.ToInt32(Session["uid"]),

sc.addtocart(1028, "MANJE BISTRE", Convert.ToInt32(Session["uid"]), 99,

Page
200
sc.addtocart(1029, "MORE LIFE", Convert.ToInt32(Session["uid"]), 99,

sc.addtocart(1030, "NOOR", Convert.ToInt32(Session["uid"]), 99,

sc.addtocart(1031, "PATAKE", Convert.ToInt32(Session["uid"]), 99,

Page
201
sc.addtocart(1032, "NAAM SHABANA", Convert.ToInt32(Session["uid"]),

sc.addtocart(1033, "IN THE SPOTLIGHT",

Page
202
Page
203
Page
204
Response.Redirect("ChangePassword.aspx");
Session.Clear();
Page
205
REMIX.ASPX.CS
using System;
using System.Linq;
using System.Web;
public partial class Remix : System.Web.UI.Page
Page
206
Session.Clear();
SEARCH.ASPX.CS
using System;
using System.Linq;
using System.Web;
using System.Data;
public partial class Search : System.Web.UI.Page
Page
207

string qry = "select * from MovieDetails where Moviename=@t1";//SQL

Query to pass into the DB

Username with Query

reading result
if (dr.HasRows)
GridView1.DataSource = dr;
GridView1.DataBind();
Page
208
else
Label3.Text = "NAME NOT FOUND";
VIEWCART.ASPX.CS
using System;
using System.Linq;
using System.Web;
using System.Data;
public partial class ViewCart : System.Web.UI.Page
Page
209
Label3.Visible = false;

string qry = "select * from Tempcart where UserId=@t1 and

PurDate=@t2";//SQL Query to pass into the DB

Session["uid"].ToString());//Passing Username with Query

reading result
if (dr.HasRows)
GridView1.DataSource = dr;
GridView1.DataBind();
else
Page
210
GridView1.Visible = false;
Label3.Text = "Your Cart is Empty";
dr.Close();
String qry1 = "Select sum(Price*Qty) from Tempcart where UserId=@t3

and PurDate=@t4"; //SQL Query to pass into the DB
SqlCommand cmd1 = new SqlCommand(qry1, con); //Sending SQL Query

to DB over the Connection
cmd1.Parameters.AddWithValue("@t3",
Session["uid"].ToString());//Passing Username with Query
cmd1.Parameters.AddWithValue("@t4",
SqlDataReader dr1 = cmd1.ExecuteReader();//Query Execute in DB &

reading result
dr1.Read();
Label4.Text = dr1[0].ToString();
protected void btnpayment_Click(object sender, EventArgs e)
Session["amt"] = Label4.Text;
Page
211
protected void GridView1_RowDeleting(object sender,

GridViewDeleteEventArgs e)
protected void GridView1_RowEditing(object sender,

GridViewEditEventArgs e)
protected void GridView1_RowCancelingEdit(object sender,

GridViewCancelEditEventArgs e)
protected void GridView1_RowUpdating(object sender,

GridViewUpdateEventArgs e)
Session["amt"] = Label4.Text;
Page
212
PAYMENT.ASPX.CS
using System;
using System.Linq;
using System.Web;
using System.Data;
public partial class Payment : System.Web.UI.Page
Page
213
Label4.Text = System.DateTime.Now.ToShortDateString();
TextBox5.Text = Session["amt"].ToString();

string qry = "select max(Receiptno) from Payment";//SQL Query to Pass

into DB
SqlCommand cmd = new SqlCommand(qry, con);//Sending SQL Query to

DB over the connection
dr.Read();
int tid = Convert.ToInt32(dr[0]);//Convert a string value into int
tid++;//increase a value
Label6.Text = tid.ToString();//Passing a value
Label7.Text = "Your Receipt Id Is: ";
dr.Close();
con.Close();
Page
214
string bnm = DropDownList3.Text;
string ct = DropDownList2.Text;
int cno = Convert.ToInt32(TextBox2.Text);
string vu = DropDownList4.Text + "/" + DropDownList5.Text;
int cvv = Convert.ToInt32(TextBox3.Text);
string cnm = TextBox4.Text;
int amt = Convert.ToInt32(TextBox5.Text);
string pdate = Label4.Text;
BankService bs = new BankService();
bool res = bs.checkcard(cno, ct, vu, cvv, cnm, amt);
if (res == false)
Label5.Text = "Invalid Card Details";
else
Page
215

string qry = "insert into Payment

values(@t1,@t2,@t3,@t4,@t5,@t6,@t7)";//SQL Query to pass into the DB
SqlCommand cmd = new SqlCommand(qry, con); //Sending SQL Query

to DB over the Connection
cmd.Parameters.AddWithValue("@t1", Label6.Text);//Passing
Username with Query
cmd.Parameters.AddWithValue("@t2", pdate);// Passing Password

with Query
cmd.Parameters.AddWithValue("@t3", amt);
cmd.Parameters.AddWithValue("@t4", cno);
cmd.Parameters.AddWithValue("@t5", bnm);
cmd.Parameters.AddWithValue("@t6", ct);
cmd.Parameters.AddWithValue("@t7", Session["uid"].ToString());
int i = cmd.ExecuteNonQuery();
Label5.Text = "Payment Succeessful";
Page
216
ADMIN ADD PRODUCT.ASPX.CS
using System;
using System.Linq;
using System.Web;
using System.Data;
public partial class AddProduct : System.Web.UI.Page
Page
217

string qry = "select max(ProdId) from Product";//SQL Query to Pass into

DB
SqlCommand cmd = new SqlCommand(qry, con);//Sending SQL Query to

DB over the connection
dr.Read();
int ProdId = Convert.ToInt32(dr[0]);//Convert a string value into int
ProdId++;//increase a value
TextBox1.ReadOnly = true;
TextBox1.Text = ProdId.ToString();//Passing a value
dr.Close();
con.Close();
protected void btnadd_Click(object sender, EventArgs e)

Page
218
string qry = "insert into Product

cmd.Parameters.AddWithValue("@t1", TextBox1.Text);//add value
cmd.Parameters.AddWithValue("@t2", TextBox2.Text);
string path="";
if(FileUpload1.HasFile)
FileUpload1.SaveAs(Server.MapPath("~/Uploaded/" +
FileUpload1.FileName));
path = "~/Uploaded/" + FileUpload1.FileName;
cmd.Parameters.AddWithValue("@t5", path);
cmd.ExecuteNonQuery();//Execute the Query
Label3.Text = "Record Saved Successfully";
Page
219
protected void btnclear_Click(object sender, EventArgs e)
TextBox2.Text = "";
TextBox3.Text = "";
TextBox4.Text = "";
TextBox5.Text = "";
WEB.CONFIG
<?xml version="1.0" encoding="utf-8"?>

<configuration>
<connectionStrings>
<add name="dbcon" connectionString="Data Source=(LocalDB)\
v11.0;AttachDbFilename=C:\Users\Dell-Pc\Documents\Visual Studio 2012\
WebSitesMusic@Video\App_Data\Music@Video.mdf;Integrated Security=True"
providerName="System.Data.SqlClient" />
<add name="Music_VideoConnectionString" connectionString="Data
Source=(LocalDB)\v11.0;AttachDbFilename=|DataDirectory|\
Music@Video.mdf;Integrated Security=True"
providerName="System.Data.SqlClient" />
</connectionStrings>
Page
220
<system.web>
<compilation debug="true" targetFramework="4.5">
<assemblies>
<add assembly="System.Data.Linq, Version=4.0.0.0, Culture=neutral,
PublicKeyToken=B77A5C561934E089" />
</assemblies>
</compilation>
<httpRuntime targetFramework="4.5" />
<pages>
<controls>
<add tagPrefix="ajaxToolkit" assembly="AjaxControlToolkit"
namespace="AjaxControlToolkit" />
</controls>
</pages>
</system.web>
</configuration>
BANKSERVICE.CS
using System;
using System.Linq;
using System.Web;
using System.Web.Services;
using System.Data;
/// <summary>
/// Summary description for BankService
/// </summary>
[WebService(Namespace = "http://tempuri.org/")]
[WebServiceBinding(ConformsTo = WsiProfiles.BasicProfile1_1)]
// To allow this Web Service to be called from script, using ASP.NET AJAX,
uncomment the following line.
// [System.Web.Script.Services.ScriptService]
public class BankService : System.Web.Services.WebService {
public BankService () {
Page
221
//Uncomment the following line if using designed components

//InitializeComponent();
}
[WebMethod]
public bool checkcard(int cno, string ct, string vu, int cvv, string cnm,
int climit)
{
SqlConnection(ConfigurationManager.ConnectionStrings["dbcon"].ConnectionStrin
g);//Create connection to DB
string qry = "select * from Cardpayment where cardno=@t1 and
cardtype=@t2 and validupto=@t3 and CVV=@t4 and cardholder=@t5 and
cardlimit>=@t6";//Create a variable
cmd.Parameters.AddWithValue("@t1",cno);
cmd.Parameters.AddWithValue("@t2",ct);
cmd.Parameters.AddWithValue("@t3",vu);
cmd.Parameters.AddWithValue("@t4",cvv);
cmd.Parameters.AddWithValue("@t5",cnm);
cmd.Parameters.AddWithValue("@t6",climit);
if (dr.HasRows)
{
return true;
}
else
{
return false;
}
dr.Close();
con.Close();
}
Page
222
SHOPCART.CS
using System;
using System.Linq;
using System.Web;
using System.Data;
/// <summary>
/// Summary description for ShopCart
/// </summary>
public class ShopCart
{
public void addtocart(int pid, string pname, int uid, int pr, int qt,
string pdate)
{
SqlConnection(ConfigurationManager.ConnectionStrings["dbcon"].ConnectionStrin
g);//Create connection to DB
Page
223
string qry = "insert into Tempcart
cmd.Parameters.AddWithValue("@t1", pid);//add value
cmd.Parameters.AddWithValue("@t2", pname);
cmd.Parameters.AddWithValue("@t3", uid);
cmd.Parameters.AddWithValue("@t4", pr);
cmd.Parameters.AddWithValue("@t5", qt);
cmd.Parameters.AddWithValue("@t6", pdate);
int i = cmd.ExecuteNonQuery();//Execute the Query
}
}
XMLFILE.XML
<?xml version="1.0" encoding="utf-8" ?>
<Advertisements>
<Ad>
<ImageUrl>~/Images/Ae-dil-hai-mushkil.jpg</ImageUrl>
<AlternateUrl>Bollywood movies</AlternateUrl>
<NavigateUrl></NavigateUrl>
<Impressions>50</Impressions>
<Keyword>ad1</Keyword>
</Ad>
<Ad>
<ImageUrl>~/Images/Airlift.jpg</ImageUrl>
</Ad>
<Ad>
<ImageUrl>~/Images/jolly llb 2.jpg</ImageUrl>
Page
224
</Ad>
<Ad>
<ImageUrl>~/Images/ok-jaanu.jpg</ImageUrl>
</Ad>
</Advertisements>
STYLESHEET.CSS
body
{
}
.img:hover
{
cursor: pointer;
height: auto;
width: auto;
transform: scale(1.1);
-webkit-transform: scale(1.1);
box-shadow: 3px 3px 1px #fff;
}
.rot:hover
{
transition: width 2s, height 2s, transform 2s;
transform: rotate(360deg);
}
.Panes
{
background-image: url(Skull.png);
Page
225
}
.shadow {
width: 350px;
height: 400px;
background-color: #F0F0F0;
-webkit-box-shadow: 0px 0px 10px rgba(0,0,0,1);
color:#0000FF;
opacity: 0.5;
}
#footer
{
position: fixed;
bottom:0px;
height: 180px;
width: 100%;
}
#foot
{
position:fixed;
bottom: 0px;
height: 120px;
width: 40%;
}
.header
{
height: 50px;
background: #000;
border: 1px solid #fff;
position:fixed;
width: 100%;
margin: 0px auto;
}
#had
{
position:fixed;
height: 100px;
width: 100%;
margin: 0px;
}
ul
{
margin: 0;
padding: 0;
Page
226
position: absolute;
top: 50%;
left: 50%;
transform: translate(-50%,-50%);
}
ul li
{
list-style: none;
float: left;
margin: 10px;
width: 100px;
height: 100px;
line-height: 100px;
text-align: center;
background: #fff;
border: solid;
border-radius: 50%;
position: relative;
overflow: hidden;
color: #262626;
font-size: 50px;
z-index: 1;
transition: .5s ease-in-out;
}
ul li:before
{
content: '';
width: 100px;
height: 100px;
position:absolute;
top: 0;
left: -100%;
background: #ccc;
z-index: -1;
border-radius: 50%;
transform: scale(0);
}
ul li:after
{
content: '';
width: 50%;
Page
227
height: 100%;
position: absolute;
right: -100%;
top: 0;
background: rgba(255,255,255,.3);
}
ul li:hover:before
{
left: 0;
transform: scale(.9);
}
ul li:hover:after
{
right: 0%;
}
ul li:nth-child(1):before
{
background:#3b5999;
}
{
background:#55acee;
}
{
background:#0077B5;
}
{
background:#e4405f;
}
ul li .fa
{
}
ul li:hover .fa
{
color: #fff;
}
Page
228

Rahul Project Music@Video

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Rahul Project Music@Video

Uploaded by

Copyright:

Available Formats

MusicManza-Online Music and Video Portal

S. No. NAME OF TOPICS PAGE NO.

4. Introduction of the Project 37

5. Objectives of the Project 38

(a) Feasibility Study 41

(b) Fact Finding 43

(c) Software Requirements Specification (SRS) 46

(i) Functional Requirement 54

(ii) Non-Functional Requirements 56

(d) Life Cycle Model (Waterfall model) 58

(e) COCOMO Model 62

(f) Scheduling Techniques 66

(i) GANT CHART 68

(ii) PERT CHART 71

(g) Risk Analysis and Management 73

(a) Modular Design 79

(b) Modular Description 80

(c) Entity Relationship Diagram 81

(e) Use case Diagram 83

(f) Data Flow Diagram (DFD) 84

(i) Zero level DFD 84

(ii) One level DFD 85

(iii) Two level DFD 86

(g) Data Dictionary 89

(a) Test Plan 95

(b) Testing type 98

(c) Test Cases 110

(d) Test/Bug Report 112

(e) Debugging 115

10. Implementation of Security 116

(a) Database Security 117

(b) Data Security 122

(c) Users & access rights 127

11. Limitations of the Project 128

12. Future Scope of the Project 129

13. Bibliography 130

14. Input and Output Screens 131

15. Coding with Comments and Error Handling 150

Signature of the Student Signature of the

Name and Address Name,

It gives me immense pleasure to put forward this practical venture. But

encouragement. So I would like to thank all those people without whose

support this project would not have been a success.

I take great pride and privilege to express my gratitude to my guide, Mr.

bountiful help which inspired me to complete my desired dissertate

work. My indebtedness is reserved for her good will and patience

during the project.

to me by all of my teachers and Lab instructors of my study centre KSM.

I am grateful to my entire Faculty and Programmers and all my friends

for helping me prepare my project.

S. No. NAME OF TOPICS PAGE NO.

1. Introduction of the Project. 7

7.1 Technical Feasibility 14

7.2 Economical Feasibility 15

7.3 Operational Feasibility 15

10. Modular Description 17

12. Entity Relationship Diagram 22

13. Data Flow Diagram 23

13.1 Zero level DFD 23

13.2 One level DFD 24

13.3 Two level DFD 25

14. Class Diagram 27

15. Use Case Diagram 28