Systems Development Essentials-Syllabus
Systems Development Essentials-Syllabus
Version 2.5
December 2016
This professional certification is not regulated by the following United Kingdom Regulators - Ofqual,
Qualification in Wales, CCEA or SQA
Technical Changes:
Minor restructuring to the sequence of the syllabus
Clarification of the importance of being able to select a particular
approach and to use a specific chosen method in detail
Addition of Application Lifecycle Management to the CASE tool
section
Need to differentiate between logical and physical models
Refresh of roles and addition of the need to understand team
structures
Clarification of Agile Approach
Made more consistent with the BCS architecture qualifications
Reduction of percentage on systems investigation and increase
on methodologies
Acronym COTS explained
Bespoke development added
Section 5.6 removed – duplication of Section 5.5
Expanded Section Heading 1.3
Introduction ........................................................................................................................ 5
Objectives .......................................................................................................................... 6
Additional time for candidates requiring Reasonable Adjustments due to a disability ......... 6
Additional time for candidates whose language is not the language of the examination ..... 7
Syllabus ............................................................................................................................. 8
The syllabus requires the candidate to contrast various generic development lifecycles,
defining the advantages and disadvantages of each in order to select the most appropriate
approach for a specific situation. It then requires that ONE development lifecycle be
addressed in detail in the context of a selected method or approach. So, for example, a
candidate may wish to consider the Unified Process, Scrum or DSDM as an example of an
Agile approach.
For the selected approach, the syllabus requires that the candidate should be able to
describe:
Identify the tasks and disciplines required for systems development and the
implementation of the development
Describe the relationship between systems development and the wider term solution
development
Interpret the business requirements and produce systems requirements
Describe the commonly used development lifecycles defined in the syllabus
Select a particular development lifecycle based on specific characteristics
Describe in detail one method that embraces one (or more) of these generic
lifecycles
Describe the structure, activities and deliverables of this method
Identify the key roles and responsibilities within the chosen method and describe how
these can be used to form teams
Describe, interpret and quality assure the key models that the selected method uses
for defining the process, static and event processes of the system
Explain the differences between logical and physical models
Make effective use of different methods of interpersonal communications
Quality assure the systems requirements documentation and models
Identify different architectures for systems development solutions
Conduct a quality review
Explain how CASE, CAST and Application Management tools might be used to
support the chosen method
Providers can submit their own approaches and lifecycles for accreditation provided that
they show how all aspects of the syllabus are handled in their proposed approach.
Candidates will not be expected to construct the models in the examination for this
certificate. Construction of these models will be examined in Systems Modelling
Techniques.
If the examination is taken in a language that is not the candidate’s native / official language
then they are entitled to use their own paper language dictionary (whose purpose is
translation between the examination language and another national language) during the
examination. Electronic versions of dictionaries will not be allowed into the examination
room.
1.1 Identify the Actors/Roles and Responsibilities within system development and
implementation (for example, analysts, designers, developers, testers and technical
architects)
1.2 Characteristics of these roles
1.3 Team structure
2. Architecture (5%)
Examinable as multiple choice, but difficult to examine in a practitioner open book
exam
3.1 Waterfall
3.2 V Model
3.3 Incremental or phased delivery
3.4 Spiral or iterative
3.5 Advantages and disadvantages of each approach
3.6 Selection of an appropriate approach on defined characteristics
5. Methods (20%)
Examinable in both multiple choice and practitioner open book.
However, the methods are chosen by the Examination Provider so each Provider will
set questions for their chosen method.
If this module were to be centralised and offered as a multiple choice then different
sets of questions would need to be produced for each possible method (e.g. Iterative,
prototyping, DSDM,).
The levels of knowledge and SFIA levels are explained in on the website www.bcs.org/levels
The levels of knowledge above will enable candidates to develop the following levels of skill
to be able to operate at the following levels of responsibility (as defined within the SFIA
framework) within their workplace:
Pre-requisites None
Supervised / Yes
Invigilated
Open Book Yes
Pass Mark 50%
Distinction Mark None
Delivery Paper based examination