Download presentation
Published byCuthbert Ramsey Modified over 9 years ago
1
Chapter 1 Assuming the Role of the Systems Analyst
Systems Analysis and Design Kendall & Kendall Sixth Edition
2
Chapter 1 The Systems Development Environment
Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 1 The Systems Development Environment
3
Major Topics Information systems Phases of analysis and design
System maintenance CASE tools Alternate methodologies Kendall & Kendall 2005 Pearson Prentice Hall
4
Information Information is an organizational resource, which must be managed as carefully as other resources. Costs are associated with information processing. Information processing must be managed to take full advantage of its potential. Kendall & Kendall 2005 Pearson Prentice Hall
5
Information Systems Analysis and Design
Complex organizational process whereby computer-based information systems are developed and maintained Application Software Computer software designed to support organizational functions or processes Systems Analyst Organizational role most responsible for analysis and design of information systems
7
A Modern Approach to Systems Analysis and Design
1950s: focus on efficient automation of existing processes 1960s: advent of 3GL, faster and more reliable computers 1970s: system development becomes more like an engineering discipline 1980s: major breakthrough with 4GL, CASE tools, object oriented methods 1990s: focus on system integration, GUI applications, client/server platforms, Internet The new century: Web application development, wireless PDAs, component-based applications
8
Categories Information systems fall into one of the following eight categories: Transaction processing systems (TPS). Office automation systems (OAS). Knowledge work systems (KWS). Management information systems (MIS). Decision support systems (DSS). Expert systems (ES) and Artificial Intelligence (AI). Group decision support systems (GDSS) and Computer-Supported Collaborative Work Systems. Executive support systems (EES). Kendall & Kendall 2005 Pearson Prentice Hall
9
Types of Information Systems and Systems Development
Transaction Processing Systems (TPS) Automate handling of data about business activities (transactions) Process orientation Management Information Systems (MIS) Converts raw data from transaction processing system into meaningful form Data orientation Decision Support Systems (DSS) Designed to help decision makers Provides interactive environment for decision making Involves data warehouses, executive information systems (EIS) Database, model base, user dialogue
10
Types of Information Systems and Systems Development (cont.)
11
New Technologies New technologies are being integrated into traditional systems: Ecommerce uses the Web to perform business activities. Enterprise Resource Planning (ERP) has the goal of integrating many different information systems within the corporation. Wireless and handheld devices, including mobile commerce (mcommerce). Open source software. Kendall & Kendall 2005 Pearson Prentice Hall
12
Kendall & Kendall 2005 Pearson Prentice Hall
13
Advantages of Using the Web
The benefits of using the Web are: Increasing awareness of the availability of the service, product, industry, person, or group. 24-hour access for users. Standard interface design. Creating a global system. Kendall & Kendall 2005 Pearson Prentice Hall
14
Nature of Analysis and Design
Systems analysis and design is a systematic approach to: Identifying problems, opportunities, and objectives. Analyzing the information flows in organizations. Designing computerized information systems to solve a problem. Kendall & Kendall 2005 Pearson Prentice Hall
15
Systems Analyst Systems analysts act as:
Outside consultants to businesses. Supporting experts within a business. As change agents. Analysts are problem solvers, and require communication skills. Analysts must be ethical with users and customers. Kendall & Kendall 2005 Pearson Prentice Hall
16
Developing Information Systems and the SDLC
System Development Methodology Standard process followed in an organization Consists of: Analysis Design Implementation Maintenance
17
Systems Development Life Cycle (SDLC)
Traditional methodology for developing, maintaining, and replacing information systems Phases in SDLC: Planning Analysis Design Implementation Maintenance Hoffer, George & Valacich
18
Traditional Waterfall SDLC
One phase begins when another completes, little backtracking and looping
19
Problems with Waterfall Approach
System requirements “locked in” after being determined (can't change) Limited user involvement (only in requirements phase) Too much focus on milestone deadlines of SDLC phases to the detriment of sound development practices
20
Alternatives to Traditional Waterfall SDLC
Prototyping CASE tools Joint Application Design (JAD) Rapid Application Development (RAD) Agile Methodologies eXtreme Programming ETHICS. Project Champions. Soft Systems Methodology. Multi-view.
21
Standard and Evolutionary Views of SDLC
22
Kendall & Kendall 2005 Pearson Prentice Hall
24
Systems Development Life Cycle
The systems development life cycle is a systematic approach to solving business problems. It is divided into seven phases. Each phase has unique activities. Kendall & Kendall Kendall & Kendall 2005 Pearson Prentice Hall
25
Kendall & Kendall 2005 Pearson Prentice Hall
26
Phase 1 Identifying: Personnel involved: Problems. Opportunities.
Objectives. Personnel involved: Analyst. User management. Systems management. Kendall & Kendall 2005 Pearson Prentice Hall
27
Phase 2 Determining information requirements:
Interview management, operations personnel. Gather systems/operating documents. Use questionnaires. Observe the system and personnel involved. Learn the who, what, where, when, and how, and the why for each of these. Kendall & Kendall 2005 Pearson Prentice Hall
28
Phase 2 (Continued) Personnel involved: Analyst. User management.
User operations workers. Systems management. Kendall & Kendall 2005 Pearson Prentice Hall
29
Phase 3 Analyzing system needs: Create data flow diagrams.
Document procedural logic for data flow diagram processes. Complete the data dictionary. Make semistructured decisions. Prepare and present the system proposal. Recommend the optimal solution to management. Kendall & Kendall 2005 Pearson Prentice Hall
30
Phase 3 (Continued) Personnel involved: Analyst. User management.
Systems management. Kendall & Kendall 2005 Pearson Prentice Hall
31
Phase 4 Designing the recommended system: Design the user interface.
Design output. Design input. Design system controls. Design files and/or database. Produce program specifications. Produce decision trees or tables. Kendall & Kendall 2005 Pearson Prentice Hall
32
Phase 4 (Continued) Personnel involved: Analyst. System designer.
User management. User operations workers. Systems management. Kendall & Kendall 2005 Pearson Prentice Hall
33
Phase 5 Developing and documenting software:
Design computer programs using structure charts, Nassi-Schneiderman charts, and pseudocode. Walkthrough program design. Write computer programs. Document software with help files, procedure manuals, and Web sites with Frequently Asked Questions. Kendall & Kendall 2005 Pearson Prentice Hall
34
Phase 5 (Continued) Personnel involved: Analyst. System designer.
Programmers. Systems management. Kendall & Kendall 2005 Pearson Prentice Hall
35
Phase 6 Testing and maintaining the system:
Test and debug computer programs. Test the computer system. Enhance system. Kendall & Kendall 2005 Pearson Prentice Hall
36
Phase 6 (Continued) Personnel involved: Analyst. System designer.
Programmers. Systems management. Kendall & Kendall 2005 Pearson Prentice Hall
37
Phase 7 Implementing and evaluating the system: Plan conversion.
Train users. Purchase and install new equipment. Convert files. Install system. Review and evaluate system. Kendall & Kendall 2005 Pearson Prentice Hall
38
Phase 7 (Continued) Personnel involved: Analyst. System designer.
Programmers. User management. User operations workers. Systems management. Kendall & Kendall 2005 Pearson Prentice Hall
39
System Maintenance System maintenance is:
Removing undetected errors, and Enhancing existing software. Time spent on maintenance typically ranges from percent of total time. Kendall & Kendall 2005 Pearson Prentice Hall
40
System Enhancements Systems are enhanced for the following reasons:
Adding additional features to the system. Business and governmental requirements change over time. Technology, hardware, and software are rapidly changing. Kendall & Kendall 2005 Pearson Prentice Hall
41
The Heart of the Systems Development Process
Current practice combines analysis, design, and implementation into a single iterative and parallel process of activities
42
Joint Application Design (JAD)
Structured process involving users, analysts, and managers Several-day intensive workgroup sessions Purpose: to specify or review system requirements
43
Rapid Application Development (RAD)
Methodology to decrease design and implementation time Involves: prototyping, JAD, CASE tools, and code generators
44
Prototyping Iterative development process:
Requirements quickly converted to a working system System is continually revised Close collaboration between users and analysts
45
Agile Methodologies Motivated by recognition of software development as fluid, unpredictable, and dynamic Three key principles Adaptive rather than predictive Emphasize people rather than roles Self-adaptive processes
46
eXtreme Programming (XP)
Extreme programming takes good software development practices and pushes them to the limit. It is based on: Values. Principles. Core practices. Kendall & Kendall 2005 Pearson Prentice Hall
47
eXtreme Programming Short, incremental development cycles
Automated tests Two-person programming teams Coding and testing operate together Advantages: Communication between developers High level of productivity High-quality code
48
Extreme Programming (XP) (Continued)
Extreme programming values are: Communication. Simplicity. Feedback. Courage. Kendall & Kendall 2005 Pearson Prentice Hall
49
Object-Oriented Analysis and Design
Object-oriented (O-O) analysis and design is used to build object-oriented programs. O-O programming examines the objects of a system. Objects are grouped into classes for optimal reuse and maintainability. Kendall & Kendall 2005 Pearson Prentice Hall
50
Based on objects rather than data or processes
Object: a structure encapsulating attributes and behaviors of a real-world entity Object class: a logical grouping of objects sharing the same attributes and behaviors Inheritance: hierarchical arrangement of classes enable subclasses to inherit properties of superclasses
51
The Unified Modeling Language
The Unified Modeling Language (UML) is an industry standard for modeling object-oriented systems. It breaks down a system into a use case model. Kendall & Kendall 2005 Pearson Prentice Hall
52
Rational Unified Process (RUP) involves an iterative, incremental approach to systems development
53
Rapid Application Development
Rapid Application development (RAD) is an object-oriented approach to systems development. Kendall & Kendall 2005 Pearson Prentice Hall
54
Kendall & Kendall 2005 Pearson Prentice Hall
55
CASE Tools CASE tools are automated, microcomputer-based software packages for systems analysis and design. Four reasons for using CASE tools are: To increase analyst productivity. Facilitate communication among analysts and users. Providing continuity between life cycle phases. To assess the impact of maintenance. Kendall & Kendall 2005 Pearson Prentice Hall
56
CASE Tools Computer-Aided Software Engineering
Software tools providing automated support for systems development Project dictionary/workbook: system description and specifications Diagramming tools Example products: Oracle Designer, Rational Rose, Visible Analyst
57
CASE Tool Categories CASE tools may be divided into several categories
Upper CASE (also called front-end CASE) tools, used to perform analysis and design. Lower CASE (also called back-end CASE). These tools generate computer language source code from CASE design. Integrated CASE, performing both upper and lower CASE functions. Kendall & Kendall 2005 Pearson Prentice Hall
58
Upper CASE Upper CASE tools: Create and modify the system design.
Store data in a project repository. The repository is a collection of records, elements, diagrams, screens, reports, and other project information. These CASE tools model organizational requirements and define system boundaries. Kendall & Kendall 2005 Pearson Prentice Hall
59
Lower CASE Lower CASE tools generate computer source code from the CASE design. Source code may usually be generated in several languages. Kendall & Kendall 2005 Pearson Prentice Hall
60
Advantages of Generating Code
Time to develop new systems decreases. The time to maintain generated code is less than to maintain traditional systems. Computer programs may be generated in more than one language. CASE design may be purchased from third-party vendors and tailored to organizational needs. Generated code is free from program coding errors. Kendall & Kendall 2005 Pearson Prentice Hall
61
Kendall & Kendall 2005 Pearson Prentice Hall
62
Reverse Engineering Reverse engineering is generating the CASE design from computer program code. Source code is examined, analyzed, and converted into repository entities. Kendall & Kendall 2005 Pearson Prentice Hall
63
Reverse Engineering (Continued)
Reverse engineering produces (depending on the tool set used): Data structures and elements, describing the files, records, and field. Screen designs, if the program is online. Report layouts for batch programs. A structure chart showing the hierarchy of the modules in the program. Database design and relationships. Kendall & Kendall 2005 Pearson Prentice Hall
64
Advantages of Reverse Engineering
Reverse Engineering has the following advantages: Reduced system maintenance time. Program documentation is produced for loosely documented programs. Structured programs may be generated from unstructured, older programs. Future system maintenance is easier to implement. Unused portions of programs may be eliminated. Kendall & Kendall 2005 Pearson Prentice Hall
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.