Learned a lot of practical material. The exercises were very practical also.
JIMMY CHAN - THALES TRANSPORT & SECURITY (HONG-KONG) LIMITED
Requirements Engineering Schulungen
Requirements Engineering courses
Erfahrungsberichte
Requirements Engineering Schulungsübersicht
| Code | Name | Dauer | Übersicht |
|---|---|---|---|
| eraamauml | Efficient Requirement Management using Agile Methods and Agile UML Modeling | 21 hours | Objective: This training course aims at helping product managers, products owners, business analysts, system architects and developers understand how to efficiently Manage Requirements on the basis of the product vision till guiding developers accurately in implementing them. More in detail, this course aims at assisting product managers in better defining the value propositions of their products on the basis of strategies and stakeholder needs. Business Analysts and product owners understand how to describe requirements of the product backlog then discover appropriate epics and user stories of the system while contributing to the required value creation. Along interactive case study exercises, participants learn how to describe in detail such requirements in order to validate correct understanding of needs and prepare system acceptance tests. Thus, only using a very common and productive UML profile, they learn to structure requirements in order to communicate efficiently with architects and developers through an iterative requirement gathering process. Audience: Product Managers Product Owners Business Analysts Anyone interetsted in the Requirements Management Process Introduction What is the Requirement Management Process ? Why Agile ? Business agility and agile software delivery : Definitions Linking Agile to Business : Business Motivation Model vs. Business Model Canvas, How to effciently use the Value Proposition Canvas for defining the Product Vision ? Business agility vs. agile software delivery principles What is Agile Not ? Impacts of alignment with strategies and capabilities Requirement Management in an Agile Context Scrum Life Cycle : Issues about completeness of requirements and traceability How productive models enhance communication in 'Agile' ? Business Extensions of Agile : Structuring Business Value Contribution of a User Story A Panorama of UML diagrams for modeling requirements Frameworks for tracing requirements toward software implementation and tests The 5 levels planning of an agile project (from Clarifying the Vision and Product Backlog to Tasks… and the Architecture Walking Skeleton) Managing Requirements within Agile Methods (Scrum, DAD) vs. the Unified Process (RUP) Roles, teams, environments Presentation of the Case Study for Structuring requirements and managing them using an iterative process How to describe the business vision and needs via traceable models ? Qualification of the requirements : The Kano model vs. the Value Proposition Canvas Structuring the Vision of the Product on the basis of strategies, environmental forces and trends Value proposition, key activities, key resources, revenue streams and cost structures, Discovering the business scope of the product using the customer needs, gains and pains Describing business use cases using 'value streams' and 'value stages' Bridging the business scope of the product with expected 'value contributions' Case Study : Describing the vision of the product How to describe user needs via agile use case modeling (epics and user stories) ? Agile Estimating and Planning Building and managing the product backlog / granularity of requirements Ahead of the sprint planning Creation of the sprint backlog Agile User Story Pattern : system scope (the subject), actors, use cases, user stories, acceptance criteria, the INVEST model The Walking Skeleton using Disciplined Agile Delivery : From Processes to Technology How to find out epics and user stories on the basis of value streams ? Value contribution of epics and user stories Writing tasks : granularity and size using the SMART model Case Study : Discovering epics and user stories on the basis of value streams Validating and testing correct understanding of detailed specifications Using an incremental requirement gathering process and the sprint backlog Rules for efficient epic, user story and architecture descriptions Diagrams for validating epics and user story descriptions How to choose the right diagram ? Refining features using use cases and relationships modeling Testing correct understanding of requirements using Test-Driven Requirements Given/When/Then structures and Operation Contracts for guiding developers in implementing requirements Coverage analysis and change management Case Study : Validating, testing and communicating detailed requirements to developers Conclusion Steps of efficient requirement gathering and system analysis processes Traceability between requirements and analysis models Patterns for gathering and testing requirements Notice: The above training-mentoring sessions are conducted interactively using examples from Requirement Engineering and Modeling tools in order to ensure good level of traceability between requirements and underlying solutions. Concepts are first explained using basic examples and are then followed by solution drafts to your potential case. After this session, we can also accompany you by reviewing and validating your solutions depending on your needs. |
| mbd | Model Based Development for Embedded Systems | 21 hours | Model Based Development (MBD) is a software development methodology that enables faster, more cost-effective development of dynamic systems such as control systems, signal processing and communication systems. It relies on graphic modeling rather than the traditional text based programming. In this instructor-led, live training participants will learn how to apply MBD methodologies to reduce development costs and accelerate the time to market of their embedded software products. By the end of this training, participants will be able to Select and utilize the right tools for implementing MBD. Use MBD to carry out rapid development in the early stages of their embedded software project. Shorten the release of their embedded software into the market. Audience Embedded systems engineers Developers and programmers Format of the course Part lecture, part discussion, exercises and heavy hands-on practice Introduction to Model Based Development Overview of the "system model" Mathematical modeling approaches Establishing the requirements Defining the system Designing the model Preparing your MBD toolkit Verifying and validating the model Simulation tools and practices: Simulink and StateFlow Engineering safety-critical embedded software Tools and approaches for testing your application Detecting and mitigating failures Reusing test suites Refining algorithms through multi-domain simulation Serial code generation Tools and practices: TargetLink SCM tools for managing MBD Using a common design environment across teams Deploying across multiple processors and hardware types Conclusion |
| ISAM1 | ISTQB CTFL | 21 hours | ISTQB CFTL 70% theory + 30% practice SW testing fundamentals Testing throughout the life cycle Static techniques Test design techniques Test management Tool support for testing |
| UML | Objektorientierte Analyse und Design mit UML | 21 hours | This course is intended for analysts, designers, developers, testers and project managers. It is an introduction to system modeling using UML. Based on selected systems (case study) following phases of system modeling are presented: from modeling requirements, through business process modeling and documentation of functional and non-functional requirements, to the analytical model. The next step is the design phase - static and dynamic modeling using project classes and the interaction between the system components. Training can be the basis for a comprehensive process modeling in enterprise systems through the use of UML in all phases of software development. Application and introduction to the web application What is the servlet and JSP page, what they are and how to use them What is the difference between a typical application, a Java web application Web application architecture Discussion of the issues of architecture within the web application Introduction to the discussion of the different layers and application layers and their applications Introduction to MVC What is the model, view and controller, what are the tasks defined within each of these three components of the model. Discussion of problems solvable with the help of the design pattern Servlets Introduction to the abstraction of the servlet, HTTP request handling process Basic HTTP Why HTTP? How does a servlet can handle the request? What type of query you can handle? The life cycle of a servlet Web application What is a web application? What is the application deployment descriptor? In what way the service control flow between the client and the application? What is the client and the server application architecture? Abstract representing the query and answer application. Attributes and HTTP requests and responses Listener interface Flow Control and conversation Introduction to the problem of conversational client application and solutions to common problems through the use of session object Association asking HTTP session and the session life cycle JSP pages What is JSP? What are the common problems solved using JSP pages in a Web application? The role of JSP pages in the application and details of JSP technology behind What are bezskryptowe JSP page? Introduction to EL Introduction to libraries and JSTL custom tag What are tags in the servlet code? How to use JSTL tag libraries and what typical problems solved using this tag? How to define my own tags? Own custom tag library (option 1 day) Issues write your own tag libraries File format descriptor tags When you write your own tag library becomes a necessity? Deployment descriptor: web.xml A thorough discussion of the process of implementing a Web application and file structure implementation Web application security issues (option 1-2) Introduction to the topic of securing web applications Using the API, container, and declarative form of defining access to resources based on roles and users Examples of applications and implementation Filters Discussion of the principles of the declaration and implementation of filters in a web application Declaration principles filters in the deployment descriptor and discuss issues within the subject filters Korporacyjne wzorce projektowe (OPCJA 1 dzień) Overview and introduction to corporate design patterns Struts (OPTIONAL - 1-2days) The introduction of a lightweight MVC web application framework Define and discuss the role of the Shares, Validator and forms within the Struts framework, discussion of control flow within the application based on Struts and write a simple application using the Struts |
| softengret | Software Engineering, Requirements Engineering and Testing | 63 hours | Software Engineering 5 days Day 1: Project Management Project versus line management and maintenance and support Project definition and project forms Management – general rules and project management Management styles What is special for IT projects? Basic project process Iterative, incremental, waterfall, agile and lean project process Project phases Project roles Project documentation and other artefacts Soft factors and peopleware PRINCE 2, PMBOK, PMI, IPMA and other project standards Day 2: Business Analysis and Requirements Engineering Fundamentals Defining business goals Business analysis, business process management, business process improvement The boundary between business and system analysis System stakeholders, system users, system context and system boudaries Why are requirements necessary? What us requirements engineering The boundary between requirements engineering and architectural design Where is requirements engineering often hidden? Requirements engineering in iterative, lean, and agile development and in continuous integration – FDD, DDD, BDD, TDD Basic requirements engineering process, roles and artefacts Standards and certifications: BABOK, ISO/IEEE 29148, IREB, BCS, IIBA Day 3: Architecture and Development Fundamentals Programming languages – structural and object-oriented paradigms Object-oriented development – how much is history, how much is the future Modularity, portability, maintainability and scalability of architectures Definition and type of software architectures Enterprise architecture and system architecture Programming styles Programming environments Programming mistakes and how to avoid and prevent them Modelling architecture and components SOA, Web Services and micro-services Automatic build and continuous integration How much architecture design is there on a project? Extreme programming, TDD and re-factoring Day 4: Quality Assurance and Testing Fundamentals Product quality: what is it? ISO 25010, FURPS etc. Product quality, user experience, Kano Model, customer experience management and integral quality User-centred design, personas and other ways to make quality individual Just-enough quality Quality Assurance and Quality Control Risk strategies in quality control The components of quality assurance: requirements, process control, configuration and change management, verification, validation, testing, static testing and static analysis Risk-based quality assurance Risk-based testing Risk-driven development Boehm’s curve in quality assurance and in testing The four testing schools – which suits your need? Day 5: Process Types, Maturity and Process Improvement The evolution of IT process: from Alan Turing through Big Blue to lean startup Process and process-oriented organization The history of processes in crafts and industries Process modelling: UML, BPMN and more Process management, process optimization, process re-engineering and process management systems Innovative process approaches: Deming, Juran, TPS, Kaizen Is (process) quality free? (Philip Crosby) The need and history of maturity improvement: CMMI, SPICE and other maturity scales Special types of maturity: TMM, TPI (for testing), Requirements Engineering Maturity (Gorschek) Process maturity versus product maturity: any correlation? any causal relationship? Process maturity versus business success: any correlation? any causal relationship? A forsaken lesson: Automated Defect Prevention and The Next Leap in Productivity Attempts: TQM, SixSigma, agile retrospectives, process frameworks Requirements Engineering - 2 days Day 1: Requirements Elicitation, Negotiation, Consolidation and Management Finding requirements: what, when and by whom Stakeholder classification Forgotten stakeholders Defining system context – defining requirements sources Elicitation methods and techniques Prototyping, personas, and requirements elicitation through testing (exploratory and otherwise) Marketing and requirements elicitation – MDRA (“Market-Driven Requirements Engineering”) Prioritising requirements: MoSCoW, Karl Wiegers and other techniques (including agile MMF) Refining requirements – agile “specification by example” Requirements negotiation: types of conflicts, conflict-solving methods Solving internal incongruence between some types of requirements (e.g. security versus ease of use) Requirements traceability – why and how Requirements status changes Requirements CCM, versioning and baselines Product view and project view on requirements Product management and requirements management in projects Day 2: Requirements Analysis, Modelling, Specification, Verification and Validation Analysis is the thinking and re-thinking you do between elicitation and specification Requirements process is always iterative, even in sequential projects Describing requirements in natural language: risks and benefits Requirements modelling: benefits and costs The rules for using natural language for requirements specification Defining and managing requirements glossary UML, BPMN and other formal and semi-formal modelling notations for requirements Using document and sentence templates for requirements description Verification of requirements – goals, levels and methods Validation – with prototyping, reviews and inspections, and testing Requirements validation and system validation Testing - 2 days Day 1: Test Design, Test Execution and Exploratory Testing Test design: after risk-based testing, choosing the optimum way to use the time and resources available Test design “from infinity to here” – exhaustive testing is not possible Test cases and test scenarios Test design on various test levels (from unit to system test level) Test design for static and for dynamic testing Business-oriented and technique-oriented test design (“black-box” and “white-box”) Attempting to break the system (“negative testing”) and supporting the developers (acceptance testing) Test design to achieve test coverage – various test coverage measures Experience-based test design Designing test cases from requirements and system models Test design heuristics and exploratory testing When to design test cases? – traditional and exploratory approach Describing test cases – how much detail? Test execution – psychological aspects Test execution – logging and reporting Designing tests for “non-functional” testing Automatic test design and MBT (Model-Based Testing) Day 2: Test Organization, Management and Automation Test levels (or phases) Who does the testing, and when? – various solutions Test environments: cost, administration, access, responsibility Simulators, emulators and virtual test environment Testing in agile scrum Test team organization and role Test process Test automation – what can be automated? Test execution automation – approaches and tools |
Kommende Kurse
| Course | Schulungsdatum | Kurspreis (Fernkurs / Schulungsraum) |
|---|---|---|
| Object-Oriented Analysis and Design using UML - Hamburg | Mi, 2017-10-11 09:30 | 2750EUR / 3400EUR |
| Efficient Requirement Management using Agile Methods and Agile UML Modeling - Erfurt | Di, 2017-10-17 09:30 | 5850EUR / 6170EUR |
Other regions
Other countries
Consulting
Requirements Engineering Schulung, Requirements Engineering boot camp, Requirements Engineering Abendkurse, Requirements Engineering Wochenendkurse
, Requirements Engineering Seminare, Requirements Engineering Lehrer
, Requirements Engineering Privatkurs, Requirements Engineering Coaching, Requirements Engineering Seminar, Requirements Engineering Training
