BCS Intermediate Certificate In Enterprise And Solution Architecture .

1y ago
4 Views
2 Downloads
511.43 KB
19 Pages
Last View : 21d ago
Last Download : 2m ago
Upload by : Maxton Kershaw
Transcription

BCS Intermediate Certificate inEnterprise and SolutionArchitecture SyllabusVersion 4.4December 2016This qualification is not regulated by the following United Kingdom Regulators - Ofqual,Qualification in Wales, CCEA or SQA

ContentsChange History . 3Background. 4Additional time for candidates requiring Reasonable Adjustments due to a disability . 5Additional time for Candidates whose language is not the language of the examination . 5Reference Model. 5Accredited Training Organisation Guidance . 6Objectives . 4Eligibility for the Examination . 4Duration and Format of the Course . 5Duration and Format of the Examination . 5Levels of Knowledge / SFIA Levels . 8Question Weighting and Course Timings . 8Syllabus . 91.Architecture and Architects. 92.Architecture Precursors . 103.Architecture Frameworks. 114.Business Architecture. 125.Data Architecture . 136.Software Architecture . 147.Applications Architecture . 158.Design for NFRs . 169.Infrastructure Architecture . 17Format of the Intermediate Examination . 18Trainer Criteria . 18Relevant Standards . 18Relevant Websites . 18Recommended Reading List . 19Copyright BCS 2016ESA Intermediate Syllabus V4.4Page 2 of 19December 2016

Change HistoryAny changes made to the syllabus shall be clearly documented with a change history log. Thisshall include the latest version number, date of the amendment and changes made. The purpose isto identify quickly what changes have been made.Version Numberand DateVersion 4.4December 2016Version 4.3March 2015Version 4.2October 2013V4.1July 2012V4.0January 2012V3.0October 2010V2.0July 2010V1.1January 2010Changes MadeStrapline regarding regulated statement has been addedUpdated language requirements for additional time and use of dictionaries.Changed the format of the syllabus so that it reflects the standard format.Standardised the trainer requirementsTrainer requirements added to show minimum pass rateAdded in details of extra time for foreign language candidatesUpdated Page 9 pre-requisites for Practitioner entry level – previouslystated candidates needed to have attended the ‘course’ should saycandidates have passed the Intermediate exam prior to taking thePractitioner. Changed ISEB for BCS logos and removed ISEB fromsyllabus.Added more information to Data Classification Category. Changed thepass rate on Practitioner level from 60% (24/40) to 26/40. ChangedDistinction level on Practitioner level from 80% to N/A. Added ChangeLog in the main body of the syllabus.Added in trainer criteria for new trainers. This is not a retrospectiverequirement. Effective July 2010.Signed off and approved.Copyright BCS 2016ESA Intermediate Syllabus V4.4Page 3 of 19December 2016

BackgroundThis document is the syllabus for the BCS Practitioner Certificate in Enterprise and SolutionArchitecture, as administered by the BCS, The Chartered Institute for IT. The syllabus in thisdocument defines the scope of BCS examinations in Enterprise and Solution Architecture.It is designed to help: Candidates to understand terms and concepts in examination questionsAccredited Training Organisations to scope training courses that lead to the examsExaminers to scope examination questionsExamination questions and associated training are based on the terms that are listed in onesyllabus and defined in the companion reference model. Each term is classified as Foundation,Intermediate or Practitioner level. Each level of certification embraces the level below. So, whilethere is no foundation level examination, there are many foundation level concepts, and these mayappear in intermediate and practitioner level examinations. It is expected that candidates willunderstand most if not all the foundation-level concepts before attending a training course. Andthat Accredited Training Organisations may cover foundation-level concepts - relatively briefly.ObjectivesThe primary aims of the BCS examinations and associated training are to give enterprise andsolution architects a broad framework that covers the range of architecture work that precedes andsteers system development, and to focus attention on areas where the architect is responsible foreffective design and risk management.A secondary aim is to provide architects with generally applicable knowledge and training. Generalhere means independent of any specific architecture framework (Gartner, TOGAF, etc.). Thisenables Accredited Training Organisations to teach general knowledge and skills, rather thanframework-specific terms, concepts, structures and processes.Holders of the Intermediate Certificate will have demonstrated their knowledge and understandingof: different kinds of architecture and the roles architects play in the IT/IS industrythe business context, and the importance of business-IT alignmentarchitecture precursors: goals, directives and constraintsarchitecture development process and description frameworksbusiness architecture concepts and techniquesdata architecture concepts and techniquesapplications architecture concepts and techniquessolution design to meet non-functional requirementsinfrastructure architecture as a process to support applications architecture.Intermediate level training and examinations cover the most of the syllabus at a remembering andunderstanding level.Eligibility for the ExaminationIt is recommended that candidates have 3 years or more experience of IS/IT work including somecontact with architects and architecture descriptions.Copyright BCS 2016ESA Intermediate Syllabus V4.4Page 4 of 19December 2016

