iSAQB CPSA-A REQ4ARC

Beschreibung

Attending the iSAQB® CPSA-A Requirements for Software Architects (REQ4ARC) course gives participants 20 Methodological Competence (MC) and 10 Technical Competence (TC) points towards the 70 points required for eligibility to take the iSAQB CPSA-A exam with Brightest. It is important to remember that as part of the 70 points required to take the iSAQB CPSA-A exam with Brightest, you will need at least ten competence points in each of the following areas: 

• Technical Competence (TC)
• Methodological Competence (MC)
• Communicative Competence (CC)

Accredited iSAQB® REQ4ARC - Requirements for Software Architects (CPSA-A) training is based on the current iSAQB® curriculum:

Part 1 - Clean start

• Even with iterative development, understanding some upfront activities is necessary
• Mastery and explicit knowledge of vision, goals, and relevant stakeholders are required
• Understand that scope and context are required, particularly the interfaces between scope and context (i.e., the external interfaces of the product)

Part 2 - Addressing functional needs

• Know the definition of functional requirements
• Ability to distinguish the functional requirements from quality requirements and constraints

Part 3 - Dealing with quality requirements and limitations

• Know the definition of quality requirements and limitations
• Knowing that there is an excellent line between functional requirements and quality requirements, because attributes are sometimes determined by being converted into functions

Part 4 - Behavioral development

• Know that BDD consists of approaches and technologies such as TDD (Test-Driven Development) and ATDD 
• Know that there are different options for specifying requirements
• Know that BDD applies to a wide range of IT system types, e.g., information systems, business intelligence systems, mobile apps

Part 5 - Prioritization and assessment of requirements

• Know different methods to express value, e.g., MoSCoW prioritization, defined value ranges, linear sorting of all requirements, weighted factor methods, and delay costs
• Understand that different stakeholders can see value in requirements

Part 6 - Collaboration between roles

• Understand that iterative system development includes all parts involved in the development process
• Know that architects are constantly interacting with business analysts and requirements experts, as well as developers and testers

Part 7 - Tools for requirements engineering

• Know different types of requirements tools (maps, wikis, modeling tools, issue trackers, etc.)

Part 8 - Requirement engineering examples

• Know the examples of well-articulated requirements of different categories