CONTENTS Phase 1 Project Analysis and Planning 1.1. Study of the Problem 1.2. Project Scoe 1.!. Objecti"es Phase 2 Cost Estimation Phase ! #odeling the $e%uirements !.1. #odule &escrition !.1.1. 'ogin !.1.2. Product &etails !.1.!. Add Ne( Products !.1.). *dating The +uantity !.2. *#' &iagram !.2.1. *se case &iagram !.2.2. Class &iagram !.2.!. Se%uence &iagram !.2.). Collaboration &iagram Phase ) Configuration #anagement ).1. S,- $e%uirements ).2. .,- $e%uirements ).!. Tools ).). Soft(are &e"eloment ).).1. /orm Creation ).).2. Scrit Phase 0 Soft(are Testing 0.1. Prearing Test Plan 0.2. Perform 1alidation Testing 0.!. 1alidation Test Criteria 0.). Co"erage Analysis 0.0. #emory 'ea2s 09CSA10
Synopsis This is a small scale project for Online shopping system.The basic idea is that customers can buy products using online. It consists of product details, security system, status and exits. The administrator can enter the name and password and generate the report and can perform operations like add , search, delete the products in the database. The Online Shopping system enables endors to set up online shops, customers to browse through the shops, and a system administrator to approe and reject re!uests for new shops and maintain lists of shop categories."lso on the agenda is designing an online shopping site to manage the items in the shop and also help customers purchase them online without haing to isit the shop physically.Our online shopping mall will use the internet as the sole method for selling goods to its consumers. Shopping will be highly personali#ed and the mall will proide lower prices than most competitors. 09CSA10 Phase 1 Project Analysis and Planning 1.1. Study of the Problem The $urrent shopping System is critical to set up online shops, customers to browse through the shops, and a system administrator to approe and reject re!uests for new shops and maintain lists of shop categories. This is a small scale project for Online shopping System. The basic idea is that the candidates can buy product from anywhere during any time by using their card number and password proided to them. The database will maintain the product details information. $ustomer can iew their product details using the card details. This Online shopping system inoles with two types of users. CUSTOME A!M"#"STATO $%STO&'( (O)'* The customers can login+logout the System. ,e+She can iew his+her product details and buy their product. The customer can just iew the information whereas he+she could not make changes in the database. A!M"#"STATO O$E% The administrator plays a ital role in the Online shopping system. The administrator controls the entire database. The report of the product is generated by the administrator itself. The main role of the administrator is to safeguard the database and can add+delete the products from the database. 1.&. Pro'e(t S(ope The supplementary specification applies to online shopping system. This specification defines the non-functional re!uirement of the system such as* Functionality: Since it stand alone application, one or more user may use it at a time. Usability: !es)top interf*(e +indo,s 9-.&000./P.0 09CSA10 Reliability: The system is aailable during online time only . Performance: The performance depends on hardware specification 1.1. Ob'e(ti2es The purpose of this document is to define the re!uirements of Online shopping system. This supplementary specification lists the re!uirements that are not readily captured in the use case model. Supplementary specification and the use case model capture a complete set of re!uirement of the system. Phase 2 Cost Estimation "n estimate is a prediction based upon probabilistic assessment. It is the responsibility of the project manager to make accurate estimations of effort and cost. This is particularly true for projects subject to competitie bidding where a bid too high compared with competitors would result in loosing the contract or a bid too low could result in a loss to the organi#ation. This does not mean that internal projects are unimportant. .rom a project leaders estimate the management often decide whether to proceed with the project. Industry has a need for accurate estimates of effort and si#e at a ery early stage in a project. ,oweer, when software cost estimates are done early in the software deelopment process the estimate can be based on wrong or incomplete re!uirements. " software cost estimate process is the set of techni!ues and procedures that organi#ations use to arrie at an estimate. "n important aspect of software projects is to know the cost. The major contributing factor is effort. +hy SCE is diffi(ult *nd error prone 3 Software cost estimation re!uires a significant amount of effort to perform it correctly. S$' is often done hurriedly, without an appreciation for the effort re!uired. /ou need experience at deeloping estimates, especially for large projects. ,uman bias i.e. "n 'stimator is likely to consider how long a certain portion of the system would take, and then to merely extrapolate this estimate to the rest of the system, ignoring the non-linear aspects of software deelopment. 09CSA10 The (*uses of poor *nd in*((ur*te estim*tion 0ew software projects are nearly always different form the last. Software practitioners don1t collect enough information about past projects. 'stimates are forced to match the resources aailable. &.1. Cost *nd Pri(ing Our project is of high range and is highly efficient which can satisfy the shopping calculation for almost all software companies. The chances of error occurrence is ery limited and so our costs around (s 23, 33,3334app5. " team of 22 members is re!uired for completing the task. It takes a time span of 6 weeks to shape the project. There are no specific enironmental constraints. Phase ! #odeling the $e%uirements 1.1. Module !es(ription 3.1.1. Login It is the login session for the "dministrator, customer and 'xit. 3.1.2. Product Details It is used to iew the product details from the database. 3.1.3. Add Ne Products It is used to add a product into the database and it includes searching a product details and remoing a product from database. 3.1.!. U"dating #$e %uantity It is used to update the product details from the database. 09CSA10 1.&. UM$ !i*gr*m 3.2.1. Use case Diagram %se $ase diagrams show the arious actiities the users can perform on the system. The System is something that performs a function. They model the dynamic aspects of the system. It proides a users perspectie of the system. Actor: "n actor is a user of the system playing a particular role. Use case: %se case is a particular actiity a user can do on the system. Relations$i": (elationships are simply illustrated with a line connecting actors to use cases. admin l ogi n customer add item i tems di spl ayed purchase 3.2.2. &lass Diagram " class diagram describes the types of objects in the system and the arious kinds of static relationships that exist among them.i.e.," graphical representation of a static iew on declaratie static elements. " class is the description of a set of objects haing similar attributes, operations, relationships and behaior. 09CSA10 adminis name : variant new age : variant city : variant new add items() custom name : variant new age : variant address : variant new city : variant new view() purchase item name : variant new itm no : variant quantity : variant cost per item : variant total cost : variant view() login user name : variant new password : variant new add items() items to display name : variant new itm no : variant manuf date : variant exp date : variant purchase() add item item name : variant new item no : variant quantity : variant view() 3.2.3. 'e(uence Diagram " se!uence diagram in %nified &odeling )anguage 4%&)5 is a kind of interaction diagram that shows how processes operate with one another and in what order. It is a construct of a &essage Se!uence $hart. Se!uence diagrams are sometimes called eent diagrams, eent scenarios, and timing diagrams. administrator customer add item view item purchase adding the item viewing the item to purchase purchasing updating the items to customer purchasing again 3.2.!. &ollaboration Diagram " $ollaboration diagram is ery similar to a Se!uence diagram in the purpose it achiees7 in other words, it shows the dynamic interaction of the objects in a system. " distinguishing feature of a $ollaboration diagram is that it shows the objects and their association with other objects in the system apart from how they interact with each other. The association between objects is not represented in a 09CSA10 Se!uence diagram. " $ollaboration diagram is easily represented by modeling objects in a system and representing the associations between the objects as links. The interaction between the objects is denoted by arrows. To identify the se!uence of inocation of these objects, a number is placed next to each of these arrows. administrat or customer add item view item purchase 5: purchasing again 1: add the item 2: viewing the item to purchase 3: purchasing 4: updating the items to customer Phase ) Configuration #anagement $onfiguration management is also used in software deelopment, where it is called %nified $onfiguration &anagement 4%$&5. %sing %$&, deelopers can keep track of the source code, documentation, problems, changes re!uested, and changes made. "n adantage of a configuration management application is that the entire collection of systems can be reiewed to make sure any changes made to one system do not adersely affect any of the other systems 4.1. S.+ e5uirements OS* 8indows $*ngu*ge* 9isual :asic 4.&. 6.+ e5uirements Intel ;II ;rocessor with 633 &,# speed. <= &: ("& 23&: ,ard disk space 09CSA10 4.1. Tools !esign Tool* (ational (ose suite 4.4. Soft,*re !e2elopment !.!.1. Form &reation Form1: Form2: 09CSA10 Form3: Form!: 09CSA10 Form): Form*: 09CSA10 !.!.2. 'cri"t Coding for form1 7ME#U8% ;riate Sub $ommand2>$lick45 .orm?.Show 'nd Sub ;riate Sub $ommand?>$lick45 .orm6.Show 'nd Sub Coding for form& 7CUSTOME PUC6ASE8% @im db "s @atabase @im rs "s (ecordset ;riate Sub $ommand2>$lick45 TextA.Text B TextC.Text 'nd Sub ;riate Sub $ommand?>$lick45 If 4Text<.Text B DD5 Then &sg:ox D'0T'( T,' E%"0TIT/D 'lse TextC.Text B 49al4TextC.Text5 - 9al4Text<.Text55 @ata2.(ecordset.'dit @ata2.(ecordset.%pdate TextA.Text B 49al4Text=.Text5 F 9al4Text<.Text55 &sg:ox DT("0S"$TIO0 S%$''SS.%).. ;"/ TO @'")'(D 'nd If 'nd Sub ;riate Sub $ommand6>$lick45 rs.&oe.irst Text2.Text B rs435 Text?.Text B rs425 Text6.Text B rs4?5 Text=.Text B rs465 TextC.Text B rs4=5 'nd Sub ;riate Sub $ommand=>$lick45 rs.&oe;reious Text2.Text B rs435 Text?.Text B rs425 Text6.Text B rs4?5 Text=.Text B rs465 TextC.Text B rs4=5 'nd Sub 09CSA10 ;riate Sub $ommandC>$lick45 rs.&oe0ext Text2.Text B rs435 Text?.Text B rs425 Text6.Text B rs4?5 Text=.Text B rs465 TextC.Text B rs4=5 'nd Sub ;riate Sub $ommand<>$lick45 rs.&oe)ast Text2.Text B rs435 Text?.Text B rs425 Text6.Text B rs4?5 Text=.Text B rs465 TextC.Text B rs4=5 'nd Sub ;riate Sub .orm>)oad45 Set db B Open@atabase4DG*H:II S,O;.&@:D5 Set rs B db.Open(ecordset4DS,O;D5 Text2.Text B D D Text?.Text B D D Text6.Text B D D Text=.Text B D D TextC.Text B D D Text<.Text B D D 'nd Sub ;riate Sub )O>$lick45 .orm2.Show 'nd Sub Coding for form1 7A!M"#"STATO $O9"#8% ;riate Sub $ommand2>$lick45 If Text2.Text B DbhuaD "nd Text?.Text B D2?6D Then &e.,ide Text2.Text B DD Text?.Text B DD .orm=.9isible B True 'lse &sg:ox Dinalid username and passwordD Text2.Text B DD Text?.Text B DD Text2.Set.ocus 'nd If 'nd Sub ;riate Sub $ommand?>$lick45 'nd 'nd Sub 09CSA10 Coding for form4 7A!M"# C6EC:8% ;riate Sub $ommand2>$lick45 .ormC.Show 'nd Sub ;riate Sub $ommand?>$lick45 .orm2.Show 'nd Sub ;riate Sub $ommand=>$lick45 .orm<.Show 'nd Sub Coding for form; 7A!! PO!UCTS8% @im db "s @atabase @im rs "s (ecordset ;riate Sub $ommand2>$lick45 @ata2.(ecordset."dd0ew 'nd Sub ;riate Sub $ommand?>$lick45 Text2.Text B DD Text?.Text B DD Text6.Text B DD Text=.Text B DD TextC.Text B DD 'nd Sub ;riate Sub $ommand6>$lick45 .orm?.Show 'nd Sub ;riate Sub .orm>)oad45 Set db B Open@atabase4DG*H:II S,O;.&@:D5 Set rs B db.Open(ecordset4DS,O;D5 'nd Sub ;riate Sub )abel2>$lick45 'nd 'nd Sub Coding for form< 7UP!AT"O# O= PO!UCTS8% @im db "s @atabase @im rs "s (ecordset 09CSA10 ;riate Sub $ombo2>$hange45 'nd Sub ;riate Sub $ommand2>$lick45 If $ombo2.)ist435 B D00D Then Text?.Text B rs4=5 Text2.Text B 49al4Text?.Text5 J 9al4Text2.Text55 @ata2.(ecordset.'dit @ata2.(ecordset.%pdate 'lse If $ombo2.)ist435 B D,"&"&D Then Text?.Text B rs4=5 Text2.Text B 49al4Text?.Text5 J 9al4Text2.Text55 @ata2.(ecordset.'dit @ata2.(ecordset.%pdate 'lse If $ombo2.)ist435 B D&/SO('S"0@)'D Then Text?.Text B rs4=5 Text2.Text B 49al4Text?.Text5 J 9al4Text2.Text55 @ata2.(ecordset.'dit @ata2.(ecordset.%pdate 'nd If 'nd Sub ;riate Sub .orm>)oad45 $ombo2."ddItem D00D $ombo2."ddItem D,"&"&D $ombo2."ddItem D&/SO('S"0@)'D Set db B Open@atabase4DG*H:II S,O;.&@:D5 Set rs B db.Open(ecordset4DS,O;D5 'nd Sub ;riate Sub )abel2>$lick45 'nd 'nd Sub Phase 0 Soft(are Testing ;.1. Prep*ring Test Pl*n ;reparing test plan is the first step in the last phase of software deelopment cycle .The test plan consists of all the actiities that had to be done in the software testing phase. This test plan has been documented using the rational test manager software. ;.&. Perform >*lid*tion Testing Software is completely assembled as a package interfacing errors hae been uncoered and a final series of software test alidation testing may begin. 9alidation successie when the customer is satisfied. 09CSA10 ;.1. >*lid*tion Test Criteri* Software alidation is achieed through a series of black box test that demonstrates conformity with re!uirements. ;.4. Co2er*ge An*lysis $oerage analysis is used to identify untested code. %sing rational pure coerage, untested code can easily be identified. ;.;. Memory $e*)s &emory leak testing has been done using rational purity software. esult% :ased on the system re!uirements specification O0)I0' S,O;;I0I I0.O(&"TIO0 S/ST'& has been designed and implemented.