Question

the case:

XYZ Pty Ltd is an established company (the 'Company') that has been selling hardware tools and paints for the last 30 years using traditional "brick and mortar" business model, based on tradesmen coming to the store and selecting the goods they want to buy. They are currently seeking to expand their business to include on-line catalogue with ability to be browsed, select items to be put in the shopping bag and to make an on-line payment with goods either being collected in the store, or shipped via a courier. The objectives are to increase the sales, to make it more convenient (time saving) for the tradies and also to allow non-trade people to shop on-line. Thy envisage 20% sales growth. The Company CEO provided the following very high-level and rough ideas for possible developers: For customers, they can browse the catalogue, explore particular item's details, add an item to shopping bag, change the number of items, add and delete items to/from shopping bag, select pick-up in the store or delivery to the nominated address and make an online payment or to send an inquiry to the store. Store personnel can respond to the inquiries and contact the customer via email or phone based on the details provided by the customer. Customers will also have the opportunity to rate and review goods purchased and service provided by the store. Store personnel will be able to respond to the customers' review. The Company wants to implement the first Minimum Viable Product (MVP) in the next six months and have secured an investment for this. Further investment to finalise the full version in the following six months will be provided on the basis of satisfactory assessment of the MVP implementation. XYZ has engaged you (i.e. a group of you) as the requirements analyst in this project.

BRIEF

1. Introduction 1.1 Purpose 1.2 Document conventions 1.3 Project Scope

2. Overall description 2.1 Product perspective 2.2 User classes and characteristics 2.3 Operating environment 2.4 Design and implementation constraints 2.5 Assumptions and dependencies

3. System features 3.1 Use case diagram make a decision as to whether a “flat” use case diagram should be included, or a hierarchical organisation of use case diagrams should be included. 3.2 Specification for selected use cases . Select n use case where n equals the number of students in your group. Document a detailed specification for the selected use case. The Use case must include the following elements as a minimum:-

ID and Name Created by Date Created Primary Actor Secondary Actors Description Trigger Preconditions Post conditions Normal Flow Alternative Flows Exceptions Priority Frequency of Use Business Rules Other information Assumptions

3.3 Swimlane diagram . Choose a process in the proposed app. Draw a Swimlane diagram for that process. 3.4 State-transition diagram . Draw a state-transition diagram for a customer job request in the proposed app. A job request is referring to a request initiated by the customer, e.g. “fix water tap leak”. Examine the various states such a request may be moved through. 3.5 Dialog map . Choose a use case other than the ones in 3.2. Draw a dialog map for that use case. 4. Data requirement 4.1 Logical data model . Include an Entity Relationship Diagram (ERD) for the proposed app. . 4.2 Data dictionary 5. External interface requirements

5.1 User interfaces . Including: 5.1.1. References to user interface standards or product line style guides that are to be followed 5.1.2. Standards for fonts, icons, button labels, images, colour schemes, field tabbing sequences, commonly used controls, branding graphics, copyright and privacy notices, and the like 5.1.3. Screen size, layout, or resolution constraints 5.1.4. Standard buttons, functions, or navigation links that will appear on every screen, such as a help button 5.1.5. Shortcut keys 5.1.6. Message display and phrasing conventions 5.1.7. Data validation guidelines (such as input value restrictions and when to validate field contents) 5.1.8. Layout standards to facilitate software localization 5.1.9. Accommodations for users who are visually impaired, colour blind, or have other limitations 5.2 Software interfaces 5.3 Hardware interfaces 6. Quality attributes 6.1 Usability 6.2 Performance 6.3 Security

Answer 1

1. Introduction
This document focuses on the system requirements of the proposed portal for hardware products.

1.1 Purpose
The purpose of this document is to build a Smart Shopping System to manage all aspects of hardware procurement for B2B and B2C segments.

This will involve a web portal with mobile compatibility across Android and iOS based platforms.

This document will serve as a guide of all the scope/requirements of the project starting from hardware, software and other resources.

1.2 Document conventions
Bold-faced text has been used to emphasize section and sub-section headings.
Highlighting is to point out words in the glossary and italicized text is used to label and recognize diagrams.

1.3 Project Scope
Create the MVP for on-line shopping facility with the aim of increasing customer convenience and spend. Extend the facility to cater to both B2B and B2C segments.

2. Overall description
2.1 Product perspective
A two-sided digital data platform that facilitates the process of hardware procurement from the store to bulk consumers and retail customers.

The software product being developed is for a web portal covering the end-to-end B2C and B2B shopping experience. It also provides analytics for managers, supervisors, and operators to access a wealth of information 24/7 from their desktop or from an internet-enabled mobile device.

2.2 User classes and characteristics

• The various user class who will be accessing this tool: Application Administrator for support service. (Super Admin access)
• Bulk consumers and hardware stores (for business use)
• retail consumers (for home use)

