Software Engineering: Question Set – 16

In the context of modular software design, which combination is considered for cohesion and coupling?

In the context of modular software design, high cohesion, and low coupling is considered.

What is Cohesion and Coupling?

Cohesion:

The level of cohesion in a module is proportional to its overall functional capacity. When performing a single operation, aggregation modules have a reduced need to interface with other elements of the software located in other regions of the application. One coagulation module is all that is required to be active, according to the ideal scenario. The degree to which a module retains its cohesiveness is referred to as its cohesion. A module is functionally independent of other modules if it has a high level of cohesiveness but a low level of connection. In this context, “functional independence” refers to the fact that each cohesive module is responsible for only one action or function. The term “coupling” refers to the comprehensive association that exists between the modules.

Coupling:

The information that is provided through the interface, in conjunction with the complexity of the interface that exists between the modules in which the reference to the section or module was formed, is necessary for coupling. Strong support for coupling Modules with a low coupling factor make the assumption that there are almost no other modules. It becomes extremely important in situations where both modules share a lot of information with one another. The degree of complexity of the interface between two modules is directly proportional to the level of coupling that exists between them.

What is the name of various CASE tools?

  • Requirement Analysis Tool
  • Structure Analysis Tool
  • Software Design Tool
  • Code Generation Tool
  • Test Case Generation Tool
  • Document Production Tool
  • Reverse Engineering Tool

What is level-0 DFD?

DFD refers to the level of abstraction that is immediately below Level 0 as Level 1. It is also referred to as DFD at the context level. It presents a single diagram that depicts the full information system.

What is physical DFD?

The Physical DFD is concerned with the manner in which the system is put into operation. After completing the creation of a logical DFD, the next diagram to be drawn is a physical DFD. It provides an explanation of the most effective way to put the system’s business operations into practice. In addition to this, it includes the actual installation of the devices and files that are necessary for the business processes. To put it another way, the physical DFD includes all of the information pertaining to implantation, including the hardware, personnel, and other external components that are necessary to carry out business activities.

What is the black hole concept in DFD?

In a data flow diagram, the term “block hole” refers to a concept that reads as follows: “A processing step may have input flows but no exit flows.” Within a black hole, data can only be stored if it comes in from the outside.

Mentions some software analysis & design tools?

  • Data Flow Diagrams
  • Structured Charts
  • Structured English
  • Data Dictionary
  • Hierarchical Input Process Output diagrams
  • Entity Relationship Diagrams and Decision tables

What is a use case diagram?

One type of behaviour diagram is called a use case diagram, and it is used to represent the observable interactions that take place between actors and the system that is being developed. The system, the use cases that are associated with it, and the actors are all represented on the diagram, along with their respective relationships to one another:

  • System: What is being described?
  • Actor: Who is using the system?
  • Use Case: What are the actors doing?

≪ Previous Page | Next Page ≫