system development methodologies report writing

system development methodologies report writing

ICT393 Advanced Business Analysis and Design

Report

Due: Session 4

Worth: 20%

Submission instructions: You should submit your assignment via theICT393LMS site. You can receive email notification that your assignment has been received. Late submissions will be penalised at the rate of 5 marks per day late or part thereof unless prior approval for an extension has been gained.

You should submit the report as a word-processed document and ensure that you include your name in the document. You must keep a copy of the final version of your submission and be prepared to provide it on request.

The University treats plagiarism, collusion, theft of other students’ work and other forms of dishonesty in assessment seriously. For guidelines on honesty in assessment including avoiding plagiarism see http://our.murdoch.edu.au/Educational-technologies/Academic-integrity/

Background

You should consider yourself to be an employee of a consulting firm called Innovative Solutions that specialises in systems analysis, design, and development services. The firm’s services range from advising other organisations of how they can meet their own needs for system development through to providing direct development services. The clients of your firm range from very small businesses of only a few employees with very little in-house expertise, to large organisations with large in-house IT departments. Client organisations not only vary widely in terms of size, but also in terms of line of business, financial resources, IT infrastructure, and organisational culture. The required timeframe for developing and implementing a proposed system will also vary depending on both internal and external environmental factors.

There are a wide variety of possible approaches to the development of systems. These vary considerably in terms of factors such as whether they are:

· Sequential versus iterative

· Model driven versus product driven

· Prescriptive versus adaptive

· Proprietary versus in-house

Different approaches are suited to different types of projects in different types of organisations.

In this assignment you will write a business report on system development methodologies for employees of Innovative Solutions to use when selecting the optimal approach for clients. You will investigate what factors should be considered when deciding which development methodology to use to support development in a particular project, and present your findings in the form of a series of guidelines. The report will act as a guide for other consultants when selecting the optimal systems development methodology for clients.

To do

To successfully complete the assignment, you should:

· Identify factors that may determine the appropriateness of a particular development approach for an organisation – for example organisational size, team size and whether the system is mission-critical may be important. Use the literature to do this.

· Review the following two existing system development methodologies in terms of their characteristics, benefits and drawbacks:

· Scrum

· Rational Unified Process

· Consider when the use of each methodology is appropriate

· Propose guidelines to help assist in the selection of which of these system development methodologies to use

· Create a report based on what you have found out. It should include some information about the factors that determine choice of methodology, some information about the methodologies, and well explained guidelines. The report will be usedby employees of the consulting firm, so should be written in a style that will be accessible to them.

Format Guidelines

· Give your report a title that clearly reflects its contents

· Include a title page and a separate table of contents

· Include an introduction section that states the purpose of the report, and a conclusion that summarises the main points as well as the main part of the report

· The main body of the report should be further sub-divided structured using section headings

· Your report should be written in language suitable for IT professionals to understand

· Your report should be around1500 words in length

· Include a bibliography at the end that lists the resources you consulted in writing the report. These should be presented using APA referencing style. Your report should also include citations when you directly quote facts you have obtained from sources– but it is not intended to be an academic essay and should primarily be your ideas and recommendations. See http://library.murdoch.edu.au/Students/Referencing/for information about how to present your bibliography.

NOTE: Plagiarism is not acceptable. Urkund will be used to report on potential plagiarism. Find out more about how to reference properly and avoid plagiarism at http://our.murdoch.edu.au/Student-life/Study-successfully/Referencing-and-citing/

This table indicates the overall distribution of marks. Use it as a checklist when planning and editing your report:

Report Structure (25%) Yes/No
Does the introduction describe the aim of the report?
Is material well linked to the aim of the report
Does the body of the report have a logical structure with subheadings used to signpost it?
Is there an effective conclusion that summarises the main points?
Content and Research (65%) Yes/No
Is there evidence of adequate research and reading? That is, have the key factors that may determine the appropriateness of development approaches been identified and understood?
Have each of the methodologies been analysed?
Are the guidelines logical, clear and well explained?
Is sufficient detail provided to understand the guidelines?
Presentation (10%) Yes/No
Does the report have a title that reflects the contents of the report?
Does the report have a title page
Does the table of contents have page numbers that match the pages numbers on the report?
Is the writing fluent (correct grammar and spelling)?
Is the language appropriate for an organisational report?
Is a bibliography provided with all sources presented using a consistent referencing style

3


Comments are closed.