Trac Nghiem CNPM

7/29/2019 Trac Nghiem CNPM

1/28

267840. Subset of program267840. Superset of programs267840. Set of program267840. None of others

267841. Maintainability267841. Dependability267841. Efficiency267841. Always correct

267842. Deliverable267842. User expectation267842. Organizations effort in development267842. None of others

267843. Complex267843. Simple267843. Efficient

267843. Rigorous

267844. The way in which we produce software267844. The way in which we produce good software267844. The way in which we deliver a product to customers267844. None of others

267845. USD267845. Months267845. Persons267845. Person-months

267846. Generic products267846. Customised products267846. Generic and Customised products267846. None of others

267847. Embedded Software267847. Artificial Intelligence software267847. Real Time Software267847. System Software

267848. System Software267848. Real Time Software267848. Personal Computer Software267848. Engineering and Scientific Software

267849. Business Software267849. System Software267849. Embedded Software267849. Web Base Software

267850. People267850. Process267850. Product267850. All of other answers

267851. People267851. Project267851. Product267851. Process

267852. People - Process Product Project267852. People Product Project - Process267852. Project Product Process People267852. People Product Process Project

267853. Subset of software267853. Super set of software267853. Software267853. None of others

267854. Documents267854. Subset of software267854. Super set of software267854. Operating procedures

267855. Know the cost of project267855. Know the status of project267855. Know the user expectation267855. None of others

267856. Set of instructions + operating system267856. Programs + Documentation + Operating Procedures

267856. Programs + Hardware manual267856. Set of program

267857. Better performance of hardware267857. Error free software267857. Reusable software267857. Quality software product

267858. Computer Aided Software Engineering267858. Component Aided Software Engineering267858. Constructive Aided Software Engineering267858. Computer Analysis Software Engineering

267859. Increase probability of success267859. Ensure the success of the project267859. Ensure the good product will be produced267859. All of others

267860. Manage the people in hisher team267860. Motivate, encourage the people in hisher team267860. Guide, control the people in hisher team267860. All of others

267861. Bev Littlewood

267861. Berry Boehm267861. Roger Pressman267861. Victor Basili

267862. Spiral model

1


2/28

267862. Prototype Model267862. Quick and Fix model267862. Waterfall model

267863. Waterfall model267863. Capability maturity model267863. Spiral model267863. Prototyping model

267864. Build and Fix model267864. Iterative Enhancement model267864. Spiral model267864. Boehm Model

267865. Taute Maintenance Model267865. Bug Seeding Model267865. Evolutionary Development Model267865. The Early Design Model

267866. Spiral model

267866. Quick and Fix model267866. Prototyping model267866. Waterfall model

267867. Software Design Life Cycle267867. System Development Life Cycle267867. Software Development Life Cycle267867. System Design Life Cycle

267868. 2 phases267868. 3 phases267868. 4 phases

267868. 1 phases

267869. 1 phases267869. 2 phases267869. 4 phases267869. 5 phases

267870. Design267870. Requirement Analysis and Specification267870. Risk Analysis

267870. Operation & Maintenance

267871. Quick267871. Design267871. Fix267871. None of others

267872. Software Requirements Specification267872. Software Requirements Solution267872. System Requirements Specification267872. None of others

267873. Small project267873. Accommodating change267873. Complex project267873. None of others

267874. Small project267874. Projects that the requirements are well-understoodand changes will be fairly limited during the design process

267874. Complex project267874. None of others

267875. Always Occur in fixed order267875. Can Occur in any order267875. Always Occur in fixed order and not overlap267875. None of others

267876. Prototyping Model267876. Waterfall model267876. Spiral Model267876. Iterative Enhancement Model

267877. Waterfall Model267877. Prototyping Model

267877. Iterative Enhancement Model267877. None of others

267878. Waterfall model267878. Spiral Model267878. Quick and Fix Model267878. Prototyping Model

267879. Waterfall model267879. Prototyping Model

267879. Iterative Enhancement Model267879. Evolutionary Development Model

selected? ?267880. Waterfall Model267880. Prototyping Model267880. Iterative Enhancement Model267880. Evolutionary Development Model

267881. Prototyping Model267881. Iterative Enhancement Model267881. Evolutionary Development Model267881. Any of others

267882. Waterfall Model267882. Spiral Model267882. Iterative Enhancement Model267882. Any of others

267883. Prototyping Model267883. Evolutionary Development Model267883. Waterfall Model267883. Spiral Model

2


3/28

267884. Prototyping Model267884. Iterative Enhancement Model267884. Waterfall Model267884. Spiral Model

267885. Waterfall Model267885. Iterative Enhancement Model267885. Spiral Model267885. Evolutionary Development Model

267886. Iterative Enhancement Model267886. Spiral Model267886. Evolutionary Development Model267886. Prototyping Model

267887. Waterfall Model267887. Iterative Enhancement Model267887. Spiral Model

267887. Evolutionary Development Model

267888. Iterative Enhancement Model267888. Spiral Model267888. Prototyping Model267888. Evolutionary Development Model

267889. Spiral Model267889. Iterative Enhancement Model267889. Evolutionary Development Model267889. Any of others

267890. Spiral Model267890. Waterfall Model267890. Prototyping Model267890. None of others

267891. Quality management267891. Risk management267891. Performance management267891. Efficiency management

267892. Spiral Model267892. Waterfall Model267892. Evolutionary Development Model267892. Iterative Enhancement Model

267893. Spiral Model267893. Prototyping267893. Evolutionary Development Model267893. Iterative Enhancement Model

267894. Prototyping267894. Evolutionary Development Model267894. Waterfall model267894. Iterative Enhancement Model

267895. Coding267895. Testing267895. Abstraction267895. Maintenance

267896. The process of demonstrating that errors are notpresent267896. The process of establishing confidence that a programdoes what it is suppose to do267896. To show that a program performs its intendedfunctions correctly267896. The process of executing a program with the intent offinding errors

267897. A program always has one path267897. It is not possible to test the software for all possiblecombination of input cases267897. It is impossible to execute all path the program267897. Complete Testing is impossible, although we maywish to do so

267898. By perform software testing activities we alwaysproduce a software without errors267898. Complete Testing is impossible, although we maywish to do so

267898. It is not possible to test the software for all possiblecombination of input cases267898. It is impossible to execute all path the program

267899. Every body can perform software testing activities267899. Developers are easy to find out errors in product thatthey created267899. Most of the times, testing persons are different fromdevelopment persons for overall benefit of the system.267899. None of others

267900. Failures267900. Bugs267900. Defects267900. Errors

267901. Fault267901. Bug267901. Failure267901. Mistake

267902. Two failures267902. One failure267902. Many failures267902. All of others

3


4/28

267903. One or more failures267903. One or more Errors267903. One or more mistakes267903. None of others

267904. Defect267904. Error267904. Mistake267904. Failure

267905. One or more faults267905. One or more mistakes267905. One or more failures267905. All of other

267906. Structural testing267906. Regression testing267906. Behavior testing267906. None of others

267907. White box testing267907. Structural testing267907. Regression testing267907. Black box testing

267908. 4n + 1 test cases267908. 4n + 3 test cases267908. 4n - 1 test cases267908. None of others

