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
Week 8: Podcasting
Today, We're having quiz. I was late for 15 minutes for the quiz.. since i was coming from North Spine.. :'(.. felt a bit rush at the end..
Later, after the quiz, we're discussing about the mobile phone technology, how it get smaller and smaller.. and eventually reach it limit. We’re talking of how to implement a better lifetime for mobile phone. One idea is to program the mobile phone such that not all application is running all the time. And one more idea is, to find alternative energy for the mobile phone. One suggested using Solar energy. Will it be possible in the future? Let’s see :D
Right after the discussion of Mobile phone, we move on to podcast, the highlight of this week. The first time I hear about it, I thought that it must be some fancy name related to the Apple most popular product, Ipod. However, it’s not the case. the company did contribute both the desire and the technology for this capability. But the podcast word itself isn’t originated from there. Interested? Below is the story of podcast:
"Podcasting" is a portmanteau word coined in 2004 that combined two words: "iPod" and "broadcasting."
While the name was primarily associated with audio subscriptions in 2004, the RSS enclosure syndication technique had been used with video files since 2001, before portable video players were widely available.
Atom, a recently developed web syndication format, supports rich media content by design, as does standard RSS 2.0 based upon XML 1.0 standards. In fact, any file with a URL, including still images and text, can be delivered via a web feed.
Use of "podcast" to describe both audio and video feeds seemed natural to some users, while others preferred to reserve the word for audio and coin new terms for video subscriptions. Other "pod-" derived neologisms include "podcasters" for individuals or organizations offering feeds, and "podcatchers" for special RSS aggregators with the ability to transfer the files to media player software or hardware.
Neither podcasting nor listening to podcasts requires an iPod or other portable player, and no over-the-air broadcasting is required. The name association came about simply because Apple Computer's iPod was the most marketed and the best-selling portable digital audio player when podcasting b

egan, and was used by early practitioners.
However, the use of the "pod" name in 2004 probably played a part in Apple's development of podcasting products and services in 2005, further linking the device and the activity in the news media.
The editors of the New Oxford American Dictionary declared "podcasting" the 2005 word of the year in December, defining the term as "a digital recording of a radio broadcast or similar program, made available on the Internet for downloading to a personal audio player".
From the beginning various writers suggested other names or alternative interpretations of the letters "P-O-D." Technology writer Doc Searls had proposed "Personal Option Digital" in September, 2004. The "Personal On Demand" interpretation was in international circulation as early as October 2004. In July 2005, Microsoft blogger Robert Scoble mentioned that interpretation while countering reports that his company was pushing the word "blogcasting" to avoid mentioning an Apple product. "Blogcasting" also implied content based on, or similar in format to, blogs, which was not always the case.
Another Apple rival in the portable audio and video market, Creative Technology, began using the "Personal On Demand" interpretation, while offering its own "Zencasts.
Other terms have been suggested, but had shortcomings -- "audioblogging," "audio magazines" and "webcasting" could describe other forms of media distribution, and "rsscasting" would be difficult to pronounce.
Podcasting as a medium was first associated with, but never limited to, audio data. As use of RSS enclosures for video spread in 2005, podcasting of video data was called, among other things, "video blogging", "video podcasting", "vlogging", "vodcasting", or "vidcasting".
Subscribing to podcasts allows a user to collect programs from a variety of sources for listening or viewing off-line, whenever and wherever is convenient. In contrast, traditional broadcasting provides only one source at a time, and the time is broadcaster-specified. While podcasts are gaining ground on personal sites and blogs, they are not yet widespread. One easy way to find podcasts is to use the Podcast Directory in iTunes; these automatically-updated podcasts can then be easily synchronised to an iPod for off-line listening.
"Streaming" files from the Internet can remove the specified-time restriction, but still offers only one source at a time, and requires the user to be connected to the Internet while playing the files. The ability to "aggregate" programs from multiple sources is a major part of the attraction of podcast-listening.
Unlike podcasts, streaming also can be used to broadcast live events over the Internet at the moment they occur.
Although streamed programs, like broadcast radio signals, can be recorded or captured by the receiver, their transient nature distinguishes them from podcast episodes, which arrive already in archived form. (This difference may make a podcast legally distinct from a webcast or streamed media file.)