1) INTRODUCTION OF PROJECT

Definitions and Acronyms:

B-TECH establishes an internet presence by the way of using website. Website enhance companys professional image, to offer company information and gi e the public a fa orable impression. !sing website medium educate customers and potential customers, to increase public awareness of our companys name, brand or identity.

Sr. No. " % '

Acronyms #dmin Client (isitor

Description $uper user, manage client data, and manages system They enter by &ogin, purchase product, iew profile They should isit the website

The B-TECH was incorporated as a ser ices pro iding related to computer #)Cs * maintenance based company in the last couple of years +n early years of its de elopment it concentrated on medium * small businesses. +ts early customers were traders, small manufacturing companies, and assorted small business houses. The B-TECH is an information technology consulting, Hardware * $oftware related ser ices and embedded solution pro iding company established in +ndia. B-TECH pro ides ,ualitati e consultancy and ser ice to global clients. B-TECH is powered by "- engineers ha ing a ast e.perience. With a strong focus on your satisfaction and usage of state-of-art technology practices, they are committed to deli er cost-effecti e solutions and ser ices consistently.

MISSION/ 0ro iding intelligent solutions QUALITY/ +s assured with standard business practices, cutting edge technology and right processes. SOLUTION/ 1e eloped in time, in budget and according to arying business needs of our customers.

Purpose
Too often a website lac2s the focus of a clear purpose and confused and clic2 away. By the way of using a website organi3ation should achie e some 2ey factors as under, To strengthen the position in the mar2etplace To strengthen brand identification To de elop a list of ,ualified prospects To gain an increase in sales To e.plain products and ser ices To ma2e product or ser ice information a ailable to distributors To ma2e product or ser ice information a ailable to current customers To pro ide information and customer ser ice To simply establish an +nternet presence To offer lin2s to other rele ant sites To complete in the global mar2etplace isitors are ,uic2ly

 To bring in new clients or customers to our location To consummate a sale To encourage potential customers to contact us by phone, mail or e-mail To e.plain our products and ser ices To ser e the needs of current and future clients

stimated Time Duration

Sr. No. Tas! Name & ' ( ) * + #nalysis 1esign Coding Testing +mplementation 1ocumentation

Start %456%5%6"" "756'5%6"" 6-5685%6"" %-5685%6"" ""5645%6"" %'5645%6""

"inis# "-56'5%6"" 645685%6"" %45685%6"" "65645%6"" %%5645%6"" '"5645%6""

Duration$In Days% %6 %6 %6 "4 "% 9

2) OBJECTIVES
There are some important ob:ecti es, to fulfill them idea of website generation is best phenomenon. Those ob:ecti es are as under. 0ro ide ser ices. $ell a product. 0resent information on a topic. )a2e a new offers announcement.

 +nform people about status. Create a forum that addresses a certain issues. 1eli er announcement on a particular sub:ect. 0ro ides better ser ice for customer. $upport communication between company, customer, and affiliate companies. 0ro ides 1atabase that able to generate report for the company. Capable of promoting the companys business. ;educe e.penses and increase companys producti ity. $upport the companys financial reporting.

3) PROBLEM STATEMENT
Pro,-em areas and need for t#e ne. system
<ur company B-TECH deals with computer sale and maintenance. Current software is good for 2eeping trac2 of sales, #)C and other details of company. But now company wants to e.pand it and ma2e a website so that the users can 2now about the company and purchase products online. !sers can get 2nowledge about products, their configuration and price by using the website so this can sa e their time. B-TECH can post the :ob re,uirements on the site and get the resumes. =ow for them it is necessary to de elop one web-based system which can ta2e care of all these modules.

4) REQUIREMENT ANALYSIS, SRS (LOGICAL DFD &UML), DATA DICTIONARY

List of Modu-e
&% Admin: #dmin should manage client information> they should also iew and print the reports. #dmin is super user they are owner of the organi3ation.

