This course does not include the exam in the cost for events before 5th October 2020. To book the exam and take it at the end of your course please book on code SDEEX-2 with one of our team.
Based on the BCS syllabus, this course is concerned with the fundamental skills of systems development. Its focus is on systems lifecycles, systems investigation, modelling and quality assurance as it is perceived that these underpin all systems development. The course also introduces the delegate to how the systems development effort could be organised. The BCS syllabus distinguishes between the different generic lifecycle types, methods and approaches, and requires a more in-depth exploration of a specific approach.
As people move into application systems analysis, from either a business or technical background, they need to acquire a fundamental understanding of the application systems development process, and the role and responsibilities of systems analysts, solution architects and designers. This course provides these essential foundations and goes on to focus on systems investigation and quality assurance techniques, as these underpin all successful systems development projects.
It also examines how the systems development effort could be organised, and distinguishes between generic lifecycle types, methods and approaches. At the end of the course delegates may sit an examination to attain the BCS Business Certificate in Systems Development Essentials.
This course may be taken as part of the Nexus programme leading to the BCS Diploma in Solution Development. This is an intensive three day course that places emphasis on the practical application of the analysis skills covered. Delegates participate in exercises, and case study tasks. Those delegates taking the BCS examination will need to spend 60-90 minutes each evening on revision and example examination questions.
The recommended combination and sequence of courses for delegates wishing to complete Nexus' programme leading to the BCS Systems Development Diploma is:
- Systems Development Essentials,
- Systems Modelling Techniques (UML) or Systems Modelling Techniques (Structured),
- Systems Design Techniques,
- Software Testing Foundation.
Following your exam you will be sent an email from BCS asking you to register for your exam. Once you have registered and your exam results become available then you will be able to log back into your account and view your results.
- Those who are new to analysis and need to acquire and practise the fundamental skills of Systems Development.
- Those wishing to attain the BCS Certificate in Systems Development Essentials. (These delegates should also book course code SDEEX-2).
The BCS syllabus requires training providers to choose a specific development approach which should be exposed and explained in more detail than the generic approaches mentioned. Nexus has chosen the Dynamic Systems Development Method (DSDM) as the full lifecycle development framework and Scrum as the approach to application software production. Both of these are popular choices in industry, and are often used together. In addition, the Unified Modelling Language (UML) is used for modelling business and software specifications, wherever applicable.
At the end of this course you will be able to:
- 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
Systems Development Roles and Responsibilities
Identify the Actors/Roles and responsibilities within system development and implementation (for example, analysts, designers, developers, testers and technical architects). Characteristics of these roles. Team structure.
Different levels of architecture – Enterprise, Business, Solution, Infrastructure (networks, databases) Inputs at Enterprise level. Inputs at Solution and Infrastructure level. Impacts of design decisions.
Systems Development Lifecycles
Waterfall. V Model. Incremental or phased delivery. Spiral or iterative. Advantages and disadvantages of each approach. Selection of an appropriate approach on defined characteristics.
Bespoke development. Evolutionary / Agile. Prototyping. Component based development. Software Package solutions (COTS Commercial off-the-shelf).
Structure and content of a chosen representative method (DSDM/Scrum). Describe and interpret three representative models (UML) from the method, showing at least: Process perspective, Data perspective, Event perspective. Explain how these models can be used to depict the logical and physical aspects of a system. Roles and team structures within the chosen method. Products within a chosen method.
Fact finding approaches: Workshops, Prototyping, Interviewing, Questionnaires (for usability or package selection for example), Scenario Analysis. Functional requirements definition. Non-functional requirements definition. Documenting system requirements. Human aspects of systems investigation and introducing change.
System Design, Implementation and Maintenance
Controls and security. Verification and validation. Interface design. Design principles and constraints (legal, ethical, financial). Different types of implementation. Sign off and deployment. Post implementation reviews. Different types of maintenance and support.
Definitions of quality. Requirements driven testing. Types of walkthrough and inspection. Post Project Reviews. Service Level Agreements.
CASE, CAST and application lifecycle tools
Software support for systems development. Features of CASE and CAST tools. Features of Application Lifecycle Management. Lifecycle coverage. Configuration and version control.
Case Study and Exercises
Throughout the course a case study and other exercises are used to reinforce and practise the topics discussed. A sample exam paper with marking scheme is also provided.
Candidates with special examination requirements should consult the BCS website for the Special Needs policy. Note that the BCS must be advised at least four weeks in advance of any special requirements. No prior knowledge of analysis techniques is expected.
If you are taking a BCS exam you must bring photographic identification with you (passport, driving license or student card), as it is a BCS requirement to produce it for the invigilator prior to the exam. Failure to produce a valid form of photographic identification will result in a candidate not being able to sit the exam. For any questions about what form of identification is acceptable please contact your Account Manager or the Nexus Training team on 44 (0)1392 205095.
BCS allow additional time for candidates who have a disability or whose native language differs to that of the examination paper. Full details are provided in the BCS Reasonable Adjustments Policy which is available to view on the BCS website. If you believe you qualify for this then please notify the Exam Administration team on the details below as early as possible. At least two weeks' notice will be required for processing this request. Delegates failing to advise Nexus and provide evidence when requested, may not be allowed the additional support offered via the BCS policy. Nexus Exam Administration can be contacted by email firstname.lastname@example.org or by phone 44(0) 1392 205095.