0% found this document useful (0 votes)
4 views3 pages

Week 12 - Mini Test - Solutions

The document outlines a test for Chapter 13, focusing on systems analysis and design concepts, including definitions and processes such as feasibility studies, conversion strategies, and prototyping. It includes fill-in-the-blank questions and essay prompts that require explanations of systems analysis purposes, development approaches, and the advantages and disadvantages of prototyping. Key aspects discussed involve user involvement, iterative design, and the identification of information requirements.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
4 views3 pages

Week 12 - Mini Test - Solutions

The document outlines a test for Chapter 13, focusing on systems analysis and design concepts, including definitions and processes such as feasibility studies, conversion strategies, and prototyping. It includes fill-in-the-blank questions and essay prompts that require explanations of systems analysis purposes, development approaches, and the advantages and disadvantages of prototyping. Key aspects discussed involve user involvement, iterative design, and the identification of information requirements.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

Week 12 – Chapter 13 Test (Con’t)

(60 minutes)
Part 1: Fill in the blanks (5 points, 0.5 points each)

1. A systems analysis includes a(n) feasibility study that is used to determine


whether the solution is achievable, from a financial, technical, and organizational
standpoint.

2. Information requirements contain a detailed statement of the information


needs that a new system must satisfy; identifies who needs what information, and
when, where, and how the information is needed.

3. A(n) systems design is the model or blueprint for an information system


solution and consists of all the specifications that will deliver the functions
identified during systems analysis.

4. Conversion is the process of changing from the old system to the new
system.

5. The conversion strategy in which the old and new systems are run
concurrently is called a(n) parallel strategy.

6. Process specifications describe the transformation occurring within the


lowest level of the data flow diagrams.

7. Computer-aided software (systems) engineering (CASE) provides


software tools to automate the methodologies to reduce the amount of repetitive
work in systems development.

8. A(n) request for proposal (RFP) is a detailed list of questions submitted to


external vendors to determine how well they meet the organization’s specific
requirements.

9. Joint application design is a process used to accelerate the generation of


information requirements by having end-users and information system specialists
work together in intensive interactive design sessions.

10. Web services loosely coupled, reusable software components based on


extensible markup language (XML) and other open protocols and standards that
enable one application to communicate with another with no custom
programming required.
Part 2: Essay Questions (5 points)

1. What is the purpose of systems analysis? What does the systems analyst
do to achieve these goals? (1.5 points)

It consists of defining the problem, identifying its causes, specifying the solution,
and identifying the information requirements that must be met by a system solution.

The system analyst creates a road map of the existing organization and systems,
identifying the primary owners and users of data in the organization. From this
organizational analysis, the systems analyst details the problems of existing systems.
By examining documents, work papers, and procedures; observing system
operations; and interviewing key users of the systems, the analyst can identify the
problem areas and objectives a solution would achieve. Often the solution requires
building a new information system or improving an existing one.

The systems analysis itself would include a feasibility study to determine whether
the solution suggested would be achievable from a financial, technical, and
organizational standpoint.

2. List the identifying features of each of the five systems development


approaches? (1.5 points)

Systems lifecycle. Sequential step-by-step formal process, written specification


and approvals, limited role of users
Prototyping. Requirements specified dynamically with experimental system;
rapid, informal, and iterative process; users continually interact with the prototype
Applications software package. Commercial software eliminates the need for
internally developed software programs
End-user development. Systems created by end users using fourth-generation
software tools, rapid and informal, minimal role of information systems specialists
Outsourcing. Systems built and sometimes operated by an external vendor

3. What are the advantages and disadvantages of prototyping? Describe the


steps in prototyping. Give at least two circumstances under which
prototyping might be useful? (2 points)

Prototyping is most useful when there is some uncertainty about requirements or


design solutions. Because prototyping encourages intense end-user involvement
throughout the process, it is more likely to produce systems that fulfill user
requirements. Working prototype systems can be developed very rapidly and
inexpensively.
Rapid prototyping can gloss over essential steps in systems development. If the
completed prototype works reasonably well, management may not see the need for
reprogramming, redesigned, full documentation in testing to build a polished
production system. This can backfire later with large quantities of data or large
numbers of users in a production environment.

The steps in prototyping are: identify the user’s basic requirements, develop an
initial prototype, use the prototype, revise and enhance the prototype.

Prototyping might be especially useful in designing end-user interfaces, or


situations in which the users have no clear ideas of what their information
requirements are.

You might also like