This report/discussions should relate to what you have read in the case study no use of references allowed. Make sure that you reference the case study appropriately using Harvard referencing – no copy of text from the case study to support your arguments.
BE AWARE THAT WE HAVE SOFTWARE THAT CAN DETECT TEXT COPIED FROM ONLINE SOURCES.
Section A – Management Summary
The case study tells us that the head of the IT division, Sally Miller, has decided to recommend one of the approaches associated with Agile Methods to the executive of The NightWatch. The Agile Method that Sally has recommended is called DSDM Atern.
Produce a management summary explaining whether DSDM Atern would be an appropriate method to use within NW. Outline any advantages/drawbacks that you perceive. Give examples from the Case Study to support your answer.
Section B – High level requirements analysis and MoSCoW prioritisation
Appendix A of the case study provides details (including minutes) of a Facilitated Workshop session run by Sally Miller and attended by a number of the key staff in the organisation.
At the end of the session a list of ‘high level requirements’ was produced.
Sally Miller was disappointed to see that some of the members of the workshop did not seem to understand the format of well-defined high-level requirements. It was clear from the requirements sheets that a couple of individuals did not put effort into the exercise and she found some of the items listed slightly rude! Since you have sufficient knowledge on DSDM Atern she decided to ask for your help.
The collection of requirements listed in Appendix A is an inappropriate set of requirements for developing a system, as a number of the requirements do not meet our criteria for a ‘high level requirement’.
Remember, a high level requirement should be a functional requirement that can be delivered to the user as part of an incremental approach using a timebox (or number of timeboxes).
Using the information given throughout the case study to help you, complete the following: B1. Review the ‘high level requirements’ list given at the end of Appendix A.
B1.1 Identify any of the requirements that you feel are not appropriate high-level requirements, giving your reasons for this.
B1.2 Rewrite, and add to, the list to end up with a total of 8-10 high level requirements that you feel are required for building the system. Briefly justify the need for each of your high level requirements against information you have gathered from the case study.
B2. Use the MoSCoW rules to prioritise the requirements in your updated ‘high level requirements list’.
B2.1. Produce an updated ‘high level requirements list’ clearly showing the prioritisation you have given to each of your requirements. There is no word limit for answer B2.1.
B2.2 Explain how you set about prioritising the requirements and justify your reasons for the decisions that you made. (500)
Section C – Legal, Social, Ethical and Professional issues
C1: NW needs to start considering Legal, Social, Ethical and Professional Issues (LSEPI) in relation to its day-to-day operations. They also need to appoint a Data Controller. Produce a management summary explaining (a) the role of the Data Controller within the organisation and (b) any legal, social, ethical and professional issues that NW may be faced with. As a part of your answer to (b) provide two practical examples from the case study that relate to each aspect of LSEPI. (500-750)
C2: Produce a management summary outlining the purpose of the BCS Code of Conduct. As a part of this, provide a practical example for each of the four BCS Code of Conduct sections to illustrate a professional issue that a System developer contracted to NW may need to consider. (500-750)
12 pekerja bebas membida secara purata £54 untuk pekerjaan ini
development frameworks, methodology and methods Relevant Skills and Experience Article Writing, English (UK), Report Writing, Software Architecture, Technical Writing Proposed Milestones £120 GBP - Paper