Software Testing and Specification Quiz

False (B)

<p>Syntactic and semantic domains.</p> Signup and view all the answers

<p>error</p> Signup and view all the answers

<p>False (B)</p> Signup and view all the answers

<p>Corrective maintenance, perfective maintenance, adaptive maintenance</p> Signup and view all the answers

<p>Syntactic domain = Set of formation rules and symbols Semantic domain = Modeling of system's semantics Satisfaction relation = Relation between syntactic and semantic domains</p> Signup and view all the answers

<p>development</p> Signup and view all the answers

<p>Relationship between syntax and semantics (C)</p> Signup and view all the answers

<p>Perfective maintenance (B)</p> Signup and view all the answers

<p>True (A)</p> Signup and view all the answers

<p>Actions to be taken when conditions are satisfied.</p> Signup and view all the answers

<p>α-testing = Performed by the development team β-testing = Performed by a friendly set of customers Acceptance testing = Performed by the customer after product delivery</p> Signup and view all the answers

<p>40:60 (B)</p> Signup and view all the answers

<p>mathematical</p> Signup and view all the answers

<p>It does not change its input value. (C)</p> Signup and view all the answers

<p>True (A)</p> Signup and view all the answers

<p>The state of outputs after the function has executed.</p> Signup and view all the answers

<p>abstract</p> Signup and view all the answers

<p>300 (C)</p> Signup and view all the answers

<p>False (B)</p> Signup and view all the answers

<p>Software Requirement Specification</p> Signup and view all the answers

<p>X′</p> Signup and view all the answers

<p>Architectural Design = High-level system abstraction Detailed Design = Specific implementation decisions User Interface Design = How users interact with the system</p> Signup and view all the answers

<p>Requirements for implementation (A)</p> Signup and view all the answers

<p>Temporal cohesion (B)</p> Signup and view all the answers

<p>False (B)</p> Signup and view all the answers

<p>coupling and cohesion</p> Signup and view all the answers

<p>Sequential</p> Signup and view all the answers

<p>Co-incidental cohesion = Unplanned random cohesion Logically categorized cohesion = Logical cohesion Execution sequence-based cohesion = Procedural cohesion Data-focused cohesion = Communicational cohesion Single well-defined function cohesion = Functional cohesion</p> Signup and view all the answers

<p>Interaction among sub-systems and modules (D)</p> Signup and view all the answers

<p>False (B)</p> Signup and view all the answers

<p>Divide a software system into multiple discrete and independent modules.</p> Signup and view all the answers

<p>concurrency</p> Signup and view all the answers

<p>Easier maintenance = Smaller components are easier to manage. Functional division = Program can be divided based on functional aspects. Reusability = Components with high cohesion can be reused. Security = Modular design offers desired security aspects.</p> Signup and view all the answers

<p>High execution speed (B)</p> Signup and view all the answers

<p>False (B)</p> Signup and view all the answers

<p>It makes components easier to maintain.</p> Signup and view all the answers

<p>modular</p> Signup and view all the answers

<p>Detailed design (C)</p> Signup and view all the answers

The process of combining different modules of a software product into a working system.

Testing done by the development team to ensure the integrated system meets the original requirements.

Testing performed by external users (like customers) to ensure the product functions correctly and meets their needs.

Testing conducted by the customer after delivery to decide whether to accept or reject the product.

The process of detecting and correcting errors found in a software product after its initial release.

Enhancing existing functionality of the software based on customer requirements.

Adapting the software to work in new environments, like different operating systems or platforms.

A measure of how well the elements within a module relate to each other. Higher cohesion means a module is more focused and organized.

A weak type of cohesion where elements are grouped together for no clear reason, making the module difficult to understand and maintain.

When elements are grouped because they are processed at similar times, even if they have unrelated functions.

A measure of how much modules depend on each other. Lower coupling means modules are more independent and easier to maintain.

The strongest type of cohesion, where all elements contribute to a single well-defined function.

A mathematical method used to describe and analyze software or hardware systems. It involves rigorous techniques to ensure correctness, reliability, and efficiency.

A language that employs a formal system to define the behavior and structure of a system.

A set of rules for combining symbols to form well-formed formulas in a formal language.

A set of objects and their relationships used to interpret the meaning of formulas in a formal language.

A collection of rules in a decision table representing a condition and its corresponding action.

A table that organizes conditions and actions in a structured format, where each column represents a rule.

A formal specification that describes a desired behavior or functionality of a system.

A formal specification that describes how a system is implemented or realized.

A representation of the system that satisfies the given specification.

A process that transforms user needs into a usable form for programmers.

A document outlining the detailed requirements for a software project.

The highest level of abstraction in software design, outlining the overall structure and components of the system.

A design level that focuses on specific modules and their interactions within the software.

A design level that specifies the internal working of each module, including data structures and algorithms.

A function that always produces the same output for a given input and doesn't modify any external data.

Conditions that must be true before executing a function.

Conditions that must be true after a function completes execution.

A declaration defining the type, name, input arguments, and output of a function.

Utilizing statements in function specifications to ensure correctness and maintainability.

High-level design breaks down the abstract system into smaller, interacting subsystems and modules. It focuses on how the system can be implemented in modular form.

Modularization is splitting a software system into independent units called modules that perform specific tasks. Each module can be built and tested separately.

Smaller components are easier to maintain, the system can be divided by function, desired levels of abstraction can be achieved, reusable modules can be created, concurrent execution is possible, and security is improved.

Software traditionally ran in a sequential manner, executing instructions one by one. This means only one part of the program was active at a given time.

Concurrency splits software into independent units of execution (like modules) and runs them in parallel. This allows multiple parts of the code to execute simultaneously.

Concurrency in software improves performance by allowing multiple parts of the program to execute simultaneously, making better use of available resources.