267909. 9267909. 13267909. 25267909. 42

267910. 6n + 1267910. 4n + 1267910. 4n + 3267910. None of others

267911. 9267911. 12267911. 8267911. 21

267912. Functional testing267912. Development testing267912. Data flow testing267912. Maintenance testing

267913. Source node267913. Destination node267913. Transfer node267913. None of others

267914. Source node267914. Destination node267914. Predicate node267914. None of others

267915. 4n + 1267915. 6n + 1267915. 5n267915. None of others

267916. 13267916. 14267916. 16267916. 17

267917. 13

267917. 15267917. 17267917. 19

267918. 64267918. 125267918. 216267918. None of others

267919. 5267919. 25

267919. 125267919. 625

267920. Four portions267920. Five portions267920. Three portions267920. Two portions

267921. Structural testing267921. Mutation testing267921. Black box testing267921. All of others

267922. Conditions stub267922. Action stub267922. Condition entries267922. None of others

267923. Conditions stub267923. Action entries267923. Condition entries267923. None of others

267924. Conditions stub267924. Action stub267924. Condition entries267924. Test case ID portion

4


5/28

267925. Action stub267925. Action entries267925. Condition entries267925. None of others

267926. Users267926. Testers267926. Developers267926. All of others

267928. Customers267928. Testers267928. Developers267928. All of others

267929. Customers267929. Testers267929. Developers267929. All of others

267930. Structural Testing267930. Functional testing267930. Development testing267930. Data flow testing

267931. Structural Testing267931. Black box testing267931. Development testing267931. White box testing

267932. Structural Testing267932. Maintenance testing267932. Development testing267932. None of others

267933. Structural Testing267933. Maintenance testing267933. Development testing267933. None of others

267934. Structural testing267934. Functional testing267934. Maintenance testing267934. Regression testing

267935. White box testing267935. Regression testing267935. Maintenance testing267935. Black box testing

267936. Process is checked267936. Developers performance is evaluated267936. The customer checks the product

267936. Product is checked

267937. Checking the software with respect to customersexpectation267937. Checking the software with respect to specification

267937. Checking the software with respect to specificationand Checking the software with respect to customersexpectation267937. None of others

267938. Checking the software with respect to customersexpectation267938. Checking the software with respect to specification

267938. Checking the software with respect to specificationand Checking the software with respect to customersexpectation267938. None of others

267939. The process of conforming that software meets itsspecification267939. The process of conforming that software meets thecustomers requirements267939. Checking the product with respect to constrains of theproject267939. All of others

267940. Customer267940. Developer267940. Tester267940. All of others

267941. The software developed as a product for anonymouscustomers267941. The software is developed for a specific customer267941. The software is developed as an operating system267941. None of others

267942. Software company

267942. Any where267942. Installation place267942. None of others

267943. Software company267943. Any where267943. Installation place267943. None of others

267944. Users site267944. Any where267944. Installation place267944. None of others

267945. Users site267945. Any where267945. Installation place267945. None of others

267946. Developers267946. Testers267946. Customers267946. All of others

267947. Developers267947. Testers267947. Designers267947. None of others

5


6/28

267948. The software is developed for a specific customer

267948. The software developed as a product for anonymouscustomers267948. We want to test the functionality of the program267948. None of others

267949. Functionality of the program267949. Structure of the program267949. Analysis the code267949. All of others

267950. Observation of the output for certain input values

267950. Analysis the code267950. Analysis the structure of program267950. All of others

267951. One or more failures

267951. Two failures267951. Three failures267951. None of others

267952. Set of test cases267952. Set of outputs267952. Set of inputs267952. All of others

267953. Set of test suite267953. Set of outputs267953. Set of inputs

267953. None of others

267954. A test case267954. Set of outputs267954. Set of inputs267954. None of others

267955. Describes an input description and an expectedoutput description267955. Set of outputs267955. Set of inputs267955. None of others

267956. Modeling267956. Validation267956. Verification267956. None of others

267957. Unit testing267957. Integration testing267957. Acceptance testing267957. Bottom up testing

267958. Boundary value analysis267958. Regression testing267958. Decision table based testing267958. None of others

267959. Boundary value analysis267959. Data flow testing267959. Decision table based testing267959. None of others

267960. Path testing267960. Data flow testing267960. Decision table based testing267960. None of others

267961. Regression testing267961. Data flow testing267961. Robustness testing267961. None of others

267962. Boundary value analysis267962. Decision table based testing267962. Equivalence class testing267962. All of others

267963. An action is taken under varying sets of conditions267963. Number of combinations of actions are taken undervarying sets of conditions267963. No action is taken under varying sets of conditions267963. None of others

267964. They do not explore combinations of inputcircumstances267964. They are not effective267964. They explore combinations of input circumstances


267965. Input and Output267965. Destination and source267965. Output and input267965. None of others

267966. Data flow testing267966. Boundary value analysis267966. Cause effect graphing267966. None of others

267967. Cause effect graphing267967. Path testing267967. All of others267967. Equivalence class testing

267968. Path testing267968. Data flow testing267968. Equivalence class testing267968. None of others

267969. Design to design path graph267969. Destination to destination path graph267969. Defect to defect path graph267969. Decision to decision path graph

6


7/28

267970. Any path through the DD path graph that introducesat least one new set of processing statements or conditions

267970. Any path through the DD path graph that introducesat most one new set of processing statements or conditions267970. Any path through the DD path graph that introducesone and only one new set of processing statements orconditions267970. None of others

267971. B.W.Boehm267971. B.W.Littlewood267971. T.J.McCabe267971. Victor Basili

267972. V(G)=e-n+2P267972. V(G)=2n + 1267972. V(G)=5n+1267972. None of others

267973. V(G)=e-n+4P267973. V(G)=n+ 2e + P267973. V(G)=5n+e267973. V(G)=Number of regions of the graph G

267974. V(G)=P +1267974. V(G)=2n + 1267974. V(G)=5n+1267974. All of others

267975. V(G)=P +1267975. V(G)=Number of regions of the graph G

267975. V(G)=e-n+2P267975. All of others

267976. Number of Connected components in the graph G

267976. Number of vertices in the graph G267976. Number of edges in the graph G267976. None of others

267977. Number of Connected components in the graph G267977. Number of edges in the graph G267977. Number of vertices in the graph G267977. None of others

267978. Number of nodes in the graph G267978. Number of Connected components in the graph G267978. Number of predicate nodes in the graph G267978. None of others

267979. 3267979. 0267979. 6267979. None of others

267980. 5267980. 1267980. 7267980. None of others

267981. 5267981. 6267981. 7267981. 8

267982. 4267982. 5267982. 6267982. None of others

267983. Two outgoing edges267983. No outgoing edges267983. Three or more outgoing edges


267984. Number of independent paths267984. Number of edges267984. Number of paths267984. None of others

267985. Data flow diagrams267985. Data dictionaries267985. None of others267985. E-R diagrams

267986. All dc-paths that are not du-path267986. All du-paths that are not dc-path267986. All du-paths267986. All dc-paths

267987. Fault checking267987. Fault seeding267987. Functional testing267987. None of others

267988. Drivers267988. Scaffolding267988. Stubs267988. None of others

