Scenarios and Use Cases

Categories:

• School

Use-case

The use-cases symbol on the use case diagram shows what the actor wants to do. Not how that user goal is achieved,

Each Use-cases describe how event triggers actions performed by the system and the user. Everything can be thought of as a response to trigger event. When a trigger event occurs, the system performs the actions defined in the use-case.

Lab2

Tutorial 2: Gathering Requirements for your chosen Case Study (no formal submission needed)

This week you can do the requirements gathering for one of the design briefs (mentioned in Assignment 1 – where you have to choose the design brief based on your family name). List these requirements appropriately (e.g. create requirements definition report).

first try:

Lab3

What is UML? Why do we need this?

Unified Modeling Language, is a standardized modeling language consisting of an integrated set of diagrams, developed to help system and software developers for specifying, visualizing, constructing, and documenting the artifacts of software systems, as well as for business modeling and other non-software systems.

 techniques to automate the production of software and to improve quality and reduce cost and time-to-market.  techniques to manage the complexity of systems as they increase in scope and scale. In particular, they recognize the need to solve recurring architectural problems, such as physical distribution, concurrency, replication, security, load balancing and fault tolerance.  (UML) was designed to respond to these needs.   What does a use case diagram represent and what are the different elements of a use case diagram?

A Use Case Diagram in Unified Modeling Language (UML) is a visual representation that illustrates the interactions between users (actors) and a system.

It captures the functional requirements of a system, showing how different users engage with various use cases, or specific functionalities, within the system.

Actor, UseCase, SystemBoundary

What are we documenting when we place a use case on the diagram?

What are we documenting when we place an actor on the diagram?

Which of the following could be an actor found on a use-case diagram? Why? o Ms. Mary Smith

o Supplier

o Customer

o Internet Customer

o Data Entry Clerk

o Database Administrator

How is use-case diagramming related to functional modeling?

Why do we draw association lines between actors and use cases?