Analysis and Design, Project 1 Rough Initial Draft of the Requirements Document Prerequisites Before starting your draft, review the following documents 1. Exhibit A below- the class presentation and handout by the sponsor of the project. 2. Writing good requirements- guidelines, class handout #3 3. Use case modeling lecture notes 4. Sample requirements document and layout- the Virtual Art Viewer Requirements Documents Project 1 Assignment Now that we have a complete understanding of how to write requirements and explored use case modeling techniques and their benefits, write a rough initial draft requirements document according to the outline presented in the Virtual Art Viewer Requirements Document. The sections of the document with the highest priorities are: Functional Requirements, Other Requirements, Executive Summary, and Software Qualities. Suggested Activities: 1. Identify the actors, use cases, and relationships that define the requirements for the proposed system and document that information in a Use-Case Glossary. 2. Write a rough initial draft of the requirements of the system described in Exhibit-A. Focus your writing efforts on the following sections as follow: Functional Requirements Section (high priority); make sure you use your work on your use cases to structure the requirements in this section. Other Requirements, Executive Summary, and Software Quality Discussion Board: A discussion board is created. If you have a question, please use the discussion board to post your comments and questions to the whole class. Exhibit A- The project sponsors class presentation. Statement of Purpose: Purpose of this document is to provide better understanding to the reader so that it can be converted into an efficient SRS documentation. Opportunities: We are providing an opportunity to the students for creating an SRS Document for business software that will be moved to the production. This gives you a chance to practice your skills and be a part of building a business software at the very beginning. Directives: - User means Cashier - Transaction means selecting multiple items for purchase or return or both and finishing it to the successful checkout. Functional Requirements: 1. System should allow user to log in into the POS. No transactions can be executed without active user. All the transactions will be associated to a user(cashier) 2. Admin user should be able to track and generate various reports based on transactions performed by all the users. 3. It should either select the product by scanning the barcode, allowing to enter upc code manually or it should allow manual selection from the inventory item list. 4. System should allow user to do return(refund) along with regular transaction. E.g. if a customer is returning 1 item and buying 5 new items, all that should be handled in single transaction. 5. Allow customer to use multiple payment methods 6. Allow user(cashier) to select an option for splitting single transaction using multiple payment methods.(Upto 6 splits in single transaction) 7. Allow user(cashier) to hold the current transaction and recall the same transaction when needed. E.g. if customer 1 is not ready for payment, cashier should be able to put that transaction on hold and start serving customer 2. Cashier will finish the transaction for customer 2 and then recall the previous transaction (for customer 1) and finish that one. 8. Allow user to remove items(s)/update item(s) count from the transaction before going to checkout. 9. It should allow user(cashier) to manually enter the cash amount received from customer to show Change-Due when cash is used for payment method at checkout. a. Allow user(cashier) to select the exact change 10. System should allow user to update the inventory when new stocks are received at the store. 11. When entering an item in the inventory, allow user to select department, vendor, cost, location(aisle), expiration date(if available), quantity etc. 12. Allow user to manually enter the price from the system prompt in case price isnt displayed automatically. 13. It should automatically calculate the taxes for the item in case they are present in the item record. Otherwise it should allow user(cashier) to select the tax category and taxes will be calculated accordingly. a. In case user(cashier) wants to select different tax category for automatically fetched tax, it should allow manual override. 14. At the successful transaction, it should print the receipt and open the cash drawer (in case of cash payment with non-zero amount). 15. For return/refund, when the item is scanned, system should show all the customer who bought the item. User(cashier) will select the correct customer and the refund will be sent to the same card (payment method) that was used at the time of that specific purchase. a. In case when splitting was used originally for the transaction and that item is being returned, the refund amount goes to first payment method. b. In case when customer is purchasing items while returning the other items, the total should reflect the refund amount. And customer will be eligible for paying newly updated price only. i. In case the price is negative (refund amount is higher than the purchase cost), then the refund goes to the first payment method used for purchasing the items that are being returned. 16. Customer can opt for house charge account which will have certain max limit. This account will keep track of amounted owed by customer and paid by customer meaning, customer doesnt need to pay due amount at every transaction but he/she can pay at their convenience and/or the due amount reaches the max limit. a. Admin can set max due amount for each house charge account separately. b. If customer pays more than what he owes, the credit will be reflected in the house charge account. 17. User should be able to select the customer from the customer database and should be able to add new customer. a. User should be able to search the customer by name, last name, phone number etc. b. This is not mandatory for all the customers meaning, customer detail section will be Null by default at every transaction. Non-Functional Requirements: 1. There will be multiple terminals the system should use 1 central local server which will be connected to all the terminals. 2. The transactions should happen parallely, and ACID properties should meet when there are concurrent transactions. 3. In case of critical failure/system crash there must be some backup that restores system and data so that there is minimal loss. Q&A with students:

My question is what would be Environmental Requirements, Other Requirements, Software Qualities, References ?