Duration and Format of the CourseCandidates can study for this certificate in two ways: by attending a training course provided by anAccredited Training Organisation or by self-study. An accredited training course will require aminimum of 19 hours of study run over a minimum of 3 days.The course can be delivered a number of different ways from traditional class-room based trainingto online e-learning.Duration and Format of the ExaminationThe format for the examination is a one-hour multiple-choice examination. The examination isclosed book i.e.no materials can be taken into the examination room. The pass mark is 26/40.Additional time for candidates requiring ReasonableAdjustments due to a disabilityCandidates may request additional time if they require reasonable adjustments. Please refer to thereasonable adjustments policy for detailed information on how and when to apply.Additional time for candidates whose language is not thelanguage of the examinationIf the examination is taken in a language that is not the candidate’s native / official language thenthey are entitled to 25% extra time.If the examination is taken in a language that is not the candidate’s native / official language thenthey are entitled to use their own paper language dictionary (whose purpose is translation betweenthe examination language and another national language) during the examination. Electronicversions of dictionaries will not be allowed into the examination room.The candidate registration form asks for the candidate’s business language, if this is not Englishthen BCS will automatically allocate additional time.Reference ModelThe reference model associated with the syllabus defines terms in just sufficient detail to help: Candidates to understand terms and concepts in examination questionsAccredited Training Organisations to be consistent with the syllabus and each otherExaminers to phrase examination questions and answersCopyright BCS 2016ESA Intermediate Syllabus V4.4Page 5 of 19December 2016

Accredited Training Organisation GuidanceEach major subject heading in the syllabus is assigned an allocated time. The purpose of this is togive both guidance on the relative proportion of time to be allocated to each section of anaccredited course and an approximate minimum time for the teaching of each section. AccreditedTraining Organisations may spend more time than is indicated and candidates may spend moretime again in reading and research.The course may be delivered as a series of modules with gaps between them, as long as it meetsall other constraints. Courses do not have to follow the same order as the syllabus.The syllabus contains references to established standards. The use of referenced standards in thepreparation of training material is mandatory. Each standard used must be the version quoted inthe current version of this syllabus.Training materials should be consistent with the terms and definitions contained in the syllabus andreference model. Accredited Training Organisations may use sources that use the same termswith different meanings, but should in this case explain any terminology clashes to candidates.Accredited Training Organisations are free to decide: the "process" that candidates are taught at the Intermediate level and apply to the casestudy in the practitioner level, andthe notations used in architecture models and descriptions.An Intermediate training course should lightly introduce the topics in Sections 10 and 11, but noexam questions will be set.On the breadth of an architect’s roleArchitect roles are broad, and the enterprise or solution architect must be a generalist. No syllabus,training course or examination can be enough to make an architect. The role requires extensiveexperience on a variety of projects.In this document, the terms “architect” and “architecture” apply principally to Enterprise andSolution Architects working in relation to Information Systems and Technologies. The role playedby architects in these roles is broad – spanning the spectrum from business concerns toinformation technologies.Note especially that while most sections of the syllabus are divided into Foundation, Intermediateor Practitioner levels, each level of certification embraces the level below. So, while there is nofoundation level examination, there are many foundation level concepts, and these may appear inintermediate and practitioner level examinations. It is expected that candidates will understandmost if not all the foundation-level concepts before attending a training course. And thatAccredited Training Organisations may cover foundation-level concepts – relatively briefly.Copyright BCS 2016ESA Intermediate Syllabus V4.4Page 6 of 19December 2016

