In 1994 he published a book about use cases and object-oriented techniques applied to business models and business process reengineering. In 1992 he co-authored the book Object-Oriented Software Engineering - A Use Case Driven Approach, which laid the foundation of the OOSE system engineering method and helped to popularize use cases for capturing functional requirements, especially in software development. Originally he had used the terms usage scenarios and usage case – the latter a direct translation of his Swedish term användningsfall – but found that neither of these terms sounded natural in English, and eventually he settled on use case. He described how this technique was used at Ericsson to capture and specify requirements of a system using textual, structural, and visual modeling techniques to drive object-oriented analysis and design. In 1987, Ivar Jacobson presented the first article on use cases at the OOPSLA'87 conference. The detailed requirements may then be captured in the Systems Modeling Language (SysML) or as contractual statements. In systems engineering, use cases are used at a higher level than within software engineering, often representing missions or stakeholder goals. The actor can be a human or another external system.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |