Reference no: EM131623194
Case Study:
Issues with the Human Activity System used for Learning Management at Griffith University.
Task Description
Identify the business problem/s within the ‘issues' above and their root causes, needs to address them and major stakeholders involved; define the requirements and an approach to their life cycle management for the designated case study; define the change strategy to achieve a future state addressing the problems, analyse value and recommend solution/s. Among others, consider limitations, costs and age of the Human Activity System used for Learning Management.
The report should adhere to BABOK v3, the required readings and lecture slides and should demonstrate your knowledge of underlying competencies as described in BABOK Chapter 3 Section 1.3 and Chapter 9. Please clearly distinguish between your work and that of your sources. All sources of business, background and contextual information should be carefully cited and listed, using APA or Harvard guidelines. Always indicate the page number(s) in the source you refer to. Direct quotes should be shown by quotation marks, should not be extensively used and will not be included in the word count.
Assignment Format:
NOTE: A template will be made available for your use. You must use the template provided.
- Title page: Student name, student number, degree, course code and title, assignment title, business problem, perspective, word count, due date
- Cover letter (not more than one page); this briefly indicates the purpose of the report, significant findings and limitations. Address the letter to your tutor or teacher.
- Executive summary (not more than one page) - should be able to be read instead of the report. It should focus on the main findings and limitations.
- Table of Contents. Should list the main headings and subheadings of the report, and the appendices (and titles of appendices), with correct page numbers.
- Table of Figures and Table of Tables with correct page numbers.
- The content organised into sections as specified in the Structure below
- References (Harvard or APA - https://app.secure.griffith.edu.au/reference_tool/index-core.php): a list of all and only the sources referenced in your written text.
- Appendices
Please put your names and student numbers in header and page numbers in the footer. Refer to the resources on Learning@Griffith as required and pay attention to pagination and referencing.
Assignment Structure:
1. Introduction
- Identify the general business problem addressed by the assignment
- Identify the scope and structure of the business report
- Identify and briefly describe any issues (such as inability to access information) which may have affected the compilation of the report
2. Identification of the Business Problem and Need
- Correct application of concepts from course material and chapters 4 (Elicitation and Collaboration) and 6 (Strategy Analysis) of BABOK: Business problem/s and opportunity/ies, business need/s (6.1.4.1) and their generation (p.105), goals and objectives (6.2.4.1), desired outcome (4.1.2).
- Select and use appropriate techniques from BABOK (6.1.6), such as SWOT, SMART, PEST(LE), Porter's Five Forces, etc. (justify selection)
- Show analysis in appropriate diagram/s or table/s.
3. Stakeholder Analysis
- Correct application of concepts from course material and BABOK Stakeholder Analysis (3.2.4.1).
- Identify a stakeholder list (3.2.8) (may start from the generic list in 2.4) and cover roles, attitudes, decision making authority, level of power and influence (3.2.4.1).
- Provide at least two diagrams to represent relations between stakeholders and their attributes (see BABOK 10.43.3.2: Stakeholder maps and 10.43.3.3: RACI matrix, (place in an appendix).
- Select and use appropriate techniques from BABOK (3.2.6) (justify selection) including document analysis, brainstorming, interviews, etc.
4. Approach to Requirements Life Cycle Management
- Choose a Business Analysis Planning Approach (3.1)
- Discuss Requirements Life Cycle Management (BABOK Ch. 5) relating to the chosen approach:
- Describe the basis for requirements prioritisation (BABOK 5.3.4.1) applied to current problem;
- Describe the conflict issue management approach (BABOK 5.5.4.2)
- Select and use appropriate techniques from BABOK (3.1.6, 5.3.6) (justify selection).
5. Define Change Strategy, Analyse Value and Recommend Solution
- Define the solution scope and how it addresses the stakeholder requirements (BABOK 6.4.4.1)
- Define what aspects are out of the scope of the solution.
- Discuss briefly potential benefits (BABOK 7.6.4.1, 7.6.4.3) and risks (6.3.4.1-6.3.4.5) and make an appropriate recommendation.
- Select and use appropriate techniques from BABOK (6.3.6, 6.4.6, and 7.6.6) (justify selection).
6. Requirements Analysis
- Business requirements - Based on your discussion in section 3, state and prioritise at least three major business requirements (BABOK 2.3). List the requirements in order of priority according to the basis for prioritisation described in Section 4.
- Stakeholder requirements - In relation to the first priority business requirement, identify and state two requirements for a stakeholder or group of stakeholders (BABOK 2.3. and 4.2.8)
- Functional requirement - Describe two functional requirements (BABOK 2.3) of a solution which will meet the two stakeholder requirements indicated above. The descriptions should use the fully developed Use Case descriptions (not diagrams!) technique (BABOK 10.47 and SAD Book Ch. 4 for Use Case Description Tables)
- Non-functional requirements: describe the relevant non-functional requirements (BABOK 2.3, 10.30 for technique and 10.30.3.1 for a list)
- Observe all parts of BABOK 7.1 (‘Specify and Model Requirements') for this Section.
7. Conclusion
Summarise the most important points from your report, referring to the relevant sections. Do not include new information.
Word count: Maximum 5,000 words; Font type: Times New Roman. Minimum font size: 10 point. Use single row and normal character spacing. Word count does not include References, Appendices or verbatim quotes.
Attachment:- Template.rar