'% /-ient: Client are the customers of the proprietor, they are medium scale, small scale and indi iduals. Clients are enter the website by the way of login function, they can iew its profile, purchase product, and they can also wor2 some other tas2s. (% 0isitor: (isitors are the non-member, non-client persons. They are post feedbac2 us, and iew :ob status, apply online, and iew some basic information )% Product: 0roducts are displayed in website and they are some price tags, model number, description, etc. The client should purchase the product by the way of using the add to cart function.

"unctiona- 1e2uirement of ne. system

This system will be used in )odules which are #dministrator, Client, 0roduct, (isitors. #s all of these ha e different re,uirements the modules are designed to meet their needs and a oid any type of confusion. The !ses of all )odules ha e been described below. ?"@ #dministrator can do the following functions. #dd * Edit * 1elete Client information (iew the Client data (iew the 0urchase data (iew the Auotation re,uest data (iew the +n,uiry data (iew the Beedbac2 data (iew the Candidates recei ed resumes 0rint the Client report 0rint the Auotation report 0rint the 0urchase report Change password ?%@ Clients can do the following functions (iew its profile data (isit the product category 0urchase product by add to cart function 0ost Beedbac2 Auotation re,uest post in,uiry re,uest Change password ?'@ (isitors can do the following functions (isit the product category

 0ost Beedbac2 0ost in,uiry re,uest $earch the :ob acancy for us 0ost resume

Non3"unctiona- 1e2uirement
!ser +nterface ;e,uirements &ogin C#dmin, ClientD Borgot password Change password 0roduct category #dd to cart purchase function ;egistration form +n,uiry form Auotation re,uest Beedbac2 form Eob a ailable in B-TECH, #pply online #dmin should manage client details #dmin should iew and print ;eports

1e2uirement Ana-ysis
;e,uirements analysis, in web de elopment, is a term used to describe all the tas2s that go into the instigation, analy3ing and definition of a new or altered computer system. ;e,uirements analysis is an important part of the software engineering process> whereby business analysts or software de elopers identify the needs or re,uirements of a client> ha ing identified these re,uirements they are then in a position to design a solution.

$uccessfully completing a Fre,uirements analysisG tas2 is a challenge. +n the first place, it is not easy to identify all the sta2eholders, gi e them all an appropriate form of input, and document all their input in a clear and concise format. #nd there are constraints. The re,uirements engineer is e.pected to determine whether or not the new system is/ Beasible $chedulable #ffordable &egal Ethical +n the rush of enthusiasm associated with a new pro:ect, there is always a temptation to downplay the importance of re,uirements analysis. Howe er, studies of pre ious pro:ects re eal that costs and technical ris2s can be reduced through rigorous and thorough up-front re,uirements engineering.

So-utions
<ne of the solutions to this problem has been recogni3ing that re,uirements analysis is a specialist field best carried out by e.perts, i.e. business or system analysts, who could bridge the gap between the business and +T C+nformation TechnologyD worlds. While this approach has helped, it has pro ed difficult to find staff that possesses e,ually good people and technical s2ills. +n addition, the techni,ues used to analy3e re,uirements ha e not pro ed sufficiently effecti e.

"easi,i-ity Ana-ysis
Three types of pro:ect feasibility ha e been considered/

 <perational Beasibility Technical Beasibility Binancial * Economical Beasibility Operationa- "easi,i-ity: The following factors suffice for considering the gi en pro:ect as operational Beasible. $ufficient support from the user. !tili3ing the software li2e multiuser, disconnected database, user-friendly interface, accuracy in users in isual identity, and complete automation will ma2e the system more useful to the users. Tec#nica- "easi,i-ity: The following factors plenty for considering the gi en pro:ect as Technically Beasibility/ The system is de eloped in #$0.=ET framewor2, and hence we can get technical assistance and implementation from #$0.=ET documentation which is easily a ailable. #s the company is ha ing 0entium +( processor, using #$0.=ET with CH, )I$A& and connected all the computer of the organi3ation with &#=, to de elop the system is technically feasible. "inancia- and conomic "easi,i-ity: The following factors plenty for considering the gi en pro:ect as "inancia--y "easi,-e The system re,uires :ust basic hardware and software tools no more

