SOLUTION MANUAL
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 and design.
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 use computer 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 the organization.
6. ERP fcan faffect fevery faspect fof fthe forganization, fsuch fas:
A. Design fof femployees’ fwork
B. Skills frequired ffor fjob fcompetency
C. Strategic fpositioning fof fthe fcompany
7. Many fissues fmust fbe fovercome ffor fthe fERP finstallation fis fto fbe fdeclared fa fsuccess:
A. User facceptance
B. Integration fwith flegacy fsystems fand fthe fsupply fchain
C. Upgrading ffunctionality f(and fcomplexity) fof fERP fmodules
D. Reorganizing fwork flife fof fusers fand fdecision fmakers
E. Expanded freach facross fseveral forganizations
F. Strategic frepositioning fof fthe fcompany
8. A fcontext-level fdata fflow fdiagram fis fan fimportant ftool ffor fshowing fdata fused fand
finformation fproduced fby fa f system. fIt fprovides fan foverview fof fthe fsetting for fenvironment fthe
fsystem fexists fwithin—which fentities fsupply f and freceive fdata/information.
, 9. The fcontext-level fdata fflow fdiagram fis fone fway fto fshow fscope, for fwhat fis fto fbe fincluded
fin fthe fsystem. fThe f project fhas fa fbudget fthat fhelps fto fdefine fscope.
10. Entity-relationship fdiagrams fhelp fthe fanalyst funderstand fthe forganizational fsystem fand
fthe fdata fstored fby fthe f organization.
11. There fare fthree ftypes fof fentities:
A. Fundamental fentity, fdescribing fa fperson, fplace, for fthing.
B. Associative fentity f(also fcalled fa fgerund, fjunction, fintersection, for fconcatenated
fentity), fjoining ftwo f entities. fIt fcan fonly fexist fbetween ftwo fentities.
C. Attributive fentity, fto fdescribe fattributes fand frepeating fgroups.
12. Relationships fare fshown fwith fa fzero for fcircle frepresenting fnone, fa fvertical fline
frepresenting fone, for fcrow’sfoot f representing fmany fand fcan fbe:
A. One fto fone
B. One fto fmany
C. Many fto fmany
13. A fuse fcase fdiagram freflects fthe fview fof fthe fsystem ffrom fthe fperspective fof fa fuser foutside
fof fthe fsystem.
14. A fuse fcase fmodel fpartitions fthe fway fthe fsystem fworks finto fbehaviors, fservices, fand
fresponses fthat fare f significant fto fthe fusers fof fthe fsystem.
15. A fuse fcase fdiagram fhas fsymbols ffor:
A. An factor, fthe frole fof fa fuser fof fthe fsystem
B. The fuse fcase frepresenting fa fsequence fof ftransactions fin fa fsystem
16. There fare ftwo fkinds fof fuse fcases:
A. Primary, fthe fstandard fflow fof fevents fwithin fa fsystem fthat fdescribe fa fstandard
fsystem fbehavior
B. Use fcase fscenarios fthat fdescribe fvariations fof fthe fprimary fuse fcase
17. There fare ffour factive fbehavioral frelationships:
A. Communicates—used f to fconnect f an f actor f to f a f use f case.
B. Includes—describes fthe fsituation f where fa fuse fcase f contains f a fbehavior fthat f is
f common ftomore fthan f one fuse fcase.
C. Extends—describes fthe fsituation fwhere f one fuse fcase f possesses f the f behavior f that
f allowsthe fnew fuse f case fto fhandle fa fvariation for fexception.
D. Generalizes—implies f that f one fthing f is fmore ftypical f than fthe f other f thing.
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 and design.
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 use computer 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 the organization.
6. ERP fcan faffect fevery faspect fof fthe forganization, fsuch fas:
A. Design fof femployees’ fwork
B. Skills frequired ffor fjob fcompetency
C. Strategic fpositioning fof fthe fcompany
7. Many fissues fmust fbe fovercome ffor fthe fERP finstallation fis fto fbe fdeclared fa fsuccess:
A. User facceptance
B. Integration fwith flegacy fsystems fand fthe fsupply fchain
C. Upgrading ffunctionality f(and fcomplexity) fof fERP fmodules
D. Reorganizing fwork flife fof fusers fand fdecision fmakers
E. Expanded freach facross fseveral forganizations
F. Strategic frepositioning fof fthe fcompany
8. A fcontext-level fdata fflow fdiagram fis fan fimportant ftool ffor fshowing fdata fused fand
finformation fproduced fby fa f system. fIt fprovides fan foverview fof fthe fsetting for fenvironment fthe
fsystem fexists fwithin—which fentities fsupply f and freceive fdata/information.
, 9. The fcontext-level fdata fflow fdiagram fis fone fway fto fshow fscope, for fwhat fis fto fbe fincluded
fin fthe fsystem. fThe f project fhas fa fbudget fthat fhelps fto fdefine fscope.
10. Entity-relationship fdiagrams fhelp fthe fanalyst funderstand fthe forganizational fsystem fand
fthe fdata fstored fby fthe f organization.
11. There fare fthree ftypes fof fentities:
A. Fundamental fentity, fdescribing fa fperson, fplace, for fthing.
B. Associative fentity f(also fcalled fa fgerund, fjunction, fintersection, for fconcatenated
fentity), fjoining ftwo f entities. fIt fcan fonly fexist fbetween ftwo fentities.
C. Attributive fentity, fto fdescribe fattributes fand frepeating fgroups.
12. Relationships fare fshown fwith fa fzero for fcircle frepresenting fnone, fa fvertical fline
frepresenting fone, for fcrow’sfoot f representing fmany fand fcan fbe:
A. One fto fone
B. One fto fmany
C. Many fto fmany
13. A fuse fcase fdiagram freflects fthe fview fof fthe fsystem ffrom fthe fperspective fof fa fuser foutside
fof fthe fsystem.
14. A fuse fcase fmodel fpartitions fthe fway fthe fsystem fworks finto fbehaviors, fservices, fand
fresponses fthat fare f significant fto fthe fusers fof fthe fsystem.
15. A fuse fcase fdiagram fhas fsymbols ffor:
A. An factor, fthe frole fof fa fuser fof fthe fsystem
B. The fuse fcase frepresenting fa fsequence fof ftransactions fin fa fsystem
16. There fare ftwo fkinds fof fuse fcases:
A. Primary, fthe fstandard fflow fof fevents fwithin fa fsystem fthat fdescribe fa fstandard
fsystem fbehavior
B. Use fcase fscenarios fthat fdescribe fvariations fof fthe fprimary fuse fcase
17. There fare ffour factive fbehavioral frelationships:
A. Communicates—used f to fconnect f an f actor f to f a f use f case.
B. Includes—describes fthe fsituation f where fa fuse fcase f contains f a fbehavior fthat f is
f common ftomore fthan f one fuse fcase.
C. Extends—describes fthe fsituation fwhere f one fuse fcase f possesses f the f behavior f that
f allowsthe fnew fuse f case fto fhandle fa fvariation for fexception.
D. Generalizes—implies f that f one fthing f is fmore ftypical f than fthe f other f thing.
