BCS Certificate in Systems Design Techniques

Overview

The certificate focuses on design issues. It is concerned with all aspects of design. The user interface (input forms, input screens, output screens, reports and documents, dialogues) as well as underlying principles of developing analysis models into logical and physical systems designs using data driven or component driven approaches. As in other certificates, the design approach is not prescribed. The syllabus refers to both UML and structured systems design models and techniques.

Who should attend

• Those who need to produce effective business specifications, develop close working relationships with end users, design solutions that fulfil business requirements, and implement those solutions.

• Those wishing to attain the BCS Certificate in Systems Design Techniques. (These delegates should also book on course code SDTEX). Candidates with special examination requirements should consult the BCS web site (http://www.bcs.org/) for the BCS Special Needs policy. Note that the BCS must be advised at least four weeks in advance of any special requirements.

Prerequisites

• Attendance at a Systems Modelling Techniques course or the equivalent knowledge of UML Analysis Models is essential

Photographic identification for exams and BCS reasonable adjustments policy

• If you are taking a BCS exam you must bring photographic identification (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.
• The BCS also allow additional time for candidates who have a disability or whose business language is not English. Candidates can request this additonal time in line with the BCS reasonable adjustments policy. If you believe you qualify please contact our examination administration team as early as possible. At least three weeks notice will be required for processing and delegates failing to advise QA and provide proof if requested by the BCS may not be allowed the additional support offered via this BCS policy.

For any questions about what form of identification is acceptable, or for more information about the BCS reasonable adjustments policy, please contact your Account Manager or the QA Examination Administration team on 44 (0)1793 696273.

Delegates will learn how to

• Develop logical and physical systems designs from structured and UML analysis models.
• Differentiate between a data driven design approach and an object driven design approach.
• Select and use a recognised design methodology to meet specific system design requirements.
• Explain the role and objectives of systems design in the systems development life cycle.
• Evaluate the suitability of an input and output system.
• Construct a usable user interface (HCI).
• Apply the rules of normalization to a set of data attributes.
• Understand and apply the principles of security, confidentiality and privacy

Course Outline.

Introduction

• Role of the system designer
• System design and Solution Delivery
• Design Approaches: Component driven design (Object Oriented); Data-driven design (Structured Systems)
• Architectural issues in design: Business, Application and IT architectural constraints; Use of design patterns for software architecture
• Impact of legacy systems
• Interpreting analysis models depicting processes and data

Component Driven Design

• Use and notation of UML (OO) models
• Coupling and cohesion in Use Case Realisation
• Component design: Presentation, business and data layers; Interfaces between these layers; User Interface Components; Persistent Data Components; Security Components; Provided and Required Interfaces
• Design using class, activity and state transition models: Mapping Class operations to Use Cases; Producing Sequence Diagrams for Class and Activity diagrams; Mapping guard conditions from state diagrams on to sequence diagrams and/or class diagrams

Data Driven Design

• Use and notation of Structured System Models
• Logical Systems Modelling
• Access Paths
• Detailed definition of processes using Structured English / pseudocode / flowcharts
• Normalisation: Normalisation of selected inputs and outputs from un-normalised to third normal form
• Physical systems modelling including de-normalising
• Star Schemas; design of Fact and Dimension Tables

Input /Output Design

• Identifying I/O Data Elements and selection of data capture and I/O technologies
• Implications of design on: Transmission; Data Quality; Data Entry; Storage and Retrieval
• Management Information Reports
• Design of input and output interfaces: Dialogue Modelling and Design; Forms and Layout Design; Inter-system data exchange format design; Style guides - purpose and usage
• Prototyping the user interface: Types of Prototype; Prototyping Issues

Controls and Security

• Verification and Validation of data
• Public; protected; private; packages, attributes and methods
• Output controls
• Physical and logical security
• Risk assessment of controls and security
• Backup and recovery procedures
• Disaster Planning