300585 - Systems Analysis & Design Workshop 6 Workshops will run to cover the practical aspects of the topic each week with two workshop case studies that runs across the whole semester and some other examples time to time. The workshop runs in two parts  Workshop slides  Workshop questions o This document contains two parts o Part A contains two case studies and questions that are to be done in workshop with the help of tutor ( to be done in Group of 2 students). Task 1 of this part would always refer to Willow brook Case study and rest of the tasks may relate to a continuous (UWS Transport Management System) or some additional case studies o Part B contains questions and tasks related to case studies that individual students need to answer in their own time and submit as a part of Portfolio(s) as per the due dates given in the Learning guide. Part A: Workshop work to be done during the workshop Design begins by a Story writing process by describing the steps to create a User Story for a made up feature. These steps are: break up the design; order, prioritize, and write the recipe. Before you proceed to the design phase, refer to the nonfunctional requirements (NFR) identified

in Analysis phase to see any NFR need to be factored in the design. These may include use cases or user stories that flesh out the higher level business requirements during requirements

identification. Design is based on and traced back to these NFRs. For e.g. Security(NFR) as a part of Login function (functional requirement) Analyze the User Interface (mockup) Following screen is the UI for Searching for a customer from the list of customers. Have a look at the mockup and understand the design considerations such as Spacing, Character limits, Header fonts, Functionalities etc. Step 1 - Break up the design This includes dividing the design into smaller chunks Even this simple design can be broken down into pieces. Pieces, that can be delivered individually (as long as an order is obeyed). In Agile, you can't deliver an incomplete feature, but you can

deliver a small part of a larger feature. There's a difference. A button that doesn't do anything when you click it is incomplete. A data table that you can view but not edit, for example, can stand on its own. The above can be broken down into the following segments /pieces 1. The table and its content 2. The search field 3. The edit and delete functionality

4. The ability to export Now frame each of the above as user stories 1. As a user I want to view the list of all the customers

