Module 2 Flashcards
It is a graphical representation of data flow in any system. It is capable of illustrating incoming data flow, outgoing data flow, and stored data.
Data Flow Diagram (DFD)
It mainly focuses on the system
process. It illustrates how data flows in the system.
Logical Data Flow Diagram
It shows how the data flow is
actually implemented in the system. Here, we include additional details such as data storage, data transmission, and specific technology or system components.
Physical Data Flow Diagram (DFD)
It describes the transfer of data between different parts of the system.
Data Flow
Due to the _______ function, input for output transformation occurs in the system.
Process
The data is stored in the warehouse for later use.
Data Store
It is an external entity that lives
outside the system and communicates with it.
Terminator
It represent the hierarchical structure of the module. It breaks down the entire system into the lowest functional modules and explains in detail the functions and sub-functions of each module of the system.
Structure Charts
It represents the process or task of the system
Module
It represents that control module can select any of the sub module on the basis of some condition.
Conditional Call
It represents the repetitive execution of module by the sub module.
Loop
It represents the flow of data between the modules.
Data Flow
It represents the flow of control between the modules.
Control Flow
It is that where all the information are to be stored.
Physical Storage
It organizes the modules of the software system in a hierarchical structure.
HIPO (Hierarchical Input Process Output)
It divides the functionality of a system into sub-functions in a hierarchical manner, but does not provide any information about data flow or control flow
HIPO Diagram
It is the use of simple English to write the structure of code in the programming process.
Structured English
It is a high-level description of a system or process that uses a combination of natural language and simple programming language.
Pseudo-Code
It is a good way to settle different combination inputs with their corresponding outputs and is also called a cause-effect table.
Decision Table
It is used to define the entities to be represented in the data and how these entities are related.
Entity-Relationship Model
It can be defined as a collection of information about any type of data or data content, such as descriptions of data types and systems. It provides all the information about the
names used in the system model.
Data Dictionary
It consist of Names (primary and secondary) and descriptions of Content and Control Items, Internal or External data stores, etc.
Data Elements
It stores the information from where the data enters into the system and exists outside of the system. The data store includes files and tables.
Data Store
It includes the manipulation of data.
Data Processing
This data processing is done at the user level.
Logical Data Processing
This data processing is done at the software level. The user cannot see it.
Physical Data Processing
It is a standard that helps define and evaluate the quality of software and systems. It is part of the SQuaRE (Systems and software Quality Requirements and Evaluation) series.
ISO/IEC 25002:2024
It is a standard that defines the software life cycle processes the steps involved in developing and maintaining software.
ISO/IEC/IEEE 12207:2017
It is a standard that helps in writing and managing requirements for software and systems.
ISO/IEC/IEEE 29148:2011
It is a global standard for quality management systems (QMS).
ISO 9001:2015
These are the limitations or restrictions in the design process imposed by internal and external factors.
Design constraints
It significantly impact design projects because they dictate how far designers can push creative and innovative boundaries.
Technical Constraints
It Impacts many areas of the design process, including human resources, tools, user research, project scope, and technology.
Financial Constraints
It impacts content and user data the most regarding UX projects. These laws change depending on the country, so designers rely on advice from legal counsel and stakeholders.
Legal and Regulatory Constraints
Describe limitations imposed on Design by other parts of the company. These limitations often relate to the organization’s values, culture, company vision, and competing interests from other departments.
Organizational Constraints
Come from the designers, relating to the choices and options during the design process, like which design tool
they use, the time it takes to complete tasks, and whether they use the product’s design system.
Self-Imposed Constraints
Relate to the skills and specialists available to the design team. It’s important to know every designer’s skill set and expertise so that managers can assign people who complement one another.
Talent Constraints
