Systems Analysis And Design 8th Edition Case Study Answers

On By In 1

This preview has intentionally blurred sections. Sign up to view the full version.

View Full Document

This preview has intentionally blurred sections. Sign up to view the full version.

View Full Document

This preview has intentionally blurred sections. Sign up to view the full version.

View Full Document

This preview has intentionally blurred sections. Sign up to view the full version.

View Full Document

This preview has intentionally blurred sections. Sign up to view the full version.

View Full Document

This preview has intentionally blurred sections. Sign up to view the full version.

View Full Document
This is the end of the preview. Sign up to access the rest of the document.
Systems Analysis and Design 8th Edition Chapter 4 Requirements Modeling
Phase Description • Systems analysis is the second of five phases in the systems development life cycle (SDLC) • Will use requirements modeling, data and process modeling, and object modeling techniques to represent the new system • Will consider various development strategies for the new system, and plan for the transition to systems design tasks 2
Chapter Objectives • Describe systems analysis phase activities and the end product of the systems analysis phase • Explain joint application development (JAD), rapid application development (RAD), and agile methods • Understand how systems analysts use a functional decomposition diagram (FDD) 3
Chapter Objectives • Describe the Unified Modeling Language (UML) and explain use case diagrams and sequence diagrams • List and describe system requirements, including outputs, inputs, processes, performance, and controls • Explain the concept of scalability 4
Chapter Objectives • Use fact-finding techniques, including interviews, documentation review, observation, questionnaires, sampling, and research • Define total cost of ownership (TCO) • Conduct a successful interview • Develop effective documentation methods to use during systems development 5
Introduction • This chapter describes requirements modeling techniques and team-based methods that systems analysts use to visualize and document new systems • The chapter then discusses system requirements and fact-finding techniques, which include interviewing, documentation review, observation, surveys and questionnaires, sampling, and research 6
Systems Analysis Phase Overview • The overall objective of the systems analysis phase is to understand the proposed project, ensure that it will support business requirements, and build a solid foundation for system development • You use models and other documentation tools to visualize and describe the proposed system 7
Systems Analysis Phase Overview • Systems Analysis Activities – Requirements modeling • Outputs • Inputs • Processes • Performance • Security 8
Systems Analysis Phase Overview • Systems Analysis Activities – Data and process modeling – Object Modeling – Development Strategies • System requirements document 9
Systems Analysis Phase Overview • Systems Analysis Skills – Analytical skills – Interpersonal skills • Team-Oriented Methods and Techniques – Joint application development (JAD) – Rapid application development (RAD) – Agile methods 10
Joint Application Development • User Involvement – Users have a vital stake in an information system and they should participate fully – Successful systems must be user-oriented, and users need to be involved – One popular strategy for user involvement is a JAD team approach 11
Joint Application Development • JAD Participants and Roles 12
 

Chapter 2

 Modern Systems Analysis and Design

8th

edition

 Instructor 

’s

 Manual 

Chapter 2

 Modern Systems Analysis and Design

8th

edition

 Instructor 

’s

 Manual 

the claims made by software and hardware vendors need to be validated by someone outside the vendor

organization,

such as current users and

independent software testing centers. Emphasize

that vendor information may be biased and even trade publication articles may describe software in a more than realistic positive light. When in doubt, check the information out. 5. Discuss the importance of software reuse and how object-oriented and component-based development are the two most common reuse methods. Also emphasize that reuse must be aligned with the organization

s overall strategic goals. Explain the four levels of adoption currently being seen in the industry:

ad hoc

, facilitated, managed, and designed (Table 2-3 lists the four approaches).

Classroom Ideas

1. Use Table 2-1 and an updated version of the same information from the most recent Software Magazine survey to begin a discussion of the many, varied sources of software in the marketplace. 2. Use Table 2-2 to

summarize

the six

alternative

sources for software and how to choose

among

them for specific software needs. This table can serve as the basis for a discussion of the make- versus-  buy decision and can be expanded to

include

the

“n

ot

invented

here

 syndrome.

Additionally,

invite a guest speaker who is currently responsible for software procurement and have them discuss the advantages and disadvantages of the sources of software. 3. Have students research the proper format and contents for Requests for Proposal and have them create and/or present an RFP (see Problem and Exercise 1). RFP preparation should include discussion of the hardware, software, and organizational issues presented in this chapter. 4. Find a local guest speaker (from your alumni base or a recruiter coming to your campus) from an organization that employs object-oriented design to come in and discuss the level of reuse and the real-world issues involved in their organization with promoting the concept, given some of the startup costs and constraints.

Answers to Key Terms

Suggested answers are provided below. These answers are presented top-down, left-to-right.2.3. Outsourcing 2.4. Request for proposal (RFP) 2.2. Enterprise resource planning (ERP) systems 2.5. Reuse 2.1. Cloud Computing

Answers to Review Questions

2.6. Six sources of software are identified in the text. These include: 1) Information Technology Services Firms, 2) packaged software producers, 3) enterprise-wide solution software, 4) cloud computing, 5) open-source, and 6) in-house development software.

0 comments

Leave a Reply

Your email address will not be published. Required fields are marked *