267989. Core dumps267989. Data flow testing267989. Mutation testing267989. None of others

267990. Structural testing

267990. Fault seeding267990. Traces267990. None of others

267991. Core dumps267991. Traces

7


8/28

267991. Fault seeding267991. None of others

267992. Core dumps267992. Traces267992. Print statements267992. All of others

267993. Functional testing267993. Data flow testing267993. Mutation testing267993. All of others

267994. Defect267994. Fault267994. Error267994. Failure

267995. System testing

267995. Acceptance testing267995. Unit testing267995. Integration testing

267996. Reviews267996. Walkthrough267996. Path testing267996. Acceptance testing

267997. Validation267997. Verification267997. Verification and Validation


267998. Boundary value analysis267998. Top down267998. Unit testing267998. None of others

267999. Sandwich267999. Data flow testing267999. Bottom up267999. None of others

268000. Top down268000. Bottom up268000. Sandwich268000. All of others

268001. White box testing268001. Regression testing268001. Black box testing268001. None of others

268002. White box testing268002. Mutation testing268002. Data flow testing268002. None of others

268003. White box testing268003. Regression testing268003. Mutation testing268003. Black box testing

268004. Development268004. Validation268004. Identification of faults268004. Functional testing

268005. Real time systems268005. Event driven systems268005. Object oriented systems268005. All of others

268006. Alpha testing268006. Beta testing268006. Regression testing


268007. Inverse Engineering268007. Reverse engineering268007. Software engineering268007. Re-engineering

268008. Functional testing268008. Development testing268008. Data flow testing268008. Maintenance testing

268009. Corrective maintenance268009. Adaptive maintenance268009. Effective maintenance268009. Perfective maintenance

268010. Corrective maintenance268010. Perfective maintenance268010. Adaptive maintenance268010. Preventive maintenance

268011. Patch is know as ?268011. Emergency fixes268011. Critical fixes268011. Routine fixes268011. None of others

268012. Modification in software due to demand of newfunctionalities268012. Modification in software due to failures268012. Modification in software due to increase in complexity

268012. Modification in software to match changes in theever-changing environment

268013. Making the product better268013. Making the product faster and smaller

8


9/28

268013. Making the product with new functionality268013. All of others

268014. Adaptive268014. Perfective268014. Corrective268014. Preventive

268015. Adaptive268015. Perfective268015. Corrective268015. Preventive

268016. CMM268016. Quick-fix model268016. Iterative enhancement model268016. Reuse-oriented model

268017. Taute maintenance model268017. Reuse oriented model268017. Quick-fix model268017. None of others

268018. Three stage model268018. Four stage model268018. Two stage model268018. Seven stage model

268019. Two phases

268019. Six phases268019. Eight phases268019. Ten phases

268020. Actual change time268020. Actual change traffic268020. Annual change traffic268020. None of others

268021. The process of retesting the modified parts of thesoftware268021. The process of testing the design documents268021. The process of reviewing SRS268021. None of others

268022. Increase confidence in the correctness of the modifiedprogram268022. Locate errors in modified program268022. Preserve the quality and reliability of the software268022. All of others

268023. Maintenance of software268023. Development of software

268023. Maintenance of software and Development ofsoftware268023. None of others

268024. Coverage technique268024. Safe technique

268024. Minimization technique268024. Maximization technique

268025. Recover information from existing code or any otherintermediate document

268025. Redocumentation andor document generation268025. Understand the source code and associateddocuments268025. All of others

268026. Old systems268026. Undeveloped systems268026. New system268026. None of others

268027. System overview268027. Reference guide268027. Installation guide268027. All of others

268028. Beginners guide268028. SRS268028. Installation guide268028. System administration

268029. SRS268029. Acceptance test plan268029. System administration268029. Design document

268030. Reverse engineering

268030. Software configuration management268030. Business process re-engineering268030. Technical feasibility

268031. Reverse engineering268031. Re-engineering268031. Restructuring268031. Forward engineering

268032. Requirement elicitation268032. Requirement design268032. Requirement analysis268032. Requirement documentation

268033. Gathering of requirements268033. Understanding of requirements268033. Capturing of requirements268033. All of others

268034. Software requirements specification268034. Systematic requirements specifications

268034. System requirements specification268034. None of others

268035. Costing and scheduling of a system268035. What of the system?268035. How to design the system?

9


10/28

268035. Systems requirement

268036. Spend time in requirements gathering268036. Document the requirements268036. Improve the quality of SRS268036. None of others

268037. Requirements are difficult to uncover268037. Requirements are subject to change268037. Requirements should be consistent268037. Requirements are always precisely know

268038. Know requirements268038. Undreamt requirements268038. Complex requirements268038. Unknown requirements

268039. Interview

268039. FAST268039. The use case approach268039. Data flow diagram

268040. Functional Application Specification Technique268040. Fast Application Specification Technique268040. Facilitated Application Specification Technique268040. None of others

268041. Quality function design268041. Quality function development

268041. Quality factor design268041. Quality function deployment

268042. Normal requirements268042. Expected requirements268042. Abnormal requirements268042. Exciting requirements

268043. I. Jacobson and others268043. B. Littlewood268043. J.D. Musa and others268043. None of others

268044. The overview of the system268044. The entities of the system268044. The internal view of the system268044. None of others

268045. Data flow design268045. Data flow diagram,268045. Descriptive function design268045. None of others

268046. Use case diagram268046. System diagram268046. None of others268046. Context diagram

268047. Entity relationship diagram268047. Entity relationship design268047. Exit related diagram268047. Exit related design

268048. Correct268048. Consistent268048. Complete268048. Brief

268049. Design document268049. Test document268049. Software requirements specification268049. None of others

268050. Entity and relationship268050. Entity Effect and relationship268050. Relationship and keys268050. Entity, relationship and attribute

268051. Flow of data268051. Flow of control268051. Flow of data and Flow of control268051. None of others

268052. Size268052. Development time268052. Cost268052. All of others

268053. LOC268053. Cyclomatic Complexity268053. Function count268053. Halsteads program length

268054. Beizer268054. M.Halstead268054. B.Boehm268054. Alan Albrecht

268055. 2268055. 4268055. 5268055. 1

268056. Initial function point uniform group268056. International function point uniform group268056. International function point user group268056. Initial function point use group

268057. UFP * CAF268057. UFP * Cost268057. UFP * FAC268057. UFP * Productivity

10


11/28

268058. Function points

268058. NordenRayleigh curve 268058. Putnam theory of software management268058. Boehms observation on manpower utilization rate

268059. B.W. Bohem268059. B.Beizer268059. Gregg Rothermal268059. Rajiv Gupta

268060. Common cost estimation model268060. Constructive cost Estimation model268060. Complete cost Estimation model268060. Comprehensive cost Estimation model

268061. E= 2.4(KLOC))1.05PM268061. E= 2.0(KLOC))1.05PM268061. E= 3.4(KLOC))1.06PM268061. E= 2.4(KLOC))1.07PM

268062. Cost268062. Time268062. Schedule268062. None of others

268063. 10268063. 14268063. 20268063. 12

268064. Complex approach268064. Bottom up approach268064. Algorithmic approach268064. Top down approach

