Ans: True
Response: See Introduction
Difficulty: easy
Systems analysts are generally experts in business, finance, and application development.
Ans: False
Response: See The Systems Analyst
Difficulty: medium
When compared to a business analyst, the systems analyst will identify how the system will provide business value.
Ans: False
Response: See Project Identification and Initiation
Difficulty: medium
The business analyst role focuses on the business issues surrounding the system.
Ans: False
Response: See The Systems Analyst
Difficulty: easy
When compared to a systems analyst, the business analyst will probably have more responsibility for determining business value.
Ans: True
Response: See Project Identification and Initiation
Difficulty: easy
Because of the need to be focused on providing information about the business value of a system, a systems analyst will probably have much training or experience in programming or application development.
Ans: False
Response: See The Systems Analyst
Difficulty: easy
The requirements analyst role includes complete and accurate determination of what the system requirements consist of for all stakeholders.
Ans: True
Response: See The Systems Analyst
Difficulty: easy
The SDLC generally can be broken into four phases: planning, analysis, design and implementation.
Ans: True
Response: See The Systems Development Life Cycle
Difficulty: easy
In SDLC, analysis is generally divided into three steps: understanding the as-is system; developing a cost-benefit analysis; and understanding the technical feasibility.
Ans: False
Response: See The Systems Development Life Cycle
Difficulty: easy
Anne has asked users and managers to identify problems with the as-is system and to describe how to solve them in the to-be system. She is probably in the analysis phase of SDLC.
Ans. True
Response: See The Systems Development Life Cycle
Difficulty: easy
Determining business requirements is generally done in the planning phase of the SDLC.
Ans: False
Response: See Figure 1-3: Systems Development Life Cycle Phases
Difficulty: easy
Difficulty: easy
The primary output of the planning phase is the system request.
Ans: True
Response: See Figure 1-3: Systems Development Life Cycle Phases
Difficulty: easy
The primary output of the analysis phase is the system proposal.
Ans: True
Response: See Figure 1-3: Systems Development Life Cycle Phases
Difficulty: easy
The normal sequence of SDLC phase outputs (from beginning to end) would be: system request; system proposal; system specifications; and installed system.
Ans: True
Response: See Figure 1-3: Systems Development Life Cycle Phases
Difficulty: easy
The question ‘Can we build it’ is asked in the design phase.
Ans: False
Response: See The Systems Development Life Cycle
Difficulty: easy
Interviewing is generally done in the analysis phase of the SDLC.
Ans: True
Response: See Figure 1-3: Systems Development Life Cycle Phases
Difficulty: easy
Juan is creating use cases. He is working in the design phase of the SDLC.
Ans: False
Response: See Figure 1-3: Systems Development Life Cycle Phases
Difficulty: easy
The planning phase of the SDLC will have two steps: project initiation and requirements determination.
Ans: False
Response: See Planning
Difficulty: easy
The three feasibility analyses in the text were: organizational feasibility, technical feasibility, and economic feasibility.
Ans: True
Response: See Planning
Difficulty: easy
Developing navigation methods, database, and file specifications and what architecture to use would occur in the design phase of the SDLC.