Data Oriented Analysis And Design_13112014_072811am 262s

Darshan Institute of Engineering & Technology 1)

Unit : 4

List five requirement of library Information system. Draw DFD lavel-0 and DFD level-1 for Library management system. There are many different types of requirements like functional requirement, non functional requirement, requirement etc. These are shown here. Figure 1 DED at level-0 Library Information System

 Here inside 0 level data flow diagram, there will be one process called library management system.  There are many entities that directly interact with this system.  For example Student can issue a book a book, pays fine, get library card, issue book as well as request or return a book.  Demanded book will be displayed inside this system. Figure 2 DED at level-1 Library Information System

Prepared By : Chirag Patel

Page 1

Darshan Institute of Engineering & Technology

Unit : 4

 Librarian will provide return date and book.  It is possible to describe this process more deeply and we can get many processes inside DFD level-1.  Here process of library management system is divided into many processes like, Get books, find book positions, update list of borrowed books, search by topic etc.  For that purpose there will be some data dictionaries required like, book shelf, List of Authors, List of titles, list of topics, list of borrowed books etc. Figure 2 DFD at level-1 of library management system

2)

Prepare an E-R Diagram for a simple Library Management System and explain it.

Inside E-R diagram, there are many entities and there were some relationship among different entities. Name of entities are given below:  Book: It is set of books and magazines which are available inside library record.  Member: It may be set of either staff or students.  Supplier: It is one entity which may have set of suppliers (Book stall) which provides books.  Publisher: It is set of publications who publish the books. There are many kind of relationship among different entities like,  Book is published by publisher  Book is supplied by any supplier  Book may be borrowed by any member like a staff or a student, Prepared By : Chirag Patel

Page 2

Darshan Institute of Engineering & Technology

Unit : 4

There are different kinds of characteristics for any single entity called as attributes. Various attributes are given for any entity inside above figure.

Prepared By : Chirag Patel

Page 3

Darshan Institute of Engineering & Technology 3)

Unit : 4

What is swim-lane diagram explain with example.  The UML swimlane diagram is a useful variation of the activity diagram and allows you to represent the flow of activities described by the use case and at the same time indicate which actor (if there are multiple actors involved in a specific use case) or analysis class (discussed later in this chapter) has responsibility for the action described by an activity rectangle.  Responsibilities are represented as parallel segments that divide the diagram vertically, like the lanes in a swimming pool.  Three analysis classes—Homeowner, Camera, and Interface—have direct or indirect responsibilities in the context of the activity diagram represented in Figure

 Referring to Figure the activity diagram is rearranged so that activities associated with a particular analysis class fall inside the swimlane for that class. For example, the Interface class represents the interface as seen by the homeowner. Prepared By : Chirag Patel

Page 4

Darshan Institute of Engineering & Technology

Unit : 4

 The activity diagram notes two prompts that are the responsibility of the interface—“prompt for reentry” and “prompt for another view.” These prompts and the decisions associated with them fall within the Interface swimlane.  However, arrows lead from that swimlane back to the Homeowner swimlane, where homeowner actions occur. Use cases, along with the activity and swimlane diagrams, are procedurally oriented.  They represent the manner in which various actors invoke specific functions (or other procedural steps) to meet the requirements of the system. But a procedural view of requirements represents only a single dimension of a system.

4)

Explain the difference between dfd and er diagram with symbols and example. A set of fundamental software design concepts has evolved over the past four decades. Although the degree of interest in each concept has varied over the years, each has tood the test of time. Data Flow Diagram Entity Relationship Diagram

Prepared By : Chirag Patel

Page 5

Darshan Institute of Engineering & Technology

Unit : 4

1. A data flow diagram (DFD) is a graphical 1. Entity–relationship model (ER model) representation of the "flow" of data through in software engineering is an abstract an information system, modeling its process way to describe a database. aspects.

2. It contains external entity, process and 2. It contains entity, relationship, data dictionary attributes for any entity etc.

3. It contains various levels like level 0, level 1 3. There is no any level for E R Diagram etc.

4. It will give idea about how data will ed 4. It will give idea about what kind of and how output will be generated. relationship among various entities.

5)

