True or False Data models can be either logical or physical. Ideally, a data flo
ID: 3757620 • Letter: T
Question
True or False
Data models can be either logical or physical.
Ideally, a data flow diagram should not have more than about twelve processes.
CRUD stands for create, read, update and delete and can be used to verify DFDs and ERDs.
In an entity called STUDENT, you might find attributes of Student-ID, Last-Name, First-Name and cell-phone.
In data flow diagrams, a repository of data is called a ‘data flow’.
A Level-0 Diagram is data flow diagram that is the result of nested decompositions of a series of sub processes from a process.
One of the first places to start developing Entity Relationship Diagrams is by looking at the level 0 process models (DFD) and the use cases for data flows and data stores.
A data flow has only one direction of flow between symbols.
Relationships are drawn with lines showing cardinality and plurality.
The major inputs and major outputs listed on the use case provide a list of the sources and destinations of the inflows and outflows on the processes on a data flow diagram.
When validating ERD’s you should balance ERD entities with the data flows and data stores from the DFD process diagrams.
True or False
Data models can be either logical or physical.
Ideally, a data flow diagram should not have more than about twelve processes.
CRUD stands for create, read, update and delete and can be used to verify DFDs and ERDs.
In an entity called STUDENT, you might find attributes of Student-ID, Last-Name, First-Name and cell-phone.
In data flow diagrams, a repository of data is called a ‘data flow’.
A Level-0 Diagram is data flow diagram that is the result of nested decompositions of a series of sub processes from a process.
One of the first places to start developing Entity Relationship Diagrams is by looking at the level 0 process models (DFD) and the use cases for data flows and data stores.
A data flow has only one direction of flow between symbols.
Relationships are drawn with lines showing cardinality and plurality.
The major inputs and major outputs listed on the use case provide a list of the sources and destinations of the inflows and outflows on the processes on a data flow diagram.
When validating ERD’s you should balance ERD entities with the data flows and data stores from the DFD process diagrams.
Explanation / Answer
Data models can be either logical or physical – True Ideally, a data flow diagram should not have more than about twelve processes – True CRUD stands for create, read, update and delete and can be used to verify DFDs and ERDs – True In an entity called STUDENT, you might find attributes of Student-ID, Last-Name, First-Name and cell-phone. – True In data flow diagrams, a repository of data is called a ‘data flow’. – False A Level-0 Diagram is data flow diagram that is the result of nested decompositions of a series of sub processes from a process- False One of the first places to start developing Entity Relationship Diagrams is by looking at the level 0 process models (DFD) and the use cases for data flows and data stores. – True A data flow has only one direction of flow between symbols.- True Relationships are drawn with lines showing cardinality and plurality. – True The major inputs and major outputs listed on the use case provide a list of the sources and destinations of the inflows and outflows on the processes on a data flow diagram.- True When validating ERD’s you should balance ERD entities with the data flows and data stores from the DFD process diagrams.- True
Related Questions
drjack9650@gmail.com
Navigate
Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.