Business Analyst Training on Use Case Fields
Use Cases header information is essential to learn how to capture correctly in business analyst training. We describe the various fields you need in a Use Case in Video Fourteen.
Skip to content
Use Cases header information is essential to learn how to capture correctly in business analyst training. We describe the various fields you need in a Use Case in Video Fourteen.
Software requirements gathering projects almost always use use cases or some form of them to understand what a user hopes to accomplish in the new system. Video Thirteen, describes use
In early May, I had the opportunity to spend a few days up in the lovely (albeit rainy and cold) city of Toronto, Canada with my fellow core team members
Decision Trees are an important topic in business analyst training because they are essential when you find detailed logic in Process Flows. Video twelve, describes how and when to create
State Tables help us identify all possible state transitions for an object during business analyst training. We cover the format and how to do State Tables in part eleven of
Process Flows are a core model in almost all software requirements gathering projects. We will cover Process Flow syntax, how to create them, and an example of one in this
As a Business Analyst creating your software requirement models, do you ever wonder, when would you use a State Table as compared to a State Diagram? Now, I’m not going
Software requirements gathering is the key to project success at ArgonDigital. In Part Nine of our new series, “Requirements Visualization Training: A Guide to RML,” we cover using State Diagrams
Org Charts are a model to use very early in the software requirements gathering process to identify all of your stakeholders. In part seven, “Org Charts Early On” you will
System Context Diagrams are a project that should be used very eary in a software requirements gathering project. In video six, “Using System Context Diagrams in Software Requirements Gathering”, we
There are many models to use in the software requirements gathering process. We use an Affinity Diagram to group the models of RML® you might use in part five, “An
People, systems, data is a categorization you can use to organize your requirements models for software requirements gathering. We explain this categorization from RML® in “People, Systems, Data Models for
Don’t miss out on this opportunity
and request a conversation today!
Cookie | Duration | Description |
---|---|---|
cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |