Skip to main content

Use Case Vs DFD, Difference in Use Case – DFD

-

 

Now a days almost all applications are based on OOP (object oriented programming); and use case diagrams depicts the functionality to be implemented in a system. On the other hand DFD (Data Flow Diagram) is the true depiction of OOP based programming.  

Use Case & Data Flow Diagram are same?

  • Use case diagrams and DFD are not contradicting each other as far as system architecture is concerned.
  • DFD diagram and Use case diagram are used to view the system from different perspective/angle.
  • A graphical representation of the flow of data or information in a system or part of system. It consists of data flows, processes, sources, destinations and stores.

Difference Between Use Case & Data Flow Diagram

  • A DFD(Data Flow Diagram) only shows the sources and destinations of data coming and going from the system and the transformation of data when it passes through some system process.
  • A Use Case is used to capture the functional requirements of the system. A use case is a high- level piece of functionality that the system will provide to different actors interacting with the system.

So from the above, you can conclude two simple definition of Data flow Diagram and Use Case.

DFD (Data Flow Diagram)

DFD is concerned with the flow of information/data and processes in the system working with this information/data. It helps in identifying any business processes or existing business processes.

At most simply you can say a data flow is about how data flow and how it will be used in system. And for more elaboration where data will be saved.

Start with context diagram simple representation of whole system. So for the further representation we do 1 more level and dig again to go through 3 level after that it’ is not much necessary to dig more. More levels needed when asked for more process information.

Read more from Visual Paradigm

Use Case

Use case is concerned with defining about what the system has to offer to its users. You can say  Unified modeling language to it.  Moreover while developing software’s or in systems engineering, all actions we performed or event happening in this model or software defined by use case. What are achievement we want to get defined by use case. Actors in use case either human or external system or you can say a bot or data server. Higher levels software’s use these use cases where all the thing must shown.

Read more from Wikipedia

Comments

Post a Comment

Popular posts from this blog

Data Consistency and Inconsistency - What is Difference

-
Image
  Data Consistency: Definition 1: Data consistency means that the changes made to the different occurrences of data should be controlled and managed in such a way that all the occurrences have the same value for any specific data item. Data inconsistency leads to a number of problems, including loss of information and incorrect results. In the database approach, it is controlled because data is shared and consistency is controlled and maintained. Data Consistency Definition 2: Data consistency meaning is the validity, accuracy and usability of related data. It ensures that each user observes a consistent(Same) view of the data, including changes made by the user’s own transactions and transactions of other users. Types of Data Consistency: Point in time consistency Transaction consistency Application consistency Data Inconsistncy: Data Inconsistency Definition: Data inconsistency meaning is that different versions of the same data appear in diffe
Read more

Cardinality in DBMS – max/minimum cardinality & examples

-
Image
  Logical Relationship in Tables: Database tables have a major advantage to bridge them with some logical relationship so to filter the records. These relationship allowed us to access one table data using another table records(via columns or rows). In other words logical filtration is called cardinality DBMS. Read Also: Relational Model in DBMS Definitions of Cardinality in DBMS: Definition 1: A number that represents, one instance of first entity(table) is related to how many instances of the second entity, is known as cardinality in dbms. Definition 2: Cardinality is a relationship or join/bridge between rows of  1 table to the rows of another table. via some column (e.g. User Table column {user_id} in another table Posts to filter the posts by user_id). Types of Cardinality in DBMS: There are three types of Cardinality in DBMS. one-to-one one-to-many many-to-one many-to-many Read Also: Degree of Relationship in DBMS one-to-one
Read more

Relational Model in DBMS

-
Image
  Relational Model (RM) represents the database as a collection of relationships. A relationship is nothing more than a table of values. Each row of the table represents a collection of related data values. These rows of the table denote a real-world entity or relationship. The table name and column names are useful for interpreting the meaning of the values in each row. Data are represented as a set of relationships. In the relational model, the data are stored as tables. However, the physical storage of data is independent of how data is organized logically. Some popular relational database management systems are: DB2 and Informix Dynamic Server – IBM Oracle and RDB – Oracle SQL Server and Access – Microsoft Concepts of relational model in DBMS Attribute: Each column in a table. Attributes are the properties that define a relationship. e.g. Student_Rollno, NAME, etc. Tables – In the Relational model the relationships are saved in table format. It is s
Read more