Business Analysis Case Study – Business Analysis Assignment Help

Assignment Task

Learning Outcomes Assessed
The following course learning outcomes are assessed by completing this assessment:
K2: Discuss a variety of contemporary tools and techniques used for business analysis and when these are appropriate to use
K3: Identify and explain the core concepts of business analysis
S1: Analyse, document and manage business requirements
S2: Investigate and compare various business analysis methods, tools and techniques
S3: Identify and apply appropriate means of communication for disseminating information between stakeholders
S4: Determine a variety of possible solutions and make recommendations to address business needs
A1: Develop, manage, and effectively communicate business requirements
A2: Analyse and critique the implementation of a business solution
A3: Prepare and justify a case for business change

Tasks:
1. Perform analysis to Identify Current State
You need to gain a clear understanding of the current situation of the organisation or sector that has an issue that you have identified you wish to address. Consider the aims and strategy of the organization/sector. Consider the existing processes and roles within the organsiation and how they interact. This is likely to help you to identify exactly where the problem or the opportunity sits.
In your report you need to give an explanation of your findings from this analysis, in particular you should:
– Explain the organisation or the sector of the economy where the issue arises – what are the key aims or business objectives of the organisation/sector, and who is served by the organisation/sector.
– Identify key processes or capabilities that are already in place – list these. Additionally, try to describe 2 of the processes using either BPMN or detailed use case descriptions.
– Try to identify, or else imagine, the current organisational structure – what roles exist within the organisation to support and execute the processes and capabilities.
– Identify key technologies that are already in use and briefly list or describe these. Then having documented those things, give a brief introduction of what/where the identified issue or opportunity for change exists. This may be in the form of two or three very high-level business objectives. (The detail will be presented in the Requirements section).
Note that you are not to include a SWOT analysis or a Business Model Canvas for this assignment (though you might find these useful aids to think with).

2. Perform Elicitation to Identify and Document Stakeholders and Requirements
You need to perform various elicitation and requirements analysis techniques in order to identify a range of requirements that would need to be addressed by any solution that is to be proposed, and then to define the requirements architecture to present these appropriately in the report. You will also need to identify and describe each group of relevant stakeholders who would be impacted by and who may need to be involved in informing this change project, and that will help you to identify requirements (by considering what each stakeholder needs the solution to be able to do). Describe what a typical member of each stakeholder group is like (e.g. job titles/roles, level of engagement with the issue/process/systems either now and/or after a change and also during elicitation).

In terms of requirements, you need to consider/identify:
– Business requirements
– stakeholder requirements (which should be broken down into functional requirements and non-functional requirements),

– transition requirements
In your report you will need to consider the ways that you will present all of the requirements that you identify (this is called the requirements architecture). This can involve producing lists of requirements, detailed use cases, process models (such as BPMN diagrams). Also consider how you will show how the more detailed requirements can be traced back to more abstract requirements (such as business requirements) – this is called requirements traceability. You will probably want to use numbering to crossreference requirements in different places in the report.
Make sure you explain what the key business objectives that need to be addressed actually are. Detailed requirements should somehow be derived from the key business objectives. Remember that business objectives are high-level descriptions – statements of goals, objectives, and outcomes that describe why a change needs to be initiated.