This means they remember and understand all the terms defined in the syllabus, at all levels. Inaddition: 3 ARCHITECTURE PRECURSORS: The Practitioner should be able to define SMARTgoals and business cases, and identity risks relating to non-functional requirements. 4 ARCHITECTURE FRAMEWORKS: The Practitioner should be aware of alternativeframeworks and comprehend one framework in more depth. 5 BUSINESS ARCHITECTURE: The Practitioner should be able to describe businessarchitecture building blocks, models and views. 6 DATA ARCHITECTURE: The Practitioner should be able to describe dataarchitecture building blocks, models and views. 7 APPLICATIONS ARCHITECTURE: The Practitioner should be able to describe anapplications architecture. 8 SOLUTION DESIGN FOR NFRS: The Practitioner should be able to design orredesign a solution to meet non-functional requirements. 9 INFRASTRUCTURE ARCHITECTURE: The Practitioner should be able to outline aninfrastructure in sufficient detail for technical/infrastructure architects to complete. 10 MIGRATION PLANNING: The Practitioner should be able to plan an architecturemigration, alongside managers using standard management planning processes. 11 ARCHITECTURE MANAGEMENT: The Practitioner should be able to govern theimplementation of an architecture.Copyright BCS 2016ESA Intermediate Syllabus V4.4Page 7 of 19December 2016

Levels of Knowledge / SFIA LevelsThis course will provide candidates with the levels of difficulty / knowledge skill highlighted withinthe following table, enabling them to develop the skills to operate at the levels of responsibilityindicated.The levels of knowledge and SFIA levels are explained in on the website www.bcs.org/levelsThe levels of knowledge above will enable candidates to develop the following levels of skill to beable to operate at the following levels of responsibility (as defined within the SFIA framework)within their workplace:LevelK7K6K5K4K3K2K1Levels of KnowledgeLevels of Skill and Responsibility mberSet strategy, inspire and mobiliseInitiate and influenceEnsure and adviseEnableApplyAssistFollowQuestion Weighting and Course TimingsSectionNumberSection Title1234567891011Architecture and ArchitectsArchitecture and PrecursorsArchitecture FrameworksBusiness ArchitectureData ArchitectureComponent ArchitectureApplications ArchitectureDesign for NFRsInfrastructure ArchitectureMigration PlanningArchitecture ManagementTotal Number of QuestionsTraining Hours2.532.52.51221.51.50.250.2519Avg. target numberof questions perpaper46553543540Mapping the Intermediate Level to Bloom’s taxonomyThe relevant levels in Bloom’s taxonomy are Level 1 - Remembering and 2 Understanding. AnIntermediate Enterprise or Solution Architect should be at Bloom Level 2 for all Sections 1 to 9.This means they remember and understand all the terms defined in the syllabus at Foundation andIntermediate Levels.Copyright BCS 2016ESA Intermediate Syllabus V4.4Page 8 of 19December 2016

Syllabus1. Architecture and ArchitectsRecognise the work and roles involved in describing the architecture (the high-level design) ofbusiness systems and the information systems that support them. (Not, in this context, work androles related to buildings).Foundation Learning ObjectivesRecognise the ways base terms like architecture, system, structure, behaviour, interface, serviceand function are used in the BCS reference model (and so, examination question wording).Intermediate Learning ObjectivesArchitecture granularityDistinguish the following three levels of granularity in architecture definition: Enterprise, Solution(s)and Software.Architecture domainsRecognise the need for separation of concerns. Recognise that architecture descriptions aresliced into high-level views to address the separate concerns of different stakeholders. Distinguishthe following four broad perspectives: Business, Information/Data, Applications andTechnology/Infrastructure.Hierarchical or layered architectureRecognise division into layers as a fundamental and widely-used technique of architecture anddesign. Recognise how the architecture domains (above) may be regarded as layers.Architect roles, goals and skillsList a variety of architect roles. Distinguish the goals of enterprise architects and solutionarchitects. List some knowledge and skills required for those roles.Copyright BCS 2016ESA Intermediate Syllabus V4.4Page 9 of 19December 2016

