Requirements Modeling and Use Cases, Part I
Loading...
Loading...
8,186
Link to this comment:
Share to:
Loading...
- 9:56UML Tutorial - Use Case, Activity, and Sequence...by bidwx9,567 views
- 10:33Use Case Diagramby dnfvideo9,744 views
- 3:41Business Analyst Interview Questions Answers Vi...by futurethoughtsllc14,945 views
- 9:35Requirements Analysisby mikemurphycs439 views
- 7:30Requirements Managementby NotionSolutions3,716 views
- 2:10Functional Requirementsby WestbrookStevens6,166 views
- 3:08Roles of a Business Analyst - what is business ...by futurethoughtsllc4,121 views
- 3:28Software Architectureby RavenMarineVideos4,813 views
- 2:16A Business Analysist In Actionby burdetteanalysis13,908 views
- 4:03Business Analysis - BA Collective - Documentationby businessanalysis7,969 views
- 5:28Business Requirement Documentationby AJPconsulting1,577 views
- 3:493.03_A Use Case Diagram for an ATMby rmb190525,331 views
- 9:26UML Sequence Digramby dnfvideo10,815 views
- 3:22Software Requirements Elicitation Part-2by influencesunil2,603 views
- 5:163.01_Use Case Basicsby rmb190517,266 views
- 3:41Use Case Modelingby shrrajeev609 views
- 3:283.02_Modeling Use Case Elementsby rmb19057,672 views
- 0:41Differences between use case model and text use...by requirementsinc1,077 views
- 7:47Requirements Modeling and Use Cases, Part IIby cjumpdotcom3,552 views
- 45:18Working with Use Case Diagramsby ignousocis16,182 views
Pls don't use this shit voice ... I hate it.. :-((
AJSwisgirl 7 months ago
@badassdesi: ok, I'll agree to call UCs requirements, but only if they are part of an overall reqs package that includes a vision, higher-level requests/features, low-level detailed bus rules, and user/system interfaces. My bias against calling them reqs is from enterprise projects where UCs alone were the *only* "reqs" allowed. These dozens projects were disasters with lots of customer anger, re-work, and 5-10x cost overruns until the "requirements process expert" was fired.
Cheers
gma683e066736 1 year ago
@badassdesi: use cases illustrate the *cases* where an actor *uses* high-level features. Inside the use cases are references to detailed business rules. The features and business rules constitute the functional requirements, and with them alone a developer could design a solution. With UCs alone a dev could not design a soln, because they are not the actual requirements.
Cheers
gma683e066736 1 year ago
@gma683e066736 yr approach is correct when you say define the requirements and illustrate how they are used in the use case. However, if you are deriving use cases from business reqns or feature reqns how do u not call them use case 'requirements'?
badassdesi 1 year ago
some more nonsense...........
badassdesi 1 year ago
Use cases are not requirements. They are scenario driven threads showing the usage of the requirements. Define the requirements first, then write use cases to illustrate how they are used. Again, USE CASES ARE NOT REQUIREMENTS.
gma683e066736 2 years ago 2
Very simple, clear, and straightforward overview of use cases in requirements analysis. I recommend this video for anyone on the business side of the house who wants to at the very least learn the lingo used by analysts and technologists.
agileBA 2 years ago