retail network report

8/12/2019 Retail Network Report

1/29

Appendix IV

Introduction:

Todays consumers are more demanding than ever. Customers have more choices and

purchasing channels than ever before and when they interact with a retailer they want you

to know who they are and what they want. To be competitive in today's demanding

multi-channel retail environment, retailers need their retail management systems

integrated to deliver enhanced customer service across channels while driving growth and

increased revenue.

Our retail management software and solution is an end-to-end suite designed especially

for multi-channel retailers and leverages et!uites "#$ platform for cloud-based

enterprise management. %inking every step of your multi-channel retail enterprise gives

you real-time visibility into your entire retail operation, accessible from anywhere at any

time.

Aim

To build a software for a uni&ue and web based retail network management and

dministration.

Existing System:

The e(isting system of retail management has no proper customer insights, which provide

better options for better operations. )ue to lack of consistency in operations, there will be

no better planning of inventory.

Proposed System:

To overcome the drawbacks of the e(isting system, we have proposed a new system,

which provides customer insights like

*now who is shopping.

Optimi+e erchandising.

void brand and store switching.

t also increases customer satisfaction by adopting best practices by


2/29

Appendix IVChoose right business partners.

Optimi+e financing and cost techni&ue.

se analytics.

dopt the right solution.

Modules and its description:

Core Modules

Purchase

/endor aster tem aster

tem indent

"n&uiry odule0

1uotation odule0

$urchase Order odule0

Stores

tem #eceipts

tem ssues

tem #eturns

Reports

tem indent report

tem en&uiry report

1uotation report

$urchase order details

tem receipt details

tem issue details


3/29

Appendix IV tem return details

!tores details

tem transaction details

CHAPTER 2

LITERATURE SURVEY

A literature review is an evaluative report of studies found in the literature related

to the selected area. It gives a theoretical basis for the research and helps in determining

the nature of the research. A literature review is selecting a limited number of works that

are central to your area rather than trying to collect a large number of works that are not

as closely connected to your topic area. A literature review goes beyond the search of

information and includes the identification and articulation of relationships between the

literature and the field of research provide a context for the research. It describes related

research in the field and shows how the work extends or challenges this, or addresses a

gap in work in the field and also provides supporting evidence for a practical problem orissue which your research is addressing, thereby underlining its significance.

Introduction to ASP.NET

.NET Framework (pronounced dot net ) is a software framework developed

by Microsoft that runs primarily on Microsoft Windows . It includes a large library and

provides language interoperability (each language can use code written in other

languages) across several programming languages . Programs written or .NET Framework

e!ecute in a software environment (as contrasted to hardware environment)" known asthe Common Language Runtime (#$%)" an application virtual machine that provides

services such as security" memory management " and exception handling . The class

library and the #$% together constitute .NET Framework.

&'P.NET is a server-side Web application framework designed or Web development to

produce dynamic Web pages . It was developed by Microsoft to allow programmers to

build dynamic web sites " web applications and web services . It was irst released in

anuary ** with version +.* o the . !" #ramework " and is the successor to

,icroso t-s $ctive %erver &ages (&'P) technology. &'P.NET is built on the Common

Language Runtime (#$%)" allowing programmers to write &'P.NET code using any
http://en.wikipedia.org/wiki/Software_frameworkhttp://en.wikipedia.org/wiki/Software_frameworkhttp://en.wikipedia.org/wiki/Microsofthttp://en.wikipedia.org/wiki/Microsofthttp://en.wikipedia.org/wiki/Microsoft_Windowshttp://en.wikipedia.org/wiki/Framework_Class_Libraryhttp://en.wikipedia.org/wiki/Language_interoperabilityhttp://en.wikipedia.org/wiki/Language_interoperabilityhttp://en.wikipedia.org/wiki/Programming_languagehttp://en.wikipedia.org/wiki/Softwarehttp://en.wikipedia.org/wiki/Softwarehttp://en.wikipedia.org/wiki/Computer_hardwarehttp://en.wikipedia.org/wiki/Common_Language_Runtimehttp://en.wikipedia.org/wiki/Common_Language_Runtimehttp://en.wikipedia.org/wiki/Process_virtual_machinehttp://en.wikipedia.org/wiki/Process_virtual_machinehttp://en.wikipedia.org/wiki/Memory_managementhttp://en.wikipedia.org/wiki/Memory_managementhttp://en.wikipedia.org/wiki/Exception_handlinghttp://en.wikipedia.org/wiki/Server-side_scriptinghttp://en.wikipedia.org/wiki/Web_application_frameworkhttp://en.wikipedia.org/wiki/Web_developmenthttp://en.wikipedia.org/wiki/Dynamic_Web_pageshttp://en.wikipedia.org/wiki/Microsofthttp://en.wikipedia.org/wiki/Programmerhttp://en.wikipedia.org/wiki/Web_sitehttp://en.wikipedia.org/wiki/Web_applicationhttp://en.wikipedia.org/wiki/Web_servicehttp://en.wikipedia.org/wiki/.NET_Frameworkhttp://en.wikipedia.org/wiki/Active_Server_Pageshttp://en.wikipedia.org/wiki/Common_Language_Runtimehttp://en.wikipedia.org/wiki/Common_Language_Runtimehttp://en.wikipedia.org/wiki/Software_frameworkhttp://en.wikipedia.org/wiki/Microsofthttp://en.wikipedia.org/wiki/Microsoft_Windowshttp://en.wikipedia.org/wiki/Framework_Class_Libraryhttp://en.wikipedia.org/wiki/Language_interoperabilityhttp://en.wikipedia.org/wiki/Programming_languagehttp://en.wikipedia.org/wiki/Softwarehttp://en.wikipedia.org/wiki/Computer_hardwarehttp://en.wikipedia.org/wiki/Common_Language_Runtimehttp://en.wikipedia.org/wiki/Process_virtual_machinehttp://en.wikipedia.org/wiki/Memory_managementhttp://en.wikipedia.org/wiki/Exception_handlinghttp://en.wikipedia.org/wiki/Server-side_scriptinghttp://en.wikipedia.org/wiki/Web_application_frameworkhttp://en.wikipedia.org/wiki/Web_developmenthttp://en.wikipedia.org/wiki/Dynamic_Web_pageshttp://en.wikipedia.org/wiki/Microsofthttp://en.wikipedia.org/wiki/Programmerhttp://en.wikipedia.org/wiki/Web_sitehttp://en.wikipedia.org/wiki/Web_applicationhttp://en.wikipedia.org/wiki/Web_servicehttp://en.wikipedia.org/wiki/.NET_Frameworkhttp://en.wikipedia.org/wiki/Active_Server_Pageshttp://en.wikipedia.org/wiki/Common_Language_Runtimehttp://en.wikipedia.org/wiki/Common_Language_Runtime


4/29

Appendix IVsupported . !" language . The &'P.NET %'$& e!tension ramework allows &'P.NET

components to process ' &P messages.

&'P.NET &rchitecture

(ntroduction to M%%)L

,icroso t '/$ 'erver is a relational database management system developed

by Microsoft . &s a database" it is a so tware product whose primary unction is to store and

retrieve data as re0uested by other so tware applications" be it those on the same computer

or those running on another computer across a network (including the Internet). There are at

least a do1en di erent editions o ,icroso t '/$ 'erver aimed at di erent audiences and or

workloads ranging rom small single2machine applications to large Internet2 acing

applications with many concurrent users. Its primary *uery languages are "-%)L and $ %(

%)L .

!!1% !erver rchitecture
http://en.wikipedia.org/wiki/List_of_CLI_languageshttp://en.wikipedia.org/wiki/SOAPhttp://en.wikipedia.org/wiki/Relational_database_management_systemhttp://en.wikipedia.org/wiki/Microsofthttp://en.wikipedia.org/wiki/Microsofthttp://en.wikipedia.org/wiki/Query_languagehttp://en.wikipedia.org/wiki/Transact-SQLhttp://en.wikipedia.org/wiki/SQLhttp://en.wikipedia.org/wiki/SQLhttp://en.wikipedia.org/wiki/List_of_CLI_languageshttp://en.wikipedia.org/wiki/SOAPhttp://en.wikipedia.org/wiki/Relational_database_management_systemhttp://en.wikipedia.org/wiki/Microsofthttp://en.wikipedia.org/wiki/Query_languagehttp://en.wikipedia.org/wiki/Transact-SQLhttp://en.wikipedia.org/wiki/SQLhttp://en.wikipedia.org/wiki/SQL


5/29

Appendix IV

(ntroduction to +"ML

2T %, which stands for 2yperTe(t arkup %anguage, is the predominant

markup language for web pages . 2T % is the basic building-blocks of 3eb$ages. t is

written in the form of 2T % elements consisting of tags , enclosed in angle brackets . The

purpose of a web browser is to read 2T % documents and compose them into visual or

audible web pages. The browser does not display the 2T % tags, but uses the tags to

interpret the content of the page.

2T % elements form the building blocks of all websites. 2T % allows images

and ob4ects to be embedded and can be used to create interactive forms . t provides a

means to create structured documents by denoting structural semantics for te(t such as

headings, paragraphs, lists, links, &uotes and other items. t can embed scripts in

languages such as 5ava!cript which affect the behavior of 2T % 3eb$ages.

2yperTe(t is the method by which you move around on the web 6 by

clicking on special te(t called hyperlinks which bring you to the ne(t page.

The fact that it is hyper 4ust means it is not linear.

arkup is what 2T % tags do to the te(t inside them.
http://en.wikipedia.org/wiki/HyperTexthttp://en.wikipedia.org/wiki/Markup_languagehttp://en.wikipedia.org/wiki/Web_pagehttp://en.wikipedia.org/wiki/HTML_elementhttp://en.wikipedia.org/wiki/Bracket#Angle_brackets_or_chevrons_.E2.9F.A8_.E2.9F.A9http://en.wikipedia.org/wiki/Web_browserhttp://en.wikipedia.org/wiki/HTML_element#Images_and_objectshttp://en.wikipedia.org/wiki/HTML_element#Images_and_objectshttp://en.wikipedia.org/wiki/HTML_element#Formshttp://en.wikipedia.org/wiki/Structured_documenthttp://en.wikipedia.org/wiki/Semantichttp://en.wikipedia.org/wiki/Scripting_languagehttp://en.wikipedia.org/wiki/JavaScripthttp://en.wikipedia.org/wiki/HyperTexthttp://en.wikipedia.org/wiki/Markup_languagehttp://en.wikipedia.org/wiki/Web_pagehttp://en.wikipedia.org/wiki/HTML_elementhttp://en.wikipedia.org/wiki/Bracket#Angle_brackets_or_chevrons_.E2.9F.A8_.E2.9F.A9http://en.wikipedia.org/wiki/Web_browserhttp://en.wikipedia.org/wiki/HTML_element#Images_and_objectshttp://en.wikipedia.org/wiki/HTML_element#Images_and_objectshttp://en.wikipedia.org/wiki/HTML_element#Formshttp://en.wikipedia.org/wiki/Structured_documenthttp://en.wikipedia.org/wiki/Semantichttp://en.wikipedia.org/wiki/Scripting_languagehttp://en.wikipedia.org/wiki/JavaScript


6/29

Appendix IV

SYSTEM REQ IREME!TS A!" A!A#YSIS

nalysis involved a detailed study of the current system, leading to specifications

of a new system. t is a detailed study of various operations performed by a system and

their relationships within and outside the system. )uring analysis, data are collected on

the available files, decision points and transactions handled by the present system.

3.1 FEASIBILITY STUDY

t is both necessary and prudent to evaluate the feasibility of a pro4ect at theearliest possible time. onths or years of effort, thousands and millions of dollars, and

untold professional embarrassment can be averted if an ill-conceived system is

recogni+ed early in the definition phase.

7easibility and risk analysis are related in many ways. f pro4ect risk is great, the

feasibility of producing &uality software is reduced. )uring product engineering,

however, we concentrate our attention on four primary areas of interest. The three

essential considerations are involved they are

Technical 7easibility

"conomical 7easibility

Operational 7easibility

$%&%' Technical (easi)ility

Technical feasibility is the need of hardware and software, which are needed to

implement the proposed system in the organi+ation. Technical re&uirements are to be

fulfilled to make the proposed system work. This should be necessarily predetermined so

as to make the system more competent.

$%&%$ Economical (easi)ility

The "conomical feasibility must satisfy the needs of the technical feasibility and

the operational feasibility. t involves the economic feasibility of developing and

implementing the proposed system.


7/29

Appendix IV$%&%* +perational (easi)ility

The proposed system should use the internet level then the different types of end

users are involved in the system, so it solves the users needs and the organi+ation needs.

nd it supports the all users environment.

SOFTWARE REQUIREMENTS SPECIFICATION

!oftware #e&uirements !pecification 8!#!9 is a re&uirements specification for

a software system . t is a complete description of the behavior of a system to be

developed. t includes a set of use cases that describe all the interactions the users will

have with the software. !#! also contains functional and non-functional re&uirements.

on-functional re&uirements are re&uirements which impose constraints on the design or

implementation.!#! describes the functionality, characteristics and constraints that are

applicable for the application.

$%$So,t-are speci,ication: Target framework0 .net framework :.; and above

Operating system0 3indows >? and above

)atabase0 ! !1% !erver =>>; and above

$rogramming language0 C@

$%* .ard-are speci,ication 0

$rocessor0 $entium dual core and above

# 0 =gb and above

2arddisk 0 A>B and above

3.5 FUNCTIONALITY REQUIREMENTS

The functional re&uirement of the Retail Network System is e(plained via specific

modules0
http://en.wikipedia.org/wiki/Requirements_specificationhttp://en.wikipedia.org/wiki/Requirements_specificationhttp://en.wikipedia.org/wiki/Software_systemhttp://en.wikipedia.org/wiki/Use_casehttp://en.wikipedia.org/wiki/Requirements_specificationhttp://en.wikipedia.org/wiki/Software_systemhttp://en.wikipedia.org/wiki/Use_case


8/29

Appendix IVA. dministrator

=. 3holesaler

:. #etailer

$%/%& A"MI!ISTRAT+R

systems administrator needs a fairly e(tensive knowledge of various computer

operations to be effective. 2e must understand how the mainframe server operates and

know how to maintain the computer system, install software and patches, resolve

problems, maintain data files, monitor the system, and e(ecute systems backup and

recovery. n short, the systems administrator should know how to do nearly everything

the system re&uires for maintenance.

$%/%' 0holesaler

$erson or firm that buys large &uantity of goods from

various producers or vendors , warehouses them, and resells to retailers . 3holesalers who

carry only non-competing goods or lines are called distributors .

$%/%' Retailer

One who sells goods or commodities directly to consumers. These items are purchased

from the manufacturer or wholesaler and sold to the end user at a marked up price.

3.6 NON FUNCTIONALITY REQUIREMENTS

$%1%& Sa,ety Re2uirements

!ome of the safety re&uirements specified by the user are as follows0

The application is designed so that the information is reviewed by user.

The application is designed so that inconsistent data D loss are prevented by

building in redundancy.

The system re&uires granular authori+ation and access control to do systemupdates for both software and routine maintenance.
http://www.businessdictionary.com/definition/person.htmlhttp://www.businessdictionary.com/definition/buy.htmlhttp://www.businessdictionary.com/definition/quantity.htmlhttp://www.businessdictionary.com/definition/goods.htmlhttp://www.businessdictionary.com/definition/producer.htmlhttp://www.businessdictionary.com/definition/vendor.htmlhttp://www.businessdictionary.com/definition/warehouse.htmlhttp://www.businessdictionary.com/definition/retailer.htmlhttp://www.businessdictionary.com/definition/lines.htmlhttp://www.businessdictionary.com/definition/call.htmlhttp://www.businessdictionary.com/definition/distributor.htmlhttp://www.businessdictionary.com/definition/person.htmlhttp://www.businessdictionary.com/definition/buy.htmlhttp://www.businessdictionary.com/definition/quantity.htmlhttp://www.businessdictionary.com/definition/goods.htmlhttp://www.businessdictionary.com/definition/producer.htmlhttp://www.businessdictionary.com/definition/vendor.htmlhttp://www.businessdictionary.com/definition/warehouse.htmlhttp://www.businessdictionary.com/definition/retailer.htmlhttp://www.businessdictionary.com/definition/lines.htmlhttp://www.businessdictionary.com/definition/call.htmlhttp://www.businessdictionary.com/definition/distributor.html


9/29

Appendix IV$%1%' Security Re2uirements

The following are some of the security re&uirements of the user from the

proposed system0

$rovides proper authentication and authori+ation facility for the use of the

system. o e(ternal persons e(cept the administrator, user is allowed to

access the website.

2ave intrusion detection firewall to prevent )O! and #oot access

violations.

$%1%$ A3aila)ility Re2uirements

pplication would be available for =E(F days with an uptime of GG.?;H.

ll pages with assets should load under : secs time in a end users browser.

$%1%* Relia)ility Re2uirements

To have less response time during communication and retrieving the

information.

To provide GGH accuracy.

To update the information only when the data is found to be consistent.

To react appropriately to the errors and e(ceptions.

$%1%/ Maintaina)ility Re2uirements

$roviding suitable interfaces for the creating and maintaining the records.

$roviding a recovery mechanism.

$roviding backup for the e(isting data.

$%1%1 Interopera)ility Re2uirements

!ince #etail etwork !ystem is a web based application, it should be

interoperable with the other systems present in the web. nd since it is a web based

application it is platform independent.

$%1%4 (lexi)ility Re2uirements


10/29

Appendix IVThe product must be fle(ible enough to adapt for any une(pected changes.

Changes is one sub-system should not affect or hinder the working of the whole

system. t should be fle(ible enough to accept new changes in the technology and

changing business environment.

C.APTER I5

SYSTEM "ESI6!

4.1 INTRODUCTION

Design is concerned with identifying software components specifyingrelationships among components. pecifying software structure and providing blue print

for the document phase. !odularity is one of the desirable properties of large systems. It

implies that the system is divided into several parts. In such a manner, the interaction

between parts is minimal clearly specified. Design will explain software components in

detail. "his will help the implementation of the system. !oreover, this will guide the

further changes in the system to satisfy the future re#uirements.

4.2 PRELIMINARY SYSTEM DESIGN

*%'%& "(" 7"ata (lo- "iagram8

)ata flow diagrams illustrate how data is processed by a system in terms of inputs

and outputs. t shows all the data flows from the system to the e(ternal entities. t

graphically represents the flow of data.

There are two types of )7) design0

I 2igh %evel )esign 82%)9

I %ow %evel )esign 8%%)9


11/29

Appendix IV

(EAT RES +( "("9S

A. The )7) shows flow of data, not of control loops and decision are

controlled consideration do not appear on a )7).=. The )7) does not indicate the time factor involved in any process whether

the data flows take place daily, weekly, monthly or yearly.

:. The se&uence of events is not brought out on the )7).

