Software Engineering MCQ
Software Engineering MCQ
151. Classification model
- One system is designed as the system controller and has responsibility for managing the execution of other sybsystems.
- 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 characterstics.
- The objective of this software development is zero-defect software.
152. Clean room software development
- One system is designed as the system controller and has responsibiity 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.
153. 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
154. 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
155. Commonality
- It takes project, product hardware and personnel attributes into account when formulating a cost estimate.
- In it server provides set of of services and set of clients uses these services.
- Extent to which standards are used to achieve interoperability
- None of these
156. Transforming of logic and data from design specifications (design descriptions) into a programming language
- Compatibility
- Compactness
- Coding
- Communication
157. An inter change of information between computer systems and peoples or between people.
- Compatibility
- Compactness
- Coding
- Communication
158. Extent to which a system or component makes eficient use of its data storage space-occupies a small volume.
- Comatibiity
- Compactness
- Code
- Communication
159. Entity-relation model is
- It decribes 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 and 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
160. Ability of two or more systems or components to perform their required functions while sharing the same hardware of software environment
- Compatibility
- Compachtness
- Code
- Communication