This course has been independantly developed but follows the BCS Systems Development Foundation syllabus. The course does not include an examination. At the end of the course, participants should be able to demonstrate knowledge and understanding of the following areas:
Life cycle types and their rationales.
Making a business case.
Programming and development approaches.
Systems modelling and specification techniques.
Quality and testing.
Implementation and changeover.
Evaluation and maintenance.
Software support tools.
Business and system analysts, designers, developers, testers and other practitioners who want an understanding of the coverage of systems development.
At the end of this course, participants will be able to
Identify the actors, tasks and disciplines required for systems development and
Identify different architectural considerations
Investigate a system
Interpret business requirements and produce system requirements
Quality assure the system requirements documentation
Derive test cases from the systems requirements documentation
Describe a range of systems development lifecycles
Describe the principles, structure and activities of the Unified Process
Describe, interpret and quality assure use case diagrams, use case descriptions, class diagrams
and sequence diagrams
Make effective use of different methods of interpersonal communications.
Conduct an appropriate system review
Explain how CASE and CAST tools might be used to support the Unified Process
There are no prerequisites for this course.
Introduction to Systems Development
What is systems development?
The scope of systems development.
Relationship with other disciplines.
Life Cycle types and their Rationales
Systems development life cycles.
Adaptation and customisation of life cycles.
Project management and life cycles.
Definition of business analysis.
Place of business analysis in the development lifecycle.
Outcomes from business analysis.
Key areas of requirements engineering.
Techniques for requirements elicitation.
Types of requirements.
Analysing and validating requirements.
Making a Business Case
Elements of a business case.
Identifying, evaluating and selecting options.
Principles of cost/benefit analysis.
Principles of impact and risk analysis.
Programming and Development Approaches Types of development approaches.
Systems Modelling and Specification Techniques
Reasons for modelling.
Modelling from different perspectives.
Cross-referencing different modelling perspectives.
Documentation and specification.
The location of systems design in the systems development lifecycle.
The objectives and constraints of systems design
Input technologies and their application.
Output technologies and their application.
The objectives and principles of process design.
The objectives and principles of data design.
The design of codes.
The scope and principles of security design.
Types of architecture.
Objectives and principles of systems architectures.
Stakeholders and roles in architecture.
Management of the architecture.
The tiered architecture approach to it system development.
Service oriented architecture and service oriented development applications.
Quality and Testing
The definition of software quality.
The objectives and limitations of testing.
The structure and purpose of the static test stages of the V model.
The purpose and content of the dynamic test stages of the V model.
Re-testing (confirmation testing).
Implementation and Changeover
The task of file and data conversion.
The principles and problems of data mapping.
Plan, test and undertake data conversion.
The role of supporting documentation, including user manuals.
Approaches to training.
Defining training needs and evaluating training effectiveness.
Evaluation and Maintenance
The location of maintenance in the systems development life cycle.
The range of metrics which might be used to evaluate a delivered software product.
The purpose and conduct of a post-implementation review.
The purpose and conduct of a post-project review.
The distinction between corrective, adaptive and perfective maintenance.
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.