2. As a user I want to be able to search for a particular customer (#1234 in below screen) 3. As a user I want to be able to edit and delete customer records (#1235 in below screen) 4. As a user I want to export customer data(#1236 in below screen)

Once you have broken down the requirement to different user stories label the mockup with the relevant user story. Then these user stories can be prioritized for design depending upon the requirements identified during analysis. Now see if user stories can have acceptance criteria for the developers to think about when designing the system Acceptance Criteria 1. Create a table with the following columns: Last Name, First Name, Address, and Phone 2. Add a level 3 heading title above the table with the label "Customers" 3. The Last Name, First Name, and Phone columns should include the last name, first name, and

primary phone number fields, respectively, for each customer 4. The Address column should be comprised of the following fields (in this order): street, city, state (abbreviated), and zip code (5 digits only). Wrap the text to the next line at 100 characters. 4. By default, order the table by customer last name (ascending) 5. Allow the table to be sorted by last name or first name In agile environments, less of the design is done upfront and more of it is delegated to component teams. The key is determining how deep to go initially, which decisions to defer and

identifying when decisions need to be made. Decisions that impact multiple development teams should be made earlier, especially scalability and security. For example Decisions like adding additional languages to an already internationalized product can be deferred until very late.

After the initial design is created, the architect works with each of the teams and reviews their designs. If additional design or design changes are required for a unit of work (such as a scrum

sprint), the architect aims to have it available by the time that unit of work starts. The architect is also responsible for communicating any changes to affected teams or stakeholders. Task 1 Case Study Willow Brook School Willowbrook School is a small private school that has retained your services as a systems analyst to assist in the development of a new information system for the school's administrative needs.

Background Willowbrook School has decided to precede to the systems analysis phase, based on the findings and proposal you presented after the preliminary investigation. Michelle the administrative assistant needs a UI to enter the student details where she can add information and edit them if needed and also generate a report on priority which contains the

following 1. First Name 2. Last Name 3. Address 4. Phone Questions 1. Considering the various steps you understood from an agile design perspective, design UI

for Michelle, identify various segments/pieces of the design and relate them to the User stories identified in workshop 4. 2. List the acceptance criteria for each of the user story. 3. List what aspects are to be considered for Agile design? Question 2

UWS Transport Management System UWS is experiencing a high number of student intakes and the immediate concern is the lack of adequate transportation facilities from major stations such as Parramatta. Further to this is the added complication of non-availability of free parking. The university is also considering offering

concession to students on their travel costs when using the OPAL card wherein a tap on tap off at the Uni bus stop is recorded in the system and every student gets a travel concession up to 40 dollars per month. One of the requirements that were identified was a need to enter the Student OPAL card details to the existing Student information system. The following are the requirements for the details to be entered into the information system.

1. Following details are to be captured in the system 1. Student Name 2. Student ID 3. Student OPAL card number 4. DOB 5. Campus

7. Course 2. School admin staff should have the facility to edit all details and extract an adhoc report if needed. 3. Admin to have the ability to search through records with Search criteria being any of the fields 4. Admin to have facility to filter and sort facility by Campus and Subject. 5. The adhoc report should be generated in less than 5 minutes from the time of request

6. Adhoc reports generated should be archived and stored for a period of 3 months post which they shall be deleted. 7. Admin staff should be able to edit and extract report subject to authentication of user name and password. All reports to be password protected Question 1. Design a User Interface (mock up) screen / report to enter the Student OPAL card details to the existing Student information system and explain the different activities you would

take to design the report from an agile design perspective? 2. What are the different types of non-functional requirements and identify the nonfunctional requirements from the above case study. Part B: Portfolio exercises to be included in Portfolio 2 submissions

Please note that Task1 of Part B is a continuing case study Task 1 On the Spot Courier Services Bill now faces a daunting task of having to implement an information system due to a growing need of warehouse management and distribution. You are a systems analyst and propose to have a new Warehouse distribution information system. Bill's immediate requirement is a daily

report of Items coming in and coming out of the warehouse. Bill wants the following to be present in the report 1. Package Identification Number 2. Package date in

3. Package date out 4. Handler name of Package in 5. Handler Name of Package Out Apart from the above Bill also wants to ensure that the report can be edited by the Warehouse

manager only. Access to edit is controlled by password authentication of manager login. Questions

1. Considering the various steps you understood from an agile design perspective, design UI for Bill, identify various segments/pieces of the design and relate them to the User stories identified in workshop 4 Use the example ( for customer details) given in Part A as a guideline and prepare the different activities you would take to design the report. 2. Why are non-functional requirements important to be considered during design phase? Task 2 Personal Trainer Inc

Personal Trainer, Inc. owns and operates fitness centres in a dozen Midwestern cities. The centres have done well, and the company is planning an international expansion by opening a new "supercenter" in the Toronto area. Personal Trainer's president, Cassia Uma, hired an IT consultant, Susan Park, to help develop an information system for the new facility. During the project, Susan will work closely with Gray Lewis, who will manage the new operation.

During requirements modelling for the new system, Susan Park met with fitness centre managers at several Personal Trainer locations. She conducted a series of interviews, reviewed company records, observed business operations, analysed the Bumblebee accounting software, and studied a sample of sales and billing transactions. Susan's objective was to develop a list of system requirements for the proposed system.

Fact-Finding Summary  A typical centre will 300–500 members, with two membership levels: full and limited. Full members have access to all activities. Limited members are restricted to only certain activities, but they can participate in other activities by paying a usage fee. All members have charge privileges. Charges for merchandise and services are recorded on a charge

slip, which is signed by the member  At the end of each day, cash sales and charges are entered into the Bumblebee accounting software, which runs on a computer workstation at each location. Daily cash receipts are deposited in a local bank and credited to the corporate Personal Trainer account. The Bumblebee program produces a daily activity report with a listing of all sales transactions.

 At the end of the month, the local manager uses Bumblebee to transmit an accounts receivable summary to the Personal Trainer headquarters in Chicago, where member statements are prepared and mailed. Members mail their payments to the Personal Trainer headquarters, where the payment is applied to the member account.

 The Bumblebee program stores basic member information, but does not include information about member preferences, activities, and history. Currently, the Bumblebee program produces one local report (the daily activity report) and three reports that are prepared at the headquarters location: a monthly member sales report, an

exception report for inactive members and late payers, and a quarterly profit-and-loss report that shows a breakdown of revenue and costs for each separate activity. The entire set of reports is processed in one hour with a data transfer rate of 1MBPS and utilises 70 percent CPU. Personal trainer is considering upgrading the system to improve efficiency. Questions 1. From the above information identify activities that can be classified as Online and batch processing?

2. From the above information and the system requirements identified in workshop 4 for this case study, identify three non-functional requirements which you would to potentially consider when designing the system.