2. Architecture PrecursorsRecognise the various inputs, statements of requirements and constraints that guide an architectas to the nature and shape of solutions to be built. Recognise the information that may be neededin a statement of architecture work.Foundation Learning ObjectivesStakeholdersIdentify stakeholders and their concerns. Apply stakeholder management techniques.Elaboration of inputs to become deliverablesRecognise that architecture involves hierarchical decomposition inputs into outputs, so the outputsat one level are inputs to the level below.Intermediate Learning ObjectivesDrivers, aims and directivesDistinguish drivers, aims and directives. Recognise the hierarchical decomposition of both aimsand directives. Define SMART aims.Solution descriptions and plansDistinguish business from IT. Recognise the hierarchical decomposition of solutions and the plansto deliver them.StandardsIdentify several standard bodies. Recognise the need for the enterprise to have a StandardsInformation Base, and to define the standards profile of solution components.Scope of architecture workRecognise ways to define the scope of architecture work, and the scope of an enterprise orsystem. Draw a context diagram showing interfaces to external systems). Distinguish theconcepts of external entity, actor, role.RequirementsRecognise the difference between functional and non-functional requirements. List ten kinds ofnon-functional requirement. Distinguish requirements, Service Level Agreements and ServiceLevel Requirements.Regulatory requirementsRecognise several kinds of regulatory requirement relevant to architecture definition.Business caseRecognise the contents of a business case; notably RoI, cost-benefit analysis, solution options andrisk analysis. Recognise in this connection the nature and purposes of gap analysis (betweenoptions), trade-off analysis, and business scenarios.Copyright BCS 2016ESA Intermediate Syllabus V4.4Page 10 of 19December 2016

3. Architecture FrameworksRecognise methodologies designed to help people create architecture descriptions and use themto good effect. Distinguish a development process (a process framework) from a classification ofarchitecture descriptions (a description framework).Intermediate Learning ObjectivesArchitecture process frameworksRecognise the phases of an architecture process framework that helps architects to describe abaseline architecture, a target architecture and the transformation between them.Recognise the ten phases of the method for enterprise architecture development (ADM) in theOpen Group Architecture Framework (TOGAF) Recognise that a process for solution architectureinvolves similar activities but with different goals and a different level of detail.Architecture descriptionsDistinguish the key concepts of architecture description (system, view, view point, concern, andstakeholder) and the relationships between them, as described in the standard popularly known asANSI 1471. Identify building blocks used in architecture descriptions.Architecture modelsRecognise that models are abstractions composed of instances of artefact types and mappingsbetween them.Distinguish three kinds of abstraction: by composition, generalisation and idealisation.Distinguish three levels in an idealisation hierarchy: conceptual, logical and physical. Recognisethe possible transformations involved in Model-Driven Architecture (MDA).Recognise the relationship (line) symbols shared by the Unified Modelling Language (UML) andArchiMate.Architecture description frameworksIdentify the rows and columns of the architecture description framework known as the Zachmanframework. Recognise the meta model of an architecture repository. Recognise the twodimensions of the Enterprise Continuum in TOGAF.Copyright BCS 2016ESA Intermediate Syllabus V4.4Page 11 of 19December 2016

4. Business ArchitectureRecognise ways to describe the structure and behaviour of a business system (not necessarilyrelated to computers), covering business functions or capabilities, business processes and theroles of the actors involved.Recognise how to map business functions and business processes to each other, to the businessgoals and business services they support, and to the applications and data they need.Foundation Learning ObjectivesDistinguish the physical and logical structures of a business (organisation units and businessfunctions or capabilities). Recognise several synonyms in this area.Distinguish business services and business processes. Recognise synonyms in this area, and theuse of the terms value stream and value chain.Recognise mappings of the above to place and time.Intermediate Learning ObjectivesBusiness architecture structure and behaviourRecognise ways to model a business system, including business process structures, businessfunction (or capability) structures, business data models and business rules.Business process decomposition and automationRecognise three levels of business process granularity: workflow, use case and automatedservice.Recognise the benefits of implementing a process as an ACID transaction and the need forcompensating transactions where this is not possible.Distinguish business services from data services.Design for business securityIdentify several features in design for human and organisational security.Copyright BCS 2016ESA Intermediate Syllabus V4.4Page 12 of 19December 2016

