Thursday, March 09, 2006

Week 9: Usecase

Time flies! It's week 9 now. Today's session is started with presentation of Infrastructure Design for a Regional Food Safety Initiative in Southeast Asia (AFSI in short). It was our assignment during the recess. Several groups were asked to present. Our group got the ‘honour’ to be the first one to present... ^^; After us, follow is a group deriving the life cycle for the animal, other defining the technology behind it, and one group even defining how the system will actually works by using a use-case diagram :D.. It’s quite related with our topic today, which is most regarding the use-case too.

I will be talking about use-case, but not from the same perspective as what we learn in the E-commerce. Yes, I myself am studying use-case in one of my core subject: Software Engineering. It’s proven to be very useful as a visual representation of the interaction between a proposed system and entities in its environment, when we’re doing the requirement analysis in our very first step of software development. Use case can be easily understood by booth programmer and customer, lead to better communication between them.

To better understand what is actually a use case, and how it is going to work, it would be much more straightforward to give an example:

A simplified example of a use case diagram, which illustrates daily interactions with and the functionality of a proposed ATM system, is shown below:


The customer, shown as a stick figure, can check account balance or withdraw cash. Viewed another way, these are the functions provided by the ATM system bounded by the rectangle. Either transaction, checking of balance or cash withdrawal, is subjected to validation of the customer’s PIN. The system can also manage the situation when a cash withdrawal request exceeds the customer’s account balance. Before we go into details of the precise meaning of each notation used, it can be seen that a use case diagram is more intuitive than a long paragraph of text describing the same system. The objective of use case diagrams is therefore to enable a proposed system to be visualized by both the developer and the client in order to better understand and refine its requirements.

With reference to this, I will explain some of the notations used in use case diagrams. We are adhering to the standard Unified Modeling Language (UML) as defined by the Open Methods Group (OMG).

A use case diagram comprises up to 6 different symbols. These are denoted as actor, use case, system boundary, association, generalization, and stereotype.

An actor is represented by a stick figure. It is a role played by an entity that is external to the proposed system and interacts with it. The role is located below the stick figure. An entity may not necessarily be a person. It could be another system. An entity may play more than one role in its

A use case is represented by an ellipse containing the name of the use case. It represents a unit of functionality to be provided by the proposed system that is of direct benefit to an actor. Each unit of functionality may comprise several actions.

The system boundary is represented by a box drawn around the use cases to be provided by the proposed system. It represents the system context in relation to external entities (actors) interacting with the system. The system boundary therefore excludes all actors.

An association is represented by a solid line and represents the relationship between an actor and a use case. An association may be unadorned or adorned with multiplicities. An unadorned solid line is known as a communication in Rational Rose (CASE tool).

A generalization representation can not be used to link up unrelated actors. For example, staff in unrelated departments or students in different faculties. Generalization also can not be used to represent the components of an actor. For example, the different sub-systems of a data management system or the different components of a sensor. Finally, generalization can not be used to represent attribute-type information e.g. a student and his/her associated records.

A stereotype, in the context of use case diagrams, is denoted by a labelled dashed line with an open arrowhead. The label can be either <> or <>. An <> stereotype from use case A to use case B implies that the action(s) specified by use case B is included in use case A. An <> stereotype from use case B to use case A implies that the action(s) specified by use case B is an extension of the typical behaviour of use case A under certain conditions. The <> stereotype and extended use case A may be annotated with additional information describing the extension.

Alright! We have gone through 6 basic notations found in a use case diagram and their usage. :D.. Overall, that covered all the basic we have to know about use-case. The implementation, as what is pointed out during seminar, will depend on each individuality, and there is nothing strange if there is 10 people in a group with 10 different use-cases, yet referring to the same system specification. It’s more than only black and white :D

1 Comments:

At 7:28 PM, Blogger cellprof said...

You are a very accomplished blogger, and it's a pity you don't speak up more in class- you could have contributed a lot to our use-case discussion. Good luck in the future!

 

Post a Comment

<< Home