Lonsdale Systems
Menu
UML-Modelling
Courses
Blog
Search
Feed
Resources
Portfolio
Contact
About
All 2 posts
Blog
Blog
Agile-Business-Analysis
Agile-Business-Analysis
Courses
Courses
Requirements-Discovery-Canvas
Requirements-Discovery-Canvas
Essentials-of-Business-Analysis
Essentials-of-Business-Analysis
Software-Testing-Courses
Software-Testing-Courses
Business-Analysis-Courses
Business-Analysis-Courses
UML-Modelling
UML-Modelling
Software-Testing
Software-Testing
Agile-Courses
Agile-Courses
Requirements-Analysis
Requirements-Analysis
Business-Analysis
Business-Analysis
Extreme-Architecture-Framework
Extreme-Architecture-Framework
Lotus-Agenda
Lotus-Agenda
Elicitation
Elicitation
Essentials-of-Business-Analysis Software-Quality
Essentials-of-Business-Analysis Software-Quality
Risk-Based-Testing
Risk-Based-Testing
Test-Automation-Reference-Model
Test-Automation-Reference-Model
Information-Gathering-Techniques
Information-Gathering-Techniques
Change-Driven-Training
Change-Driven-Training
Software-Testing-Canvas
Software-Testing-Canvas
All categories →
Courses
Blog
Search
Feed
Resources
Portfolio
Contact
About
← PREVIOUS
NEXT PAGE →
Rebooting the Use Case Diagram
Use cases have fallen out of favour in recent times with user stories becoming the preferred way for teams to manage requirements. In the rush away from use cases, everyone seems to have forgotten Use Case Diagrams.
The UML Collaboration Element
The collaboration element can be used to highlight a collection of UML elements that collaborate in a way that is not immediately obvious
Courses
Blog
Search
Feed
Resources
Portfolio
Contact
About
Lonsdale Systems