5. Data ArchitectureRecognise ways to describe the data structures used by a business and/or its applications,including meta data: that is, descriptions of data in storage, data in motion, data structures anddata items. Recognise mappings of data objects to data qualities, applications, technologies etc.Recognise information architecture can embrace not only data architecture but alsoknowledge/content management.Foundation Learning ObjectivesRecognises how the data stored in and transmitted between information systems is a model ofentities and events in the external environment, or real world.Recognise how data is described using meta data, data structures, data types and datadictionaries.Intermediate Learning ObjectivesKnowledge and/or content managementDistinguish knowledge and/or content management from data management.Data architecture structureUnderstand how to describe data in storage using data models. Recognise the issues in storingstate outside of a database in a cache. Recognise the functions of database management systemand concept of a federated transaction across a distributed database.Understand how to describe data in motion, data flow definitions, regular expression, messageformats and canonical data models.Data qualities and integrationRecognise how the three primary data qualities (CIA) may be measured at three or more levels.Distinguish data store integrity from data flow (or message) integrity.Recognise the dimensions of a data dissemination view.Recognise the way denormalisation is used to optimise output from a data warehouse,Recognise the concept of master data management, and ways to implement it.Design for data securityRecognise key concepts in data security: security protection, security feature, security policy,information domain, identity, encryption, checksum and digital signature.Copyright BCS 2016ESA Intermediate Syllabus V4.4Page 13 of 19December 2016

6. Software ArchitectureRecognise ways to modularise the internal structure of an application, and ways to connectcomponents, ranging from tightly coupled to loosely-coupled.Foundation Learning ObjectivesRecognise system modeling techniques including at least context diagrams, data flow diagrams,use case diagrams, process flow charts (activity diagrams), interaction diagrams (sequencediagrams) and state charts.Recognise the core concepts of modular design including: encapsulation, façade, aggregation bycluster or affinity analysis, stateful and stateless components.Recognise the core elements of a service contract and principles of service-oriented design.Recognise the concepts of transactional processing.Recognise the concept of delegation from clients to servers. Distinguish cyclic dependency fromhierarchical (non-cyclic) dependency. Recognise several service qualities and service-orienteddesign challenges.Intermediate Learning ObjectivesComponent structures and patternsRecognise the essential ideas in component structures and patterns: client versus server, looselycoupled versus tightly-coupled.Recognise basic design patterns: hierarchical and peer-to-peer structures, fork and chainstructures. model-view controller (MVC).Recognise a few common OO design patterns.Component interfacesRecognise the concepts of an Application Programming Interface (API) and Interface DescriptionLanguage (IDL). Recognise how an interface is realised by a component.Distinguish asynchronous from synchronous communication, from both client and serverperspectives.Component interoperation stylesRecognise how the following component interoperation styles are successively more looselycoupled: Distributed Objects style (DO): Service-Oriented Architecture style (SOA):Representational State Transfer style (REST): Event-Driven Architecture style (EDA).Copyright BCS 2016ESA Intermediate Syllabus V4.4Page 14 of 19December 2016

Component communication stylesRecognise how the following component communication styles increasingly decouple client/senderfrom server/receiver: point-to-point communication, introduction agent (direct broker) and mediator(indirect broker). Recognise at least one middleware technology used for each style.Publish and subscribe distributionDistinguish different kinds of publish and subscribe distribution.7. Applications ArchitectureRecognise ways to describe the structure and behaviour of applications used in a business, with afocus on how they interact with each other and with business users or actors. Recognise the needfor enterprise and solution architects to focus on data consumed and produced by applicationsrather than their internal structure. Recognise mappings of applications to business functions theysupport and to application platform technologies they need.Foundation Learning ObjectivesDistinguish three kinds of application: user application, infrastructure application, platformapplication.Recognise the main purposes of Enterprise Resource Planning (ERP) and Customer RelationshipManagement (CRM) systems.Intermediate Learning ObjectivesApplications architecture structure and behaviourRecognise the goals and concepts of application portfolio management.Distinguish structural and behavioural models of applications architecture.Recognise a variety of approaches to application integration: screen scrapers, ETL, applicationconsolidation. Distinguish point-to-point from hub and spoke application integration. Recognisethe TOGAF concepts of Boundaryless Information Flow and Integrated Information InfrastructureReference Model (III-RM).Design for applications securityDistinguish the steps in applications security: identification, authentication, authorisation andaccess. Recognise the concept of three-factor authentication. Recognise different securitycontrols needed in different layers of an enterprise application.Application platformRecognise the purposes of application platform technologies: notably component distributionmiddleware, database and transaction middleware (remote database access, transactionprocessing and distributed transaction manager).Copyright BCS 2016ESA Intermediate Syllabus V4.4Page 15 of 19December 2016

