Use Cases for Business Analysis The use case is a method for documenting the interactions between the user of a system and the system itself. Use cases have been in the software development lexicon for over twenty years, ever since it was introduced by Ivar Jacobson in the late 1980s. They were originally intended as aids to software design in object-oriented approaches. However, the method is now used throughout the Solution Development Life Cycle from elicitation through to specifying test cases, and is even applied to software development that is not object oriented. This course identifies how business analysts can apply use cases to the processes of defining the problem domain through elicitation, analyzing the problem, defining the solution, and confirming the validity and usability of the solution. What you will Learn You'll learn how to: Apply the use case method to define the problem domain and discover the conditions that need improvement in a business process Employ use cases in the analysis of requirements and information to create a solution to the business problem Translate use cases into requirements Getting Started Introductions Course structure Course goals and objectives Foundation Concepts Overview of use case modeling What is a use case model? The 'how and why' of use cases When to perform use case modeling Where use cases fit into the solution life cycle Use cases in the problem domain Use cases in the solution domain Use case strengths and weaknesses Use case variations Use case driven development Use case lexicon Use cases Actors and roles Associations Goals Boundaries Use cases though the life cycle Use cases in the life cycle Managing requirements with use cases The life cycle is use case driven Elicitation with Use Cases Overview of the basic mechanics and vocabulary of use cases Apply methods of use case elicitation to define the problem domain, or 'as is' process Use case diagrams Why diagram? Partitioning the domain Use case diagramming guidelines How to employ use case diagrams in elicitation Guidelines for use case elicitation sessions Eliciting the problem domain Use case descriptions Use case generic description template Alternative templates Elements Pre and post conditions Main Success Scenario The conversation Alternate paths Exception paths Writing good use case descriptions Eliciting the detailed workflow with use case descriptions Additional information about use cases Analyzing Requirements with Use Cases Use case analysis on existing requirements Confirming and validating requirements with use cases Confirming and validating information with use cases Defining the actors and use cases in a set of requirements Creating the scenarios Essential (requirements) use case Use case level of detail Use Case Analysis Techniques Generalization and Specialization When to use generalization or specialization Generalization and specialization of actors Generalization and specialization of use cases Examples Associating generalizations Subtleties and guidelines Use Case Extensions The <> association The <> association Applying the extensions Incorporating extension points into use case descriptions Why use these extensions? Extensions or separate use cases Guidelines for extensions Applying use case extensions Patterns and anomalies o Redundant actors Linking hierarchies Granularity issues Non-user interface use cases Quality considerations Use case modeling errors to avoid Evaluating use case descriptions Use case quality checklist Relationship between Use Cases and Business Requirements Creating a Requirements Specification from Use Cases Flowing the conversation into requirements Mapping to functional specifications Adding non-functional requirements Relating use cases to other artifacts Wire diagrams and user interface specifications Tying use cases to test cases and scenarios Project plans and project schedules Relationship between Use Cases and Functional Specifications System use cases Reviewing business use cases Balancing use cases Use case realizations Expanding and explaining complexity Activity diagrams State Machine diagrams Sequence diagrams Activity Diagrams Applying what we know Extension points Use case chaining Identifying decision points Use Case Good Practices The documentation trail for use cases Use case re-use Use case checklist Summary What did we learn, and how can we implement this in our work environment?
Use Cases for Business Analysis: In-House Training The use case is a method for documenting the interactions between the user of a system and the system itself. Use cases have been in the software development lexicon for over twenty years, ever since it was introduced by Ivar Jacobson in the late 1980s. They were originally intended as aids to software design in object-oriented approaches. However, the method is now used throughout the Solution Development Life Cycle from elicitation through to specifying test cases, and is even applied to software development that is not object oriented. This course identifies how business analysts can apply use cases to the processes of defining the problem domain through elicitation, analyzing the problem, defining the solution, and confirming the validity and usability of the solution. What you will Learn You'll learn how to: Apply the use case method to define the problem domain and discover the conditions that need improvement in a business process Employ use cases in the analysis of requirements and information to create a solution to the business problem Translate use cases into requirements Getting Started Introductions Course structure Course goals and objectives Foundation Concepts Overview of use case modeling What is a use case model? The 'how and why' of use cases When to perform use case modeling Where use cases fit into the solution life cycle Use cases in the problem domain Use cases in the solution domain Use case strengths and weaknesses Use case variations Use case driven development Use case lexicon Use cases Actors and roles Associations Goals Boundaries Use cases though the life cycle Use cases in the life cycle Managing requirements with use cases The life cycle is use case driven Elicitation with Use Cases Overview of the basic mechanics and vocabulary of use cases Apply methods of use case elicitation to define the problem domain, or 'as is' process Use case diagrams Why diagram? Partitioning the domain Use case diagramming guidelines How to employ use case diagrams in elicitation Guidelines for use case elicitation sessions Eliciting the problem domain Use case descriptions Use case generic description template Alternative templates Elements Pre and post conditions Main Success Scenario The conversation Alternate paths Exception paths Writing good use case descriptions Eliciting the detailed workflow with use case descriptions Additional information about use cases Analyzing Requirements with Use Cases Use case analysis on existing requirements Confirming and validating requirements with use cases Confirming and validating information with use cases Defining the actors and use cases in a set of requirements Creating the scenarios Essential (requirements) use case Use case level of detail Use Case Analysis Techniques Generalization and Specialization When to use generalization or specialization Generalization and specialization of actors Generalization and specialization of use cases Examples Associating generalizations Subtleties and guidelines Use Case Extensions The <> association The <> association Applying the extensions Incorporating extension points into use case descriptions Why use these extensions? Extensions or separate use cases Guidelines for extensions Applying use case extensions Patterns and anomalies o Redundant actors Linking hierarchies Granularity issues Non-user interface use cases Quality considerations Use case modeling errors to avoid Evaluating use case descriptions Use case quality checklist Relationship between Use Cases and Business Requirements Creating a Requirements Specification from Use Cases Flowing the conversation into requirements Mapping to functional specifications Adding non-functional requirements Relating use cases to other artifacts Wire diagrams and user interface specifications Tying use cases to test cases and scenarios Project plans and project schedules Relationship between Use Cases and Functional Specifications System use cases Reviewing business use cases Balancing use cases Use case realizations Expanding and explaining complexity Activity diagrams State Machine diagrams Sequence diagrams Activity Diagrams Applying what we know Extension points Use case chaining Identifying decision points Use Case Good Practices The documentation trail for use cases Use case re-use Use case checklist Summary What did we learn, and how can we implement this in our work environment?
ISTQB® FOUNDATION TRAINING COURSE (2 persons minimum) The aim of this course is to provide you with the knowledge and skills to pass an exam certifying you as an ISTQB® Certified Tester - Foundation Level. Most organisations require this certification as a minimum skill requirement for software testers. In this course you will learn a standardized approach to software testing that will be immediately applicable to your projects. In order to get the certification you will be required to pass a 60-minute exam. Our trainers will fully prepare you by employing scenarios that mirror the exam questions, and by focusing course delivery with a balance of theory and practice. Target group: Functional Tester, Agile Tester, User Acceptance Tester, Test Automation Specialist, Performance Testing Specialist, Testing Team Lead, Test Manager, Business analyst Prerequisites: There are no specific prerequisites for this course. This course is suitable for anyone involved in software testing. Duration: 3 days. Training objectives: Learn aspects of test planning, estimation, monitoring and control. Understand and use international standards and terminology. Understand and implement effective testing techniques. Be well prepared for the exam. Identify the missing testing skills for the career development purposes. This course covers the following areas: Fundamentals of software testing Testing throughout the life cycle (software development models, test levels, test types) Test design techniques (e.g. specification-based or black-box techniques, structure-based or white-box techniques) Static testing (static testing techniques, review process, tool-assisted static analysis) Test management (test organisation, test planning and estimation, test progress monitoring and control, risks) Tools to support testing (types, benefits and risks) Language: English
This course shows you how to apply various approaches and algorithms to solve business problems through AI and ML, follow a methodical workflow to develop sound solutions, use open-source, off-the-shelf tools to develop, test, and deploy those solutions, and ensure that they protect the privacy of users. This course includes hands-on activities for each topic area.
Introduction to Agile and Scrum This half-day course provides an overview of Agile principles and mindset, and the Scrum framework as a key Agile approach. It will provide you with the key benefits of an Agile approach, and its differences with the traditional Waterfall method. Lastly, as Agile is looked upon more frequently as an alternative delivery method, you will review situations where Agile can be adapted outside of software development, where it is most commonly used. What you will Learn At the end of this program, you will be able to: Explain the basics and benefits of using an Agile approach Describe the Scrum framework, its events, artifacts and roles and responsibilities Illustrate Agile approaches outside of Software Development Getting Started Introduction Course structure Course goals and objectives Agile Introduction What is Agile? Agile Benefits Agile Methods Overview of Scrum Scrum Overview Scrum Events Scrum Artifacts Scrum Roles Definition of Done Agile Approaches Outside of Software Development Agile in other environments Product Development Course Development Marketing Agile Project Candidates Summary What Agile is not... Concerns and Pitfalls
Introduction to Agile for Executives: In-House Training This session provides executives with an overview of Agile values and principles, the key benefits of an Agile approach, and its differences with the traditional Waterfall method. During the session, we compare and contrast the major Agile methods, with an emphasis on Scrum, as the most popular in the market. And most importantly, we present some criteria for Agile Transformation, possible certifications to pursue, and what is needed at the senior leadership level to achieve the best business results. What you will Learn At the end of this program, you will be able to: Explain the basics and benefits of using an Agile approach Describe the Scrum framework, its events, artifacts, and roles and responsibilities Illustrate an Agile approach outside of Software Development Define Scaled Agile Determine how to support an Agile transformation for your organization Getting Started Introduction Course structure Course goals and objectives Agile Introduction What is Agile? Agile benefits Agile myths and realities Overview of Agile Methods Overview of Agile methods Scrum method Lean and Kanban methods Criteria and certifications What Executives Need to Know About Agile Agile is not just for IT Agile can be scaled Agile transformation needs your support Summary and Next Steps Review Personal Action Plan
Introduction to Agile for Executives This session provides executives with an overview of Agile values and principles, the key benefits of an Agile approach, and its differences with the traditional Waterfall method. During the session, we compare and contrast the major Agile methods, with an emphasis on Scrum, as the most popular in the market. And most importantly, we present some criteria for Agile Transformation, possible certifications to pursue, and what is needed at the senior leadership level to achieve the best business results. What you will Learn At the end of this program, you will be able to: Explain the basics and benefits of using an Agile approach Describe the Scrum framework, its events, artifacts, and roles and responsibilities Illustrate an Agile approach outside of Software Development Define Scaled Agile Determine how to support an Agile transformation for your organization Getting Started Introduction Course structure Course goals and objectives Agile Introduction What is Agile? Agile benefits Agile myths and realities Overview of Agile Methods Overview of Agile methods Scrum method Lean and Kanban methods Criteria and certifications What Executives Need to Know About Agile Agile is not just for IT Agile can be scaled Agile transformation needs your support Summary and Next Steps Review Personal Action Plan
How to be a Great Executive Sponsor: In-House Training This three-hour course provides key tips and techniques for becoming an actively engaged, and impactful, Executive Sponsor of projects and programs. It will explain not just what your role is, but the very specific actions you can, and must, take to increase your project's probability of success. This three-hour course provides key tips and techniques for becoming an actively engaged, and impactful, Executive Sponsor of projects and programs. It will explain not just what your role is, but the very specific actions you can, and must, take to increase your project's probability of success. And, it will highlight the key personality and other traits that are found in successful Sponsors. Regardless if you're sponsoring an Agile software development project, a construction megaproject, or any other type of project in between, this course will help get you 'hit the ground running' and being an 'impact player' on day one. Various activities and discussions will acquaint you with this important role and what you need to do to become a great executive sponsor. What you Will Learn At the end of this program, you will be able to: Define project success so everyone is 'singing from the same sheet of music' Immediately apply the ten key attributes of a great sponsor on your project Recognize great sponsorship and determine if you're the right fit for the role Practice Sponsorship over the course of the project life cycle by engaging in very specific actions and activities Be a better investment manager by analyzing the behaviors of successful activist investors Foundation Concepts The quantifiable benefits of being an actively engaged Sponsor Sponsor defined Clarence Kelly Johnson and the SR-71 Blackbird: An example of the power of Sponsorship Defining Project Success Project success: More than meeting the triple constraints Benefits management: The Sponsor's focus The Investment - Life-cycle vs. the Project Life-cycle The three questions Sponsors need to ask to define project success 10 Key Attributes of a Great Sponsor 10 Key Attributes of a Great Sponsor The Makings of a Great Sponsor The most important skills and competencies of an executive sponsor What great Sponsors do and when Four Things a Great Sponsor Can Learn from an Activist Investor The story of Outerwall, Inc. and Glen Welling of Engaged Capital, LLC Sponsors and Activist Investors Sponsorship of the 2nd Avenue Subway in Manhattan: A classic textbook example
How to be a Great Executive Sponsor This three-hour course provides key tips and techniques for becoming an actively engaged, and impactful, Executive Sponsor of projects and programs. It will explain not just what your role is, but the very specific actions you can, and must, take to increase your project's probability of success. This three-hour course provides key tips and techniques for becoming an actively engaged, and impactful, Executive Sponsor of projects and programs. It will explain not just what your role is, but the very specific actions you can, and must, take to increase your project's probability of success. And, it will highlight the key personality and other traits that are found in successful Sponsors. Regardless if you're sponsoring an Agile software development project, a construction megaproject, or any other type of project in between, this course will help get you 'hit the ground running' and being an 'impact player' on day one. Various activities and discussions will acquaint you with this important role and what you need to do to become a great executive sponsor. What you Will Learn At the end of this program, you will be able to: Define project success so everyone is 'singing from the same sheet of music' Immediately apply the ten key attributes of a great sponsor on your project Recognize great sponsorship and determine if you're the right fit for the role Practice Sponsorship over the course of the project life cycle by engaging in very specific actions and activities Be a better investment manager by analyzing the behaviors of successful activist investors Foundation Concepts The quantifiable benefits of being an actively engaged Sponsor Sponsor defined Clarence Kelly Johnson and the SR-71 Blackbird: An example of the power of Sponsorship Defining Project Success Project success: More than meeting the triple constraints Benefits management: The Sponsor's focus The Investment - Life-cycle vs. the Project Life-cycle The three questions Sponsors need to ask to define project success 10 Key Attributes of a Great Sponsor 10 Key Attributes of a Great Sponsor The Makings of a Great Sponsor The most important skills and competencies of an executive sponsor What great Sponsors do and when Four Things a Great Sponsor Can Learn from an Activist Investor The story of Outerwall, Inc. and Glen Welling of Engaged Capital, LLC Sponsors and Activist Investors Sponsorship of the 2nd Avenue Subway in Manhattan: A classic textbook example
Introduction to Agile and Scrum: In-House Training This half-day course provides an overview of Agile principles and mindset, and the Scrum framework as a key Agile approach. It will provide you with the key benefits of an Agile approach, and its differences with the traditional Waterfall method. Lastly, as Agile is looked upon more frequently as an alternative delivery method, you will review situations where Agile can be adapted outside of software development, where it is most commonly used. What you will Learn At the end of this program, you will be able to: Explain the basics and benefits of using an Agile approach Describe the Scrum framework, its events, artifacts and roles and responsibilities Illustrate Agile approaches outside of Software Development Getting Started Introduction Course structure Course goals and objectives Agile Introduction What is Agile? Agile Benefits Agile Methods Overview of Scrum Scrum Overview Scrum Events Scrum Artifacts Scrum Roles Definition of Done Agile Approaches Outside of Software Development Agile in other environments Product Development Course Development Marketing Agile Project Candidates Summary What Agile is not... Concerns and Pitfalls