This course has been independantly developed but follows the BCS Systems Development Essentials syllabus. Course fees do not include the BCS examination. At the end of the course, participants should 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.
Business and system analysts, designers, developers, testers and other practitioners who want to gain skills in systems development.
There are no prerequisites for this course.
Systems Development Roles and Responsibilities
Identify the actors/roles and responsibilities within system development and implementation.
Characteristics of these roles.
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.
Evolutionary / agile, prototyping, component based development.
If you need training for 3 or more people, you should ask us about onsite training. Putting aside the obvious location benefit, content can be customised to better meet your business objectives and more can be covered than in a public classroom. It's a cost effective option.
Submit an enquiry from any page on this site, and let us know you are interested in the requirements box, or simply mention it when we contact you.