video libray system neha 536850

8/14/2019 Video Libray System Neha 536850

1/100

ON

Submitted by:

Reg. No-536850In fulfillment

Of DOEACC A Level

At

JAGAN INSTITUTE OF MANAGEMENT STUDIESPlot No.2, P.P.Tower, SEC-3, Rohini

DELHI-110085

Neha KalraReg. no:-536850

1/100


2/100

Project Report

On

A Level

Year 2008 Submitted By:-

Neha Kalra

Reg No:-536850

JAGAN INSTITUTE OF MANAGEMENT STUDIES

Plot No.2, P.P.Tower, SEC-3, RohiniDELHI-110085


2/100


3/100

Executive directorDOEACC6 C.G.O ComplexLodhi Road Delhi-110003

May , 2008

Sir,

I am submitting my A level project for Information System for

Video Library ". Details of my Registration No., Postal Addressetc. are as under-:

Project Title-Information System for Video Library

Level- A

Registration Number- 536850

Name-Neha Kalra

Address- E-94 First Floor phase -I Ashok Vihar Delhi-110052

Your sincerely,Neha KalraReg No-536850


3/100


4/100

Certificate

This is to certify that Project title InformationSystem for Video Library is original work done solely

by

Neha Kalra

Reg No-536850

Under The Guidance of

Mr.Mohit Mathur

JAGAN INSTITUTE OF MANAGEMENT STUDIES

Plot No.2, P.P.Tower, SEC-3, Rohini

DELHI-110085


4/100


5/100

ACKNOWLEDGEMEN

TNothing concrete can be achieved without an optimal combination

of inspiration and perspiration. No work can be accomplished withouttaking the guidance of the experts. It is only the critiques fromingenious intellectuals that help transform a product into a qualityproduct.

For this, I would like to thank Mr. Mohit Mathur, lecturer ofJAGANINSTITUTE OF MANAGEMENT STUDIES, Delhi and all of

the JIMS faculty members for having given me an opportunity to workunder their guidance. I am grateful for their continuous support and

precious time.

It has been good to work on this project and a great experiencein itself.

Place: Delhi NEHA KALRA Reg. No.-

536850


5/100


6/100

INDEX

Abstract

Introduction

System Analysis

Introduction

Objective

Defining A System

System Life Cycle

System Design

DFD

Concept

General Data Flow Rules

Control Flow Data Modeling


6/100


7/100

Physical & Logical Dfd

Data Flow Hierarchy

ER Diagram

Coding

Output

Testing

Testing Objective

Testing Rules

Testing And Quality Assurance

Types Of Testing

Implementation

Maintenance

Hardware And System Requirement

Limitations


7/100


8/100

Bibliography

References

Suggestions


8/100


9/100

ABSTRACT

My project called Information System for Video Library ishighly professionalized and can keep records of transactions. By using thetechniques of C++ the project was given an excellent outlook for easyunderstanding and working. This software is capable of holding number ofaccounts. This program deals with: -

1. List of movies that can be given on rent and left in the library.2. Store Customers information.3. Modification in the existing details.4. Calculation of remaining amount after deduction of rent.

Platform

This application has been developed on Windows XP using

Turbo c++.


9/100


10/100


10/100


11/100

INTRODUCTION

Information System for Video Library software is the

most widely used application. It stores the important data like list ofmovies on rent and left that includes the entire list that could be issued toa customer as per his choice. This software is basically made for store thecustomers information. In this software, new list of movies can be addedto movie list.

It has become an important way of keeping the records issued movies.Moreover, it has reduced manual work & calculation. It is also not anexpensive mode; whenever we want details of any customer or movie wecan easily access that particular record.

It is most convenient to obtain the information of the customers, andallows organizations to provide details more efficiently. The interaction isasynchronous, so the organization can prioritize and categorize according toits business process.


11/100

Data of customer

accessed through thefile from computer

memory

Data displayed on outputscreen, as required.

Data ofcustomer

stored in the file

Data entered by addmodule to the datafile.


12/100

Basic elements of InformationSystem for video library

Basic elements of this software is the details of the video library regardingissued movies, movie list, add movie, customers detail which are to bestored in Information system for video library. This data can be accessedwhenever it is required.

In this software data is written in add module and are stored in a datafile. These data can be seen by display module also we can see the record byentering choice. This software is also able to delete the records stored to thefile. This all could be done by modify, display, sort module.


12/100

Input to the

fileAdd module

Movie List

Video Library

Output to the

file

Cust. InfoIssue Add Item


13/100

Information system forvideo library

Different modules are made here to do different tasks by switchingfrom one module to another and make it possible to draw someconclusions as to what should be done. These can be reconstructed byreading the header file from top to bottom.

List of Common modules used:

Add module: This is the main module by which we can feed therecord of the movies; the record includes name of the movie, price of

the movie and rent amount. By this module we can add Video librarydata.

Issue module:This module is used when any customer want to issue amovie. In this user enter the name of the movie then after checking inthe file amount to be deposited as caution money and rent amount isdisplayed on the screen and again ask for continue and then usersinformation is taken as input and video is issued to the customer.

Return module: Using this module a customer return the moviewhich is taken on rent .In this module the name of the movie he want toreturn and his name, address is taken as input and after searching in thefile it shows the remaining amount after deduction of rent from thecaution money.