8. Design for NFRsRecognise a selection of common techniques used in design for NFRs.Foundation Learning ObjectivesNone.Intermediate Learning ObjectivesRecognise four designs for performance techniques: Database optimization (normalisation,denormalisation, index, and access path analysis), cache, scale up, scale out (aka clustering).Recognise two design for resilience techniques: Fail over, Defensive design.Recognise two design for recoverability techniques: Back up, Backup site.Recognise two design for integrity techniques.Recognise two design for serviceability techniques.Recognise design for security techniques mentioned in other sections of the syllabus and identifyrelevant standards ISO/IEC 27001: 2013 and ISO/IEC 27002:2013.Copyright BCS 2016ESA Intermediate Syllabus V4.4Page 16 of 19December 2016

9. Infrastructure ArchitectureRecognise ways to describe the structure and behaviour of the technology platform that underpinsuser applications: covering the client and server nodes of the hardware configuration, the platforma

different kinds of architecture and the roles architects play in the IT/IS industry the business context, and the importance of business-IT alignment architecture precursors: goals, directives and constraints architecture development process and description frameworks business architecture concepts and techniques

Related Documents:

STEP #2 - Look at spine. If individual vertebrae are visible, BCS 3. STEP #3 - Look at shape between hooks and pins. Shallow U - BCS 6, Strong U - BCS 5, V Shape - BCS 4, Strong V - BCS 3, Very Strong V - BCS 2. Figure 3. 3-Step Body Condition Score (BCS) guide for beef cattle. Step 1 - Look at the last two ribs. If

Public Relations and Communications Committee Co-Chair Lisa Evangelista CScD, CCC-SLP, BCS-S Joan Kelly Arsenault MA, CCC-SLP, BCS-S Maria Centeno PhD, CCC-SLP, BCS-S Marta Kazandjian MA, CCC-SLP, BCS-S Gina Palma MS, CCC-SLP, BCS-S Historian Joe Murray PhD, CCC-SLP, BCS-S Consumer Board Member Phillip Hartzer BSIM, MSM Easy2Digest: June 2021

BCS ITQ Suite of Qualifications Version 2.10 January 2020 Centres in Wales who are considering delivering the following qualifications to 14-16 year old learners, should contact BCS in the first instance. 500/6226/8 BCS Level 1 Award in IT User Skills (ECDL Essentials) (ITQ) 601/1237/2 BCS Level 2 ECDL Certificate in IT User Skills

BCS Level 1 Award in IT User Skills (ECDL Essentials) (ITQ) QAN - 500/6226/8 24.75 BCS Level 1 ECDL Award in IT User Skills – (Flexiqual) QAN - 601/0633/5 24.75 BCS Level 1 ECDL Certificate in IT User Skills – (Flexiqual) QAN - 601/1236/0 27.00 BCS Level 1 Smart Digital Award in E-Safety QAN: 603/6931/0 17.00

BCS Essentials Certificate in Artificial Intelligence Syllabus V1.0 BCS 2018 Page 10 of 16 Recommended Reading List Artificial Intelligence and Consciousness Title Artificial Intelligence, A Modern Approach, 3rd Edition Author Stuart Russell and Peter Norvig, Publication Date 2016, ISBN 10 1292153962

Certificate Course Smart Phone Repairing 10th Pass / Fail Certificate Course in Mobile Repairing 10th Pass / Fail 6 Months Certificate Name of The Courses Required Qualification Certificate Course in Electronics 10th Pass / Fail Certificate Course in Black & White TV Servicing 10th Pass / Fail Certificate Course in Black &With Color TV & DVD 10th Pass / Fail Certificate Course in Color TV .

BCS Confidence: English Literature Review [Type text] For more information please contact: 01938858860, BCS Confidence [Type t

Sample exam: EXIN BCS SIAM Foundation (SIAMF.EN) 4 Introduction This is the sample exam EXIN BCS SIAM Foundation (SIAMF.EN). The Rules and Regulations for EXIN’s examinations apply to this exam. This exam consists of 40 multiple-choice questions. Each multiple-choice question has