in estments are re,uired. E.isting computers will be utili3ed for the proposed system> additional e.penditure will not be incurred. The fully computeri3ed system will reduce the man-hours, manual wor2 of calculations, 2eeping records and maintain them and other o erhead by simplifying day to acti ities. Socia- feasi,i-ity: The introduction of the system no doubt disturbs the wor2ing style of the company, the organi3ation unity remains intact and mail interaction with the users will 2eep organi3ation healthy. This system is somewhat challenging wor2 for team, so team interaction and communication is important. /onc-usion: Brom this study of all the feasibility, this system is feasible in all the aspects and will help the organi3ation for smooth wor2ing and satisfy all the need of the organi3ation.

1IS4 ANALYISIS AND MANA5 M NT

1IS4 ASS SSM NT: ;is2 assessment is an acti ity that must be under ta2en during pro:ect planning. This in ol es identifying the ris2s * analy3ing them. The ma:or planning acti ity in ris2 management is assessment and conse,uent planning for ris2 control. +n addition, identifying a ris2 on the early basis can pro ide a lot of time to the management in order to handle the ris2s efficiently * effecti ely. The software ris2 can be broadly di ided into three categories, they are

 Cost ;is2 0erformance ;is2 $chedule ;is2 Cost ris2 is the degree of uncertainty associated with budget and outlay for the pro:ect and its impact on the pro:ect. 0erformance ris2 is the possibility that the system will be unable to deli er all or some of the anticipated benefits or will not perform according to the re,uirements. $chedule ris2 is a degree of uncertainty associated with a pro:ect schedule or ability of the pro:ect to achie e the specified milestones.

1IS4 /ONT1OL: ;is2 control comprises acti e measures that are ta2en by pro:ect management to minimi3e the impact to the ris2. +t starts with ris2 management planning. 0lans are de eloped for each identified ris2 that needs to be controlled. The arious ways to specify how to deal with a ris2 are/

1is! A6oidance: +t entails ta2ing actions that will a oid the ris2 all together.

1is! 1eduction: +f the ris2 cant be a oided, perhaps the probability of ris2 materiali3ing can be reduced. 1is! 1eso-ution: The actual elimination or reduction is done in this step. The prototyping is done in ris2 resolution step and necessary information is to be obtained to reduce the ris2.

1is! Monitorin7: +t is acti ity of monitoring the status of arious ris2 and their control acti ities. While monitoring the ris2, reassessments might need to be performed if real

situation differs subse,uently from the situation predicted earlier based on assessment and planning.

Data "-o. Dia7ram

# data-flow diagram C1B1D is a graphical representation of the FflowG of data through an information system. 1B1s can also be used for the isuali3ation of data processing. <n a 1B1, data items flow from an e.ternal data source or an internal data store or an e.ternal data sin2, ia an internal process. # 1B1 pro ides no information about the timing of processes, or about whether processes will operate in se,uence or in parallel. 1ata flow diagram are directed graphs in which the nodes specify processing acti ities and the arcs specify data items transmitted between processing nodes. The system designer ma2es a conte.t le el 1B1 or &e el 6, which shows the FinteractionG between Fthe systemG and Fthe system en ironmentG. The system is Fdecomposed in lower-le el 1B1G into a set of Fprocess, data stores, and the data flows between these processes and data storesG. Each process is then decomposed into an Fe en-lowerle el diagram containing its sub processesG. This approach Fthen continues on the subse,uent sub processesG, until a necessary and sufficient le el of detail is reached which is called the primiti e process. These are different notations to draw data-flow diagrams, defining different flow, and e.ternal entities. isual representations for processes, data stores, data

/ONT 8T L 0 L D"D:

L 0 L 9 1O D"D:

?0.T.<.@

L 0 L ON D"D: &.& L 0 L D"D

'.& L 0 L D"D

