Case Study: Australian Fashion Designs
Background:
Australian Fashion Designs (AFD) is a Brisbane based business with design offices in both Melbourne and Sydney which has traditionally sold women's clothing to retail outlets through sales representatives, and wedding dresses directly to customers through wedding representatives. The business works with two fashion clothing manufacturers in China and New Zealand, with delivery through the postal service.
The sales representatives are given their own retail stores to work with. This is so stores who are selling AFD products are not approached by more than one sales person.
Depending on the number of stores, more than one sales representative may be assigned to one sales area. The retail stores are charged for the product at the recommended retail price less a discount. The amount of this discount varies according to the volume of stocks bought by the store and is normally assigned by the sales representative when they gain a new client.
The wedding representatives also sell the dresses at recommended retail less a discount which is the same for all wedding representatives. As these wedding representatives sell to private people rather than businesses, AFD does not want to keep a record of who they sell to. They must pay for any orders at the time they order however the head office wants to be able to see a total of how much they order every year. Depending on the volume of orders, more than one sales area may be assigned to one wedding representative.
The business was started by the business owner, Julia Spencer who initially undertook all the ordering and selling however the business has now grown to include both part- time and full-time employees. The organisation is also looking to expand further into men's clothing. Currently the business still has manual stock control and customer relationship systems which have worked well in the past and an off-the-shelf accounting system which is used to manage the accounts receivable and accounts payable of the business.
Although the off-the-shelf accounting package is used and email for communication with suppliers and customers, there is currently a low level of computer use in the organisation. The sales people (both sales representatives and wedding representatives) use an AFD supplied phone and their own laptops, tablets, etc. to take and keep track of orders. The sales people phone orders in to head office and telephone to check on the progress of orders. This means that currently some staff at the head office almost exclusively handle telephone calls from sales people. These phone calls are often lengthy as some sales people only phone their orders in once a week, which concerns Julia Spencer as she does not know the value of the daily sales of each sales person, or who they are visiting as the sales people control their own schedule.
Although the manual systems for stock management and customer relationship management have worked in the past, Julia Spencer and the new purchasing manager Nicolas Steven and the customer manager Sheela Brown feel an information system could offer significant improvements to the work processes currently in place.
Sheela Brown would like the sales people to order products online as they make the sales. One of her requirements would be to enable the sales people to "check in" online at every retail outlet they visit whether they make a sale or not. This is so she can check
what sales calls they make. The sales people are concerned that this takes away the autonomy that they currently have. On the other hand, Nicolas Steven would like to run a report once a month that shows stock levels and how long each product line takes to sell. He would also like to make bigger orders more often to take advantage of smaller shipping costs per piece of merchandise and bulk ordering discounts offered by their suppliers.
Business Processes:
A JAD session with key stakeholders revealed the following information. The business processes described below are the system requirements for this information system solution:
• It has been decided to focus on building and implementing the Customer Relationship Management (CRM) application and run a separate project for the purchasing project later. Therefore, do not model any of the purchasing system (this is where AFD purchase from their suppliers).
• Before a retail store can become a customer of AFD, they must fill in an application form. Applications are reviewed by the management team and not all applications are approved. AFD records the following details for all customers: Name, Address, Telephone, Email, Application date, Discount level, Sales area, and Date last visited. Additionally, AFD records Australian Business Number (ABN) for retailers only (not private customers).
• The geographical sales areas for the sales people have been defined for the whole of Australia using current population numbers. However, AFD does not yet have enough wedding representatives to cover all of Australia so some sales areas do not yet have a wedding representative assigned while some wedding representative are assigned to more than one geographical sales area in cities such as Melbourne.
• AFD wants to run a sales report on the last day of every month that shows the amount of sales, per sales area and per sales person.
• AFD also requires that the following information on each sales visit be kept, the customer, the date of the visit, sales people(s) who visited, and amount of order. Please note for unsuccessful sales visits to potential customers, it is planned that the customer is identified as "potential customer" when their record is created for each geographical sales area to track these visits.
• The wedding representatives are expected to manage their own customers and work load so AFD does not store any details of the weddings held.
• Any payments for salaries or expenses to sales people are outside the scope of this system
Part A
Task 1: Report
The AFD management team has heard of agile and iterative systems development methodologies but is unsure of their effectiveness for their project as there is little knowledge about these in the organisation. Therefore, they want you to write a report discussing the four (4) various methodologies of agile and iterative developments. State under what circumstances each one would be used and then make a recommendation for this project. To do well in this report you must use the detail from the case study in your report as examples, rather than given general information.
The following sections need to be included:
o General introduction to the agile and iterative methodologies.
o Methodology 1
- General discussion
- Advantages
- Disadvantages
o Methodology 2
- General discussion
- Advantages
- Disadvantages
o Methodology 3
- General discussion
- Advantages
- Disadvantages
o Methodology 4
- General discussion
- Advantages
- Disadvantages
o Recommendation
Your target audience is executive business people, who have extensive business experience but limited computing knowledge.
Your report should be no less than one thousand (1000) words and it would be best to be no longer than one thousand five hundred (1500) words long. Appropriate referencing is required. The textbook Satzinger et al. is a valid resource, however it is expected that at least five (5) other resources will also be used and cited.
Task 2: Memo
Review the AFD case study and complete the following task with reference to the information in the case study.
Currently there is not a strong reliance from AFD on computers to get their work done outside standard applications. Therefore, acceptance of the new system is a concern for the management team. They have requested that you write a brief memorandum commenting on adopting a User Centred Design (UCD) approach and setting a plan for the development of the Human Computer Interaction (HCI) when considering the CRM application. Briefly discuss UCD and HCI in general and investigate the implications of adopting a UCD approach on the project, introduce your plan supported by the principles of UCD and HCI, and then state why you would recommend this plan. You are expected to use theory in your response.
Your target audience is executive business people, who have extensive business experience but limited computing knowledge. Attach this memo to your report from Task 1 as an appendix.
There is limited information available to you now but you are required to make reasonable assumptions based on the information that you have. Assumptions should be noted and specifically mentioned within your memo. Your memo should be no less than seven hundred and fifty (750) words and it would be best to be no longer than one thousand (1000) words long.
Part B
Modelling and Diagramming
Review the AFD case study and complete the following tasks with reference to the information in the case study.
Do NOT extend the scope for any of the following solutions beyond that specifically described in the case study above.
You are permitted to make reasonable assumptions where necessary but these should be noted.
It is recommended that you review all documentation for this case study before finalising any single solution. Ensure that the required consistency has been included within and between each task solution. You may use a tool such as Microsoft Visio or www.draw.io to draw the models or neatly hand draw and scan into a pdf document. However, you should submit only one document.
Task 3: Event Table
Review the AFD case study and prepare an event table for the information system to support the business processes as described. Use at least the following headings for the event table:
|
Event
|
Event Type
|
Trigger
|
Source
|
Activity/Use Case
|
System Response/
Output
|
Destination
|
Task 4: Domain Model Class Diagram
Review the AFD case study to prepare a domain model class diagram for the supporting information system.
Solutions must follow the methodology as outlined within the Satzinger et al. textbook. Solutions are expected to show:
• The class name and attributes list for each class and sub class as required
• All required associations
• All attributes as specifically mentioned in the case study must be reflected
• Other attributes as needed to support the described functionality.
It is not necessary to show methods, however you may include them if you wish. Solutions are expected to align with the components as shown in Figure 4-23 of the Satzinger et al. textbook.
Task 5: Design Class Diagram
Prepare a Design class diagram for the Sales Representative and Order classes ONLY. These classes should be part of the Domain model class diagram solution for the previous task.
Each of these design class diagrams are expected to have a complete attributes list and a comprehensive methods list which supports the specified functionality as described in the case study.
Solutions must follow the methodology as outlined within the Satzinger et al. textbook. Solutions are expected to align with the components for the ‘Design class diagram for Student' as shown on the right hand of Figure 12-4.
Task 6: Use Case Diagram
Review the AFD case study and your event table solution from Task 3 to prepare a Use Case diagram for the supporting information system.
Solutions must follow the methodology as outlined within the Satzinger et al. textbook. Solutions are expected to align with the components as shown in Figure 3-12 and 3-15.
Task 7: Use Case Description (intermediate)
Prepare a Use Case intermediate description for the 'Takes Order' use case, as documented in the event table solution and the use case diagram solution.
Solutions must follow the methodology as outlined within the Satzinger et al. textbook. Solutions are expected to align with the components as shown in Figure 5-2.
Attachment:- Systems Analysis.rar