Display module:Suppose we have entered a number of records and itis difficult to locate the particular record by displaying the recordsstored in the data file. This module solves this problem. When we callthis module from main module it gives us two options first is for viewthe customer information and second is for view the movie list.


13/100


14/100

Delete module:This module is used to delete the movie from the listof movies. In this module after entering the movie name it shows theno. of copies of movie in the library and after confirmation delete it.


14/100


15/100

System Analysis

A system is a set or arrangement of functionally dependent componentsinteractively working together to attain a predefined goal by processinginformation.

Analysis is the process of diagnosing situations, done with a defiant aim,with the boundaries of the system kept in mind to produce a report basedon the findings. Analysis is a Fact Finding Technique where studies likeUsers need, System Requirement Specification, Feasibility Analysis andCost Benefit Analysis are carried out.

This is the most important step in a software project where we get ageneral idea about the needs of the customers or end users by having manto man conversation with them and about the various conditions andrestrictions that have to be taken care of while developing the softwareapplication.

System Analysis

System analysis was conducted with the following objectives in mind:

1. Identification of need

2. Information Gathering

3. Evaluate the system concept of feasibility


15/100


16/100

1. Identification of Need

The success of the system depends largely on how accurately a problemis defined, thoroughly investigated, and properly carried out through thechoice of solution. Uses need identification and analysis re concernedwith what the user needs rather then what he/she wants. Until the

problem has been identified, defined and evaluated the analyst shouldntthink about solutions and whether the problem is worth solving or not.This step is intended to help the user and the analyst understand the real

problem rather than its symptoms.

2. Information Gathering

A key part of system development is gathering information. The analystmust know what information to get, where to find it, how to collect it,and how to make use of it. The proper use of tools for gathering

information is the key to accessible analysis.

3. Feasibility Study

Feasibility study is carried out to test if the proposed system is feasiblein terms of economy, technology, resource availability etc. As such,given unlimited resources and infinite time, all projects are feasible.

Unfortunately, such results and time are not possible in real lifesituations. Hence it is both necessary and prudent the evaluate thefeasibility of the project at the earliest possible time in order to avoidunnecessary wastage of time, effort, and professional embarrassment ofover an ill conceived system. Feasibility study is a test of the system


16/100


17/100

proposed regarding its workability, impact on the organization ability tomeet the users need and effective use of resources.


17/100


18/100


18/100


19/100

System Design

System design is a solution, a HOW TO APPROACH to thecreation of a new system. This important phase is composed of severalsteps. It provides the understanding and procedural details to implementsthe system. Design goes through a logical and physical stage of the

progress. Logical design reviews the present physical system, preparesinput/output specifications, makes audit security and controlspecifications, detailed implementation plans, and prepares the logicaldesign walkthrough. The physical design makes out the details of the

physical system, plans the system implementation and specifies any newhardware and software products.

System design is a highly creative process, which can be greatlyfacilitated by the following:

1. Strong problem definition.2. Pictorial description of the existing systems.3. Set of requirements of the new systems.


19/100


20/100


20/100


21/100

Project Planning AndManagement

Project management is a technique used by a manager to ensure successfulcompletion of a project. It includes the following functions:

Estimating resource requirements Scheduling tasks and events Providing for training and site preparation

Selecting qualified staff and supervising their work Monitoring the projects program Documentation Periodic evaluation Contingency planning

From these functions, we can see that project management is a specializedarea. It involves the application of planning, organization, and controlconcepts to critical, one-of-a-kind projects.

Without Planning it is difficult to measure progress. As plans arecrystallized, crisis should begin to disappear. A project manager must planthe life cycle of the project and delegate authority for its implementation.Project Planning involves plotting project activities against a time frame.One of the first steps in planning is developing a road map structure or anetwork based on analysis of the tasks that must be performed to completethe project.

My project was not a critical one and there was nothing in it to implement

these all functions as I create the project and there was no one else with me.Therefore all functions of project management need not be implemented.


21/100


22/100


22/100


23/100

ER-DIAGRAM


23/100

ANKITSVIDEO LIBRARY

Addmovie

Exit

Issue

Return

Printreport

Delete

Price

Rent

Copy

Moviename

Rent

cust.name

Price

Cust.addMovie

list

Cust.info

Movie

Rent

Price

Copie

NameMovie.

Cust.name

Add

Name

Price

Rent

Copy

Cust.nam

e

Add

Movie.


24/100


24/100


25/100

DFD(Data FlowDiagram)

Concept

A Data Flow Diagram (DFD) is a graphical tool used to describe andanalyze the movement of data through the system- manual orautomated including the process, stores of data and delays in thesystem. They are central tools and the basis from which othercomponents are developed. It depicts the transformation of data fromwhich other components are developed. It depicts the transformationof data from input to output through processes and the interaction

between processes.

Transformation of data from input to output through processesdescribed logically and independent of physical components is calledthe DFD. The physical DFD shows the actual implementations andmovement of data between people, departments and workstations.

DFDs are excellent mechanism for communicating with the customersduring requirement analysis and are widely used for representing of

external and top-level internal design specification. In the lattersituations, DFDs are quite valuable for establishing namingconventions and names of the system components such as subsystems,files and data links.

A DFD, also known as bubble chart, has the purpose of clarifyingsystem requirements and identifying major transformation that will