"(" SYM +#S

n the )7), there are four !ymbols

A. s&uare define a source or destination system data

=. n arrow identified data flow. t is the pipeline through which the

information flow

:. circle or a bubble represents a process that transforms

E. ncoming data flow into outgoing data flows

;. n open rectangle is a data store, data at rest or a temporary of data

$rocess that transformation data flow

!ource or )estination of data

)irections

)atabase

C+!STR CTI!6 A "("

!everal rules of thumb are used in drawing )7)s


12/29

Appendix IV$rocess should be named and numbered for an easy reference. "ach name

should be representative of the process.

The direction of flow is top to bottom and from left to right. )ata

traditionally flow from source to the destination although they may flow

back to the source. One way to indicate this is to draw long flow line backto the source. n alternative way is to repeat the source symbol as a

destination. !ince it is used more than once in the )7) it is marked with a

short diagonal.

3hen a process is e(ploded into lower level details, they are numbered.

The names of data stores and destinations are written in capital letters.

$rocess and dataflow names have the first letter of each work capitali+ed.

)7) typically shows the minimum contents of data store. "ach data storeshould contain all the data elements that flow in and out. 1uestionnaires should contain

all the data elements that flow in and out. issing interface redundancies and like is than

accounted for often through interviews.

"ATA ST+RE

