SOLUTION MANUAL For Systems Analysis and Design, 10th Edition by Kendall Kenneth and Kendall Julie, Verified Chapters 1 - 16, Complete Newest Version

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

,TABLE OF CONTENTS SB SB




I. Systems Analysis Fundamentals
SB SB SB




1. Systems, Roles, and Development Methodologies
SB SB SB SB




2. Understanding and Modeling Organization Systems SB SB SB SB




3. Project Management SB




II. Information Requirements Analysis
SB SB SB




4. Information Gathering: Interactive Methods SB SB SB




5. Information Gathering: Unobtrusive Methods SB SB SB




6. Agile Modeling, Prototyping, and Scrum
SB SB SB SB




III. The Analysis Process
SB SB SB




7. Using Data Flow Diagrams
SB SB SB




8. Analyzing Systems Using Data Dictionaries
SB SB SB SB




9. Process Specifications and Structured Decisions
SB SB SB SB




10. Object-Oriented Systems Analysis and Design Using UML SB SB SB SB SB SB




IV. The Essentials of Design
SB SB SB SB




11. Designing Effective Output SB SB




12. Designing Effective Input SB SB




13. Designing Databases SB




14. Human-Computer Interaction and UX Design SB SB SB SB




V. Quality Assurance and Implementation
SB SB SB SB




15. Designing Accurate Data Entry Procedures
SB SB SB SB




16. Quality Assurance and Implementation
SB SB SB

,Chapter 2 SB




Understanding and Modeling Organizational Systems SB SB SB SB




Key Points and Objectives SB SB SB




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




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




3. Systems are described as either open, with free flowing information, or closed with restricted access toinformation.
SB SB SB SB SB SB SB SB SB SB SB SB SB SB SB B
S




4. A virtual organization is one that has parts of the organization in different physical locations. They usecomputer net
SB SB SB SB SB SB SB SB SB SB SB SB SB SB SB SB B
S SB




works and communications technology to work on projects. Advantages of a virtual organization are:
SB SB SB SB SB SB SB SB SB SB SB SB SB




A. Reduced costs of physical facilities SB SB SB SB




B. More rapid response to customer needs
SB SB SB SB SB




C. Flexibility for employees to care for children or aging parents
SB SB SB SB SB SB SB SB SB




5. Enterprise systems or Enterprise Resource Planning (ERP) describes an integrated organizational information system
SB SB SB SB SB SB SB SB SB SB SB SB




. The software helps the flow of information between the functional areas within theorganization.
SB SB SB SB SB SB SB SB SB SB SB SB SB B
S




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




A. Design of employees’ work SB SB SB




B. Skills required for job competency
SB SB SB SB




C. Strategic positioning of the company SB SB SB SB




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




A. User acceptance SB




B. Integration with legacy systems and the supply chain SB SB SB SB SB SB SB




C. Upgrading functionality (and complexity) of ERP modules SB SB SB SB SB SB




D. Reorganizing work life of users and decision makers SB SB SB SB SB SB SB




E. Expanded reach across several organizations SB SB SB SB




F. Strategic repositioning of the company SB SB SB SB




8. A context-
SB




level data flow diagram is an important tool for showing data used and information produced by asystem. It provides an ove
SB SB SB SB SB SB SB SB SB SB SB SB SB SB SB SB B
S SB SB SB SB




rview of the setting or environment the system exists within—which entities supply and receive data/information.
SB SB SB SB SB SB SB SB SB SB SB SB SB SB




9. The context- SB




level data flow diagram is one way to show scope, or what is to be included in the system. Theproject has a budget that hel
SB SB SB SB SB SB SB SB SB SB SB SB SB SB SB SB SB SB SB B
S SB SB SB SB SB




ps to define scope.
SB SB SB

, 10. Entity-relationship diagrams help the analyst understand the organizational system and the data stored by theorganization.
SB SB SB SB SB SB SB SB SB SB SB SB SB SB B
S




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




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




B. Associative entity (also called a gerund, junction, intersection, or concatenated entity), joining twoentities. It c
SB SB SB SB SB SB SB SB SB SB SB SB B
S SB SB




an only exist between two entities.
SB SB SB SB SB




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




12. Relationships are shown with a zero or circle representing none, a vertical line representing one, or crow’sfoot represen
SB SB SB SB SB SB SB SB SB SB SB SB SB SB SB SB B
S SB




ting many and can be:
SB SB SB SB




A. One to one SB SB




B. One to many SB SB




C. Many to many SB SB




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




14. A use case model partitions the way the system works into behaviors, services, and responses that aresignificant to t
SB SB SB SB SB SB SB SB SB SB SB SB SB SB SB SB B
S SB SB




he users of the system.
SB SB SB SB




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




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




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




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




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




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




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




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




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




C. Extends—
describes the situation where one use case possesses the behavior that allowsthe new use case to handle a varia
SB SB SB SB SB SB SB SB SB SB SB B
S SB SB SB SB SB SB SB




tion or exception. SB SB




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