268065. Software cost268065. Personal cost268065. Hardware cost268065. All of others

268066. Organic268066. Embedded268066. Semidetached268066. None of others

268067. University of Maryland268067. IBM268067. University of Southern California

268067. AT&T Bell labs

268068. End user programming268068. Requirement sector268068. Infrastructure sector268068. System integration

268069. Operating System

268069. Compilers268069. Database management system268069. Result management system

268070. 2268070. 4268070. 3268070. 5

268071. Application Composition estimation model268071. Early design estimation model268071. Post architecture estimation model268071. Comprehensive cost estimation model

268072. 3 Categories268072. 5 Categories268072. 2 Categories268072. 10 Categories

268073. Risk assessment

268073. Risk generation268073. Risk control268073. None of others

268074. Control coupling268074. Common coupling268074. Data coupling268074. Content coupling

268075. External coupling268075. Content coupling268075. Common coupling

268075. Data coupling

268076. Logical cohesion268076. Functional cohesion268076. Procedural cohesion268076. Temporal cohesion

268077. Logical cohesion268077. Temporal cohesion268077. Coincidental cohesion268077. Sequential cohesion

268078. Bottom up design268078. Embedded design268078. Top down design268078. Hybrid design

268079. Cohesion between temporary variables268079. Cohesion with respect to time268079. Cohesion between local variable268079. Coincidental cohesion

268080. Operations are part of single functional task and areplaced in same procedures268080. Operations are part of single functional task and areplaced in multiple procedures268080. Operations are part of multiple tasks268080. None of others

11


12/28

268081. External coupled268081. Content coupled268081. Data coupled268081. Common coupled

268082. Coupling268082. Modularity268082. Cohesion268082. None of others

268083. Closed system268083. Open system268083. Logical system268083. Hierarchical system

268084. Coupling268084. Modularity268084. Cohesion268084. Stability

268085. Product metrics268085. Process metrics268085. Project metrics268085. People metric

268086. M.Halstead

268086. T.J.McCabe268086. B.Littlewood268086. G.Rothermal

268087. Number of bits required to store the program268087. Actual size of the program if a uniform binaryencoding scheme for vocabulary is used268087. Number of bits required to execute the program268087. None of others

268088. Person-Month268088. Elementary mental discriminations268088. Hours268088. None of others

268089. Number of component related to component A268089. Count the number of component that can call or passcontrol, to component A268089. Number of components dependent component A268089. None of others

268090. Number of component related to component A

268090. Number of components dependent component A268090. Number of component that are called by component A


268091. LOC268091. Program length268091. Function count268091. Cyclomatic complexity

268092. Vocabulary268092. Level268092. Logic268092. None of other

268093. 5 to 20268093. 1 to 10268093. 20 to 40268093. 40 to 80

268094. Volume268094. Effective volume

268094. Potential Volume268094. None of others

268095. V=N log2n268095. V=2N log2n

268095. V=(N2) log2n268095. V=N log2n +1

268096. LOC268096. Program length268096. Function count


268097. Burn-in268097. Wear-out268097. Useful life268097. Test-out

268098. The probability of failure free operation of a programfor a specified time in a specified environment268098. The probability of failure of a program for a specifiedtime in a specified environment268098. The probability of failure of a program for a specifiedtime in any environment268098. None of others

268099. Defect in program268099. Error in program268099. Mistake in program268099. All of others

268101. Execution time

268101. Clock time268101. Machine time268101. Calendar time

268102. Time to failure268102. Failures experienced in a time interval

12


13/28

268102. Time interval between failures268102. All of others

268103. 100268103. 1268103. 10268103. 0

268104. Decreases268104. no effect268104. Increases268104. None of others

268105. 0.90268105. 0.95268105. 0.92268105. 0.98

268106. Conformance to requirements268106. Level of satisfaction268106. Fitness for the purpose268106. All of others

268107. Number of defects per million lines of source code268107. Number of defects per function point268107. Number of defects per unit of size of software268107. All of others

268108. 2268108. 11268108. 3268108. 6

268109. Product transition268109. Product revision268109. Product specification268109. Product operation

268110. Quality criteria268110. Quality guidelines268110. Quality factors | 268110. Quality specification

268111. Primary uses268111. Primitive constructs268111. Intermediate construct268111. Final construct

268112. McCall model

268112. ISO9000268112. Boehm model268112. ISO9126

268113. Bev.Littlewood268113. R.Pressman

268113. J.D.Musa268113. Victor Baisili

268114. Non Homogeneous Poisson Process268114. Non Homogeneous Poisson Product268114. Non Heterogeneous Poisson Process268114. Non Heterogeneous Poisson Product

268115. 6 KPAs268115. 0 KPAs268115. 2 KPAs268115. None of others

268116. Mean time between failures268116. Minimum time between failures268116. Maximum time between failures268116. Many time between failures

268117. Improve the software process268117. Test the software

268117. Automatically develop the software268117. All of others

268118. 1268118. 5268118. 3268118. 7

268119. Removed268119. Remaining268119. Removed and Remaining


268120. Analysis phase268120. Coding phase268120. Design phase268120. Testing phase

268121. Capacity maturity model268121. Cost management model268121. Capability maturity model268121. Comprehensive maintenance model

268122. Initial268122. Defined268122. Repeatable268122. Managed

268123. Initial268123. Defined268123. Repeatable268123. Optimizing

268124. Initial268124. Managed268124. Repeatable268124. Optimizing

13


14/28

268125. Harvard University268125. Carnegie Mellon University268125. Cambridge University268125. Maryland University

268126. Quality model268126. Requirement model268126. Process improvement model268126. Design model

268127. ISO9000268127. CMM268127. ISO9126268127. Spiral model

268128. 15268128. 20268128. 25268128. 10

268129. Quality characteristic268129. Quality attributes268129. Quality factors268129. All of others

268130. One attribute268130. Tree attributes268130. Two attributes268130. Four attributes

268131. Maintainability268131. Testability268131. Flexibility268131. None of others

268132. The Jenlinsky-Moranda model268132. Spiral model268132. Basic execution time model268132. None of others

268133. One KPA268133. Several KPAs268133. Equal KPAs268133. No KPA

268134. Key Process Area268134. Key Principal Area268134. Key Product Area268134. Key Performance Area

268135. Errors

268135. Failures268135. Faults268135. Bugs

268136. True

268136. False268136. Cannot say268136. Not fixed

268137. Time268137. Quality268137. Speed268137. None of others

268138. Mean time to failure268138. Minimum time to failure268138. Maximum time to failure268138. None of others

268139. 2 related standards268139. 10 related standards268139. 5 related standards268139. 25 related standards

268140. A good manager can ensure the success of project

268140. A good manager can Increase probability of success268140. A good manager can Ensure the good product will beproduced268140. All of other

268141. Manage the people in hisher team

268141. Motivate, encourage the people in hisher team268141. Generate test cases for testing268141. All of others

268142. Design268142. Quick design268142. Requirement Analysis and Specification


268143. 1 phases268143. 3 phases268143. 4 phases268143. None of other

268144. 6 phases268144. 1 phases268144. 4 phases268144. None of other

268145. Quick Design268145. Requirement268145. Risk Analysis


268146. Design validation and verification268146. Requirement validation

