Use cases (Systems engineering)

Enlarge text Shrink text
  • Topic
| מספר מערכת 987007532654505171
Information for Authority record
Name (Hebrew)
תרחישי שימוש (הנדסת מערכות)
Name (Latin)
Use cases (Systems engineering)
See Also From tracing topical name
Systems engineering
MARC
MARC
Other Identifiers
Wikidata: Q613417
Library of congress: sh 98004228
Sources of Information
  • Work cat.: 98-29948: Schneider, G. Applying use cases, 1998:CIP galley (use cases are a way of defining system requirements from a user point of view. They are used in the developments analysis phase of a project, as well as contributing to test plans and user guides. They are used to validate a proposed design and to ensure it meets all requirements. Use cases are also used when creating a project schedule, helping to plan what goes into each release.)
  • Alta Vista, July 17, 1998(titles: use cases)
Wikipedia description:

In software and systems engineering, a use case is a potential scenario in which a system receives an external request (such as user input) and responds to it. A use case is a list of actions or event steps typically defining the interactions between a role (known in the Unified Modeling Language (UML) as an actor) and a system to achieve a goal. The actor can be a human or another external system. In systems engineering, use cases are used at a higher level than within software engineering, often representing missions or stakeholder goals. The detailed requirements may then be captured in the Systems Modeling Language (SysML) or as contractual statements.

Read more on Wikipedia >