Software Engineering

Project
MEGA MART ADVERTISEMENT RELEASE MANAGEMENT
Academic Session: 2011-2014 Course Code: B.B.A (CAM)-154

Submitted By Ashish Kumar Roll no: 01390101911 B.B.A (CAM) 2nd Semester

Submitted to: Ms.Sheetal Under the guidance of Ms.Sheetal

FAIRFIELD INSTITUTE OF MANAGEMENT & TECHONOLOGY

(Affiliated to GGS Inderprastha University, Delhi)

ISO 9001:2008 & 14001:2004 CERTIFIED Kapashera, New Delhi-110037

CERTIFICATE

This is to certify that the project report entitled MEGA MART ADVERTISMENT RELEASE MANAGEMENT is being submitted by Ashish Kumar in partial fulfillment of Degree of Bachelor of Business Administration to Fairfield Institute Of Management & Techonology is a record of bonafied work carried out by them under my guidance and supervision. The results embodied in this project report have not been submitted to any other University or Institute for the award of any degree.

Guide Ms. Sheetal Dept. Of Object Oriented Programing Using C++

ACKNOWLEDGEMENT
Behind every student who ascends the height of success and achievement has a group effort and it is reflected in this project. We cannot undermine the role and responsibility of the people who were instrumental in extending all possible support for preparation of this project report. We express our deep sense of gratitude and appreciation to Software Engineering department Ms. Anuradha Khatri and our guide Ms. Sheetal for their constant valuable guidance and help in implementing our project report. We further take this opportunity to thank all the staff members of our college for taking active participation and providing us all the necessary data and statistics during the preparation of our report so as to make it a great success.

Ashish Kumar

ABSTRACT
3

We can widespread our knowledge in the field of MARKETING. In this system we can innovatively create ads and can use them for publicity of the mega mart. We can find out their effectiveness and hence, can study the market along with the customers mind set. Mega Mart wanted to revive its brand image ,so it hired an ad agency for it.The ad agency came up with brilliant ideas for marketing.They created ads of all types like audio, video, print media etc.The task of managing these ads was huge and they wanted a software developed to manage the process better.

CONTENTS
CHAPTERS
1.

PAGE NO:

2. 3.

4. 5.

Introduction ............................................................................6 Overall Description..7 Feasibility11 3.1 Technical Feasibility: 3.2 Operational Feasibility: 3.3 Economical Feasibility: Software paradigm used.12 Hardware & software requirements........15
4

5.1 Hardware Specifications: 5.2 Software Specifications: 6. System Features.......16 6.1 login page 6.2 Staff Report page 6.3 Manager Report Page 7. Analysis..19 Functional Requirements: . Data flow Diagram . An Entity Relationship Diagram Description: 8. Testing.28 8.1 independent unit tests (iut): 8.2 system testing: 8.3 psychology of testing: 8.4 testing objectives: 8.5 levels of testing: 8.5.1 unit testing: 8.5.2 integration testing: 8.5.3 system testing: 8.5.4 acceptance testing: 8.5.5 white box testing: 8.5.6 black box testing: 8.6 test information flow: 8.7 system security 9. Future scope of the Project.....42 10.Bibliography43 1. Purpose Ad release and its maintenance is a very huge database. This database is a very sensitive part for any organization as on it depends, more or less the entire marketing. It requires a very keen and careful handling. By using this database, the person concerned for this section can update or retrieve any query he/she wants as per the requirement. As the whole organization is depending on this database so it needs to be under high security. Passwords in suitable sections help in enhancing the security level of the database. It is well managed by the authority concerned for the various segments of the database. INTRODUCTION

Intended Audience and Reading Suggestions This document is intended for the referral of the following section of readers: Developers Project Managers Users Testers Documentation Writers Mega mart and Forum mart Managers Advertisers Project Scope This project of Mega Mart Ad Release Management is to be integrated with the existing advertisement and marketing System. This will be added as a new feature to the ad release and maintenance department so that it will provide better publishing facilities for the firm and aims at the proper and easy management of the ad articles and market scenario.

References This document includes the following references:

Data Flow Diagram Data Model Diagram (E-R Diagram) Various User Interfaces

2.Overall Description

