Reference no: EM133106807

CMPS 303 Object Oriented Systems Analysis and Design - Southern Alberta Institute of Technology

Requirements Analysis

Title Page
- name of system, group members, date, client(s), instructor(s)

Name of System:
Tasty Food Web Application

Group members:
o Eshetu Tiku
o Kinza Martin
o Mehari Brhane
o Azmatullah Khan
o Dhaval Vadalia
o Gurjivan Cheema

Table of Contents
- including figures, tables, and appendices

Preface
Purpose of Document
- What is this document about, what information does it contain that a reader might be interested in?

• This document provides information about the Tasty Food business and their businessneeds related to their Information Technology requirements.
• Details of the system requirements.
• Meeting minutes of the meetings with client.
• Details of the system development from end to end.

Documentation Standards (javadoc??)
- special notations used in this document, e.g. use of fonts and colours (do not give a detailed explanation of UML)

• Use of Times New Roman size 14 for headings and size 12 for paragraphs and
subheadings
• Standard spacing 1.0

User Requirements

Business Overview and Objectives
A local business which prepares home-made food products with locally sourced
ingredients delivered to the people who have a busy schedule. The business currently has
single orders as well as subscription ordering models and wants to expand their customer
base through social media and increasing their online presence.

Project Overview
Statement of the Problem
The business owner wants to increase their online presence through marketing on social media as well as develop an IT (Information Technology) tool to manage orders, billing, and inventory.
Project Scope
- summary of major functional requirements of the system as determined in your conversations with your client.

- NOTE: for the purposes of ITSD you include the functional requirements of report generation and backup and restore from within the system as functional requirements, even if the client does not mention them

• Report generation
• Backup and restore
• Process order
• Order received and order delivered notifications
• Process the charge to customer
• Create receipt
• Capture customer feedback
• Show order status from order received to order delivered
• Update customer information
• Update product information

System Environment
- environment in which the system will be implemented. Interested in the business/industrial environment the system will operate in here, not technical details like OS, database, etc.

Home-based food preparation retail business catering to local postal codes

Current System
- If the client has an existing system that you will be replacing or expanding, describe it here

Currently utilizing Facebook marketplace and phone orders/phone billing.

System Requirements
[Remove Fact-Finding Methodology section]
Use Case Diagram
- Updated UML use case diagram to show any additions or changes in the original set of use cases you identified in the previous document.

Use Case Descriptions and Scenarios
- Actor role definition, i.e. what types of users will your system have? Describe briefly what each actor does
- Updated use case descriptions in the brief, essential format as required(note the words "brief" and "essential"; see the module 3 slides for details on what these terms mean).
- A separate description is needed for each use case in your use case diagram

• Owner: The Tasty Food, can manage any required updates and maintain consistency of the applications use

• Customer: can login with their accounts and view food items and order food through the web application.

• Manage Account: customer creates an account that will be used for personal information, such as full name, email address, phone number, address, and other details. The account is used to verify and update customer personal information. The customer can also update and delete account information.

• Account Login: Customers can login to access their previous orders, make changes to their information and make new orders. Owner also login to admin account to generate report, update product info or customer data etc.

• Place Order: customer can place an order through web application after sign in.

includes: Search Menu: a customer searches for a food name and selects the items from the menu list.

extends: Make Payment: Once the order is placed then the customer can pay via credit, debit card.

• Generates Report: Owner can generate a verity of reports such as daily or weekly sales reports etc.

• Update Product Information: Owner can update the product information like change in price, add, edit, delete product etc.

• System Maintenance: The owner maintains any simple security flaw or report to temporary admin.

• Update Customer data: Owner can update customer data like contact number, address change etc.

• Managing order: Owner can maintain orders like if orders are pending, they can email customers for ordering food.

Non-Functional Requirements
• Information about how the application must do some things, e.g. performance constraints, adherence to legislation on data handling, security requirements, etc.
• Secure access to confidential data (user's details)
• The online payment system shall be available for use between the hours of 11:00 a.m. and 9:00 p.m.
• The system shall achieve 99.5% up time
• Better component design to get better performance at peak time
• More payment gateways
• This list is by no means a final one. The final list will be dictated by implementation constraints, market forces and most importantly by customer demands
• Performance requirements
• The system shall wait for all user inputs and execute only the necessary functions given a user input to the system. All functions shall be completed quickly.

• The system should accommodate a high number of items and users without any fault
• Responses to view information should take no longer than 2 seconds to appear on the screen
• The web application should handle expected and non-expected errors in ways that prevent loss of information and long downtime periods.
• Safety requirements
• System use should not cause any harm to users.
• Security requirement
• System will use secured database
• Normal users can only read information, but they cannot edit or modify anything except their personal information
• Customers shall be forced to change their password the next time they log in if they have not changed it within the length of time established as "password expiration duration"
• Passwords shall never be viewable at the point of entry or at any other time
• The access permission for system data may only be changed by the system's data administrator
• The system shall be accessible by people who are color blind, to the extent that they shall be able to discern all text and other information displayed by the system as easily as a person without color blindness

System Interface Requirements
• Not about the "user interface"! Is your system going to interact with any other systems, e.g. accounting software, inventory control software etc.? A database program used by your application is not considered a separate system in this context
• Interact with /debit/credit charges and banking system
• Various interfaces for the system could be
• Login page
• Registration form
• There will be a screen displaying information about food products.
• If the customers select the order now button, then another screen of menu list page will be opened
• After ordering food products, the system will send one copy of the bill to the customer's email address
Maintainability and Administration Requirements
• Maintainability: Will your system need to be updated/extended after the initial version is deployed? How will you plan for that?
• Administration: What are the system administration requirements for your system, e.g. must provide for easy user account administration, backup and restore, etc.?

• Maintainability: As a business website the system may add more functional and non-functional features to stay competitive. It may also update features that are not relevant for the business. To maintain the system easily, we will design a well loosely coupled system and subsystem will communicate using high level API (Application Programming Interface).

• Administration: Cloud-based remote login to access the system. The system will include features that will allow the client to generate reports about daily or weekly visitors and how many of them order.
Usability Requirements
• Analysis of HCI requirements. How experienced are the expected users of the system? Inexperienced users will probably need you to provide more feedback and support than experienced ones. If you have both types of users how will you support the needs of each group?
• Here's where you consider the user interface requirements for your system

Attachment:- Object Oriented Systems Analysis and Design.rar