10th Edition by Kendall Kenneth and Kendall Julie,
All Chapters 1 - 16
,TABLE OF CONTENTS JT JT
I. Systems Analysis Fundamentals
JT JT JT
1. Systems, Roles, and Development Methodologies
JT JT JT JT
2. Understanding and Modeling Organization Systems JT JT JT JT
3. Project Management JT
II. Information Requirements Analysis
JT JT JT
4. Information Gathering: Interactive Methods JT JT JT
5. Information Gathering: Unobtrusive Methods JT JT JT
6. Agile Modeling, Prototyping, and Scrum
JT JT JT JT
III. The Analysis Process
JT JT JT
7. Using Data Flow Diagrams
JT JT JT
8. Analyzing Systems Using Data Dictionaries
JT JT JT JT
9. Process Specifications and Structured Decisions
JT JT JT JT
10. Object-Oriented Systems Analysis and Design Using UML JT JT JT JT JT JT
IV. The Essentials of Design
JT JT JT JT
11. Designing Effective Output JT JT
12. Designing Effective Input JT JT
13. Designing Databases JT
14. Human-Computer Interaction and UX Design JT JT JT JT
V. Quality Assurance and Implementation
JT JT JT JT
15. Designing Accurate Data Entry Procedures
JT JT JT JT
16. Quality Assurance and Implementation
JT JT JT
,Chapter 2 JT
Understanding and Modeling Organizational Systems JT JT JT JT
Key Points and Objectives JT JT JT
1. Organizations are complex systems composed of interrelated and interdependent subsystems.
JT JT JT JT JT JT JT JT JT
2. System and subsystem boundaries and environments have an impact on information system analysis anddesign.
JT JT JT JT JT JT JT JT JT JT JT JT JT JT
3. Systems are described as either open, with free flowing information, or closed with restricted access toinformation.
JT JT JT JT JT JT JT JT JT JT JT JT JT JT JT JT
4. A virtual organization is one that has parts of the organization in different physical locations. They usecomputer netw
JT JT JT JT JT JT JT JT JT JT JT JT JT JT JT JT JT JT
orks and communications technology to work on projects. Advantages of a virtual organization are:
JT JT JT JT JT JT JT JT JT JT JT JT JT
A. Reduced costs of physical facilities JT JT JT JT
B. More rapid response to customer needs
JT JT JT JT JT
C. Flexibility for employees to care for children or aging parents
JT JT JT JT JT JT JT JT JT
5. Enterprise systems or Enterprise Resource Planning (ERP) describes an integrated organizational information system
JT JT JT JT JT JT JT JT JT JT JT JT
. The software helps the flow of information between the functional areas within theorganization.
JT JT JT JT JT JT JT JT JT JT JT JT JT JT
6. ERP can affect every aspect of the organization, such as:
JT JT JT JT JT JT JT JT JT
A. Design of employees’ work JT JT JT
B. Skills required for job competency
JT JT JT JT
C. Strategic positioning of the company JT JT JT JT
7. Many issues must be overcome for the ERP installation is to be declared a success:
JT JT JT JT JT JT JT JT JT JT JT JT JT JT
A. User acceptance JT
B. Integration with legacy systems and the supply chain JT JT JT JT JT JT JT
C. Upgrading functionality (and complexity) of ERP modules JT JT JT JT JT JT
D. Reorganizing work life of users and decision makers JT JT JT JT JT JT JT
E. Expanded reach across several organizations JT JT JT JT
F. Strategic repositioning of the company JT JT JT JT
8. A context-
JT
level data flow diagram is an important tool for showing data used and information produced by asystem. It provides an ove
JT JT JT JT JT JT JT JT JT JT JT JT JT JT JT JT JT JT JT JT JT
rview of the setting or environment the system exists within—which entities supply and receive data/information.
JT JT JT JT JT JT JT JT JT JT JT JT JT JT
9. The context- JT
level data flow diagram is one way to show scope, or what is to be included in the system. Theproject has a budget that hel
JT JT JT JT JT JT JT JT JT JT JT JT JT JT JT JT JT JT JT JT JT JT JT JT JT
ps to define scope.
JT JT JT
, 10. Entity-relationship diagrams help the analyst understand the organizational system and the data stored by theorganization.
JT JT JT JT JT JT JT JT JT JT JT JT JT JT JT
11. There are three types of entities:
JT JT JT JT JT
A. Fundamental entity, describing a person, place, or thing. JT JT JT JT JT JT JT
B. Associative entity (also called a gerund, junction, intersection, or concatenated entity), joining twoentities. It c
JT JT JT JT JT JT JT JT JT JT JT JT JT JT JT
an only exist between two entities.
JT JT JT JT JT
C. Attributive entity, to describe attributes and repeating groups. JT JT JT JT JT JT JT
12. Relationships are shown with a zero or circle representing none, a vertical line representing one, or crow’sfoot represen
JT JT JT JT JT JT JT JT JT JT JT JT JT JT JT JT JT JT
ting many and can be:
JT JT JT JT
A. One to one JT JT
B. One to many JT JT
C. Many to many JT JT
13. A use case diagram reflects the view of the system from the perspective of a user outside of the system.
JT JT JT JT JT JT JT JT JT JT JT JT JT JT JT JT JT JT JT
14. A use case model partitions the way the system works into behaviors, services, and responses that aresignificant to th
JT JT JT JT JT JT JT JT JT JT JT JT JT JT JT JT JT JT JT
e users of the system.
JT JT JT JT
15. A use case diagram has symbols for:
JT JT JT JT JT JT
A. An actor, the role of a user of the system
JT JT JT JT JT JT JT JT JT
B. The use case representing a sequence of transactions in a system
JT JT JT JT JT JT JT JT JT JT
16. There are two kinds of use cases:
JT JT JT JT JT JT
A. Primary, the standard flow of events within a system that describe a standard system behavior
JT JT JT JT JT JT JT JT JT JT JT JT JT JT
B. Use case scenarios that describe variations of the primary use case
JT JT JT JT JT JT JT JT JT JT
17. There are four active behavioral relationships:
JT JT JT JT JT
A. Communicates—used to connect an actor to a use case. JT JT J T JT JT JT JT JT
B. Includes—
describes the situation where a use case contains a behavior that is common tomore than one use case.
JT JT JT JT JT JT JT JT JT JT JT JT JT JT JT JT JT JT
C. Extends—
describes the situation where one use case possesses the behavior that allowsthe new use case to handle a variat
JT JT JT JT JT JT JT JT JT JT JT JT JT JT JT JT JT JT JT
ion or exception.JT JT
D. Generalizes—implies that one thing is more typical than the other thing. JT JT JT JT JT JT JT JT JT JT