Product Perspective This product is going to be implemented against an existing system as it is more user-friendly and efficient. Using this software the concerned authority
6

can enter the data via an interface which will be stored in the database, rather than directly manipulating with the database. It takes less time to enter an item as only some selections need to be done rather than entering the values manually. And can be viewed publicly without any tempering in it. Product Features The product contents are Entering User Id and password in the Login screen. Viewing Advertisement pricing details. Viewing Strategy report. Entering Advertisement pricing details. Budget Allocation by the manager. All the data should be saved to database generating unique records. Display message to the user.

Entering User Id and Password in the login screen:Here basically the persons associated or authorized with the database management are allowed to access. They are prior provided with a user name and a password to access the database or the main field of work. The user name is the identity through which they are known to the database and the password they enter for their user name is like a key to the lock at the database house. However, the password can be changed from time to time but not the user name. The user name gives the database the information about the user who is logging in.

Viewing Advertisement pricing details:Here the individual, whether it is a staff or an official or the developer or the customer (the public) can view the advertising details. The details can be the pricing details, the discounts on some articles, the exciting offers, and all valid stores for that advertisement.

Viewing Strategy report:Here basically the manager or an official, who is held the authority to supervise and overview all the advertisement and marketing management, takes a look of the scenario from here. He studies and reviews the marketing details from a report called the strategy report. No staff or the users are allowed to access this part. Entering Advertisement pricing details:Here the staff and the manager or the official-in-charge of ad creation or ad release department enters their ads for the products along with the pricing details. Again here the pricing details include every bit of the rating details like the prices, the offers, the discounts, etc. Both the users and the manager can do this. Budget Allocation by the manager:The pricing is basically dependant on a budget that is thought and decided by the manager-in-charge of the firms marketing and advertisement department. The staff or the person who creates and releases the ads for the mega mart or the forum mart is allowed to put up ads only in the decided budget. The manager is the one who decides a budget for the advertisements of the products. A new budget cannot be taken up while the old one is yet to be accomplished.

