This chapter introduces systems analysis and design and discusses the impact of information technology on business. It defines the components of an information system as hardware, software, data, processes, and people. The chapter also explains different types of information systems and the role of systems analysts in developing systems using various methods like structured analysis, object-oriented analysis, and agile development.
This chapter introduces systems analysis and design and information systems. It discusses how information technology impacts business strategy and defines the components of an information system. It also explains different types of information systems and development methods like structured analysis, object-oriented analysis, and agile development. The role of systems analysts and how they help develop high-quality information systems is also covered.
This chapter introduces systems analysis and design. It discusses how information technology impacts business strategy and defines the components of an information system. It also explains different types of information systems and development methods like structured analysis, object-oriented analysis, and agile methods. The role of systems analysts and developing high-quality information systems is also covered.
This document provides an overview of systems analysis and design. It discusses the role of the systems analyst and describes the typical software development process. This includes methodologies, techniques, and tools used for analysis and design. It also summarizes key components of an information system like data, data flows, and processing logic. Finally, it outlines the traditional systems development life cycle with its phases of project identification, analysis, design, implementation, and maintenance.
System analysis and design
Introduction
Information system components
Business today
Modeling business operation
Business information systems
What information do user need
Systems development tools
Systems development methods
Chapter exercises
The document discusses key topics in system design, including different types of information systems and their users. It describes the components of information systems as hardware, software, data, processes, and people. Various system development tools and techniques are covered, such as modeling, prototyping, and CASE tools. Structured analysis and object-oriented methodology are distinguished. The systems development life cycle and roles of systems analysts are defined.
LECTURE 1-BASIC CONCEPT OF INFORMATION SYSTEM.pptxAOmaAli
This document provides an overview of information systems analysis and design. It defines information systems as methods used by companies to create and maintain systems that perform basic business functions. The main goal is to improve organizational systems through software development and employee training. Systems analysts perform analysis and design based on understanding organizational objectives, structure, and processes as well as how to exploit information technology. A system is defined as an interrelated set of business procedures used within an organization to turn data into information.
This document discusses the key principles and learning objectives for Chapter 12 of the textbook "Principles of Information Systems, Tenth Edition". It covers the importance of teamwork in systems development and identifies the roles of key participants. It also discusses different systems development life cycles like traditional, prototyping, and rapid application development. Finally, it outlines factors that influence the success or failure of systems development projects, including project planning, managing change, and quality standards.
The document describes the systems development life cycle (SDLC) as a framework for developing information systems using well-defined sequential phases: planning, analysis, design, implementation, and maintenance. It explains the key tasks for each phase and also discusses newer approaches like prototyping, outsourcing options, and agile methodologies.
This chapter introduces systems analysis and design and information systems. It discusses how information technology impacts business strategy and defines the components of an information system. It also explains different types of information systems and development methods like structured analysis, object-oriented analysis, and agile development. The role of systems analysts and how they help develop high-quality information systems is also covered.
This chapter introduces systems analysis and design. It discusses how information technology impacts business strategy and defines the components of an information system. It also explains different types of information systems and development methods like structured analysis, object-oriented analysis, and agile methods. The role of systems analysts and developing high-quality information systems is also covered.
This document provides an overview of systems analysis and design. It discusses the role of the systems analyst and describes the typical software development process. This includes methodologies, techniques, and tools used for analysis and design. It also summarizes key components of an information system like data, data flows, and processing logic. Finally, it outlines the traditional systems development life cycle with its phases of project identification, analysis, design, implementation, and maintenance.
System analysis and design
Introduction
Information system components
Business today
Modeling business operation
Business information systems
What information do user need
Systems development tools
Systems development methods
Chapter exercises
The document discusses key topics in system design, including different types of information systems and their users. It describes the components of information systems as hardware, software, data, processes, and people. Various system development tools and techniques are covered, such as modeling, prototyping, and CASE tools. Structured analysis and object-oriented methodology are distinguished. The systems development life cycle and roles of systems analysts are defined.
LECTURE 1-BASIC CONCEPT OF INFORMATION SYSTEM.pptxAOmaAli
This document provides an overview of information systems analysis and design. It defines information systems as methods used by companies to create and maintain systems that perform basic business functions. The main goal is to improve organizational systems through software development and employee training. Systems analysts perform analysis and design based on understanding organizational objectives, structure, and processes as well as how to exploit information technology. A system is defined as an interrelated set of business procedures used within an organization to turn data into information.
This document discusses the key principles and learning objectives for Chapter 12 of the textbook "Principles of Information Systems, Tenth Edition". It covers the importance of teamwork in systems development and identifies the roles of key participants. It also discusses different systems development life cycles like traditional, prototyping, and rapid application development. Finally, it outlines factors that influence the success or failure of systems development projects, including project planning, managing change, and quality standards.
The document describes the systems development life cycle (SDLC) as a framework for developing information systems using well-defined sequential phases: planning, analysis, design, implementation, and maintenance. It explains the key tasks for each phase and also discusses newer approaches like prototyping, outsourcing options, and agile methodologies.
This document outlines the key principles and learning objectives covered in Chapter 13 of Principles of Information Systems, Ninth Edition. It discusses systems design, implementation, maintenance, and review. Specifically, it covers: 1) the purpose of systems design and differences between logical and physical design, 2) considerations for implementation including acquiring software/hardware and user preparation, and 3) the importance of maintenance and review to extend a system's useful life.
Chapter 4 Requirements ModelInformation Technology Project Management - part ...AxmedMaxamuudYoonis
The chapter discusses requirements modeling techniques used in systems analysis to understand business needs and visualize the proposed system. This includes modeling outputs, inputs, processes and security requirements. It also covers fact-finding methods like interviews, documentation review and questionnaires to gather requirements, as well as documenting findings. The overall goal of systems analysis is to ensure the new system supports business needs before designing it.
The document provides an overview of chapter presentations for an information systems textbook. It states that the presentations cover the chapter objectives, list all objectives at the beginning of each presentation, and can be customized for class needs. Some figures from the chapters are also included.
This chapter discusses systems analysis phase activities like requirements modeling, data and process modeling, and object modeling. It describes techniques like joint application development (JAD), rapid application development (RAD), and agile methods. The chapter objectives are to explain these techniques and how to document requirements, conduct interviews, and develop effective documentation for systems development.
01. Developing Business _ IT Solutions 2011.pptiqbal051663
The document discusses the systems development process, including systems analysis and design, prototyping, user interface design, implementation, project management, and post-implementation activities. It provides learning objectives for each step and examples to illustrate key points. The overall goal is to apply a systems approach to information systems development and management of the development process.
This chapter discusses requirements modeling techniques used in systems analysis, including joint application development, rapid application development, and agile methods. It also covers identifying system requirements through fact-finding techniques like interviews, documentation review, and questionnaires. The goal of systems analysis is to understand business needs and create a foundation for subsequent system design.
The document discusses the key phases of systems development: design, implementation, maintenance, and review. It describes the logical and physical design process, including object-oriented design. Implementation activities like acquiring hardware and software, user training, and testing are also outlined. The importance of ongoing maintenance to fix issues and adapt to changes is highlighted. Systems are regularly reviewed to ensure they continue to meet needs.
The chapter discusses the systems implementation phase, which includes application development, testing, training users, converting data, and installing the new system. It covers structured, object-oriented, and agile development methods. Testing strategies like unit, integration, and system testing are explained. The chapter also discusses documenting the system, training users, converting data, changing over to the new system, and evaluating the new system after implementation.
The document summarizes key points from Chapter 11 of a systems analysis textbook. It discusses the systems implementation phase, which includes application development, testing, training users, converting data, and installing the new system. It also covers post-implementation tasks like evaluating the new system and presenting a final report to management. The chapter objectives are to explain various implementation and testing processes, as well as techniques for training, converting data, installing systems, and evaluating results.
The document discusses requirement gathering and analysis. It emphasizes the importance of requirements in project success and describes key tasks in requirements engineering including inception, elicitation, and elaboration. During inception, questions are asked to understand the problem, stakeholders, and desired solution. Elicitation involves discovering requirements through collaboration and techniques like use cases. Elaboration refines information through analysis modeling with elements like use cases, classes, and behaviors. The goal is a model that defines the functional, informational, and behavioral domains of the problem.
The document describes the sales order processing system flow chart of a company. There are five key departments involved: sales order processing, credit, finished goods, shipping, and billing. The sales order goes through each department in a linear fashion, with copies of documents like purchase orders, sales orders, bills of lading, and invoices being prepared and filed at each step.
The document provides an overview of chapter objectives and key concepts from a textbook on information systems. It discusses the difference between data, information, and knowledge and various types of business information systems like transaction processing systems, enterprise resource planning systems, and decision support systems. It also summarizes the systems development process, competitive strategy, careers in information systems, and global challenges.
This chapter discusses database design and the systems development life cycle (SDLC). It explains that the SDLC traces the development of an information system through planning, analysis, design, implementation, and maintenance phases. Within the information system, the database life cycle (DBLC) describes the development of the database through initial study, design, implementation, testing, operation, and maintenance phases. The chapter also covers topics of conceptual database design, logical design, and physical design.
The document discusses planning and developing information systems. It describes key steps in planning like creating mission and vision statements, strategic and tactical plans, and budgets. Careful planning is necessary for successful enterprise system implementation. Development approaches include the traditional systems development life cycle (SDLC) process of analysis, design, implementation, and support or more agile methods. Analysis involves feasibility studies to determine if a system is needed. Design includes data modeling and testing. Implementation has conversion strategies to transition to the new system. Agile methods emphasize iterative development and user feedback.
This chapter discusses the systems analysis phase of the SDLC. The objectives are to understand the proposed project, ensure it supports business needs, and provide a foundation for design. Key activities include requirements modeling using tools like use case diagrams, data and process modeling, and considering development strategies. The chapter also covers fact-finding techniques like interviews, documentation review and questionnaires to understand requirements and system stakeholders.
Pengantar Analisis Dan Desain Sistem InformasiSherly Uda
This document discusses systems analysis and design. It defines systems analysis and design as the process of creating automated information systems. It discusses the roles of system analysts in identifying ways to improve organizations. System analysts need technical, business, analytical, communication, and interpersonal skills. The document also reviews the systems development life cycle (SDLC) process, which includes planning, analysis, design, implementation, and documentation phases. Different SDLC methodologies like waterfall, prototyping, and agile development are also covered.
This document provides an overview of the Information Systems Analysis and Modeling module. The module aims to help students understand tools and techniques used in information systems development, analyze and design systems, and evaluate methodologies. It covers topics such as requirements determination, object-oriented analysis, conceptual and physical design, and comparing methodologies. Students will be assessed through an exam, critiques of readings, and a requirements analysis assignment. Reading materials include textbooks on information systems development and object-oriented software engineering.
Fundamentals of different kinds of information systems
Roles of systems analysts
Phases in the systems development life cycle as they relate to Human- Computer Interaction (HCI) factors
Computer-Aided Software Engineering (CASE) tools
This document provides an introduction to systems analysis and design. It describes the impact of information technology and defines key terms. It explains different approaches to systems development like structured analysis, object-oriented analysis, and agile methods. It also describes the role of the systems analyst and the skills needed to be successful in the field.
This chapter discusses system architecture and design. It covers selecting an architecture, client/server models, online and batch processing, network topologies, wireless networks, and completing the system design specification. The objectives are to understand issues in selecting an architecture, describe different processing and network designs, and explain how to finalize a system design.
This chapter discusses the systems support and security phase of the SDLC. It covers maintaining and supporting operational systems, including user support, maintenance tasks, performance management, security, backups and disaster recovery. The chapter also addresses future challenges like system obsolescence and outlines strategies for IT professionals to advance their careers through certification.
This document outlines the key principles and learning objectives covered in Chapter 13 of Principles of Information Systems, Ninth Edition. It discusses systems design, implementation, maintenance, and review. Specifically, it covers: 1) the purpose of systems design and differences between logical and physical design, 2) considerations for implementation including acquiring software/hardware and user preparation, and 3) the importance of maintenance and review to extend a system's useful life.
Chapter 4 Requirements ModelInformation Technology Project Management - part ...AxmedMaxamuudYoonis
The chapter discusses requirements modeling techniques used in systems analysis to understand business needs and visualize the proposed system. This includes modeling outputs, inputs, processes and security requirements. It also covers fact-finding methods like interviews, documentation review and questionnaires to gather requirements, as well as documenting findings. The overall goal of systems analysis is to ensure the new system supports business needs before designing it.
The document provides an overview of chapter presentations for an information systems textbook. It states that the presentations cover the chapter objectives, list all objectives at the beginning of each presentation, and can be customized for class needs. Some figures from the chapters are also included.
This chapter discusses systems analysis phase activities like requirements modeling, data and process modeling, and object modeling. It describes techniques like joint application development (JAD), rapid application development (RAD), and agile methods. The chapter objectives are to explain these techniques and how to document requirements, conduct interviews, and develop effective documentation for systems development.
01. Developing Business _ IT Solutions 2011.pptiqbal051663
The document discusses the systems development process, including systems analysis and design, prototyping, user interface design, implementation, project management, and post-implementation activities. It provides learning objectives for each step and examples to illustrate key points. The overall goal is to apply a systems approach to information systems development and management of the development process.
This chapter discusses requirements modeling techniques used in systems analysis, including joint application development, rapid application development, and agile methods. It also covers identifying system requirements through fact-finding techniques like interviews, documentation review, and questionnaires. The goal of systems analysis is to understand business needs and create a foundation for subsequent system design.
The document discusses the key phases of systems development: design, implementation, maintenance, and review. It describes the logical and physical design process, including object-oriented design. Implementation activities like acquiring hardware and software, user training, and testing are also outlined. The importance of ongoing maintenance to fix issues and adapt to changes is highlighted. Systems are regularly reviewed to ensure they continue to meet needs.
The chapter discusses the systems implementation phase, which includes application development, testing, training users, converting data, and installing the new system. It covers structured, object-oriented, and agile development methods. Testing strategies like unit, integration, and system testing are explained. The chapter also discusses documenting the system, training users, converting data, changing over to the new system, and evaluating the new system after implementation.
The document summarizes key points from Chapter 11 of a systems analysis textbook. It discusses the systems implementation phase, which includes application development, testing, training users, converting data, and installing the new system. It also covers post-implementation tasks like evaluating the new system and presenting a final report to management. The chapter objectives are to explain various implementation and testing processes, as well as techniques for training, converting data, installing systems, and evaluating results.
The document discusses requirement gathering and analysis. It emphasizes the importance of requirements in project success and describes key tasks in requirements engineering including inception, elicitation, and elaboration. During inception, questions are asked to understand the problem, stakeholders, and desired solution. Elicitation involves discovering requirements through collaboration and techniques like use cases. Elaboration refines information through analysis modeling with elements like use cases, classes, and behaviors. The goal is a model that defines the functional, informational, and behavioral domains of the problem.
The document describes the sales order processing system flow chart of a company. There are five key departments involved: sales order processing, credit, finished goods, shipping, and billing. The sales order goes through each department in a linear fashion, with copies of documents like purchase orders, sales orders, bills of lading, and invoices being prepared and filed at each step.
The document provides an overview of chapter objectives and key concepts from a textbook on information systems. It discusses the difference between data, information, and knowledge and various types of business information systems like transaction processing systems, enterprise resource planning systems, and decision support systems. It also summarizes the systems development process, competitive strategy, careers in information systems, and global challenges.
This chapter discusses database design and the systems development life cycle (SDLC). It explains that the SDLC traces the development of an information system through planning, analysis, design, implementation, and maintenance phases. Within the information system, the database life cycle (DBLC) describes the development of the database through initial study, design, implementation, testing, operation, and maintenance phases. The chapter also covers topics of conceptual database design, logical design, and physical design.
The document discusses planning and developing information systems. It describes key steps in planning like creating mission and vision statements, strategic and tactical plans, and budgets. Careful planning is necessary for successful enterprise system implementation. Development approaches include the traditional systems development life cycle (SDLC) process of analysis, design, implementation, and support or more agile methods. Analysis involves feasibility studies to determine if a system is needed. Design includes data modeling and testing. Implementation has conversion strategies to transition to the new system. Agile methods emphasize iterative development and user feedback.
This chapter discusses the systems analysis phase of the SDLC. The objectives are to understand the proposed project, ensure it supports business needs, and provide a foundation for design. Key activities include requirements modeling using tools like use case diagrams, data and process modeling, and considering development strategies. The chapter also covers fact-finding techniques like interviews, documentation review and questionnaires to understand requirements and system stakeholders.
Pengantar Analisis Dan Desain Sistem InformasiSherly Uda
This document discusses systems analysis and design. It defines systems analysis and design as the process of creating automated information systems. It discusses the roles of system analysts in identifying ways to improve organizations. System analysts need technical, business, analytical, communication, and interpersonal skills. The document also reviews the systems development life cycle (SDLC) process, which includes planning, analysis, design, implementation, and documentation phases. Different SDLC methodologies like waterfall, prototyping, and agile development are also covered.
This document provides an overview of the Information Systems Analysis and Modeling module. The module aims to help students understand tools and techniques used in information systems development, analyze and design systems, and evaluate methodologies. It covers topics such as requirements determination, object-oriented analysis, conceptual and physical design, and comparing methodologies. Students will be assessed through an exam, critiques of readings, and a requirements analysis assignment. Reading materials include textbooks on information systems development and object-oriented software engineering.
Fundamentals of different kinds of information systems
Roles of systems analysts
Phases in the systems development life cycle as they relate to Human- Computer Interaction (HCI) factors
Computer-Aided Software Engineering (CASE) tools
This document provides an introduction to systems analysis and design. It describes the impact of information technology and defines key terms. It explains different approaches to systems development like structured analysis, object-oriented analysis, and agile methods. It also describes the role of the systems analyst and the skills needed to be successful in the field.
Similar to chapter01-120827115344-phpapp01.pdf (20)
This chapter discusses system architecture and design. It covers selecting an architecture, client/server models, online and batch processing, network topologies, wireless networks, and completing the system design specification. The objectives are to understand issues in selecting an architecture, describe different processing and network designs, and explain how to finalize a system design.
This chapter discusses the systems support and security phase of the SDLC. It covers maintaining and supporting operational systems, including user support, maintenance tasks, performance management, security, backups and disaster recovery. The chapter also addresses future challenges like system obsolescence and outlines strategies for IT professionals to advance their careers through certification.
This chapter discusses project management techniques including work breakdown structures, task patterns, critical path analysis, Gantt charts, PERT/CPM charts, risk management, and monitoring and controlling projects. It explains how to plan a project by identifying tasks, estimating durations, and determining dependencies. Project managers use scheduling tools to track progress and ensure projects are completed on time and on budget. Risk management and addressing issues that arise are also important for project success.
This chapter discusses analyzing the business case for IT projects. It explains that a business case justifies a proposed project based on reasons and benefits for the company. The chapter also describes strategic planning, which examines a company's vision and mission and leads to goals and objectives. Finally, the chapter outlines the preliminary investigation process, which includes understanding requirements, analyzing costs/benefits, and evaluating feasibility before presenting recommendations to management.
This chapter discusses software development strategies, including software as a service, web-based development, outsourcing, and in-house development. It covers evaluating alternatives through cost-benefit analysis and financial tools. The software acquisition process involves identifying requirements, potential vendors, evaluating alternatives, performing cost analysis, making a recommendation, and implementing the solution. The chapter also describes the transition from analysis to design, including creating system documentation and prototypes.
This chapter discusses data and process modeling tools used by systems analysts to develop a logical model of an information system. It describes data flow diagrams (DFDs) which use symbols to show how data moves through a system, a data dictionary which defines all data elements, and process description tools like structured English and decision tables. The goal is to develop a logical model that shows what the system does without describing how it is implemented physically.
This chapter discusses object modeling and the Unified Modeling Language (UML). It defines key object-oriented analysis concepts like objects, attributes, methods, classes and relationships. The chapter describes UML diagramming techniques including use case diagrams, class diagrams, sequence diagrams, state transition diagrams and activity diagrams. It emphasizes organizing the object model and using CASE tools to develop diagrams representing the system components.
This chapter discusses data design concepts including file-oriented systems, database management systems, data design terminology, data relationships, normalization, and entity relationship diagrams. It also covers data storage and access methods like data warehousing and mining. The chapter concludes with a discussion of data controls and security measures.
This document discusses system design and decomposing systems into subsystems. It covers:
- Analyzing requirements, functional models, object models, and dynamic models to inform system design goals and subsystem decomposition.
- Identifying design goals and typical trade-offs between goals like functionality vs usability.
- Decomposing the system into subsystems using concepts like layers, partitions, and subsystem interfaces. Properties of good subsystem decomposition like low coupling are discussed.
- The relationship between subsystems, layers, and virtual machines is explained as a way to structure complex systems hierarchically.
This presentation was provided by Steph Pollock of The American Psychological Association’s Journals Program, and Damita Snow, of The American Society of Civil Engineers (ASCE), for the initial session of NISO's 2024 Training Series "DEIA in the Scholarly Landscape." Session One: 'Setting Expectations: a DEIA Primer,' was held June 6, 2024.
How to Manage Your Lost Opportunities in Odoo 17 CRMCeline George
Odoo 17 CRM allows us to track why we lose sales opportunities with "Lost Reasons." This helps analyze our sales process and identify areas for improvement. Here's how to configure lost reasons in Odoo 17 CRM
A review of the growth of the Israel Genealogy Research Association Database Collection for the last 12 months. Our collection is now passed the 3 million mark and still growing. See which archives have contributed the most. See the different types of records we have, and which years have had records added. You can also see what we have for the future.
Executive Directors Chat Leveraging AI for Diversity, Equity, and InclusionTechSoup
Let’s explore the intersection of technology and equity in the final session of our DEI series. Discover how AI tools, like ChatGPT, can be used to support and enhance your nonprofit's DEI initiatives. Participants will gain insights into practical AI applications and get tips for leveraging technology to advance their DEI goals.
Main Java[All of the Base Concepts}.docxadhitya5119
This is part 1 of my Java Learning Journey. This Contains Custom methods, classes, constructors, packages, multithreading , try- catch block, finally block and more.
This presentation includes basic of PCOS their pathology and treatment and also Ayurveda correlation of PCOS and Ayurvedic line of treatment mentioned in classics.
A workshop hosted by the South African Journal of Science aimed at postgraduate students and early career researchers with little or no experience in writing and publishing journal articles.
हिंदी वर्णमाला पीपीटी, hindi alphabet PPT presentation, hindi varnamala PPT, Hindi Varnamala pdf, हिंदी स्वर, हिंदी व्यंजन, sikhiye hindi varnmala, dr. mulla adam ali, hindi language and literature, hindi alphabet with drawing, hindi alphabet pdf, hindi varnamala for childrens, hindi language, hindi varnamala practice for kids, https://www.drmullaadamali.com
How to Build a Module in Odoo 17 Using the Scaffold MethodCeline George
Odoo provides an option for creating a module by using a single line command. By using this command the user can make a whole structure of a module. It is very easy for a beginner to make a module. There is no need to make each file manually. This slide will show how to create a module using the scaffold method.
How to Build a Module in Odoo 17 Using the Scaffold Method
chapter01-120827115344-phpapp01.pdf
1. Systems Analysis and Design
9th Edition
Chapter 1
Introduction to Systems Analysis and
Design
2. Chapter Objectives
• Discuss the impact of information technology on
business strategy and success
• Define an information system and describe its
components
• Explain how profiles and models can represent
business functions and operations
• Explain how the Internet has affected business
strategies and relationships
• Identify various types of information systems and
explain who uses them
2
3. Chapter Objectives
• Distinguish between structured analysis,
object-oriented analysis, and agile methods
• Compare the traditional waterfall model with
agile methods and models
• Apply five basic guidelines for systems
development
• Discuss the role of the information technology
department and the systems analysts who
work there
3
4. Introduction
• Companies use
information as a weapon
in the battle to increase
productivity, deliver
quality products and
services, maintain
customer loyalty, and
make sound decisions
• Information technology
can mean the difference
between success and
failure
4
5. The Impact of Information Technology
• Information Technology (IT)
– Combination of hardware and software products
and services that companies use to manage,
access, communicate, and share information
• The Future
– Three issues that will shape the future
• Changes in world
• Changes in technology
• Changes in client demand
5
6. The Impact of Information Technology
• Systems Development
– Business information systems are developed by
people who are technically qualified, business-
oriented, and highly motivated
– Must be good communicators with strong
analytical and critical thinking skills
6
7. The Impact of Information Technology
• Systems Analysis and Design
– Systems Analysis and Design
• Step-by-step process for developing high-quality
information systems
– Systems Analyst
• Plan, develop, and maintain information systems
7
8. The Impact of Information Technology
• Who develops Information Systems?
– In-house applications
– Software packages
– Internet-based application services
– Outsourcing
– Custom solutions
– Enterprise-wide software strategies
– How versus What
8
9. Information System Components
• A system is a set of related components that
produces specific results
• A Mission-critical system is one that is vital to a
company’s operations
• Data consists of basic facts that are the system’s
raw material
• Information is data that has been transformed
into output that is valuable to users
• Information systems have five key components:
hardware, software, data, processes, and people
9
10. Information System Components
• Hardware
– Is the physical layer of
the information system
– Moore’s Law
• Software
– System software
– Application software
– Enterprise applications
10
11. Information System Components
• Software
– Horizontal system
– Vertical system
– Legacy systems
• Data
– Tables store data
– Linked tables work
together to supply
data
11
12. Information System Components
• Processes
– Describe the tasks and
business functions that
users, managers, and IT
staff members perform
to achieve specific
results
• People
– Stakeholders
– Users, or end users
12
13. Understanding The Business
• Business Process Modeling
• Business Profile
• Business Models
– Business model
– Business process
– Business process reengineering (BPR)
13
14. Understanding The Business
• New Kinds of
Companies
– Production-oriented
– Service-oriented
– Internet-dependent
– Dot-com (.com)
– Brick-and-mortar
14
15. Impact of the Internet
• E-Commerce or I-Commerce
• B2C (Business-to-Consumer)
• B2B (Business-to-Business)
– EDI
– Extensible markup language (XML)
– Supply chain management (SCM)
– Supplier relationship management (SRM)
15
16. Business Information Systems
• In the past, IT managers divided systems into
categories based on the user group the system
served
– Office systems
– Operational systems
– Decision support systems
– Executive information systems
16
17. Business Information Systems
• Today, identify a system by its functions and
features, rather than by its users
– Enterprise computing systems
– Transaction processing systems
– Business support systems
– Knowledge management systems
– User productivity systems
17
18. Business Information Systems
• Enterprise computing
systems
– Support company-wide
operations and data
management
requirements
– Enterprise resource
planning (ERP)
– Many hardware and
software vendors target
the enterprise
computing market
18
19. Business Information Systems
• Transaction processing
systems
– Involve large amounts of
data and are mission-
critical systems
– Efficient because they
process a set of
transaction-related
commands as a group
rather than individually
19
20. Business Information Systems
• Business support systems
– Provide job-related information to users at all
levels of a company
– Management information systems (MIS)
– Radio frequency identification (RFID)
– What-if
20
21. Business Information Systems
• Knowledge management systems
– Called expert systems
– Simulate human reasoning by combining a
knowledge base and inference rules
– Many knowledge management systems use a
technique called fuzzy logic
21
22. Business Information Systems
• User productivity systems
– Technology that improves productivity
– Groupware
• Information systems integration
– Most large companies require systems that
combine transaction processing, business support,
knowledge management, and user productivity
features
22
24. Systems Development Tools
• Modeling
– Business model
– Requirements model
– Data model
– Object model
– Network model
– Process model
24
25. Systems Development Tools
• Prototyping
– Prototype
– Speeds up the development process significantly
– Important decisions might be made too early,
before business or IT issues are thoroughly
understood
– Can be an extremely valuable tool
25
26. Systems Development Tools
• Computer-Aided Systems Engineering (CASE)
Tools
– Also called computer-aided software engineering
– CASE tools
– Can generate program code, which speeds the
implementation process
26
27. Systems Development Methods
• Structured Analysis
– Systems development
life cycle (SDLC)
– Predictive approach
– Uses a set of process
models to describe a
system graphically
– Process-centered
technique
– Waterfall model
27
28. Systems Development Methods
• Structured Analysis
– Deliverable or end product
– Disadvantage in the built-in structure of the SDLC,
because the waterfall model does not emphasize
interactivity among the phases
– This criticism can be valid if the SDLC phases are
followed too rigidly
– Adjacent phases usually interact
28
29. Systems Development Methods
• Structured Analysis
– The SDLC model usually includes five steps
• Systems planning
• Systems analysis
• Systems design
• Systems implementation
• Systems support and security
29
30. Systems Development Methods
• Structured Analysis
– Systems Planning
• Systems planning phase
• Systems request – begins the process & describes
problems or desired changes
• Purpose of this phase is to perform a preliminary
investigation
• Key part of preliminary investigation is a feasibility
study
30
31. Systems Development Methods
• Structured Analysis
– Systems Analysis
• Deliverable is the System requirements document
– Systems Design
• Deliverable is system design specification
• Management and user involvement is critical
31
32. Systems Development Methods
• Structured Analysis
– Systems Implementation
• New system is constructed
– Systems Support and Security
• A well-designed system must be secure, reliable,
maintainable, and scalable
• Most information systems need to be updated
significantly or replaced after several years of operation
32
33. Systems Development Methods
• Object-oriented
Analysis
– Combines data &
processes that act on the
data into things called
objects
– Object is a member of a
class
– Objects possess
properties
– Methods change an
object’s properties
33
34. Systems Development Methods
• Object-Oriented Analysis
– A message requests specific behavior or
information from another object
– Usually follow a series of analysis and design
phases that are similar to the SDLC
– Interactive model
34
35. Systems Development Methods
• Agile Methods
– Are the newest development
– Emphasize continuous feedback
– Iterative development
– Agile community has published the Agile
Manifesto
– Spiral model
35
36. Systems Development Methods
• Agile Methods
– Agile process determines the end result
– Other adaptive variations and related methods
exist
– Two examples are Scrum and Extreme
Programming (XP)
– Analysts should understand the pros and cons of
any approach before selecting a development
method
36
37. Systems Development Methods
• Other Development Methods
– Joint application development (JAD)
– Rapid application development (RAD)
– Might encounter other systems development
techniques
– Rational Unified Process (RUP®)
– Microsoft Solutions Framework (MSF)
37
38. Systems Development Guidelines
• Develop a project plan
• Involve users and listen carefully to them
• Use project management tools to identify
tasks and milestones
• Develop accurate cost and benefit information
• Remain flexible
38
40. The Systems Analyst
• Responsibilities
– Translate business requirements into IT projects
• Knowledge, Skills, and Education
• Needs technical knowledge, strong oral and
written communication skills and analytic ability,
an understanding of business operations, and
critical thinking skills
• Certification
– Important credential
40
41. The Systems Analyst
• Career Opportunities
– Job titles
– Company organization
– Company size
– Corporate culture
– Salary, location, and future growth
41
42. Chapter Summary
• IT refers to the combination of hardware and
software resources that companies use to
manage, access, communicate, and share
information
• The essential components of an information
system are hardware, software, data, processes,
and people
• Successful companies offer a mix of products,
technical and financial services, consulting, and
customer support
42
43. Chapter Summary
• Information systems are identified as
enterprise computing systems, transaction
processing systems, business support systems,
knowledge management systems, or user
productivity systems
• Organization structure includes top managers,
middle managers and knowledge workers,
supervisors and team leaders
43
44. Chapter Summary
• The IT department develops, maintains and
operates a company’s information systems
• Systems analysts need a combination of
technical and business knowledge, analytical
ability, and communication skills
• Systems analysts need to consider salary,
location, and future growth potential when
making a career decision
44