become programs in system design. So, it is starting point of design phase that functionally decomposes the requirement specificationsdown to the lowest level of detail. A DFD consists of a series of

bubbles joined by lines.

In a DFD there are four components:


25/100


26/100

Sources or Destination of data such as human beings, entities, whichinteract with the system outside the system boundary, who forms thesource and the recipient of information are depicted in the form of aclosed rectangle.Data flow is a packet of data. It identifies data flow. It is a pipelinethrough which information flows. It is depicted in DFD as an arrowwith the pointer pointing in the direction of the data flow. Thisconnecting symbol is present between the entity, process and datastores. This arrow mark also specifies sender and receiver.Process depicts the procedure, function or modules that transforminput data to outputs. They are represented as circles or bubble withthe procedure name and the unique number inside the circle.Data stores are the physical areas in the computers hard disk where agroup of related data is stored in the form of files. They are depictedas an open-ended rectangle. The store is used either for storing data

into files or for the reference purpose.

The DFD methodology is quite effective, especially when the requireddesign is unclear. The DFD is easy to understand after a brieforientation.


26/100


27/100

Data Flow Diagram(0 level)(INFORMATION SYSTEM FOR VIDEO LIBRARY)

Detail entered through keyboard


27/100

Data input

Temporary

stored inprocessing

Data

permanently

stored in a data

file

Data output


28/100

Detailed Design

Data Flow Diagram(1

level)

Data entered

Input

Memory

Input &

Output data

Output


28/100

Add module

Temporarydata

Permanentlystored in file

ExtractingInformation

From file

Display module Delete module


29/100


29/100


30/100

Hardware and SystemRequirement

Following Hardware and software are required to run the

program:

Hardware used:-

Processor- Pentium 2000MHZ or P III or above

Memory- 128 MB RAM or above

Hard disk- 2 GB or above (at least 10 MB free space

Required)

Cache- 256 KB or Above Monitor- SVGA Monitor

Peripherals- Standard Keyboard & Mouse

Software used:-

Operating System- MS Windows 98 or above Application Software- Turbo C++ compiler,

MS Word 2003


30/100


31/100


31/100


32/100

//~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

//****************************************************

//PROJECT ON INFORMATION SYSTEM FOR VIDEOLIBRARY//***************************************************

*//~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

~~~~~

//****************************************************

// PASSWORD=nehak//****************************************************

//****************************************************

// HEADER FILES USED//***************************************************

*

#include#include#include#include#include#include#include#include

#include

//****************************************************

// CREATION OF STRUCTURE VIDEO


32/100


33/100

//****************************************************

struct video{

char name[100];float rent;float copy;float copy_init;int count;int price;

};

//****************************************************// CREATION OF STRUCTURE CUSTOMER//***************************************************

*

struct customer{char vid_name[100];

char cust_name[100];char cust_add[200];int cust_count;

};

//****************************************************

// THE CLASS CONTAINING ALL THE FUNCTIONS//***************************************************

*

