McqMate
These multiple-choice questions (MCQs) are designed to enhance your knowledge and understanding in the following areas: Computer Science Engineering (CSE) , Information Technology Engineering (IT) , Bachelor of Science in Computer Science SY (BSc CS) , Bachelor of Computer Applications (BCA) , Bachelor of Business Administration in Computer Applications (BBA [CA]) .
Chapters
| 751. |
The outcome of construction phased can be treated as: |
| A. | Product release |
| B. | Beta release |
| C. | Alpha release |
| D. | All of the above |
| Answer» B. Beta release | |
| 752. |
Which one is not a step of requirement engineering? |
| A. | Requirements elicitation |
| B. | Requirements analysis |
| C. | Requirements design |
| D. | Requirements documentation |
| Answer» C. Requirements design | |
| 753. |
Requirements elicitation means |
| A. | Gathering of requirements |
| B. | Capturing of requirements |
| C. | Understanding of requirements |
| D. | All of the above |
| Answer» D. All of the above | |
| 754. |
SRS stands for |
| A. | Software requirements specification |
| B. | System requirements specification |
| C. | Systematic requirements specifications |
| D. | None of the above |
| Answer» A. Software requirements specification | |
| 755. |
SRS document is for |
| A. | “What” of a system? |
| B. | How to design the system? |
| C. | Costing and scheduling of a system |
| D. | System’s requirement. |
| Answer» A. “What” of a system? | |
| 756. |
Requirements review process is carried out to |
| A. | Spend time in requirements gathering |
| B. | Improve the quality of SRS |
| C. | Document the requirements |
| D. | None of the above |
| Answer» B. Improve the quality of SRS | |
| 757. |
Which one of the statements is not correct during requirements engineering? |
| A. | Requirements are difficult to uncover |
| B. | Requirements are subject to change |
| C. | Requirements should be consistent |
| D. | Requirements are always precisely known. |
| Answer» D. Requirements are always precisely known. | |
| 758. |
Which one is not a type of requirements? |
| A. | Known requirements |
| B. | Unknown requirements |
| C. | Undreamt requirements |
| D. | Complex requirements |
| Answer» D. Complex requirements | |
| 759. |
Which one is not a requirements elicitation technique? |
| A. | Interviews |
| B. | The use case approach |
| C. | FAST |
| D. | Data flow diagram. |
| Answer» D. Data flow diagram. | |
| 760. |
FAST stands for |
| A. | Functional Application Specification Technique |
| B. | Fast Application Specification Technique |
| C. | Facilitated Application Specification Technique |
| D. | None of the above |
| Answer» C. Facilitated Application Specification Technique | |
| 761. |
QFD in requirement engineering stands for |
| A. | Quality function design |
| B. | Quality factor design |
| C. | Quality function development |
| D. | Quality function deployment |
| Answer» D. Quality function deployment | |
| 762. |
Which is not a type of requirements under quality function deployment? |
| A. | Normal requirements |
| B. | Abnormal requirements |
| C. | Expected requirements |
| D. | Exciting requirements |
| Answer» B. Abnormal requirements | |
| 763. |
Use case approach was developed by |
| A. | I. Jacobson and others |
| B. | J.D. Musa and others |
| C. | B. Little wood |
| D. | None of the above |
| Answer» A. I. Jacobson and others | |
| 764. |
Context diagram explains |
| A. | The overview of the system |
| B. | The internal view of the system |
| C. | The entities of the system |
| D. | None of the above |
| Answer» A. The overview of the system | |
| 765. |
DFD stands for |
| A. | Data Flow design |
| B. | Descriptive functional design |
| C. | Data flow diagram |
| D. | None of the above |
| Answer» C. Data flow diagram | |
| 766. |
ERD stands for |
| A. | Entity relationship diagram |
| B. | Exit related diagram |
| C. | Entity relationship design |
| D. | Exit related design |
| Answer» A. Entity relationship diagram | |
| 767. |
Which is not a characteristic of a good SRS? |
| A. | Correct |
| B. | Complete |
| C. | Consistent |
| D. | Brief |
| Answer» D. Brief | |
| 768. |
Outcome of requirements specification phase is |
| A. | Design Document |
| B. | SRS Document |
| C. | Test Document |
| D. | None of the above |
| Answer» B. SRS Document | |
| 769. |
The basic concepts of ER model are: |
| A. | Entity and relationship |
| B. | Relationships and keys |
| C. | Entity, effects and relationship |
| D. | Entity, relationship and attribute |
| Answer» D. Entity, relationship and attribute | |
| 770. |
The DFD depicts |
| A. | Flow of data |
| B. | Flow of control |
| C. | Both (a) & (b) |
| D. | None of the above |
| Answer» A. Flow of data | |
| 771. |
Product features are related to: |
| A. | Functional requirements |
| B. | Non functional requirements |
| C. | Interface requirement |
| D. | None of the above |
| Answer» A. Functional requirements | |
| 772. |
Which one is a quality attribute? |
| A. | Reliability |
| B. | Availability |
| C. | Security |
| D. | All of the above |
| Answer» D. All of the above | |
| 773. |
IEEE standard for SRS is: |
| A. | IEEE Standard 837-1998 |
| B. | IEEE Standard 830-1998 |
| C. | IEEE Standard 832-1998 |
| D. | IEEE Standard 839-1998 |
| Answer» B. IEEE Standard 830-1998 | |
| 774. |
Which one is not a functional requirement? |
| A. | Efficiency |
| B. | Reliability |
| C. | Product features |
| D. | Stability |
| Answer» C. Product features | |
| 775. |
APIs stand for: |
| A. | Application performance interfaces |
| B. | Application programming interfaces |
| C. | Application programming integration |
| D. | Application performance integration |
| Answer» B. Application programming interfaces | |
| 776. |
After the finalization of SRS, we may like to estimate |
| A. | Size |
| B. | Cost |
| C. | Development time |
| D. | All of the above. |
| Answer» D. All of the above. | |
| 777. |
Which one is not a size measure for software |
| A. | LOC |
| B. | Function Count |
| C. | Cyclomatic Complexity |
| D. | Halstead’s program length |
| Answer» C. Cyclomatic Complexity | |
| 778. |
Function count method was developed by |
| A. | B.Beizer |
| B. | B.Boehm |
| C. | M.halstead |
| D. | Alan Albrecht |
| Answer» D. Alan Albrecht | |
| 779. |
Function point analysis (FPA) method decomposes the system into functional units. The total numbers of functional units are |
| A. | 2 |
| B. | 5 |
| C. | 4 |
| D. | 1 |
| Answer» B. 5 | |
| 780. |
COCOMO was developed initially by |
| A. | B.W.Bohem |
| B. | Gregg Rothermal |
| C. | B.Beizer |
| D. | Rajiv Gupta |
| Answer» A. B.W.Bohem | |
| 781. |
A COCOMO model is |
| A. | Common Cost estimation model |
| B. | Constructive cost Estimation model |
| C. | Complete cost estimation model |
| D. | Comprehensive Cost estimation model |
| Answer» B. Constructive cost Estimation model | |
| 782. |
Estimation of software development effort for organic software is COCOMO is |
| A. | E=2.4(KLOC)1.05PM |
| B. | E=3.4(KLOC)1.06PM |
| C. | E=2.0(KLOC)1.05PM |
| D. | E-2.4(KLOC)1.07PM |
| Answer» A. E=2.4(KLOC)1.05PM | |
| 783. |
Estimation of size for a project is dependent on |
| A. | Cost |
| B. | Schedule |
| C. | Time |
| D. | None of the above |
| Answer» D. None of the above | |
| 784. |
In function point analysis, number of Complexity adjustment factor is |
| A. | 10 |
| B. | 20 |
| C. | 14 |
| D. | 12 |
| Answer» C. 14 | |
| 785. |
COCOMO-II estimation model is based on |
| A. | Complex approach |
| B. | Algorithm approach |
| C. | Bottom up approach |
| D. | Top down approach |
| Answer» B. Algorithm approach | |
| 786. |
Cost estimation for a project may include |
| A. | Software Cost |
| B. | Hardware Cost |
| C. | Personnel Costs |
| D. | All of the above |
| Answer» D. All of the above | |
| 787. |
In COCOMO model, if project size is typically 2-50 KLOC, then which mode is to be selected? |
| A. | Organic |
| B. | Semidetached |
| C. | Embedded |
| D. | None of the above |
| Answer» A. Organic | |
| 788. |
COCOMO-II was developed at |
| A. | University of Maryland |
| B. | University of Southern California |
| C. | IBM |
| D. | AT & T Bell labs |
| Answer» B. University of Southern California | |
| 789. |
Which one is not a Category of COCOMO-II? |
| A. | End User Programming |
| B. | Infrastructure Sector |
| C. | Requirement Sector |
| D. | System Integration |
| Answer» C. Requirement Sector | |
| 790. |
Which one is not infrastructure software? |
| A. | Operating system |
| B. | Database management system |
| C. | Compilers |
| D. | Result management system |
| Answer» D. Result management system | |
| 791. |
How many stages are in COCOMO-II? |
| A. | 2 |
| B. | 3 |
| C. | 4 |
| D. | 5 |
| Answer» B. 3 | |
| 792. |
Which one is not a stage of COCOMO-II? |
| A. | Application Composition estimation model |
| B. | Early design estimation model |
| C. | Post architecture estimation model |
| D. | Comprehensive cost estimation model |
| Answer» D. Comprehensive cost estimation model | |
| 793. |
The most desirable form of coupling is |
| A. | Control |
| B. | Data |
| C. | Common |
| D. | Content |
| Answer» B. Data | |
| 794. |
The worst type of coupling is |
| A. | Content |
| B. | Common |
| C. | External |
| D. | Data coupling |
| Answer» A. Content | |
| 795. |
The most desirable form of cohesion is |
| A. | Logical cohesion |
| B. | Procedural cohesion |
| C. | Functional cohesion |
| D. | Temporal cohesion |
| Answer» C. Functional cohesion | |
| 796. |
The worst type of cohesion is |
| A. | Temporal cohesion |
| B. | Coincidental cohesion |
| C. | Logical cohesion |
| D. | Sequential cohesion |
| Answer» B. Coincidental cohesion | |
| 797. |
Which one is not a strategy for design? |
| A. | Bottom up design |
| B. | Top down design |
| C. | Embedded design |
| D. | Hybrid design |
| Answer» C. Embedded design | |
| 798. |
Software testing is: |
| A. | The process of demonstrating that errors are not present |
| B. | The process of establishing confidence that a program does what it is supposed to do |
| C. | The process of executing a program to show it is working as per specifications |
| D. | The process of executing a program with the intent of finding errors |
| Answer» D. The process of executing a program with the intent of finding errors | |
| 799. |
Software mistakes during coding are known as: |
| A. | failures |
| B. | defects |
| C. | bugs |
| D. | errors |
| Answer» C. bugs | |
| 800. |
Functional testing is known as: |
| A. | Structural testing |
| B. | Behavior testing |
| C. | Regression testing |
| D. | None of the above |
| Answer» B. Behavior testing | |
Done Studing? Take A Test.
Great job completing your study session! Now it's time to put your knowledge to the test. Challenge yourself, see how much you've learned, and identify areas for improvement. Don’t worry, this is all part of the journey to mastery. Ready for the next step? Take a quiz to solidify what you've just studied.