Professional Documents
Culture Documents
Please note that this Example Assessment Brief is NOT an authorised assignment brief. It is
provided as a reference only. Centres must develop assignments and assessment materials
that meet the needs of their students and align with their curriculum planning. This Example
Assessment Brief may be used as a starting point for the development of an assignment;
however, Centres are expected to modify and revise the Example Assessment Brief to meet
the specific needs of their students and curriculum. All assessment briefs must be Internally
Verified
Example Assessment Brief 1
Student Name/ID
Number
Unit Number and Title 9: Software Development Lifecycles
Academic Year
Unit Tutor
Assignment Title Planning a Software Development Lifecycle
Issue Date
Submission Date
IV Name & Date
Submission Format
The submission for LO1 and LO2 is in the form of two sets of documentation including at
least one presentation with detailed speaker notes/handouts and suitable illustrations
and examples.
The submission for LO3 and LO4 also requires a presentation with detailed speaker
notes/handouts and suitable illustrations and examples as well as a software analysis and
supporting documentation with appropriately formatted reports and other documents as
required.
This should be written in a concise, formal business style using single spacing and font size
12. You are required to make use of headings, paragraphs and subsections as appropriate,
and all work must be supported with research and referenced using the Harvard
referencing system. Please also provide a bibliography using the Harvard referencing
system. The recommended word limit is 2,000-2,500 words, although you will not be
penalised for exceeding the total word limit.
The submission for LO3 and LO4 also requires a presentation with detailed speaker
notes/handouts and suitable illustrations and examples as well as a software analysis and
supporting documentation with appropriately formatted reports and other documents as
required.
This should be written in a concise, formal business style using single spacing and font size
12. You are required to make use of headings, paragraphs and subsections as appropriate,
and all work must be supported with research and referenced using the Harvard
referencing system. Please also provide a bibliography using the Harvard referencing
system. The recommended word limit is 2,000-2,500 words, although you will not be
penalised for exceeding the total word limit.
Requirements document:
1. Demonstrate your expertise and understanding of software development via a
software investigation.
2. You are being tasked with the software investigation into the requirements for the
management of the whole process from entering the race to documenting the final
results and allocating prizes. This will take some research on your part, but a list of
essential requirements is available, unfortunately it isn't a complete list, you will
have to identify and include others as they arise.
Manage entries by runners Record entry fee payments Manage staffing, marshals, judges,
timekeepers etc. both volunteers and paid staff.
Record results and track riders.
Record payments to customers.
Track customers.
Track staffing of water points along the race and logistics of providing suitable supplies in
a suitable form.
Produce certificates to go with medals for those who complete the course with time,
name etc.
Entries are expected to be in the usual multiple thousands.
Your final task is to look into the suitability of software behavioural design techniques
with a view to the company adopting appropriate ones.
First: prepare a presentation discussing the suitability of different software behavioural
design techniques using appropriate examples to illustrate this. You will need to include
detailed lecture notes/handouts for your audience.
Include, as the second half of your presentation, an analysis of a suitable range of
software behavioural tools and techniques.