A. )ata cannot move directly from one data store to another data store, a

process must move data.=. )ata con not move directly from an outside source to a data store, a

process, which receives, must move data from the source and place the

data into data store.

:. data store has a noun phrase label.

S+ RCE +R SI!;

The origin or destination of data

A. )ata cannot move direly form a source to sink it must be moved by

process

=. source and or sink has a noun phrase land.

"ATA (#+0

A. data flow has only one destination of flow between symbols. t may

flow in both directions between a process and a data store to show a read


13/29

Appendix IV before an update. The later is usually indicated however by two separate

arrows since these happen at different type.

=. 4oin in )7) means that e(actly the same data comes from any of two or

more different processes data store or sink to a common location.

:. data flow cannot go directly back to the same process it leads. Theremust be at least one other process that handles the data flow produce some

other data flow returns the original data into the beginning process

E. data flow to a data store means updates 8 delete or change9

;. data flow from a data store means retrieve or use.


14/29

Appendix IV

"(" (or Admin #ogi n

(igure *%&: "(" ,or Admin #ogin

$holesalerDetails

$ogin

&uthentication

'tore

Process

'tore

Process

%mployeedetails

%mployeeDetails

$holesalerDetails

Invalid

Valid

Valid

Valid

Invalid

Invalid

Valid

Admin

ales'tore

Process

ales

%eport

%eport

&etailerDetails 'tore

Process

&etailerDetails

%eport

Valid

Invalid

%eport

Invalid


15/29

Appendix IV 4.3 DETAILED DESIGN

)etailed design is also called as low-level design. )uring detailed design, the

internal logic of various functionalities in the proposed system is decided. )uring this