2.3 Operating environment
This application will be built using asp.net, IIS and windows server at the backend. The minimum hardware will be of a requirement of a basic web server with windows server 2012 R2 operating system which is the most up-to-date version of Windows Server available. SQL database for reporting and IIS service for sync.

2.4 Design and implementation constraints

• Compatibility with Mac O/S (El Capitan)/ Windows
• Portability to Android 4.4+
• Android Studio 2.1 and Java development

2.5 Assumptions and dependencies
•   It is assumed that the Consumer Portal will have the same use cases as those currently used in the physical store.
•   Availability of mobile devices and sensors for testing for a market release.

3. System features

3.1 “Flat” use case diagram with Specifications, Primary and Secondary Users, Pre and Post - Conditions:

Primary Processes HARDWARE ONLINE HCR - Hardware retail shop XYZ PTY. LTD. Primary Users Secondary User XYZ ONLINE SERVER WAREHOUSE ONLINE USERS • Users browse through items • Users add items to the cart • Users place orders and make online payment Online orders received Orders compiled Orders segregated location wise Wholesale & retail indents created • Payments collected using payment gateway Order placed on XYZ before cut-off time Order quantity and delivery details are shared

Secondary Processes XYZ Managed Activities From Suppliers HCR1 HCR2 XYZ main facility XYZ Retail Shops XYZ HCR... Back-end Managed Activities End customer bills ADVANT-TECH = XYZ ONLINE

Pre & Post Conditions XYZ PTY. LTD. XYZ 1.Providing SPOC for XYZ Online 2.Receiving online orders from HCOL 3.Sourcing hardware from warehouse 4. Transportation of ordered quantity to retail stores 5.Delivery of online ordered quantity 6.Providing space at XYZ retail store for order segregation 1.Collecting orders from online customers 2.Collecting online payments from customers 3.Compiling online orders with item, quantity & delivery location info. 4.Providing order details to XYZ main office by cut-off time daily 5.Checking quantity and quality before delivery 6.Segregating order for delivery to end customer 7.Handling and resolving XYZ customer complaints

3.3 Swimlane diagram

Customer Order Booking $ Provide Feedback/ Self-Service Requests Receive Supply Confirm Supply Return bags & damaged items Start Message Receive Online Portal Pass Payment Customer Feedback/ Self-Service Reg. Validate Order against Stock is Confirm Order to Bank/ Deduct from Wallet Provide Sale Orders Pass Refund Requests to Bank/ Add to Wallet Order Fulfilled End Provide Daily Payments list Confirm ayment Make Refunds Bank Portal

3.4 Sequence diagram

New User Registration User XYZOnline Server User DB Pmt Gateway Go to www.hcol.com HCOL home screen New user registration User rego, screen Create UID/PWD + CAPTCHA Validate Validate OK/Error OK/Error User ID. Success/NOK Delivery addr/contact details Validate Save Save OK OK User Regn Successful

Wallet Recharge User XYZOnline Server User DB Pmt Gateway Log-in Log-in Fetch user details user details/wallet bal user details/wallet bal. user details/wallet bal. Recharge/Amt Recharge/Amt w Initiate Payment Payment Success Update wallet bal. Wallet bal. Wallet bal. Wallet bal.

4. Data Requirement

4.1 Context diagram

PARTS PARTS SUPPLIERS INVENTORY RAISE PURCHASE ORDER RECENS ITEMS ELEC PARTSL DISTRIB UPDATE INVENTORY CHECK INVENTORY DESPATCH ITEM CONFIRM SALE ORDER RECENE SALE ORDER DESPATCHED SALES TEAM ITEMS

4.2 Data Dictionary

Data Dictionary [Hardware Parts] Field Name Field Size Part Code 6 Part Name 15 Part Qty 4 Part RO Lvl 4 Data Type Data Format Description Alphanumeric AAAA99 Item code Text Item name Integer NNNN Item quantity Integer NNNN Safe re-order level (minimum level) Example STMO12 Stepper Motor 5000 1000 [Sale Orders] Field Name SO No Field Size 6 Example 567123 Data Type Data Format Description Integer NNNNNN Sale Order Number Date/Time DD/MM/YYYY Sale Order Date Alphanumeric AAAA99 Item code SO Dt 10 15/06/2020 Part Code 6 STMO12 [Purchase Orders] Field Name PO No Field Size 6 Example 567123 Data Type Data Format Description Integer NNNNNN Purchase Order Number Date/Time DD/MM/YYYY Purchase Order Date Alphanumeric AAAA99 Item code PO Dt 10 15/06/2020 Part Code 6 STMO12 [Depatches] Field Name Desp No Field Size 6 Data Type Integer Example 567123 Data Format Description NNNNNN Despatch Number DD/MM/YYYY Despatch Date AAAA99 Item code Desp Dt Part Code 10 6 Date/Time Alphanumeric 15/06/2020 STMO12