{"msg":"第一节 专业英语","code":200,"data":{"currentIndex":null,"examId":null,"examTime":null,"questionList":[{"id":"796239675344834561","title":"<p><strong>请作答第<span style=\"color: red\">4</span>个空。</strong></p>A requirement is simply a statement of what the system must do or what characteristics it needs to have. Requirements evolve from broad statements of overall （71） from the system to detailed statements of the business capabilities that a system should support to detailed technical statements of the way in which the capabilities will be implemented in the new system. （72） focus on describing how to create the software product that will be produced from the project Nonfunctional requirements are primarily used in the design phase when decisions are made about the user interface, the hardware and software, and the system's underlying architecture. The system's physical and technical environments would be considered （73）. The speed, capacity, and reliability of the system belong to （74）. （75） describes that who has authorized access to the system under what circumstances.","analyze":"需求只是陈述了系统必须做什么或者系统需要有什么特性，需求来自于从系统总体业务需要的广泛陈述到系统所支持业务能力的详细陈述，再到新系统能力实现中所采用方法的详细技术陈述。功能性需求致力于描述如何创建将在项目中产生的软件产品。非功能性需求主要在设计阶段中做出关于用户界面、硬件和软件，以及系统底层架构的决策时使用。系统的物理和技术环境将被看作一种操作需求。系统的速度、能力和可靠性属于性能需求。安全性需求描述了谁在什么情况下具有访问系统的权限。","multi":0,"questionType":1,"answer":"B","chooseItem":["796239676292747265"],"itemList":[{"id":"796239676259192833","questionId":"796239675344834561","content":" security requirement","answer":0,"chooseValue":"A"},{"id":"796239676292747265","questionId":"796239675344834561","content":" performance requirement","answer":1,"chooseValue":"B"},{"id":"796239676317913089","questionId":"796239675344834561","content":" technical requirement","answer":0,"chooseValue":"C"},{"id":"796239676347273217","questionId":"796239675344834561","content":" information requirement","answer":0,"chooseValue":"D"}],"userAnswer":null,"userChooseItem":null,"answerCorrect":null,"userCollect":null},{"id":"796239749114253313","title":"<p><strong>请作答第<span style=\"color: red\">2</span>个空。</strong></p>Many of the activities performed during the preliminary investigation are still being conducted in (71).but in much greater depth than before. During this phase, the analyst must become fully aware of the(72)and must develop enough knowledge about the(73)and the existing systems to. enable an effective solution to be proposed and implemented. Besides the(74)for process and data of current system,the deliverable from this phase also includes the(75)for the proposed system.","analyze":"初始调查阶段的许多活动仍然会在分析阶段进行，但会比前面更为深入。在这个阶段，分析师必须认识到根本性问题并且必须获取到足够的关于业务环境和现有系统的知识，以便提出和实现一种有效的解决方案。除了现有系统过程与数据的逻辑模型外，这一阶段的交付品还包括了所建议系统的形式化需求定义。","multi":0,"questionType":1,"answer":"B","chooseItem":["796239750057971713"],"itemList":[{"id":"796239750024417281","questionId":"796239749114253313","content":" main symptom","answer":0,"chooseValue":"A"},{"id":"796239750057971713","questionId":"796239749114253313","content":" root problem","answer":1,"chooseValue":"B"},{"id":"796239750087331841","questionId":"796239749114253313","content":" final blueprint","answer":0,"chooseValue":"C"},{"id":"796239750120886273","questionId":"796239749114253313","content":" data specification","answer":0,"chooseValue":"D"}],"userAnswer":null,"userChooseItem":null,"answerCorrect":null,"userCollect":null},{"id":"796239690310111233","title":"<p><strong>请作答第<span style=\"color: red\">4</span>个空。</strong></p>A requirement is simply a statement of what the system must do or what characteristics it needs to have. Requirements written from the perspective of user and focus on user needs are called __(71)__. Requirements written from the developer's perspective and describe how the system will be implemented are called __(72)__. Requirements evolve from detailed statemens of business capabilities that a system should have to detailed statements of the technical way in whick the capabilities will be implemented in the new system. Requirements can be either functional or nofunctional in nature. For example, during the analysis phase of travel vehicles sales system, the system that must have the ability to search for available inventory is __(73)__. The requirement that the system should be able to work on any Web browser belongs to __(74)__. That customer personal information is protected in compliance with the Data Protection Act is a requirement of __(75)__.","analyze":"简单说需求就是关于系统必须做什么或需要有哪些特点的陈述。从用户角度所撰写的需求主要关注用户的需要，称为业务需求。从开发者角度所撰写的需求主要描述系统如何被实现，称为系统需求。需求从一个系统应有业务功能的详细陈述演变到新系统中实现这些功能中所采用技术途径的详细陈述。需求本身可以是功能性或非功能性的。例如，在旅行车销售系统的分析阶段，系统必须能够搜索现有的库存是一种功能性需求。系统应该能够适应任何Web浏览器的需求属于操作需求。客户个人信息应依照Data Protection Act予以保护则是文化和政治方面的需求。","multi":0,"questionType":1,"answer":"C","chooseItem":["796239691304161281"],"itemList":[{"id":"796239691245441025","questionId":"796239690310111233","content":" functional requirements","answer":0,"chooseValue":"A"},{"id":"796239691274801153","questionId":"796239690310111233","content":" technical requirements","answer":0,"chooseValue":"B"},{"id":"796239691304161281","questionId":"796239690310111233","content":" operational requirements","answer":1,"chooseValue":"C"},{"id":"796239691329327105","questionId":"796239690310111233","content":" information requirements","answer":0,"chooseValue":"D"}],"userAnswer":null,"userChooseItem":null,"answerCorrect":null,"userCollect":null},{"id":"796239772182925313","title":"<p><strong>请作答第<span style=\"color: red\">1</span>个空。</strong></p>System analysis is traditionally done top-down using structured analysis based on(71).Object-oriented analysis focuses on creation of models.The three types of the analysis model are(72).There are two substages of object-oriented analysis.(73)focuses on real-world things whose semantics the application captures.The object constructed in the requirement analysis shows the(74)of the real-world system and organizes it into workable pieces.(75)addresses the computer aspects of the application that are visible to users.The objects are those which can be expected to vary from time to time quite rapidly.","analyze":"传统的系统分析以功能分解为基础，利用结构化分析自顶向下完成。面向对象分析关注于模型的创建。该分析模型有三种类型：类模型、交互模型和状态模型。面向对象分析有两个子阶段。领域分析侧重于现实世界中那些语义被应用程序获取的事物。在需求分析中所构造的对象说明了现实世界系统的静态结构并将其组织为可用的片段。应用分析处理应用系统中用户可见的计算机问题。所分析的对象可能会被预计时不时地发生较快的变化。","multi":0,"questionType":1,"answer":"A","chooseItem":["796239773109866497"],"itemList":[{"id":"796239773109866497","questionId":"796239772182925313","content":" functional decomposition","answer":1,"chooseValue":"A"},{"id":"796239773139226625","questionId":"796239772182925313","content":" object abstraction","answer":0,"chooseValue":"B"},{"id":"796239773164392449","questionId":"796239772182925313","content":" data inheritance","answer":0,"chooseValue":"C"},{"id":"796239773189558273","questionId":"796239772182925313","content":" information generalization","answer":0,"chooseValue":"D"}],"userAnswer":null,"userChooseItem":null,"answerCorrect":null,"userCollect":null},{"id":"796239733695991809","title":"<p><strong>请作答第<span style=\"color: red\">2</span>个空。</strong></p>Feasibility should be measured throughout the life cycle of system development. The scope and complexity of an apparently feasible project can change after the initial problems and opportunities are fully analyzed or after the system has been designed. Thus, a project that is feasible at one point may become infeasible later. The first feasibility analysis is conducted during the (71) . The (72) represents a major feasibility analysis activity since it charts one of many possible implementations as the target for systems design. (73) is a measure of how well the solution will work in the organization. It is also a measure of how people feel about the system. When it is determined in the later stages of the system life cycle, (74) is often performed with a working prototype of the proposed system. This is a test of the system’s user interfaces and is measured in how easy they are to learn and to use and how they support the desired productivity levels of the users. Economic feasibility has been defined as a cost-benefit analysis. The (75) technique is a simple and popular method for determining if and when an investment will pay for itself.","analyze":"可行性的判定贯穿于系统幵发的生命周期。一个明显可行的项目，在全面分析了初始问题和机会或系统设计后，其范围和复杂性会发生变化。因此，某一时刻可行的项目在此后可能会变得不可行。第一次可行性分析在初始调研阶段进行。由于要绘制多个可能的实现方案之一作为系统设计的目标，决策分析阶段表示一个主要的可行性分析活动。 操作可行性是对解决方案在企业中工作效果的度量，它也是衡量人们对于系统的感受。当它在系统生命周期后面的阶段被确定后，经常会用一个建议系统的工作原型进行可用性分析。这是对系统用户界面的一种测试，它通过系统如何易于学习和使用及系统如何支持用户所期望的生产力水平进行衡量。偿还分析技术是一种简单流行的方法用于确定是否及何时将收回成本。","multi":0,"questionType":1,"answer":"D","chooseItem":["796239734719401985"],"itemList":[{"id":"796239734614544385","questionId":"796239733695991809","content":" problem analysis phase","answer":0,"chooseValue":"A"},{"id":"796239734648098817","questionId":"796239733695991809","content":" preliminary investigation phase","answer":0,"chooseValue":"B"},{"id":"796239734681653249","questionId":"796239733695991809","content":" requirements analysis phase","answer":0,"chooseValue":"C"},{"id":"796239734719401985","questionId":"796239733695991809","content":" decision analysis phase","answer":1,"chooseValue":"D"}],"userAnswer":null,"userChooseItem":null,"answerCorrect":null,"userCollect":null},{"id":"796239799093579777","title":"<p><strong>请作答第<span style=\"color: red\">5</span>个空。</strong></p>The analysis phase answers the questions of who will use the system, what the system will do, and where and when it will be used. During this phase, the project team investigates any current system, identifies (71)，and develops&nbsp;a concept for the new system. This phase has tbree steps: first, (72) is developed to guide the project team's efforts. It usually includes an analysis of the current system and its problems, and the ways to design a new system. The next step is (73) .The analysis of this information - in conjunction with input from the project sponsor and many other people - leads to the development of a concept for&nbsp;a new system. The system concept is then used as a basis to develop a set of business analysis models that describes how the business will operate if the new system were developed. The set of models typically includes models that represent the (74) necessary to support the underlying business process. Last, the analyses, system concepts, and models are combined into a document called the (75) , which is presented to the project sponsor and other key decision makers that decide whether the project should continue to move forward.","analyze":"分析阶段回答谁将使用该系统、系统能做什么及系统在何时何地使用的问题。在该阶段，项目组调研当前系统、识别改进机会并开发出一个新系统的概念。这个阶段分为三个步骤：首先，开发一个分析策略来指导项目组工作。这些分析策略通常包括了当前系统及其问题的分析和设计新系统的方法。下一步是需求收集。对这些信息（汇同系统发起人和很多其他人员的输入）的分析会导致开发出一个新系统的概念。系统概念作为开发一组业务分析模型的基础，这些模型描述了新系统开发完成后企业如何运作。这组模型通常包含那些表示数据和过程的模型，这些数据和过程是支持底层业务过程所必需的。最后，这些分析、系统概念和模型合并到一个称为系统建议书的文档中，将被提交给项目组发起人和其他决定项目是否继续执行的主要决策人员。","multi":0,"questionType":1,"answer":"C","chooseItem":["796239800100212737"],"itemList":[{"id":"796239800028909569","questionId":"796239799093579777","content":" requirements statement","answer":0,"chooseValue":"A"},{"id":"796239800062464001","questionId":"796239799093579777","content":" design specification","answer":0,"chooseValue":"B"},{"id":"796239800100212737","questionId":"796239799093579777","content":" system proposal","answer":1,"chooseValue":"C"},{"id":"796239800133767169","questionId":"796239799093579777","content":" project charter","answer":0,"chooseValue":"D"}],"userAnswer":null,"userChooseItem":null,"answerCorrect":null,"userCollect":null},{"id":"796239739941310465","title":"<p><strong>请作答第<span style=\"color: red\">4</span>个空。</strong></p>Feasibility should be measured throughout the life cycle of system development. The scope and complexity of an apparently feasible project can change after the initial problems and opportunities are fully analyzed or after the system has been designed. Thus, a project that is feasible at one point may become infeasible later. The first feasibility analysis is conducted during the (71) . The (72) represents a major feasibility analysis activity since it charts one of many possible implementations as the target for systems design. (73) is a measure of how well the solution will work in the organization. It is also a measure of how people feel about the system. When it is determined in the later stages of the system life cycle, (74) is often performed with a working prototype of the proposed system. This is a test of the system’s user interfaces and is measured in how easy they are to learn and to use and how they support the desired productivity levels of the users. Economic feasibility has been defined as a cost-benefit analysis. The (75) technique is a simple and popular method for determining if and when an investment will pay for itself.","analyze":"可行性的判定贯穿于系统幵发的生命周期。一个明显可行的项目，在全面分析了初始问题和机会或系统设计后，其范围和复杂性会发生变化。因此，某一时刻可行的项目在此后可能会变得不可行。第一次可行性分析在初始调研阶段进行。由于要绘制多个可能的实现方案之一作为系统设计的目标，决策分析阶段表示一个主要的可行性分析活动。 操作可行性是对解决方案在企业中工作效果的度量，它也是衡量人们对于系统的感受。当它在系统生命周期后面的阶段被确定后，经常会用一个建议系统的工作原型进行可用性分析。这是对系统用户界面的一种测试，它通过系统如何易于学习和使用及系统如何支持用户所期望的生产力水平进行衡量。偿还分析技术是一种简单流行的方法用于确定是否及何时将收回成本。","multi":0,"questionType":1,"answer":"C","chooseItem":["796239740926971905"],"itemList":[{"id":"796239740859863041","questionId":"796239739941310465","content":" performance analysis","answer":0,"chooseValue":"A"},{"id":"796239740901806081","questionId":"796239739941310465","content":" control analysis","answer":0,"chooseValue":"B"},{"id":"796239740926971905","questionId":"796239739941310465","content":" usability analysis","answer":1,"chooseValue":"C"},{"id":"796239740947943425","questionId":"796239739941310465","content":" interface analysis","answer":0,"chooseValue":"D"}],"userAnswer":null,"userChooseItem":null,"answerCorrect":null,"userCollect":null},{"id":"796239684291284993","title":"<p><strong>请作答第<span style=\"color: red\">2</span>个空。</strong></p>A requirement is simply a statement of what the system must do or what characteristics it needs to have. Requirements written from the perspective of user and focus on user needs are called __(71)__. Requirements written from the developer's perspective and describe how the system will be implemented are called __(72)__. Requirements evolve from detailed statemens of business capabilities that a system should have to detailed statements of the technical way in whick the capabilities will be implemented in the new system. Requirements can be either functional or nofunctional in nature. For example, during the analysis phase of travel vehicles sales system, the system that must have the ability to search for available inventory is __(73)__. The requirement that the system should be able to work on any Web browser belongs to __(74)__. That customer personal information is protected in compliance with the Data Protection Act is a requirement of __(75)__.","analyze":"简单说需求就是关于系统必须做什么或需要有哪些特点的陈述。从用户角度所撰写的需求主要关注用户的需要，称为业务需求。从开发者角度所撰写的需求主要描述系统如何被实现，称为系统需求。需求从一个系统应有业务功能的详细陈述演变到新系统中实现这些功能中所采用技术途径的详细陈述。需求本身可以是功能性或非功能性的。例如，在旅行车销售系统的分析阶段，系统必须能够搜索现有的库存是一种功能性需求。系统应该能够适应任何Web浏览器的需求属于操作需求。客户个人信息应依照Data Protection Act予以保护则是文化和政治方面的需求。","multi":0,"questionType":1,"answer":"D","chooseItem":["796239685373415425"],"itemList":[{"id":"796239685289529345","questionId":"796239684291284993","content":" operational requirements","answer":0,"chooseValue":"A"},{"id":"796239685318889473","questionId":"796239684291284993","content":" business requirements","answer":0,"chooseValue":"B"},{"id":"796239685344055297","questionId":"796239684291284993","content":" technical requirements","answer":0,"chooseValue":"C"},{"id":"796239685373415425","questionId":"796239684291284993","content":" system requirements","answer":1,"chooseValue":"D"}],"userAnswer":null,"userChooseItem":null,"answerCorrect":null,"userCollect":null},{"id":"796239796128206849","title":"<p><strong>请作答第<span style=\"color: red\">4</span>个空。</strong></p>The analysis phase answers the questions of who will use the system, what the system will do, and where and when it will be used. During this phase, the project team investigates any current system, identifies (71)，and develops&nbsp;a concept for the new system. This phase has tbree steps: first, (72) is developed to guide the project team's efforts. It usually includes an analysis of the current system and its problems, and the ways to design a new system. The next step is (73) .The analysis of this information - in conjunction with input from the project sponsor and many other people - leads to the development of a concept for&nbsp;a new system. The system concept is then used as a basis to develop a set of business analysis models that describes how the business will operate if the new system were developed. The set of models typically includes models that represent the (74) necessary to support the underlying business process. Last, the analyses, system concepts, and models are combined into a document called the (75) , which is presented to the project sponsor and other key decision makers that decide whether the project should continue to move forward.","analyze":"分析阶段回答谁将使用该系统、系统能做什么及系统在何时何地使用的问题。在该阶段，项目组调研当前系统、识别改进机会并开发出一个新系统的概念。这个阶段分为三个步骤：首先，开发一个分析策略来指导项目组工作。这些分析策略通常包括了当前系统及其问题的分析和设计新系统的方法。下一步是需求收集。对这些信息（汇同系统发起人和很多其他人员的输入）的分析会导致开发出一个新系统的概念。系统概念作为开发一组业务分析模型的基础，这些模型描述了新系统开发完成后企业如何运作。这组模型通常包含那些表示数据和过程的模型，这些数据和过程是支持底层业务过程所必需的。最后，这些分析、系统概念和模型合并到一个称为系统建议书的文档中，将被提交给项目组发起人和其他决定项目是否继续执行的主要决策人员。","multi":0,"questionType":1,"answer":"A","chooseItem":["796239797046759425"],"itemList":[{"id":"796239797046759425","questionId":"796239796128206849","content":" data and processes","answer":1,"chooseValue":"A"},{"id":"796239797076119553","questionId":"796239796128206849","content":" system infrastructures","answer":0,"chooseValue":"B"},{"id":"796239797105479681","questionId":"796239796128206849","content":" external agents","answer":0,"chooseValue":"C"},{"id":"796239797134839809","questionId":"796239796128206849","content":" design specification","answer":0,"chooseValue":"D"}],"userAnswer":null,"userChooseItem":null,"answerCorrect":null,"userCollect":null},{"id":"796239693250318337","title":"<p><strong>请作答第<span style=\"color: red\">5</span>个空。</strong></p>A requirement is simply a statement of what the system must do or what characteristics it needs to have. Requirements written from the perspective of user and focus on user needs are called __(71)__. Requirements written from the developer's perspective and describe how the system will be implemented are called __(72)__. Requirements evolve from detailed statemens of business capabilities that a system should have to detailed statements of the technical way in whick the capabilities will be implemented in the new system. Requirements can be either functional or nofunctional in nature. For example, during the analysis phase of travel vehicles sales system, the system that must have the ability to search for available inventory is __(73)__. The requirement that the system should be able to work on any Web browser belongs to __(74)__. That customer personal information is protected in compliance with the Data Protection Act is a requirement of __(75)__.","analyze":"简单说需求就是关于系统必须做什么或需要有哪些特点的陈述。从用户角度所撰写的需求主要关注用户的需要，称为业务需求。从开发者角度所撰写的需求主要描述系统如何被实现，称为系统需求。需求从一个系统应有业务功能的详细陈述演变到新系统中实现这些功能中所采用技术途径的详细陈述。需求本身可以是功能性或非功能性的。例如，在旅行车销售系统的分析阶段，系统必须能够搜索现有的库存是一种功能性需求。系统应该能够适应任何Web浏览器的需求属于操作需求。客户个人信息应依照Data Protection Act予以保护则是文化和政治方面的需求。","multi":0,"questionType":1,"answer":"D","chooseItem":["796239694282117121"],"itemList":[{"id":"796239694219202561","questionId":"796239693250318337","content":" information requirements","answer":0,"chooseValue":"A"},{"id":"796239694240174081","questionId":"796239693250318337","content":" system performance","answer":0,"chooseValue":"B"},{"id":"796239694261145601","questionId":"796239693250318337","content":" secrity and control","answer":0,"chooseValue":"C"},{"id":"796239694282117121","questionId":"796239693250318337","content":" cultural and political","answer":1,"chooseValue":"D"}],"userAnswer":null,"userChooseItem":null,"answerCorrect":null,"userCollect":null},{"id":"796239755024027649","title":"<p><strong>请作答第<span style=\"color: red\">4</span>个空。</strong></p>Many of the activities performed during the preliminary investigation are still being conducted in (71).but in much greater depth than before. During this phase, the analyst must become fully aware of the(72)and must develop enough knowledge about the(73)and the existing systems to. enable an effective solution to be proposed and implemented. Besides the(74)for process and data of current system,the deliverable from this phase also includes the(75)for the proposed system.","analyze":"初始调查阶段的许多活动仍然会在分析阶段进行，但会比前面更为深入。在这个阶段，分析师必须认识到根本性问题并且必须获取到足够的关于业务环境和现有系统的知识，以便提出和实现一种有效的解决方案。除了现有系统过程与数据的逻辑模型外，这一阶段的交付品还包括了所建议系统的形式化需求定义。","multi":0,"questionType":1,"answer":"A","chooseItem":["796239755988717569"],"itemList":[{"id":"796239755988717569","questionId":"796239755024027649","content":" logical models","answer":1,"chooseValue":"A"},{"id":"796239756018077697","questionId":"796239755024027649","content":" physical models","answer":0,"chooseValue":"B"},{"id":"796239756051632129","questionId":"796239755024027649","content":" design models","answer":0,"chooseValue":"C"},{"id":"796239756080992257","questionId":"796239755024027649","content":" implementation models","answer":0,"chooseValue":"D"}],"userAnswer":null,"userChooseItem":null,"answerCorrect":null,"userCollect":null},{"id":"796239781297147905","title":"<p><strong>请作答第<span style=\"color: red\">4</span>个空。</strong></p>System analysis is traditionally done top-down using structured analysis based on(71).Object-oriented analysis focuses on creation of models.The three types of the analysis model are(72).There are two substages of object-oriented analysis.(73)focuses on real-world things whose semantics the application captures.The object constructed in the requirement analysis shows the(74)of the real-world system and organizes it into workable pieces.(75)addresses the computer aspects of the application that are visible to users.The objects are those which can be expected to vary from time to time quite rapidly.","analyze":"传统的系统分析以功能分解为基础，利用结构化分析自顶向下完成。面向对象分析关注于模型的创建。该分析模型有三种类型：类模型、交互模型和状态模型。面向对象分析有两个子阶段。领域分析侧重于现实世界中那些语义被应用程序获取的事物。在需求分析中所构造的对象说明了现实世界系统的静态结构并将其组织为可用的片段。应用分析处理应用系统中用户可见的计算机问题。所分析的对象可能会被预计时不时地发生较快的变化。","multi":0,"questionType":1,"answer":"A","chooseItem":["796239782224089089"],"itemList":[{"id":"796239782224089089","questionId":"796239781297147905","content":" static structure","answer":1,"chooseValue":"A"},{"id":"796239782257643521","questionId":"796239781297147905","content":" system components","answer":0,"chooseValue":"B"},{"id":"796239782287003649","questionId":"796239781297147905","content":" data flows","answer":0,"chooseValue":"C"},{"id":"796239782316363777","questionId":"796239781297147905","content":" program procedures","answer":0,"chooseValue":"D"}],"userAnswer":null,"userChooseItem":null,"answerCorrect":null,"userCollect":null},{"id":"796239816244088833","title":"<p><strong>请作答第<span style=\"color: red\">2</span>个空。</strong></p>The traditional model for systems development was that an IT department used (71)which is a process-centered technique, and consulted users only when their input or approval was needed.Compared with traditional methods, many companies find that JAD allows key users to participate effectively in the (72).When properly used, JAD can result in a more accurate statement of system requirements, a better understanding of common goals, and a stronger commitment to the success of the new system. RAD is a team-based technique that speeds up information systems development and produces a functioning information system. While the end product of JAD is a(an) (73),the end product of RAD is the (74).The RAD model consists of four phases. During the (75),users interact with systems analysts and develop models and prototypes that represent all system processes, outputs, and inputs.","analyze":"系统开发的传统模式是IT部门使用一种以过程为中心的结构化分析技术，只有当需要用户输入或认可的时候才与用户讨论。与传统方法相比，许多公司发现JAD能让主要用户有效地参与到需求建模过程中。如果使用得当，JAD能够产生更为准确的系统需求陈述，更好地理解共同目标和对于新系统取得成功更强有力的承诺。RAD是一种团队开发技术，能够加快信息系统的开发并生产出正常运作的信息系统。JAD的最终产品是一个需求模型，而RAD的最终产品是新的信息系统。RAD模型包括4个阶段。在用户设计阶段，用户与系统分析员交互，开发模型和原型以表示系统所有的加工、输出和输入。","multi":0,"questionType":1,"answer":"B","chooseItem":["796239817187807233"],"itemList":[{"id":"796239817162641409","questionId":"796239816244088833","content":" initial scope definition","answer":0,"chooseValue":"A"},{"id":"796239817187807233","questionId":"796239816244088833","content":" requirements modeling process","answer":1,"chooseValue":"B"},{"id":"796239817212973057","questionId":"796239816244088833","content":" object modeling process","answer":0,"chooseValue":"C"},{"id":"796239817233944577","questionId":"796239816244088833","content":" architecture design","answer":0,"chooseValue":"D"}],"userAnswer":null,"userChooseItem":null,"answerCorrect":null,"userCollect":null},{"id":"796239787223699457","title":"<p><strong>请作答第<span style=\"color: red\">1</span>个空。</strong></p>The analysis phase answers the questions of who will use the system, what the system will do, and where and when it will be used. During this phase, the project team investigates any current system, identifies (71)，and develops&nbsp;a concept for the new system. This phase has tbree steps: first, (72) is developed to guide the project team's efforts. It usually includes an analysis of the current system and its problems, and the ways to design a new system. The next step is (73) .The analysis of this information - in conjunction with input from the project sponsor and many other people - leads to the development of a concept for&nbsp;a new system. The system concept is then used as a basis to develop a set of business analysis models that describes how the business will operate if the new system were developed. The set of models typically includes models that represent the (74) necessary to support the underlying business process. Last, the analyses, system concepts, and models are combined into a document called the (75) , which is presented to the project sponsor and other key decision makers that decide whether the project should continue to move forward.","analyze":"分析阶段回答谁将使用该系统、系统能做什么及系统在何时何地使用的问题。在该阶段，项目组调研当前系统、识别改进机会并开发出一个新系统的概念。这个阶段分为三个步骤：首先，开发一个分析策略来指导项目组工作。这些分析策略通常包括了当前系统及其问题的分析和设计新系统的方法。下一步是需求收集。对这些信息（汇同系统发起人和很多其他人员的输入）的分析会导致开发出一个新系统的概念。系统概念作为开发一组业务分析模型的基础，这些模型描述了新系统开发完成后企业如何运作。这组模型通常包含那些表示数据和过程的模型，这些数据和过程是支持底层业务过程所必需的。最后，这些分析、系统概念和模型合并到一个称为系统建议书的文档中，将被提交给项目组发起人和其他决定项目是否继续执行的主要决策人员。","multi":0,"questionType":1,"answer":"A","chooseItem":["796239788142252033"],"itemList":[{"id":"796239788142252033","questionId":"796239787223699457","content":" improvement opportunities","answer":1,"chooseValue":"A"},{"id":"796239788163223553","questionId":"796239787223699457","content":" logical model","answer":0,"chooseValue":"B"},{"id":"796239788192583681","questionId":"796239787223699457","content":" system requirements","answer":0,"chooseValue":"C"},{"id":"796239788217749505","questionId":"796239787223699457","content":" system architecture","answer":0,"chooseValue":"D"}],"userAnswer":null,"userChooseItem":null,"answerCorrect":null,"userCollect":null},{"id":"796239813295493121","title":"<p><strong>请作答第<span style=\"color: red\">1</span>个空。</strong></p>The traditional model for systems development was that an IT department used (71)which is a process-centered technique, and consulted users only when their input or approval was needed.Compared with traditional methods, many companies find that JAD allows key users to participate effectively in the (72).When properly used, JAD can result in a more accurate statement of system requirements, a better understanding of common goals, and a stronger commitment to the success of the new system. RAD is a team-based technique that speeds up information systems development and produces a functioning information system. While the end product of JAD is a(an) (73),the end product of RAD is the (74).The RAD model consists of four phases. During the (75),users interact with systems analysts and develop models and prototypes that represent all system processes, outputs, and inputs.","analyze":"系统开发的传统模式是IT部门使用一种以过程为中心的结构化分析技术，只有当需要用户输入或认可的时候才与用户讨论。与传统方法相比，许多公司发现JAD能让主要用户有效地参与到需求建模过程中。如果使用得当，JAD能够产生更为准确的系统需求陈述，更好地理解共同目标和对于新系统取得成功更强有力的承诺。RAD是一种团队开发技术，能够加快信息系统的开发并生产出正常运作的信息系统。JAD的最终产品是一个需求模型，而RAD的最终产品是新的信息系统。RAD模型包括4个阶段。在用户设计阶段，用户与系统分析员交互，开发模型和原型以表示系统所有的加工、输出和输入。","multi":0,"questionType":1,"answer":"A","chooseItem":["796239814209851393"],"itemList":[{"id":"796239814209851393","questionId":"796239813295493121","content":" structured analysis","answer":1,"chooseValue":"A"},{"id":"796239814235017217","questionId":"796239813295493121","content":" object-oriented analysis","answer":0,"chooseValue":"B"},{"id":"796239814260183041","questionId":"796239813295493121","content":" prototype analysis","answer":0,"chooseValue":"C"},{"id":"796239814285348865","questionId":"796239813295493121","content":" process analysis","answer":0,"chooseValue":"D"}],"userAnswer":null,"userChooseItem":null,"answerCorrect":null,"userCollect":null},{"id":"796239822120308737","title":"<p><strong>请作答第<span style=\"color: red\">4</span>个空。</strong></p>The traditional model for systems development was that an IT department used (71)which is a process-centered technique, and consulted users only when their input or approval was needed.Compared with traditional methods, many companies find that JAD allows key users to participate effectively in the (72).When properly used, JAD can result in a more accurate statement of system requirements, a better understanding of common goals, and a stronger commitment to the success of the new system. RAD is a team-based technique that speeds up information systems development and produces a functioning information system. While the end product of JAD is a(an) (73),the end product of RAD is the (74).The RAD model consists of four phases. During the (75),users interact with systems analysts and develop models and prototypes that represent all system processes, outputs, and inputs.","analyze":"系统开发的传统模式是IT部门使用一种以过程为中心的结构化分析技术，只有当需要用户输入或认可的时候才与用户讨论。与传统方法相比，许多公司发现JAD能让主要用户有效地参与到需求建模过程中。如果使用得当，JAD能够产生更为准确的系统需求陈述，更好地理解共同目标和对于新系统取得成功更强有力的承诺。RAD是一种团队开发技术，能够加快信息系统的开发并生产出正常运作的信息系统。JAD的最终产品是一个需求模型，而RAD的最终产品是新的信息系统。RAD模型包括4个阶段。在用户设计阶段，用户与系统分析员交互，开发模型和原型以表示系统所有的加工、输出和输入。","multi":0,"questionType":1,"answer":"D","chooseItem":["796239823156301825"],"itemList":[{"id":"796239823084998657","questionId":"796239822120308737","content":" system proposal","answer":0,"chooseValue":"A"},{"id":"796239823105970177","questionId":"796239822120308737","content":" system design model","answer":0,"chooseValue":"B"},{"id":"796239823131136001","questionId":"796239822120308737","content":" new system architecture","answer":0,"chooseValue":"C"},{"id":"796239823156301825","questionId":"796239822120308737","content":" new information system","answer":1,"chooseValue":"D"}],"userAnswer":null,"userChooseItem":null,"answerCorrect":null,"userCollect":null},{"id":"796239758064898049","title":"<p><strong>请作答第<span style=\"color: red\">5</span>个空。</strong></p>Many of the activities performed during the preliminary investigation are still being conducted in (71).but in much greater depth than before. During this phase, the analyst must become fully aware of the(72)and must develop enough knowledge about the(73)and the existing systems to. enable an effective solution to be proposed and implemented. Besides the(74)for process and data of current system,the deliverable from this phase also includes the(75)for the proposed system.","analyze":"初始调查阶段的许多活动仍然会在分析阶段进行，但会比前面更为深入。在这个阶段，分析师必须认识到根本性问题并且必须获取到足够的关于业务环境和现有系统的知识，以便提出和实现一种有效的解决方案。除了现有系统过程与数据的逻辑模型外，这一阶段的交付品还包括了所建议系统的形式化需求定义。","multi":0,"questionType":1,"answer":"C","chooseItem":["796239759063142401"],"itemList":[{"id":"796239759004422145","questionId":"796239758064898049","content":" hardware and software specification","answer":0,"chooseValue":"A"},{"id":"796239759033782273","questionId":"796239758064898049","content":" system performance specification","answer":0,"chooseValue":"B"},{"id":"796239759063142401","questionId":"796239758064898049","content":" formal requirements definition","answer":1,"chooseValue":"C"},{"id":"796239759088308225","questionId":"796239758064898049","content":" general problem statement","answer":0,"chooseValue":"D"}],"userAnswer":null,"userChooseItem":null,"answerCorrect":null,"userCollect":null},{"id":"796239736808165377","title":"<p><strong>请作答第<span style=\"color: red\">3</span>个空。</strong></p>Feasibility should be measured throughout the life cycle of system development. The scope and complexity of an apparently feasible project can change after the initial problems and opportunities are fully analyzed or after the system has been designed. Thus, a project that is feasible at one point may become infeasible later. The first feasibility analysis is conducted during the (71) . The (72) represents a major feasibility analysis activity since it charts one of many possible implementations as the target for systems design. (73) is a measure of how well the solution will work in the organization. It is also a measure of how people feel about the system. When it is determined in the later stages of the system life cycle, (74) is often performed with a working prototype of the proposed system. This is a test of the system’s user interfaces and is measured in how easy they are to learn and to use and how they support the desired productivity levels of the users. Economic feasibility has been defined as a cost-benefit analysis. The (75) technique is a simple and popular method for determining if and when an investment will pay for itself.","analyze":"可行性的判定贯穿于系统幵发的生命周期。一个明显可行的项目，在全面分析了初始问题和机会或系统设计后，其范围和复杂性会发生变化。因此，某一时刻可行的项目在此后可能会变得不可行。第一次可行性分析在初始调研阶段进行。由于要绘制多个可能的实现方案之一作为系统设计的目标，决策分析阶段表示一个主要的可行性分析活动。 操作可行性是对解决方案在企业中工作效果的度量，它也是衡量人们对于系统的感受。当它在系统生命周期后面的阶段被确定后，经常会用一个建议系统的工作原型进行可用性分析。这是对系统用户界面的一种测试，它通过系统如何易于学习和使用及系统如何支持用户所期望的生产力水平进行衡量。偿还分析技术是一种简单流行的方法用于确定是否及何时将收回成本。","multi":0,"questionType":1,"answer":"A","chooseItem":["796239737743495169"],"itemList":[{"id":"796239737743495169","questionId":"796239736808165377","content":" Operational feasibility","answer":1,"chooseValue":"A"},{"id":"796239737777049601","questionId":"796239736808165377","content":" Technical feasibility","answer":0,"chooseValue":"B"},{"id":"796239737814798337","questionId":"796239736808165377","content":" Schedule feasibility","answer":0,"chooseValue":"C"},{"id":"796239737848352769","questionId":"796239736808165377","content":" Economic feasibility","answer":0,"chooseValue":"D"}],"userAnswer":null,"userChooseItem":null,"answerCorrect":null,"userCollect":null},{"id":"796239784287686657","title":"<p><strong>请作答第<span style=\"color: red\">5</span>个空。</strong></p>System analysis is traditionally done top-down using structured analysis based on(71).Object-oriented analysis focuses on creation of models.The three types of the analysis model are(72).There are two substages of object-oriented analysis.(73)focuses on real-world things whose semantics the application captures.The object constructed in the requirement analysis shows the(74)of the real-world system and organizes it into workable pieces.(75)addresses the computer aspects of the application that are visible to users.The objects are those which can be expected to vary from time to time quite rapidly.","analyze":"传统的系统分析以功能分解为基础，利用结构化分析自顶向下完成。面向对象分析关注于模型的创建。该分析模型有三种类型：类模型、交互模型和状态模型。面向对象分析有两个子阶段。领域分析侧重于现实世界中那些语义被应用程序获取的事物。在需求分析中所构造的对象说明了现实世界系统的静态结构并将其组织为可用的片段。应用分析处理应用系统中用户可见的计算机问题。所分析的对象可能会被预计时不时地发生较快的变化。","multi":0,"questionType":1,"answer":"C","chooseItem":["796239785214627841"],"itemList":[{"id":"796239785189462017","questionId":"796239784287686657","content":" Program analysis","answer":0,"chooseValue":"A"},{"id":"796239785202044929","questionId":"796239784287686657","content":" Function requirement","answer":0,"chooseValue":"B"},{"id":"796239785214627841","questionId":"796239784287686657","content":" Application analysis","answer":1,"chooseValue":"C"},{"id":"796239785223016449","questionId":"796239784287686657","content":" Physical model","answer":0,"chooseValue":"D"}],"userAnswer":null,"userChooseItem":null,"answerCorrect":null,"userCollect":null},{"id":"796239681258803201","title":"<p><strong>请作答第<span style=\"color: red\">1</span>个空。</strong></p>A requirement is simply a statement of what the system must do or what characteristics it needs to have. Requirements written from the perspective of user and focus on user needs are called __(71)__. Requirements written from the developer's perspective and describe how the system will be implemented are called __(72)__. Requirements evolve from detailed statemens of business capabilities that a system should have to detailed statements of the technical way in whick the capabilities will be implemented in the new system. Requirements can be either functional or nofunctional in nature. For example, during the analysis phase of travel vehicles sales system, the system that must have the ability to search for available inventory is __(73)__. The requirement that the system should be able to work on any Web browser belongs to __(74)__. That customer personal information is protected in compliance with the Data Protection Act is a requirement of __(75)__.","analyze":"简单说需求就是关于系统必须做什么或需要有哪些特点的陈述。从用户角度所撰写的需求主要关注用户的需要，称为业务需求。从开发者角度所撰写的需求主要描述系统如何被实现，称为系统需求。需求从一个系统应有业务功能的详细陈述演变到新系统中实现这些功能中所采用技术途径的详细陈述。需求本身可以是功能性或非功能性的。例如，在旅行车销售系统的分析阶段，系统必须能够搜索现有的库存是一种功能性需求。系统应该能够适应任何Web浏览器的需求属于操作需求。客户个人信息应依照Data Protection Act予以保护则是文化和政治方面的需求。","multi":0,"questionType":1,"answer":"B","chooseItem":["796239682282213377"],"itemList":[{"id":"796239682248658945","questionId":"796239681258803201","content":" operational requirements","answer":0,"chooseValue":"A"},{"id":"796239682282213377","questionId":"796239681258803201","content":" business requirements","answer":1,"chooseValue":"B"},{"id":"796239682311573505","questionId":"796239681258803201","content":" technical requirements","answer":0,"chooseValue":"C"},{"id":"796239682345127937","questionId":"796239681258803201","content":" system requirements","answer":0,"chooseValue":"D"}],"userAnswer":null,"userChooseItem":null,"answerCorrect":null,"userCollect":null},{"id":"796239793146056705","title":"<p><strong>请作答第<span style=\"color: red\">3</span>个空。</strong></p>The analysis phase answers the questions of who will use the system, what the system will do, and where and when it will be used. During this phase, the project team investigates any current system, identifies (71)，and develops&nbsp;a concept for the new system. This phase has tbree steps: first, (72) is developed to guide the project team's efforts. It usually includes an analysis of the current system and its problems, and the ways to design a new system. The next step is (73) .The analysis of this information - in conjunction with input from the project sponsor and many other people - leads to the development of a concept for&nbsp;a new system. The system concept is then used as a basis to develop a set of business analysis models that describes how the business will operate if the new system were developed. The set of models typically includes models that represent the (74) necessary to support the underlying business process. Last, the analyses, system concepts, and models are combined into a document called the (75) , which is presented to the project sponsor and other key decision makers that decide whether the project should continue to move forward.","analyze":"分析阶段回答谁将使用该系统、系统能做什么及系统在何时何地使用的问题。在该阶段，项目组调研当前系统、识别改进机会并开发出一个新系统的概念。这个阶段分为三个步骤：首先，开发一个分析策略来指导项目组工作。这些分析策略通常包括了当前系统及其问题的分析和设计新系统的方法。下一步是需求收集。对这些信息（汇同系统发起人和很多其他人员的输入）的分析会导致开发出一个新系统的概念。系统概念作为开发一组业务分析模型的基础，这些模型描述了新系统开发完成后企业如何运作。这组模型通常包含那些表示数据和过程的模型，这些数据和过程是支持底层业务过程所必需的。最后，这些分析、系统概念和模型合并到一个称为系统建议书的文档中，将被提交给项目组发起人和其他决定项目是否继续执行的主要决策人员。","multi":0,"questionType":1,"answer":"D","chooseItem":["796239794148495361"],"itemList":[{"id":"796239794093969409","questionId":"796239793146056705","content":" project scope definition","answer":0,"chooseValue":"A"},{"id":"796239794110746625","questionId":"796239793146056705","content":" problems analysis","answer":0,"chooseValue":"B"},{"id":"796239794127523841","questionId":"796239793146056705","content":" decision analysis","answer":0,"chooseValue":"C"},{"id":"796239794148495361","questionId":"796239793146056705","content":" requirements gathering","answer":1,"chooseValue":"D"}],"userAnswer":null,"userChooseItem":null,"answerCorrect":null,"userCollect":null},{"id":"796239819201073153","title":"<p><strong>请作答第<span style=\"color: red\">3</span>个空。</strong></p>The traditional model for systems development was that an IT department used (71)which is a process-centered technique, and consulted users only when their input or approval was needed.Compared with traditional methods, many companies find that JAD allows key users to participate effectively in the (72).When properly used, JAD can result in a more accurate statement of system requirements, a better understanding of common goals, and a stronger commitment to the success of the new system. RAD is a team-based technique that speeds up information systems development and produces a functioning information system. While the end product of JAD is a(an) (73),the end product of RAD is the (74).The RAD model consists of four phases. During the (75),users interact with systems analysts and develop models and prototypes that represent all system processes, outputs, and inputs.","analyze":"系统开发的传统模式是IT部门使用一种以过程为中心的结构化分析技术，只有当需要用户输入或认可的时候才与用户讨论。与传统方法相比，许多公司发现JAD能让主要用户有效地参与到需求建模过程中。如果使用得当，JAD能够产生更为准确的系统需求陈述，更好地理解共同目标和对于新系统取得成功更强有力的承诺。RAD是一种团队开发技术，能够加快信息系统的开发并生产出正常运作的信息系统。JAD的最终产品是一个需求模型，而RAD的最终产品是新的信息系统。RAD模型包括4个阶段。在用户设计阶段，用户与系统分析员交互，开发模型和原型以表示系统所有的加工、输出和输入。","multi":0,"questionType":1,"answer":"C","chooseItem":["796239820157374465"],"itemList":[{"id":"796239820111237121","questionId":"796239819201073153","content":" data flow diagram","answer":0,"chooseValue":"A"},{"id":"796239820136402945","questionId":"796239819201073153","content":" entity relationship model","answer":0,"chooseValue":"B"},{"id":"796239820157374465","questionId":"796239819201073153","content":" requirements model","answer":1,"chooseValue":"C"},{"id":"796239820174151681","questionId":"796239819201073153","content":" object model","answer":0,"chooseValue":"D"}],"userAnswer":null,"userChooseItem":null,"answerCorrect":null,"userCollect":null},{"id":"796239743015735297","title":"<p><strong>请作答第<span style=\"color: red\">5</span>个空。</strong></p>Feasibility should be measured throughout the life cycle of system development. The scope and complexity of an apparently feasible project can change after the initial problems and opportunities are fully analyzed or after the system has been designed. Thus, a project that is feasible at one point may become infeasible later. The first feasibility analysis is conducted during the (71) . The (72) represents a major feasibility analysis activity since it charts one of many possible implementations as the target for systems design. (73) is a measure of how well the solution will work in the organization. It is also a measure of how people feel about the system. When it is determined in the later stages of the system life cycle, (74) is often performed with a working prototype of the proposed system. This is a test of the system’s user interfaces and is measured in how easy they are to learn and to use and how they support the desired productivity levels of the users. Economic feasibility has been defined as a cost-benefit analysis. The (75) technique is a simple and popular method for determining if and when an investment will pay for itself.","analyze":"可行性的判定贯穿于系统幵发的生命周期。一个明显可行的项目，在全面分析了初始问题和机会或系统设计后，其范围和复杂性会发生变化。因此，某一时刻可行的项目在此后可能会变得不可行。第一次可行性分析在初始调研阶段进行。由于要绘制多个可能的实现方案之一作为系统设计的目标，决策分析阶段表示一个主要的可行性分析活动。 操作可行性是对解决方案在企业中工作效果的度量，它也是衡量人们对于系统的感受。当它在系统生命周期后面的阶段被确定后，经常会用一个建议系统的工作原型进行可用性分析。这是对系统用户界面的一种测试，它通过系统如何易于学习和使用及系统如何支持用户所期望的生产力水平进行衡量。偿还分析技术是一种简单流行的方法用于确定是否及何时将收回成本。","multi":0,"questionType":1,"answer":"A","chooseItem":["796239743930093569"],"itemList":[{"id":"796239743930093569","questionId":"796239743015735297","content":" payback analysis","answer":1,"chooseValue":"A"},{"id":"796239743959453697","questionId":"796239743015735297","content":" retum-on-investment analysis","answer":0,"chooseValue":"B"},{"id":"796239743984619521","questionId":"796239743015735297","content":" present value","answer":0,"chooseValue":"C"},{"id":"796239744005591041","questionId":"796239743015735297","content":" time value of money","answer":0,"chooseValue":"D"}],"userAnswer":null,"userChooseItem":null,"answerCorrect":null,"userCollect":null},{"id":"796239752058654721","title":"<p><strong>请作答第<span style=\"color: red\">3</span>个空。</strong></p>Many of the activities performed during the preliminary investigation are still being conducted in (71).but in much greater depth than before. During this phase, the analyst must become fully aware of the(72)and must develop enough knowledge about the(73)and the existing systems to. enable an effective solution to be proposed and implemented. Besides the(74)for process and data of current system,the deliverable from this phase also includes the(75)for the proposed system.","analyze":"初始调查阶段的许多活动仍然会在分析阶段进行，但会比前面更为深入。在这个阶段，分析师必须认识到根本性问题并且必须获取到足够的关于业务环境和现有系统的知识，以便提出和实现一种有效的解决方案。除了现有系统过程与数据的逻辑模型外，这一阶段的交付品还包括了所建议系统的形式化需求定义。","multi":0,"questionType":1,"answer":"D","chooseItem":["796239753061093377"],"itemList":[{"id":"796239752968818689","questionId":"796239752058654721","content":" hardware environment","answer":0,"chooseValue":"A"},{"id":"796239752998178817","questionId":"796239752058654721","content":" testing environment","answer":0,"chooseValue":"B"},{"id":"796239753027538945","questionId":"796239752058654721","content":" software environment","answer":0,"chooseValue":"C"},{"id":"796239753061093377","questionId":"796239752058654721","content":" business environment","answer":1,"chooseValue":"D"}],"userAnswer":null,"userChooseItem":null,"answerCorrect":null,"userCollect":null},{"id":"796239825106653185","title":"<p><strong>请作答第<span style=\"color: red\">5</span>个空。</strong></p>The traditional model for systems development was that an IT department used (71)which is a process-centered technique, and consulted users only when their input or approval was needed.Compared with traditional methods, many companies find that JAD allows key users to participate effectively in the (72).When properly used, JAD can result in a more accurate statement of system requirements, a better understanding of common goals, and a stronger commitment to the success of the new system. RAD is a team-based technique that speeds up information systems development and produces a functioning information system. While the end product of JAD is a(an) (73),the end product of RAD is the (74).The RAD model consists of four phases. During the (75),users interact with systems analysts and develop models and prototypes that represent all system processes, outputs, and inputs.","analyze":"系统开发的传统模式是IT部门使用一种以过程为中心的结构化分析技术，只有当需要用户输入或认可的时候才与用户讨论。与传统方法相比，许多公司发现JAD能让主要用户有效地参与到需求建模过程中。如果使用得当，JAD能够产生更为准确的系统需求陈述，更好地理解共同目标和对于新系统取得成功更强有力的承诺。RAD是一种团队开发技术，能够加快信息系统的开发并生产出正常运作的信息系统。JAD的最终产品是一个需求模型，而RAD的最终产品是新的信息系统。RAD模型包括4个阶段。在用户设计阶段，用户与系统分析员交互，开发模型和原型以表示系统所有的加工、输出和输入。","multi":0,"questionType":1,"answer":"B","chooseItem":["796239826067148801"],"itemList":[{"id":"796239826037788673","questionId":"796239825106653185","content":" requirements planning phase","answer":0,"chooseValue":"A"},{"id":"796239826067148801","questionId":"796239825106653185","content":" user design phase","answer":1,"chooseValue":"B"},{"id":"796239826100703233","questionId":"796239825106653185","content":" construction phase","answer":0,"chooseValue":"C"},{"id":"796239826113286145","questionId":"796239825106653185","content":" cutover phase","answer":0,"chooseValue":"D"}],"userAnswer":null,"userChooseItem":null,"answerCorrect":null,"userCollect":null},{"id":"796239730739007489","title":"<p><strong>请作答第<span style=\"color: red\">1</span>个空。</strong></p>Feasibility should be measured throughout the life cycle of system development. The scope and complexity of an apparently feasible project can change after the initial problems and opportunities are fully analyzed or after the system has been designed. Thus, a project that is feasible at one point may become infeasible later. The first feasibility analysis is conducted during the (71) . The (72) represents a major feasibility analysis activity since it charts one of many possible implementations as the target for systems design. (73) is a measure of how well the solution will work in the organization. It is also a measure of how people feel about the system. When it is determined in the later stages of the system life cycle, (74) is often performed with a working prototype of the proposed system. This is a test of the system’s user interfaces and is measured in how easy they are to learn and to use and how they support the desired productivity levels of the users. Economic feasibility has been defined as a cost-benefit analysis. The (75) technique is a simple and popular method for determining if and when an investment will pay for itself.","analyze":"可行性的判定贯穿于系统幵发的生命周期。一个明显可行的项目，在全面分析了初始问题和机会或系统设计后，其范围和复杂性会发生变化。因此，某一时刻可行的项目在此后可能会变得不可行。第一次可行性分析在初始调研阶段进行。由于要绘制多个可能的实现方案之一作为系统设计的目标，决策分析阶段表示一个主要的可行性分析活动。 操作可行性是对解决方案在企业中工作效果的度量，它也是衡量人们对于系统的感受。当它在系统生命周期后面的阶段被确定后，经常会用一个建议系统的工作原型进行可用性分析。这是对系统用户界面的一种测试，它通过系统如何易于学习和使用及系统如何支持用户所期望的生产力水平进行衡量。偿还分析技术是一种简单流行的方法用于确定是否及何时将收回成本。","multi":0,"questionType":1,"answer":"B","chooseItem":["796239731691114497"],"itemList":[{"id":"796239731657560065","questionId":"796239730739007489","content":" problem analysis phase","answer":0,"chooseValue":"A"},{"id":"796239731691114497","questionId":"796239730739007489","content":" preliminary investigation phase","answer":1,"chooseValue":"B"},{"id":"796239731728863233","questionId":"796239730739007489","content":" requirements analysis phase","answer":0,"chooseValue":"C"},{"id":"796239731754029057","questionId":"796239730739007489","content":" decision analysis phase","answer":0,"chooseValue":"D"}],"userAnswer":null,"userChooseItem":null,"answerCorrect":null,"userCollect":null},{"id":"796239666465492993","title":"<p><strong>请作答第<span style=\"color: red\">1</span>个空。</strong></p>A requirement is simply a statement of what the system must do or what characteristics it needs to have. Requirements evolve from broad statements of overall （71） from the system to detailed statements of the business capabilities that a system should support to detailed technical statements of the way in which the capabilities will be implemented in the new system. （72） focus on describing how to create the software product that will be produced from the project Nonfunctional requirements are primarily used in the design phase when decisions are made about the user interface, the hardware and software, and the system's underlying architecture. The system's physical and technical environments would be considered （73）. The speed, capacity, and reliability of the system belong to （74）. （75） describes that who has authorized access to the system under what circumstances.","analyze":"需求只是陈述了系统必须做什么或者系统需要有什么特性，需求来自于从系统总体业务需要的广泛陈述到系统所支持业务能力的详细陈述，再到新系统能力实现中所采用方法的详细技术陈述。功能性需求致力于描述如何创建将在项目中产生的软件产品。非功能性需求主要在设计阶段中做出关于用户界面、硬件和软件，以及系统底层架构的决策时使用。系统的物理和技术环境将被看作一种操作需求。系统的速度、能力和可靠性属于性能需求。安全性需求描述了谁在什么情况下具有访问系统的权限。","multi":0,"questionType":1,"answer":"A","chooseItem":["796239667400822785"],"itemList":[{"id":"796239667400822785","questionId":"796239666465492993","content":" business needs","answer":1,"chooseValue":"A"},{"id":"796239667417600001","questionId":"796239666465492993","content":" operation processes","answer":0,"chooseValue":"B"},{"id":"796239667434377217","questionId":"796239666465492993","content":" technical specification","answer":0,"chooseValue":"C"},{"id":"796239667451154433","questionId":"796239666465492993","content":" function components","answer":0,"chooseValue":"D"}],"userAnswer":null,"userChooseItem":null,"answerCorrect":null,"userCollect":null},{"id":"796239778235305985","title":"<p><strong>请作答第<span style=\"color: red\">3</span>个空。</strong></p>System analysis is traditionally done top-down using structured analysis based on(71).Object-oriented analysis focuses on creation of models.The three types of the analysis model are(72).There are two substages of object-oriented analysis.(73)focuses on real-world things whose semantics the application captures.The object constructed in the requirement analysis shows the(74)of the real-world system and organizes it into workable pieces.(75)addresses the computer aspects of the application that are visible to users.The objects are those which can be expected to vary from time to time quite rapidly.","analyze":"传统的系统分析以功能分解为基础，利用结构化分析自顶向下完成。面向对象分析关注于模型的创建。该分析模型有三种类型：类模型、交互模型和状态模型。面向对象分析有两个子阶段。领域分析侧重于现实世界中那些语义被应用程序获取的事物。在需求分析中所构造的对象说明了现实世界系统的静态结构并将其组织为可用的片段。应用分析处理应用系统中用户可见的计算机问题。所分析的对象可能会被预计时不时地发生较快的变化。","multi":0,"questionType":1,"answer":"D","chooseItem":["796239779254521857"],"itemList":[{"id":"796239779158052865","questionId":"796239778235305985","content":" Static analysis","answer":0,"chooseValue":"A"},{"id":"796239779191607297","questionId":"796239778235305985","content":" Semantic analysis","answer":0,"chooseValue":"B"},{"id":"796239779225161729","questionId":"796239778235305985","content":" Scope analysis","answer":0,"chooseValue":"C"},{"id":"796239779254521857","questionId":"796239778235305985","content":" Domain analysis","answer":1,"chooseValue":"D"}],"userAnswer":null,"userChooseItem":null,"answerCorrect":null,"userCollect":null},{"id":"796239775148298241","title":"<p><strong>请作答第<span style=\"color: red\">2</span>个空。</strong></p>System analysis is traditionally done top-down using structured analysis based on(71).Object-oriented analysis focuses on creation of models.The three types of the analysis model are(72).There are two substages of object-oriented analysis.(73)focuses on real-world things whose semantics the application captures.The object constructed in the requirement analysis shows the(74)of the real-world system and organizes it into workable pieces.(75)addresses the computer aspects of the application that are visible to users.The objects are those which can be expected to vary from time to time quite rapidly.","analyze":"传统的系统分析以功能分解为基础，利用结构化分析自顶向下完成。面向对象分析关注于模型的创建。该分析模型有三种类型：类模型、交互模型和状态模型。面向对象分析有两个子阶段。领域分析侧重于现实世界中那些语义被应用程序获取的事物。在需求分析中所构造的对象说明了现实世界系统的静态结构并将其组织为可用的片段。应用分析处理应用系统中用户可见的计算机问题。所分析的对象可能会被预计时不时地发生较快的变化。","multi":0,"questionType":1,"answer":"B","chooseItem":["796239776154931201"],"itemList":[{"id":"796239776112988161","questionId":"796239775148298241","content":" function model,class model and state model","answer":0,"chooseValue":"A"},{"id":"796239776154931201","questionId":"796239775148298241","content":" class model,interaction model and state model","answer":1,"chooseValue":"B"},{"id":"796239776201068545","questionId":"796239775148298241","content":" class model,interaction model and sequence model","answer":0,"chooseValue":"C"},{"id":"796239776247205889","questionId":"796239775148298241","content":" function model,interaction model and state model","answer":0,"chooseValue":"D"}],"userAnswer":null,"userChooseItem":null,"answerCorrect":null,"userCollect":null},{"id":"796239672354295809","title":"<p><strong>请作答第<span style=\"color: red\">3</span>个空。</strong></p>A requirement is simply a statement of what the system must do or what characteristics it needs to have. Requirements evolve from broad statements of overall （71） from the system to detailed statements of the business capabilities that a system should support to detailed technical statements of the way in which the capabilities will be implemented in the new system. （72） focus on describing how to create the software product that will be produced from the project Nonfunctional requirements are primarily used in the design phase when decisions are made about the user interface, the hardware and software, and the system's underlying architecture. The system's physical and technical environments would be considered （73）. The speed, capacity, and reliability of the system belong to （74）. （75） describes that who has authorized access to the system under what circumstances.","analyze":"需求只是陈述了系统必须做什么或者系统需要有什么特性，需求来自于从系统总体业务需要的广泛陈述到系统所支持业务能力的详细陈述，再到新系统能力实现中所采用方法的详细技术陈述。功能性需求致力于描述如何创建将在项目中产生的软件产品。非功能性需求主要在设计阶段中做出关于用户界面、硬件和软件，以及系统底层架构的决策时使用。系统的物理和技术环境将被看作一种操作需求。系统的速度、能力和可靠性属于性能需求。安全性需求描述了谁在什么情况下具有访问系统的权限。","multi":0,"questionType":1,"answer":"C","chooseItem":["796239673390288897"],"itemList":[{"id":"796239673327374337","questionId":"796239672354295809","content":" a functional requirement","answer":0,"chooseValue":"A"},{"id":"796239673365123073","questionId":"796239672354295809","content":" a technical requirement","answer":0,"chooseValue":"B"},{"id":"796239673390288897","questionId":"796239672354295809","content":" an operational requirement","answer":1,"chooseValue":"C"},{"id":"796239673419649025","questionId":"796239672354295809","content":" a service requirenient","answer":0,"chooseValue":"D"}],"userAnswer":null,"userChooseItem":null,"answerCorrect":null,"userCollect":null},{"id":"796239745989496833","title":"<p><strong>请作答第<span style=\"color: red\">1</span>个空。</strong></p>Many of the activities performed during the preliminary investigation are still being conducted in (71).but in much greater depth than before. During this phase, the analyst must become fully aware of the(72)and must develop enough knowledge about the(73)and the existing systems to. enable an effective solution to be proposed and implemented. Besides the(74)for process and data of current system,the deliverable from this phase also includes the(75)for the proposed system.","analyze":"初始调查阶段的许多活动仍然会在分析阶段进行，但会比前面更为深入。在这个阶段，分析师必须认识到根本性问题并且必须获取到足够的关于业务环境和现有系统的知识，以便提出和实现一种有效的解决方案。除了现有系统过程与数据的逻辑模型外，这一阶段的交付品还包括了所建议系统的形式化需求定义。","multi":0,"questionType":1,"answer":"A","chooseItem":["796239746929020929"],"itemList":[{"id":"796239746929020929","questionId":"796239745989496833","content":" analysis phase","answer":1,"chooseValue":"A"},{"id":"796239746975158273","questionId":"796239745989496833","content":" design phase","answer":0,"chooseValue":"B"},{"id":"796239747021295617","questionId":"796239745989496833","content":" implementation phase","answer":0,"chooseValue":"C"},{"id":"796239747067432961","questionId":"796239745989496833","content":" maintenance phase","answer":0,"chooseValue":"D"}],"userAnswer":null,"userChooseItem":null,"answerCorrect":null,"userCollect":null},{"id":"796239669384728577","title":"<p><strong>请作答第<span style=\"color: red\">2</span>个空。</strong></p>A requirement is simply a statement of what the system must do or what characteristics it needs to have. Requirements evolve from broad statements of overall （71） from the system to detailed statements of the business capabilities that a system should support to detailed technical statements of the way in which the capabilities will be implemented in the new system. （72） focus on describing how to create the software product that will be produced from the project Nonfunctional requirements are primarily used in the design phase when decisions are made about the user interface, the hardware and software, and the system's underlying architecture. The system's physical and technical environments would be considered （73）. The speed, capacity, and reliability of the system belong to （74）. （75） describes that who has authorized access to the system under what circumstances.","analyze":"需求只是陈述了系统必须做什么或者系统需要有什么特性，需求来自于从系统总体业务需要的广泛陈述到系统所支持业务能力的详细陈述，再到新系统能力实现中所采用方法的详细技术陈述。功能性需求致力于描述如何创建将在项目中产生的软件产品。非功能性需求主要在设计阶段中做出关于用户界面、硬件和软件，以及系统底层架构的决策时使用。系统的物理和技术环境将被看作一种操作需求。系统的速度、能力和可靠性属于性能需求。安全性需求描述了谁在什么情况下具有访问系统的权限。","multi":0,"questionType":1,"answer":"C","chooseItem":["796239670382972929"],"itemList":[{"id":"796239670345224193","questionId":"796239669384728577","content":" User requirements","answer":0,"chooseValue":"A"},{"id":"796239670362001409","questionId":"796239669384728577","content":" Business requirements","answer":0,"chooseValue":"B"},{"id":"796239670382972929","questionId":"796239669384728577","content":" Function requirements","answer":1,"chooseValue":"C"},{"id":"796239670399750145","questionId":"796239669384728577","content":" System requirements ","answer":0,"chooseValue":"D"}],"userAnswer":null,"userChooseItem":null,"answerCorrect":null,"userCollect":null},{"id":"796239678293430273","title":"<p><strong>请作答第<span style=\"color: red\">5</span>个空。</strong></p>A requirement is simply a statement of what the system must do or what characteristics it needs to have. Requirements evolve from broad statements of overall （71） from the system to detailed statements of the business capabilities that a system should support to detailed technical statements of the way in which the capabilities will be implemented in the new system. （72） focus on describing how to create the software product that will be produced from the project Nonfunctional requirements are primarily used in the design phase when decisions are made about the user interface, the hardware and software, and the system's underlying architecture. The system's physical and technical environments would be considered （73）. The speed, capacity, and reliability of the system belong to （74）. （75） describes that who has authorized access to the system under what circumstances.","analyze":"需求只是陈述了系统必须做什么或者系统需要有什么特性，需求来自于从系统总体业务需要的广泛陈述到系统所支持业务能力的详细陈述，再到新系统能力实现中所采用方法的详细技术陈述。功能性需求致力于描述如何创建将在项目中产生的软件产品。非功能性需求主要在设计阶段中做出关于用户界面、硬件和软件，以及系统底层架构的决策时使用。系统的物理和技术环境将被看作一种操作需求。系统的速度、能力和可靠性属于性能需求。安全性需求描述了谁在什么情况下具有访问系统的权限。","multi":0,"questionType":1,"answer":"D","chooseItem":["796239679274897409"],"itemList":[{"id":"796239679195205633","questionId":"796239678293430273","content":" System constraint","answer":0,"chooseValue":"A"},{"id":"796239679224565761","questionId":"796239678293430273","content":" Cultural requirement","answer":0,"chooseValue":"B"},{"id":"796239679258120193","questionId":"796239678293430273","content":" Control requirement","answer":0,"chooseValue":"C"},{"id":"796239679274897409","questionId":"796239678293430273","content":" Security requirement","answer":1,"chooseValue":"D"}],"userAnswer":null,"userChooseItem":null,"answerCorrect":null,"userCollect":null},{"id":"796239790163906561","title":"<p><strong>请作答第<span style=\"color: red\">2</span>个空。</strong></p>The analysis phase answers the questions of who will use the system, what the system will do, and where and when it will be used. During this phase, the project team investigates any current system, identifies (71)，and develops&nbsp;a concept for the new system. This phase has tbree steps: first, (72) is developed to guide the project team's efforts. It usually includes an analysis of the current system and its problems, and the ways to design a new system. The next step is (73) .The analysis of this information - in conjunction with input from the project sponsor and many other people - leads to the development of a concept for&nbsp;a new system. The system concept is then used as a basis to develop a set of business analysis models that describes how the business will operate if the new system were developed. The set of models typically includes models that represent the (74) necessary to support the underlying business process. Last, the analyses, system concepts, and models are combined into a document called the (75) , which is presented to the project sponsor and other key decision makers that decide whether the project should continue to move forward.","analyze":"分析阶段回答谁将使用该系统、系统能做什么及系统在何时何地使用的问题。在该阶段，项目组调研当前系统、识别改进机会并开发出一个新系统的概念。这个阶段分为三个步骤：首先，开发一个分析策略来指导项目组工作。这些分析策略通常包括了当前系统及其问题的分析和设计新系统的方法。下一步是需求收集。对这些信息（汇同系统发起人和很多其他人员的输入）的分析会导致开发出一个新系统的概念。系统概念作为开发一组业务分析模型的基础，这些模型描述了新系统开发完成后企业如何运作。这组模型通常包含那些表示数据和过程的模型，这些数据和过程是支持底层业务过程所必需的。最后，这些分析、系统概念和模型合并到一个称为系统建议书的文档中，将被提交给项目组发起人和其他决定项目是否继续执行的主要决策人员。","multi":0,"questionType":1,"answer":"B","chooseItem":["796239791074070529"],"itemList":[{"id":"796239791057293313","questionId":"796239790163906561","content":" a user manual","answer":0,"chooseValue":"A"},{"id":"796239791074070529","questionId":"796239790163906561","content":" an analysis strategy","answer":1,"chooseValue":"B"},{"id":"796239791090847745","questionId":"796239790163906561","content":" an analysis use case","answer":0,"chooseValue":"C"},{"id":"796239791103430657","questionId":"796239790163906561","content":" a design user case","answer":0,"chooseValue":"D"}],"userAnswer":null,"userChooseItem":null,"answerCorrect":null,"userCollect":null},{"id":"796239687353126913","title":"<p><strong>请作答第<span style=\"color: red\">3</span>个空。</strong></p>A requirement is simply a statement of what the system must do or what characteristics it needs to have. Requirements written from the perspective of user and focus on user needs are called __(71)__. Requirements written from the developer's perspective and describe how the system will be implemented are called __(72)__. Requirements evolve from detailed statemens of business capabilities that a system should have to detailed statements of the technical way in whick the capabilities will be implemented in the new system. Requirements can be either functional or nofunctional in nature. For example, during the analysis phase of travel vehicles sales system, the system that must have the ability to search for available inventory is __(73)__. The requirement that the system should be able to work on any Web browser belongs to __(74)__. That customer personal information is protected in compliance with the Data Protection Act is a requirement of __(75)__.","analyze":"简单说需求就是关于系统必须做什么或需要有哪些特点的陈述。从用户角度所撰写的需求主要关注用户的需要，称为业务需求。从开发者角度所撰写的需求主要描述系统如何被实现，称为系统需求。需求从一个系统应有业务功能的详细陈述演变到新系统中实现这些功能中所采用技术途径的详细陈述。需求本身可以是功能性或非功能性的。例如，在旅行车销售系统的分析阶段，系统必须能够搜索现有的库存是一种功能性需求。系统应该能够适应任何Web浏览器的需求属于操作需求。客户个人信息应依照Data Protection Act予以保护则是文化和政治方面的需求。","multi":0,"questionType":1,"answer":"A","chooseItem":["796239688313622529"],"itemList":[{"id":"796239688313622529","questionId":"796239687353126913","content":" a functional requirements","answer":1,"chooseValue":"A"},{"id":"796239688334594049","questionId":"796239687353126913","content":" a technical requirements","answer":0,"chooseValue":"B"},{"id":"796239688355565569","questionId":"796239687353126913","content":" an operational requirements","answer":0,"chooseValue":"C"},{"id":"796239688376537089","questionId":"796239687353126913","content":" a service requirements","answer":0,"chooseValue":"D"}],"userAnswer":null,"userChooseItem":null,"answerCorrect":null,"userCollect":null},{"id":"796235455346528257","title":"<p><strong>请作答第<span style=\"color: red\">1</span>个空。</strong></p>A variety of tools is available to help the analyst to discover the users' true needs. These tools are grouped into three broad techniques that are based on the degree of change anticipated in the to-be system - Business process（71） is used when the basic business Requirements outlined in the system request focus on employing computer technology in some aspect of the business process. Two popular activities used in the technique are（72）. Business process （73）means that the basic business requirements target moderate changes to the organization' s operations. （74）are three popular activities in the technique. Business process （75）means changing the current way of doing business and making major changes to take advantage of new ideas and new technology.","analyze":"多种工具用来帮助分析人员发现用户的真实需求，这些工具按照目标系统设想的变化程度可以分为三类广义技术。当系统需求中描述的基本业务需求关注于将计算机技术运用于业务流程的某些方面时，使用业务流程自动化，该技术中使用的两种流行活动是问题分析和因果分析。业务流程改进意味着基本业务需求目标会让组织的运作有适度改变，持续期分析、作业成本方法和非正式基准是该技术中流行的5项活动。业务流程再造意味着要改变当前执行业务的方式和为了采用新理念和新技术的优势而进行重大改变。","multi":0,"questionType":1,"answer":"A","chooseItem":["796235456353161217"],"itemList":[{"id":"796235456353161217","questionId":"796235455346528257","content":" automation","answer":1,"chooseValue":"A"},{"id":"796235456382521345","questionId":"796235455346528257","content":" modeling","answer":0,"chooseValue":"B"},{"id":"796235456411881473","questionId":"796235455346528257","content":" improvement","answer":0,"chooseValue":"C"},{"id":"796235456437047297","questionId":"796235455346528257","content":" reengineering","answer":0,"chooseValue":"D"}],"userAnswer":null,"userChooseItem":null,"answerCorrect":null,"userCollect":null},{"id":"796235458429341697","title":"<p><strong>请作答第<span style=\"color: red\">2</span>个空。</strong></p>A variety of tools is available to help the analyst to discover the users' true needs. These tools are grouped into three broad techniques that are based on the degree of change anticipated in the to-be system - Business process（71） is used when the basic business Requirements outlined in the system request focus on employing computer technology in some aspect of the business process. Two popular activities used in the technique are（72）. Business process （73）means that the basic business requirements target moderate changes to the organization' s operations. （74）are three popular activities in the technique. Business process （75）means changing the current way of doing business and making major changes to take advantage of new ideas and new technology.","analyze":"多种工具用来帮助分析人员发现用户的真实需求，这些工具按照目标系统设想的变化程度可以分为三类广义技术。当系统需求中描述的基本业务需求关注于将计算机技术运用于业务流程的某些方面时，使用业务流程自动化，该技术中使用的两种流行活动是问题分析和因果分析。业务流程改进意味着基本业务需求目标会让组织的运作有适度改变，持续期分析、作业成本方法和非正式基准是该技术中流行的5项活动。业务流程再造意味着要改变当前执行业务的方式和为了采用新理念和新技术的优势而进行重大改变。","multi":0,"questionType":1,"answer":"B","chooseItem":["796235459435974657"],"itemList":[{"id":"796235459406614529","questionId":"796235458429341697","content":" duration analysis and outcome analysis","answer":0,"chooseValue":"A"},{"id":"796235459435974657","questionId":"796235458429341697","content":" problem analysis and root cause analysis","answer":1,"chooseValue":"B"},{"id":"796235459461140481","questionId":"796235458429341697","content":" technology analysis and activity elimination","answer":0,"chooseValue":"C"},{"id":"796235459486306305","questionId":"796235458429341697","content":" activity-based costing and informal benchmarking","answer":0,"chooseValue":"D"}],"userAnswer":null,"userChooseItem":null,"answerCorrect":null,"userCollect":null},{"id":"796235462074191873","title":"<p><strong>请作答第<span style=\"color: red\">3</span>个空。</strong></p>A variety of tools is available to help the analyst to discover the users' true needs. These tools are grouped into three broad techniques that are based on the degree of change anticipated in the to-be system - Business process（71） is used when the basic business Requirements outlined in the system request focus on employing computer technology in some aspect of the business process. Two popular activities used in the technique are（72）. Business process （73）means that the basic business requirements target moderate changes to the organization' s operations. （74）are three popular activities in the technique. Business process （75）means changing the current way of doing business and making major changes to take advantage of new ideas and new technology.","analyze":"多种工具用来帮助分析人员发现用户的真实需求，这些工具按照目标系统设想的变化程度可以分为三类广义技术。当系统需求中描述的基本业务需求关注于将计算机技术运用于业务流程的某些方面时，使用业务流程自动化，该技术中使用的两种流行活动是问题分析和因果分析。业务流程改进意味着基本业务需求目标会让组织的运作有适度改变，持续期分析、作业成本方法和非正式基准是该技术中流行的5项活动。业务流程再造意味着要改变当前执行业务的方式和为了采用新理念和新技术的优势而进行重大改变。","multi":0,"questionType":1,"answer":"C","chooseItem":["796235463038881793"],"itemList":[{"id":"796235463001133057","questionId":"796235462074191873","content":" automation","answer":0,"chooseValue":"A"},{"id":"796235463022104577","questionId":"796235462074191873","content":" modeling","answer":0,"chooseValue":"B"},{"id":"796235463038881793","questionId":"796235462074191873","content":" improvement","answer":1,"chooseValue":"C"},{"id":"796235463059853313","questionId":"796235462074191873","content":" reengineering","answer":0,"chooseValue":"D"}],"userAnswer":null,"userChooseItem":null,"answerCorrect":null,"userCollect":null},{"id":"796235465177976833","title":"<p><strong>请作答第<span style=\"color: red\">4</span>个空。</strong></p>A variety of tools is available to help the analyst to discover the users' true needs. These tools are grouped into three broad techniques that are based on the degree of change anticipated in the to-be system - Business process（71） is used when the basic business Requirements outlined in the system request focus on employing computer technology in some aspect of the business process. Two popular activities used in the technique are（72）. Business process （73）means that the basic business requirements target moderate changes to the organization' s operations. （74）are three popular activities in the technique. Business process （75）means changing the current way of doing business and making major changes to take advantage of new ideas and new technology.","analyze":"多种工具用来帮助分析人员发现用户的真实需求，这些工具按照目标系统设想的变化程度可以分为三类广义技术。当系统需求中描述的基本业务需求关注于将计算机技术运用于业务流程的某些方面时，使用业务流程自动化，该技术中使用的两种流行活动是问题分析和因果分析。业务流程改进意味着基本业务需求目标会让组织的运作有适度改变，持续期分析、作业成本方法和非正式基准是该技术中流行的5项活动。业务流程再造意味着要改变当前执行业务的方式和为了采用新理念和新技术的优势而进行重大改变。","multi":0,"questionType":1,"answer":"A","chooseItem":["796235466155249665"],"itemList":[{"id":"796235466155249665","questionId":"796235465177976833","content":" Duration analysis, activity-based costing and informal benchmarking","answer":1,"chooseValue":"A"},{"id":"796235466180415489","questionId":"796235465177976833","content":" Outcome analysis, technology analysis and activity elimination","answer":0,"chooseValue":"B"},{"id":"796235466209775617","questionId":"796235465177976833","content":" Problem analysis, root cause analysis and critical path analysis","answer":0,"chooseValue":"C"},{"id":"796235466239135745","questionId":"796235465177976833","content":" Cost-benefit analysis, schedule analysis and risk analysis","answer":0,"chooseValue":"D"}],"userAnswer":null,"userChooseItem":null,"answerCorrect":null,"userCollect":null},{"id":"796235468206264321","title":"<p><strong>请作答第<span style=\"color: red\">5</span>个空。</strong></p>A variety of tools is available to help the analyst to discover the users' true needs. These tools are grouped into three broad techniques that are based on the degree of change anticipated in the to-be system - Business process（71） is used when the basic business Requirements outlined in the system request focus on employing computer technology in some aspect of the business process. Two popular activities used in the technique are（72）. Business process （73）means that the basic business requirements target moderate changes to the organization' s operations. （74）are three popular activities in the technique. Business process （75）means changing the current way of doing business and making major changes to take advantage of new ideas and new technology.","analyze":"多种工具用来帮助分析人员发现用户的真实需求，这些工具按照目标系统设想的变化程度可以分为三类广义技术。当系统需求中描述的基本业务需求关注于将计算机技术运用于业务流程的某些方面时，使用业务流程自动化，该技术中使用的两种流行活动是问题分析和因果分析。业务流程改进意味着基本业务需求目标会让组织的运作有适度改变，持续期分析、作业成本方法和非正式基准是该技术中流行的5项活动。业务流程再造意味着要改变当前执行业务的方式和为了采用新理念和新技术的优势而进行重大改变。","multi":0,"questionType":1,"answer":"D","chooseItem":["796235469212897281"],"itemList":[{"id":"796235469141594113","questionId":"796235468206264321","content":" automation","answer":0,"chooseValue":"A"},{"id":"796235469166759937","questionId":"796235468206264321","content":" modeling","answer":0,"chooseValue":"B"},{"id":"796235469187731457","questionId":"796235468206264321","content":" improvement","answer":0,"chooseValue":"C"},{"id":"796235469212897281","questionId":"796235468206264321","content":" reengineering","answer":1,"chooseValue":"D"}],"userAnswer":null,"userChooseItem":null,"answerCorrect":null,"userCollect":null},{"id":"796234979355938817","title":"<p><strong>请作答第<span style=\"color: red\">1</span>个空。</strong></p>During the systems analysis phase, greater user involvement usually results in better communication, faster development times, and more satisfied users.There are three common team-based approaches that encourage system users to participate actively in various development tasks.1) （71） is a popular fact-finding technique that brings users into the development process as active participants. The end product of the approach is a requirements model.2) （72） is a team-based technique that speeds up information systems development and produces a functioning information system. The approach consists of several phases. The （73） combines elements of the systems planning and systems analysis phases of the SDLC.Users, managers, and IT staff members discuss and agree on business needs, project scope, constraints, and system requirements. During （74）, users interact with systems analysts and develop models and prototypes that represent all system processes, outputs, and inputs.3) （75） attempt to develop a system incrementally by building a series of prototypes and constantly adjusting them to user requirements.","analyze":"在系统分析阶段，参与的用户越多沟通效果越好、开发效率和用户满意度更高。有三种常见的基于团队的方法可以鼓励系统用户积极参与各种幵发任务。1)联合应用程序开发是一种流行的事实发现技术，它使用户主动参与到开发过程中。该方法的最终产品是需求模型。2)快速应用开发是一种基于团队的技术，可加速信息系统开发并生成功能正确的信息系统。该方法包括几个阶段：需求计划阶段将系统开发周期中系统规划与系统分析阶段的要素结合起来。用户、经理和IT员工讨论并商定业务需求、项目范围、约束和系统需求。用户设计阶段，用户与系统分析师进行交互，并开发表示所有系统进程、输出和输入的模型和原型。敏捷方法试图通过构建一系列原型并不断根据用户需求进行调整来逐步开发系统。","multi":0,"questionType":1,"answer":"B","chooseItem":["796234980433874945"],"itemList":[{"id":"796234980404514817","questionId":"796234979355938817","content":" Questionnaires","answer":0,"chooseValue":"A"},{"id":"796234980433874945","questionId":"796234979355938817","content":" Joint application development","answer":1,"chooseValue":"B"},{"id":"796234980454846465","questionId":"796234979355938817","content":" Interviews","answer":0,"chooseValue":"C"},{"id":"796234980475817985","questionId":"796234979355938817","content":" Prototyping","answer":0,"chooseValue":"D"}],"userAnswer":null,"userChooseItem":null,"answerCorrect":null,"userCollect":null},{"id":"796234982472306689","title":"<p><strong>请作答第<span style=\"color: red\">2</span>个空。</strong></p>During the systems analysis phase, greater user involvement usually results in better communication, faster development times, and more satisfied users.There are three common team-based approaches that encourage system users to participate actively in various development tasks.1) （71） is a popular fact-finding technique that brings users into the development process as active participants. The end product of the approach is a requirements model.2) （72） is a team-based technique that speeds up information systems development and produces a functioning information system. The approach consists of several phases. The （73） combines elements of the systems planning and systems analysis phases of the SDLC.Users, managers, and IT staff members discuss and agree on business needs, project scope, constraints, and system requirements. During （74）, users interact with systems analysts and develop models and prototypes that represent all system processes, outputs, and inputs.3) （75） attempt to develop a system incrementally by building a series of prototypes and constantly adjusting them to user requirements.","analyze":"在系统分析阶段，参与的用户越多沟通效果越好、开发效率和用户满意度更高。有三种常见的基于团队的方法可以鼓励系统用户积极参与各种幵发任务。1)联合应用程序开发是一种流行的事实发现技术，它使用户主动参与到开发过程中。该方法的最终产品是需求模型。2)快速应用开发是一种基于团队的技术，可加速信息系统开发并生成功能正确的信息系统。该方法包括几个阶段：需求计划阶段将系统开发周期中系统规划与系统分析阶段的要素结合起来。用户、经理和IT员工讨论并商定业务需求、项目范围、约束和系统需求。用户设计阶段，用户与系统分析师进行交互，并开发表示所有系统进程、输出和输入的模型和原型。敏捷方法试图通过构建一系列原型并不断根据用户需求进行调整来逐步开发系统。","multi":0,"questionType":1,"answer":"C","chooseItem":["796234983520882689"],"itemList":[{"id":"796234983457968129","questionId":"796234982472306689","content":" Object-oriented development","answer":0,"chooseValue":"A"},{"id":"796234983487328257","questionId":"796234982472306689","content":" Model-driven development","answer":0,"chooseValue":"B"},{"id":"796234983520882689","questionId":"796234982472306689","content":" Rapid application development","answer":1,"chooseValue":"C"},{"id":"796234983554437121","questionId":"796234982472306689","content":" Commercial Application package","answer":0,"chooseValue":"D"}],"userAnswer":null,"userChooseItem":null,"answerCorrect":null,"userCollect":null},{"id":"796234985529954305","title":"<p><strong>请作答第<span style=\"color: red\">3</span>个空。</strong></p>During the systems analysis phase, greater user involvement usually results in better communication, faster development times, and more satisfied users.There are three common team-based approaches that encourage system users to participate actively in various development tasks.1) （71） is a popular fact-finding technique that brings users into the development process as active participants. The end product of the approach is a requirements model.2) （72） is a team-based technique that speeds up information systems development and produces a functioning information system. The approach consists of several phases. The （73） combines elements of the systems planning and systems analysis phases of the SDLC.Users, managers, and IT staff members discuss and agree on business needs, project scope, constraints, and system requirements. During （74）, users interact with systems analysts and develop models and prototypes that represent all system processes, outputs, and inputs.3) （75） attempt to develop a system incrementally by building a series of prototypes and constantly adjusting them to user requirements.","analyze":"在系统分析阶段，参与的用户越多沟通效果越好、开发效率和用户满意度更高。有三种常见的基于团队的方法可以鼓励系统用户积极参与各种幵发任务。1)联合应用程序开发是一种流行的事实发现技术，它使用户主动参与到开发过程中。该方法的最终产品是需求模型。2)快速应用开发是一种基于团队的技术，可加速信息系统开发并生成功能正确的信息系统。该方法包括几个阶段：需求计划阶段将系统开发周期中系统规划与系统分析阶段的要素结合起来。用户、经理和IT员工讨论并商定业务需求、项目范围、约束和系统需求。用户设计阶段，用户与系统分析师进行交互，并开发表示所有系统进程、输出和输入的模型和原型。敏捷方法试图通过构建一系列原型并不断根据用户需求进行调整来逐步开发系统。","multi":0,"questionType":1,"answer":"A","chooseItem":["796234986469478401"],"itemList":[{"id":"796234986469478401","questionId":"796234985529954305","content":" requirements planning phase","answer":1,"chooseValue":"A"},{"id":"796234986498838529","questionId":"796234985529954305","content":" business process modeling","answer":0,"chooseValue":"B"},{"id":"796234986528198657","questionId":"796234985529954305","content":" business process improvement","answer":0,"chooseValue":"C"},{"id":"796234986561753089","questionId":"796234985529954305","content":" scope definition phase","answer":0,"chooseValue":"D"}],"userAnswer":null,"userChooseItem":null,"answerCorrect":null,"userCollect":null},{"id":"796234988562436097","title":"<p><strong>请作答第<span style=\"color: red\">4</span>个空。</strong></p>During the systems analysis phase, greater user involvement usually results in better communication, faster development times, and more satisfied users.There are three common team-based approaches that encourage system users to participate actively in various development tasks.1) （71） is a popular fact-finding technique that brings users into the development process as active participants. The end product of the approach is a requirements model.2) （72） is a team-based technique that speeds up information systems development and produces a functioning information system. The approach consists of several phases. The （73） combines elements of the systems planning and systems analysis phases of the SDLC.Users, managers, and IT staff members discuss and agree on business needs, project scope, constraints, and system requirements. During （74）, users interact with systems analysts and develop models and prototypes that represent all system processes, outputs, and inputs.3) （75） attempt to develop a system incrementally by building a series of prototypes and constantly adjusting them to user requirements.","analyze":"在系统分析阶段，参与的用户越多沟通效果越好、开发效率和用户满意度更高。有三种常见的基于团队的方法可以鼓励系统用户积极参与各种幵发任务。1)联合应用程序开发是一种流行的事实发现技术，它使用户主动参与到开发过程中。该方法的最终产品是需求模型。2)快速应用开发是一种基于团队的技术，可加速信息系统开发并生成功能正确的信息系统。该方法包括几个阶段：需求计划阶段将系统开发周期中系统规划与系统分析阶段的要素结合起来。用户、经理和IT员工讨论并商定业务需求、项目范围、约束和系统需求。用户设计阶段，用户与系统分析师进行交互，并开发表示所有系统进程、输出和输入的模型和原型。敏捷方法试图通过构建一系列原型并不断根据用户需求进行调整来逐步开发系统。","multi":0,"questionType":1,"answer":"D","chooseItem":["796234989644566529"],"itemList":[{"id":"796234989573263361","questionId":"796234988562436097","content":" physical architecture design","answer":0,"chooseValue":"A"},{"id":"796234989594234881","questionId":"796234988562436097","content":" object design","answer":0,"chooseValue":"B"},{"id":"796234989623595009","questionId":"796234988562436097","content":" prototypes design","answer":0,"chooseValue":"C"},{"id":"796234989644566529","questionId":"796234988562436097","content":" user design phase","answer":1,"chooseValue":"D"}],"userAnswer":null,"userChooseItem":null,"answerCorrect":null,"userCollect":null},{"id":"796234991901102081","title":"<p><strong>请作答第<span style=\"color: red\">5</span>个空。</strong></p>During the systems analysis phase, greater user involvement usually results in better communication, faster development times, and more satisfied users.There are three common team-based approaches that encourage system users to participate actively in various development tasks.1) （71） is a popular fact-finding technique that brings users into the development process as active participants. The end product of the approach is a requirements model.2) （72） is a team-based technique that speeds up information systems development and produces a functioning information system. The approach consists of several phases. The （73） combines elements of the systems planning and systems analysis phases of the SDLC.Users, managers, and IT staff members discuss and agree on business needs, project scope, constraints, and system requirements. During （74）, users interact with systems analysts and develop models and prototypes that represent all system processes, outputs, and inputs.3) （75） attempt to develop a system incrementally by building a series of prototypes and constantly adjusting them to user requirements.","analyze":"在系统分析阶段，参与的用户越多沟通效果越好、开发效率和用户满意度更高。有三种常见的基于团队的方法可以鼓励系统用户积极参与各种幵发任务。1)联合应用程序开发是一种流行的事实发现技术，它使用户主动参与到开发过程中。该方法的最终产品是需求模型。2)快速应用开发是一种基于团队的技术，可加速信息系统开发并生成功能正确的信息系统。该方法包括几个阶段：需求计划阶段将系统开发周期中系统规划与系统分析阶段的要素结合起来。用户、经理和IT员工讨论并商定业务需求、项目范围、约束和系统需求。用户设计阶段，用户与系统分析师进行交互，并开发表示所有系统进程、输出和输入的模型和原型。敏捷方法试图通过构建一系列原型并不断根据用户需求进行调整来逐步开发系统。","multi":0,"questionType":1,"answer":"A","chooseItem":["796234992853209089"],"itemList":[{"id":"796234992853209089","questionId":"796234991901102081","content":" Agile methods","answer":1,"chooseValue":"A"},{"id":"796234992878374913","questionId":"796234991901102081","content":" The FAST framework","answer":0,"chooseValue":"B"},{"id":"796234992907735041","questionId":"796234991901102081","content":" Reverse Engineering","answer":0,"chooseValue":"C"},{"id":"796234992932900865","questionId":"796234991901102081","content":" Reengineering","answer":0,"chooseValue":"D"}],"userAnswer":null,"userChooseItem":null,"answerCorrect":null,"userCollect":null},{"id":"796234741882834945","title":"<p><strong>请作答第<span style=\"color: red\">1</span>个空。</strong></p>During the systems planning phase, a systems analyst conducts a （71）activity to study the systems request and recommend specific action. After obtaining an authorization to proceed, the analyst interacts with （72） to gather facts about the problem or opportunity, project scope and constraints, project benefits, and estimated development time and costs. In many cases, the systems request does not reveal the underlying problem, but only a symptom. A popular technique for investigating causes and effects is called （73）The analyst has analyzed the problem or opportunity, defined the project scope and constraints, and performed （74）to evaluate project usability, costs, benefits, and time constraints. The end product of the activity is （75）. The main content must include an estimate of time, staffing requirements, costs, benefits, and expected results for the next phase of the SDLC.","analyze":"在系统计划阶段，系统分析师执行一项初步调查（preliminary investigation），研究系统需求和具体的建议活动。在获得继续进行的授权之后，分析师与经理和用户（managers and users）进行交互，以收集关于机会、项目范围和约束、项目收益以及估计的开发时间和成本等问题的事实。大多数情况下，系统需求只是描述了症状，而未揭示潜在的问题。一种调查因果关系的流行技术叫做鱼刺图（fishbone diagram）。分析师分析了问题或机会，定义了项目范围和约束，并执行可行性分析（feasibility analysis）来评估项目可用性、成本、收益和时间约束。此活动的最终输出是项目章程（a project charter）。主要内容必须包括系统开发生命周期下一阶段的时间、人员需求、成本、效益和对预期结果的估计。","multi":0,"questionType":1,"answer":"C","chooseItem":["796234743057240065"],"itemList":[{"id":"796234742998519809","questionId":"796234741882834945","content":" case study","answer":0,"chooseValue":"A"},{"id":"796234743027879937","questionId":"796234741882834945","content":" requirements discovery","answer":0,"chooseValue":"B"},{"id":"796234743057240065","questionId":"796234741882834945","content":" preliminary investigation","answer":1,"chooseValue":"C"},{"id":"796234743086600193","questionId":"796234741882834945","content":" business understanding","answer":0,"chooseValue":"D"}],"userAnswer":null,"userChooseItem":null,"answerCorrect":null,"userCollect":null},{"id":"796234745129226241","title":"<p><strong>请作答第<span style=\"color: red\">2</span>个空。</strong></p>During the systems planning phase, a systems analyst conducts a （71）activity to study the systems request and recommend specific action. After obtaining an authorization to proceed, the analyst interacts with （72） to gather facts about the problem or opportunity, project scope and constraints, project benefits, and estimated development time and costs. In many cases, the systems request does not reveal the underlying problem, but only a symptom. A popular technique for investigating causes and effects is called （73）The analyst has analyzed the problem or opportunity, defined the project scope and constraints, and performed （74）to evaluate project usability, costs, benefits, and time constraints. The end product of the activity is （75）. The main content must include an estimate of time, staffing requirements, costs, benefits, and expected results for the next phase of the SDLC.","analyze":"在系统计划阶段，系统分析师执行一项初步调查（preliminary investigation），研究系统需求和具体的建议活动。在获得继续进行的授权之后，分析师与经理和用户（managers and users）进行交互，以收集关于机会、项目范围和约束、项目收益以及估计的开发时间和成本等问题的事实。大多数情况下，系统需求只是描述了症状，而未揭示潜在的问题。一种调查因果关系的流行技术叫做鱼刺图（fishbone diagram）。分析师分析了问题或机会，定义了项目范围和约束，并执行可行性分析（feasibility analysis）来评估项目可用性、成本、收益和时间约束。此活动的最终输出是项目章程（a project charter）。主要内容必须包括系统开发生命周期下一阶段的时间、人员需求、成本、效益和对预期结果的估计。","multi":0,"questionType":1,"answer":"C","chooseItem":["796234746110693377"],"itemList":[{"id":"796234746056167425","questionId":"796234745129226241","content":" system users","answer":0,"chooseValue":"A"},{"id":"796234746085527553","questionId":"796234745129226241","content":" system owner","answer":0,"chooseValue":"B"},{"id":"796234746110693377","questionId":"796234745129226241","content":" managers and users","answer":1,"chooseValue":"C"},{"id":"796234746131664897","questionId":"796234745129226241","content":" business analysts","answer":0,"chooseValue":"D"}],"userAnswer":null,"userChooseItem":null,"answerCorrect":null,"userCollect":null},{"id":"796234748111376385","title":"<p><strong>请作答第<span style=\"color: red\">3</span>个空。</strong></p>During the systems planning phase, a systems analyst conducts a （71）activity to study the systems request and recommend specific action. After obtaining an authorization to proceed, the analyst interacts with （72） to gather facts about the problem or opportunity, project scope and constraints, project benefits, and estimated development time and costs. In many cases, the systems request does not reveal the underlying problem, but only a symptom. A popular technique for investigating causes and effects is called （73）The analyst has analyzed the problem or opportunity, defined the project scope and constraints, and performed （74）to evaluate project usability, costs, benefits, and time constraints. The end product of the activity is （75）. The main content must include an estimate of time, staffing requirements, costs, benefits, and expected results for the next phase of the SDLC.","analyze":"在系统计划阶段，系统分析师执行一项初步调查（preliminary investigation），研究系统需求和具体的建议活动。在获得继续进行的授权之后，分析师与经理和用户（managers and users）进行交互，以收集关于机会、项目范围和约束、项目收益以及估计的开发时间和成本等问题的事实。大多数情况下，系统需求只是描述了症状，而未揭示潜在的问题。一种调查因果关系的流行技术叫做鱼刺图（fishbone diagram）。分析师分析了问题或机会，定义了项目范围和约束，并执行可行性分析（feasibility analysis）来评估项目可用性、成本、收益和时间约束。此活动的最终输出是项目章程（a project charter）。主要内容必须包括系统开发生命周期下一阶段的时间、人员需求、成本、效益和对预期结果的估计。","multi":0,"questionType":1,"answer":"A","chooseItem":["796234749059289089"],"itemList":[{"id":"796234749059289089","questionId":"796234748111376385","content":" fishbone diagram","answer":1,"chooseValue":"A"},{"id":"796234749105426433","questionId":"796234748111376385","content":" PERT diagram","answer":0,"chooseValue":"B"},{"id":"796234749147369473","questionId":"796234748111376385","content":" Gantt diagram","answer":0,"chooseValue":"C"},{"id":"796234749168340993","questionId":"796234748111376385","content":" use case diagram","answer":0,"chooseValue":"D"}],"userAnswer":null,"userChooseItem":null,"answerCorrect":null,"userCollect":null},{"id":"796234751122886657","title":"<p><strong>请作答第<span style=\"color: red\">4</span>个空。</strong></p>During the systems planning phase, a systems analyst conducts a （71）activity to study the systems request and recommend specific action. After obtaining an authorization to proceed, the analyst interacts with （72） to gather facts about the problem or opportunity, project scope and constraints, project benefits, and estimated development time and costs. In many cases, the systems request does not reveal the underlying problem, but only a symptom. A popular technique for investigating causes and effects is called （73）The analyst has analyzed the problem or opportunity, defined the project scope and constraints, and performed （74）to evaluate project usability, costs, benefits, and time constraints. The end product of the activity is （75）. The main content must include an estimate of time, staffing requirements, costs, benefits, and expected results for the next phase of the SDLC.","analyze":"在系统计划阶段，系统分析师执行一项初步调查（preliminary investigation），研究系统需求和具体的建议活动。在获得继续进行的授权之后，分析师与经理和用户（managers and users）进行交互，以收集关于机会、项目范围和约束、项目收益以及估计的开发时间和成本等问题的事实。大多数情况下，系统需求只是描述了症状，而未揭示潜在的问题。一种调查因果关系的流行技术叫做鱼刺图（fishbone diagram）。分析师分析了问题或机会，定义了项目范围和约束，并执行可行性分析（feasibility analysis）来评估项目可用性、成本、收益和时间约束。此活动的最终输出是项目章程（a project charter）。主要内容必须包括系统开发生命周期下一阶段的时间、人员需求、成本、效益和对预期结果的估计。","multi":0,"questionType":1,"answer":"A","chooseItem":["796234752033050625"],"itemList":[{"id":"796234752033050625","questionId":"796234751122886657","content":" feasibility analysis","answer":1,"chooseValue":"A"},{"id":"796234752058216449","questionId":"796234751122886657","content":" requirement analysis","answer":0,"chooseValue":"B"},{"id":"796234752083382273","questionId":"796234751122886657","content":" system proposal","answer":0,"chooseValue":"C"},{"id":"796234752108548097","questionId":"796234751122886657","content":" fact-finding","answer":0,"chooseValue":"D"}],"userAnswer":null,"userChooseItem":null,"answerCorrect":null,"userCollect":null},{"id":"796234754054705153","title":"<p><strong>请作答第<span style=\"color: red\">5</span>个空。</strong></p>During the systems planning phase, a systems analyst conducts a （71）activity to study the systems request and recommend specific action. After obtaining an authorization to proceed, the analyst interacts with （72） to gather facts about the problem or opportunity, project scope and constraints, project benefits, and estimated development time and costs. In many cases, the systems request does not reveal the underlying problem, but only a symptom. A popular technique for investigating causes and effects is called （73）The analyst has analyzed the problem or opportunity, defined the project scope and constraints, and performed （74）to evaluate project usability, costs, benefits, and time constraints. The end product of the activity is （75）. The main content must include an estimate of time, staffing requirements, costs, benefits, and expected results for the next phase of the SDLC.","analyze":"在系统计划阶段，系统分析师执行一项初步调查（preliminary investigation），研究系统需求和具体的建议活动。在获得继续进行的授权之后，分析师与经理和用户（managers and users）进行交互，以收集关于机会、项目范围和约束、项目收益以及估计的开发时间和成本等问题的事实。大多数情况下，系统需求只是描述了症状，而未揭示潜在的问题。一种调查因果关系的流行技术叫做鱼刺图（fishbone diagram）。分析师分析了问题或机会，定义了项目范围和约束，并执行可行性分析（feasibility analysis）来评估项目可用性、成本、收益和时间约束。此活动的最终输出是项目章程（a project charter）。主要内容必须包括系统开发生命周期下一阶段的时间、人员需求、成本、效益和对预期结果的估计。","multi":0,"questionType":1,"answer":"C","chooseItem":["796234755031977985"],"itemList":[{"id":"796234754985840641","questionId":"796234754054705153","content":" a report to management","answer":0,"chooseValue":"A"},{"id":"796234755011006465","questionId":"796234754054705153","content":" a requirement definition","answer":0,"chooseValue":"B"},{"id":"796234755031977985","questionId":"796234754054705153","content":" a project charter","answer":1,"chooseValue":"C"},{"id":"796234755052949505","questionId":"796234754054705153","content":" a request for proposal","answer":0,"chooseValue":"D"}],"userAnswer":null,"userChooseItem":null,"answerCorrect":null,"userCollect":null},{"id":"796234020726788097","title":"<p><strong>请作答第<span style=\"color: red\">1</span>个空。</strong></p>Requirements validation is the process of checking that requirements actually define the system that the customer really wants. It overlaps with analysis as it is concerned with finding problems with the requirements. Requirements validation is important because errors in a requirements document can lead to extensive rework costs when these problems are discovered during development or after the system is in service. The cost of fixing a requirements problem by making a system change is usually much greater than repairing design or coding errors. The reason for this is that a change to the requirements usually means that the system design and implementation must also be changed. Furthermore, the system must then be re-tested.<br> During the requirements validation process, different types of checks should be carried out on the requirements in the requirements document. These checks include:<br> 1.（71）: A user may think that a system is needed to perform certain function. However, further thought and analysis may identify additional or different functions that are required. Systems have diverse stakeholders with different needs and any set of requirements is inevitably a compromise across the stakeholder community.<br> 2.（72）: Requirements in the document should not conflict. That is, there should not be contradictory constraints or different descriptions of the same system function.<br> 3.（73）: The requirements document should include requirements that define all functions and the constraints intended by the system user.<br> 4. Realism checks: Using knowledge of existing technology, the requirements should be checked to ensure that they can actually be implemented. These checks should also take account of the（74）for the system development.<br> 5. Verifiability: To reduce the potential for dispute between customer and contractor, system requirements should always be written so that they are verifiable. This means that you should be able to write a set of tests that can demonstrate that the delivered system meets each specified（75）.","analyze":"需求验证是检查需求是否实际定义了客户真正想要的系统的过程。它与分析重叠，因为它关注的是发现需求中的问题。需求验证是很重要的，因为当这些问题在开发过程中或系统投入使用后被发现时，需求文件中的错误会导致大量的返工成本。通过改变系统来修复需求问题的成本通常比修复设计或编码错误要大得多。原因是对需求的改变通常意味着系统的设计和实施也必须改变。此外，还必须重新测试系统。<br> 在需求验证过程中，应该对需求文件中的需求进行不同类型的检查。这些检查包括：<br> 1.（）:用户可能认为需要一个系统来执行某些功能。然而，进一步的思考和分析可能会发现需要额外的或不同的功能。系统有不同的利益相关者，有不同的需求，任何一套需求都不可避免地是整个利益相关者群体的妥协。<br> 2.（）:文件中的要求不应冲突。也就是说，不应该有相互矛盾的约束或对同一系统功能的不同描述。<br> 3.（）:需求文件应该包括定义所有功能的需求和系统用户所期望的约束。<br> 4. 现实性检查。利用现有技术的知识，应该对需求进行检查，以确保它们能够真正被实现。这些检查也应该考虑到系统开发的（）。<br> 5. 可验证性。为了减少客户和承包商之间潜在的争议，系统需求的编写应该始终是可验证的。这意味着你应该能够编写一套测试，以证明所交付的系统符合每一个指定的（）。 <br> （1）A. 安全检查&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; B. 有效性检查&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;C. 一致性检查&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; D. 完整性检查<br> （2）A. 安全检查 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; B. 安全检查&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;C. 一致性检查&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; D. 可用性检查<br> （3）A. 一致性检查&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; B. 可用性检查&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; C. 操作性检查&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; D. 完整性检查<br> （4）A. 工具&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; B. 测试 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; C. 模型 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; D. 预算和时间表<br> （5）A. 需求&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; B. 模型 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; C. 设计 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; D. 实施","multi":0,"questionType":1,"answer":"B","chooseItem":["796234021825695745"],"itemList":[{"id":"796234021796335617","questionId":"796234020726788097","content":" Security checks","answer":0,"chooseValue":"A"},{"id":"796234021825695745","questionId":"796234020726788097","content":" Validity checks","answer":1,"chooseValue":"B"},{"id":"796234021859250177","questionId":"796234020726788097","content":" Consistency checks","answer":0,"chooseValue":"C"},{"id":"796234021896998913","questionId":"796234020726788097","content":" Completeness checks","answer":0,"chooseValue":"D"}],"userAnswer":null,"userChooseItem":null,"answerCorrect":null,"userCollect":null},{"id":"796234023964790785","title":"<p><strong>请作答第<span style=\"color: red\">2</span>个空。</strong></p>Requirements validation is the process of checking that requirements actually define the system that the customer really wants. It overlaps with analysis as it is concerned with finding problems with the requirements. Requirements validation is important because errors in a requirements document can lead to extensive rework costs when these problems are discovered during development or after the system is in service. The cost of fixing a requirements problem by making a system change is usually much greater than repairing design or coding errors. The reason for this is that a change to the requirements usually means that the system design and implementation must also be changed. Furthermore, the system must then be re-tested.<br> During the requirements validation process, different types of checks should be carried out on the requirements in the requirements document. These checks include:<br> 1.（71）: A user may think that a system is needed to perform certain function. However, further thought and analysis may identify additional or different functions that are required. Systems have diverse stakeholders with different needs and any set of requirements is inevitably a compromise across the stakeholder community.<br> 2.（72）: Requirements in the document should not conflict. That is, there should not be contradictory constraints or different descriptions of the same system function.<br> 3.（73）: The requirements document should include requirements that define all functions and the constraints intended by the system user.<br> 4. Realism checks: Using knowledge of existing technology, the requirements should be checked to ensure that they can actually be implemented. These checks should also take account of the（74）for the system development.<br> 5. Verifiability: To reduce the potential for dispute between customer and contractor, system requirements should always be written so that they are verifiable. This means that you should be able to write a set of tests that can demonstrate that the delivered system meets each specified（75）.","analyze":"需求验证是检查需求是否实际定义了客户真正想要的系统的过程。它与分析重叠，因为它关注的是发现需求中的问题。需求验证是很重要的，因为当这些问题在开发过程中或系统投入使用后被发现时，需求文件中的错误会导致大量的返工成本。通过改变系统来修复需求问题的成本通常比修复设计或编码错误要大得多。原因是对需求的改变通常意味着系统的设计和实施也必须改变。此外，还必须重新测试系统。<br> 在需求验证过程中，应该对需求文件中的需求进行不同类型的检查。这些检查包括：<br> 1.（）:用户可能认为需要一个系统来执行某些功能。然而，进一步的思考和分析可能会发现需要额外的或不同的功能。系统有不同的利益相关者，有不同的需求，任何一套需求都不可避免地是整个利益相关者群体的妥协。<br> 2.（）:文件中的要求不应冲突。也就是说，不应该有相互矛盾的约束或对同一系统功能的不同描述。<br> 3.（）:需求文件应该包括定义所有功能的需求和系统用户所期望的约束。<br> 4. 现实性检查。利用现有技术的知识，应该对需求进行检查，以确保它们能够真正被实现。这些检查也应该考虑到系统开发的（）。<br> 5. 可验证性。为了减少客户和承包商之间潜在的争议，系统需求的编写应该始终是可验证的。这意味着你应该能够编写一套测试，以证明所交付的系统符合每一个指定的（）。 <br> （1）A. 安全检查&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; B. 有效性检查&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;C. 一致性检查&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; D. 完整性检查<br> （2）A. 安全检查 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; B. 安全检查&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;C. 一致性检查&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; D. 可用性检查<br> （3）A. 一致性检查&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; B. 可用性检查&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; C. 操作性检查&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; D. 完整性检查<br> （4）A. 工具&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; B. 测试 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; C. 模型 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; D. 预算和时间表<br> （5）A. 需求&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; B. 模型 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; C. 设计 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; D. 实施","multi":0,"questionType":1,"answer":"C","chooseItem":["796234025130807297"],"itemList":[{"id":"796234025067892737","questionId":"796234023964790785","content":" Security checks","answer":0,"chooseValue":"A"},{"id":"796234025097252865","questionId":"796234023964790785","content":" Safety checks","answer":0,"chooseValue":"B"},{"id":"796234025130807297","questionId":"796234023964790785","content":" Consistency checks","answer":1,"chooseValue":"C"},{"id":"796234025160167425","questionId":"796234023964790785","content":" Usability checks","answer":0,"chooseValue":"D"}],"userAnswer":null,"userChooseItem":null,"answerCorrect":null,"userCollect":null},{"id":"796234027144073217","title":"<p><strong>请作答第<span style=\"color: red\">3</span>个空。</strong></p>Requirements validation is the process of checking that requirements actually define the system that the customer really wants. It overlaps with analysis as it is concerned with finding problems with the requirements. Requirements validation is important because errors in a requirements document can lead to extensive rework costs when these problems are discovered during development or after the system is in service. The cost of fixing a requirements problem by making a system change is usually much greater than repairing design or coding errors. The reason for this is that a change to the requirements usually means that the system design and implementation must also be changed. Furthermore, the system must then be re-tested.<br> During the requirements validation process, different types of checks should be carried out on the requirements in the requirements document. These checks include:<br> 1.（71）: A user may think that a system is needed to perform certain function. However, further thought and analysis may identify additional or different functions that are required. Systems have diverse stakeholders with different needs and any set of requirements is inevitably a compromise across the stakeholder community.<br> 2.（72）: Requirements in the document should not conflict. That is, there should not be contradictory constraints or different descriptions of the same system function.<br> 3.（73）: The requirements document should include requirements that define all functions and the constraints intended by the system user.<br> 4. Realism checks: Using knowledge of existing technology, the requirements should be checked to ensure that they can actually be implemented. These checks should also take account of the（74）for the system development.<br> 5. Verifiability: To reduce the potential for dispute between customer and contractor, system requirements should always be written so that they are verifiable. This means that you should be able to write a set of tests that can demonstrate that the delivered system meets each specified（75）.","analyze":"需求验证是检查需求是否实际定义了客户真正想要的系统的过程。它与分析重叠，因为它关注的是发现需求中的问题。需求验证是很重要的，因为当这些问题在开发过程中或系统投入使用后被发现时，需求文件中的错误会导致大量的返工成本。通过改变系统来修复需求问题的成本通常比修复设计或编码错误要大得多。原因是对需求的改变通常意味着系统的设计和实施也必须改变。此外，还必须重新测试系统。<br> 在需求验证过程中，应该对需求文件中的需求进行不同类型的检查。这些检查包括：<br> 1.（）:用户可能认为需要一个系统来执行某些功能。然而，进一步的思考和分析可能会发现需要额外的或不同的功能。系统有不同的利益相关者，有不同的需求，任何一套需求都不可避免地是整个利益相关者群体的妥协。<br> 2.（）:文件中的要求不应冲突。也就是说，不应该有相互矛盾的约束或对同一系统功能的不同描述。<br> 3.（）:需求文件应该包括定义所有功能的需求和系统用户所期望的约束。<br> 4. 现实性检查。利用现有技术的知识，应该对需求进行检查，以确保它们能够真正被实现。这些检查也应该考虑到系统开发的（）。<br> 5. 可验证性。为了减少客户和承包商之间潜在的争议，系统需求的编写应该始终是可验证的。这意味着你应该能够编写一套测试，以证明所交付的系统符合每一个指定的（）。 <br> （1）A. 安全检查&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; B. 有效性检查&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;C. 一致性检查&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; D. 完整性检查<br> （2）A. 安全检查 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; B. 安全检查&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;C. 一致性检查&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; D. 可用性检查<br> （3）A. 一致性检查&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; B. 可用性检查&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; C. 操作性检查&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; D. 完整性检查<br> （4）A. 工具&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; B. 测试 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; C. 模型 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; D. 预算和时间表<br> （5）A. 需求&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; B. 模型 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; C. 设计 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; D. 实施","multi":0,"questionType":1,"answer":"D","chooseItem":["796234028163289089"],"itemList":[{"id":"796234028071014401","questionId":"796234027144073217","content":" Consistency checks","answer":0,"chooseValue":"A"},{"id":"796234028108763137","questionId":"796234027144073217","content":" Usability checks","answer":0,"chooseValue":"B"},{"id":"796234028146511873","questionId":"796234027144073217","content":" Operational checks","answer":0,"chooseValue":"C"},{"id":"796234028163289089","questionId":"796234027144073217","content":" Completeness checks","answer":1,"chooseValue":"D"}],"userAnswer":null,"userChooseItem":null,"answerCorrect":null,"userCollect":null},{"id":"796234030134611969","title":"<p><strong>请作答第<span style=\"color: red\">4</span>个空。</strong></p>Requirements validation is the process of checking that requirements actually define the system that the customer really wants. It overlaps with analysis as it is concerned with finding problems with the requirements. Requirements validation is important because errors in a requirements document can lead to extensive rework costs when these problems are discovered during development or after the system is in service. The cost of fixing a requirements problem by making a system change is usually much greater than repairing design or coding errors. The reason for this is that a change to the requirements usually means that the system design and implementation must also be changed. Furthermore, the system must then be re-tested.<br> During the requirements validation process, different types of checks should be carried out on the requirements in the requirements document. These checks include:<br> 1.（71）: A user may think that a system is needed to perform certain function. However, further thought and analysis may identify additional or different functions that are required. Systems have diverse stakeholders with different needs and any set of requirements is inevitably a compromise across the stakeholder community.<br> 2.（72）: Requirements in the document should not conflict. That is, there should not be contradictory constraints or different descriptions of the same system function.<br> 3.（73）: The requirements document should include requirements that define all functions and the constraints intended by the system user.<br> 4. Realism checks: Using knowledge of existing technology, the requirements should be checked to ensure that they can actually be implemented. These checks should also take account of the（74）for the system development.<br> 5. Verifiability: To reduce the potential for dispute between customer and contractor, system requirements should always be written so that they are verifiable. This means that you should be able to write a set of tests that can demonstrate that the delivered system meets each specified（75）.","analyze":"需求验证是检查需求是否实际定义了客户真正想要的系统的过程。它与分析重叠，因为它关注的是发现需求中的问题。需求验证是很重要的，因为当这些问题在开发过程中或系统投入使用后被发现时，需求文件中的错误会导致大量的返工成本。通过改变系统来修复需求问题的成本通常比修复设计或编码错误要大得多。原因是对需求的改变通常意味着系统的设计和实施也必须改变。此外，还必须重新测试系统。<br> 在需求验证过程中，应该对需求文件中的需求进行不同类型的检查。这些检查包括：<br> 1.（）:用户可能认为需要一个系统来执行某些功能。然而，进一步的思考和分析可能会发现需要额外的或不同的功能。系统有不同的利益相关者，有不同的需求，任何一套需求都不可避免地是整个利益相关者群体的妥协。<br> 2.（）:文件中的要求不应冲突。也就是说，不应该有相互矛盾的约束或对同一系统功能的不同描述。<br> 3.（）:需求文件应该包括定义所有功能的需求和系统用户所期望的约束。<br> 4. 现实性检查。利用现有技术的知识，应该对需求进行检查，以确保它们能够真正被实现。这些检查也应该考虑到系统开发的（）。<br> 5. 可验证性。为了减少客户和承包商之间潜在的争议，系统需求的编写应该始终是可验证的。这意味着你应该能够编写一套测试，以证明所交付的系统符合每一个指定的（）。 <br> （1）A. 安全检查&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; B. 有效性检查&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;C. 一致性检查&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; D. 完整性检查<br> （2）A. 安全检查 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; B. 安全检查&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;C. 一致性检查&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; D. 可用性检查<br> （3）A. 一致性检查&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; B. 可用性检查&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; C. 操作性检查&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; D. 完整性检查<br> （4）A. 工具&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; B. 测试 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; C. 模型 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; D. 预算和时间表<br> （5）A. 需求&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; B. 模型 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; C. 设计 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; D. 实施","multi":0,"questionType":1,"answer":"C","chooseItem":["796234031422263297"],"itemList":[{"id":"796234031342571521","questionId":"796234030134611969","content":" tools","answer":0,"chooseValue":"A"},{"id":"796234031384514561","questionId":"796234030134611969","content":" tests","answer":0,"chooseValue":"B"},{"id":"796234031422263297","questionId":"796234030134611969","content":" models","answer":1,"chooseValue":"C"},{"id":"796234031434846209","questionId":"796234030134611969","content":" budget and schedule","answer":0,"chooseValue":"D"}],"userAnswer":null,"userChooseItem":null,"answerCorrect":null,"userCollect":null},{"id":"796234033443917825","title":"<p><strong>请作答第<span style=\"color: red\">5</span>个空。</strong></p>Requirements validation is the process of checking that requirements actually define the system that the customer really wants. It overlaps with analysis as it is concerned with finding problems with the requirements. Requirements validation is important because errors in a requirements document can lead to extensive rework costs when these problems are discovered during development or after the system is in service. The cost of fixing a requirements problem by making a system change is usually much greater than repairing design or coding errors. The reason for this is that a change to the requirements usually means that the system design and implementation must also be changed. Furthermore, the system must then be re-tested.<br> During the requirements validation process, different types of checks should be carried out on the requirements in the requirements document. These checks include:<br> 1.（71）: A user may think that a system is needed to perform certain function. However, further thought and analysis may identify additional or different functions that are required. Systems have diverse stakeholders with different needs and any set of requirements is inevitably a compromise across the stakeholder community.<br> 2.（72）: Requirements in the document should not conflict. That is, there should not be contradictory constraints or different descriptions of the same system function.<br> 3.（73）: The requirements document should include requirements that define all functions and the constraints intended by the system user.<br> 4. Realism checks: Using knowledge of existing technology, the requirements should be checked to ensure that they can actually be implemented. These checks should also take account of the（74）for the system development.<br> 5. Verifiability: To reduce the potential for dispute between customer and contractor, system requirements should always be written so that they are verifiable. This means that you should be able to write a set of tests that can demonstrate that the delivered system meets each specified（75）.","analyze":"需求验证是检查需求是否实际定义了客户真正想要的系统的过程。它与分析重叠，因为它关注的是发现需求中的问题。需求验证是很重要的，因为当这些问题在开发过程中或系统投入使用后被发现时，需求文件中的错误会导致大量的返工成本。通过改变系统来修复需求问题的成本通常比修复设计或编码错误要大得多。原因是对需求的改变通常意味着系统的设计和实施也必须改变。此外，还必须重新测试系统。<br> 在需求验证过程中，应该对需求文件中的需求进行不同类型的检查。这些检查包括：<br> 1.（）:用户可能认为需要一个系统来执行某些功能。然而，进一步的思考和分析可能会发现需要额外的或不同的功能。系统有不同的利益相关者，有不同的需求，任何一套需求都不可避免地是整个利益相关者群体的妥协。<br> 2.（）:文件中的要求不应冲突。也就是说，不应该有相互矛盾的约束或对同一系统功能的不同描述。<br> 3.（）:需求文件应该包括定义所有功能的需求和系统用户所期望的约束。<br> 4. 现实性检查。利用现有技术的知识，应该对需求进行检查，以确保它们能够真正被实现。这些检查也应该考虑到系统开发的（）。<br> 5. 可验证性。为了减少客户和承包商之间潜在的争议，系统需求的编写应该始终是可验证的。这意味着你应该能够编写一套测试，以证明所交付的系统符合每一个指定的（）。 <br> （1）A. 安全检查&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; B. 有效性检查&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;C. 一致性检查&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; D. 完整性检查<br> （2）A. 安全检查 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; B. 安全检查&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;C. 一致性检查&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; D. 可用性检查<br> （3）A. 一致性检查&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; B. 可用性检查&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; C. 操作性检查&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; D. 完整性检查<br> （4）A. 工具&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; B. 测试 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; C. 模型 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; D. 预算和时间表<br> （5）A. 需求&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; B. 模型 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; C. 设计 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; D. 实施","multi":0,"questionType":1,"answer":"A","chooseItem":["796234034370859009"],"itemList":[{"id":"796234034370859009","questionId":"796234033443917825","content":" requirement","answer":1,"chooseValue":"A"},{"id":"796234034400219137","questionId":"796234033443917825","content":" model","answer":0,"chooseValue":"B"},{"id":"796234034429579265","questionId":"796234033443917825","content":" design","answer":0,"chooseValue":"C"},{"id":"796234034458939393","questionId":"796234033443917825","content":" implementation","answer":0,"chooseValue":"D"}],"userAnswer":null,"userChooseItem":null,"answerCorrect":null,"userCollect":null},{"id":"796235216451555329","title":"<p><strong>请作答第<span style=\"color: red\">1</span>个空。</strong></p>The purpose of systems analysis phase is to build a logical model of the new system. The first step is71, where you investigate business processes and document what the new system must do to satisfy users. This step continues the investigation that began during the 72. You use the fact-finding results to build business models, data and process models, and object models. The deliverable for the systems analysis phase is the 73, which describes management and user requirements, costs and benefits, and outlines alternative development strategies.<br>The purpose of the systems design phase is to create a physical model that will satisfy all documented requirements for the system. During the systems design phase, you need to determine the74, which programmers will use to transform the logical design into program modules and code. The deliverable for this phase is the 75, which is presented to management and users for review and approval.","analyze":"系统分析阶段的目的是构建一个新系统的逻辑模型。第一步是需求建模，调查新系统为了满足用户需要必须完成的业务过程和文档。这一步继续在系统计划阶段开始的调查。你可以利用事实发现的结果构建业务模型、数据和过程模型，以及对象模型。系统分析阶段的可交付成果是系统需求文档，它描述了管理和用户需求、成本和收益、并概述候选的开发策略。<br>系统设计阶段的目的是创建一个能够满足系统所有已记录系统需求的物理棋型。在系统设计阶段，你需要确定系统过程模型，程序员用其将逻辑设计转换到程序模块和代码。这一阶段的可交付成果是系统设计规格说明，提供给管理层和用户用于审查和批准。<br><br>application architecture 应用架构<br>system data model 系统数据模型<br>system process model 系统过程模型<br>implement environment 实施环境","multi":0,"questionType":1,"answer":"C","chooseItem":["796235217504325633"],"itemList":[{"id":"796235217445605377","questionId":"796235216451555329","content":" System logical modeling","answer":0,"chooseValue":"A"},{"id":"796235217470771201","questionId":"796235216451555329","content":" use case modeling","answer":0,"chooseValue":"B"},{"id":"796235217504325633","questionId":"796235216451555329","content":" requirements modeling","answer":1,"chooseValue":"C"},{"id":"796235217533685761","questionId":"796235216451555329","content":" application modeling","answer":0,"chooseValue":"D"}],"userAnswer":null,"userChooseItem":null,"answerCorrect":null,"userCollect":null},{"id":"796235219467259905","title":"<p><strong>请作答第<span style=\"color: red\">2</span>个空。</strong></p>The purpose of systems analysis phase is to build a logical model of the new system. The first step is71, where you investigate business processes and document what the new system must do to satisfy users. This step continues the investigation that began during the 72. You use the fact-finding results to build business models, data and process models, and object models. The deliverable for the systems analysis phase is the 73, which describes management and user requirements, costs and benefits, and outlines alternative development strategies.<br>The purpose of the systems design phase is to create a physical model that will satisfy all documented requirements for the system. During the systems design phase, you need to determine the74, which programmers will use to transform the logical design into program modules and code. The deliverable for this phase is the 75, which is presented to management and users for review and approval.","analyze":"系统分析阶段的目的是构建一个新系统的逻辑模型。第一步是需求建模，调查新系统为了满足用户需要必须完成的业务过程和文档。这一步继续在系统计划阶段开始的调查。你可以利用事实发现的结果构建业务模型、数据和过程模型，以及对象模型。系统分析阶段的可交付成果是系统需求文档，它描述了管理和用户需求、成本和收益、并概述候选的开发策略。<br>系统设计阶段的目的是创建一个能够满足系统所有已记录系统需求的物理棋型。在系统设计阶段，你需要确定系统过程模型，程序员用其将逻辑设计转换到程序模块和代码。这一阶段的可交付成果是系统设计规格说明，提供给管理层和用户用于审查和批准。<br><br>application architecture 应用架构<br>system data model 系统数据模型<br>system process model 系统过程模型<br>implement environment 实施环境","multi":0,"questionType":1,"answer":"A","chooseItem":["796235220390006785"],"itemList":[{"id":"796235220390006785","questionId":"796235219467259905","content":" systems planning phase","answer":1,"chooseValue":"A"},{"id":"796235220415172609","questionId":"796235219467259905","content":" systems modeling phase","answer":0,"chooseValue":"B"},{"id":"796235220440338433","questionId":"796235219467259905","content":" systems analysis phase","answer":0,"chooseValue":"C"},{"id":"796235220465504257","questionId":"796235219467259905","content":" systems design phase","answer":0,"chooseValue":"D"}],"userAnswer":null,"userChooseItem":null,"answerCorrect":null,"userCollect":null},{"id":"796235222461992961","title":"<p><strong>请作答第<span style=\"color: red\">3</span>个空。</strong></p>The purpose of systems analysis phase is to build a logical model of the new system. The first step is71, where you investigate business processes and document what the new system must do to satisfy users. This step continues the investigation that began during the 72. You use the fact-finding results to build business models, data and process models, and object models. The deliverable for the systems analysis phase is the 73, which describes management and user requirements, costs and benefits, and outlines alternative development strategies.<br>The purpose of the systems design phase is to create a physical model that will satisfy all documented requirements for the system. During the systems design phase, you need to determine the74, which programmers will use to transform the logical design into program modules and code. The deliverable for this phase is the 75, which is presented to management and users for review and approval.","analyze":"系统分析阶段的目的是构建一个新系统的逻辑模型。第一步是需求建模，调查新系统为了满足用户需要必须完成的业务过程和文档。这一步继续在系统计划阶段开始的调查。你可以利用事实发现的结果构建业务模型、数据和过程模型，以及对象模型。系统分析阶段的可交付成果是系统需求文档，它描述了管理和用户需求、成本和收益、并概述候选的开发策略。<br>系统设计阶段的目的是创建一个能够满足系统所有已记录系统需求的物理棋型。在系统设计阶段，你需要确定系统过程模型，程序员用其将逻辑设计转换到程序模块和代码。这一阶段的可交付成果是系统设计规格说明，提供给管理层和用户用于审查和批准。<br><br>application architecture 应用架构<br>system data model 系统数据模型<br>system process model 系统过程模型<br>implement environment 实施环境","multi":0,"questionType":1,"answer":"D","chooseItem":["796235223644786689"],"itemList":[{"id":"796235223539929089","questionId":"796235222461992961","content":" system charter","answer":0,"chooseValue":"A"},{"id":"796235223573483521","questionId":"796235222461992961","content":" system scope definition","answer":0,"chooseValue":"B"},{"id":"796235223611232257","questionId":"796235222461992961","content":" system blueprint","answer":0,"chooseValue":"C"},{"id":"796235223644786689","questionId":"796235222461992961","content":" system requirement document","answer":1,"chooseValue":"D"}],"userAnswer":null,"userChooseItem":null,"answerCorrect":null,"userCollect":null},{"id":"796235225708384257","title":"<p><strong>请作答第<span style=\"color: red\">4</span>个空。</strong></p>The purpose of systems analysis phase is to build a logical model of the new system. The first step is71, where you investigate business processes and document what the new system must do to satisfy users. This step continues the investigation that began during the 72. You use the fact-finding results to build business models, data and process models, and object models. The deliverable for the systems analysis phase is the 73, which describes management and user requirements, costs and benefits, and outlines alternative development strategies.<br>The purpose of the systems design phase is to create a physical model that will satisfy all documented requirements for the system. During the systems design phase, you need to determine the74, which programmers will use to transform the logical design into program modules and code. The deliverable for this phase is the 75, which is presented to management and users for review and approval.","analyze":"系统分析阶段的目的是构建一个新系统的逻辑模型。第一步是需求建模，调查新系统为了满足用户需要必须完成的业务过程和文档。这一步继续在系统计划阶段开始的调查。你可以利用事实发现的结果构建业务模型、数据和过程模型，以及对象模型。系统分析阶段的可交付成果是系统需求文档，它描述了管理和用户需求、成本和收益、并概述候选的开发策略。<br>系统设计阶段的目的是创建一个能够满足系统所有已记录系统需求的物理棋型。在系统设计阶段，你需要确定系统过程模型，程序员用其将逻辑设计转换到程序模块和代码。这一阶段的可交付成果是系统设计规格说明，提供给管理层和用户用于审查和批准。<br><br>application architecture 应用架构<br>system data model 系统数据模型<br>system process model 系统过程模型<br>implement environment 实施环境","multi":0,"questionType":1,"answer":"A","chooseItem":["796235226622742529"],"itemList":[{"id":"796235226622742529","questionId":"796235225708384257","content":" application architecture","answer":1,"chooseValue":"A"},{"id":"796235226652102657","questionId":"796235225708384257","content":" system data model","answer":0,"chooseValue":"B"},{"id":"796235226677268481","questionId":"796235225708384257","content":" system process model","answer":0,"chooseValue":"C"},{"id":"796235226698240001","questionId":"796235225708384257","content":" implement environment","answer":0,"chooseValue":"D"}],"userAnswer":null,"userChooseItem":null,"answerCorrect":null,"userCollect":null},{"id":"796235228690534401","title":"<p><strong>请作答第<span style=\"color: red\">5</span>个空。</strong></p>The purpose of systems analysis phase is to build a logical model of the new system. The first step is71, where you investigate business processes and document what the new system must do to satisfy users. This step continues the investigation that began during the 72. You use the fact-finding results to build business models, data and process models, and object models. The deliverable for the systems analysis phase is the 73, which describes management and user requirements, costs and benefits, and outlines alternative development strategies.<br>The purpose of the systems design phase is to create a physical model that will satisfy all documented requirements for the system. During the systems design phase, you need to determine the74, which programmers will use to transform the logical design into program modules and code. The deliverable for this phase is the 75, which is presented to management and users for review and approval.","analyze":"系统分析阶段的目的是构建一个新系统的逻辑模型。第一步是需求建模，调查新系统为了满足用户需要必须完成的业务过程和文档。这一步继续在系统计划阶段开始的调查。你可以利用事实发现的结果构建业务模型、数据和过程模型，以及对象模型。系统分析阶段的可交付成果是系统需求文档，它描述了管理和用户需求、成本和收益、并概述候选的开发策略。<br>系统设计阶段的目的是创建一个能够满足系统所有已记录系统需求的物理棋型。在系统设计阶段，你需要确定系统过程模型，程序员用其将逻辑设计转换到程序模块和代码。这一阶段的可交付成果是系统设计规格说明，提供给管理层和用户用于审查和批准。<br><br>application architecture 应用架构<br>system data model 系统数据模型<br>system process model 系统过程模型<br>implement environment 实施环境","multi":0,"questionType":1,"answer":"B","chooseItem":["796235229705555969"],"itemList":[{"id":"796235229663612929","questionId":"796235228690534401","content":" system architecture description","answer":0,"chooseValue":"A"},{"id":"796235229705555969","questionId":"796235228690534401","content":" system design specification","answer":1,"chooseValue":"B"},{"id":"796235229743304705","questionId":"796235228690534401","content":" system technique architecture","answer":0,"chooseValue":"C"},{"id":"796235229776859137","questionId":"796235228690534401","content":" physical deployment architecture","answer":0,"chooseValue":"D"}],"userAnswer":null,"userChooseItem":null,"answerCorrect":null,"userCollect":null},{"id":"796234499645001729","title":"<p><strong>请作答第<span style=\"color: red\">1</span>个空。</strong></p>Unified Modeling Language (UML) is a widely used method of visualizing and documenting an information system. The UML can be used to develop (71)<span> </span>,in which an object represents a<br> person, place, event, or transaction that is significant to the information system. Systems analysts define an object’s attributes during the (72).An object also has (73)，which are tasks or functions that the object performs when it receives a message, or command, to do so. A(n) (74) is a group of similar objects. If objects are similar to nouns, attributes are similar to adjectives that describe the characteristics of an object. Objects can have a specific attribute called a(n) (75), which of an object is an adjective that describes the object's current status. All objects within a class share common attributes and methods, so a class is like a blueprint, or template for all the objects within the class.","analyze":"统一建模语言（UML)是一种广泛用于可视化和文档化信息系统的方法。UML可用于开发对象模型，其中的对象表示人、地点、事件或信息系统的关键业务。系统分析师在系统设计过程中定义对象的属性。对象还具有方法，这些方法是对象在收到消息或命令时执行的任务或功能。一个类是一组相似的对象。如果把对象类比于名词，那属性就可类比于描述一个对象特征的形容词。对象可以具有称为状态的特定属性，通常一个对象的状态用于描述该对象的当前状态。一个类中的所有对象共享共同的属性和方法，所以一个类就像个蓝图，或该类中所有对象的模板。","multi":0,"questionType":1,"answer":"B","chooseItem":["796234500685189121"],"itemList":[{"id":"796234500668411905","questionId":"796234499645001729","content":" database models","answer":0,"chooseValue":"A"},{"id":"796234500685189121","questionId":"796234499645001729","content":" object models","answer":1,"chooseValue":"B"},{"id":"796234500710354945","questionId":"796234499645001729","content":" event models","answer":0,"chooseValue":"C"},{"id":"796234500727132161","questionId":"796234499645001729","content":" static system models","answer":0,"chooseValue":"D"}],"userAnswer":null,"userChooseItem":null,"answerCorrect":null,"userCollect":null},{"id":"796234502744592385","title":"<p><strong>请作答第<span style=\"color: red\">2</span>个空。</strong></p>Unified Modeling Language (UML) is a widely used method of visualizing and documenting an information system. The UML can be used to develop (71)<span> </span>,in which an object represents a<br> person, place, event, or transaction that is significant to the information system. Systems analysts define an object’s attributes during the (72).An object also has (73)，which are tasks or functions that the object performs when it receives a message, or command, to do so. A(n) (74) is a group of similar objects. If objects are similar to nouns, attributes are similar to adjectives that describe the characteristics of an object. Objects can have a specific attribute called a(n) (75), which of an object is an adjective that describes the object's current status. All objects within a class share common attributes and methods, so a class is like a blueprint, or template for all the objects within the class.","analyze":"统一建模语言（UML)是一种广泛用于可视化和文档化信息系统的方法。UML可用于开发对象模型，其中的对象表示人、地点、事件或信息系统的关键业务。系统分析师在系统设计过程中定义对象的属性。对象还具有方法，这些方法是对象在收到消息或命令时执行的任务或功能。一个类是一组相似的对象。如果把对象类比于名词，那属性就可类比于描述一个对象特征的形容词。对象可以具有称为状态的特定属性，通常一个对象的状态用于描述该对象的当前状态。一个类中的所有对象共享共同的属性和方法，所以一个类就像个蓝图，或该类中所有对象的模板。","multi":0,"questionType":1,"answer":"C","chooseItem":["796234503755419649"],"itemList":[{"id":"796234503705088001","questionId":"796234502744592385","content":" systems maintenance process","answer":0,"chooseValue":"A"},{"id":"796234503730253825","questionId":"796234502744592385","content":" systems implementation process","answer":0,"chooseValue":"B"},{"id":"796234503755419649","questionId":"796234502744592385","content":" systems design process","answer":1,"chooseValue":"C"},{"id":"796234503776391169","questionId":"796234502744592385","content":" systems testing process","answer":0,"chooseValue":"D"}],"userAnswer":null,"userChooseItem":null,"answerCorrect":null,"userCollect":null},{"id":"796234505751908353","title":"<p><strong>请作答第<span style=\"color: red\">3</span>个空。</strong></p>Unified Modeling Language (UML) is a widely used method of visualizing and documenting an information system. The UML can be used to develop (71)<span> </span>,in which an object represents a<br> person, place, event, or transaction that is significant to the information system. Systems analysts define an object’s attributes during the (72).An object also has (73)，which are tasks or functions that the object performs when it receives a message, or command, to do so. A(n) (74) is a group of similar objects. If objects are similar to nouns, attributes are similar to adjectives that describe the characteristics of an object. Objects can have a specific attribute called a(n) (75), which of an object is an adjective that describes the object's current status. All objects within a class share common attributes and methods, so a class is like a blueprint, or template for all the objects within the class.","analyze":"统一建模语言（UML)是一种广泛用于可视化和文档化信息系统的方法。UML可用于开发对象模型，其中的对象表示人、地点、事件或信息系统的关键业务。系统分析师在系统设计过程中定义对象的属性。对象还具有方法，这些方法是对象在收到消息或命令时执行的任务或功能。一个类是一组相似的对象。如果把对象类比于名词，那属性就可类比于描述一个对象特征的形容词。对象可以具有称为状态的特定属性，通常一个对象的状态用于描述该对象的当前状态。一个类中的所有对象共享共同的属性和方法，所以一个类就像个蓝图，或该类中所有对象的模板。","multi":0,"questionType":1,"answer":"A","chooseItem":["796234506691432449"],"itemList":[{"id":"796234506691432449","questionId":"796234505751908353","content":" methods","answer":1,"chooseValue":"A"},{"id":"796234506737569793","questionId":"796234505751908353","content":" interactions","answer":0,"chooseValue":"B"},{"id":"796234506779512833","questionId":"796234505751908353","content":" interfaces","answer":0,"chooseValue":"C"},{"id":"796234506808872961","questionId":"796234505751908353","content":" behaviors","answer":0,"chooseValue":"D"}],"userAnswer":null,"userChooseItem":null,"answerCorrect":null,"userCollect":null},{"id":"796234508755030017","title":"<p><strong>请作答第<span style=\"color: red\">4</span>个空。</strong></p>Unified Modeling Language (UML) is a widely used method of visualizing and documenting an information system. The UML can be used to develop (71)<span> </span>,in which an object represents a<br> person, place, event, or transaction that is significant to the information system. Systems analysts define an object’s attributes during the (72).An object also has (73)，which are tasks or functions that the object performs when it receives a message, or command, to do so. A(n) (74) is a group of similar objects. If objects are similar to nouns, attributes are similar to adjectives that describe the characteristics of an object. Objects can have a specific attribute called a(n) (75), which of an object is an adjective that describes the object's current status. All objects within a class share common attributes and methods, so a class is like a blueprint, or template for all the objects within the class.","analyze":"统一建模语言（UML)是一种广泛用于可视化和文档化信息系统的方法。UML可用于开发对象模型，其中的对象表示人、地点、事件或信息系统的关键业务。系统分析师在系统设计过程中定义对象的属性。对象还具有方法，这些方法是对象在收到消息或命令时执行的任务或功能。一个类是一组相似的对象。如果把对象类比于名词，那属性就可类比于描述一个对象特征的形容词。对象可以具有称为状态的特定属性，通常一个对象的状态用于描述该对象的当前状态。一个类中的所有对象共享共同的属性和方法，所以一个类就像个蓝图，或该类中所有对象的模板。","multi":0,"questionType":1,"answer":"D","chooseItem":["796234509824577537"],"itemList":[{"id":"796234509723914241","questionId":"796234508755030017","content":" actor","answer":0,"chooseValue":"A"},{"id":"796234509757468673","questionId":"796234508755030017","content":" instance","answer":0,"chooseValue":"B"},{"id":"796234509795217409","questionId":"796234508755030017","content":" component","answer":0,"chooseValue":"C"},{"id":"796234509824577537","questionId":"796234508755030017","content":" class","answer":1,"chooseValue":"D"}],"userAnswer":null,"userChooseItem":null,"answerCorrect":null,"userCollect":null},{"id":"796234511858814977","title":"<p><strong>请作答第<span style=\"color: red\">5</span>个空。</strong></p>Unified Modeling Language (UML) is a widely used method of visualizing and documenting an information system. The UML can be used to develop (71)<span> </span>,in which an object represents a<br> person, place, event, or transaction that is significant to the information system. Systems analysts define an object’s attributes during the (72).An object also has (73)，which are tasks or functions that the object performs when it receives a message, or command, to do so. A(n) (74) is a group of similar objects. If objects are similar to nouns, attributes are similar to adjectives that describe the characteristics of an object. Objects can have a specific attribute called a(n) (75), which of an object is an adjective that describes the object's current status. All objects within a class share common attributes and methods, so a class is like a blueprint, or template for all the objects within the class.","analyze":"统一建模语言（UML)是一种广泛用于可视化和文档化信息系统的方法。UML可用于开发对象模型，其中的对象表示人、地点、事件或信息系统的关键业务。系统分析师在系统设计过程中定义对象的属性。对象还具有方法，这些方法是对象在收到消息或命令时执行的任务或功能。一个类是一组相似的对象。如果把对象类比于名词，那属性就可类比于描述一个对象特征的形容词。对象可以具有称为状态的特定属性，通常一个对象的状态用于描述该对象的当前状态。一个类中的所有对象共享共同的属性和方法，所以一个类就像个蓝图，或该类中所有对象的模板。","multi":0,"questionType":1,"answer":"A","chooseItem":["796234512911585281"],"itemList":[{"id":"796234512911585281","questionId":"796234511858814977","content":" state","answer":1,"chooseValue":"A"},{"id":"796234512936751105","questionId":"796234511858814977","content":" constant","answer":0,"chooseValue":"B"},{"id":"796234512961916929","questionId":"796234511858814977","content":" instance","answer":0,"chooseValue":"C"},{"id":"796234512987082753","questionId":"796234511858814977","content":" member","answer":0,"chooseValue":"D"}],"userAnswer":null,"userChooseItem":null,"answerCorrect":null,"userCollect":null}]}}