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 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 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 diagrams help the analyst understand the organizational system and the data stored by the
organization.
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 twoentities. 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 aresignificant
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:
A. Primary, the standard flow of events within a system that describe a standard system behavior
B. Use case scenarios that describe variations of the primary use case
17. There are four active behavioral relationships:
A. Communicates—used to connect an actor to a use case.
B. Includes—describes the situation where a use case contains a behavior that is common tomore than one use
case.
C. Extends—describes the situation where one use case possesses the behavior that allowsthe new use case to
handle a variation or exception.
D. Generalizes—implies that one thing is more typical than the other thing.
,18. The steps required to create a use case model are:
A. Review the business specifications and identify the actors within the problem domain.
B. Identify the high-level events and develop the primary use cases that describe the eventsand how actors
initiate them.
C. Review each primary use case to determine possible variations of flow through the usecase.
D. Develop the use case documents for all primary use cases and all important use casescenarios.
19. Use case scenarios are text descriptions of the use case, and may contain the following:
A. The use case name and a unique ID
B. The area of the business
C. The actors
D. The stakeholders
E. The level
F. A brief description of the use case
G. The triggering event
H. The type of trigger, either external or temporal
I. The steps performed for the use case
J. Preconditions, what must have occurred before the use case can start to execute
K. Postconditions, what has been accomplished by the use case
L. Assumptions that have been made for the use case to execute
M. Requirements met by the use case
N. Minimum guarantee
O. Success guarantee
P. Any outstanding issues
Q. An optional priority
R. An optional risk
20. Use case levels describe how global or detailed the use case description is. Levels are:
A. White (like clouds): enterprise level
, B. Kite: business unit or department level
C. Blue (sea level): user goals
D. Indigo (or fish): functional or subfunctional
E. Black (or clam): most detailed
21. Use case descriptions are created with these four steps:
A. Use agile stories, problem definition objectives, user requirements, or a features list.
B. Ask about the tasks that must be done.
C. Determine if there are any iterative or looping actions.
D. The use case ends when the customer goal is complete.
22. Use cases are helpful because they:
A. Effectively communicate systems requirements
B. Allow people to tell stories
C. Make sense to nontechnical people
D. Do not depend on a special language
E. Can describe functional requirements
F. Can describe nonfunctional requirements
G. Help analysts define boundaries
H. Can be traceable, allowing analysts to identify links between use cases and other design and
documentation tools
23. The three levels of managerial control are:
A. Operations management
B. Middle management
C. Strategic management
24. In systems analysis and design, collaborative design means that stakeholders who are external (outside clients) as well as
those who are internal to the company follow processes to share in designing a system thatmeets their goals.
25. Each of the three levels of management, different organization structure, leadership style, technological considerations,
organization culture, and human interaction all carry implications for the analysis and designof information systems.
Consulting Opportunity 2.1 (p. 21)
The E in Vitamin E Stands for Ecommerce
1. The elements that are interrelated or interdependent are:
Elements 1 and 2: attracting customers and informing customers.
, Elements 4, 5, 6, and 7: completing transactions, accepting payments, arranging for delivery of goods and services,
and supporting customers after the sale.
2. The items that are critical for initial development are elements 1, 2, 4, 5, 6, and 7, mentioned above. Elements 3 and
8 (allowing customers to customize products online, and personalizing the look and feel ofthe website) may be done
at a later date.
3. The elements that should be handled in-house are:
Elements 1, 2, 3, 4, 6, and 8: attracting customers, informing customers, allowing customers to customize
products online, completing transactions with customers, supporting customers after the sale, and personalizing the
look and feel of the website.
These are best done in-house using corporate data and corporate systems. Performing the workin-house allows
management to quickly change the information used and presented to the customers, as well as providing control
over the system.
The elements that should be outsourced are 1, 5, and 7: attracting customers, accepting payments, and arranging for
delivery of goods and services. Notice that attracting customers falls into both categories. This depends on the nature of
advertisement and other ways of attracting customers. If banner ads, those on the top of a Web page, are used, they
may be provided by a specialist. The same is true for radio, billboard, magazine, and television ads. Accepting payments
is better outsourced, using one or more of the many Web-based payment options or using a traditional credit card.
Arranging for delivery of goods and services is better done by an outside shipping company(unless the corporation has
its own shipping line).
Some of the other functions of the ecommerce may be outsourced as well. Some corporationshave the Web
development done by a consulting firm and some have a third party host the website.
Consulting Opportunity 2.2 (p. 40)
Where There’s Carbon, There’s a Copy
Richard and Harry had failed to consider the impact of tossing out the pink forms on the rest of thesystem. They did not realize
that systems and subsystems are interrelated and interdependent.
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 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 diagrams help the analyst understand the organizational system and the data stored by the
organization.
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 twoentities. 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 aresignificant
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:
A. Primary, the standard flow of events within a system that describe a standard system behavior
B. Use case scenarios that describe variations of the primary use case
17. There are four active behavioral relationships:
A. Communicates—used to connect an actor to a use case.
B. Includes—describes the situation where a use case contains a behavior that is common tomore than one use
case.
C. Extends—describes the situation where one use case possesses the behavior that allowsthe new use case to
handle a variation or exception.
D. Generalizes—implies that one thing is more typical than the other thing.
,18. The steps required to create a use case model are:
A. Review the business specifications and identify the actors within the problem domain.
B. Identify the high-level events and develop the primary use cases that describe the eventsand how actors
initiate them.
C. Review each primary use case to determine possible variations of flow through the usecase.
D. Develop the use case documents for all primary use cases and all important use casescenarios.
19. Use case scenarios are text descriptions of the use case, and may contain the following:
A. The use case name and a unique ID
B. The area of the business
C. The actors
D. The stakeholders
E. The level
F. A brief description of the use case
G. The triggering event
H. The type of trigger, either external or temporal
I. The steps performed for the use case
J. Preconditions, what must have occurred before the use case can start to execute
K. Postconditions, what has been accomplished by the use case
L. Assumptions that have been made for the use case to execute
M. Requirements met by the use case
N. Minimum guarantee
O. Success guarantee
P. Any outstanding issues
Q. An optional priority
R. An optional risk
20. Use case levels describe how global or detailed the use case description is. Levels are:
A. White (like clouds): enterprise level
, B. Kite: business unit or department level
C. Blue (sea level): user goals
D. Indigo (or fish): functional or subfunctional
E. Black (or clam): most detailed
21. Use case descriptions are created with these four steps:
A. Use agile stories, problem definition objectives, user requirements, or a features list.
B. Ask about the tasks that must be done.
C. Determine if there are any iterative or looping actions.
D. The use case ends when the customer goal is complete.
22. Use cases are helpful because they:
A. Effectively communicate systems requirements
B. Allow people to tell stories
C. Make sense to nontechnical people
D. Do not depend on a special language
E. Can describe functional requirements
F. Can describe nonfunctional requirements
G. Help analysts define boundaries
H. Can be traceable, allowing analysts to identify links between use cases and other design and
documentation tools
23. The three levels of managerial control are:
A. Operations management
B. Middle management
C. Strategic management
24. In systems analysis and design, collaborative design means that stakeholders who are external (outside clients) as well as
those who are internal to the company follow processes to share in designing a system thatmeets their goals.
25. Each of the three levels of management, different organization structure, leadership style, technological considerations,
organization culture, and human interaction all carry implications for the analysis and designof information systems.
Consulting Opportunity 2.1 (p. 21)
The E in Vitamin E Stands for Ecommerce
1. The elements that are interrelated or interdependent are:
Elements 1 and 2: attracting customers and informing customers.
, Elements 4, 5, 6, and 7: completing transactions, accepting payments, arranging for delivery of goods and services,
and supporting customers after the sale.
2. The items that are critical for initial development are elements 1, 2, 4, 5, 6, and 7, mentioned above. Elements 3 and
8 (allowing customers to customize products online, and personalizing the look and feel ofthe website) may be done
at a later date.
3. The elements that should be handled in-house are:
Elements 1, 2, 3, 4, 6, and 8: attracting customers, informing customers, allowing customers to customize
products online, completing transactions with customers, supporting customers after the sale, and personalizing the
look and feel of the website.
These are best done in-house using corporate data and corporate systems. Performing the workin-house allows
management to quickly change the information used and presented to the customers, as well as providing control
over the system.
The elements that should be outsourced are 1, 5, and 7: attracting customers, accepting payments, and arranging for
delivery of goods and services. Notice that attracting customers falls into both categories. This depends on the nature of
advertisement and other ways of attracting customers. If banner ads, those on the top of a Web page, are used, they
may be provided by a specialist. The same is true for radio, billboard, magazine, and television ads. Accepting payments
is better outsourced, using one or more of the many Web-based payment options or using a traditional credit card.
Arranging for delivery of goods and services is better done by an outside shipping company(unless the corporation has
its own shipping line).
Some of the other functions of the ecommerce may be outsourced as well. Some corporationshave the Web
development done by a consulting firm and some have a third party host the website.
Consulting Opportunity 2.2 (p. 40)
Where There’s Carbon, There’s a Copy
Richard and Harry had failed to consider the impact of tossing out the pink forms on the rest of thesystem. They did not realize
that systems and subsystems are interrelated and interdependent.
