SOLUTION MANUAL For
Systems Analysis And
Design 11th Edition By
Kendall Kenneth And Kendall
Julie, All CHAPTER:s 1 - 16
1
,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
2
,CHAPTER: 2
UNDERSTANDING AND MODELING
ORGANIZATIONALSYSTEMS
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 Andd
i esign.
3. Systems Are Described As Either Open, With Free Flowing Information, Or Closed
With Restricted Access Toinformation.
4. A Virtual Organization Is One That Has Parts Of The Organization In Different
Physical Locations. They Useci omputer 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 Theiorganization.
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
3
, 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 AS i ystem. 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.
11. There Are Three Types Of Entities:
A. Fundamental Entity, Describing A Person, Place, Or Thing.
B. Associative Entity (Also Called A Gerund, Junction, Intersection, Or
Concatenated Entity), Joining Twoei ntities. It Can Only Exist Between Two
Entities.
C. Attributive Entity, To Describe Attributes And Repeating Groups.
12. Relationships Are Shown With A Zero Or Circle Representing None, A Vertical
Line Representing One, Or Crow’sfoot Representing Many And Can Be:
A. One To One
B. One To Many
C. Many To Many
13. A Use Case Diagram Reflects The View Of The System From The Perspective Of A User Outside
Of The System.
14. A Use Case Model Partitions The Way The System Works Into Behaviors, Services,
And Responses That Aresi ignificant To The Users Of The System.
15. A Use Case Diagram Has Symbols For:
A. An Actor, The Role Of A User Of The System
B. The Use Case Representing A Sequence Of Transactions In A System
16. There Are Two Kinds Of Use Cases:
4
Systems Analysis And
Design 11th Edition By
Kendall Kenneth And Kendall
Julie, All CHAPTER:s 1 - 16
1
,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
2
,CHAPTER: 2
UNDERSTANDING AND MODELING
ORGANIZATIONALSYSTEMS
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 Andd
i esign.
3. Systems Are Described As Either Open, With Free Flowing Information, Or Closed
With Restricted Access Toinformation.
4. A Virtual Organization Is One That Has Parts Of The Organization In Different
Physical Locations. They Useci omputer 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 Theiorganization.
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
3
, 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 AS i ystem. 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.
11. There Are Three Types Of Entities:
A. Fundamental Entity, Describing A Person, Place, Or Thing.
B. Associative Entity (Also Called A Gerund, Junction, Intersection, Or
Concatenated Entity), Joining Twoei ntities. It Can Only Exist Between Two
Entities.
C. Attributive Entity, To Describe Attributes And Repeating Groups.
12. Relationships Are Shown With A Zero Or Circle Representing None, A Vertical
Line Representing One, Or Crow’sfoot Representing Many And Can Be:
A. One To One
B. One To Many
C. Many To Many
13. A Use Case Diagram Reflects The View Of The System From The Perspective Of A User Outside
Of The System.
14. A Use Case Model Partitions The Way The System Works Into Behaviors, Services,
And Responses That Aresi ignificant To The Users Of The System.
15. A Use Case Diagram Has Symbols For:
A. An Actor, The Role Of A User Of The System
B. The Use Case Representing A Sequence Of Transactions In A System
16. There Are Two Kinds Of Use Cases:
4