(.& L 0 L D"D

?0.T.< .@

+.& L 0 L D"D

?0.T.<.@

L 0 L T:O D"D:

+.&.& L 0 L D"D

?0.T.<. @

ntity 1e-ations#ip Dia7ram

#n E;1 is a model that identifies the concepts or entities that e.ist in a system and the relationships between those entities. #n E;1 is often used as a way to isuali3e a relational database. Each entity represents a database table, and the relationship lines represent the 2eys in one table that point to specific records in related tables. E;1s may also be more abstract, not necessarily capturing e ery table needed within a database, but ser ing to diagram the ma:or concepts and relationships.

DATA DI/TIONA1Y List of Ta,-es

#pply <nline Table Client Table Beedbac2 Table +n,uiry Table 0roduct Table

 0urchase Table Auotation Table # data dictionary or metadata repository is a Fcentrali3ed repository of information about data such as meaning, relationships to other data, origin, usage, and format.G The term may ha e one of se eral closely related meanings pertaining to databases and database management systems/ # document describing a database or collection of databases #n integral component of a 1B)$ that is re,uired to determine its structure # piece of middleware that e.tends or supplants the nati e data dictionary of a 1B)$ # data dictionary is a collection of descriptions of the data ob:ects or items in a data model for the benefit of programmers and others who need to refer to them. # first step in analy3ing, a system of ob:ects with which users interact is to identify each ob:ect and its relationship to other ob:ects. This process is called data modeling and results in a picture of ob:ect relationships.

Use /ase Dia7ram for 0isitors

?0.T.<.@

System f-o. dia7ram

?0.T.<.@

Acti6ity dia7ram for c-ient

;ard.are < Soft.are 1e2uirement

The term specification means Fdifferent things to different peopleG. +t includes analysis <f data describing the system to determine how well it is performing, what re,uirements must be met, and strategies for fulfilling them.

 ;ard.are 1e2uirements C0! / 0entium 8 J ".K LH3 or faster Hard dis2 / 8. LB or abo e ;#) / " LB <perating $ystem / )icrosoft Windows M0 C;ecommendedD

Soft.are 1e2uirements : +nternet E.plorer C;ecommendedD )icrosoft .=et Bramewor2 '.4 )icrosoft $A& $er er %664

9) TESTING PROCEDURES
Testing has a dual function> it is used to establish the presence of defects in the program and it is also used to help :udge whether or not the program is usable in practice. Testing is used for alidation and erification, which ensures that the Web0ortal conforms to its specification and meets the need of the Company. The testing is done by our +n-house employees that act as no ice users and test the application with all possible ways to find the bugs and error as well as chec2 alidation.

T STIN5 PLANS
The purpose of test plan is to ser e as the Test #pproach for the F0lanning 1epartment )oduleG. The Test 0lan aims/ To define o er all scope of the testing. To identify the test items. To define the different testing approaches that will be followed during the testing phase. To identify the different deli erables of the testing.

To detail the acti ities, dependencies and effort re,uired to conduct the Testing. To define arious criteria need to conduct the test.

T#e Testin7 process We tested the website process acti ities such as 1esign, +mplementation and ;e,uirement Engineering. #s design errors are costlier to repair, once, the system has started to operate it is therefore ,uite ob ious to repair them all at the initial stage of the system.

.
Unit testing

Module testing

Sub system testing System testing Acceptance testing

Testing 0rocess Chart 1e2uirements Tracea,i-ity #s most interested portion in the system is system meeting its re,uirements therefore testing should be planned so that all re,uirements are indi idually tested, we chec2ed the output of certain combination of inputs, which gi es desirable output or not. $trictly going along our re,uirements specifications ga e us the path to get desirable result for system users.

 Tested Items <ur test items were li2e, alidation of each and e ery field when user enters the data. The user is not allowed to enter incorrect data and also he is not allowed to lea e the te.t bo.es blan2. The mandatory fields which were the necessary fields were tested to contain data and not blan2. #lso places where only numeric or alphabetic characters were re,uired testing was done to see that no other data other than specific input was entered. Testin7 sc#edu-e We ha e tested each module bac2 to bac2 so that errors and omissions can be found as early as possible. <nce the system has been de eloped fully we tested it on other machines by deploying it on arious machines. 5enera- P-an for Testin7 ". Company )anagement $ystem Corporate Website is tested using Bottom-!p testing strategy. %. Testing of form pages and interfaces while input and output design. '. )odule wise testing C#lso sub module wise testingD while code de elopment. 8. +ntegration testing of system when integration of indi idual modules was done. 4. 0lanned top-down approach for integration testing. -. $ecurity Testing and !ser &e el Testing