268146. Risk Analysis268146. None of other

268147. Design268147. Requirement

14


15/28

268147. Operation268147. None of other

268148. Design268148. Requirement268148. Operation268148. None of other

268149. The process of demonstrating that errors are notpresent268149. The process of establishing confidence that a programdoes what it is suppose to do268149. To show that a program performs its intendedfunctions correctly268149. None of other

268150. 2n + 1 test cases268150. 2n + 3 test cases268150. 2n - 1 test cases268150. None of others

268151. 4n^2 + 1268151. 4n + 1268151. 4n + 3268151. None of others

268152. Functional testing268152. Development testing268152. Data flow testing268152. None of other

268153. Five portions268153. Three portions268153. Two portions268153. None of other

268154. Structural testing268154. Mutation testing268154. Functional testing268154. All of others

268155. Managers268155. Testers268155. Developers268155. None of others

268156. Managers268156. Testers268156. Developers268156. None of others

268157. Analysis the usage of variable

268157. Analysis the code268157. Analysis the structure of program268157. None of others

268158. an error268158. a fault268158. a failure268158. a defect

268159. v & w are true, x z are false268159. w, x & y are true, v & z are false268159. w & y are true, v, x & z are false268159. all of the above are true

268160. test items268160. test tasks268160. test environment

268160. test specification

268161. all the planned tests have been run268161. time has run out268161. all faults have been fixed correctly268161. it depends on the risks for the system being tested

268162. 1000, 5000, 99999268162. 9999, 50000, 100000268162. 10000, 50000, 9999268162. 9999, 10000, 50000, 99999, 10000

268163. testing quality attributes of the system includingperformance and usability268163. testing to see where the system does not functionproperly268163. testing a system feature using only the softwarerequired for that action268163. testing a system feature using only the softwarerequired for that function

268164. auditing conformance to ISO9001268164. status accounting of configuration items268164. record of changes to documentation over time268164. controlled library access

268165. to specify which modules to combine when and howmany at once

268165. to specify how the software should be divided intomodules268165. to ensure that the integration testing can beperformed by a small team268165. to ensure that all of the small modules are testedadequately

15


16/28

268166. to plan when to stop testing268166. to know when test planning is complete268166. to set the criteria used in generating test inputs268166. to ensure that the test case specification is complete

268167. 1 test for statement coverage, 2 for branch coverage


268167. 1 test for statement coverage, 1 for branch coverage268167. 2 tests for statement coverage, 2 for branch coverage


268168. 1 test for statement coverage, 1 for branch coverage268168. 2 tests for statement coverage, 2 for branch coverage268168. 2 tests for statement coverage, 3 for branch coverage

268169. 2 tests for statement coverage, 2 for branch coverage

268169. 1 test for statement coverage, 3 for branch coverage268169. 3 tests for statement coverage, 3 for branch coverage268169. 3 tests for statement coverage, 2 for branch coverage

268170. Analyse your needs and requirements268170. Search the internet268170. Attend a tool exhibition268170. Find out what your budget would be for the tool

268171. Everyone who may eventually have some use for the

tool268171. The vendor contractor to write the initial scripts268171. The managers to see what projects it should be usedin268171. A small team to establish the best way to use the tool

268172. Whether the value stored in a variable is correct

268172. The re-definition of a variable before it has been used268172. The use of a variable before it has been defined268172. Unreachable (dead) code

268173. LCSAJ268173. Equivalence partitioning268173. Syntax testing268173. State transition testing

268174. Performed by customers at their own site268174. Performed by customers at their software developerssite268174. Useful to test bespoke software268174. Performed as early as possible in the lifecycle

268175. developers would typically use i and iv; test team ii,iii, v and vi268175. developers would typically use i, ii, iii and iv; test

team v and vi268175. developers would typically use i, iii, iv and v; testteam ii and vi268175. developers would typically use i, iv and vi; test teamii, iii and v

268176. testing for a business perspective268176. testing by an independent test team268176. ensuring that the system is acceptable to all users268176. testing the system with other systems

268177. black box design techniques all have an associatedmeasurement technique268177. cyclomatic complexity is not a test measurementtechnique268177. white box measurement techniques all have anassociated test design technique268177. black box measurement techniques all have anassociated test design technique

268178. inspection is appropriate even when there are nowritten documents268178. inspection compares documents with predecessor

(source) documents268178. managers can perform inspections on managementdocuments268178. inspections should be led by a trained leader

16


17/28

268179. generating expected outputs268179. comparison of expected outcomes with actualoutcomes268179. reading test values from a data file268179. replaying inputs according to a programmed script

268180. re-testing is running a test again; regression testinglooks for unexpected side effects268180. re-testing is done after faults are fixed; regressiontesting is done earlier268180. re-testing is done by developers, regression testing isdone by independent testers268180. re-testing uses different environments, regressiontesting uses the same environment

268181. most useful when specified in advance268181. only important in system testing268181. only used in component testing268181. derived from the code

268182. re-allocate resource to meet original plans268182. report on deviations from the project plan268182. raise incidents on faults that they have found268182. provide information for risk analysis and qualityimprovement

268183. code reviews268183. code inspections268183. a test management tool268183. a static analysis tool

268184. a configuration management tool268184. a debugging tool268184. a dynamic analysis tool268184. a test management tool

268185. the actual and expected outcomes268185. how to fix the fault268185. test environment details268185. how to reproduce the fault

268186. top-down integration testing268186. business process-based testing268186. performance, load and stress testing268186. requirements-based testing

268187. expected outcomes are defined by the softwaresbehaviour268187. expected outcomes are derived from a specification,not from the code268187. expected outcomes include outputs to a screen and

changes to files and databases268187. expected outcomes may include timing constraintssuch as response times

268188. BS7925-1

268188. ANSI/IEEE 829268188. ISO/IEC 12207268188. BS7925-2

268189. Increases as we move the product towards live use

268189. Decreases as we move the product towards live use268189. Is more expensive if found in requirements thanfunctional design268189. Is not important

268190. Quality plans268190. Test items (i.e. software versions)268190. Schedules and deadlines268190. What is not to be tested

268191. Yes, because both help detect faults and improvequality

268191. No, because they do not apply to the testdocumentation268191. Yes, because testing includes all non-constructiveactivities268191. No, because they are normally applied before testing

268192. Recovery testing268192. Generating many transactions268192. Measuring response time268192. Simulating many users

268193. Why does computer hardware cost so much?268193. Why does software take a long time to finish?268193. Why does it cost so much to develop a piece ofsoftware?268193. Why can't software errors be removed from productsprior to delivery?

268194. Multiple change requests introduce errors incomponent interactions268194. Software spare parts become harder to order268194. Software suffers from exposure to hostileenvironments268194. Defects are more likely to arise after software hasbeen used often

268195. Off-the-shelf software components are unavailable inmany application domains.268195. Component reuse is common in the software world.268195. Reusable components are too expensive to use.268195. Software is easier to build without using someoneelse's components.

268196. both b and c268196. complexity268196. content268196. determinacy

17


18/28

268197. Manufacturing268197. Process268197. Methods268197. Tools

268198. communication, planning, modeling, construction,deployment268198. communication, risk management, measurement,production, reviewing268198. analysis, designing, programming, debugging,maintenance268198. analysis, planning, designing, programming, testing

