1 / 70

UML

Objectives. Identify actors from a problem statement.Identify use cases from a problem statement.Learn how to create a use-case diagram that accurately models the system.Learn how to write use-case specification, glossary, and supplementary specification document.. The Purpose of the Requirements

hien
Download Presentation

UML

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

    1. UML Use Case Modeling

    2. Objectives Identify actors from a problem statement. Identify use cases from a problem statement. Learn how to create a use-case diagram that accurately models the system. Learn how to write use-case specification, glossary, and supplementary specification document. The Requirements Overview module provides an overview of the activities that immediately precede Analysis and Design. It is meant to describe the interface between the Requirements and the Analysis and Design disciplines. The Requirements Overview module provides enough information to give you an appreciation for the Requirements discipline, and enable you to read and interpret the Requirements artifacts that serve as the starting point for the Analysis and Design activities.   The Requirements Overview module provides an overview of the activities that immediately precede Analysis and Design. It is meant to describe the interface between the Requirements and the Analysis and Design disciplines. The Requirements Overview module provides enough information to give you an appreciation for the Requirements discipline, and enable you to read and interpret the Requirements artifacts that serve as the starting point for the Analysis and Design activities.  

    3. The Purpose of the Requirements Discipline The Requirements discipline intends to: Find agreement on what the system should do. Provide a better understanding of the system requirements. Define the boundaries of the system. Provide a basis for planning the technical contents of iterations. Provide a basis for estimating cost. Define a user-interface for the system. The purpose of the Requirements discipline is to: Establish and maintain agreement with the customers and other stakeholders on what the system should do. Provide system developers with a better understanding of the system requirements. Define the boundaries of (delimit) the system. Provide a basis for planning the technical contents of iterations. Provide a basis for estimating cost and time to develop the system. Define a user-interface for the system, focusing on the needs and goals of the users. The purpose of the Requirements discipline is to: Establish and maintain agreement with the customers and other stakeholders on what the system should do. Provide system developers with a better understanding of the system requirements. Define the boundaries of (delimit) the system. Provide a basis for planning the technical contents of iterations. Provide a basis for estimating cost and time to develop the system. Define a user-interface for the system, focusing on the needs and goals of the users.

More Related