“Computers must support the way in which people naturally and comfortably work. This is needed both for personal job satisfaction and for corporate survival. I care about whether the team is thriving, and whether the software is being delivered. Keeping the people trained and the process light are key to both.”
Humans and Technology, Inc.
In 1986, Ivar Jacobson first formulated the visual modeling technique for specifying use cases. Originally he used the terms usage scenarios and usage case, but found that neither of these terms sounded natural in English, and eventually he settled on the term use case.
Since then, use cases have become one of the most accepted forms of specifying software requirements.
By the end of the course the student will be able to understand what must happen prior to analysis, define requirements efficiently and effectively and create analysis artifacts, such as use-cases and domain models, using the UML notation.
Through course exercises the student will understand how requirements are used to follow an iterative-incremental use-case driven process.
This course is targeted towards project managers, technical leaders, architects, development staff and test engineers.