268199. eliminate the need for cumbersome documentation268199. emphasize maneuverability and adaptability268199. do not waste development time on planning activities268199. make extensive use of prototype creation

268200. Performed268200. Optimized268200. both a and b268200. Reused

268201. ISO 19002268201. ISO 9001268201. SPICE268201. both b and c

268202. Practitioner requires careful supervision by the projectmanager268202. Emphasizes personal measurement of work product268202. Individual practitioner is responsible for estimatingand scheduling268202. Practitioner is empowered to control quality ofsoftware work products

268203. Accelerate software process improvement268203. Allow better time management by highly trainedprofessionals268203. Build self-directed software teams268203. both b and c

268204. A reasonable approach when requirements are welldefined.268204. A good approach when a working program is requiredquickly.268204. The best approach to use for projects with largedevelopment teams.

268204. An old fashioned model that cannot be used in amodern context.

268205. Classical life cycle model268205. Waterfall model

268205. Spiral model268205. both a and b

268206. A good approach when a working core product isrequired quickly268206. A reasonable approach when requirements are welldefined268206. The best approach to use for projects with largedevelopment teams268206. A revolutionary model that is not used for commercialproducts

268207. A high speed adaptation of the linear sequentialmodel.268207. Another name for component-based development.268207. A useful approach when a customer cannot definerequirements clearly.268207. All of the above.

268208. All of the above

268208. Are iterative in nature268208. Can easily accommodate product requirementschanges268208. Do not generally produce throwaway systems

268209. A useful approach when a customer cannot definerequirements clearly268209. A reasonable approach when requirements are welldefined268209. The best approach to use for projects with largedevelopment teams.268209. A risky model that rarely produces a meaningful

product

268210. Includes project risks evaluation during each iteration

268210. Ends with the delivery of the software product268210. Is more chaotic than the incremental model268210. All of the above

268211. Often used for the development of client/serverapplications.268211. Another name for the rapid application developmentmodel268211. Only used for development of parallel or distributedsystems268211. Used whenever a large number of change requestsare anticipated

268212. Works best when object technologies are available forsupport.268212. Not able to support the development of reusablecomponents.268212. Only appropriate for computer hardware design.268212. Not cost effective by known quantifiable software

metrics.

268213. All of the above268213. Define the specification for computer-based systems268213. Develop defect free computer-based systems

18


19/28

268213. Verify the correctness of computer-based systems

268214. Validation phase268214. Inception phase268214. Elaboration phase268214. Construction phase

268215. Eliminate the use of project planning and testing

268215. Only essential work products are produced268215. Process allows team to streamline tasks268215. Uses incremental product delivery strategy

268216. Software increments must be delivered in short timeperiods268216. Risk analysis must be conducted before planningtakes place

268216. Software processes must adapt to changesincrementally268216. both a and c

268217. All of the above268217. Competence268217. Decision-making ability268217. Mutual trust and respect

268218. planning, design, coding, testing

268218. analysis, design, coding, testing268218. planning, analysis, design, coding268218. planning, analysis, coding, testing

268219. speculation, collaboration, learning268219. analysis, design, coding268219. feasibility study, functional model iteration,implementation268219. requirements gathering, adaptive cycle planning,iterative development

268220. What is the cause of the problems you areencountering?268220. What obstacles are you encountering?268220. What do you plan to accomplish at the next teammeeting?268220. What did you do since the last meeting?

268221. Analysis268221. Coding268221. Design268221. both a and c

268222. Pareto principle (20% of any product requires 80% ofthe effort)268222. All design should be as simple as possible, but nosimpler268222. A software system exists only to provide value to itsusers268222. Remember that you produce others will consume

268223. reduce the granularity of the plan268223. analyze requirements in depth268223. get all team members to "sign up" to the plan268223. begin design

268224. Define useful software features and functionsdelivered to end-users268224. Determine a schedule used to deliver each softwareincrement268224. Provide a substitute to performing detailed schedulingof activities

268224. Used to estimate the effort required build the currentincrement

268225. Develop overall project strategy268225. Identify the functionality to deliver in each softwareincrement268225. Create a detailed schedule for the complete softwareproject268225. Devise a means of tracking progress on a regularbasis

268226. architecture, interface, component268226. cost, risk, schedule268226. information, function, behavior268226. None of the above

268227. Create unit tests before you begin coding268227. Create a visual layout that aids understanding268227. Keep variable names short so that code is compact

268227. Write self-documenting code, not programdocumentation

268228. Build a software component268228. Unit test the component268228. Create a user interface268228. both a and b

268229. Allows developers to make changes to the deliveredincrement268229. Delivery schedule can be revised to reflect changes268229. Developers can identify changes to incorporate intonext increment268229. All of the above

19


20/28

268230. documentation268230. software268230. people, hardware268230. all of the above

268231. detailed view268231. domain view268231. element view268231. world view

268232. assumptions268232. constraints268232. budget | 268232. both a and b

268233. applications, data, technology infrastructure268233. communications, organization, financial infrastructure268233. network, database, reporting structure268233. systems, requirements, data structure

268234. business system design, construction and integration

268234. business area analysis268234. information strategy planning268234. business area design

268235. data, hardware, software, people268235. data, documentation, hardware, software268235. data, hardware, software, procedures268235. documentation, hardware, people, procedures

268236. AFD268236. DFD268236. SCD268236. SFD

268237. input268237. output268237. user interface268237. all of the above

268238. Activity diagrams268238. Class diagrams268238. Deployment diagrams

268238. All of above

268239. basic problem understanding268239. nature of the solution needed268239. people who want a solution


268240. All of above268240. scope268240. understanding268240. volatility

268241. information268241. functional268241. behavioral268241. all of the above

268242. Function, performance and constraints of a computer-based system268242. implementation of each allocated system268242. element software architecture

268242. time required for system simulation

268243. examine the system model for errors268243. have the customer look over the requirements268243. send them to the design team and see if they haveany concerns268243. use a checklist of questions to examine eachrequirement

268244. debug programs following the detection of run-timeerrors

268244. determine the performance of algorithmimplementations268244. identify, control, and track requirements changes

268244. none of the above

268245. What will be the economic benefit from a goodsolution?268245. Who is against this project?268245. Who will pay for the work?268245. Who will use the solution?

268246. cannot be a member of the software team268246. cannot be a customer268246. controls and facilitates the process268246. must be an outsider

268247. exciting268247. expected

268247. mandatory268247. normal

268248. size of the budget268248. size of the product being built

20


21/28

268248. software process being used268248. stakeholders needs

268249. activity diagram268249. class diagram268249. dataflow diagram268249. state diagram

268250. define set of software requirements that can bevalidated268250. describe customer requirements268250. develop an abbreviated solution for the problem

268250. establish basis for software design

268251. control item268251. diagram268251. data object

268251. both a and c

268252. Behavioral elements268252. Class-based elements268252. Data elements268252. Scenario-based elements

268253. cardinality268253. modality268253. directionality

268253. both a and b

268254. depicts relationships between data objects268254. depicts functions that transform the data flow268254. indicates how data are transformed by the system268254. indicates system reactions to external events

