On This Page

This set of Software Engineering Multiple Choice Questions & Answers (MCQs) focuses on Software Engineering Set 16

Q1 | Behavioral models is
  • Here each component has a unique name and an associated set of attribute, which differs for each version of component
  • Extent to which a software system records information concerning transac- tions performed against the system.
  • Extent to which a system or component is operational and accessible when required for use
  • Used to describe the over all behavior of the system
Q2 | In Bottom-up integration
  • The low-level components of a system are integrated and tested before the higher-level components have been developed
  • The testing process starts with modules at lower levels in the hierarchy and works up the hierarchy of modules until the final module is tested.
  • An event driven control system, where an event is broadcasted to each sub- system and any sub-system that can handle that event responds to it.
  • Control starts of the top of a sub routine hierarchy and through sub routine calls passes to lower levels.
Q3 | In Broadcast models
  • The low-level components of a system are integrated and tested before the higher-level components have been developed.
  • The testing process starts with modules at lower levels in the hierarchy and works up the hierarchy of modules until the final module is tested
  • An event driven control system, where an event is broadcasted to each sub- system and any sub-system that can handle that event responds to it.
  • Control starts of the top of a sub routine hierarchy and through sub routine calls passes to lower levels.
Q4 | Bottom-up testing
  • The low-level components of a system are integrated and tested before the higher-level components have been developed.
  • The testing process starts with modules at lower levels in the hierarchy and works up the hierarchy of modules until the final module is tested.
  • An event driven control system, where an event is broadcasted to each sub- system and any sub-system that can handle that event responds to it.
  • Control starts of the top of a sub routine hierarchy and through sub routine calls passes to lower levels.
Q5 | In Call-return control model
  • The low-level components of a system are integrated and tested before the higher-level components have been developed.
  • The testing process starts with modules at lower levels in the hierarchy and works up the hierarchy of modules until the final module is tested.
  • An event driven control system, where an event is broadcasted to each sub- system and any sub-system that can handle that event responds to it.
  • Control starts of the top of a sub routine hierarchy and through sub routine calls passes to lower levels
Q6 | Capacity is
  • A measure of the amount of work a system can perform
  • It provides automated support for software process.
  • Support individual process tasks
  • Set of tools to support a particular phase of software process such as design, implementation or testing.
Q7 | CASE (Computer Aided Software Engineering) is
  • A measure of the amount of work a system can perform
  • It provides automated support for software process.
  • Support individual process tasks
  • Set of tools to support a particular phase of software process such as design, implementation or testing:
Q8 | CASE Tools
  • A measure of the amount of work a system can perform
  • It provides automated support for software process.
  • Support individual process tasks
  • Set of tools to support a particular phase of software process such as design, implementation or testing
Q9 | CASE Workbench
  • A measure of the amount of work a system can perform
  • It provides automated support for software process.
  • Support individual process tasks
  • Set of tools to support a particular phase of software process such as design, implementation or testing
Q10 | Centralized control models
  • Here one system is designed as the system controller and has responsibility for managing the execution of other subsystems.
  • Each system is named as in attribute- based identification and associated with one or more change requests.
  • An object class inheritance diagram, how entities have common characteristics.
  • The objective of this software development is zero-defect software.
Q11 | Change-oriented identification
  • One system is designed as the system controller and has responsibility for managing the execution of other subsystems.
  • Each system is named as in attribute- based identification and associated with one or more change requests.
  • An object class inheritance diagram, how entities have common characteristics.
  • The objective of this software development is zero-defect software.
Q12 | Hard real time systems are
  • These system runs on a single processor or an integrated group of processors
  • A system where each sub-system can respond to generated events where the events might be generated from other sub-systems or from the environment of the system.
  • A system continues in operation after some system faults have manifested themselves.
  • A system whose operation is incorrect, if results are not produced according to the timing specifications
Q13 | Classification model
  • One system is designed as the system controller and has responsibility for managing the execution of other subsystems.
  • Each system is named as in attribute- based identification and associated with one or more change requests.
  • An object class inheritance diagram, how entities have common characteristics.
  • The objective of this software develop- ment is zero-defect software.
Q14 | Clean room software development
  • One system is designed as the system controller and has responsibility for managing the execution of other subsystems.
  • Each system is named as in attribute- based identification and associated with one or more change requests.
  • An object class inheritance diagram, how entities have common characteristics.
  • The objective is to develop zero-defect software.
Q15 | COCOMO cost model
  • It takes project, product hardware and personnel attributes into account when formulating a cost estimate.
  • In it server provides set of services and set of clients uses these services.
  • Extent to which standards are used to achieve interoperability.
  • None of these
Q16 | Client server architecture
  • It takes project, product hardware and personnel attributes into account when formulating a cost estimate.
  • In it server provides set of services and set of clients uses these services.
  • Extent to which standards are used to achieve interoperability.
  • None of these
Q17 | Commonality
  • It takes project, product hardware and personnel attributes into account when formulating a cost estimate.
  • In it server provides set of services and set of clients uses these services.
  • Extent to which standards are used to achieve interoperability
  • None of these
Q18 | Transforming of logic and data from designspecifications (design descriptions) into a programming language
  • Compatibility
  • Compactness
  • Coding
  • Communication
Q19 | An inter change of information between computer systems and peoples or between people.
  • Compatibility
  • Compactness
  • Coding
  • Communication
Q20 | Extent to which a system or component makes efficient use of its data storage space- occupies a small volume.
  • Compatibility
  • Compactness
  • Code
  • Communication
Q21 | Entity-relation model is
  • It describes the basic entities in the design and relation between them.
  • Observational techniques used to understand social and organizational requirements.
  • It is based on the idea of developing an initial implementation, exposing it uses on requirement and refining it through many versions until an adequate system has been developed.
  • Based on an idea of developing an initial implementation, exposing this to uses comment and retiring it until and adequate system has been developed.
Q22 | Ability of two or more systems or components to perform their required functions while sharing the same hardware or software environment
  • Compatibility
  • Compactness
  • Code
  • Communication
Q23 | Completeness in software system is referred as
  • Extent to which all the parts of a software system or component are present and each of its parts is fully specified and developed.
  • Testing of individual hardware/software components
  • An Entity-relation (E-R) diagram show how entities in the system are composed of other entities.
  • It consists of wide range of different types of computer programs, which be used to support software process activities such as a requirement analysis, system modeling, debugging and testing.
Q24 | Composition model is
  • Extent to which all the parts of a software system or component are present and each of its parts is fully specified and developed.
  • Testing of individual hardware/software components
  • An Entity-relation (E-R) diagram show how entities in the system are composed of other entities
  • It consists of wide range of different types of computer programs, which be used to support software process activities such as a requirement analysis, system modeling, debugging and testing.
Q25 | Match the following : A-Control metrics : B- Process metrics: C- Control: D-Correctness: 1- They are associated with software process. 2- They are associated with software products. 3- Protective measure that reduces system vulnerability. 4- Extent to which a system or component is free from faults in its specification, design, and implementation
  • A-1, B-2,C-3,D-4
  • A-4,B-3,C-2,D-1
  • A-3, B-2,C-1,D-4
  • None is true