Xuetong Homework & Exercises & Homework and Tests, a collection of multiple-choice recitation editions
Note: The scope of the exam is chapters 1--9, 11, 14-17; chapters not listed are not tested
Repeated topics in Xuetong homework and exercise sets have been deleted
Self-collection of the word version of this blog: https://pan.baidu.com/s/1wvLPKc5Mb0MT8xeM3q5-LQ?pwd=1234
Extraction code: 1234
Blog Learning Pass homework has been updated Chapter 17, new link
https://pan.baidu.com/s/1b0Rf-Q8uSr74w8oJWjN9bQ?pwd=1234
Extraction code: 1234
Learning multiple choice questions reciting edition collection
learning through homework
1. (Multiple-choice questions) Requirements engineers need to have the following skills (proficiency in software development methods and technologies; very precise expression skills, especially documentation skills; very good communication skills).
2. The (events and things) that must be involved in the solution system is called the problem domain of the problem.
3. Software requirements can be classified into functional requirements, performance requirements, quality attributes, external interfaces and (constraints).
4. Excellent requirements should be complete, correct, feasible, necessary, unambiguous and (verifiable).
5. There are direct methods and (indirect methods) to solve problems.
6. The basis of problem solving is (simulation and sharing).
7. Common quality attribute requirements include reliability, usability, security, portability, ease of use, and (maintainability).
8. The two aspects of problem solving include solution system and (problem domain).
9. The requirements development process includes requirements acquisition, requirements analysis, requirements specification and (requirements verification).
10. The practical method of requirements engineering process is requirements engineering (work style and behavior method).
11. The following (statistical reports) belong to quantitative hard data?
12. Stakeholders that are easier to find are called initial stakeholders, also known as (stakeholder baseline), and usually include customers, managers and relevant investors.
13. The common difficulties in requirement acquisition do not include which of the following (model building)
14. Which of the following statements is incorrect (vision (vision), is to describe the scope of the product)
15. (Multiple choice) In requirements acquisition activities, if the project requires, two well-defined formal documents may be produced, namely () and (project prospect and scope; use case documents).
16. (Multiple-choice questions) Among the acquisition activities, the substantive steps are mainly the following points: (determine the content to be acquired; determine the source of the information to be acquired; determine the acquisition method to be adopted; implement the acquisition; record the results)
17. (Multiple-choice questions) The methods of requirement acquisition include: (interview, questionnaire, prototype, observation and document analysis)
18. (Multiple choice) Requirements engineering needs to obtain the following contents: (requirements, problem domain description, environment and constraints)
19. Sources of requirement acquisition: (stakeholders, related products, hard data, important documents, relevant technical standards and regulations)
20. Which of the following is not a clear description of the problem (too many waste products are produced).
21. In the project prospect and scope document, what information should the project prospect not include (detailed functional requirements).
22. (Multiple choice) Regarding business process analysis, the correct answer is (all).
23. (Multiple choice) Especially for You Jewelers is a small jewelry retailer in a university town~~~ Which of the following are the business requirements of the system to be developed (realize effective tracking of customer bills and receipts, realize the profit and related sales check, implementing a customer database)
24. Assuming that it is desired to have 90% certainty in all situations contained in the invoice sample, then the certainty factor should be (1,645).
25. Stakeholder identification in complex situations can use (stakeholder network) stakeholder identification method.
26. The User/Task matrix is usually used for (priority assessment) stakeholder assessment.
27. Which of the following (statistical reports) are quantitative hard data?
28. Methods for identifying stakeholders include inflating and then shrinking, stakeholder networking, and (checklist)
29. Stakeholder descriptions include job characteristics and (personal characteristics).
30. Which of the following (regulatory manuals) are qualitative hard data?
31. The Power/Interest analysis chart can be used for both stakeholder priority assessment and (risk assessment) assessment.
32. Stakeholders that are easier to find are called initial stakeholders, also known as (stakeholder baseline), and usually include customers, managers and relevant investors.
33. The principle of stakeholder sampling does not include (the more the better).
34. The interview report records a lot of content, and the following options (displeasure that occurred during the interview) do not need to be recorded.
35. Interview means (all of the above).
36. The process of carrying out the interview, including (all of the above).
37. (Multiple choice) During the interview process, what are the recommended types of questions? (Procedural prompts, meta questions)
38. (Multiple choice) Interview is a widely used demand acquisition method, which can obtain rich content, including (facts and problems; interviewee's point of view; interviewee's feelings; organizational and personal goals)
39. (Multiple choice) What are the advantages of interviews? (It can obtain a wide range of information including facts, problems, attitudes of interviewees and other types of information; it can establish mutual friendly relations with stakeholders and increase the participation enthusiasm of stakeholders in projects; the development conditions are simple and the economic cost is low)
40. Using the evolutionary prototype method, you need to pay attention to the prototype (robustness) and code quality during development.
41. Storyboard prototypes are divided into passive storyboard prototypes, active storyboard prototypes and (interactive storyboard prototypes).
42. The biggest advantage of the prototype method is that it can solve the (uncertainty) in the system development early, thereby reducing the risk of software project failure.
43. Using experimental development methods, it is necessary to implement multiple technical solutions and examine important system (quality attributes).
44. Demonstration prototypes are mainly used in (project initiation phase).
45. Classified according to the way of use, prototypes can be divided into: demonstration prototypes, (prototypes in the strict sense), test prototypes and guidance system prototypes.
46. Classified according to the development method, prototypes can be divided into: evolutionary prototypes and discarded prototypes, among which discarded prototypes are subdivided into (exploratory prototypes and experimental prototypes).
47. The basic process of using the prototype method to obtain requirements includes determining prototype requirements, prototype development, (prototype evaluation) and prototype revision links.
48. The fundamental tasks of requirements analysis include establishing analysis models and (creating software system solutions)
49. Three analysis models include calculation model, (business model) and software analysis model
50. Class diagram is an (object-oriented) method
51. Context map is a method of (structured analysis information engineering)
52. The two worlds for building analytical models are the computer world and the (problem world)
53. The disassembled sub-parts of complex systems are called (viewpoints).
54. The three elements of a model language include grammar, (pragmatics) and pragmatics.
55. Activity diagram is an (object-oriented) method
56. The main elements of an interaction diagram include objects, lifelines and (messages)
57. The sub-activities of requirements modeling include (problem domain modeling), creating solutions and solution modeling.
58. The sequence diagram expresses the sequence of messages in the interactive behavior, and the following (concurrent messages) do not belong to the messages described by the sequence diagram.
59. The key to object-oriented analysis and design is to realize the transition from (use case model) to complete object model.
60. (Multiple choice, 10 points) The establishment of a domain model needs to be completed through steps such as identifying candidate objects and classes, determining conceptual classes, establishing relationships between classes, and adding important attributes of classes. The methods for identifying candidate classes include (List of noun analysis, behavior analysis, concept class analysis).
61. (Multiple choice, 10 points) An object refers to an independently identifiable entity with a clear role in an application, and each object contains the following (identity, state, behavior) elements.
62. The generation stage of the software requirements specification document is (the definition and documentation stage of system requirements and solutions).
63. The whole process of selecting and using templates in requirements specification activities is correct (standard templates, organizational templates, project templates, project software requirements specification documents).
64. The introduction is a summary of the entire software requirements specification, which does not include the following content (product prospect).
65. The main goal of documentation is (communication).
66. Which of the following statements is wrong (the readability of the software requirements specification document refers to the use of literary means to make the document fascinating).
67. There are system expressions (all of the above).
68. The English abbreviation for Software Requirements Specification is (SRS)
69. In the process of requirements development, many different types of requirements documents may be generated, and the differences between them are manifested in (all of the above).
70. The reason for writing the requirements statement is (all of the above).
71. Requirements engineering is the sum of all requirements processing activities, which includes two parts: requirements development and (requirements management)
72. Backtracking from requirements (one of the two links of forward tracking) to explain which stakeholders' needs and (goals) software requirements come from
73. Requirements tracking is based on (software requirements specification document) as the baseline, in the forward and backward directions, to describe the requirements and the ability to track changes in requirements
74. The maintenance of the requirement baseline mainly includes configuration management and (status maintenance)
75. Backtracking refers to the evolution process from (use case) to software requirement specification document
Learning Common Problem Set
1. The biggest reason for demand problems in software production is that the (simulation) understanding of application software is not thorough or the application is not firm.
2. The purpose of requirements analysis is to ensure the requirements (completeness and consistency).
3. The results of the system requirements development will be finally written (system requirements specification).
4. The (entities and states) in the real world constitute the basic scope of problem solving, which is called the problem domain of the problem.
5. Functional requirements are usually divided into three levels, namely business requirements, user requirements and (system requirements).
6. If an intermediate object (Mediate Artifact) is used before the final object (Final Artifact) is generated
If the final object is expressed within a certain breadth and depth, then the intermediate object is considered to be the prototype of the final object in that breadth and depth.
7. According to the classification of development methods, prototypes can be divided into: evolutionary prototypes and (disposable prototypes) prototypes.
8. Classified according to the functions involved, prototypes can be divided into: horizontal prototypes and (vertical prototypes) prototypes.
9. The requirement content of the prototype can be analyzed from three latitudes: namely (appearance, role and realization).
10. When the user cannot complete the active information notification, or the language communication with the demand engineer cannot produce effective results
, it is necessary to use (observation method).
11. Which of the following (sampling-based methods) is not a common model-driven method for requirements elicitation?
12. Functional goals can be divided into (satisfaction goals and information goals).
13. The main task of the goal analysis phase of the goal-oriented method is (to establish a goal model).
14. The notation used to describe the scene must meet the requirements of formality, and generally non-formal language and semi-formal language can be used
and formal language. In practice, (informal natural language) is the main way of description.
15. The following (writing system requirements specification) is not the application of scenario method in requirements engineering.
16. Compared with other scene methods, the biggest feature of use cases is the use of (static structured text) description.
17. There are three main types of relationships between use cases (inclusion, extension, and generalization).
18. The activities of analysis mainly include identification, definition and structuring, and its purpose is to obtain something that can be converted into knowledge
information, this analysis activity is called (building a requirements analysis model).
19. (Abstract and Decompose) are two commonly used means of modeling.
20. Abstraction (reduces) the complexity of a problem by emphasizing essential features.
21. Requirements analysis only needs to describe the solution and does not need to explore the implementation details, and the analysis model is (semi-formal), which is especially applicable.
22. The context diagram describes the boundaries and connections between the system and external entities in the environment. It illustrates from a real-world perspective
The system (boundary and environment) is identified and all inputs and outputs are identified.
23. (Data Flow Diagram DFD) is the core technique of the structured analysis method, which shows the input, processing, storage and output of the system, and how they work together in harmony.
24. An important task of requirements analysis activities is to carry out (requirements refinement), clarify the implicit information of user needs, and expand it into clear behavior expectations for software systems, that is, system requirements.
25. In the hierarchical structure, DFD defines three hierarchical categories of DFD diagrams: (context diagram), 0-layer diagram and N-layer diagram.
26. Because data storage is the internal function realization of the system, when the system is regarded as a black box, there is no
will appear ( Datastore Instance ).
27. Data modeling technology can make up for the shortcomings of process modeling (data description), which describes the characteristics of data definition, structure and relationship.
28. The conceptual entity is an abstract concept that does not consider the physical existence behind the concept, so it usually does not contain the associated
other ( traits (i.e. attributes) ).
29. In ERD modeling, entities usually refer to (logical entities).
30. Attributes in ERD are characteristics of entities, not data. Attributes will exist in a certain form, and this existence is the number
data, known as the (value) of an attribute.
31. The degree of relationship (Degree) in ERD refers to the number of entities participating in the relationship, and is an index to measure the relationship (complexity).
32. The cardinality of relations in ERD is divided into large cardinality and small cardinality. Large cardinality is also known as (key constraint).
33. When establishing a relationship between entities, some incidental entities may be generated, which are called associated entities. The common form
Yes ( process_entity ).
34. Among the technologies to realize the synchronization of ERD and process model, (function/entity matrix) is a relatively common technology.
35. The following (attributes) are not relationships in the use case model?
36. The system boundary refers to the dividing line between the system components contained in a system and the things outside the system. The use case model uses a
(Rectangular box) to represent the system boundary to show the context of the system.
37. There are three behavioral models used by UML, namely: (interaction diagram, state diagram and activity diagram).
38. Project vision and scope documents, user requirements documents are considered to belong (user documents), and the focus is on the real world of users.
39. System requirement specification document, software requirement specification document, hardware requirement specification document, interface requirement specification document
Format specification documents and human-computer interaction documents are used together for the purpose of system development and are considered (development documents).
40. The following (sellers) are not the readers of the requirements specification document?