268255. class268255. instance268255. subclass268255. super class

268256. Behavioral elements268256. Class-based elements268256. Flow-based elements268256. Scenario-based elements

268257. depicts functions that transform the data flow268257. indicates how data are transformed by the system268257. indicates system reactions to external events268257. both a and b

268258. needed to model event driven systems268258. useful for modeling real-time systems268258. required for all systems268258. both a and b

268259. events268259. people268259. structures268259. all of the above

268260. computation268260. data manipulation268260. event monitors268260. transformers

268261. class collaborators268261. class name268261. class reliability268261. class responsibilities

268262. its attributes only268262. its collaborators

268262. its operations only268262. both its attributes and operations

268263. actor and the OO system exchange information268263. class operation is invoked268263. messages are passed between objects268263. all of the above

268264. depicts relationships between data objects268264. depicts functions that transform the data flow268264. indicates how data are transformed by the system268264. indicates system reactions to external events

268265. consumer or producer of data.268265. data object hierarchy.268265. observable mode of behavior.268265. well defined process.

268266. architecture268266. data268266. interfaces268266. All of above

268267. accuracy268267. complexity268267. efficiency268267. quality

268268. implements all requirements in the analysis model268268. provides a complete picture of the software

268268. exhibits strong coupling between its modules268268. both a and b

268269. configuration management268269. functional component

21


22/28

268269. notation quality assessment268269. guidelines refinement heuristics

268270. control268270. data268270. procedural268270. All of above

268271. Dynamic models268271. Functional models268271. Structural models268271. All of the above

268272. can be written more compactly.268272. focuses on just one thing.268272. is able to complete its function in a timely manner.268272. is connected to other modules and the outside world.

268273. can be written more compactly.268273. focuses on just one thing.268273. is able to complete its function in a timely manner.268273. is connected to other modules and the outside world.

268274. coupling objects together more tightly.268274. enabling a number of different operations to share thesame name.

268274. making objects more dependent on one another.268274. removing the barriers imposed by encapsulation.

268275. Business domain classes268275. Entity classes268275. Process classes268275. User interface classes

268276. Architectural design elements268276. Component-level design elements268276. Data design elements268276. Interface design elements

268277. Architectural design268277. Component-level design268277. Data design268277. Interface design



268280. software developers do not need to do any testing268280. a test team will test the software more thoroughly

268280. testers do not get involved with the project untiltesting begins268280. arguments between developers and testers arereduced

268282. conduct formal technical reviews prior to testing268282. specify requirements in a quantifiable manner268282. wait till code is written prior to writing the test plan |268282. both a and b

268283. error handling268283. execution paths268283. algorithmic performance268283. both a and b

268284. major decision points are tested early268284. no stubs need to be written268284. no drivers need to be written268284. both a and c

268285. major decision points are tested early268285. no drivers need to be written268285. no stubs need to be written268285. regression testing is not required

268286. control logic is invoked268286. data flow paths are established268286. drivers require testing268286. both a and b

268287. bulletproofing shrink-wrapped software268287. rolling integration testing268287. testing that hides implementation errors268287. unit testing for small programs

268288. groups of classes that collaborate or communicate insome way268288. single operations as they are added to the evolvingclass implementation

268288. operator programs derived from use-case scenarios268288. none of the above

268289. developer268289. end users

22


23/28

268289. test team268289. systems engineers

268290. observability268290. simplicity268290. stability268290. all of the above

268291. black-box testing268291. glass-box testing268291. grey-box testing268291. white-box testing

268292. behavioral testing268292. black-box testing268292. grey-box testing

268292. white-box testing

268293. logic errors268293. performance errors268293. typographical errors268293. both a and c

268294. cycles in the program268294. errors in the program268294. independent logic paths in the program

268294. statements in the program

268295. rely on basis path testing268295. exercise the logical conditions in a program module

268295. select test paths based on the locations and uses ofvariables268295. focus on testing the validity of loop constructs

268296. rely on basis path testing268296. exercise the logical conditions in a program module268296. select test paths based on the locations and uses ofvariables268296. focus on testing the validity of loop constructs

268297. rely basis path testing268297. exercise the logical conditions in a program module268297. select test paths based on the locations and uses of

variables268297. focus on testing the validity of loop constructs

268298. incorrect or missing functions268298. interface errors

268298. performance errors268298. all of the above

268299. conventional software testing268299. operations and classes that are critical or suspect

268299. use-case validation268299. white-box testing of operator algorithms

268300. encapsulation268300. inheritance268300. polymorphism268300. both b and c

268301. concentrates on actor and software interaction268301. misses errors in specifications268301. misses errors in subsystem interactions268301. both a and b

268302. examine object behaviors268302. exercise communication mechanisms268302. exercise object dependencies268302. exercise structure observable by the user

268303. attribute-based partitioning268303. category-based partitioning268303. equivalence class partitioning268303. state-based partitioning

268304. data flow diagram268304. object-relation diagram268304. state diagram268304. use-case diagram

268306. people, performance, payoff, product268306. people, product, performance, process268306. people, product, process, project268306. people, process, payoff, product

268307. determine the budget.268307. select a team organizational model.268307. determine the project constraints.268307. establish the objectives and scope.

268308. milestones268308. work products268308. QA points268308. All of the above

268309. customers268309. end-users268309. project managers268309. sales people

23


24/28

268310. closed paradigm268310. open paradigm268310. random paradigm268310. synchronous paradigm

268311. degree of communication desired268311. predicted size of the resulting program268311. rigidity of the delivery date268311. All of above

268312. give team members more control over process andtechnical decisions.268312. give team members less control over process andtechnical decisions.268312. hide bad news from the project team members untilthings improve.268312. reward programmers based on their productivity.

268313. interoperability268313. performance268313. scale268313. uncertainty

268314. context, lines of code, function268314. context, function, communication requirements268314. information objectives, function, performance268314. communications requirements, performance,information objectives

268315. software process model268315. functionality to be delivered268315. process used to deliver functionality268315. both b and c

268316. when the project is extremely small in size268316. any time the software is mission critical268316. rapid prototyping does not require their use268316. neverthe activities should always occur

268317. double the project team size268317. start on the right foot268317. track progress268317. both b and c

268318. defect tracking against quality targets268318. empirical cost estimation268318. formal risk management


268319. Improve our methods of communication268319. Make the process quite rigid268319. Use only agile process models268319. All of the above.

268320. Linear sequential models268320. Spiral models268320. Agile, incremental models268320. Formal models

268321. Raw data that has special meaning268321. Information that has business meaning268321. Unrelated pieces of information268321. Data or information from different contexts that canbe associated with one another

268322. developing one technology leads to the developmentof even more advanced technologies

268322. a market must be pushed to recognize the need for agiven technology268322. developed must be pushed to adopt processes thatallows them to use the technology268322. none of the above

268323. product268323. management268323. client268323. modeling

268324. Never steal data for personal gain.268324. Never distribute or sell proprietary informationobtained as part of your work on a software project.268324. Never maliciously destroy or modify another person'sprograms, files, or data, Never violate the privacy of anindividual, a group, or an organization.268324. All of the above

329872. business level orientation329872. currency of information329872. integration329872. simple

