Write a Business Analysis Report, for a business case study. This report will include business requirements documentation with modelling artefacts such as:  The assignment comprises of two parts (Part A, worth 10% and Part B, worth 20%). You will give an oral presentation of your assignment at the end of completion of your assignment.   You are given a generic case study (see Appendix), which you will adapt to a particular industry scenario ofyour choice. The first part (Part A) of this assignment is to critically analyse different types of business problems and the contexts in which they exist in this chosen scenario. The discussion will take the form of a well-researched and justified Business Analysis Preliminary Report, containing an introduction to the scenario, identifying the problems and recommending the appropriate business processes for a prototype system as a solution.  The main purpose of the exercise is to analyse the requirements of the case scenario and identify end-to-end business processes using business object oriented modelling (BOOM) framework and techniques in order to arrive at a plan for the suggested system.  With this preliminary business  analysis you would develop for Part B, the final business requirements document with detailed set of  artefacts for the suggested system.  You will use SAS Studio/ SAS Enterprise Miner to draw the process flows. Your report should be well supported with in-text citations and full references from respected sources. You should include academic journals, books, theses, trade magazines and well-respected sources of related Internet material as you find to be relevant. There should be a minimum number of FIVE (5) relevant references in your report, and only ONE (1) of these sources may be from a website.  You must follow proper Harvard style referencing; including inline citation.   

Part A deliverables to be included in the Business Analysis Preliminary Report:(DUE WEEK 7 – 10%)Recap the Steps of B.O.O.M:Initiation: Make the business case for the project. Work also begins on the user experience and on drafts of architectural proof of concepts. The prototyping effort during the Initiation phase should be risk-driven and limited to gaining confidence that a solution is possible. As a business analyst, you will carry out the following steps in BOOM for Part A:

1a) Model business use cases

1b) Model system use cases

Please attach a copy of the Marking guide to your hardcopy of submitted report.   

For Part B, you will carry out the following steps in BOOM: 

1c) Begin structural model (class diagrams for key business classes)1d) Set baseline (BRD/Initiation) Discovery: Conduct investigation leading to an understanding of the solution’s desired behavior. (On iterative projects, requirements analysis peaks during this phase but never disappears entirely.) During this phase, architectural proofs of concept are also constructed.   2a) Behavioral analysis2b) Structural analysis (object/data model) (class diagram)   

Part B deliverables to be included in the Business Analysis Final Report:(DUE WEE12 – 20%) In the second part (Part B) of this assignment, you will develop and apply appropriate solution processes based on object oriented analysis techniques and recommend your solution that can monitor and evaluate changes to the workflow of end-to-end business processes. To achieve this, you will complete the behavioural and structural analysis of the business case scenario by completing the remaining BOOM initiation and discovery steps given above.  Perform the following tasks: Hint. Cycle time efficiency is equal to theoretical cycle time divided by total cycle time. To calculate theoretical cycle time, only take into consideration time spent in “actual work”, excluding waiting times and non-valued-added activities.   

Please attach a copy of the Marking guide to your hardcopy of submitted report. 

Note on Plagiarism: Plagiarism will not be tolerated. All reports and prototype websites must be original. Each student must submit a signed statement of originality available as a coversheet with the report.Week 13 Oral Presentation (10%). The oral presentation will be marked based on clarity of the presentation, ability to focus on key issues and appropriate use of business analysis concepts and BOOM artefacts for their chosen industry case scenario. The students must demonstrate their proposed model meets the business requirements of the case scenario. All students must equitably participate during the in-class presentation.     

Appendix: Generic Case Study (Help-desk system)   Consider the following process performed by a helpdesk office that handles requests from clients. The clients are employees and different stakeholders of a company.  (You are required to choose any industry scenario for this company). There are about 1000 clients in total. A request may be a business process related query such as processing a customer after-sales request or an IT-related problem that a client has, or even an access request (e.g. requesting rights to access an IT system). Requests need to be handled according to their type and their priority. There are three priority levels: “critical”, “urgent” or “normal”.   The current process works as follows. A client calls the help desk or sends an e-mail in order to make a request. The help desk is staffed with five “Level-1” support staff who typically are junior people with less than 12 months experience, but are capable of resolving known problems and simple requests. The hourly cost of a Level-1 staff member is AUD 40.   When the Level-1 employee does not know the resolution to a request, the request is forwarded to a more experienced “Level-2” support staff. There are three Level-2 staff members and their hourly cost is AUD 60. When a Level-2 employee receives a request, he/she evaluates it and assigns it a priority level. The job tracking system will later assign the request to the same or another Level-2 staff depending on the assigned priority level and the backlog of requests. Once the request is assigned to a Level-2 staff member, the request is researched by the Level-2 employee and a resolution is developed and sent back to the Level-1 employee. Eventually, the Level-1 employee forwards the resolution to the client who tests the resolution. The client notifies the outcome of the test to the Level-1 employee via e-mail. If the client states that the request is fixed, it is marked as complete and the process ends. If the request is not fixed, it is resent to Level-2 support for further action and goes through the process again.   Requests are registered in a job tracking system. The job tracking system allows help desk employees to record the details of the request, the priority level and the name of the client who generated the request. When a request is registered, it is marked as “open”. When it is moved to level 2, it is marked as “forwarded to level 2” and when the resolution is sent back to “Level 1’ the request is marked as “returned to level 1”. Finally, when a request is resolved, it is marked as “closed”. Every request has a unique identifier. When a request is registered, the job tracking system sends an e-mail to the client. The e-mail includes a ”request reference number” that the client needs to quote when asking questions about the request.   The helpdesk receives approximately 50 new requests per working day. The current process is known to be error-prone. 

The most frequent types of errors include:     Additional Feedback             

Rubrics used for assessment (Scale 1-5)  Lack of justification of conclusions. Poor usage of language and references. Legend for Student Learning Outcomes       

PART B 

Marking Guide (Business Analysis  Final Report for an Organisation + Oral Presentation)   Additional Feedback     Rubrics used for assessment (Scale 1-5)  Lack of justification of conclusions. Poor usage of language and references. Legend for Student Learning Outcomes    (%)    

Answer rating: 100% (QA)

PART A To begin with a warehouse is a planned space for the storage and handling of goods and materials Fritz Institute In general warehouses are focal points for product and information flow between ... View the full answer