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 |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 |a | system. |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. |The | project |has |a |budget |that |helps | to |define |scope.
|
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 |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 |a | system. |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. |The | project |has |a |budget |that |helps | to |define |scope.
|
