The purpose of the systems analysis phase is to build a logical model of the new system.The first step is（71），where you investigate business processes and document what the new system must do to sati

●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 effectivelyin 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 functiog.information system. Whilethe end productof jAD is a(an)(73),theendproduct of RAD is the (74) .The RAD model consists offour phases. During the(75),users interact with systems analysts and develop models and prototypes that represent all system processes, outputs, and inputs.

(71) A. structured analysis

B. object-oriented analysis

C. prototype analysis

D. process analysis

(72) A. initial scope definition

B. requirements modeling process

C. object modeling process

D. architecture design process

(73) A. data flow diagram

B. entity relationstip model

C. requirements model

D. object model

(74) A. system proposal

B. system design model

C. new system architecture

D. new information system

(75) A. requirements planning phase

B. user design phase

C. construction phase

D. cutover phase

The purpose of systems analysis phase is to build a logical model of the new system. The first step is（ ）, 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（ ）. 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（ ）, which describes management and user requirements, costs and benefits, and outlines alternative development strategies. 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 the（ ）, which programmers will use to transform the logical design into program modules and code. The deliverable for this phase is the（ ）, which is presented to management and users for review and approval.

A.System logical modelingB.use case modelingC.requirements modelingD.application modeling A.systems planning phaseB.systems modeling phaseC.systems analysis phaseD.systems design phase A.system charterB.system scope definitionC.system blueprintD.system requirement document A.application architectureB.system data modelC.system process modelD.implement environment A.system architecture descriptionB.system design specificationC.system technique architectureD.physical deployment architecture

● 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.

（71）

A. analysis phase

B. design phase

C. implementation phase

D. maintenance phase

（72）

A. main symptom

B. root problem

C. final blueprint

D. data specification

（73）

A. hardware environment

B. testing environment

C. software environment

D. business environment

（74）

A. logical models

B. physical models

C. design models

D. implementation models

（75）

A. hardware and software specification

B. system performance specification

C. formal requirements definition

D. general problem statement

●In general,atypical (71) model is composed of several phases, such as requirements analysis phase, generaUdetailed design phase, implementation phase, system acceptance testing phase.

(71)

A. waterfall

B.incremental

C.spiral

D.prototyping

Accelerated analysis approaches emphasize the construction of (71) to more rapidly identify business and user requirements for a new system. As an accelerated analysis technology,(72) reads the program code and automatically generates the equivalent system model, and the code can be obtained from (73) All system analysis approaches require some form. of (74) which includes those techniques to be used to identify or extract system problems and solution requirements from user community.(75) is a classical set of techniques used to collect information about system problems, opportunities, solution requirements, and priorities.

A．object models

B．prototypes

C．use cases

D．components

There is nothing in this world constant but inconstancy．--SWIFT

Project after project designs a set of algorithms and then plunges into construction of customer-deliverable software on a schedule that demands delivery of the first thing built．

In most projects,the first system built is （71） usable,It may be too slow,too big,awkward to use,or all three．There is no （72） but to start again,smarting but smarter,and build a redesigned version in which these problems are solved．The discard and （73） may be done in one lump,or it may be done piece-by-piece．But all large-system experience shows that it will be done．Where a new system concept or new technology is used,one has to build a system to throw away,for even the best planning is not so omniscient（全知的）as to get it right the first time．

The management question,therefore ,is not whether to build a pilot system and throw it away．You will do that．The only question is whether to plan in advance to build a （74）,or to promise to deliver the throwaway to customers．Seen this way,the answer is much clearer．Delivering that throwaway to customers buys time,but it does so only at the （75） of agony（极大痛苦）for the user,distraction for the builders while they do the redesign,and a bad reputation for the product that best redesign will find hard to live down．

Hence plan to throw one away;you will,anyhow．

71.()

A.almost

B.often

C.usually

D.barely

A address

B location

C program

D application

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 ny current system,identifies (71) , and develops a concept for the new system. This phase as three steps: first, (72) is developed to guide the project team's efforts. It usually ncludes an analysis of the current system and its problems, and the ways to design a new ystem. The next step is (73) The analysis ofthis information - in conjunction withinput rom the project sponsor and many other people - leads to the development of a concept for a ew system. The system concept is then used as a basis to develop a set ofbusiness analysis odels 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 nderlying business process. Last, the analyses, system concepts, and models are combined nto a document called the (75), which is presented to the project sponsor and other key ecision makers that decide whether the project should continue to move forward

A.improvementopportunities

B.logicalmodel

C.systemrequirements

D.systemarchitecture@@@SXB@@@A.a user manual

B.an analysis strategy

C. an analysis use case

D.a design user case@@@SXB@@@A.project scope definition

B.prob,lems analysis

C.decisionanalysis

D.requirementsgathering@@@SXB@@@A.dataandprocesses

B.systeminfrastructures

C.externalagents

D.systemsoftware@@@SXB@@@A.requirementsstatement

B.designspecification

C.systemproposal

D.project charter

试题(71)～(75)

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 ny current system,identifies (71) , and develops a concept for the new system. This phase as three steps: first, (72) is developed to guide the project team's efforts. It usually ncludes an analysis of the current system and its problems, and the ways to design a new ystem. The next step is (73) The analysis ofthis information - in conjunction withinput rom the project sponsor and many other people - leads to the development of a concept for a ew system. The system concept is then used as a basis to develop a set ofbusiness analysis odels 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 nderlying business process. Last, the analyses, system concepts, and models are combined nto a document called the (75), which is presented to the project sponsor and other key ecision makers that decide whether the project should continue to move forward.

(71) A. improvementopportunities

B. logicalmodel

C. systemrequirements

D. systemarchitecture

(72) A. a user manual

B. an analysis strategy

C. an analysis use case

D. a design user case

(73) A. project scope definition

B. prob,lems analysis

C. decisionanalysis

D. requirementsgathering

(74) A. dataandprocesses

B. systeminfrastructures

C. externalagents

D. systemsoftware

(75) A. requirementsstatement

B. designspecification

C. systemproposal

D. project charter