Uml Usecase 2007

8/6/2019 Uml Usecase 2007

1/24

Group MembersAishwaraya

Jay shreeSanthosh kumar

Surender

Vijayan

Vishnu arthi


2/24

y Visual modeling.

y UML.

y When can we use UML?

y Diagrams.

y USE CASE Diagramy Actors

y Use cases

y Stereotypes

y Use case diagram for designer as knowledge creatorand user.

y References


3/24

y Software models are similar to

Mechanical

Drawings

Electrical

Schematics

Construction

Blueprints


4/24

7 source files

940 lines of codeOne diagram

OR


5/24

A picture is worth a thousand lines of code


6/24

DOCUMENTATION

REAL APPLICATION

METRICS


7/24

y Unified Modeling Language

An industry standard notation for

y Expressing software Requirements.y Expressing software Architecture.

y Expressing software Dynamics and Behavior.

y Documenting Software Deployment.


8/24

y The UML is the standard notation only.

y It does not specifyprocess at all.

y UML is most effective when combined with effective

software process.


9/24

y Visual UML modeling has been traditionally focused on

ANALYSIS and DESIGN

TestingImplementationDesignAnalysisRequire-

-ments


10/24

y CLARITY: Graphical Depiction of ideas are easy tounderstand.

y AUDIENCE: This Clarity allows a wider audience to

understand and participate.y DISCIPLINE: Modeling, as a rigorous technique,

imposes discipline on the specifications of businessproblems and a common language to understand and

resolve them.


11/24


12/24

An actor specifies a role that some external entityadopts when interacting with your system directly. Itmay represent a user role, or a role played by another

system, that touches the boundary of your system.

Identifying actorsy Who or what uses the system?

y

What roles do they play in the interaction?y Who installs the system?

y Who starts and shutdowns the system?

y Who maintains the system?

y Who gets and provides information to the system?


13/24

A specification of sequences of actions, includingvariant sequences and error sequences, that a system,subsystem or class can perform by interacting with

outside actors.

Finding Use Casesstarts with the actors previously defined

y

Which functions does the actor require from the system?What does the actor need to do?

y Does the actor need to read, create, destroy, modify, or storesome kind of information in the system?

y Does the actor have to be notified about events in the system,

or does the actor need to notify the system about something?


14/24


15/24

A use-case description can be rather difficult tooverview if it contains too many alternatives, optionalor exceptional flows of events that are performed only

if certain conditions are met as the use-case instance iscarried out.


16/24

This relationship occurs when you have behaviorsthat are similar across more than one use case and youdont want to redundantly copy the behavior in each

use case.


17/24


18/24

y Develop a knowledge base system. The software mustprovide the following requirements

y The knowledge base system must contain the process,

procedures etc.., for manufacturing products.y Designers should be able to create knowledge base

system.

y Designers should be able to get details from knowledgebase for design tasks.

y Knowledge base or data base should be able to storeknowledge base data.


19/24


20/24


21/24


22/24


23/24


24/24

y UNIFIED: Result of unifying the information systemsand technology industrys best engineering practices.

y MODELING: a number of models are used to describe

the system.y LANGUAGE: not simply a notation for drawing

diagrams, but a complete language or capturingsemantics about a subject and expressing the same for

the purpose of communication.

Uml Usecase 2007

Documents

Transcript of Uml Usecase 2007