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 2
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 hdiagrams hhelp hthe hanalyst hunderstand hthe horganizational hsystem hand hthe hdata hstored hby hthe
horganization.
11. There hare hthree htypes hof hentities:
A. Fundamental hentity, hdescribing ha hperson, hplace, hor hthing.
B. Associative hentity h(also hcalled ha hgerund, hjunction, hintersection, hor hconcatenated hentity), hjoining htwo
hentities. hIt hcan honly hexist hbetween htwo hentities.
C. Attributive hentity, hto hdescribe hattributes hand hrepeating hgroups.
12. Relationships hare hshown hwith ha hzero hor hcircle hrepresenting hnone, ha hvertical hline hrepresenting hone, hor hcrow’s
hfoot hrepresenting hmany hand hcan hbe:
A. One hto hone
B. One hto hmany
C. Many hto hmany
13. A huse hcase hdiagram hreflects hthe hview hof hthe hsystem hfrom hthe hperspective hof ha huser houtside hof hthe hsystem.
14. A huse hcase hmodel hpartitions hthe hway hthe hsystem hworks hinto hbehaviors, hservices, hand hresponses hthat hare
hsignificant hto hthe husers hof hthe hsystem.
15. A huse hcase hdiagram hhas hsymbols hfor:
A. An hactor, hthe hrole hof ha huser hof hthe hsystem
B. The huse hcase hrepresenting ha hsequence hof htransactions hin ha hsystem
16. There hare htwo hkinds hof huse hcases:
A. Primary, hthe hstandard hflow hof hevents hwithin ha hsystem hthat hdescribe ha hstandard hsystem hbehavior
B. Use hcase hscenarios hthat hdescribe hvariations hof hthe hprimary huse hcase
17. There hare hfour hactive hbehavioral hrelationships:
A. Communicates—used h to h connect h an h actor h to h a h use h case.
B. Includes—describes hthe hsituation h where ha h use h case h contains h a h behavior hthat h is h common htohmore hthan
hone huse hcase.
C. Extends—describes h the hsituation h where h one huse hcase h possesses h the h behavior h that h allowshthe hnew huse
hcase hto hhandle ha hvariation hor hexception.
D. Generalizes—implies hthat h one hthing h is h more h typical hthan h the h other h thing.
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 2
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 hdiagrams hhelp hthe hanalyst hunderstand hthe horganizational hsystem hand hthe hdata hstored hby hthe
horganization.
11. There hare hthree htypes hof hentities:
A. Fundamental hentity, hdescribing ha hperson, hplace, hor hthing.
B. Associative hentity h(also hcalled ha hgerund, hjunction, hintersection, hor hconcatenated hentity), hjoining htwo
hentities. hIt hcan honly hexist hbetween htwo hentities.
C. Attributive hentity, hto hdescribe hattributes hand hrepeating hgroups.
12. Relationships hare hshown hwith ha hzero hor hcircle hrepresenting hnone, ha hvertical hline hrepresenting hone, hor hcrow’s
hfoot hrepresenting hmany hand hcan hbe:
A. One hto hone
B. One hto hmany
C. Many hto hmany
13. A huse hcase hdiagram hreflects hthe hview hof hthe hsystem hfrom hthe hperspective hof ha huser houtside hof hthe hsystem.
14. A huse hcase hmodel hpartitions hthe hway hthe hsystem hworks hinto hbehaviors, hservices, hand hresponses hthat hare
hsignificant hto hthe husers hof hthe hsystem.
15. A huse hcase hdiagram hhas hsymbols hfor:
A. An hactor, hthe hrole hof ha huser hof hthe hsystem
B. The huse hcase hrepresenting ha hsequence hof htransactions hin ha hsystem
16. There hare htwo hkinds hof huse hcases:
A. Primary, hthe hstandard hflow hof hevents hwithin ha hsystem hthat hdescribe ha hstandard hsystem hbehavior
B. Use hcase hscenarios hthat hdescribe hvariations hof hthe hprimary huse hcase
17. There hare hfour hactive hbehavioral hrelationships:
A. Communicates—used h to h connect h an h actor h to h a h use h case.
B. Includes—describes hthe hsituation h where ha h use h case h contains h a h behavior hthat h is h common htohmore hthan
hone huse hcase.
C. Extends—describes h the hsituation h where h one huse hcase h possesses h the h behavior h that h allowshthe hnew huse
hcase hto hhandle ha hvariation hor hexception.
D. Generalizes—implies hthat h one hthing h is h more h typical hthan h the h other h thing.