T STIN5 ST1AT 5Y
The wor2flow for testing is gi en by/

$tart !nit Testing =<

$uccess IE$ +ntegration Testing End

=<

$uccess IE$

$ystem Testing =<

$ign <ff IE$ $uccess

=<

$uccess

IE$

!ser #cceptance Testing

". # strategy for website testing integrates website test case design method into a well-planned series of steps that result in the successful construction of the website. The strategy pro ides the roadmap that describes the steps to be conducted as a part of testing, then these steps are planed and then underta2en, and how much effort, time and resource will be re,uired. %. Bottom up testing in ol es integrating and testing the modules to the lower le els in the hierarchy, and then wor2ing up hierarchy of modules until the final module is tested. '. Bottom up testing strategy shows how actual testing is to be done with whole system but it does not show any detail about each module testing. 8. Bor each module testing we ha e decided to test each lower le el module with white bo. testing strategy. 4. When all modules were tested successfully then we mo ed one step up and continued with white bo. testing strategy. 6. When all modules were tested successfully then we integrated those modules and tried to test integrated system using blac2 bo. testing strategy.

T STIN5 M T;ODS

 Unit testin7 !nit testing focuses erification effort on the smallest unit of website design, the website component or module. +n this type of testing the indi idual modules were tested and erified whether accurate output was made a ailable or not. The modules were tested indi idually as they could result into faster responses then when they were integrated. Inte7ration Testin7 When the unit testing was o er, all the modules were integrated one by one and tested as a whole. +t might be possible that all modules may wor2 indi idually, but they may not wor2 when put together. 1ata can be lost across the interface, one module can ha e an ad erse affect on the other or sub functions of another, when combined may not produce desired ma:or function, indi idually acceptable imprecision may be magnified to unacceptable le el> global data structure can present problem. $o any system has to be tested this way so that the final output is the desired one. #lso the common functions throughout the system were ta2en and formed into a class so that they could be accessed from the same place without creating any ambiguities. 0a-idation Testin7 #fter the integration testing software is completely assembled as a pac2age, interfacing errors ha e been unco ered and corrected, alidation testing begins. (alidation testing can be defined in many ways but a simple definition is that a alidation succeeds when the website functions in a manner that can be reasonably accepted by the users. System testin7 #ny website is only one element of a larger internet based system. !ltimately website is incorporated with other system elements li2e hardware, people, information and a series of system integration and alidation tests are conducted. $ystem testing is

actually a series of different test whose primary purpose is to fully e.ercise the internet based system. # necessary chec2 to be performed was that of the new system being accepted by the older windows application. The data is not being misplaced when both the systems e.ist. Stora7e Testin7 The database of the system has to be stored on the hard dis2. $o the storage capacity of the hard dis2 should be enough to store all the data re,uired for the efficient running of the system.

