O SlideShare utiliza cookies para otimizar a funcionalidade e o desempenho do site, assim como para apresentar publicidade mais relevante aos nossos usuários. Se você continuar a navegar o site, você aceita o uso de cookies. Leia nosso Contrato do Usuário e nossa Política de Privacidade.
O SlideShare utiliza cookies para otimizar a funcionalidade e o desempenho do site, assim como para apresentar publicidade mais relevante aos nossos usuários. Se você continuar a utilizar o site, você aceita o uso de cookies. Leia nossa Política de Privacidade e nosso Contrato do Usuário para obter mais detalhes.
09CSA10 Online Shopping System CONTENTSPhase 1 Project Analysis and Planning 1.1. Study of the Problem 1.2. Project Scope 1.3. ObjectivesPhase 2 Cost EstimationPhase 3 Modeling the Requirements 3.1. Module Description 3.1.1. Login 3.1.2. Product Details 3.1.3. Add New Products 3.1.4. Updating The Quantity 3.2. UML Diagram 3.2.1. Use case Diagram 3.2.2. Class Diagram 3.2.3. Sequence Diagram 3.2.4. Collaboration DiagramPhase 4 Configuration Management 4.1. S/W Requirements 4.2. H/W Requirements 4.3. Tools 4.4. Software Development 4.4.1. Form Creation 4.4.2. ScriptPhase 5 Software Testing 5.1. Preparing Test Plan 5.2. Perform Validation Testing 5.3. Validation Test Criteria 5.4. Coverage Analysis 5.5. Memory Leaks
09CSA10 Synopsis This is a small scale project for Online shopping system.The basicidea is that customer’s can buy products using online. It consists ofproduct details, security system, status and exits. The administrator canenter the name and password and generate the report and can performoperations like add , search, delete the products in the database. The Online Shopping system enables vendors to set up onlineshops, customers to browse through the shops, and a system administratorto approve and reject requests for new shops and maintain lists of shopcategories.Also on the agenda is designing an online shopping site tomanage the items in the shop and also help customers purchase themonline without having to visit the shop physically.Our online shoppingmall will use the internet as the sole method for selling goods to itsconsumers. Shopping will be highly personalized and the mall willprovide lower prices than most competitors.
09CSA10Phase 1 Project Analysis and Planning1.1. Study of the Problem The Current shopping System is critical to set up online shops, customers tobrowse through the shops, and a system administrator to approve and reject requestsfor new shops and maintain lists of shop categories. This is a small scale project forOnline shopping System. The basic idea is that the candidates can buy product fromanywhere during any time by using their card number and password provided to them.The database will maintain the product details information. Customer can view theirproduct details using the card details. This Online shopping system involves with twotypes of users. • CUSTOMER • ADMINISTRATORCUSTOMER ROLE: The customer’s can login/logout the System. He/She can view his/her productdetails and buy their product. The customer can just view the information whereashe/she could not make changes in the database.ADMINISTRATOR ROLE: The administrator plays a vital role in the Online shopping system. Theadministrator controls the entire database. The report of the product is generated bythe administrator itself. The main role of the administrator is to safeguard the databaseand can add/delete the products from the database.1.2. Project Scope The supplementary specification applies to online shopping system.This specification defines the non-functional requirement of the system such as:Functionality: Since it stand alone application, one or more user may use it at a time.Usability: Desktop interface Windows 98/2000/XP/7
09CSA10Reliability: The system is available during online time only .Performance: The performance depends on hardware specification1.3. Objectives The purpose of this document is to define the requirements of Onlineshopping system. This supplementary specification lists the requirements that are notreadily captured in the use case model. Supplementary specification and the use casemodel capture a complete set of requirement of the system.Phase 2 Cost Estimation An estimate is a prediction based upon probabilistic assessment. It is theresponsibility of the project manager to make accurate estimations of effort and cost.This is particularly true for projects subject to competitive bidding where a bid toohigh compared with competitors would result in loosing the contract or a bid too lowcould result in a loss to the organization. This does not mean that internal projects areunimportant. From a project leaders estimate the management often decide whether toproceed with the project. Industry has a need for accurate estimates of effort and sizeat a very early stage in a project. However, when software cost estimates are doneearly in the software development process the estimate can be based on wrong orincomplete requirements. A software cost estimate process is the set of techniques andprocedures that organizations use to arrive at an estimate. An important aspect ofsoftware projects is to know the cost. The major contributing factor is effort.Why SCE is difficult and error prone ?• Software cost estimation requires a significant amount of effort to perform it correctly.• SCE is often done hurriedly, without an appreciation for the effort required.• You need experience at developing estimates, especially for large projects.• Human bias i.e. An Estimator 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 development.
09CSA10The causes of poor and inaccurate estimation• New software projects are nearly always different form the last.• Software practitioners dont collect enough information about past projects.• Estimates are forced to match the resources available.2.1. Cost and Pricing Our project is of high range and is highly efficient which can satisfy the shoppingcalculation for almost all software companies. The chances of error occurrence is verylimited and so our costs around Rs 10, 00,000(app). • A team of 11 members is required for completing the task. • It takes a time span of 3 weeks to shape the project. • There are no specific environmental constraints.Phase 3 Modeling the Requirements3.1. Module Description3.1.1. Login It is the login session for the Administrator, customer and Exit.3.1.2. Product Details It is used to view the product details from the database.3.1.3. Add New Products It is used to add a product into the database and it includes searching a productdetails and removing a product from database.3.1.4. Updating The Quantity It is used to update the product details from the database.
09CSA103.2. UML Diagram3.2.1. Use case Diagram Use Case diagrams show the various activities the users can perform on thesystem. The System is something that performs a function. They model the dynamicaspects of the system. It provides a user’s perspective of the system. Actor: An actor is a user of the system playing a particular role. Use case: Use case is a particular activity a user can do on the system. Relationship: Relationships are simply illustrated with a line connecting actors to use cases. customer items di splayed purchase login add item admin3.2.2. Class Diagram A class diagram describes the types of objects in the system and the variouskinds of static relationships that exist among them.i.e.,A graphical representation of astatic view on declarative static elements. A class is the description of a set of objectshaving similar attributes, operations, relationships and behavior.
09CSA10 custom items to display purchase name : variant new name : variant new item name : variant new age : variant itm no : variant itm no : variant address : variant new manuf date : variant quantity : variant city : variant new exp date : variant cost per item : variant total cost : variant view() purchase() view() adminis login add item name : variant new age : variant user name : variant new item name : variant new city : variant new password : variant new item no : variant quantity : variant add items() add items() view()3.2.3. Sequence Diagram A sequence diagram in Unified Modeling Language (UML) is a kind ofinteraction diagram that shows how processes operate with one another and in whatorder. It is a construct of a Message Sequence Chart. Sequence diagrams aresometimes called event diagrams, event 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 again3.2.4. Collaboration Diagram A Collaboration diagram is very similar to a Sequence diagram in the purposeit achieves; in other words, it shows the dynamic interaction of the objects in asystem. A distinguishing feature of a Collaboration diagram is that it shows theobjects and their association with other objects in the system apart from how theyinteract with each other. The association between objects is not represented in a
09CSA10Sequence diagram. A Collaboration diagram is easily represented by modeling objectsin a system and representing the associations between the objects as links. Theinteraction between the objects is denoted by arrows. To identify the sequence ofinvocation of these objects, a number is placed next to each of these arrows. administrat 1: add the item or add item customer 5: purchasing again 2: viewing the item to purchase 3: purchasing view item purchase 4: updating the items to customerPhase 4 Configuration Management Configuration management is also used in software development, where it iscalled Unified Configuration Management (UCM). Using UCM, developers can keeptrack of the source code, documentation, problems, changes requested, and changesmade. An advantage of a configuration management application is that the entirecollection of systems can be reviewed to make sure any changes made to one systemdo not adversely affect any of the other systems4.1. S/W Requirements OS: Windows Language: Visual Basic4.2. H/W Requirements Intel PII Processor with 300 MHz speed. 64 MB RAM 10MB Hard disk space
09CSA104.3. Tools Design Tool: Rational Rose suite4.4. Software Development4.4.1. Form CreationForm1:Form2:
09CSA104.4.2. ScriptCoding for form1 (MENU):Private Sub Command1_Click()Form2.ShowEnd SubPrivate Sub Command2_Click()Form3.ShowEnd SubCoding for form2 (CUSTOMER PURCHASE):Dim db As DatabaseDim rs As RecordsetPrivate Sub Command1_Click()Text7.Text = Text5.TextEnd SubPrivate Sub Command2_Click()If (Text6.Text = "") ThenMsgBox "ENTER THE QUANTITY"ElseText5.Text = (Val(Text5.Text) - Val(Text6.Text))Data1.Recordset.EditData1.Recordset.UpdateText7.Text = (Val(Text4.Text) * Val(Text6.Text))MsgBox "TRANSACTION SUCEESSFUL.. PAY TO DEALER"End IfEnd SubPrivate Sub Command3_Click()rs.MoveFirstText1.Text = rs(0)Text2.Text = rs(1)Text3.Text = rs(2)Text4.Text = rs(3)Text5.Text = rs(4)End SubPrivate Sub Command4_Click()rs.MovePreviousText1.Text = rs(0)Text2.Text = rs(1)Text3.Text = rs(2)Text4.Text = rs(3)Text5.Text = rs(4)End Sub
09CSA10Private Sub Command5_Click()rs.MoveNextText1.Text = rs(0)Text2.Text = rs(1)Text3.Text = rs(2)Text4.Text = rs(3)Text5.Text = rs(4)End SubPrivate Sub Command6_Click()rs.MoveLastText1.Text = rs(0)Text2.Text = rs(1)Text3.Text = rs(2)Text4.Text = rs(3)Text5.Text = rs(4)End SubPrivate Sub Form_Load()Set db = OpenDatabase("Z:BIG SHOP.MDB")Set rs = db.OpenRecordset("SHOP")Text1.Text = " "Text2.Text = " "Text3.Text = " "Text4.Text = " "Text5.Text = " "Text6.Text = " "End SubPrivate Sub LO_Click()Form1.ShowEnd SubCoding for form3 (ADMINISTRATOR LOGIN):Private Sub Command1_Click()If Text1.Text = "bhuva" And Text2.Text = "123" ThenMe.HideText1.Text = ""Text2.Text = ""Form4.Visible = TrueElseMsgBox "invalid username and password"Text1.Text = ""Text2.Text = ""Text1.SetFocusEnd IfEnd SubPrivate Sub Command2_Click()EndEnd Sub
09CSA10Coding for form4 (ADMIN CHECK):Private Sub Command1_Click()Form5.ShowEnd SubPrivate Sub Command2_Click()Form1.ShowEnd SubPrivate Sub Command4_Click()Form6.ShowEnd SubCoding for form5 (ADD PRODUCTS):Dim db As DatabaseDim rs As RecordsetPrivate Sub Command1_Click()Data1.Recordset.AddNewEnd SubPrivate Sub Command2_Click()Text1.Text = ""Text2.Text = ""Text3.Text = ""Text4.Text = ""Text5.Text = ""End SubPrivate Sub Command3_Click()Form2.ShowEnd SubPrivate Sub Form_Load()Set db = OpenDatabase("Z:BIG SHOP.MDB")Set rs = db.OpenRecordset("SHOP")End SubPrivate Sub Label1_Click()EndEnd SubCoding for form6 (UPDATION OF PRODUCTS):Dim db As DatabaseDim rs As Recordset
09CSA10Private Sub Combo1_Change()End SubPrivate Sub Command1_Click()If Combo1.List(0) = "NN" ThenText2.Text = rs(4)Text1.Text = (Val(Text2.Text) + Val(Text1.Text))Data1.Recordset.EditData1.Recordset.UpdateElseIf Combo1.List(0) = "HAMAM" ThenText2.Text = rs(4)Text1.Text = (Val(Text2.Text) + Val(Text1.Text))Data1.Recordset.EditData1.Recordset.UpdateElseIf Combo1.List(0) = "MYSORESANDLE" ThenText2.Text = rs(4)Text1.Text = (Val(Text2.Text) + Val(Text1.Text))Data1.Recordset.EditData1.Recordset.UpdateEnd IfEnd SubPrivate Sub Form_Load()Combo1.AddItem "NN"Combo1.AddItem "HAMAM"Combo1.AddItem "MYSORESANDLE"Set db = OpenDatabase("Z:BIG SHOP.MDB")Set rs = db.OpenRecordset("SHOP")End SubPrivate Sub Label1_Click()EndEnd SubPhase 5 Software Testing5.1. Preparing Test Plan Preparing test plan is the first step in the last phase of software developmentcycle .The test plan consists of all the activities that had to be done in the softwaretesting phase. This test plan has been documented using the rational test managersoftware.5.2. Perform Validation Testing Software is completely assembled as a package interfacing errors have beenuncovered and a final series of software test validation testing may begin. Validationsuccessive when the customer is satisfied.
09CSA105.3. Validation Test Criteria Software validation is achieved through a series of black box test thatdemonstrates conformity with requirements.5.4. Coverage Analysis Coverage analysis is used to identify untested code. Using rational purecoverage, untested code can easily be identified.5.5. Memory Leaks Memory leak testing has been done using rational purity software.Result: Based on the system requirements specification ONLINE SHOPPINGINFORMATION SYSTEM has been designed and implemented.