Reference no: EM13752348

Assignment -1:

Read the following case study.

Sam is an IT manager of the ABC Supermarkets, a small chain of supermarkets in the Bay of Plenty area with stores in Auckland, Tauranga, Rotorua, Hamilton, Christchurch, and Queenstown. The supermarkets have their own computer systems that assist in the day-to-day operation of the business and are all linked to the corporate office in Auckland. The supermarket operates the normal suite of systems to take care of the supply chain management, inventory management, etc.

He would like to have an on-line shopping system for his customers as well as an order management system for his back-office staff. He believes that with these two sub-systems, he will be able to attract more customers, streamline business processes, and reduce company's operating costs. He has looked at several of the big chain on-line ordering systems in NZ such as Countdown and New World and found out that what he would like to have in the new on-line system.

You are to play the role of a system analyst brought in by the company to assist the company analyse and design their new system. You will need to understand the company's current activities and system by gathering all relevant information. Although there will be some in-class discussion, your team will need to develop a questionnaire to help gather the information required. Then, you will perform analysis and modeling of system requirements.

Read the narrative below concerning the way the company would like their new on- line shopping system to work. The system can be divided into two smaller systems: front-office system and back-office system.

1. Front-office system

The front-office system is used for a customer order process. A customer will use/interact with this system when purchasing products from the company. There are two sub-systems needed to be developed as part of the front-office system: Registration sub-system and Product order sub-system.

1.1 Registration sub-system

For a new customer, registration is required. To register, the customer enters her email address, password, name (first name and last name), home address (street number, street, suburb, city or town, and postcode), and telephone number.

1.2 Product order sub-system

From the product home page, she can browse through various products that we have for sale. She can choose a product category e.g., bakery, deli, fruit & vegetables etc. in order to find the product she wants. All products in a category are displayed. Each product needs to have the name of the product, a photo of the product, the capacity or weight of the product (e.g. 500grams, 2 litres), and the price. If she wishes to purchase the product, she selects the product, chooses the quantity wanted (1 by default), and then clicks on "Add to Trolley".

At any time she can click "View trolley" to see the contents of her trolley. The particulars of each product are displayed together with the total price. She can change the quantity of any product or remove it from the trolley. If she wants to proceed to checkout, she clicks "Check Out". To complete her checkout, she must do the following steps.

First, she needs to supply her email address and password to login.

Second, she needs to confirm her delivery details. The delivery details are displayed. By default the delivery details are the same as that supplied at registration. If she wants to send the products to a different delivery address, she puts in a new address. Then, she needs to select the date and time of the delivery.

Third, she needs to supply her credit card details. These include her credit card number, security code, expiration date and name on the card. By default the system displays the address at registration as the billing address. This can be changed if necessary. The details (credit card information, the total of the purchase, and the name of the store) are sent to the Bank for approval. Once the payment is confirmed, the order is given an ID number and the entire order with payment is displayed as a receipt.

2. Back-office system (also a back-office sub-system, as there is only one system)

Three times a day, the supermarket's back-office staff are sent an alert with all the orders that are needed for the next delivery. For each order, the system displays the delivery details (name and address) and a list of all the products that are ordered. For each product the quantity is given together with the location (aisle number) of that product. The products are ordered by aisle for easy retrieval. Once packed each container is labelled with the delivery address. The delivery person picks up the containers and delivers the orders. The customer signs for the order and receives a receipt listing the products, prices and payment information for that order.

Part 1: In-class/Team Participation

During the semester tutorials/labs, there will be time for your team to meet and work on assignment-related activities, which could be either individual-based or group-based. Your individual mark is given based on your in-class participation and work done in each class.

Part 2: Requirements Gathering

Develop a questionnaire or survey that will help you gather the information that you need to understand the company's current IT system and what is required to be developed based on the narrative above. Your requirement document should contain a range of questions in different styles that cover functional and non-function requirements. Each question must be related to a technical aspect of their current or future system.

Part 3: Requirements modelling

Part 3.1 A Use Case Diagram

Based on the information from the narrative and your questionnaire, draw a use case diagram for the new (entire) system.

Part 3.2 A Use Case Description

Write a Use Case Description (in a tabular format) of the customer order process

Part 3.3 An Activity Diagram

Draw an Activity Diagram that models the customer order process

Assignment -2:

Part 1: In-class/Team Participation (20 marks - individual assessment)

During the semester tutorials/labs, there will be time for your team to meet and work on assignment-related activities, which could be either individual-based or group-based. Your individual mark is given based on your in-class participation and work done in each class.

Part 2: Requirement Modeling using Data Flow Diagrams

Develop the following Data Flow Diagrams for the new system.

2.1 A Context diagram

2.2 A Level-0 diagram showing ALL sub-systems

2.3 A Level-1 diagram showing ONLY Back-office sub-system

Part 3: System Design

Choose ONLY one of the following design options. DO NOT attempt and submit more than one as only one will be (randomly) selected for marking.

• System Environment Design

Design system environment (architecture) to support the entire system. The system is to be deployed on the company's premises but securely connected to the Internet.

This includes in your report:

- a system design diagram including software and application, computer system and hardware, and network infrastructure, etc

- a detailed description and the reason/purpose of each design component

• User Interfaces Design

Develop user interfaces design for Product order sub-system.

- Identify all the web pages (Name each web page by yourself)

- Draw a website structure. The structure should show all the pages required by the system, menus, and a link from each menu to each of those pages.

- Draw a wireframe for each web page