Beruflich Dokumente
Kultur Dokumente
NOTES:
Coursework must be submitted to Turnitin via Blackboard which gives it a date
and time stamp, by 2.00pm on the deadline day.
The following penalties will be applied to coursework which is submitted after the
deadline for submission:
• where the piece of work is submitted after the original deadline (or any
formally agreed extension to the deadline): 10% of the total marks available
for that piece of work will be deducted from the mark for each working day
(or part thereof) following the deadline up to a total of five working days;
• where the piece of work is submitted more than five working days after the
original deadline (or any formally agreed extension to the deadline): a mark
of zero will be recorded.
If a student believes he/she has a valid reason for being unable to meet the
deadline he/she must complete an Extenuating Circumstances form and submit it
as soon as is practicable (in principle before the deadline) to the Programme
Administrator at HBS Admin Deck office.
NOTE: It is recommended that you keep a copy of all coursework that you
submit.
INMR66 /INMG95– Business Domain & Requirements Analysis
Coursework
Introduction
The aim of this coursework is to enable students to apply the concepts and
techniques introduced during the lectures to a case study and assess their
understanding and ability to perform the tasks in business domain and
requirements analysis. Students are to conduct the task based on the scenario
described in this coursework document, and are expected to carry out the process
of business domain and requirements analysis to the scenario in order to provide a
systematic analysis of the problem domain that facilitates the project initiation,
management and execution at a later stage (the project initiation, management,
and execution issues themselves are outside the scope of this coursework). The
learning objectives of the coursework include the acquisition of critical thinking,
analysis and writing skills.
Coursework Requirements
- The new system should be made available to the public. In addition, to raise
public awareness and interest in climate change as well as other pollution issues,
the system will also accept data collected by members of public using mobile
devices i.e. to utilise the concept of crowdsourcing/collective intelligence where
members of public will be able to download a mobile application to do so. Such
data will be first checked by the MoE for suitability before added to the system.
- The data can be aggregated and visualised on a map according to different
regions (imagine something similar to Google Maps®).
Useful information:
- Muller, C.L., Chapman, L., Johnston, S., Kidd, C., Illingworth, S., Foody, G.,
Overeem, A. and Leigh, R.R. (2015), Crowdsourcing for climate and atmospheric
sciences: current status and future potential. International Journal of Climatology, 35:
3185–3203. doi: 10.1002/joc.4210
(Available at http://onlinelibrary.wiley.com/doi/10.1002/joc.4210/full)
-Giuliani, G., Ray, N., De Bono, A., Dao, H., Van Woerden, J. V., Witt, R., Beniston,
M., and Lehmann, A. (2011). Sharing Environment Data through GEOSS,
International Journal of Applied Geospatial Research, 2 (1), 1-17, (Available at
http://www.unige.ch/climate/Publications/Beniston/JAGR2011.pdf)
Students must produce a written report that documents the results of business
domain and requirements analysis of the scenario provided above. The report will
be in two self-contained and separate parts:
A) Executive Report (2 pages*)
B) Business Domain and Requirement Analysis Report
The report, such that A + B, should contain approximately 5,000 words (with a
variation of 10%) including any diagrams but excluding the references. An
appendix (outside word count) can be used to include more detailed material to
back up the main body points, but will not be assessed. The minimum font size
for the body text should be 10pt.
The report should contain all the aspects of business domain and requirements
analysis covered in the module. The total of 100 marks will be allocated to the
following aspects of the report, which should also be used as a guideline to
structure the report:
A. Executive Summary (10 marks –TWO pages*)
The executive summary should effectively summarise within the page limit the business case
(i.e. outcome of the business domain and requirements analysis conducted (as in Section B)
aimed at senior level management/project sponsor), including, the background, problem or
opportunity, options available and considered, cost/benefit analysis (immediate and longer
term, tangible and intangible), impacts and risks, and recommendations.
* Note the length for the executive summary is two pages, if it exceeds two pages, the
third page onwards of the Executive Summary will be excluded from the assessment.
Strategy analysis
In this sub-section, you should carry out strategy analysis to support the needs for
the new information system and align it with the business objectives/strategy.
Organisational analysis
In this sub-section, you should conduct the organisation analysis (e.g. organisation
culture and structure analysis) in which the new information system is introduced
to demonstrate the understanding of the organisational context, and align it with
the business objectives/strategy.
Stakeholder analysis
In this sub-section, you should identify the key stakeholders, describe their roles and
responsibilities in the context of the information system developed (e.g. RACI/RASCI
chart), and make an assessments of the stakeholders identified (e.g. power/interest
analysis) and devise strategies for stakeholder management.
Quality of the report: There are 10 marks allocated to the quality of a report as
follows:
o Clarity of organisation and structure/presentation e.g. consistency,
logic of arguments, overall flow, coherence and integration
o Fluency, style of writing, referencing and use of Harvard System
referencing.
Note:
Where conditions are underspecified, make reasonable assumptions based on
existing organisations or literature, providing the source of information.
The criteria used for grading assignment:
Conclusion, 70% and Very good analysis of the evidence with clear and
critical above illuminating conclusions that is very well-justified
evaluation and and related to the business case.
future
improvements 69-69% Clear and orderly analysis of the evidence with
(20%) good and appropriate conclusion with adequate
support and justification in relation to the business
case
50-59% Some critical analysis but prone to descriptive or
narrative; evidence supports the conclusion, but
not always very directly /clearly. The question is
not fully addressed.
49% and Largely descriptive. The discussion is limited in
below scope and/or relevance. The question is only partly
addressed.
Please note student who attained a mark of 60% or above at the first attempt will
be eligible for the BCS Practitioner Certificate in Business Analysis Practice (BAP).