Beruflich Dokumente
Kultur Dokumente
Q1. How does a use case report differ from a Data Flow Diagram?
Ans. (Contributed by Prerna Kejriwal)
Data Flow Diagram :
Physical data flow diagrams are implementation-dependent. They show the actual devices, depart
people, etc., involved in the current system.
Logical data flow diagrams, in contrast, describe the system independently of how it is actually
implemented; that is, they show what takes place, rather than how an activity is accomplished.
Both types of data flow diagrams support a top-down approach to systems analysis, whereby anal
begin by developing a general understanding of the system and gradually explode components in
greater detail. As details are added, information about control can also be included, although uppe
level general diagrams are drawn without showing specific control issues to ensure focuses on dat
processes.
a. An input data flow with information added by the process (for example, an annoted invoice)
b. A response or change of data form (such as change of profit dollars into profit percentage)
c. Change of status (from unapproved to approved status)
d. Change of content (assembly or separation of information contained in one or more incoming
data flows)
e. Change in organization (for example, the physical separation or rearrangement of data)
When beginning a systems study in an unfamiliar area, you need to get the lay of the land. Physical elem
stand out first: the people, reports and documents, file cabinets and in-baskets, and events. It’s not unus
remember certain key people or places. Physical data flow diagrams depict these physical elements.
Once you have the lay of the land, the essentials of a task can be studied more carefully. You need to ge
below the surface, so to speak. That’s what logical data flow diagrams are all about.
Logical data flow diagrams describe data, processes, and events differently. They are more abstract than
physical data flow diagrams, but that difference is important. As an analyst, you have to know more abou
job that must be done than the people who are actually doing the work. This doesn’t mean that people ar
important, for they surely are. But if a key worker becomes ill or chooses to leave the company, the work
remain. Desks, files and computers will change, too. By focusing on the understanding elements – the log
nonphysical aspects – you gain an understanding of the fundamental structure of the system. Only then c
you develop a complete understanding and form a basis for designing the right system.
In the above diagram, there are three actors: the customer, the bank officer, and the credit system. Ther
six major pieces of functionality the system will provide: depositing funds, transferring funds, withdrawin
money, changing a PIN, viewing a balance, and making a payment.
One of the major benefits of a Use Case diagrams is communication. Your customers can look at this diag
and receive a great deal of information. By looking at the use cases, they will know what functionality wil
included in the system. By looking at the actors, they will know exactly who will be interfacing with the sy
By looking at the set of use cases and actors, they will know exactly what the scope of the project will be
can help them identify up front any missing functionality.
Site Search
Web
© 2009 Microsoft | Privacy | Legal | Feedback
Add a Search Box to your website!
SPONSORED SITES