Laptop Sale Management System by Using Chatbot, Lab Reports of Web Application Development

Download Laptop Sale Management System by Using Chatbot and more Lab Reports Web Application Development in PDF only on Docsity! Laptop Sale Management System by Using Chatbot Software Requirements Specification Version 1.0 Group Id: Supervisor Name 1. Introduction of Design Document This section contains all the necessary preparation that was required in order to make the implementation phase of this development as easy and efficient as possible. The section was broken down into a number of areas. The first discussed potential designs for data storage. This involved an analysis into normalization and how it would be implemented to improve data manipulation. The second section involved UML diagrams to identify all the use cases required for the final solution. ERD diagrams were produced for these use cases to assist understanding and thus provide a guide for implementing these features into the new system. The following section further discusses usability issues, followed by a look at and how counter measures could be implemented into the system. The system was analyzed and designed before implementation began. In this section, Entity Relationship Diagram, Sequence diagrams, Architecture Design Diagram, Class Diagram, Database Design, Interface Design and Test Cases webpage diagrams are described in details. 2. Entity Relationship Diagram (ERD) Entity An object in the real world with an independent existence. Attribute Property that describes an aspect of the entity. Degree Degree of relationship is the number of participating entity type. Cardinality Specify the number of relationship is instance that an entity can participate in. 3. Sequence Diagrams Reading a sequence diagram is very simple. Start at the top left corner with the "driver" class instance that starts the sequence. Then follow each message down the diagram. Remember: Even though the example sequence diagram in Figure 4 shows a return message for each sent message, this is optional. Basic The main purpose of a sequence diagram is to define event sequences that result in some desired outcome. The focus is less on messages themselves and more on the order in which messages occur; nevertheless, most sequence diagrams will communicate what messages are sent between a system's objects as well as the order in which they occur. The diagram conveys this information along the horizontal and vertical dimensions: the vertical dimension shows, top down, the time sequence of messages/calls as they occur, and the horizontal dimension shows, left to right, the object instances that the messages are sent to. Notation Customers Interface Class Diagram Active Class 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 Use visibility markers to signify who can access the information contained within a class. Private visibility hides information from anything outside the class partition. Public visibility allows all other classes to view the marked information. Protected visibility allows child classes to access information they inherited from a parent class. Association 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. Message Messages are arrows that represent communication between objects. Use half-arrowed lines to represent asynchronous messages. Asynchronous messages are sent from an object that will not wait for a response from the receiver before continuing its tasks. 6. Database Design 7. Interface Design Home Laptop Store Home Hp» Delly Samsung ~ Lenovo y Toshibar Accery — Contaét Us Contact With US 8. Test Cases T/C ID : 1 T/C Name: Create Account T/C Priority: “Medium” High ”Low” Preconditions: The User create a Account using email. SN Action Inputs Expected Actual Test Test Test Outcome Output Applicatio n result comments 1 Create Account @gmail.com Create Account Create Account PC PASS [ User 27/06/2019 Successful 2 Enter Create Account Create Account PC PASS User Email @mail.com Successful Successful 27/06/2019 ]: Password: **** Create Account Successful T/C ID : 2 T/C Name: Login T/C Priority: “Medium” High ”Low” Preconditions: The User/Admin login into the System. SN Action Inputs Expected Actual Test Test Test Outcome Output Applicatio n result comments 1 Login @gmail.com Login Login PC PASS User/Admin 27/06/2019 Successful 2 Enter Login Login PC PASS User/Admin Email @mail.com Successful Successful 27/06/2019 Password: **** Login Successful T/C ID : 3 T/C Name: Conversational Flow T/C Priority: “Medium” High ”Low” Preconditions: The Customers can Communicate through Chatbot. SN Action Inputs Expected Actual Test Test Test Outcome Output Applicatio n result comments 1 Conversati onal flow Conversation Conversat ional flow Conversat ional flow PC PASS User 27/06/2019 Successful 2 Enter Conversati onal flow Conversati onal flow PC PASS User Email @mail.com Successful Successful 27/06/2019 Password: **** Successful T/C ID : 4 T/C Name: Ask Question T/C Priority: “Medium” High ”Low” Preconditions: The Customers Ask Question through chatbot. SN Action Inputs Expected Actual Test Test Test