/onfi7uration 1e6ie. The intent of the re iew is to ensure that all elements of the software configuration ha e been properly de eloped are catalogued, and ha e the necessary detail to bolster the support phase of the software life cycle. A-p#a and =eta Testin7 # client conducts the #lpha Test at the de elopers site. The software is used in a natural setting with the de eloper Floo2ing o er the shoulderG of the user and recording errors and usage problems. #lpha tests are conducted in a controlled en ironment. The Beta test is conducted at one more customer sites by the end user of the software. !nli2e #lpha Testing, the de eloper is generally not present. Therefore, the Beta test is a F&i eG application of the software in an en ironment that cannot be controlled by the de eloper. Performance Testin7 0erformance tasting is designed to test the runtime performance of the system within the conte.t of the system. These tests were performed at module le el as well as a system le el. +ndi idual modules were tested for re,uired performance. But the true performance of the system can be ascertained only when all the modules are fully integrated.

 /ondition Testin7 Condition testing is a test case design method that e.ercises the logical conditions contained in a program module. +f the condition is incorrect, then at least one component of the condition is incorrect. +t may include/ Boolean <perator Error Boolean (ariable Error Boolean 0arenthesis Error ;ational <perator Error #rithmetic E.pression Error

5UI Testin7 +n the system, standard tests for L!+s ha e been performed, which are as follows/ Testing the windows control for its re,uired position and si3e. The position and related labels for all data controls were chec2ed. =ame of the window. #ll menu functions and sub-functions were erified for correctness. Te.t typeface, si3e and format used throughout the system were chec2ed for uniformity. (alidation for all inputs was done. +ntelligible data input messages are shown properly. Each menu function was tested, whether it in o2es the corresponding functionality properly. 0ull down controls was erified for proper functionality, for e.g. the combo bo. control facilities the selection of items fills in. (arious action buttons were also chec2ed for proper toggle, depending on operation performed.

#ll the input controls were chec2ed for corresponding domain of inputs allowed. #ll re,uired fields arent left blan2 * Lrouping info is displayed appropriately.

1 ) TESTING REPORTS
Purpose
The purpose of this application is to reduce the o erall o erhead in paper wor2 and all the records are maintained such that the user as well as administrator can easily segment them into desired properties so it is easy for any no ice user to ha e access to the application #nother purpose is to ma2e record of papers in database so that it can be referred in future.

1e2uired Input < >pected 1esu-t

E.ample/ Test cases of login module Test /ase Tit-e Purpose of test Test3data &ogin to the system Enabling a user to login to the system !sername / admin 0assword/NNNNN Steps $elect user user type/admin or user Enter a username and password Clic2 on the login and password 1atabase is chec2ed to see if the username5password e.ists. +f it e.ists the )ain )enu page opens depending on the user &ogged +n.

>pected 1esu-t

Else an error message is displayed. The )ain )enu page is loaded depending on the !ser logged in.

Notes < Questions

The username field should not e.ceed the preset length. !sername and password fields cannot special characters and could not be blan2. Either #dmin or user needs to be selected.

Test /ase Tit-e Purpose of test Test3data

Entering 1ata during ;egistration 1ata enters successfully or not =ame, Lender, !serid, 0assword,

;etype 0assword, #ddress, City, $tate, 0in code, Contact no. , Email. Steps Enter alues for all listed abo e Clic2 on the submit button. Chec2 the alidations. Chec2 both passwords are same or not. 1atabase is chec2ed after submit button whether the new data are entered or not. #fter complete entering of data and after pressing submit button, intended page must open. >pected 1esu-t Notes < Questions Else an error message is displayed. The Home 0age is loaded. !ser should meet all alidations and

also enter alid email address.

12) FUTURE EN!ANCEMENT

We can include payment process which can ma2e real-time payments. ". Credit card processing, internet ban2ing can also be included. %. +f any unseen error occurs then the page is redirected to a custom page. This should be identified and be 2nown to the administrator for further assistance. This is pending to be done. '. <nline Help for registration and product module is yet to be done 8. +nteraction with clients can be done through e-mails.

13) LIMITATIONS
". <nly registered users CclientsD can purchase the products. %. +n resume submit module, we accept only user input. ;esume upload facility is not there. '. +n forgot password page, we display password to the user. +t is not being sent in e-mail.

14) CONCLUSION
=o !ser, =o $oftware E ery pro:ect wor2, doesnt matter Website 1e elopment or any other pro:ect, could not be the result of sole effort> e en though, de eloper team consists four members. We thin2 success of any pro:ect doesnt depend only on better web de elopment s2ills, but also, 3eal to listen and help the users. <nly user interaction at de elopment phase can gi e you an idea to fulfill their re,uirements. We e.perienced that we ma2e the website for users and not for the fame of being a better programmer or web de eloper. !ltimately, users appraise your efforts not your peers. The loo2 and feel of the pro:ect was de eloped after regular updating from the #dministrator and thus in ol ed a lot of time and effort.

1") BIBLIOGRAP!Y
4. B&#CO B<<O -. #$0.=ET W+TH CH. 7. #$0.=ET W+TH (B.=ET. K. 0;<L;#))+=L += #$0.=ET. 9. #1(#=CE1 0;<L;#))+=L += #$0.=ET.