phase, further details of the data structures, the table designs and algorithmic design of

each of the functionality is specified. t also involves the entity-relationship diagrams and

the use-case diagrams that further e(plain the data flow in the system. ma4or task of

detailed design is to spell out, in detail, the attributes and methods needed by each class.

The design produces the details that state how a system met the re&uirements identified

during system analysis. t is a graphical tool used to describe and analy+e the movement

of data. The transformation of data from input to output

)etailed )esign is carried out in different phases. The phases are as follows.

)atabase )esign

"ntity-#elationship8"#9 )iagram

nified odeling %anguage 8 %9 )esign

se-Case )iagram

ctivity )iagram

*%$%& Entity


16/29

Appendix IV'ormali(ation is a process in which we eliminate the problem of data redundancy

in the database design and build a data model that supports different functional

re#uirements and alternate database designs.

'ormali(ation is a successive process, which involves the following steps)

All attributes must be single valued. "his is referred to as first normal form. "his

means that the attribute data is not repeated.

An attribute must depend upon its entity*s entire uni#ue ID. "his is referred as

second normal form. !ove the attributes to a table where they depend upon the

primary key. Do not have a table that has attributes that don*t solely depend

upon the key.

'on+uni#ue ID attributes can be dependent upon another non+uni#ue ID

attribute. "his is referred to as third normal form. 3hen normali+ation is complete, each table must have e(actly one primary key,

