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 dcan daffect devery daspect dof dthe dorganization, dsuch das:
A. Design dof demployees’ dwork
B. Skills drequired dfor djob dcompetency
C. Strategic dpositioning dof dthe dcompany
7. Many dissues dmust dbe dovercome dfor dthe dERP dinstallation dis dto dbe ddeclared da dsuccess:
A. User dacceptance
B. Integration dwith dlegacy dsystems dand dthe dsupply dchain
C. Upgrading dfunctionality d(and dcomplexity) dof dERP dmodules
D. Reorganizing dwork dlife dof dusers dand ddecision dmakers
E. Expanded dreach dacross dseveral dorganizations
F. Strategic drepositioning dof dthe dcompany
8. A dcontext-level ddata dflow ddiagram dis dan dimportant dtool dfor dshowing ddata d used dand
dinformation dproduced dby da d system. dIt dprovides dan doverview dof dthe dsetting d or
denvironment dthe dsystem dexists dwithin—which dentities d supply d and dreceive ddata/information.
, 9. The dcontext-level ddata dflow ddiagram dis done dway dto dshow dscope, dor dwhat dis dto dbe
d included din dthe dsystem. dThe d project dhas da dbudget dthat dhelps d to ddefine dscope.
10. Entity-relationship ddiagrams dhelp dthe danalyst dunderstand dthe dorganizational dsystem dand
dthe ddata dstored dby dthe d organization.
11. There dare dthree dtypes dof dentities:
A. Fundamental dentity, ddescribing da dperson, dplace, dor dthing.
B. Associative dentity d(also dcalled da dgerund, djunction, dintersection, dor
dconcatenated dentity), djoining d two d entities. dIt dcan donly dexist dbetween dtwo
dentities.
C. Attributive dentity, dto ddescribe dattributes dand drepeating dgroups.
12. Relationships dare dshown dwith da dzero dor dcircle drepresenting dnone, da dvertical dline
drepresenting d one, dor dcrow’sfoot d representing dmany dand dcan dbe:
A. One dto done
B. One dto dmany
C. Many dto dmany
13. A duse dcase ddiagram dreflects dthe dview dof dthe dsystem dfrom dthe dperspective dof da duser
doutside dof dthe dsystem.
14. A duse dcase dmodel dpartitions dthe dway dthe dsystem dworks dinto dbehaviors, dservices,
dand dresponses d that dare d significant dto dthe dusers dof d the dsystem.
15. A duse dcase ddiagram dhas dsymbols dfor:
A. An dactor, dthe drole dof da duser dof dthe dsystem
B. The duse dcase drepresenting da dsequence dof dtransactions din da dsystem
16. There dare dtwo dkinds dof duse dcases:
A. Primary, dthe dstandard dflow dof devents dwithin da dsystem dthat ddescribe da dstandard
dsystem dbehavior
B. Use dcase dscenarios dthat ddescribe dvariations dof dthe dprimary duse dcase
17. There dare dfour dactive dbehavioral drelationships:
A. Communicates—used d to d connect d an d actor d to d a d use d case.
B. Includes—describes dthe dsituation d where d a d use d case d contains d a d behavior d that
d is d common d tomore dthan d one duse dcase.
C. Extends—describes d the dsituation d where d one d use d case d possesses d the d behavior
d that d allowsthe dnew duse d case dto dhandle da dvariation dor dexception.
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 dcan daffect devery daspect dof dthe dorganization, dsuch das:
A. Design dof demployees’ dwork
B. Skills drequired dfor djob dcompetency
C. Strategic dpositioning dof dthe dcompany
7. Many dissues dmust dbe dovercome dfor dthe dERP dinstallation dis dto dbe ddeclared da dsuccess:
A. User dacceptance
B. Integration dwith dlegacy dsystems dand dthe dsupply dchain
C. Upgrading dfunctionality d(and dcomplexity) dof dERP dmodules
D. Reorganizing dwork dlife dof dusers dand ddecision dmakers
E. Expanded dreach dacross dseveral dorganizations
F. Strategic drepositioning dof dthe dcompany
8. A dcontext-level ddata dflow ddiagram dis dan dimportant dtool dfor dshowing ddata d used dand
dinformation dproduced dby da d system. dIt dprovides dan doverview dof dthe dsetting d or
denvironment dthe dsystem dexists dwithin—which dentities d supply d and dreceive ddata/information.
, 9. The dcontext-level ddata dflow ddiagram dis done dway dto dshow dscope, dor dwhat dis dto dbe
d included din dthe dsystem. dThe d project dhas da dbudget dthat dhelps d to ddefine dscope.
10. Entity-relationship ddiagrams dhelp dthe danalyst dunderstand dthe dorganizational dsystem dand
dthe ddata dstored dby dthe d organization.
11. There dare dthree dtypes dof dentities:
A. Fundamental dentity, ddescribing da dperson, dplace, dor dthing.
B. Associative dentity d(also dcalled da dgerund, djunction, dintersection, dor
dconcatenated dentity), djoining d two d entities. dIt dcan donly dexist dbetween dtwo
dentities.
C. Attributive dentity, dto ddescribe dattributes dand drepeating dgroups.
12. Relationships dare dshown dwith da dzero dor dcircle drepresenting dnone, da dvertical dline
drepresenting d one, dor dcrow’sfoot d representing dmany dand dcan dbe:
A. One dto done
B. One dto dmany
C. Many dto dmany
13. A duse dcase ddiagram dreflects dthe dview dof dthe dsystem dfrom dthe dperspective dof da duser
doutside dof dthe dsystem.
14. A duse dcase dmodel dpartitions dthe dway dthe dsystem dworks dinto dbehaviors, dservices,
dand dresponses d that dare d significant dto dthe dusers dof d the dsystem.
15. A duse dcase ddiagram dhas dsymbols dfor:
A. An dactor, dthe drole dof da duser dof dthe dsystem
B. The duse dcase drepresenting da dsequence dof dtransactions din da dsystem
16. There dare dtwo dkinds dof duse dcases:
A. Primary, dthe dstandard dflow dof devents dwithin da dsystem dthat ddescribe da dstandard
dsystem dbehavior
B. Use dcase dscenarios dthat ddescribe dvariations dof dthe dprimary duse dcase
17. There dare dfour dactive dbehavioral drelationships:
A. Communicates—used d to d connect d an d actor d to d a d use d case.
B. Includes—describes dthe dsituation d where d a d use d case d contains d a d behavior d that
d is d common d tomore dthan d one duse dcase.
C. Extends—describes d the dsituation d where d one d use d case d possesses d the d behavior
d that d allowsthe dnew duse d case dto dhandle da dvariation dor dexception.