329873. constraints329873. set of components329873. semantic models329873. syntactic models

329874. algorithmic complexity329874. characteristics and constraints329874. control and data329874. design patterns

24


25/28

329875. accessibility329875. control329875. design329875. implementation

329876. Peer-level systems329876. Subordinate systems329876. Superordinate systems329876. Working systems

329877. Communications components329877. Database components329877. Interface components329877. Memory management components

329878. data flow view329878. module view329878. process view329878. user view

329879. cohesion flow329879. dependencies329879. cost329879. size

329880. low coupling329880. good modularity329880. transaction flow329880. transform flow

329881. high coupling329881. poor modularity329881. transaction flow329881. transform flow

329882. creation of a CFD329882. derivation of the control hierarchy329882. distribution of worker modules329882. refinement of the module view

329883. entity relationship diagrams

329883. module interface descriptions329883. DFD329883. test cases for each module

329884. allow interaction to interruptible329884. allow interaction to be undoable329884. hide technical internals from casual users329884. only provide one defined method for accomplishing atask

329885. define intuitive shortcuts329885. disclose information in a progressive fashion329885. establish meaningful defaults329885. provide an on-line tutorial

329886. each application should have its own distinctive lookand feel329886. None ofabove answers!329886. navigational methods are context sensitive329886. visual information is organized according to a designstandard, input mechanisms remain the same throughout theapplication

329887. design model329887. implementation model329887. user model329887. user's model

329888. design model329888. user model329888. system model329888. system perception

329889. Implementation model329889. user model329889. user's model329889. system perception

329890. cost estimation329890. interface construction329890. interface validation329890. user and task analysis

329891. have users indicate their preferences onquestionnaires329891. rely on the judgement of experienced programmers329891. None of above answers329891. observe users performing tasks manually & studyexisting computer-based solutions

329892. adaptive user profiles329892. None of above answers329892. displays system

329892. response time & error handling resolution ofgraphics

329893. code generation

25


26/28

329893. drawing tools329893. None is right answer.329893. windows handlers, input validation

329894. customers329894. experienced programmers329894. product users329894. project managers

329895. down time for the application329895. None of All329895. software reliability329895. time spent looking at help materials, number of usererrors

329896. ability to undergo change

329896. adaptability to new environments329896. operational characteristics329896. production costs and scheduling

329897. large body of scientific evidence supports their use329897. provides software engineers with an objectivemechanism for assessing software quality329897. they allow all software quality information to beexpressed unambiguously as a single number329897. all of the above

329898. design329898. feedback329898. measurement329898. quantification

329899. easy to compute329899. qualitative in nature329899. reliable over time329899. widely applicable

329900. functionality and performance329900. performance and completeness329900. specificity and completeness329900. specificity and functionality

329901. None of all

329901. data structural relationships329901. internal module complexity329901. module effectiveness & architectural structure

329902. completeness329902. efficiency329902. size329902. volatility

329903. attributes required for each class329903. completion time required for system implementation

329903. complexity of the class hierarchy | 329903. level ofobject reusability achieved

329904. making it a base class329904. making it a subclass329904. partitioning the class329904. starting a new class hierarchy

329905. complexity

329905. coupling329905. module cohesion329905. performance

329906. modules in the program329906. none of all329906. operators in the program & operands in theprogram329906. volume elements in the program

329907. metrics that focus on defect removal effectiveness329907. none of all329907. metrics that estimate the duration of the testingprocess329907. metrics that predict the number of test cases required& metrics that focus on test coverage

329908. maintainability of a software product based on itsavailability329908. relative age of a software product being consideredfor retirement329908. reliability of a software product following regressiontesting329908. stability of a software product as it is modified duringmaintenance

329909. as soon as the code is written329909. during the design stage329909. when the requirements have been formallydocumented329909. as soon as possible in the development life cycle

329910. Poor quality software329910. Poor software and poor testing329910. bad luck329910. insufficient time for testing

26


27/28

329911. to show that system will work after release329911. to decide when the software is of sufficient quality torelease329911. to find as many bugs as possible before release329911. to give information for a risk based decision aboutrelease

329912. performance testing can be done during unit testingas well as during the testing of whole system329912. The acceptance test does not necessarily include aregression test329912. Verification activities should not involve testers(reviews, inspections etc)329912. Test environments should be as similar to productionenvironments as possible

329913. as polite, constructive and helpful as possible329913. firm about insisting that a bug is not a feature if itshould be fixed329913. diplomatic, sensitive to the way they may react tocriticism

329913. All of the above

329914. the most important tests first329914. the most difficult tests first(to allow maximum timefor fixing)329914. the easiest tests first(to give initial confidence)329914. the order they are thought of All

329915. the documentation is poor, so it takes longer to findout what the software is doing.329915. wages are rising329915. the fault has been built into more

documentation,code,tests, etc329915. none of the above

329916. should be able to understand a functionalspecification or requirements document329916. should be able to understand the source code.329916. is highly motivated to find faults329916. is creative to find the systems weaknesses

329917. a process for selecting test cases329917. a process for determining expected outputs329917. a way to measure the quality of software329917. a way to measure in a test plan what has to be done

329918. needs configuration management just likerequirements, design and code329918. should be newly constructed for each new version ofthe software329918. is needed only until the software is released intoproduction or use329918. does not need to be documented and commented, asit does not form part of the released
software system

329919. only records defects329919. is of limited value329919. is a valuable source of project information duringtesting if it contains all incidents329919. should be used only by the test team.

329920. reducing test time329920. no change329920. increasing test time329920. cant say

329921. is nothing to do with testing329921. is a partial measure of test thoroughness329921. branch coverage should be mandatory for all software329921. can only be applied at unit or module testing, not atsystem testing

329922. when time for testing has run out.329922. when all planned tests have been run329922. when the test completion criteria have been met

329922. when no faults have been found by the tests run

329923. Component testing should be black box, systemtesting should be white box.329923. if u find a lot of bugs in testing, you should not bevery confident about the quality of software329923. the fewer bugs you find,the better your testing was329923. the more tests you run, the more bugs you will find.

329924. how well you know a particular technique329924. the objective of the test329924. how appropriate the technique is for testing theapplication329924. whether there is a tool to support the technique

329925. 1329925. 2329925. 3329925. 4

329926. State-Transition329926. Usability329926. Performance329926. Security

329927. State analysis329927. Coverage analysis329927. Dynamic analysis329927. Memory analysis

27


28/28

329928. IEEE829329928. IEEE610329928. BS7925-1329928. BS7925-2

329929. IEEE 829329929. IEEE 610329929. BS7925-1329929. BS7925-2

329930. Faults in program specifications are the mostexpensive to fix.329930. Faults in code are the most expensive to fix.329930. Faults in requirements are the most expensive to fix

329930. Faults in designs are the most expensive to fix.

329931. Design based329931. Big-bang329931. Bottom-up329931. Top-down

329932. statement testing329932. equivalence partitioning329932. error- guessing329932. usability testing

329933. Large329933. Small329933. Difficult to write329933. Difficult to test

329934. code inspection329934. coverage analysis329934. usability assessment329934. installation test

329935. white box329935. glass box329935. structural329935. functional

Bao g m ton b 543 cu h i v cu tr l i.