Assignment 3.2: understanding UML
Look up the links that Yishay has sent (posted on LKL blog) re UML and find out a bit more about it.
then try and use UML to make a diagram of my use case scenario.
I'm looking at site about UML and use case diagrams which trys to explain what they are, how you make one, and why they are useful.According to this:
The UML is applicable to object-oriented problem solving. Anyone interested in learning UML must be familiar with the underlying tenet of object-oriented problem solving -- it all begins with the construction of a model. A model is an abstraction of the underlying problem. The domain is the actual world from which the problem comes.
Models consist of objects that interact by sending each other messages. Think of an object as "alive." Objects have things they know (attributes) and things they can do (behaviors or operations). The values of an object's attributes determine its state.
Classes are the "blueprints" for objects. A class wraps attributes (data) and behaviors (methods or functions) into a single distinct entity. Objects are instances of classes.
Use case diagrams describe what a system does from the standpoint of an external observer. The emphasis is on what a system does rather than how.
Use case diagrams are closely connected to scenarios. A scenario is an example of what happens when someone interacts with the system. Here is a scenario for a medical clinic.
"A patient calls the clinic to make an appointment for a yearly checkup. The receptionist finds the nearest empty time slot in the appointment book and schedules the appointment for that time slot. "
A use case is a summary of scenarios for a single task or goal. An actor is who or what initiates the events involved in that task. Actors are simply roles that people or objects play. The picture below is a Make Appointment use case for the medical clinic. The actor is a Patient. The connection between actor and use case is a communication association (or communication for short).
Actors are stick figures. Use cases are ovals. Communications are lines that link actors to use cases.
A use case diagram is a collection of actors, use cases, and their communications. We've put Make Appointment as part of a diagram with four actors and four use cases. Notice that a single use case can have multiple actors.
Use case diagrams are helpful in three areas.
determining features (requirements). New use cases often generate new requirements as the system is analyzed and the design takes shape.
communicating with clients. Their notational simplicity makes use case diagrams a good way for developers to communicate with clients.
generating test cases. The collection of scenarios for a use case may suggest a suite of test cases for those scenarios.
another good link detailing the elements in a use case scenario>
This makes sense to me but i can not think my idea of the essay into a set of actors, use cases and communications (which probably means i am not clear enough at all).
then try and use UML to make a diagram of my use case scenario.
I'm looking at site about UML and use case diagrams which trys to explain what they are, how you make one, and why they are useful.According to this:
The UML is applicable to object-oriented problem solving. Anyone interested in learning UML must be familiar with the underlying tenet of object-oriented problem solving -- it all begins with the construction of a model. A model is an abstraction of the underlying problem. The domain is the actual world from which the problem comes.
Models consist of objects that interact by sending each other messages. Think of an object as "alive." Objects have things they know (attributes) and things they can do (behaviors or operations). The values of an object's attributes determine its state.
Classes are the "blueprints" for objects. A class wraps attributes (data) and behaviors (methods or functions) into a single distinct entity. Objects are instances of classes.
Use case diagrams describe what a system does from the standpoint of an external observer. The emphasis is on what a system does rather than how.
Use case diagrams are closely connected to scenarios. A scenario is an example of what happens when someone interacts with the system. Here is a scenario for a medical clinic.
"A patient calls the clinic to make an appointment for a yearly checkup. The receptionist finds the nearest empty time slot in the appointment book and schedules the appointment for that time slot. "
A use case is a summary of scenarios for a single task or goal. An actor is who or what initiates the events involved in that task. Actors are simply roles that people or objects play. The picture below is a Make Appointment use case for the medical clinic. The actor is a Patient. The connection between actor and use case is a communication association (or communication for short).
Actors are stick figures. Use cases are ovals. Communications are lines that link actors to use cases.
A use case diagram is a collection of actors, use cases, and their communications. We've put Make Appointment as part of a diagram with four actors and four use cases. Notice that a single use case can have multiple actors.
Use case diagrams are helpful in three areas.
determining features (requirements). New use cases often generate new requirements as the system is analyzed and the design takes shape.
communicating with clients. Their notational simplicity makes use case diagrams a good way for developers to communicate with clients.
generating test cases. The collection of scenarios for a use case may suggest a suite of test cases for those scenarios.
another good link detailing the elements in a use case scenario>
This makes sense to me but i can not think my idea of the essay into a set of actors, use cases and communications (which probably means i am not clear enough at all).
posted by carey at 10:13 AM
0 Comments:
Post a Comment
<< Home