and the data in the table is dependent solely upon the tables primary key.

(igure *%$: System E


17/29

Appendix IV

(igure *%$: Acti3ity "iagram

SEQ E!CE "IA6RAM

& se0uence diagram is an interaction diagram that shows how processes operate with one

another and in what order. It is a construct o a ,essage 'e0uence #hart . & se0uence

diagram shows ob3ect interactions arranged in time se0uence. It depicts the ob3ects andclasses involved in the scenario and the se0uence o messages e!changed between the

ob3ects needed to carry out the unctionality o the scenario. 'e0uence diagrams are typically

associated with use case reali1ations in the $ogical 4iew o the system under development.

'e0uence diagrams are sometimes called event diagrams" event scenarios

& se0uence diagram shows" as parallel vertical lines ( lifelines )" di erent processes or ob3ects

that live simultaneously" and" as hori1ontal arrows" the messages e!changed between them"

in the order in which they occur. This allows the speci ication o simple runtime scenarios in a

graphical manner.
http://en.wikipedia.org/wiki/Interaction_diagramhttp://en.wikipedia.org/wiki/Interaction_diagramhttp://en.wikipedia.org/wiki/Message_Sequence_Charthttp://en.wikipedia.org/wiki/Message_Sequence_Charthttp://en.wikipedia.org/wiki/Interaction_diagramhttp://en.wikipedia.org/wiki/Message_Sequence_Chart


18/29

Appendix IV

(igure *%*: Acti3ity "iagram


19/29

Appendix IVC.APTER 5

SYSTEM IMP#EME!TATI+!

5.1 INTRODUCTION

!ystem implementation is that stage of development life cycle, when the

theoretically designed system is turned into actual working system. This phase is very

critical so it must be carefully planned and controlled, otherwise it can cause problems.

ll possible constraints must be taken into consideration before implementing the system

because the new system must assure the users about its effective working.

mplementation phase also involves installation of the software and user training.

nstallation details can be provided in the user manual.

/%' SYSTEM M+" #ES

The following modules are designed for the current pro4ect using !$. "T

Presentation #ayer

uilt on 2T %.

Ser3er data)ase #ayer

uilt on !!1% server.

"ata #ayer

uilt on C@ %anguage.

/%$ IMP#EME!TATI+! PR+CE" RE


20/29

Appendix IVmplementation of the pro4ect was done using $rogramming language like C@ and

mark up language 2T % with database server on the 3indows platform. The 7ront end

part was done in 2T % with C!! which was helpful in designing the front-end where the

user can enter the data.

/%$%& Pseudo code

ser #ogin

!tep A0 !tart.

!tep =0 "nter the user ) and password.

!tep :0 !elect login.

!tep E0 Connect a database and prepare !1% &uery.

!tep ;0 "(ecute a !"%"CT &uery and the input user ) is compared with all the

input values of database.

!tep J0 f matches then go to !tep ? else go to !tep F.

!tep F0 ser ) and password does not matches.

!tep ?0 ser d available.

!tep G0 Bo to $rogram page.

!tep A>0 !elect the download link.

!tep AA0 Connect a database and prepare a !1% &uery for download file.

!tep A=0 !elect the path.

!tep A:0 !ave the file.

!tep AE0 )isplay message K)ownload !uccessfulL.

