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 acan aaffect aevery aaspect aof athe aorganization, asuch aas:
A. Design aof aemployees’ awork
B. Skills arequired afor ajob acompetency
C. Strategic apositioning aof athe acompany
7. Many aissues amust abe aovercome afor athe aERP ainstallation ais ato abe adeclared aa asuccess:
A. User aacceptance
B. Integration awith alegacy asystems aand athe asupply achain
C. Upgrading afunctionality a(and acomplexity) aof aERP amodules
D. Reorganizing awork alife aof ausers aand adecision amakers
E. Expanded areach aacross aseveral aorganizations
F. Strategic arepositioning aof athe acompany
8. A acontext-level adata aflow adiagram ais aan aimportant atool afor ashowing adata a used aand
ainformation aproduced aby aa a system. aIt aprovides aan aoverview aof athe asetting a or
aenvironment athe asystem aexists awithin—which aentities a supply a and areceive adata/information.
, 9. The acontext-level adata aflow adiagram ais aone away ato ashow ascope, aor awhat ais ato abe
a included ain athe asystem. aThe a project ahas aa abudget athat ahelps a to adefine ascope.
10. Entity-relationship adiagrams ahelp athe aanalyst aunderstand athe aorganizational asystem aand
athe adata astored aby athe a organization.
11. There aare athree atypes aof aentities:
A. Fundamental aentity, adescribing aa aperson, aplace, aor athing.
B. Associative aentity a(also acalled aa agerund, ajunction, aintersection, aor
aconcatenated aentity), ajoining a two a entities. aIt acan aonly aexist abetween atwo
aentities.
C. Attributive aentity, ato adescribe aattributes aand arepeating agroups.
12. Relationships aare ashown awith aa azero aor acircle arepresenting anone, aa avertical aline
arepresenting a one, aor acrow’sfoot a representing amany aand acan abe:
A. One ato aone
B. One ato amany
C. Many ato amany
13. A ause acase adiagram areflects athe aview aof athe asystem afrom athe aperspective aof aa auser
aoutside aof athe asystem.
14. A ause acase amodel apartitions athe away athe asystem aworks ainto abehaviors, aservices,
aand aresponses a that aare a significant ato athe ausers aof a the asystem.
15. A ause acase adiagram ahas asymbols afor:
A. An aactor, athe arole aof aa auser aof athe asystem
B. The ause acase arepresenting aa asequence aof atransactions ain aa asystem
16. There aare atwo akinds aof ause acases:
A. Primary, athe astandard aflow aof aevents awithin aa asystem athat adescribe aa astandard
asystem abehavior
B. Use acase ascenarios athat adescribe avariations aof athe aprimary ause acase
17. There aare afour aactive abehavioral arelationships:
A. Communicates—used a to a connect a an a actor a to a a a use a case.
B. Includes—describes athe asituation a where a a a use a case a contains a a a behavior a that
a is a common a tomore athan a one ause acase.
C. Extends—describes a the asituation a where a one a use a case a possesses a the a behavior
a that a allowsthe anew ause a case ato ahandle aa avariation aor aexception.
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 acan aaffect aevery aaspect aof athe aorganization, asuch aas:
A. Design aof aemployees’ awork
B. Skills arequired afor ajob acompetency
C. Strategic apositioning aof athe acompany
7. Many aissues amust abe aovercome afor athe aERP ainstallation ais ato abe adeclared aa asuccess:
A. User aacceptance
B. Integration awith alegacy asystems aand athe asupply achain
C. Upgrading afunctionality a(and acomplexity) aof aERP amodules
D. Reorganizing awork alife aof ausers aand adecision amakers
E. Expanded areach aacross aseveral aorganizations
F. Strategic arepositioning aof athe acompany
8. A acontext-level adata aflow adiagram ais aan aimportant atool afor ashowing adata a used aand
ainformation aproduced aby aa a system. aIt aprovides aan aoverview aof athe asetting a or
aenvironment athe asystem aexists awithin—which aentities a supply a and areceive adata/information.
, 9. The acontext-level adata aflow adiagram ais aone away ato ashow ascope, aor awhat ais ato abe
a included ain athe asystem. aThe a project ahas aa abudget athat ahelps a to adefine ascope.
10. Entity-relationship adiagrams ahelp athe aanalyst aunderstand athe aorganizational asystem aand
athe adata astored aby athe a organization.
11. There aare athree atypes aof aentities:
A. Fundamental aentity, adescribing aa aperson, aplace, aor athing.
B. Associative aentity a(also acalled aa agerund, ajunction, aintersection, aor
aconcatenated aentity), ajoining a two a entities. aIt acan aonly aexist abetween atwo
aentities.
C. Attributive aentity, ato adescribe aattributes aand arepeating agroups.
12. Relationships aare ashown awith aa azero aor acircle arepresenting anone, aa avertical aline
arepresenting a one, aor acrow’sfoot a representing amany aand acan abe:
A. One ato aone
B. One ato amany
C. Many ato amany
13. A ause acase adiagram areflects athe aview aof athe asystem afrom athe aperspective aof aa auser
aoutside aof athe asystem.
14. A ause acase amodel apartitions athe away athe asystem aworks ainto abehaviors, aservices,
aand aresponses a that aare a significant ato athe ausers aof a the asystem.
15. A ause acase adiagram ahas asymbols afor:
A. An aactor, athe arole aof aa auser aof athe asystem
B. The ause acase arepresenting aa asequence aof atransactions ain aa asystem
16. There aare atwo akinds aof ause acases:
A. Primary, athe astandard aflow aof aevents awithin aa asystem athat adescribe aa astandard
asystem abehavior
B. Use acase ascenarios athat adescribe avariations aof athe aprimary ause acase
17. There aare afour aactive abehavioral arelationships:
A. Communicates—used a to a connect a an a actor a to a a a use a case.
B. Includes—describes athe asituation a where a a a use a case a contains a a a behavior a that
a is a common a tomore athan a one ause acase.
C. Extends—describes a the asituation a where a one a use a case a possesses a the a behavior
a that a allowsthe anew ause a case ato ahandle aa avariation aor aexception.
