Solution Manual of Systems Analysis and Design (10th Edition) by Kenneth Kendall and Julie Kendall

SOLUTION MANUAL for Systems Analysis and Design
10th Edition by Kendall Kenneth and Kendall Julie,
All Chapters 1 - 16

,TABLE OF CONTENTS
I. Systems Analysis Fundamentals

1. Systems, Roles, and Development Methodologies
2. Understanding and Modeling Organization Systems
3. Project Management

II. Information Requirements Analysis

4. Information Gathering: Interactive Methods
5. Information Gathering: Unobtrusive Methods
6. Agile Modeling, Prototyping, and Scrum

III. The Analysis Process

7. Using Data Flow Diagrams
8. Analyzing Systems Using Data Dictionaries
9. Process Specifications and Structured Decisions
10. Object-Oriented Systems Analysis and Design Using UML

IV. The Essentials of Design

11. Designing Effective Output
12. Designing Effective Input
13. Designing Databases
14. Human-Computer Interaction and UX Design

V. Quality Assurance and Implementation

15. Designing Accurate Data Entry Procedures
16. Quality Assurance and Implementation

,Chapter 1
Understanding and Modeling Organizational Systems
Key Points and Objectives

1. Organizations are complex systems composed of interrelated and interdependent subsystems.


2. System and subsystem boundaries and environments have an impact on information system analysis anddesign.


3. Systems are described as either open, with free flowing information, or closed with restricted access to
information.


4. A virtual organization is one that has parts of the organization in different physical locations. They usecomputer
networks and communications technology to work on projects. Advantages of a virtual organization are:



A. Reduced costs of physical facilities
B. More rapid response to customer needs
C. Flexibility for employees to care for children or aging parents


5. Enterprise systems or Enterprise Resource Planning (ERP) describes an integrated organizational information
system. The software helps the flow of information between the functional areas within theorganization.

6. ERP can affect every aspect of the organization, such as:

A. Design of employees’ work
B. Skills required for job competency
C. Strategic positioning of the company

7. Many issues must be overcome for the ERP installation is to be declared a success:

A. User acceptance
B. Integration with legacy systems and the supply chain
C. Upgrading functionality (and complexity) of ERP modules
D. Reorganizing work life of users and decision makers
E. Expanded reach across several organizations
F. Strategic repositioning of the company


8. A context-level data flow diagram is an important tool for showing data used and information produced by asystem. It
provides an overview of the setting or environment the system exists within—which entities supply and receive
data/information.

9. The context-level data flow diagram is one way to show scope, or what is to be included in the system. Theproject has
a budget that helps to define scope.

, 10. Entity-
relationship diagrams help the analyst understand the organizational system and the data stored by theorganization.
ZI ZI ZI ZI ZI ZI ZI ZI ZI ZI ZI ZI ZI ZI IZ




11. There are three types of entities:
ZI ZI ZI ZI ZI




A. Fundamental entity, describing a person, place, or thing. ZI ZI ZI ZI ZI ZI ZI



B. Associative entity (also called a gerund, junction, intersection, or concatenated entity), joining twoentities. It
ZI ZI ZI ZI ZI ZI ZI ZI ZI ZI ZI ZI IZ ZI



can only exist between two entities.
ZI ZI ZI ZI ZI ZI



C. Attributive entity, to describe attributes and repeating groups.
ZI ZI ZI ZI ZI ZI ZI




12. Relationships are shown with a zero or circle representing none, a vertical line representing one, or crow’sfoot repres
ZI ZI ZI ZI ZI ZI ZI ZI ZI ZI ZI ZI ZI ZI ZI ZI IZ ZI



enting many and can be:
ZI ZI ZI ZI




A. One to one ZI ZI



B. One to many ZI ZI



C. Many to many ZI ZI




13. A use case diagram reflects the view of the system from the perspective of a user outside of the system.
ZI ZI ZI ZI ZI ZI ZI ZI ZI ZI ZI ZI ZI ZI ZI ZI ZI ZI ZI




14. A use case model partitions the way the system works into behaviors, services, and responses that aresignificant t
ZI ZI ZI ZI ZI ZI ZI ZI ZI ZI ZI ZI ZI ZI ZI ZI IZ ZI



o the users of the system.
ZI ZI ZI ZI ZI




15. A use case diagram has symbols for:
ZI ZI ZI ZI ZI ZI




A. An actor, the role of a user of the system
ZI ZI ZI ZI ZI ZI ZI ZI ZI



B. The use case representing a sequence of transactions in a system
ZI ZI ZI ZI ZI ZI ZI ZI ZI ZI




16. There are two kinds of use cases:
ZI ZI ZI ZI ZI ZI




A. Primary, the standard flow of events within a system that describe a standard system behavior
ZI ZI ZI ZI ZI ZI ZI ZI ZI ZI ZI ZI ZI ZI



B. Use case scenarios that describe variations of the primary use case
ZI ZI ZI ZI ZI ZI ZI ZI ZI ZI




17. There are four active behavioral relationships:
ZI ZI ZI ZI ZI




A. Communicates—used to connect an actor to a use case. ZI ZI ZI ZI ZI ZI ZI ZI




B. Includes—
describes the situation where a use case contains a behavior that is common tomore than one use case.
ZI ZI ZI ZI ZI ZI ZI ZI ZI ZI ZI ZI ZI IZ ZI ZI ZI ZI




C. Extends—
describes the situation where one use case possesses the behavior that allowsthe new use case to handle a va
ZI ZI ZI ZI ZI ZI ZI ZI ZI ZI ZI IZ ZI ZI ZI ZI ZI ZI ZI



riation or exception. ZI ZI




D. Generalizes—implies that one thing is more typical than the other thing. ZI ZI ZI ZI ZI ZI ZI ZI ZI ZI