class fns{private : //PRIVATE MEMBER FUNCTIONS


33/100


34/100

int i,row,flag;char ch,ans,test;char name_iss[100],name[100];char name_customer[100],cust_address[200];public: //PUBLIC MEMBER FUNCTIONS

void res(); //FOR DISPLAYING THE MAIN MENUvoid add(); //FOR ADDING VIDEOSvoid retur(); //FOR RETURNING VIDEOSvoid issue(); //FOR ISSUING VIDEOSvoid report(); //FOR DISPLAYING RECORDSvoid credits(); //FOR SHOWING CREDITSvoid del(); //FOR DELETING VIDEOSvoid del_cust(); //FOR DELETING CUSTOMERSvoid count1(); //FOR READING THE NO. OF VIDEOS

void count2(); //FOR WRITING THE NO. OF VIDEOSvoid count3(); //FOR READING THE NO. OFCUSTOMERS

void count4(); //FOR WRITING THE NO. OFCUSTOMERS

void init_display(); //FOR INITIAL DISPLAYvoid password(); //FOR PASSWORDvoid border(); //FOR OUTER BOUNDARYvoid start(); //FOR STARTING OF A PROGRAM

void first(); //FOR FIRST PAGE OF A PROGRAM};//***************************************************

*// CREATION OF FIRST PAGE *//***************************************************

*void fns::first(){

clrscr();textbackground(1);clrscr();int i,j;

_setcursortype(_NOCURSOR);


34/100


35/100

gotoxy(33,25);cout


36/100

midx = getmaxx() / 2;midy = getmaxy() / 2;setcolor(getmaxcolor());int i;

for(i=1;i


37/100

// CREATION OF BORDER *//***************************************************

*

void fns::border()

{int i;a:for(i=1;i


38/100

}

//****************************************************

// CREATION OF OBJECTS *//****************************************************

video vid;fns functions;customer cust;

//****************************************************// THIS FUNCTION ADDS NEW RECORDS *//***************************************************

*

void fns :: add(){ clrscr();textbackground(2);

ans='y';do{count1();clrscr();gotoxy(32,5);cout


39/100

if(strlen(name)==0){gotoxy(28,21);cout


40/100

fflush(stdin);cin>>vid.rent;gotoxy(20,14);cout>vid.copy;if(vid.copy


41/100

void fns :: issue(){clrscr();textbackground(3);

flag=0;ifstream vfile;vfile.open("cv.dat");ofstream afile;afile.open("a.dat");clrscr();gotoxy(34,5);cout


42/100

gotoxy(59,21);fflush(stdin);cin>>ans;if((ans=='y')||(ans=='Y')){

clrscr();gotoxy(34,5);cout


43/100

cout


44/100

afile.close();ifstream cfile;cfile.open("a.dat");ofstream bfile;bfile.open("cv.dat");

while(cfile){cfile.read((char *)&vid,sizeof(video));if(!cfile)break;bfile.write((char *)&vid,sizeof(video));}cfile.close();bfile.close();

}

//****************************************************

// THIS FUNCTION RETURNS A VIDEO *//***************************************************

*

void fns :: retur(){ clrscr();textbackground(4);// border();flag=0;row=0;ifstream vfile;vfile.open("cv.dat");ofstream afile;

afile.open("a.dat");clrscr();gotoxy(30,5);cout


45/100

cout


46/100

ifstream zfile;zfile.open("cust.dat");while(zfile){zfile.read((char *)&cust,sizeof(customer));

if(!zfile)break;

if((strcmpi(name_iss,cust.vid_name)==0)&&(strcmpi(cust_address,cust.cust_add)==0))

{if(strcmpi(name_customer,cust.cust_name)==0){

vid.copy++;

flag=1 ;}}

}zfile.close();if(flag==0){gotoxy(19,21);cout


47/100

cout


48/100

//******************************************************

// THIS FUNCTION DISPLAYS THE IMPORTANTINFORMATION *

//***************************************************

***

void fns :: report(){clrscr();//border();gotoxy(38,5);cout


49/100

gotoxy(19,6);cout


50/100

xfile.close();clrscr();gotoxy(38,5);cout


51/100

clrscr();row=8 ;clrscr();gotoxy(19,5);cout


52/100

dfile.open("cv.dat");count1();clrscr();flag=0;gotoxy(32,5);

cout


53/100

gotoxy(20,18);cout


54/100

ofstream bfile;bfile.open("cv.dat");while(cfile){cfile.read((char *)&vid,sizeof(video));

if(!cfile)break;bfile.write((char *)&vid,sizeof(video));

}cfile.close();bfile.close();count1();vid.count--;count2();

gotoxy(27,21);ifstream xfile;xfile.open("cust.dat");ofstream wfile;wfile.open("c.dat");while(xfile){xfile.read((char *)&cust,sizeof(customer));if(!xfile)

break;if(strcmpi(name,cust.cust_name)==0);elsewfile.write((char *)&cust,sizeof(customer));

}xfile.close();wfile.close();ifstream efile;efile.open("c.dat");

ofstream ffile;ffile.open("cust.dat");while(efile){efile.read((char *)&cust,sizeof(customer));


54/100


55/100

if(!efile)break;ffile.write((char *)&cust,sizeof(customer));

}efile.close();

ffile.close();gotoxy(27,21);cout


56/100

if(!vfile)break;if(cust.cust_count==i);else if(cust.cust_count!=i)afile.write((char *)&cust,sizeof(customer));

}vfile.close();afile.close();ifstream cfile;cfile.open("c.dat");ofstream bfile;bfile.open("cust.dat");while(cfile){

cfile.read((char *)&cust,sizeof(customer));if(!cfile)break;bfile.write((char *)&cust,sizeof(customer));}cfile.close();bfile.close();

}

//****************************************************

// THIS FUNCTION DISPLAYS THE CREDITS *//***************************************************

*

void fns :: credits(void){clrscr();

// border();textbackground(5);char text1[]={"CREDITS"};

char text2[]={"Information system for Video LibraryManagement"};


56/100


57/100

char text3[]={"Was Made On C++"};char text4[]={"For DOEACC 'A' LEVEL By"};char text5[]={"NEHA KALRA"};char text8[]={"Under The Super Vision Of"};char text9[]={"Our C++ Teacher"};

char text10[]={"Mr. Mohit Mathur"};gotoxy(37,5);for(i=0;i


58/100

gotoxy(33,17);for(i=0;i


59/100

clrscr();password();gotoxy(20,14);

}

//*****************************************************

// THIS FUNCTION IS DISPLAYS THE MAIN MENU//***************************************************

**

void fns :: res(){ clrscr();

// border();while(ch!='7'){textbackground(4);clrscr();gotoxy(30,5);cout


60/100

// border();gotoxy(33,21);coutch;switch(ch){case '1':add();

break;case '2':issue();

break;case '3':retur();

break;case '4':report();break;

case '5':del();break;

case '6':credits();break;

case '0':exit(0);default:cout


61/100

int pass[5];const int check[5]={'a','n','k','i','t'};LABEL:clrscr();gotoxy(30,14);

cout


62/100

void fns :: count2(){ofstream yfile;yfile.open("ab.dat");yfile.put(vid.count);

yfile.close();}

//*****************************************************

// THIS FUNCTION READS THE NUMBER OF VIDEOS//***************************************************

**

void fns :: count1(){vid.count = 0;ifstream zfile;zfile.open("ab.dat");zfile.get(test);vid.count=test;if(!zfile)

vid.count=0;zfile.close();

}

//*****************************************************

// THIS FUNCTION WRITES THE NUMBER OFCUSTOMERS

//*****************************************************

void fns :: count4(){


62/100


63/100

ofstream yfile;yfile.open("ba.dat");yfile.put(cust.cust_count);yfile.close();

}

//*****************************************************

// THIS FUNCTION READS THE NUMBER OFCUSTOMERS

//*****************************************************

void fns :: count3(){cust.cust_count=0;ifstream zfile;zfile.open("ba.dat");zfile.get(test);cust.cust_count=test;if(!zfile)cust.cust_count=0;

zfile.close();}

//*****************************************************

// START OF MAIN//***************************************************

**

void main(){textbackground(MAGENTA);

functions.first();functions.init_display();


63/100


64/100

functions.start();functions.res();

}

//~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

~~~~~~//*****************************************************

// END OF PROJECT//***************************************************

**//~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

~~~~~~


64/100


65/100


65/100


66/100

******************************************************

MAIN MENU******************************************************

VIDEO LIBRARY MANAGEMENT~~~~~~~~~~~~~~~~~~~~~~~~1. To Add a Video

2. To Issue a Video

3. To Return a Video

4. To Print a Report

5. To Delete a Video

6. To Display Credits

0. To Exit

Enter your choice:


66/100


67/100

CHOICE 1

******************************************************

ADD MODULE******************************************************

To Add a New Video

Name ==> KRAZY4

Price ==> 250

Rent ==> 50

Copies ==> 8


67/100


68/100

Do You Want To Continue...? (Y/N):

CHOICE 2

*****************************************************

* ISSUE MODULE******************************************************

To Issue a Video

Enter Name of the VideoYou Want To Issue ==> GURU

Name => GURU

Rent => 40


68/100


69/100

Do You Want To Continue...? (Y/N): Y

To Issue a Video

Enter Your Name ==> NEHA KALRA

Enter Your Address ==> PITAMPURA

Advance = Rs.200

Do You Want To Continue...? (Y/N): Y


69/100


70/100

CHOICE 3

******************************************************

RETURN MODULE******************************************************

To Return an Issued VideoEnter Name of the Video

You Want To Return ==> GURU

Name => GURU

Rent => 40


70/100


71/100

Press Any Key to Continue

To Return an Issued Video

Enter Your Name ==> NEHA KALRA

Enter Your Address ==> PITAMPURA

Advance Paid By You ==> Rs.200

Amount Due To You ==> Rs.160


71/100


72/100

The Video Has Been Successfully Returned

CHOICE 4

******************************************************

DISPLAY INFORMATION******************************************************

Display

1. To Display Customer Information2. To Display the Video Records

3. Return to Main Menu


72/100


73/100

Enter your choice:

Sub choice 1 of choice 4

Customer Details

Name Address Video

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Neha pitampura 123Neha pitampura jab we met


73/100


74/100

Neha Rohini 123123 west 123

Sub choice 2 of choice 4

Movie list with detail information

Name Copies Price Rent

Initial / Current

----------------------------------------------Jab we met 3 / 1 250 40123 3 / 1 290 45KRAZY4 8 / 8 250 50


74/100


75/100

CHOICE 5

****************************************************** DELETE MODULE

******************************************************

To Delete a Video

Enter Name of the VideoYou Want To Delete ==> 123


75/100


76/100

Name => 123

Price => 290

Rent => 45

Initial Copies => 3

Current Copies => 1

Are You Sure... (Y/N)

CHOICE 6

****************************************************** TO DISPLAY CREDITS

******************************************************

CREDITS


76/100


77/100

Information System for Video Library

Was Made On C++

For DOEACC 'A' LEVEL By

NEHA KALRA

Under The Super Vision Of

Our C++ Teacher

Mr. MOHIT MATHUR

Press Any Key to Continue


77/100


78/100


78/100


79/100

Introduction to Testing

The importance of software testing and its implications with respect tosoftware quality cannot be overemphasized. Software testing is a crucialelement of software quality assurance and represents the ultimate reviewof specification, design, and coding.

The increasing visibility of software as a system element and theattendant costs associated with a software failure are motivating forcesfor well-planned, thorough testing. It is not unusual for a software

development organization to expend 40 % of total project effort ontesting.

Defect can be caused by a flaw in the application software or by a flaw inthe application specification. For example, unexpected (incorrect) resultscan be from errors made during the construction phase, or from analgorithm incorrectly defined in the specification. Testing is commonlyassumed to mean executing software and finding errors. This type oftesting is known as dynamic testing, and while valid, it is not the mosteffective way of testing. Static testing, the review, inspection and

validation of development requirements, is the most effective and costefficient way of testing. A structured approach to testing should use bothdynamic and static testing techniques.

1.Testing Objectives

Testing is a process of executing a program with the intent of finding an

error .A good test case is one that has a high probability of finding an asyet undiscovered error. If testing is conducted successfully (i.e. accordingto the objective stated), it will uncover errors in the software. As asecondary benefit, testing demonstrates that software functions appear to

be working according to specification, that performance requirements


79/100


80/100

appear to have been met. In addition, data collected when testing isconducted provides a good indication of software reliability and someindication of software quality as a whole.

Ten Testing Rules

1. Test early and test often.

2. Integrate the application development and testing life cycles. You'llget better results and you won't have to mediate between two armedcamps in your IT shop.

3. Formalize a testing methodology; you'll test everything the same wayand you'll get uniform results.

4. Develop a comprehensive test plan; it forms the basis for the testingmethodology.

5. Use both static and dynamic testing.

6. Define your expected results.

7. Understand the business reason behind the application. You'll write abetter application and better testing scripts.

8. Use multiple levels and types of testing (regression, systems,integration, stress and load).

9. Review and inspect the work, it will lower costs.


80/100


81/100

10. Dont let your programmers check their own work; they'll miss theirown errors.

Testing and Quality Assurance

What is the relationship between testing and Software Quality Assurance(SQA)? An application that meets its requirements totally can be said toexhibit quality. Quality is not based on a subjective assessment butrather on a clearly demonstrable, and measurable, basis. QualityAssurance and Quality Control are not the same. Quality Control is a

process directed at validating that a specific deliverable meets standards,is error free, and is the best deliverable that can be produced. It is aresponsibility internal to the team. QA, on the other hand, is a review

with a goal of improving the process as well as the deliverable. QA isoften an external process. QA is an effective approach to producing ahigh quality product. One aspect is the process of objectively reviewing

project deliverables and the processes that produce them (includingtesting), to identify defects, and then making recommendations forimprovement based on the reviews. The end result is the assurance thatthe system and application is of high quality, and that the process isworking. The achievement of quality goals is well within reach whenorganizational strategies are used in the testing process. From the clients'

perspective, an application's quality is high if it meets their expectations.

Testing and Types of testing

One of the test methods SQA team practice is "Black Box" testing. TheSQA engineers, like the customers whom they attempt to emulate, areisolated from the source code and must rely upon their understanding ofthe application and its features and functions. SQA engineers work withDevelopment engineers toward development of code which lends itselfto the exercise of automated test tools, thus providing for stable,repeatable, reliable testing of base features and functions. The deductive,reasoning, creative skills of the SQA engineers are thus freed from the


81/100
http://www.sqatester.com/methodology/testmethods.htm#Blackhttp://www.sqatester.com/methodology/testmethods.htm#Black


82/100

more repetitive tasks to focus on development of more user centrictesting, which expands the scope coverage.

Manual Testing

-GUI - SQA team members upon receipt of the Development build, walkthrough the GUI and either update existing hard copy of the productRoadmaps, or create new hard copy. This is then passed on to the Toolsengineer to automate for new builds and regression testing. Defects areentered into the bugs tracking database, for investigation and resolution.Questions about GUI content are communicated to the Developmentteam for clarification and resolution. The team works to arrive at a GUIappearance and function that is "customer oriented" and appropriate for

the platform, Web, UNIX, Windows, and Macintosh. Automated GUIregression tests are run against the product at Alpha and Beta "Hand offto QA, (HQA) to validate that the GUI remains consistent throughoutthe development process. During the Alpha and Beta periods, selectedcustomers validate the customer orientation of the GUI.-Features & Functions - SQA test engineers, relying on the teamdefinition, exercise the product features and functions accordingly.Defects in feature/function capability are entered into the defect trackingsystem and are communicated to the team. Features are expected to

perform as expected and their functionality should be oriented towardease of use and clarity of objective. Tests are planned around newfeatures and regression tests are exercised to validate existing featuresand functions are enabled and performing in a manner consistent with

prior releases. SQA using the exploratory testing method manually testsand then plans more exhaustive testing and automation. Regression testsare exercised which consist of using developed test cases against the

product to validate field input, boundary conditions and so on...Automated tests developed for prior releases are also used for regressiontesting.

-Installation - Product is installed on each of the supported operatingsystems in either default, flat file configuration, or with one of thesupported databases. Every operating system and database, supported bythe product, is tested, though not in all possible combinations. SQA iscommitted to executing, during the development life cycle, the


82/100
http://www.sqatester.com/glossary/index.htm#Graphicalhttp://www.sqatester.com/glossary/index.htm#Handhttp://www.sqatester.com/softwarelife/index.htm#Alphahttp://www.sqatester.com/softwarelife/index.htm#Betahttp://www.sqatester.com/glossary/index.htm#featurehttp://www.sqatester.com/glossary/index.htm#Graphicalhttp://www.sqatester.com/glossary/index.htm#Handhttp://www.sqatester.com/softwarelife/index.htm#Alphahttp://www.sqatester.com/softwarelife/index.htm#Betahttp://www.sqatester.com/glossary/index.htm#feature


83/100

combinations most frequently used by the customers. Clean and upgradeinstallations are the minimum requirements.Documentation - All documentation, which is reviewed by Development

prior to Alpha, is reviewed by the SQA team prior to Beta. On-line helpand context sensitive Help are considered documentation as well asmanuals, HTML documentation and Release Notes. SQA not onlyverifies technical accuracy, clarity and completeness, they also provideeditorial input on consistency, style and typographical errors.

Automated Testing

-GUI - Automated GUI tests are run against the product at Alpha andBeta "Hand off to QA" (HQA) to validate that the GUI has remained

consistent within the product throughout the development process. Theautomated Roadmaps walk through the client tool windows andfunctions, validating that each is there and that it functions.-Data Driven - Data driven scripts developed using the automation toolsand auto driver scripts are exercised for both UNIX and Windows

platforms to provide repeatable, verifiable actions and results of corefunctions of the product. Currently these are a subset of all functionality.These are used to validate new builds prior to extensive manual testing,thus assuring both Development and SQA of the robustness of the code.

-Future - Utilization of automated tools will increase as our QA productgroups become more proficient at the creation of automated tests.Complete functionality testing is a goal, which will be implementedfeature by feature.


83/100


84/100

Reporting

The SQA team lead produces a formal test plan, which is submitted to

the project team for validation and information. Input is solicited for theunderstanding of requirements, so that the plan can accurately reflect thetesting which will be required. Because of the variances betweenDevelopment teams' style of disseminating feature, function scope anddefinition, the amount of information available is not always consistent.The SQA lead attempts to establish a good working relationship with theDevelopment team, so that questions can be asked and comprehensive,identical understanding of the product will exist. The lead also pairs aQA engineer with a development counter part to facilitate day-to-dayinteraction.

SQA engineers produce status sheets for distribution to the members ofthe product teams. The data on the status sheets have included: features,functions, time estimated to test, time consumed and amount of testingyet to be done, the last has proved to be too subjective. Some testengineers include the staff assigned to specific testing and the percentagecomplete. The later is difficult to estimate due to the iterative process, asfeature and function specifics change often and rapidly during thedevelopment cycle, as they are refined. The evolving report, whichappears to give the most information, is one which lists the features, the

build in which they were tested or re-tested and the pass or fail status ofthe test.SQA provides monitoring of the defects which appear in the product,through the use of QA designed Flashboards (graphical representationsof the aggregate numbers of defects) and reports. The defects found inthe product are recorded in a Bug Tracking database, where theinformation is made available to the development group. Informationstored in the database then provides statistical and trend analysis fordefect find rates and product areas. This information is compared to that

presented by the Development team and the Product team. Customer

support is kept abreast of these defects and influences the priorityassigned to the defect by the team.Team leads have established directories for their products in which test

plans and weekly status reports have been posted. These are updated


84/100


85/100

weekly by the team lead and reviewed by the manager and linked orposted to the QA home page on the intranet.QA managers work with their teams to assess better forms and methodsof information dissemination. These reviewed with the largerengineering and project teams so that the teams feel they understand thescope of work to be done by SQA and the status of a project currently

being tested.

TESTING TERMINOLOGY

Software testing is often equated to finding bugs. However test scenariosthat do not reveal failures are also informative, so I offer this definition:

SOFTWARE TESTING

It is a process of executing a software system to determine whether itmatches its specification and executes in its intended environmentThe fact that the system is being executed distinguishes testing fromcode reviews,In which uncompiled source code is read and analyzed statistically(usually by developers). Testing, on the other hand, requires a running

executable.

A specification is a crucial artifact to support testing. It defines correctbehavior so that incorrect behavior is easy to identify. Incorrect behavioris a software failure. Failures are caused by faults in the source code,which are often referred to as defects or bugs .The oracle comparesactual output with specified output to identify failures. Generally thecode developer diagnoses the casual fault.

Software can also fail by not satisfying environmental constraints thatfall outside the specification. For example, if the code takes too muchmemory, executes too slowly, or if the product works on one operatingsystem but not another, these are considered failures.


85/100


86/100

Software testing is classified according to the manner in which thetesters perform the first two phases of the testing process. The scope ofthe first phase, modeling the softwares environment, determineswhether the tester is doing unit testing, integration testing, orsystem testing.

Unit testing

It tests individual software components or a collection of components.Testers define the input domain for the units in question and ignore therest of the system. Unit testing sometimes requires the construction ofthrowaway driver code and stubs and is often performed in a debugger.

Integration testing

It tests multiple components that have each received prior and separateunit testing. In general, the focus is on the subset of the domain thatrepresents communication between the components.

System testing

It tests a collection of components that constitute a deliverable product.Usually, the entire domain must be considered to satisfy the criteria for asystem test.

The second phase of testing, test selection, determines what type oftesting is being done. There are two main types:

Functional testing requires the selection of test scenarios withoutregard to source code structure. Thus, test selection methods and testdata adequacy criteria, described in the main text, must be based on

attributes of the specification or operational environment and not onattributes of the code or data structures. Functional testing is also calledspecification-based testing, behavioral testing, and black boxtesting.


86/100


87/100

Structural testing requires that inputs be based solely on thestructure of the source code or its data structures. Structural testing isalso called code-based testingand white-box testing.


87/100


88/100


88/100


89/100

Maintenance

MAINTAINENCE REPRESENTS UP TO 70% OF THE TOTAL LIFE

CYCLE COST OF SOFTWARE.


89/100

DESIGNDESIGN CODECODE TESTTEST 11%11% 8%8%11%11%

MAINTAINCEMAINTAINCE 70%70%

CodeCode

20%20%

DESIGN TEST

40%40%

40%40%

TOTAL LIFETOTAL LIFE

CYCLE OFCYCLE OF

SOFTWARESOFTWARE

DEVELOPMENTDEVELOPMENT

COSTCOST


90/100

WHAT DO YOU MEAN BY SOFTWARE MAINTENANCE? WHATWHAT DO YOU MEAN BY SOFTWARE MAINTENANCE? WHATARE THE PROBLEMS FACED TO MAINTAIN A SOFTWAREARE THE PROBLEMS FACED TO MAINTAIN A SOFTWAREQUALITY?QUALITY?

Maintenance is the enigma of system development; it holds the softwareindustry captive, typing up, and programming resources. Analysts and

programmers spend far more time maintaining programs than they dowriting them. Maintenance accounts for 50-80 percent of total systemdevelopment. The federal government alone spends more than $1.3

billion a year on software maintenance. Whereas the cost of hardware hassteadily declined, the cost of producing programs has skyrocketed. Forexample, 10 years ago the development cost of one of Development ofDefense (DOD) project averaged $75 per line of programminginstruction, whereas maintenance costs ran as high as $4000 per line.

This problem occurs across industry largely because software is a

handmade product designed in an ad hoc fashion with few standards; incomes out late, is poorly documented, and therefore is difficult tomaintain. There are other problems as well:

1. Maintenance is not as rewarding as exciting as developingsystems. It is perceived as requiring neither skill norexperience.

2. Users are not fully cognizant of the maintenance problem or its

high cost.

3. Few tools and techniques are available for maintenance.

4. A good test plan is lacking.


90/100


91/100

5. Standards, procedure and guidelines are poorly defined andenforced.

6. Maintenance is viewed as a necessary evil, often delegated to junior programmers. There is practically no maintenancemanager job classification.

7. Programs are often maintained without care for structure anddocumentation.

8. There are minimal standards for maintenance.

GIVE THE BROAD STUDY ON MAINTAINCE OR ENHANCEMENT?GIVE THE BROAD STUDY ON MAINTAINCE OR ENHANCEMENT?

Maintenance can be classified as corrective, adaptive, or perfective.Corrective maintenance means repairing processing or performancefailures or making changes because of previously uncorrected problemsor false assumptions.Adaptive maintenance means changing the

program function. Perfective maintenance means enhancing the

performance or modifying the program function.Perfective maintenancemeans enhancing the performance or modifying the program to respondto the users additional or changing needs. Of these types, more time andmoney are spent on perfective than on corrective and adaptivemaintenance together.

Maintenance covers a wide range of activities, including correctingcoding and design errors, updating documentation and test data, andupgrading user support. Many activities classified as maintenance are

actually enhancements. Maintenance means restoring something to itsoriginal condition. Unlike hardware, however, software does not wearout; it is corrected.


91/100


92/100

In contrast, enhancement means adding, modifying, or redeveloping thecode to support changes in the specifications. It is necessary to keep upwith changing user needs and the operational environment.

Although software does not wear out like a piece of hardware, it ages

and eventually fails to perform because of cumulative maintenance. Overtime, the integrity of the program, test data, and documentationdegenerated as a result of modifications. Eventually, it takes more effortto maintain the application than to rewrite it.


92/100


93/100


93/100


94/100

Limitations

The application developed of Information System for Video Libraryhas following Limitations-:

This is not for online working.

Application developed does not imbibe any password security.

The Backup of all the data are quite obvious but the application hasnot provided any backup security option.

It is also incapable of handling any Network (LAN).

The program can only be executed on Turbo c++ or Visual c++.


94/100


95/100


95/100


96/100

Conclusion

This project is designed to meet the requirements of anInformation system

for video library. It has been developed in C++ and the database has been

built in C++ binary file only, keeping in mind the specifications of the

system.

For designing the system we have used simple data flow diagrams.

Overall the project teaches us the essential skills like:

1. How to engineer particular software product be it a small package for

a small company or a huge package for an MNC.

2. The steps needed to develop a particular product.

3. The precautions that need to be taken to build a quality product.

4. The factors that need to looked after while manufacturing a product.

5. Using the system analysis and design techniques like the context free

diagrams, data flow diagrams and the entity relationship diagrams.

6. Understanding programming logic and language in C++.


96/100


97/100


97/100


98/100

Bibliography

A REFERENCE SECTION LISTING SPECIFIC REFERENCEA REFERENCE SECTION LISTING SPECIFIC REFERENCEMADE IN THE TEXT.MADE IN THE TEXT.

There were not much specific/special references in the whole project; fewof the ref. mentioned is given below:

Introduction : This section deals with the information aboutproject, meaning of banking, aspects of banking and much more.

Analysis and Design:: This section explains what the steps aretaken in the analysis and design procedure in accordance with the

project. This section is taken from:

System Analysis and Design (Elias M.Awad).

Project Management and Planning:: This section dealswith the management and planning of all the modules to be createdand implemented. This section was taken from: System Analysis and Design (Elias M.Awad).

Data Flow Diagram:: This section explains few things aboutthe DFDs. This section was taken from:


Testing:: This section explains the testing procedure and the stepstaken for the same, These were taken from:


98/100


99/100


A Bibliography section listing general literature, related to theA Bibliography section listing general literature, related to theproject that has been read.project that has been read.

References:

SYSTEM ANALYSIS AND DESIGN (Elias M.Awad).

LET US C++ (Yashavant P.kanetkar).

Object-Oriented Programming with C++ (E.Balaguruswamy).


99/100


100/100

Suggestions

______________________________________________________

______________________________________________________

____________________________________________________________________________________________________________

______________________________________________________

______________________________________________________

______________________________________________________

______________________________________________________

______________________________________________________

______________________________________________________

______________________________________________________

______________________________________________________

______________________________________________________

______________________________________________________

______________________________________________________

______________________________________________________

______________________________________________________

______________________________________________________

______________________________________________________

______________________________________________________

______________________________________________________

______________________________________________________

______________________________________________________

______________________________________________________

______________________________________________________

______________________________________________________

video libray system neha 536850

Documents