Software Engineering - Online Reservation System - Assignment Example

Requirements Documentation: World Wonders Reservation System Other Product Requirements Applicable Standards FEAT25 WorldWonders applications will have to comply with standard web user interface such as Google Chrome and Microsoft Internet Explorer (Wysocki, 2010). System Requirements FEAT26 The web application will work on all operating systems the above mentioned browsers can work with. Documentation Requirements Online Helpdesk FEAT5 The web site will include an Instant message service interface that works on all applications. Use Case Diagram Introduction This document is used to keep terminology that must be used in an accurate manner in the context of the WorldWonders.com Reservation system project, in order, to maintain proper communication within the involved team. Purpose Team members should collect all terminologies that they believe should be used with a high degree of clarity (Wysocki, 2010). Scope Terminologies within this document hold only to the WorldWonders.com Reservation system project, the language may or may not be different from the language used in other projects by WorldWonder Inc. (Dina Berkeley, 2007). Definitions Administrator An administrator is defined as an employee of WorldWonders Inc., who will be responsible for observing and maintaining the conditions of orders, modifying the databases containing the customers and cars for hire, among other activities. Customer The Customer is defined as one who owns a valid CustomerID and password on the directories with WorldWonders Inc. Catalog The catalog includes all products and services that are available for reservation on the WorldWonders.com Website. CustomerID This is used to identify the customers and the administrator. Reservation Cart The reservation cart is the general term for the container of all products and services that have been selected for supply. Visitor A visitor is defined as a user who visits the WorldWonders.com Website. Customers could also be regarded as visitors if they were just browsing through the site and did not visit the Cashier page. Introduction Purpose This document describes non-functional requirements that are adopted in the overall WorldWonders.com Web System projects. Scope This document applies to the WorldWonders.com Web App. Functionality This Use case specification specifies all the functionality in the system. Check the use case specifications for more details. Usability This section involves all of those system requirements that affect usability. Interface Ease of Use SUPP1 The system shall follow standard interface guidelines. The system shall be able to exercise its functionalities on Internet Explorer 4.0 and thereafter on Netscape Navigator. SUPP2 The system shall be user friendly. SUPP3 Training SUPP4 This shall be availed for all modules of the system. Reliability Defects The number of acknowledged defects in the deployed system shall be less than 50. Fault Tolerance The system shall be able to exercise its functionalities on Internet Explorer 4.0 and thereafter on Netscape Navigator. SUPP5 The system shall be able to operate in a fault tolerant manner 7 x 24. Performance This section outlines all the performance characteristics of the system. Supportability This segment indicates any specifications that will enhance the maintainability or supportability of the WorldWonders.com Web System. Response Time SUPP8 For any query, the response time shall be less than 10 seconds. Coding Standards SUPP9 The system shall be Internet Explorer 4.0 and thereafter Netscape Navigator compliant as indicated in the Netscape Navigator and Microsoft Internet Explorer compatibility requirements documents. UC7 Brief Description The arrange reservation use case is an extension of the Check-in use case and generates a summary for the depository system. The depository system is considered an actor in this use case scenario (Dina Berkeley, 2007). The information produced by this should be all the required information needed to place the reserve and make a reservation of the service(s) for the customer Flow of Events Basic Flow UC7.1 Upon successful completion of the Check-in use case, the entire reservation information will be sent to the depository system. UC7.2 The Web reservation software sends information in the form of a statement that can be parsed electronically by the depository system (Dina Berkeley, 2007). The report includes the following information: UC7.2.1 Customer name UC7.2.2 Customer address UC7.2.3 Customer phone number UC7.2.4 Product reserve number for each product reserved UC7.2.5 Customer ID UC7.2.6 Quantity of each product reserved The depository system responds with the estimated availability time for the product(s) in the user’s reservation cart in the system. Alternate Flows Inventory not available In case that some, or the entire inventory is not available, the depository system provides a report to the web page stating that the product (s) is (are) out of stock or unavailable. Special Requirements None Pre-Conditions A customer or client must order or book at least one product or service and proceed to the Cashier page to complete the check-in process. Post-Conditions None Extension Points Arrange reservation is an extension of the Check-in use case UC4 Check order status Brief Description UC4.1 Customers and administrators can view the conditions of their reservation(s) by entering their CustomerID and Password. They can then see a summary of their reserves. From the review, users can display details of any reservation, including what was reserved, and the amount charged for the reservation. Flow of Events Request Order Status The use case shall commence when the user clicks the subject, Orders, to check on the conditions of a previous reservation. Provide CustomerID and Password The system shall display a page on which the client enters his or her CustomerID and Password. Show Existing reservation The system shall display a list of all reservations placed by this user; the system shall sorts the listed reservations in ascending order by the number of reservation. View Order Details UC4.5 To see the details of a specific reservation, the user clicks on an OrderID. UC4.6 The user clicks a Title to view details of a specific product On the Order Details page. The product details include: Picture of the reserved element Name Title Price Reservation representative of the order Service area location Use Case Completion/end UC4.7 The use case ends when the customer begins the Browse Catalog use case, or leaves the WorldWonders.com Website. Alternative Flows UC4.8 User enters an invalid CustomerID and/or Password UC4.8.1 If the customer or administrator enters an invalid CustomerID and/or password, the program will displays a message indicating that the CustomerID/Password combination is not correct or valid. UC4.8.2 The client clicks the browser’s Back button to return to the CustomerID/Password entry page (Dina Berkeley, 2007). Special Requirements Not available Pre-Conditions UC4.9 The customer or administrator must have a valid CustomerID/Password combination Post-Conditions Not available Extension Points Not available o reservation UC2 Do reservation Brief Description UC2.1 The user can select and reserve a product or service from WorldWonders This Do reservation use case is an extension of the Browse Catalog use case in the system. Flow of Events Select a product/service UC2.2 The use case starts when the user indicates the desire to reserve one or more items by clicking on the reservation cart icon next to the product or service. products may be added to the reservation cart from the catalog page or any specific view page. UC2.3 To place more than 1 of a product in the reservation cart, the user clicks the reservation cart icon for that product several times. Place Item On List UC2.4 Each time the user clicks on an item’s reservation cart icon, the system places that product or services on an internally-maintained list. The system does not provide the customer with any visual feedback. View reservation Cart UC2.5 The customer examines the contents of the reservation cart by clicking on the link text, reservation Cart. Proceed to Checkout UC2.6 The use case ends when the user clicks the link text, Cashier, to complete the reservation. Alternative Flows UC2.7 Remove a product from cart UC2.7.1 On the reservation cart view page, the user may remove a product or service from the carriage by choosing the Remove from Cart link next to each selection in the reservation cart. Special Requirements None UC19 Here is subject for a Parent or Root requirement. UC19.1 Use this subject to create a Child requirement. UC19.1.1 Use this subject to create a Child requirement of the Child requirement directly above. Pre-Conditions UC2.8 The customer is in the detailed view or catalog view the when the use case starts. Post-Conditions Not available. Extension Points This use case is an extension of the Browse for resource use case. UC1 Browse Catalog Brief Description UC1.1 The user can look for available services/products and filter results by performer, composition, and composer. Any additional information related to the primary and alternative flows is contained in the sequence and activity diagrams in the WorldWonders.com Rose design. Flow of Events Basic Flow UC1.2 The browse catalog use case begins when the user displays the WorldWonders homepage UC1.3 The system presents an alternative to browse the catalog of products and services UC1.4 The system also presents a better selection of the day. UC1.5 The user clicks the “catalog” link UC1.6 The system presents a list of all available services and products UC1.7 The user looks at the details of a service by selecting the link to its title UC1.8 The system displays the following information: UC1.8.1 Picture of the item UC1.8.2 Product title UC1.8.3 Reservation representative UC1.8.4 Service/product situation UC1.9 This flow finishes when the user goes back to the homepage and chooses another option or closes the browser session. UC1.10 Search by selected criteria UC1.11 The user searches through the catalog of all available services and products by first selecting one of the following choices from a list. UC1.11.1 Composer Performer UC1.11.2 Composition UC1.12 The user enters text into a search field then clicks the Search button. UC1.13 The system displays a list of products/services that meet the user’s search criteria Special Requirements None Pre-Conditions TC15 This use case must be initiated from the WorldWonders homepage. Post-Conditions None Extension Points The Shop for reservation use case is an extension of this use case. UC3 Checkout Brief Description UC3.1 Valid customers have the option to reserve a service or product that they have added to their reservation cart. Flow of Events The use case starts when the user selects Cashier from the catalog, detailed view, or the reservation cart. The customer proceeds to the Cashier to book or reserve The system requests information to validate the customer and the customer, provides that information. UC3.3 The system requires the user to enter the following requirement: UC3.3.1 CustomerID UC3.3.2 Password The system displays a summary of the current order. UC3.4 The system displays a summary of items in the reservation cart, including the following details from the user’s membership records: UC3.4.1 customer address UC3.4.2 The digits of the customer’s credit card An estimate of when WorldWonder will avail the product. UC3.4.3 The total amount that WorldWonder will charge to the customer’s credit card. The customer verifies his or her e-mail address. UC3.5 The system prompts the customer to confirm their e-mail address. The customer completes the request. UC3.6 The user clicks a button to complete the order. The system confirms the order. UC3.7 The system displays a confirmation that the reservation has been placed and provides a reserve number for future reference. With the reservation completed, the user may visits the catalog or leaves the WorldWonders.com website. UC3.8 The use case ends when the user leaves the order confirmation page on the site. Alternative Flows UC3.9 No order placed UC3.10 The user could browse back to the home page, leave the WorldWonders.com site, or end their browser session. UC3.11 Empty cart UC3.12 If the user’s reservation cart is empty, the system displays a pop up message that indicates that the user has not selected any items to reserve. The use case ends. Special Requirements None Pre-Conditions UC3.13 User must already be an official member of WorldWonders.com with a CustomerID and Password. UC15 customers must have added at least one product to the reservation cart. Post-Conditions None Extension Points None References Dina Berkeley, R. d. (2007). Software development project management:process and support. Michigan: Ellis Horwood. Wysocki, R. K. (2010). Effective Software Project Management. Michigan: Wiley. Read More