!tep A;0 Bo to 2ome page.

!tep AJ0 !top.


21/29

Appendix IVpdate Pass-ord

!tep A0 !tart.

!tep =0 Bet user d and password.

!tep :0 !elect %ogin.

!tep E0 Connect a database and prepare !1% 1uery.

!tep ;0 "(ecute a !"%"CT &uery and the input user ) is compared with all the

input values of database.

!tep J0 f the ser ) entered by the user is not correct then go to !tep F else goto !tep ?.

!tep F0 )isplay message K3rong serL.

!tep ?0 !elect !ettings.

!tep G0 "nter the old password.

!tep A>0 "nter the new password.

!tep AA0 #e-enter the new password to be updated.

!tep A=0 !elect pdate.

!tep A:0 Connect database $repare an !1% &uery.

!tep AE0 "(ecute an $) T" &uery and the old password is replaced with the

new $assword.

!tep A;0 !tore the new password into the database.

!tep AJ0 )isplay message K ew password is successfully savedL and go to

program page.

!tep AF0 !top.


22/29

Appendix IV

C.APTER 5I

SYSTEM TESTI!6

6.1 INTRODUCTION

Test )esign refers to understanding the sources of test cases, test coverage, how to

develop and document test cases, and how to build and maintain test data. There are =

primary methods by which tests can be designed and they are0