Using appropriate example explain data dictionary.  The data dictionary is an organized listing of all data elements. Both and system analyst will have a common understanding of inputs, outputs, components of stores and intermediate calculations.  The format of dictionaries varies from tool to tool, most contain the following information:

Prepared By : Chirag Patel

Page 6

Darshan Institute of Engineering & Technology

Unit : 4

 Name—the primary name of the data or control item, the data store or an external entity.  Alias—other names used for the first entry.  Where-used/how-used—a listing of the processes that use the data or control item and how it is used.  Content description—a notation for representing content.  Supplementary information—other information about data types, preset values (if known), restrictions or limitations, and so forth.  Once a data object or control item name and its aliases are entered into the data dictionary, consistency in naming can be enforced.  The notation used to develop a content description is noted in the following table: Sr No Data Construct Notation Meaning 1 Sequence + and 2 Selection [|] Either-or 3 Repetition {}n n repetitions of 4 --= Is composed of 5 --() Optional data 6 --*...* Delimits comments The notation enables a software engineer to represent composite data in one of the three fundamental ways that it can be constructed: 1. As a sequence of data items. 2. As a selection from among a set of data items. 3. As a repeated grouping of data items.  Each data item entry that is represented as part of a sequence, selection, or repetition may itself be another composite data item that needs further refinement within the dictionary.  To illustrate the use of the data dictionary, we have the monitor system process for Safe Home, shown in Figure. The data item telephone number is specified as input. Telephone number could be a 7-digit local number, a 4-digit extension, or a 25-digit long distance carrier sequence.  In addition it indicates where and how this data item is used and any supplementary information that is relevant to it. The data dictionary entry begins as follows: Fig-8 Data dictionary Name: Aliases: Where used/how used

telephone number None assess against set-up(output) dial phone(input)

description: telephone number = [local number | long distance number] local number = prefix + access number long distance number= area code + access number

For large computer-based systems, the data dictionary grows rapidly in size and complexity. In fact, Prepared By : Chirag Patel

Page 7

Darshan Institute of Engineering & Technology

Unit : 4

it is extremely difficult to maintain a dictionary manually. For this reason, CASE tools should be used. 6)

Using appropriate example explain control flow mode.  A control flow diagram (CFD) is a diagram to describe the control flow of a business process, process or program.  It shows how events flow among processes.  It also shows how external events activate the processes.  The dashed arrow is used to represent the control flow or events.  A solid bar is used to represent the window.  The widow is used to control processes used in the DFD based on the event.  Two commonly used representations:  Control Specification(CSPEC), which is used to indicate How the software behaves when an event is sensed  Process Specification(PSPEC), used to describe the inner workings of the process  When a data input to the process a data condition should occur to get the control output.  There are certain events that are control driven rather than data driven. Such application can be modelled with the control information along with data modelling.  Guidelines:  List all the sensors that can be read.  List all the interrupt conditions  List all the data conditions  List all the switches actuated by the operator.  Use noun/verb processing technique to identify the control information.  Avoid common errors while specifying the control.

7)

Explain feasibility study with the example of atm machine in banking system. Draw use case diagram of atm machine.  Inside a ATM banking system, first of all it should be checked whether your product will be feasible or bot.

Prepared By : Chirag Patel

Page 8

Darshan Institute of Engineering & Technology

Unit : 4

 It will be tested based on various criteria called as feasibility study. There are 4 different dimensions: Technology  For ATM system, we have to check whether this project is technically feasible or not?  If any kind of errors may be generated inside your appliocation then it may be reduced through technology. Finance  A next criterion is also checked whether the product is financially feasible or not.  Cost of software and market price both should be considered. Time  There will be some time duration inside your product should be completed.  At the specific time it should be deployed. Resource  To create the product there will be some requirements of resources. It should be fulfilled.  Use case diagram of ATM system is shown below.  There are various actors like, Bank customer, Cashier and Maintenance person.  Cashier is the person who deposites money and then he will not present at the ATM center.  Same, maintenance person check machine and repair machine. But he will not present at ATM center.  Customer can perform following activities at ATM center:  Withdraw money  Check balance  Check PIN  Money transfer etc.  At the time of authentication it may be possible that person may enter wrong PIN or he may want help.

Prepared By : Chirag Patel

Page 9

Darshan Institute of Engineering & Technology

Prepared By : Chirag Patel

Unit : 4

Page 10