FruitLand ( Management System ) Developed By: Wajid Ali (2502/FBAS/BSSE/F14) Supervised By: Mr. Usman Rafiq INTERNATIONAL ISLAMIC UNIVERSITY ISLAMABAD Faculty of Basic and Applied Sciences Department of Computer Sciences And Software Engineering “In the Name of Allah, the Most Beneficent, the Most Merciful” AcknowledgementI take this occasion to thank God, almighty for blessing me with his grace and taking my endeavor to a successful culmination. I extend my sincere thanks to my supervisor, Mr.
Usman Rafiq , for providing me the right guidance and advice at the crucial junctures and for showing me the right way. I extend my sincere thanks to other respected faculty teachers, for providing me the right guide. Last but not the least, I would like to thank my friends and family for the support and encouragement they have given me during the course of my work. Abstract This project is a web base shopping system for a shop. The project aim is to deliver’s the online shopping facilities. This project is an attempt to provide the advantage of online shopping to customers of a real shop.
It helps in buying the products in the shop anywhere through internet by using an application. Thus the customer will get the service of online shopping and home delivery from different shop. This system can be implemented to any shop in the locality or to multinational branded shops having retail outlet chains. If shops are providing an online portal where their customers can enjoy easy shopping from anywhere, the shops won’t be losing any more customers to the trending online shops such as flipcart or eBay.
TABLE OF CONTENT: TOC o “1-3” h z u Chapter No 1: Introduction PAGEREF _Toc489414636 h 7 1.1: Introduction: PAGEREF _Toc489414637 h 8 1.2: Project Overview: PAGEREF _Toc489414638 h 8 1.3: Project Objective: PAGEREF _Toc489414639 h 9 1.4: Scope of Project: PAGEREF _Toc489414640 h 9 1.5: System Analysis: PAGEREF _Toc489414641 h 9 1.5.1: EXISTING SYSTEM PAGEREF _Toc489414642 h 10 1.5.2: PROPOSED SYSTEM PAGEREF _Toc489414643 h 11 1.5.3: System Specification Requirement: PAGEREF _Toc489414644 h 12 1.6: System Study: PAGEREF _Toc489414645 h 13 1.6.1: Modules: PAGEREF _Toc489414646 h 15 1. 7:FEASIBILITY STUDY PAGEREF _Toc489414646 h 16 1.7.1 OPERATIONAL FEASIBILITY PAGEREF _Toc489414648 h 171.7.2 TECHNICAL FEASIBILITY PAGEREF _Toc489414649 h 181.7.3 ECONOMICAL FEASIBILITY PAGEREF _Toc489414650 h 19CHAPTER No: 02 SYSTEM ANALYSIS: PAGEREF _Toc489414651 h 20 2: Use Case Model: PAGEREF _Toc489414652 h 21 2.1: Use Case Diagram of the system: PAGEREF _Toc489414653 h 222.2.1: Use case Registration PAGEREF _Toc489414654 h 23 2.2.2: Use case view Item PAGEREF _Toc489414655 h 232.2.3: Use case purchase item PAGEREF _Toc489414656 h 232.2.4: Use case Make Payment: PAGEREF _Toc489414657 h 232.2.5: Use case Track Order: PAGEREF _Toc489414658 h 23 2.3: Use case description in detailed expended format: PAGEREF _Toc489414659 h 242.3.1 Use case Registration: PAGEREF _Toc489414660 h 242.3.2 Use case View Item: PAGEREF _Toc489414661 h 252.3.3: use case Purchase Item: PAGEREF _Toc489414662 h 262.3.4: Use case Make Payment: PAGEREF _Toc489414663 h 272.3.5: Use case add item PAGEREF _Toc489414664 h 282.3.6: Use case Track order2 PAGEREF _Toc489414665 h 9 2.4: System Sequence Diagram: PAGEREF _Toc489414666 h 30 2.5: Domain Modal PAGEREF _Toc489414667 h 31CHAPTER 3:SYSTEM DESIGN PAGEREF _Toc489414668 h 33 3.1: INPUT AND OUTPUT DESIGN PAGEREF _Toc489414669 h 343.1.1: INPUT DESIGN PAGEREF _Toc489414670 h 343.1.2: OUTPUT DESIGN: PAGEREF _Toc489414671 h 34 3.2 : System Tools: PAGEREF _Toc489414672 h 353.2.1: Front-End: PAGEREF _Toc489414673 h 363.2.2: Backend: PAGEREF _Toc489414674 h 37 3.3: Data flow Diagram: PAGEREF _Toc489414675 h 383.3.1: Zero Level data Flow Diagram:3 PAGEREF _Toc489414676 h 93.3.2: Level one data flow diagram for admin PAGEREF _Toc489414677 h 403.3.3: Level one data flow diagram for user: PAGEREF _Toc489414678 h 41 3.4: Collaboration Diagram: PAGEREF _Toc489414679 h 43 3.5:Design Class Diagram: PAGEREF _Toc489414680 h 45 3.6:Entity Relationship Diagram: PAGEREF _Toc489414681 h 47Chapter 4: Testing PAGEREF _Toc489414682 h 48 4.1: Methadology: PAGEREF _Toc489414683 h 49 4.2: Interface Testing: PAGEREF _Toc489414684 h 51 4.3:Test Cases: PAGEREF _Toc489414685 h 53 4.4: Result: PAGEREF _Toc489414686 h 54Chapter 5: Conclusion PAGEREF _Toc489414682 h 55 5.1:Project Conclusion PAGEREF _Toc489414683 h 56Chapter 6: Conclusion PAGEREF _Toc489414682 h 57 6. 1:Websites/papers used for help PAGEREF _Toc489414683 h 58 Chapter No 1: Introduction 1.1: IntroductionThis Project is an online shopping framework for a current shop. The venture objective is to convey the internet shopping application. Web based shopping is the procedure whereby purchasers straight forwardly purchase merchandise or administrations from a vender progressively, without a delegate benefit, over the Internet. It is a type of electronic business.
This venture is an endeavor to give the benefits of internet shopping to clients of a genuine shop. It helps purchasing the items in the shop anyplace through web by utilizing an android gadget. Along these lines the client will get the administration of web based shopping and home conveyance from his most loved shop. This project enables guests to your on-line shopping site to gather things in a virtual shopping basket. They may see the substance of their shopping basket whenever and may include or erase things freely. The program consequently computes the subtotal; deals impose, shipping charges, and great aggregate.
At the point when a guest chooses to registration, the request data including the purchaser’s name, address and charging guideline is messaged to your request office (or whomever you pick) and a receipt is sent to the customer.This is programming which causes you to do the real piece of web based shopping by utilizing this website and can be overseen by on the web; you (or the Customer) can do the all real exchange in a secured way. Here the client will feel a virtual shopping by adding the chose item to his truck notwithstanding that; he can likewise bulks option 1.2: Project OverviewThe focal idea of the application is to enable the client to shop for all intents and purposes utilizing the Internet and enable clients to purchase dry fruits items from the web store. The data relating to the items are stores on server side (store). The Server procedure the clients and the things are sent to the address put together by them. The application was outlined into two modules initially is for the clients who wish to purchase the dry fruits items. Second is for the vendors who keeps up and refreshes the data relating to the corrective things and those of the clients.
The end client of this item is a departmental store where the application is facilitated on the web and the manager keeps up the database. The application which is sent at the client database, the points of interest of the things are presented from the database for 1.3: Project ObjectiveThe goal of the project is to make an application in web based stage to buy things in a current shop. In order to build such an application complete web support need to be provided. An entire and productive web application which can give the web based shopping knowledge is the fundamental goal of the venture.
1.4: Scope of ProjectThis system can be implemented to any shop in the locality or to multinational branded shops having retail outlet chains. The system recommends a facility to accept the orders 24*7 and a home delivery system which can make customers happy. If shops are providing an online portal where their customers can enjoy easy shopping from anywhere, the shops won’t be losing any more customers to the trending online shops such as flipcart or eBay. Since the application is available in the Smartphone it is easily accessible and always available. 1.5: System AnalysisFramework investigation is that the route toward get-together, diagnosis problems and exploitation the knowledge to suggest changes on the framework. Framework examination could be a basic reasoning development that needs real correspondence between the framework customers and structure designers.
Framework examination or study could be a basic time of any framework amendment method. The framework is seen with everything taken into consideration, the information sources area unit perceived and also the system is subjected to shut examination to acknowledge the problem ranges. The arrangements area unit given as a proposition. The proposition is unbroken a watch on client request and fitting changes area unit created. This circle closes once the client is content with the proposition.
1.5.1: EXISTING SYSTEMThe present system for shopping is to visit the shop physically and from the accessible item pick the thing client need and purchasing the thing by installment of the cost of the thing. 1. It is less easy to understand. 2. Client must go to shop and select items. 3.
It is hard to recognize the required item. 4. Description of the product is limited. 5. It is a tedious procedure 6.
Not in reach of far distant users. 1.5.2: PROPOSED SYSTEMIn the proposed framework customer require not go to the shop for buying the things. He can orchestrate the thing he wishes to buy through the web application. The shop proprietor will be overseer of the framework. Shop proprietor can choose middle people who will help proprietor in managing the customers and thing masterminds.
The system similarly recommends a home transport structure for the purchased things. 1.5.3: System Specification Requirement1.5.3.1: GENERAL DESCRIPTION Item Description: The framework comprises of a web application which can give the web based shopping administration for the client. “Web application ought to have the capacity to help the client for choosing his thing and to help the proprietor in dealing with the requests from the clients.” Issue Statement: As electronic searching remodeled into associate degree example these days the steady outlets square measure losing their customers to on-line brands. Customers have straightforward searching foundation and saving time through searching on the net. For fighting with those on-line brands, If outlets square measure giving net an internet} passage wherever their customers will look through web and obtain the items at their portals it’ll extend the quantity of consumers. 1.5.3.2: SYSTEM OBJECTIVES To give web based shopping of items in a current shop.
To give a web based shopping site for a similar shop. 1.5.3.3: SYSTEM REQUIREMENTS 1.5.3.3.1 NON FUNCTIONAL REQUIREMENTS i. Proficiency REQUIREMENT At the point when a web based shopping basket executed client can buy item in a proficient way. ii.
Reliability Requirement The framework ought to give a dependable situation to both clients and owner. All requests ought to be coming to at the administrator with no blunders. iii. Ease of use Requirement The web based application is intended for easy to understand condition and usability. iv. Implementation REQUIREMENT Usage of the system utilizing html, CSS, Bootstrap and so on in front end with JavaScript as back end.
What’s more, the database part is produced by Firebase. Responsive web designing is used for making the website compatible for any type of screen. v. Delivery REQUIREMENT The entire framework is required to be conveyed in four months of time with a week after week assessment by the project guide 1.5.3.3.2: FUNCTIONAL REQUIREMENTS Client USER LOGIN Feature Description: This segment used by the customer to login into framework. A customer must login with his customer name and mystery word to the framework after enlistment.
Then again in the event that they are invalid, the customer not allowed to go into the framework. Functional Requirements: – Username and password will be given after client enrollment is confirmed. – Password ought to be hidden from others while writing it in the field REGISTER NEW USER Feature Description: Another client should enroll in the system by providing essential details in order to view the products in the system. The administrator must acknowledge another client by unblocking him.
Functional Requirements: – System must have the capacity to check and approve data. – The system must encode the secret key of the client to give security. ITEM PURCHASING Feature Description: The client can add the desired item into his cart by clicking add to cart option given on the product. He can view his product by just clicking on the cart. All items included via cart can be seen in the cart. Client can delete a thing from the cart by clicking delete button.
After confirming the items in the cart the user can submit the cart by providing a delivery address. On successful submitting the cart will become empty. Functional Requirements: – System must guarantee that, only register customer can buy products. Administrator MANAGE USER Feature Description: The admin can include client, erase client, view client MANAGE PRODUCTS Feature Description: The admin can include item, erase item and view item.
MANAGE ORDERS Feature Description: The admin can view order and delete order1.6: System Study1.6.1: ModulesAfter the careful analysis of system, it is identified to be presented with following modules Administration User 1.6.1.1: Administration The powerful user of the system. It is the owner of the system. He can perform several following functionalities as follow: User Management Product Management Order Management 1.6.1.1.1: User Management Add User: Admin has the capability of adding the user View User: He/ she also can view the register customer Delete User: He/ she also have privileges to delete some customer User Management View User Add user Delete User Fig: User Management 1.6.1.1.2: Product Management Add Product As the system have many products in the store. The administrator has the capability to add more products in the system Delete Product Just like adding the product he can delete the certain product if it is out of stock etc. Search Product He has the capability if searching as well.
Delete Product Add product Product Management Search Product Fig: Product Management 1.6.1.1.3: Order Management: View Order The admin can view the orders which are being placed Delete Order The administrator has the power to delete the certain order when it is delivered Order Management Delete Order View Order Fig: Order Management 1.6.1.2: User Module The user can perform the following function while visiting the site: Registration After visiting the site, the user can easily registers him/her by just clicking on the register button. He/she just have to provide basic information during registration. Login: Once register, he/she can login to the profile by providing username and password. Search Product The user has the capability of searching the product. Manually searching the product takes too much time. View description The user can view the detailed description of the product to make them clear about the product.
Add to cart Once the user is satisfied with the product, he/she can add it to the cart for ordering. Checkout After adding product to cart, user can confirm the order by clicking on checkout. Purchase Product View Product User Search Product Fig: User Module CHAPTER No: 02 SYSTEM ANALYSES2.1: Use Case ModelAn utilization case chart is a realistic delineation of the connections among the components of a framework. An utilization case is a procedure utilized in framework investigation to recognize, clear up, and sort out framework necessities. Utilize case outlines are utilized in UML (Unified Modeling Language), a standard documentation for the demonstrating of certifiable articles and frameworks. Use case diagrams depict: Use cases.
A use case describes a sequence of actions that provide something of measurable value to an actor and is drawn as a horizontal ellipse. Actors. An actor is a person, organization, or external system that plays a role in one or more interactions with your system. Actors are drawn as stick figures. Associations.
Relationship amongst performing artists and utilize cases are shown being used case charts by strong lines. An affiliation exists at whatever point a performing artist is included with a cooperation depicted by an utilization case. Affiliations are displayed as lines interfacing use cases and on-screen characters to each other, with a discretionary pointed stone toward one side of the line. The pointed stone is regularly used to showing the bearing of the underlying conjuring of the relationship or to demonstrate the essential on-screen character inside the utilization case. The sharpened stones are normally mistaken for information stream and therefore I maintain a strategic distance from their utilization. System boundary boxes : You can draw a square shape around the utilization cases, called the framework limit box, to demonstrate the extent of your framework.
Anything inside the container speaks to usefulness that is in degree and anything fresh isn’t. Framework limit boxes are once in a while utilized, despite the fact that now and again I have utilized them to distinguish which utilize cases will be conveyed in each significant arrival of a framework. Packages : Bundles are UML builds that empower you to sort out model components, (for example, utilize cases) into gatherings. Bundles are portrayed as document envelopes and can be utilized on any of the UML charts, including both utilize case outlines and class graphs. I utilize bundles just when my outlines end up inconvenient, which by and large infers they can’t be imprinted on a solitary page, to sort out an extensive graph into littler ones 2.1: Use Case Diagram of the system Registration Add Item Make Payment View Item Purchase Item User Admin Fig: Use Case Diagram 2.2: Use case description in brief format: 2.2.1: Register User Registration Use case ID: 01 Description The user visit the website and request for registration, the registration form open and user fill the form and submit it 2.2.2: View ItemView Item Use case ID: 02 Description After visiting the site , the user clicks on the product category to view the different items 2.2.3: Purchase itemPurchase Item Use case ID: 03 Description Once the user see the product description of desired item, he/she can purchase it by adding it to the cart 2.2.4: Make Payment:Make Payment Use case ID: 04 Description If the user is interested in purchasing, he/she has to fill the booking form and has bound to pay after receiving the product 2.3: Use case description in detailed expended format:2.3.1: Register User:Registration Use case ID: 01 Actor: User, Admin Purpose To get updated about discounts and new products Overview User/ admin get register their self to get updated for new products and discounts etcType: Primary Cross Reference: Pre-Conditions: visit the web page Typical course of Events Actor Actions System Response 1) User/ admin request for registration Registration form opens 2) Fill the registration form and submitted Account confirmation / rejection message Post-Condition Account will be created for future actions such as transactions etc. Alternative course of Events (if any) Actor Actions System Response 2.1) Admin/ user reenter registration data Confirms registration 2.3.2 : View Item:View Items Use case ID: 02 Actor: Admin/ user Purpose To know description of product Overview Actor can view the items for the sake of purchasing to know about product Type: Primary Cross Reference: Pre-Conditions: Visit the website Typical course of Events Actor Actions System Response 1) Click on the products catalog Products catalog opens 2) Click on desired product Display info regarding selected product Post-Condition View detailed description about product and then can add it to cart Alternative course of Events (if any) Actor Actions System Response 2.3.3: Purchase Item:Purchase Item Use case ID: 03 Actor: User Purpose Overview Actor can purchase items if product description satisfies him/her Type: Primary Cross Reference: Pre-Conditions: Fill out the mailing address to which the product will be delivered Typical course of Events Actor Actions System Response 1) Click on desired product Detailed description will open 2) Add it to cart Checkout option displays 3) Click on checkout button Mailing address form will open 4) provide mailing address Order confirms Post-Condition Alternative course of Events (if any) Actor Actions System Response 2.3.4: Make Payment:Make Payment Use case ID: 04 Actor: User Purpose To buy item Overview Actor have to pay prize of selected product when received Type: Primary Cross Reference: Pre-Conditions: Actor will get the product after paying the prize of selected item Typical course of Events Actor Actions System Response 1) Select product and add it to cart Checkout form displays 2) Confirm the purchase Order confirmation dialog opens 3) Make payment, after receiving product Post-Condition Make payment about receiving the product Alternative course of Events (if any) Actor Actions System Response 2.3.5: Add ItemAdd Item Use case ID: 05 Actor: User/admin Purpose Overview Product will be added to online selling Type: Primary Cross Reference: Pre-Conditions: Product will be available for purchasing Typical course of Events Actor Actions System Response 1) Admin will click on add product button Products catalog form will open 2) select product and add it Confirmation message received Post-Condition Product will be available for purchasing Alternative course of Events (if any) Actor Actions System Response 2.4: System Sequence DiagramGrouping graph portray joint efforts among classes with respect to an exchange of messages after some time.
They’re furthermore called event diagrams. A progression diagram is a conventional way to deal with envision and affirm distinctive runtime circumstances. These can foresee how a structure will act and to discover obligations a class may require amid the time spent showing another system Fig: System Sequence Diagram FruitLand Customer Product Database register()login()Verify()productInfo()Search()displayProductInfo()buy()mailingAdressproductDelivery()Logout productInfo Fig: Sequence Diagram 2.5: Domain ModalA space demonstrate contains area classes and space connections. Area classes speak to the diverse sorts of articles in the space, and space connections speak to data about a connection between two space classes *. 0 Pays for Payment amount1 Places Order supplies0.* 1 owns1 Supplied by * Supplier Customer itemunitCart Product nameFruitLand Accounts ProductDescription namedesc Fig: Domain Model Chapter 3: SYSTEM DESIGN 3.0: SYSTEM DESIGNSystem design is used to creation of the new system.
In the phase of system design, the focus is on the implementation of feasible system. It emphasizing on translating the design. It has two phases of development: Physical Design Logical Design During the phase of logical design, the system analyst describes the inputs, outputs, databases and functions etc. All in a format that meets the user requirements.
The expert likewise indicates the requirements of the client at a level that for all intents and purposes decides the data stream all through the framework and the information assets. Here the intelligent outline is done through information stream charts and database plan. The physical outline is trailed by physical plan or coding. Physical outline creates the working framework by characterizing the plan particulars, which determine precisely what the applicant framework must do.
The software engineers compose the essential projects that acknowledge contribution from the client. 3.1 INPUT AND OUTPUT DESIGN3.1.1 INPUT DESIGN: Input design is the link that ties the information system into the world of its users. The input design involves determining the inputs, validating the data, minimizing the data entry and provides a multi-user facility. Inaccurate inputs are the most common cause of errors in data processing. Errors entered by the data entry operators can be controlled by input design.
The user-originated inputs are converted to a computer based format in the input design. Input data are collected and organized into groups of similar data. Once identified, the appropriate input media are selected for processing. All the input data are validated and if any data violates any conditions, the user is warned by a message.
If the data satisfies all the conditions, it is transferred to the appropriate tables in the database. In this project the student details are to be entered at the time of registration. A page is designed for this purpose which is user friendly and easy to use. The design is done such that users get appropriate messages when exceptions occur. 3.1.2 OUTPUT DESIGN:Computer output is the most important and direct source of information to the user.
Output design is a very important phase since the output needs to be in an efficient manner. Efficient and intelligible output design improves the system relationship with the user and helps in decision making. Allowing the user to view the sample screen is important because the user is the ultimate judge of the quality of output. The output module of this system is the selected notifications.
3.2 : System ToolsDifferent tools are being used for developing this project, which are as under: 3.2.1: Front-End:HTML The main thing to acknowledge about HTML5 is, it is anything but a solitary element. It’s involved numerous components, including the fifth update of HTML, CSS3 and numerous JavaScript API’s. It enables you to utilize the media experience of the work area on the web. Preceding this innovation, encounters of this kind could just work on the work area. With HTML5, designers can make applications and sites that capacity like work area applications, which enable you to utilize the web stage to achieve the greater part of your clients on the double. Clients never again need to download applications for different gadgets; They can begin an application by tapping on a connection or catch and not need to stress over having the most recent refresh.
An intriguing part of HTML5 is that it will enable you to make applications that capacity notwithstanding when not associated, or when your framework is disconnected. The trap is having the capacity to store the benefits and substance locally. At the point when this is done, the application works, paying little heed to where you go or if your framework is on the web. Another of the positive parts of the disconnected highlights is having the capacity to store information in the reserve or such that enables the information to be held regardless of whether the page is reloaded. HTML5 enables you to implant video specifically into a site page.
Know that while the video component has been institutionalized, how the video codec is bolstered differs with every program, so it’s imperative to watch that as a major aspect of your improvement procedure. New sorts of frame components have been incorporated, which enable you to show a given kind of information at that point depend upon the program to execute it. A portion of the information choices are: Telephone number, email, URL, date, time, shading alongside various varieties. CSS BOOTSTRAP JAVASCRIPT JQUERY AJAX 3.3: Data flow DiagramA data flow diagram (DFD) is a graphical representation of the “flow” of data through system.
DFDs can also be used for the visualization of data processing (structured design). A Data Flow Diagram (DFD) is a structured analysis and design tool that can be used for flowcharting. A DFD is a network that describes the flow of data and the processes that change or transform the data throughout a system. This network is constructed by using a set of symbols that do not imply any physical implementation.
It has the purpose of clarifying system requirements and identifying major transformations. So it is the starting point of the design phase that functionally decomposes the requirements specifications down to the lowest level of detail. DFD can be considered to an abstraction of the logic of an information-oriented or a process-oriented system flow-chart. For these reasons DFD’s are often referred to as logical data flow diagrams.
EXTERNAL ENTITY An external entity is a source or destination of a data flow. Only those entities which originate or receive data are represented on a data flow diagram. The symbol used is a rectangular box. PROCESS A process shows a transformation or manipulation of data flow within the system. The symbol used is an oval shape. DATAFLOW The data flow shows the flow of information from a source to its destination.
Data flow is represented by a line, with arrowheads showing the direction of flow. Information always flows to or from a process and may be written, verbal or electronic. Each data flow may be referenced by the processes or data stores at its head and tail, or by a description of its contents. DATA STORE A data store is a holding place for information within the system: It is represented by an open ended narrow rectangle. Data stores may be long-term files such as sales ledgers, or may be short-term accumulations: for example batches of documents that are waiting to be processed.
Each data store should be given a reference followed by an arbitrary number. 3.3.1: Zero Level data Flow Diagram: FruitLand Shop Management Admin User Product InformationProduct Information User OrderOrder Detail Fig: Zero Level Data Flow Diagram 3.3.2: Level one data flow diagram for adminLogInADM Request for LoginLogin Detail Verified Loginverify Login Details Manage Product PROD. New Product DetailProduct Detail Update Product InfoUpdate Product Detail Manage User CUST.Request for customer DetailModify User ADMIN Customer DetailModify Customer Detail Manage Order Order Order ConfirmOrder Confirm Order InfoOrder Detail Generate Bill BILL Bill IdBill Detail Report Bill DetailBill Info REPORT Report Get ReportReport Info Fig : Level 1 data flow diagram for admin 3.3.3: Level one data flow diagram for user View Product PROD. View Product Product Informationverify Login Details Login/ Register CUST.Login informationLogin Information Login InfoLogin Detail Select Product PROD. Product Information USER Product Info Order Product Order Give Order DetailOrder Detail Order DetailOrder Information Generate Bill BILL Request For BillBill Detail Report Bill DetailBill Info REPORT Feedback Information Feedback ResponseFeedback Fig : Level one data flow diagram for user 3.4: Collaboration DiagramIn the coordinated effort outline, the strategy call succession is shown by some numbering system.
The number demonstrates how the techniques are called consistently. We have taken a similar request administration framework to depict the coordinated effort graph. Technique calls are like that of an arrangement outline. Be that as it may, distinction being the arrangement graph does not portray the protest association, though the coordinated effort chart demonstrates the question association. To pick between these two charts, accentuation is put on the kind of necessity.
On the off chance that the time arrangement is critical, at that point the grouping outline is utilized. In the event that association is required, at that point cooperation graph is utilized. ELEMENTS OF COLLABORATION DIAGRAM: A collaboration diagram consists of following elements: Object: The objects interact with each other in the system. Depicted by a rectangle with the name of the object in it, preceded by a colon and underlined Relation/Association: A link connects the associated objects. Qualifiers can be placed on either end of the association to depict cardinality. Messages: An arrow pointing from the commencing object to the destination object shows the interaction between the objects.
The number represents the order/sequence of this interaction :Category 1.1:search() 1:findProduct() 1.2:viewProduct() :Product :FruitLand 2.2:makeOrder() 2:checkout() :ShoppingCart:Order 2.1:addProduct() Fig: Collaboration Diagram 3.5: Design Class Diagram:A class diagram models the static structure of a system. It shows relationships between classes, objects, attributes, and operations 3.5.1: ELEMENTS OF CLASS DIAGRAM: Classes Classes represent an abstraction of entities with common characteristics. Associations represent the relationships between classes. Illustrate classes with rectangles divided into compartments. Place the name of the class in the first partition (centered, bolded, and capitalized), list the attributes in the second partition (left-aligned, not bolded, and lowercase), and write operations into the third. Active Classes Active classes initiate and control the flow of activity, while passive classes store data and serve other classes.
Illustrate active classes with a thicker border. Visibility Associations Associations represent static relationships between classes. Place association names above, on, or below the association line. Use a filled arrow to indicate the direction of the relationship. Place roles near the end of an association.
Roles represent the way the two classes see each other. Multiplicity (Cardinality) Composition and Aggregation Generalization C_idnameamountPayment buyProduct()viewProduct()makePayment()addToCart()deleteFromCart()buyProduct()viewProduct()makePayment()addTocart()deleteFromCart()nameidadressCustomer viewProduct()addProduct()deleteProduct()modifyProduct()makeShipment()confirmDelivery()idnameAdmin idnamepriceProduct makeshasBuy manage Cart idnamequantitydetailprice Fig: Class Diagram 3.6: Entity Relationship DiagramAn entity relationship diagram (ERD) shows the relationships of entity sets stored in a database. An entity in this context is a component of data. In other words, ER diagrams illustrate the logical structure of databases. At first glance an entity relationship diagram looks very much like a flowchart. It is the specialized symbols, and the meanings of those symbols, that make it unique Entity relationship Diagram Symbols: Entities: Substances, which are spoken to by square shapes.
An element is a question or idea about which you need to store data A powerless element is a substance that must characterized by an outside key association with another element as it can’t be particularly distinguished by its own traits alone. Actions: Actions, which are represented by diamond shapes, show how two entities share information in the database Attributes: Connecting lines: solid lines that connect attributes to show the relationships of entities in the diagram. Cardinality pricenamename ididmanage Product Admin makeSelect/view handlePayment Customer name idquantity id nameview detailCart addressid pricename amount Fig: Entity Relationship Diagram Chapter 4: Testing This chapter comprises the methods that were used for testing, validating etc4.1: MethodologyWith this testing approach, each one of the specs were set up for a model, and a game plan was by then attempted to be showed up; the analyzer started forming his or her code and checked whether he or she could get comparative results that the specs said. Thusly, the specs were attempted on each model, and steady testing was associated.
This moreover restricted the testing that would should be executed toward the complete of the item lifecycle. At the same time, all parts of the item were attempted. Dares to take after while executing the reasoning are according to the accompanying: 1. Start with a base limit that you have to realize. 2.
Make a record with the point by point essential definition, an action outline with a depiction of stream, database tables to be used, a part graph, and a portrayal of each section with the precondition and tables that would be impacted by the fragment. 3. Give the record to the analyzer, and work with the analyzer while he or she makes the code to check if the progression in the report can be executed and if the delayed consequence of every use case can be proficient. 4.
If the analyzer finds a phase hard to execute or assumes he or she is feeling the loss of additional information to realize the convenience, by then go to stage 2; for the most part, go to stage 3. 5. Demand that the analyzer sign on each one of the slip-ups and inconveniences he or she encountered while managing the model utilization. 6. Once the model is done and the results between the architect’s model and analyzer’s model match, tackle the other need, and develop the model to indisputable programming.
7. At the point when the testing approach was executed, the accompanying advantages and disadvantages with respect to the testing approach were figured it out. Pros of using the methodology Helps give a better understanding about the requirements. Better design at the end of the cycle. Reduced testing to be performed at the end of the cycle Documents produced would be of higher quality.
Cons of using the methodology The person working on the document should be experienced. There are increased time and money involved with testing. Different viewpoints for the same problem can lead to varying results. 4.2: Interface Testing:This section lists the functional requirements used for creating the test-case table, the test cases that were used to verify the interface table, and the results for the test-cases table.
Table 1 lists the functional requirements for the interface built for the online shopping-cart application, along with a short description of each requirement List Of functional requirements: Functional Requirement Number Functional Requirement Short Description FR01 The online shopping-cart application shall have two types of authentication: User authentication and Admin authentication. FR02 The online shopping-cart application shall be accessible to all the users to browse all the categories and the items. FR03 The users shall be able to view the items they added to the shopping cart. FR06 The Admin shall be able to upload new/revised items as well as to add/modify the categories. FR07 The Admin shall be able to view all the users registered in the system. FR08 The Admin shall be able to view all the information about users who placed an order from the shopping cart.
FR09 The users shall not be able to check out with an empty cart. FR10 The users shall not be able to place an order without providing valid information for all rows in the order form. FR11 The users shall not be able to place an order if any of the columns in the order form are left empty. 4.3: Test CasesTC01: To test the Login/Authentication interface Input: Username and Password Output: Valid Destination Page Valid Range: User Name Alphanumeric, Password Alphanumeric End Messages/Result i.
If (User == Valid User), an order form appears to complete the checkout process ii. If (User != Valid User), an error message is displayed on the Login interface. 2. TC02: To test, the users can view the items they add to the shopping cart. Description of Purpose: The system shows all the saved items in shopping cart for a particular user. The user can choose to check out the items or go back to continue shopping.
Input: The user adds an item to the shopping cart from any of the available categories. Output: The shopping-cart page pops up, showing the item that is added by the user. End messages/Result i. If (Selection == Item and document == exists), the user is able to add that item to the cart, and the item shows up in the shopping cart, prompting user to delete the item, to continue shopping, or to check out the item. ii. If (Selection = Item and Selection = View Cart), an empty shopping cart pops up with buttons to check out or to continue shopping.
3. TC03: To test, the Admin can upload new/revised categories and items. Description: The Admin can add or upload more items to a category or can add a completely new category. The Admin can also modify the price, information and shipping taxes, etc. for the existing items and categories.
Input i. User=Admin ii. Selection=Items iii. Selection=Categories Output: New or modified items or categories in the shopping cart. End messages/Result i.If (User type = “Admin” &Selection = (Items || Category)&& Item/Category =existing), then display the modified items or categories in the shopping cart. ii.If (User type == “Admin” &Selection == (Items || Category) & Item/ Category=existing), then display newly added items or categories in the shopping cart.
4. TC04: To test, the Admin can view all the users registered in the system. Description: The Admin can view all the users who are registered in the system in the database. Input i.
User Name Alphanumeric, Password Alphanumericii. User==Admin iii. Selection==View Database Output: User List End messages/Result i. If( login type == “Admin” &Database.clicked = ‘true’ and list.clicked=true and userlist.exists=true), then display users. ii.
If (login type == “Admin” &Database.clicked = ‘true’ and list.clicked=true and userlist.exists=false), then display the empty database. 5. TC05: To test, the Admin can view the information about all users who successfully placed an order. Description: For the Admin, a database, which contains all information about the users, is created after each user checks out the items and successfully places an order. Input i. User Name ?Alphanumeric, Password ??Alphanumeric ii.
User==Admin iii. Selection==Database?Users Info Output: A database with the user’s information or an empty database. End messages/Result i. If (login type == “Admin” ;Checkout.clicked = ‘true’ and Place Order.clicked=true and userlist.exists=true), then display the database containing the user’s personal information. ii. If (login type = “Admin” &Checkout.clicked = ‘true’ and PlaceOrder.clicked=true and userlist.exists = false), then display the empty database.
iii. If (login type = “Admin” &Checkout.clicked = ‘true’ and PlaceOrder.clicked=false and userlist.exists=true), then do not update the row in the database. 6. TC06: To test that users cannot checkout with an empty shopping cart. Description: If there are no items in the shopping cart, the checkout button is disabled, and the users cannot click the checkout button. A user cannot check out with an empty cart.
Input i. User Name Alphanumeric, Password Alphanumeric ii. User==Users iii. Selection==View Cart No Items in the Shopping Cart Output: Disabled checkout button. End messages/Result If (login type == “Users” & Items . AddToCart = ‘false’ & ViewCart.clicked =’true’), then display the empty shopping cart with no items and a disabled checkout button.
ii. If (login type == “Users” & Items.AddToCart = ‘true’ & ViewCart.clicked =’true’ & Checkout.clicked == ‘true’), then display items in the shopping cart with the checkout button enabled so that users can check out. 7. TC07: To test that users are not able to submit an order form if the information in any of the fields is invalid.
Description: The users cannot place a successful order if any information on the order form is invalid (i.e., A zip code is a 5-digit number, so any non-numeric value will be invalid.) or if any of the information is incomplete or left blank. Input I. User Name Alphanumeric, Password Alphanumeric ii. User==Users iii. Selection==Checkout Order Form Place Order Output: User successfully or unsuccessfully places the order. End messages/Result I.
If (login type == “User” &CheckoutButton.clicked = ‘true’ and Order Form Information. Valid==’false’ or Order Form Information .Invalid==’false’ && PlaceOrder.clicked=true), then display an error message after the place order button is clicked. ii. If (login type == “User” &CheckoutButton.clicked = ‘true’ and Order Form Information. Valid==’true’ and Order Form Information.
Invalid == ‘true’ PlaceOrder.clicked=true), then successfully place the order and display the success message. 4.4: Result:This section listed the result , which is being taken by running the above mentioned test cases: Test Case Number Expected Result Actual Result TC01 Pass Pass TC02 Pass Pass TC03 Pass Pass TC04 Pass Pass TC05 Pass Pass TC06 Pass Pass TC07 Pass Pass Fig: Test Cases result Chapter No 5: Conclusion The project entitled FruitLand has completed successfully. The system has been developed with much care and free of errors and at the same time it is efficient and less time consuming. The purpose of this project was to develop a web application for purchasing items from a shop. This project helped me in gaining valuable information and practical knowledge on several topics like designing web pages using html & css, usage of responsive templates, designing of web applications, and management of database using firebase. The entire system is secured.
Also the project helped me understanding about the development phases of a project and software development life cycle. I learned how to test different features of a project. This project has given me great satisfaction in having designed an application which can be implemented to any nearby shops or branded shops selling various kinds of products by simple modifications. There is a scope for further development in my project to a great extend.
A number of features can be added to this system in future like providing moderator more control over products so that each moderator can maintain their own products. Another feature I wished to implement was providing classes for customers so that different offers can be given to each class. System may keep track of history of purchases of each customer and provide suggestions based on their history. These features could have implemented unless the time did not limited to me. Chapter No 6: References Websites/Papers Used for help: 1 JavaScript Enlightenment,Cody Lindley-First Edition, based on JavaScript 1.5, ECMA-262, Edition 2 Mc GrawHill’s , Java : The complete reference 7thEdition, Herbert Schildit 3 Complete CSS Guide ,Maxine Sherrin and John Allsopp-O’Reilly Media; September 2012 4.
http://www.w3schools.com/5. http://msdn.microsoft.com/6. http://agilemodeling.com/7. https://www.smartdraw.com/ 8. https://www.tutorialspoint.com/9. https://www.tutorialspoint.com/sql/