lac= ox Testing 0 lack-bo( test design treats the system as a literal Mblack-

bo(M, so it doesn't e(plicitly use knowledge of the internal structure. t is usually

described as focusing on testing functional re&uirements. !ynonyms for black bo(

include0 behavioral, functional, opa&ue-bo(, and closed-bo(.

0hite ox Testing 0 3hite-bo( test design allows one to peek inside the Mbo(M,

and it focuses specifically on using internal knowledge of the software to guide

the selection of test data. t is used to detect errors by means of e(ecution-orientedtest cases. !ynonyms for white-bo( include0 structural, glass-bo( and clear-bo(.


23/29

Appendix IV3hile black bo( and white bo( are terms that are still in popular use, many people

prefer the terms M ehavioralM and M!tructuralM. ehavioral test design is slightly different

from black-bo( test design because the use of internal knowledge isn't strictly forbidden,

but it's still discouraged. n practice, it hasn't proven useful to use a single test design

method. One has to use a mi(ture of different methods so that they aren't hindered by thelimitations of a particular one. !ome call this MBray-bo(M or MTranslucent-bo(M test

design, but others wish we'd stop talking about bo(es altogether.

1%&%& 6 I Testing

B is the abbreviation for Braphic ser nterface. t is absolutely essential that

any application has to be user-friendly. The end user should be comfortable while using

all the components on screen and the components should also perform their functionality

with utmost clarity. 2ence it becomes very essential to test the B components of any

application. B Testing can refer to 4ust ensuring that the look-and-feel of the

application is acceptable to the user, or it can refer to testing the functionality of each and

every component involved.

The following is a set of guidelines to ensure effective B Testing and can be

used even as a checklist while testing a product D application.

Testing Strategieslack bo( testing should make use of randomly generated inputs 8only a test range

should be specified by the tester9. !ome of them are0

To eliminate any guesswork by the tester as to the methods of the function

)ata outside of the specified input range should be tested to check the robustness

of the program

oundary cases should be tested 8top and bottom of specified range9 to make sure

the highest and lowest allowable inputs produce proper output!tress testing should be performed 8try to overload the program with inputs to see

where it reaches its ma(imum capacity9, especially with real time systems

Crash testing should be performed to see what it takes to bring the system down

Test monitoring tools should be used whenever possible to track which tests have

already been performed and the outputs of these tests to avoid repetition and to aid

in the software maintenance

Other functional testing techni&ues include0 transaction testing, synta( testing,domain testing, logic testing, and state testing.


24/29

Appendix IV7inite state machine models can be used as a guide to design functional tests

fter the development phase, the software needs to be tested for completeness,

correctness, reliability and maintainability. The testing phase involves testing of the

system using various test data. The various strategies used for testing the software are0

I nit Testing

I ntegration Testing

I /alidation Testing

I Output Testing

I ser cceptance Testing

nit Testing

nit testing is used to perform the verification of the smallest units of software

design such as individual forms of the module. ll the validations and conditions are

tested in the module level. Control parts are tested to ensure the information properly

flows in and out of the program. n our system, the modules of the system are tested

separately. nit testing has been successfully handled. The data was given to each

module in all respects and have been found working properly.

Integration Testing

ntegration testing is systematic techni&ue for constructing the program structure,

while conducting test to recover errors associated with interfacing. n this case all the

modules are combined and given the test data. The combined modules work successfully

without any side effect on other programs and everything was found working fine. The

integration testing for proper interaction between the modules was done at developers

level and the results were documented.

5alidation Testing

/alidation succeeds when the software functions in manner that is reasonably

e(pected by the customer. !oftware validation is achieved through a series of black bo(

tests that demonstrates conformity with re&uirement. )eviation or errors discovered at


25/29

Appendix IVthis pro4ect is corrected prior to completion of the pro4ect with the help of the user by

negotiating to establish a method for resolving deficiencies.

/arious validation tests have been applied in this pro4ect. separate function

itself has been written to facilitate easy validation checking. 3henever validation

checking is needed the function will be called. The function mainly checks whether the

data entered is a valid date and so on.

The purpose of defining a separate function is to facilitate the easy understanding

and also to avoid repetition of the same code in different modules. 2ence since validation

checking is needed in all the places where the user enters some input it is easier to call the

function whenever necessary. f any invalid data is entered by the user it prompts the

mistake and re&uest to enter the valid data. Thus the proposed system has been tested by

using validation testing.

+utput Testing

fter performing the validation testing, the ne(t step is output testing of the

proposed system, since no system could be useful if it does not produce the re&uired

output in the specific format. One of the ma4or uses of the application is to produce anumber of reports. Output testing does not result any correction in the system.

ser Acceptance Testing

ser acceptance of the system is a key factor for the success of any system. The

system under consideration is tested for user acceptance by constantly keeping in touch

with prospective system and user at the time of developing and making changes whenever

re&uired.


26/29

Appendix IV

6.2 TEST CASESTa)le 1%&: Test Cases

APPENDIX

S!APS.+TS

TestId

Test Cases Expected Result Actual Result ResultStatus

A %ogin $age

sername,

$assword

/alidation

f it is dmin, go to

the dmin 2ome

page and if it is ser

go to the ser $age.

!uccessfully enter

into their specific

home page

$ass

= f ser ) and

$assword is not

correct.

3arning messageL

$lease enter the

correct passwordL.

The warning

message is displayed

$ass

: Create user $rofile !aved details into

)atabase

)etails saved

!uccessfully

$ass

E "dit user $rofile !aved )etails into

)atabase

!aved )etails and

retrieved

$ass

; Changing $assword !ave the new

password

ew password

successfully saved

$ass

J $roper alignment of

pages

!hould be follow

correct link.

3ill be follow

correct link.

$ass

F f user ) is not

correct

)isplay message

K "nter the correct

)L

K"nter the correct )

and $asswordL is

displayed.

7ail

? f user enter

incorrect password

K"nter correct

passwordL message

should be displayed.

K"nter correct )

and passwordL is

displayed.

7ail


27/29

Appendix IVC.APTER 5III

C+!C# SI+!

The website is developed to manage the retail system in network efficiently.

t helps the user to do manage the inventory easily and fastly.

t saves the time of the user.

C.APTER I>


28/29

Appendix IV( T RE E!.A!CEME!TS

sing online processing of documents.

C.APTER >


29/29

Appendix IV

I #I+6RAP.Y

10.1 BOOKS REFERRED

ooks on operation !anagement)

asics of -peration !anagement) Study Guide

undamentals of -peration !anagement by Jo n T !ent"er

10.2 REFERENCE

http0DDmsdn.microsoft.comDen-usDlibraryDJA?ayhyJ.asp(Dphp.netDlinks.php.

http 0DDwww.tutorialspoint.comDcsharpDcsharpN&uickNguide.htmowthread.php

:>A-%earn-$2$-%inks
http://msdn.microsoft.com/en-us/library/618ayhy6.aspx/php.net/links.phphttp://msdn.microsoft.com/en-us/library/618ayhy6.aspx/php.net/links.phphttp://www.webidsupport.com/forums/showthread.php?301-Learn-PHP-Linkshttp://www.webidsupport.com/forums/showthread.php?301-Learn-PHP-Linkshttp://msdn.microsoft.com/en-us/library/618ayhy6.aspx/php.net/links.phphttp://www.webidsupport.com/forums/showthread.php?301-Learn-PHP-Linkshttp://www.webidsupport.com/forums/showthread.php?301-Learn-PHP-Links

retail network report

Documents