All the data should be saved to database generating unique records:All the ads, the budget, the pricing details, the valid dates for the ads and so on, whatever it is created `by the staff or the manger, every data is required to be added and saved in the existing database of the mega mart. Every data or record that is entered and saved in the database is of significance and is unique. No duplicate data are entertained in the database.
8

Display message to the user:The user being the final audience has the access to all the ads that the mega mart releases for its marketing purpose. But not to the database, of course. The user can see all the ads and use them for buying the corresponding products. In case, the user is faced with some difficulties or violates or exceeds any term or condition of marketing, that is pre-defined, he is prompted with pre-defined messages. Also the user is provided with messages at required steps and times. This makes the interface more user friendly.

User Classes and Characteristics This software will be generally used by the staff and member, manager or the official-in-charge of advertisement management of the mega mart. But the authentication of various users is different. Operating Environment The operating environment of this software is: 1. Software required i) Windows (Vista, 7, Xp) ii) C++ 2. Hardware required i) Primary Disk RAM (min 512 MB) ii) Secondary Devices i.1) Hard Disk (min 40 GB)
9

i.2) External Disk User Documentation After the completion of the project, the user will be not provided with a User Manual like other software. But shall definitely have a pamphlet or a booklet depending upon the type of the ad released. If the ad is on a medium like internet (website), he/she shall have a help column on the page of display itself. if the ad is a audio or video one the users shall be given with the booklet with every detail in it. And a brochure if its a home to home advertisement. This lets the user help in knowing the product efficiently, so that they dont regret about their decision of having spent their money on an advertised product.

3.Feasibility
3.1 Technical Feasibility

Proposed project is beneficial only if it can turn into an online system that will meet the requirement. C++ also platform independent. It operates at the server side and provides output at the client end. It will run in those clients in which visual studio are installed.

3.2 Operational Feasibility: The client has limited access. The client can access those informations from the server which are being authenticated by the server.

10

3.3 Economical Feasibility The project can be set up with minimal cost.

Since, all features regarding a management are available in this

application, the user need not to install different softwares.

4.Software Paradigm Used

A prototype model has been used that suggests that a working prototype of the system should be built before carrying out the development of the actual software. A prototype is a toy implementation of the system. By constructing the prototype and submitting it for user evaluation, many customer requirements get properly defined and technical issues get resolved by experimenting with the prototype which finally minimizes the change requests from the customer and the associated redesign costs. The software engineering paradigm is also called a process model. A process model for software engineering is chosen based on the nature of the

11

project and application, the methods and tools to be used, and the controls and deliverables that are required. In this project, System Development Life Cycle (SDLC) model is used. The various phase of this method can be described briefly follows.

Fig: model

Prototyping of software development

Phase Requirement s Determinatio n Requirement s Speciation

What is done? Determine requirements to be met by System being compiled.

What

is

the

end

product? Set of priorities

Draw up understandable plan of what the system will provide as outputs. Determine needs and priority by consensus among end users.

Detailed specifications of information to be provided.

12

Feasibility Study

Taking into account available resources such as human, computers, time and money and find whether specified requirements can be met.

Feasibility Document specifying resource needs and availability. Expected costs vs. Benefits of the system are carried Design programs. Database, test plan. Evaluation report with suggestion to improve. Improved system containing modifications and improvement

System Design System Evolution System Modification/ Maintenance

Logical design of programs, design of databases, test and implementation plan. Find out from users if system meets their requirement. Change system, adding or deleting features to satisfy users(modified) needs

5.Hardware / Software Requirements

5.1 Hardware Specifications
13

Hardware Used: Microprocessor Processor Speed Main Memory Secondary Memory : Intel Pentium core 2 Duo : 1.8GHz : 256 MB : 40 GB

Secondary Memory Speed : 1024 MHz RAM Capacity 5.2 Software Specifications Operating System: Windows (XP, Vista, 7) Front End: C++ : 512 MB

6. System Features
This section illustrates organizing the functional requirements for the product by system features, the major services provided by the product. 6.1) Login page
14

The login page is the first page before entering into the database and account section of the department. Here the Login screen is required to allow only validated users to use the application. The Login screen, allows the user to enter his/her User Id and Password. On validating the user he/she is redirected to the next page depending on whether hes staff or manager. In case the User forgets his password by clicking on the forgotten password link, hes directed to another page which displays a message stating password has been sent to his mail id. This is done only when the User enters a valid user id. 6.2) Staff Report page The staff, after they login can see the data or ad details entered by them. The ads are sorted and viewed only in descending order of the applicable rates. And this is always. The staff can only enter the new Ad details and is not allowed to modify or delete any records. All the data and ads are unique and different from each other. Duplicate and null data is not allowed. Once the details are entered they are saved into the database. This is done for every new data. If the applicable rate is more than the budget amount then a prompt is generated whether he still wants to save the record else the record is saved normally.

6.3) Manager Report page Managers are allowed to view the details of the Ads created by the staff members. Here also the ads are sorted and viewed in the descending order of the applicable rate in order to allocate budget. The manager creates a new budget after viewing the strategy report in which he enters the details of the budget.
15

The budget allocation page contains the following columnsa) Budget amount b) Start date and c) End date of the budget. A new budget cannot be created until the existing tenure is completed. The manager is the only person authorized to prepare budgets.

External Interface Requirements User Interfaces The interfaces are to be prepared using the platform of vb.Net (Visual Studio 2005).The standards that will be used for the designing of the interfaces are as follows: Text boxes o Border Style = fixed 3D Buttons o Font Size = 10, bold Style = Microsoft Sans Serif Forms o Back Color = light cyan Labels o Font Size = 10, bold o Style = Microsoft Sans Serif

Software Interfaces The interfaces are connected to the database that stores all the details that are required for the working of the project as per the user requirement. The database is prepared using MYSQL server 2005.

16

Other Nonfunctional Requirements Performance Requirements The project of Mega Mart Ad Release Management will be having the following business logic which has been decided after consulting with the users, who are the consumers and the public. They are listed below: The database should be properly maintained for the efficient working of the software. Enough data storage capacity should be there. The project should be user friendly and understandable. There should low coupling and high cohesion. The information and data need to be accurate and true. The pricing details and its validation should be mentioned very clearly and precisely. The entire user requirement should be met. Security Requirements For the security reasons, the user authentications are to be given as follows: 1. Administrator o Creating an user Here the administrator has the power to create a new user who can access the accounts section. Here the individual can be the staff or the manager. o Deleting an user Here the administrator has the power to delete any user, means he has the authority to deprive any user from accessing the accounts section. The users here can be the staff or the manager. o Changing the password Here the administrator can change the password of any part of the part of the complete database. o Assigning authority to other users Here the administrator has the power to assign authority to any outside user to access the accounts section, i.e., the database (only some restricted pages) in view mode only. 2. Manager
17

o This person has the authority to estimate and prepare a budget, can change the budget. o He / she can take important decisions regarding any transaction. o Can do any sort of manipulations in the database. o Can punish his peers. After the Administrator, the manager is the only very important person.

7. Analysis
Functional Requirements:

18

This project is for to make campus recruitment drive of a college online, so that a student can access about the Upcoming Company, package, date. Student can also view their result on college website. Placement officer can also get information about students record anywhere. They can modify and update the record. After studying and analyzing we concluded that the following details of the software are required. The pictorial representation is the best way to represent the collection of data at the time of analysis and represents in the form of HIPO diagram (Modular Description), DFD (Data Flow Diagram), ERD (Entity Relationship Diagram) etc. The pictorial representation provides better understandable approach for development. Data flow Diagram A dataflow diagram is a graphical representation that depicts information flow and the transform that are applied as data move from input and output. The basic forms of a Data Flow Diagram also move from known as a Data Flow Graph or a Bubble Chart. The data flow diagram (DFD) shows the functional relationships of the values computed by a system including input values and output values and internal data store. A data flow diagram is graph showing the flow of data values. In 0-level DFD shows how a visitor can register and how the registered user can login to the software and access various options. The level-1 DFD shows that a visitor enters the registration details and these details are verified. The new registration details are send back to the database registered user and the username is given to the visitor. Registered user can
19

directly login with his/her username and process the options but if the user enters any incorrect username or password then he/she has to re-enter. Types of Data Flow Diagram: Logical Data Flow Diagrams Physical Data Flow Diagrams

20

External Entity: The External Entity symbol represents sources of data to the system, or destinations of data from the system. i.e. a Person, a System, or an organization that sends or receives data.

Data flow symbol: The Data Flow symbol represents movement of data. Data Store Symbol The Data Store symbol represents data that is saved on some file or in a table in the database. Process Symbol The Process symbol represents an activity that transforms or manipulates the flow). data (A process transforms incoming data flow into outgoing data

Data flow diagram

MANAGER

GIVES DATA GETS DATA

AD RELEASE MANAGE MENT SYSTEM 0.0

GIVES DATA GETS DATA

STAFF

21

Fig: DFD level 0

Level 1

ADMGT_LOGIN_TB

ADMGT_AD_IDS_TB GIVES DATA GIVES DATA GIVES DATA GET DAT A GIVES DATA GIVES DATA GIVES USERID & PWD GIVES DATA MAINTAINS STAFF DETAILS GIVES USERID & PWD

ADMGT_CHANNEL_TB

MANAGER

MANAG ER MANAG E-MENT 1.0

STAFF MANAG E-MENT 2.0

STAFF

GIVES DATA

GIVES DATA

GET DATA ADMGT_DURATION_TB

GIVES DATA

GIVES DATA

GIVES DATA

GIVES DATA

ADMGT_TIME_SLOT_TB

22
ADMGT_BUDGET_TB

Fig : DFD level 1

Level 2

ADMGT_LOGIN _TB
GIVES DATA

ADMGT_CHANNEL_TB
GIVES DATA

ADMGT_AD_IDS_TB

GIVES DATA

VALIDATI ON 1.1

BUDGET ALLOCAT ION 1.2

GIVES DATA

ADMGT_DURATION_T B

GIVES USERID & PSW

MAINTAIN S
GIVES DATA GIVES DATA

MANAGER

ADMGT_TIME_SLOT_T B

ADMGT_BUDGET_TB

23

LEVEL-2 OF MANAGER

ADMGT_LOGIN _TB
GIVES DATA

ADMGT_CHANNEL_TB
GIVES DATA GIVES DATA MAINTAIN S

ADMGT_AD_IDS_TB

VALIDATI ON 2.1
GIVES USERID & PSW

AD ENTRY 2.2

GIVES DATA

ADMGT_DURATION_T B

STAFF GIVES DATA

GIVES DATA

ADMGT_TIME_SLOT_T B

ADMGT_BUDGET_TB

24

LEVEL -2 OF STAFF

An Entity Relationship Diagram Description: E-R diagram is one of the pictorial representation in which the meaningful relationships are entitled between various entities. It represents the real world application. The relationship is used in data modeling to represent an association between entities. This association has certain characteristic properties represented by the attributes of the relationship set.

ADMGT_BUDGET _TB

MAI NTAI NS

ADMGT_LOGIN_ TB US ES

ADMGT_CHANNE L_TB

ADMGT_AD_IDS _TB US ES

US ES ADMGT_TIME_SLO T_TB

US ES

ADMGT_DURATIO N_TB 25

Fig: Entity relationship diagram

26

8.Testing
Testing plays a critical role in quality assurance for software .Due to the limitation of the verification method for the previous phases, design and requirement fault also appear in the code. Testing is used to detect these errors, in edition to the error introduced during coding phase. Testing is a dynamic method for verification and validation, where the system is to be tested is executed and behavior of the system is observed. Due to this testing the failure of the system can be observed, from which the presence of fault can be deduced. However, separate activities have to be performed to identify the faults. There are two method of testing: functional and structural. In functional testing, the internal logic of the system under testing is not considered and the test cases are decided from the specification or the requirements. It is often called Black Box Testing. Equivalence class partitioning, boundary analysis, and cause effect graphing are examples of methods for selecting test cases for functional testing. In structural testing, the test cases are decided entirely on the internal logic of the program or module being tested. As the goal of testing is to detect any errors in the programs different flavor of testing are often used. Unit testing are used to test a module or a small collection of modules and the focus is on detecting coding errors in modules. During integration testing modules are combined into sub-system, which are then tested. The goal here is to test the system design. In system testing and acceptance testing, the entire System is tested. The goal here is to test the
27

requirement themselves. Structural testing can be used for unit testing while at higher level mostly functional testing is used. In the project Monthly Materialization Report System we used the unit testing and functional testing. System testing is a critical phase in systems implementation. Testing of a system involves hardware device testing and debugging of computer programs and testing information processing procedures. Testing can be done with test data, which attempts to simulate all possible conditions that may arise during processing. The plane for testing are prepared and then implemented. The testing methods adopted in the testing of the system were Independent Unit Testing and System Testing

8.1 INDEPENDENT UNIT TEST (IUT) IUT focuses first on the modules, independently of one another, to locate errors. This enables the tester to detect errors in coding and logic that are contained within that module alone. Those resulting from the interaction between modules are initially avoided. IUT is generally white box oriented which is predicted on the close examination of procedural detail. It exercises all the logical decisions on their true and false side, executes all loops at their boundaries and within their operational bounds and checks whether the required validations have been met. White box testing exercises internal data structure to assure their validity.
28

8.2 SYSTEM TESTING Here the system testing involved is the most widely used testing process consists of five stages as shown in the figure. In general, the sequence of testing activities is component testing, integration testing then user testing. However, as defects are discovered at any one stage, they required program modifications to correct them and this may required other stages in the testing process to be repeated.

Testing is the process of detecting errors. Testing performs a very critical role for quality assurance and for ensuring the reliability of the software. The results of testing are used later on during maintenance also.
29

Testing is vital to the success of the system. System testing makes a logical assumption that if the parts of the system are correct, the goal will be successfully achieved. In adequate testing or non-testing leads to errors that may not appear until months or even years later (Remember the New York three day power failure due to a misplaced Break statement). This creates two problems: 1. The time lag between the cause and the appearance of the problem. 2. The time interval effect of the system errors on files and the records on the system. A small error can conceivably explode into a much larger problem. Effective testing early in the process translates directly into long term cost savings from a reduced number of errors. Another reason for system testing is its utility as a user oriented vehicle before implementation. The best program is worthless if it does not meet the user requirements. Unfortunately, the users demands are often compromised by efforts to facilitate program or design efficiency in terms of processing time or design efficiency.

Thus in this phase we went to test the code we wrote. We needed to know if the code compiled with the design or not? Whether the code gave the desired outputs on given inputs? Whether it was ready to be installed on the users computer or some more modifications were needed?
30

Through the web applications are characteristically different from there software counterparts but the basic approach for testing these web applications is quite similar. These basic steps of testing have been picked from software engineering practices. The following are the steps, we undertook: 1. The content of the Intranet site is reviewed to uncover Content errors. Content Errors covers the typographical errors, grammatical errors, errors in content consistency, graphical representation and cross referencing errors 2. The design model of the web application is reviewed to uncover the navigation errors. Use cases, derived as a part of the analysis activity allows a web designer to exercise each usage scenario against the architectural and navigational design. In essence these non-executable tests help to uncover the errors in navigation. When web applications are considered the concept of unit changes. Each web page encapsulates content navigation links, content and processing elements. It is not always possible to test each of these individually. Thus is the base of the web applications the unit to be considered is the web page. Unlike the testing of the algorithmic details of a module the data that flows across the module interface, page level testing for web applications is driven by content, processing and links encapsulating the web page.

3.

31

4. The Assembled web application is tested for overall functionality and content delivery. The various user cases are used that test the system for errors and mistakes. 5. The Web application is tested for a variety of environmental settings and is tested for various configurations and upon various platforms. The modules are integrated and integration test are conducted. 1. Thread based testing is done to monitor the regression tests so that the site does not become very slow is a lot of users are simultaneously logged on. 2. A controlled and monitored population of end users tests Intranet application, this all comprises of the User Acceptance Testing. Because web application evolves continuously, the testing process is an ongoing activity, conducted by web support staff in our case the Organizations IS people who will finally update and manage the application.

8.3 PSYCHOLOGY OF TESTING

The aim of testing is often to demonstrate that a program works by showing that it has no errors. The basic purpose of testing phase is to detect the errors that
32

may be present in the program. Hence one should not start testing with the intent of showing that a program works, but the intent should be to show that a program doesnt work. Testing is the process of executing a program with the intent of finding errors.

8.4 TESTING OBJECTIVES

The main objective of testing is to uncover a host of errors, systematically and with minimum effort and time. Stating formally, we can say, 1. Testing is a process of executing a program with the intent of finding an error. 2. A successful test is one that uncovers an as yet undiscovered error. 3. A good test case is one that has a high probability of finding error, if it exists. 4. The tests are inadequate to detect possibly present errors. 5. The software more or less confirms to the quality and reliable standards.

8.5 LEVELS OF TESTING

In order to uncover the errors present in different phases, we have the concept of levels of testing. The basic levels of testing are
33

8.5.1 UNIT TESTING

Unit testing focuses verification effort on the smallest unit of software i.e. the module. Using the detailed design and the process specifications, testing is done to uncover errors within the boundary of the module. All modules must be successful in the unit test before the start of the integration testing begins. In this project each service can be thought of a module. There are so many modules like Login, HR Department, Interviewer Section, etc. Each module has been tested by giving different sets of inputs. When developing the module as well as finishing the development, the module works without any error. The inputs are validated when accepting them from the user.
34

8.5.2 INTEGRATION TESTING After unit testing, we have to perform integration testing. The goal here is to see if modules can be integrated properly, the emphasis being on testing interfaces between modules. This testing activity can be considered as testing the design and hence the emphasis on testing module interactions. In this project the main system is formed by integrating all the modules. When integrating all the modules I have checked whether the integration effects working of any of the services by giving different combinations of inputs with which the two services run perfectly before Integration. 8.5.3 SYSTEM TESTING Here the entire software system is tested. The reference document for this process is the requirements document, and the goal is to see if software meets its requirements. Here entire HRRP has been tested against requirements of project and it is checked whether all requirements of project have been satisfied or not. 8.5.4 ACCEPTANCE TESTING Acceptance Testing is performed with realistic data of the client to demonstrate that the software is working satisfactorily. Testing here is focused
35

on external behavior of the system; the internal logic of program is not emphasized. Test cases should be selected so that the largest number of attributes of an equivalence class is exercised at once. The testing phase is an important part of software development. It is the process of finding errors and missing operations and also a complete verification to determine whether the objectives are met and the user requirements are satisfied. 8.5.5 WHITE BOX TESTING This is a unit testing method, where a unit will be taken at a time and tested thoroughly at a statement level to find the maximum possible errors. I tested step wise every piece of code, taking care that every statement in the code is executed at least once. The white box testing is also called Glass Box Testing. I have generated a list of test cases, sample data, which is used to check all possible combinations of execution paths through the code at every module level. White-box test focuses on the program control structure. Test cases are derived to ensure that all statement in the program control structure. Test cases are derived to ensure that all statement in the program control structure. Test cases are derived to ensure that all statement in the program has been executed at least once during testing and that all logical conditions have been exercised. Basis path testing, a white box technique, makes use of program graphs (or graph matrices) to derive the set of linearly independent test that will ensure
36

coverage. Condition and data flow testing further exercising degrees of complexity. 8.5.6 BLACK BOX TESTING Probes the programs ability to handle data at the limits of acceptability. This testing method considers a module as a single unit and checks the unit at interface and communication with other modules rather getting into details at statement level. Here the module will be treated as a block that will take some input and generate output. Output for a given set of input combinations are forwarded to other modules. Black-box test are designed to uncover errors functional requirement without regard to the internal workings of a program. Black-box testing techniques focus on the information domain of the software, deriving test cases by partitioning the input and output domain of a program in manner that provides through test coverage. The black-box test is used to demonstrate that software functions are operational, that input is properly produced, and that the integrity of external information are maintained. A black-box test examines some fundamental aspect of a system with little or no regard for the integral logical structure of the software. Graph based testing methods explore the relationship between and behavior of program objects. Equivalence partitioning divides the input classes of data are likely to exercise specific software function. Boundary values analysis
37

8.6 TEST INFORMATION FLOW

A strategy for software testing may also be viewed in the context of the spiral. Unit testing begins at the vortex of the spiral and, concentrates on each unit, component of the software as implemented in source code. Testing progresses moving outward along the spiral to integration testing, where the focus is on designed the construction of the software architecture. Taking another turn outward on spiral, we encounter validation testing, where requirements established as part of software requirements analysis are validated against the software that has been constructed. Finally, we arrive at system testing, where the software and other system elements are tested as a whole. To test computer software, we spiral out along stream lines that broaden the scope of testing with each turn. Considering the process from a procedural point of view, testing within the context of software engineering is actually a series of four steps that are implemented sequentially. The steps are shown in Figure. Initially, tests focus on each component individually, ensuring that it functions properly as unit. Hence, the name is unit testing. Unit testing makes heavy use of white-box testing techniques, exercising specific paths in modules control structure to ensure complete coverage and maximum error detection.

38

39

8.7 SYSTEM SECURITY

There are basically two types of security associated with this system:8.7.1. PHYSICAL SECURITY Damage due to natural causes like earth tremor, flooding, water logging, fire hazards, atmospheric or environmental conditions etc.For overcoming these difficulties the replica of the data are automatically stored at various networks and for environmental conditions Air conditioning environment is created. 8.7.2. DATA SECURITY There are basically two problems associated with data security:1. Data not being available to the authorized person at the time of need. 2. Data becoming available to the unauthorized person. To overcome these difficulties the following access facilities has been provided:i) IDENTIFICATION:Unique Ids for the different users have been provided. ii) AUTHENTICATION:System checks the password under the particular user identification. The computer permits the various resources to the authorized person. iii) AUTHORIZATION:The access control mechanism to prevent unauthorized logging to the system.
40

9. FUTURE SCOPE OF THE PROJECT

This way of advertisement can enhance the market scenario and competition much better. It also is going to decrease the total duration and efforts put in publicity part of a mega mart.

More user friendly for the customers and the publishers.

41

10.BIBLIOGRAPHY
These are the following links which assist me at each and every step in completing this project, without them I was not be able to finish this important project:1. www.scribd.com 2. www.wikipedia.com 3. www.answers.com 4. www.askme.com 5. www.esnips.com 6. www.yatra.com Instead of this useful website, following books also help me: 1. OBJECT ORIENTED PROGRAMMING WITH C++ By:-Sumita Arora 2. OBJECT ORIENTED PROGRAMMING WITH C++ By: - ROBERT LAFORE

42