Solution manual for systems analysis and design 10th edition by kendall kenneth and kendall julie

SOLUTION MANUAL for Systems Analysis and Design
b b b b b b




10th Edition by Kendall Kenneth and Kendall Julie,
b b b b b b b




All Chapters 1 - 16
b b b b

,TABLEOFCONTENTS b b




I. Systems Analysis Fundamentals
b b b




1. Systems, Roles, and Development Methodologies
b b b b




2. Understanding and Modeling Organization Systems b b b b




3. Project Management b




II. Information Requirements Analysis
b b b




4. Information Gathering: Interactive Methods b b b




5. Information Gathering: Unobtrusive Methods b b b




6. Agile Modeling, Prototyping, and Scrum
b b b b




III. The Analysis Process
b b b




7. Using Data Flow Diagrams b b b




8. Analyzing Systems Using Data Dictionariesb b b b




9. Process Specifications and Structured Decisions
b b b b




10. Object-Oriented Systems Analysis and Design Using UML b b b b b b




IV. The Essentials of Design
b b b b




11. Designing Effective Output b b




12. Designing Effective Input b b




13. Designing Databases b




14. Human-Computer Interaction and UX Design b b b b




V. Quality Assurance and Implementation
b b b b




15. Designing Accurate Data Entry Procedures b b b b




16. Quality Assurance and Implementation
b b b

,Chapter2 b




Understandingand ModelingOrganizational Systems b b b b




KeyPoints and Objectives b b b




1. Organizations are complex systems composed of interrelated and interdependentsubsystems.
b b b b b b b b b




2. System and subsystem boundaries and environments have an impact on information system analysis anddesign.
b b b b b b b b b b b b b b




3. Systems are described as either open, with freeflowinginformation, or closed with restricted access toinformation.
b b b b b b b b b b b b b b b b




4. A virtual organization is one that has parts of the organization in different physical locations. They usecomputer networks
b b b b b b b b b b b b b b b b b b




and communications technology to work on projects. Advantages of a virtual organization are:
b b b b b b b b b b b b b




A. Reducedcosts of physical facilities b b b b




B. More rapidresponse to customer needs b b b b b




C. Flexibilityfor employees tocare for children or aging parents b b b b b b b b b




5. Enterprise systems or Enterprise Resource Planning (ERP) describes an integrated organizational information system.
b b b b b b b b b b b b




The software helps the flow of information between the functional areas within theorganization.
b b b b b b b b b b b b b b




6. ERP can affect everyaspect of the organization, suchas:
b b b b b b b b b




A. Design of employees’ work b b b




B. Skillsrequired for job competency b b b b




C. Strategic positioningof thecompany b b b b




7. Manyissues must be overcome for theERP installation isto be declared a success:
b b b b b b b b b b b b b b




A. User acceptance b




B. Integration with legacy systems and the supply chain b b b b b b b




C. Upgradingfunctionality(and complexity) of ERP modules b b b b b b




D. Reorganizingworklife of users and decision makers b b b b b b b




E. Expandedreach across several organizations b b b b




F. Strategicrepositioningof the company b b b b




8. A context-level data flow diagram is an important tool for showing data used and information produced by asystem. It provides
b b b b b b b b b b b b b b b b b b b b




an overview of the setting or environment the system exists within—which entities supplyand receive data/information.
b b b b b b b b b b b b b b b b




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
b b b b b b b b b b b b b b b b b b b b b b b b




that helps to define scope.
b b b b b

, 10. Entity-relationship diagrams help the analyst understand the organizational system and the data stored by theorganization.
b b b b b b b b b b b b b b b




11. Therearethreetypes of entities:
b b b b b




A. Fundamentalentity, describinga person, place, or thing. b b b b b b b




B. Associative entity (also called a gerund, junction, intersection, or concatenated entity), joining twoentities. It can
b b b b b b b b b b b b b b b




only exist between two entities.
b b b b b




C. Attributive entity, to describe attributesandrepeatinggroups. b b b b b b b




12. Relationships are shown with a zero or circle representing none, a vertical line representing one, or crow’sfoot representing
b b b b b b b b b b b b b b b b b b




many and can be:
b b b b




A. One to one b b




B. One to many b b




C. Manyto many b b




13. A use case diagramreflects the view of the systemfromthe perspective of a user outside of the system.
b b b b b b b b b b b b b b b b b b b




14. A use case model partitionsthe waythe systemworks into behaviors, services, andresponses thataresignificant to the
b b b b b b b b b b b b b b b b b b b




users of the system.
b b b b




15. A use case diagramhas symbols for:
b b b b b b




A. An actor, the role of a user of the system
b b b b b b b b b




B. The use case representing a sequence of transactions ina system
b b b b b b b b b b




16. There are two kinds of use cases:
b b b b b b




A. Primary, the standardflow of events withina systemthat describe a standard systembehavior
b b b b b b b b b b b b b b




B. Use case scenarios that describe variations of the primaryuse case
b b b b b b b b b b




17. There arefour active behavioral relationships:
b b b b b




A. Communicates—used to connect an actor to a use case. b b b b b b b b




B. Includes—describes the situation where a use case contains a behavior that is common tomore than one use case. b b b b b b b b b b b b b b b b b b




C. Extends—describes the situation where one use case possesses the behavior that allowsthe new use case to handle a b b b b b b b b b b b b b b b b b b




variation or exception.
b b b




D. Generalizes—implies that one thing is more typical than the other thing. b b b b b b b b b b