.png){kind=logo}
Chapter 1 Modern Systems Analysis and Design 9th edition GE Instructor’s Manual 1 Copyright © 2021 Pearson Education Ltd.Chapter 1 The Systems Development Environment Chapter Overview Chapter 1 is an overview of the systems development process, as well as an overview of the textbook.This chapter introduces students to the modern approach to systems analysis and design using various methodologies. Students are introduced to several systems development components, including the process and data-oriented approaches to systems development, different types of information systems, and the systems development life cycle.This textbook is intended primarily for juniors taking a core course in the information systems major, although the book can be adapted for a similar course at the junior college level or for a two-course sequence on analysis and design. Often students are not familiar with the systems development process, different organizational components, or how these components work together. This chapter provides the general organizational context in which systems development takes place.The text uses the Systems Development Life Cycle (S D L C) methodology (including its associated problems with the traditional waterfall approach) to introduce students to the structured approach in creating new systems. The student is also introduced to other methodologies such as the Agile Methodologies, eXtreme Programming, Object-Oriented Analysis and Design (O O A D), and the Rational Unified Process (R U P). The text compares and contrasts the new with more traditional methods in an effort to show both the advantages and limitations of these methods.Chapter 1 introduces students to visual and emerging development tools. C A S E tools are used to apply an engineering approach to systems development and can support each phase of the S D L C.Instructional Objectives Specific student learning objectives are included at the beginning of the chapter.
From an instructor’s point of view, the objectives of this chapter are to:
1.Define and discuss the modern approach to systems analysis and design from an organizational perspective incorporating techniques, tools, and methodologies.
2.Explain how an organization’s objectives, structure, and processes are essential in the development of systems to meet their needs.
3.Explain that the S D L C process is not sequential but cyclical and that the order is adaptable as required for different projects; also, to emphasize that often analysts and designers may go backwards to the previous step to complete unfinished products or to correct errors or omissions discovered in the next phase.
4.Explain the difference between the logical design and the physical design as it relates to systems development.
5.Discuss the problems with the waterfall S D L C and explain the different approaches analysts, designers and developers have developed to improve the Systems Analysis and Design process.
6.Discuss Agile methodologies and eXtreme programming and how these compare to the traditional Systems Development Life Cycle (S D L C).
7.Explain and discuss object-oriented analysis and design (O O A D) and the Rational Unified Process (R U P).Modern Systems Analysis and Design, 9e (Global Edition) Joseph Valacich, Joey George, Jeffrey Hoffer (Instructor Manual All Chapters, 100% Original Verified, A+ Grade) 1 / 4
Chapter 1 Modern Systems Analysis and Design 9th edition GE Instructor’s Manual
Copyright © 2021 Pearson Education Ltd.2
- Show students that the life cycle is a flexible basis for systems analysis and design and that it
- Compare and contrast the various development approaches introduced in Chapter 1 and
- Finally explain that the boundaries and divisions of the 5 steps in Figure 1-2 when imposed to
- Figure 1-1 depicts that methodologies, techniques, and tools drive organizational approaches to
- When introducing the systems development life cycle model featured in the textbook, discuss
- Provide a brief overview of the activities and outputs from each of the five life cycle phases,
- Figure 1-9 illustrates the R U P life cycle. Discuss R U P, and its benefits and drawbacks as it
- Ask students to compare Agile methodologies to traditional S D L C (see Table 1-3 Five Critical
- This chapter introduces eXtreme programming. If your students have sufficient background,
- Discuss I B M’ s Rational Unified Process (R U P) shown in Figure 1-9. This Web site
can support many different tools and techniques, such as Agile methodologies and eXtreme Programming.
depict how they all use an iterative approach.
explain the steps are neither hard nor fast and that in many real-world situations phases or sub-phases may be combined to improve efficiency and understanding. The cycle is an organizing and guiding principle; however, in companies and software development teams will adapt it to suit their needs for specific projects.Classroom Ideas
systems analysis and design. Ask students to identify the names of methodologies, techniques, and tools. List them on the board under the heading that they suggest; then after they have identified 5 or 6 in each heading, review and emphasize the differences among the three and move any from an incorrect category to the correct one and explain why it is one and not the other.
other life cycle models using actual ones from existing organizations. Show that the basic model presented (Planning, Analysis, Design, Implementation, and Maintenance) are broken down into smaller phases by many companies but that in the end they could be categorized into one of the basic five explained. This reinforces to students that no one standard life cycle model exists and the model they will use as a systems analyst will likely differ from the textbook’s life cycle model. The point is that the life cycle represents activities that must be done; and the phases are a way to introduce, in an organized way, the methods, techniques, tools, and skills necessary for successful systems analysis and design.
based on your own experience or from reading the rest of the textbook. Table 1-1 summarizes the products, outputs or deliverables of each phase based on the in-text descriptions.
relates to O O A D. Discuss the differences between R U P and the traditional S D L C. Table 1-2 presents the Agile Manifesto.
Factors that Distinguish Agile and Traditional Approaches to Systems Development). Introduce a case study project where Agile methodologies were employed. Ask students to identify problems that the project ran into using Agile methodologies as well as any benefits gained by this approach.
assign students to programming pairs and have them work on a small programming problem, including testing. Ask students to report upon their experience.
https://www.ibm.com/search?q=rup&lnk=mhsrch&v=18&en=utf&lang=en&cc=us should help with background information.
- / 4
Chapter 1 Modern Systems Analysis and Design 9th edition GE Instructor’s Manual
Copyright © 2021 Pearson Education Ltd.3 Answers to Key Terms Suggested answers are provided below. These answers are presented top-down, left to right
1.5. Information systems analysis and design
1.2. Application software
1.15. Systems analyst
1.17. Systems development methodology
1.16. Systems development life cycle
1.13. Planning
1.1. Analysis
1.3. Design
1.7. Logical design
1.12. Physical design
1.4. Implementation
1.8. Maintenance
1.11. Object-oriented analysis and design (O O A D) (R A D)
1.9. Object
1.6. Inheritance
1.10. Object class
1.14. Rational Unified Process (R U P)
Answers to Review Questions
1.18. The role of the systems analyst is to study the problems and needs of an organization to
determine how people, methods, and information technology can best be combined to bring about improvements in the organization.
1.19. Software designed to support a specific organizational function or process, such as payroll,
market analysis, or inventory management, is known as application software.
1.20. Logical design is the part of the design phase of the SDLC in which all the functional features of
the system chosen for development are described independent of any platform. Physical design is the part of the design phase in which the logical specifications are transformed into technology-specific details, based on which all programming and system construction is accomplished. In other words, logical design is high-level design of a proposed information system that does not delve into the details of the system. For example, if an organization wants to implement a human resource information system, then logical design provides an abstract representation of the flow of human resource data as well as the inputs and outputs of the proposed human resource system. Meanwhile, physical design is more detailed – it must specify databases, the programming language, and technologies. Considering the example of the human resource information system, physical design mentions the programming language to be used to design the system. Most importantly, the physical design specifies the database that is to be used to store the data, that is, the analyst also includes entities like the date and attributes of the date entity, such as the year and week. 3 / 4
Chapter 1 Modern Systems Analysis and Design 9th edition GE Instructor’s Manual
Copyright © 2021 Pearson Education Ltd.4
1.21. The early 1980s marked the breakthrough of personal (desktop) computers, such as the IBM PC.
Many more employees had access to a computer, so they had the option to work with ordinary applications/office software.
1.22. According to Fowler, Agile methodologies share three key principles: (1) a focus on adaptive
rather than predictive methodologies, (2) a focus on people rather than roles, and (3) a focus on self-adaptive software development processes. Together, these principles try to establish a more realistic approach of looking at the end users and the system rather than a more abstract approach.
1.23. eXtreme programming is an approach to software development distinguished by short
development cycles, an incremental planning approach, a focus on automated tests written by programmers and customers to monitor the development process, and reliance on an evolutionary approach to development that lasts throughout the lifetime of the system. This methodology uses an evolutionary approach to software development. Coding and testing are part of the same process and are done by a two-person programming team. Code is tested shortly after it is written and integrated into the system within a few hours of being written. All phases of the life cycle converge into a series of activities based on coding, testing, listening, and designing.
1.24. Rational Unified Process (RUP) is an object-oriented systems development methodology. It is
one of the most popular realizations of the iterative approach to object-oriented development.RUP establishes four phases of development –– inception, elaboration, construction, and transition. Each phase is organized into several separate parts.
1.25. Although theoretically the SDLC approach is the benchmark for designing an information
system, when applied practically, it is not possible to arrive at a clear-cut segmentation of the activities into different phases. The exact sequencing of steps may vary from one project to the next. Hence, instead of requesting segmenting in the analysis stage, system specifications in design, and coding and testing in the implementation phase, currently, all these activities are combined into the analysis–design–code–test process. This is considered the base of Agile methodologies and the heart of the system development process.
1.26. Object-oriented analysis and design (OOAD) is a structure that encapsulates (or packages)
attributes and the methods that operate on those attributes. It is an abstraction of a real-world thing, where data and processes are placed together to model the structure and behavior of the real-world object.
1.27. Compared to traditional coding practices, the advantages of pair programming include: (1) more
and better communication among developers, (2) higher levels of productivity, (3) higher- quality code, and (4) reinforcement of the other practices such as the code-and-test discipline.Answers to Problems and Exercises
1.28. Speed is an important factor for two reasons: (1) By undertaking a systems development
process, the client organization hopes for economic or other benefits. The sooner the new system is in place, the better. (2) Especially when working according to the SDLC model, it is difficult to change preconditions late in the process. Thus, if the time allotted for the development process is short, there is less risk of the system being built according to an outdated specification. When working in an agile fashion, it is somewhat easier to alter the system according to new requirements, but it is still a costly process.
1.29. A methodology is an acclaimed, comprehensive, and multi-step approach to creating or
developing something; for instance, developing an information system using the SDLC or one
- / 4
.png)