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.
This chapter provides an overview of systems analysis and design methods. It defines key terms like information systems, stakeholders, and systems analysts. It also outlines important business and technology drivers that influence modern system development like globalization, e-commerce, and mobile technologies. Finally, it presents a simple system development process and discusses project and process management.
Cascade Human Resources Ltd plays host to Denis Bernard from HR Comparison as he guides us through the fundamentals of choosing the right HR System for your organisation.
After which, HR product specialist Marc Greggains will give you a brief overview of the sponsor Cascade HR and Ric Mellor, Cascade Product Services Manager, will guide you through the essentials you need to know for preparing and implementing your HR system project.
The document discusses systems development and analysis. It covers the following key points in 3 sentences:
The systems development life cycle involves 5 phases: analysis, conceptual design, physical design, implementation, and operations/maintenance. Planning is important to coordinate projects and ensure consistency, efficiency, and lower costs. A feasibility study analyzes technical, operational, economic, legal, and scheduling feasibility to determine if a project should proceed.
The system approach involves recognizing and defining problems, developing and evaluating alternative solutions, selecting the best solution, designing it, and implementing and evaluating it. Systems thinking sees interrelationships rather than linear cause-and-effect chains. The systems development lifecycle is an iterative process that includes investigation, analysis, design, implementation, and evaluation. Investigation assesses feasibility, requirements are determined in analysis, design specifies the solution, and implementation puts the system to use.
This document provides an introduction to information systems for non-technical managers. It discusses how information systems are designed to help managers understand the implications of technology and prepare for advances like artificial intelligence. The document then outlines several key topics that will be covered, including data, information, knowledge, and different models that illustrate their relationships. It also defines what an information system is and distinguishes between information technology and information systems.
This document provides an introduction to information systems and key concepts in knowledge management and expert systems.
It begins with defining information systems and distinguishing them from information technology. It then covers models for understanding the relationships between data, information, knowledge and wisdom.
The document discusses different types of information systems like transaction processing systems, management information systems, decision support systems, and executive information systems. It also covers knowledge management concepts like explicit and tacit knowledge, and how information technology can be used to create, capture, share and distribute organizational knowledge.
Finally, the document introduces expert systems, their components like the knowledge base and inference engine, and techniques like forward and backward chaining used in the inference engine. It provides examples
This document provides an introduction to information systems for non-technical managers. It discusses key concepts like the DIKW model, which organizes data, information, knowledge and wisdom hierarchically. It also discusses different types of information systems like TPS, MIS, DSS and EIS and how they map to different levels of the organization and support different types of decisions. Transaction processing systems are described as capturing daily transactions while management information systems provide performance reports. Decision support systems help with non-routine decisions using models or data. Executive information systems support strategic decisions with internal and external data. The document concludes with a discussion of knowledge management and expert systems, which use artificial intelligence to capture and distribute expert knowledge.
This chapter provides an overview of systems analysis and design methods. It defines key terms like information systems, stakeholders, and systems analysts. It also outlines important business and technology drivers that influence modern system development like globalization, e-commerce, and mobile technologies. Finally, it presents a simple system development process and discusses project and process management.
Cascade Human Resources Ltd plays host to Denis Bernard from HR Comparison as he guides us through the fundamentals of choosing the right HR System for your organisation.
After which, HR product specialist Marc Greggains will give you a brief overview of the sponsor Cascade HR and Ric Mellor, Cascade Product Services Manager, will guide you through the essentials you need to know for preparing and implementing your HR system project.
The document discusses systems development and analysis. It covers the following key points in 3 sentences:
The systems development life cycle involves 5 phases: analysis, conceptual design, physical design, implementation, and operations/maintenance. Planning is important to coordinate projects and ensure consistency, efficiency, and lower costs. A feasibility study analyzes technical, operational, economic, legal, and scheduling feasibility to determine if a project should proceed.
The system approach involves recognizing and defining problems, developing and evaluating alternative solutions, selecting the best solution, designing it, and implementing and evaluating it. Systems thinking sees interrelationships rather than linear cause-and-effect chains. The systems development lifecycle is an iterative process that includes investigation, analysis, design, implementation, and evaluation. Investigation assesses feasibility, requirements are determined in analysis, design specifies the solution, and implementation puts the system to use.
This document provides an introduction to information systems for non-technical managers. It discusses how information systems are designed to help managers understand the implications of technology and prepare for advances like artificial intelligence. The document then outlines several key topics that will be covered, including data, information, knowledge, and different models that illustrate their relationships. It also defines what an information system is and distinguishes between information technology and information systems.
This document provides an introduction to information systems and key concepts in knowledge management and expert systems.
It begins with defining information systems and distinguishing them from information technology. It then covers models for understanding the relationships between data, information, knowledge and wisdom.
The document discusses different types of information systems like transaction processing systems, management information systems, decision support systems, and executive information systems. It also covers knowledge management concepts like explicit and tacit knowledge, and how information technology can be used to create, capture, share and distribute organizational knowledge.
Finally, the document introduces expert systems, their components like the knowledge base and inference engine, and techniques like forward and backward chaining used in the inference engine. It provides examples
This document provides an introduction to information systems for non-technical managers. It discusses key concepts like the DIKW model, which organizes data, information, knowledge and wisdom hierarchically. It also discusses different types of information systems like TPS, MIS, DSS and EIS and how they map to different levels of the organization and support different types of decisions. Transaction processing systems are described as capturing daily transactions while management information systems provide performance reports. Decision support systems help with non-routine decisions using models or data. Executive information systems support strategic decisions with internal and external data. The document concludes with a discussion of knowledge management and expert systems, which use artificial intelligence to capture and distribute expert knowledge.
The document discusses various types of decision support systems that can help managers at different levels of an organization. It describes executive support systems that help senior managers address strategic issues through integrated business information and data visualization. It also discusses expert systems that capture human expertise in specific domains through knowledge bases and inference engines. Finally, it summarizes decision support systems as interactive tools that combine data and models to support semi-structured and unstructured decision-making.
This document discusses how information systems support various business functions like accounting, finance, engineering, supply chain management, and human resources. It explains how systems increase effectiveness and efficiency, and how tools like ERP systems integrate across business functions and organizations to improve information sharing in supply chains.
The document discusses the key aspects of information system development including the system development environment, personnel involved, types of information systems, and the system development life cycle. It notes that system development requires planning, involves users, management, and technical staff. It also outlines common system types like transaction processing systems, management information systems, expert systems, and decision support systems. Finally, it describes the main phases of system development as preliminary investigation, analysis, design, development, implementation, and maintenance.
CASE (COMPUTER AIDED SOFTWARE ENGINEERING)
CASE and its Scope
CASE support in software life cycle documentation
project management
Internal Interface
Reverse Software Engineering
Architecture of CASE environment.
This chapter discusses output design and prototyping. It defines different types of outputs like internal, external and turnaround outputs. It describes report formats like detailed, summary and exception reports. The chapter also covers output implementation methods, chart types, output design principles and guidelines. It provides examples of tabular, graphical and other types of report prototypes.
The document discusses implementing an ERP management system for a real estate company called Nirmala Consol Private Limited. Currently, the company's bill generation process takes 3 months to complete. Implementing an ERP system would integrate different departments like marketing, finance, IT, and HR. It would allow efficient data sharing and minimize the bill generation process to only 4 days. An ERP system would improve information quality, decision making, planning, cash management, inventory management, productivity and other operational functions. It would reduce the time management accountants spend on data collection and increase the time spent on analysis. In conclusion, an ERP system offers long term cost efficiencies and enhances communication and productivity across the organization.
I do not have enough context to participate meaningfully in an interactive class discussion. As an AI system, I do not have personal experiences to draw from. However, based on the material provided, here are some key considerations for mobile application development:
- Small screens require optimized UIs with large touch targets
- Limited memory/processing requires lightweight code and local storage
- Connectivity issues mean offline usage and local data caching are important
- Battery life impacts user experience, so efficiency in networking, processing etc is critical
- User requirements focus more on tasks that can be done on the go versus at a desk
- Sales processes may shift from in-store only to also include options to browse, order etc remotely via mobile for added
This document provides an overview of basic computer and information technology concepts. It discusses how computers receive input, process data, and produce output. It defines information technology as the tools used to receive, process, store, retrieve, print, and transmit information electronically. It also outlines the key components of a computer system, including hardware like the central processing unit, memory, and physical devices; and software programs and applications. Finally, it describes the main hardware components of computers and their functions.
The document discusses internal controls and their importance for businesses. It provides:
1) Three main reasons for internal controls - to achieve business goals, mitigate risks, and ensure compliance.
2) Five interrelated components of internal controls - control environment, risk assessment, control activities, information and communication, and monitoring.
3) A definition of internal control as a system using people, processes, and procedures to reasonably ensure achieving business objectives. Management is responsible for the internal control system.
1. Computers can automate controls but also enable easier circumvention of segregation of duties. Strict access controls and monitoring are needed.
2. Digital data and remote access require strong authorization procedures for transactions and sensitive tasks.
3. Recordkeeping is easier but data integrity controls like input validation, processing checks, and audit trails are critical to prevent and detect errors and fraud.
The document summarizes key aspects of the production cycle for a manufacturing business. It discusses four main activities: product design, planning and scheduling, production operations, and cost accounting. It describes important documents and decisions for each activity. The accountant's role is to design an accounting information system that provides necessary cost data to support decision-making at each stage of the production cycle.
The document provides an introduction to Manufacturing Execution Systems (MES) by Michael McClellan, the president of MES Solutions Incorporated. It describes that MES bridges the gap between planning systems like ERP and control systems on the plant floor by collecting online information to manage resources. MES provides benefits like reduced cycle times, inventory, and lead times as well as improved quality and customer service by empowering plant operations with real-time data. The core functions of MES include interfacing with planning systems, managing work orders, tracking inventory and labor, and collecting production data to optimize manufacturing execution.
The chapter discusses strategic uses of information systems and competitive advantage. It explains that strategic information systems help companies gain strategic advantages over competitors through initiatives like reducing costs, creating barriers to entry, establishing customer lock-in, innovating new products and services, and differentiating offerings. While information systems can provide early competitive benefits, these advantages erode over time as competitors catch up, so companies must continually innovate and reinvent their strategies and systems.
This chapter discusses computer hardware components, including input devices like keyboards and mice, the central processing unit, memory, storage, and output devices. It classifies computers as supercomputers, mainframes, midrange computers, or microcomputers based on their processing power and size. The chapter also examines notebook/laptop computers, handheld devices, and converging technologies that combine functions in single devices.
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.
This document provides an overview of key principles and learning objectives from Chapter 2 of the textbook "Principles of Information Systems, Tenth Edition". It discusses how organizational structure, culture, and change affect information systems implementation. It also explains how businesses seek competitive advantage through lower costs, increased profits, improved service, and new systems. Finally, it defines important terms like organizational structure, culture, competitive advantage, and strategic planning.
The document summarizes key topics from a chapter on information systems in organizations, including how organizational structure, culture, and change affect IS implementation. It also discusses competitive advantage, return on investment for measuring IS value, and careers in the information systems field.
The document discusses transaction processing systems (TPS), enterprise resource planning (ERP) systems, and customer relationship management (CRM). It describes how TPS support basic business functions like order processing and accounting. ERP systems provide integrated software to manage operations across an entire organization. CRM systems help companies manage relationships with customers and improve marketing, sales, and customer service.
The document discusses principles and objectives of information and decision support systems. It defines management information systems (MIS) as integrated systems that provide the right information to the right people at the right time. Decision support systems (DSS) are used for unstructured problems and include databases, models, and interfaces. Specialized systems like group support systems (GSS) and executive support systems (ESS) build on the DSS approach to support group and executive decision making respectively.
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 the role of systems analysts and what they do. It begins by explaining that information systems have become essential for businesses to compete. Systems analysts play a special role in developing these systems by facilitating the analysis, design, and implementation of technology solutions to business problems.
The document then defines systems analysts as professionals who understand both business and technology. They study business problems and needs to determine how information systems and applications can solve issues and improve the business. Systems analysts are responsible for capturing and flowing business data to and from computer systems.
Finally, the document outlines the typical tasks and responsibilities of systems analysts. They follow a systematic approach called the systems development life cycle which includes planning, analysis, design, implementation, and
The document discusses various types of decision support systems that can help managers at different levels of an organization. It describes executive support systems that help senior managers address strategic issues through integrated business information and data visualization. It also discusses expert systems that capture human expertise in specific domains through knowledge bases and inference engines. Finally, it summarizes decision support systems as interactive tools that combine data and models to support semi-structured and unstructured decision-making.
This document discusses how information systems support various business functions like accounting, finance, engineering, supply chain management, and human resources. It explains how systems increase effectiveness and efficiency, and how tools like ERP systems integrate across business functions and organizations to improve information sharing in supply chains.
The document discusses the key aspects of information system development including the system development environment, personnel involved, types of information systems, and the system development life cycle. It notes that system development requires planning, involves users, management, and technical staff. It also outlines common system types like transaction processing systems, management information systems, expert systems, and decision support systems. Finally, it describes the main phases of system development as preliminary investigation, analysis, design, development, implementation, and maintenance.
CASE (COMPUTER AIDED SOFTWARE ENGINEERING)
CASE and its Scope
CASE support in software life cycle documentation
project management
Internal Interface
Reverse Software Engineering
Architecture of CASE environment.
This chapter discusses output design and prototyping. It defines different types of outputs like internal, external and turnaround outputs. It describes report formats like detailed, summary and exception reports. The chapter also covers output implementation methods, chart types, output design principles and guidelines. It provides examples of tabular, graphical and other types of report prototypes.
The document discusses implementing an ERP management system for a real estate company called Nirmala Consol Private Limited. Currently, the company's bill generation process takes 3 months to complete. Implementing an ERP system would integrate different departments like marketing, finance, IT, and HR. It would allow efficient data sharing and minimize the bill generation process to only 4 days. An ERP system would improve information quality, decision making, planning, cash management, inventory management, productivity and other operational functions. It would reduce the time management accountants spend on data collection and increase the time spent on analysis. In conclusion, an ERP system offers long term cost efficiencies and enhances communication and productivity across the organization.
I do not have enough context to participate meaningfully in an interactive class discussion. As an AI system, I do not have personal experiences to draw from. However, based on the material provided, here are some key considerations for mobile application development:
- Small screens require optimized UIs with large touch targets
- Limited memory/processing requires lightweight code and local storage
- Connectivity issues mean offline usage and local data caching are important
- Battery life impacts user experience, so efficiency in networking, processing etc is critical
- User requirements focus more on tasks that can be done on the go versus at a desk
- Sales processes may shift from in-store only to also include options to browse, order etc remotely via mobile for added
This document provides an overview of basic computer and information technology concepts. It discusses how computers receive input, process data, and produce output. It defines information technology as the tools used to receive, process, store, retrieve, print, and transmit information electronically. It also outlines the key components of a computer system, including hardware like the central processing unit, memory, and physical devices; and software programs and applications. Finally, it describes the main hardware components of computers and their functions.
The document discusses internal controls and their importance for businesses. It provides:
1) Three main reasons for internal controls - to achieve business goals, mitigate risks, and ensure compliance.
2) Five interrelated components of internal controls - control environment, risk assessment, control activities, information and communication, and monitoring.
3) A definition of internal control as a system using people, processes, and procedures to reasonably ensure achieving business objectives. Management is responsible for the internal control system.
1. Computers can automate controls but also enable easier circumvention of segregation of duties. Strict access controls and monitoring are needed.
2. Digital data and remote access require strong authorization procedures for transactions and sensitive tasks.
3. Recordkeeping is easier but data integrity controls like input validation, processing checks, and audit trails are critical to prevent and detect errors and fraud.
The document summarizes key aspects of the production cycle for a manufacturing business. It discusses four main activities: product design, planning and scheduling, production operations, and cost accounting. It describes important documents and decisions for each activity. The accountant's role is to design an accounting information system that provides necessary cost data to support decision-making at each stage of the production cycle.
The document provides an introduction to Manufacturing Execution Systems (MES) by Michael McClellan, the president of MES Solutions Incorporated. It describes that MES bridges the gap between planning systems like ERP and control systems on the plant floor by collecting online information to manage resources. MES provides benefits like reduced cycle times, inventory, and lead times as well as improved quality and customer service by empowering plant operations with real-time data. The core functions of MES include interfacing with planning systems, managing work orders, tracking inventory and labor, and collecting production data to optimize manufacturing execution.
The chapter discusses strategic uses of information systems and competitive advantage. It explains that strategic information systems help companies gain strategic advantages over competitors through initiatives like reducing costs, creating barriers to entry, establishing customer lock-in, innovating new products and services, and differentiating offerings. While information systems can provide early competitive benefits, these advantages erode over time as competitors catch up, so companies must continually innovate and reinvent their strategies and systems.
This chapter discusses computer hardware components, including input devices like keyboards and mice, the central processing unit, memory, storage, and output devices. It classifies computers as supercomputers, mainframes, midrange computers, or microcomputers based on their processing power and size. The chapter also examines notebook/laptop computers, handheld devices, and converging technologies that combine functions in single devices.
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.
This document provides an overview of key principles and learning objectives from Chapter 2 of the textbook "Principles of Information Systems, Tenth Edition". It discusses how organizational structure, culture, and change affect information systems implementation. It also explains how businesses seek competitive advantage through lower costs, increased profits, improved service, and new systems. Finally, it defines important terms like organizational structure, culture, competitive advantage, and strategic planning.
The document summarizes key topics from a chapter on information systems in organizations, including how organizational structure, culture, and change affect IS implementation. It also discusses competitive advantage, return on investment for measuring IS value, and careers in the information systems field.
The document discusses transaction processing systems (TPS), enterprise resource planning (ERP) systems, and customer relationship management (CRM). It describes how TPS support basic business functions like order processing and accounting. ERP systems provide integrated software to manage operations across an entire organization. CRM systems help companies manage relationships with customers and improve marketing, sales, and customer service.
The document discusses principles and objectives of information and decision support systems. It defines management information systems (MIS) as integrated systems that provide the right information to the right people at the right time. Decision support systems (DSS) are used for unstructured problems and include databases, models, and interfaces. Specialized systems like group support systems (GSS) and executive support systems (ESS) build on the DSS approach to support group and executive decision making respectively.
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 the role of systems analysts and what they do. It begins by explaining that information systems have become essential for businesses to compete. Systems analysts play a special role in developing these systems by facilitating the analysis, design, and implementation of technology solutions to business problems.
The document then defines systems analysts as professionals who understand both business and technology. They study business problems and needs to determine how information systems and applications can solve issues and improve the business. Systems analysts are responsible for capturing and flowing business data to and from computer systems.
Finally, the document outlines the typical tasks and responsibilities of systems analysts. They follow a systematic approach called the systems development life cycle which includes planning, analysis, design, implementation, and
management system development and planningmilkesa13
The document discusses systems development and the systems development lifecycle (SDLC). It describes the SDLC as having sequential phases including systems investigation, analysis, design, programming, testing, implementation, operation, and maintenance. The goal of the SDLC is to ensure high quality systems are delivered on time and budget by providing strong project management controls. Key activities in the SDLC include requirements gathering, logical and physical design, prototyping, various testing approaches, and implementation strategies like parallel and phased conversions.
The document discusses the systems development process. It describes key phases in the traditional systems development life cycle (SDLC) including investigation, analysis, design, implementation, and maintenance. Effective systems development requires defining objectives and establishing requirements. Errors found later in the SDLC are more costly to fix. Common SDLC models include traditional, prototyping, rapid application development, and end-user development. Project management tools can help plan and track systems development projects.
The document discusses the importance of aligning business processes and information technology (IT) in supply chain management. It explains that investing in both business processes and IT leads to better supply chain performance than investing in only one. The goals of supply chain IT are described as providing visibility of supply chain data, enabling analysis of that data, and facilitating collaboration with partners. Different components of supply chain management systems are outlined, including decision support systems, enterprise resource planning software, and the use of analytics and artificial intelligence.
This document discusses health information systems and the systems development life cycle (SDLC). It defines health information systems and describes their components. The SDLC includes planning, analysis, design, and implementation phases. The planning phase involves identifying projects, evaluating necessity through a technical, economic, and organizational feasibility analysis to determine if a proposed project is viable.
A presentation that contains an introduction to the whole concept of System Life Cycle. System Life Cycle - A methodology used for improving a system / process.
The document defines key terms related to systems analysis and design. It describes the principal phases of the systems development life cycle as analysis, design, development, implementation, and maintenance. Various approaches to systems development are discussed, including waterfall, spiral, agile, prototyping, V-model, and incremental models. The roles and functions of a systems analyst are outlined as coordinating projects, communicating with stakeholders, and planning and designing new systems.
PLANNING PHASE(1).pdf and designing phaseshamdiabdrhman
The document describes the systems development life cycle (SDLC), which includes planning, analysis, design, and implementation phases. It discusses the role of systems analysts in analyzing business situations, identifying opportunities for improvement, and designing information systems. Systems analysts work as part of a team with business and technical experts to develop systems that provide value to organizations.
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.
System Analysis And Design_FinalPPT_NirmishaKShehla Ghori
The document discusses conducting a system analysis and design for Retail Rockers to develop a new information processing system. It describes analyzing the needs and issues with the current system across various departments. The proposed system objectives are outlined along with data flow diagrams, entity relationship diagrams, use case diagrams and screen designs for the new application.
This document provides an overview of various information systems used in business, including business information systems, enterprise resource planning (ERP) systems, and management information systems (MIS). It describes the key components, objectives, and benefits of these systems. Business information systems provide data to help organizations manage efficiently, using hardware, software, data, procedures, and people. ERP systems integrate various business functions into a shared database. The objectives of MIS are to implement organizational structure and dynamics to better manage organizations and gain competitive advantages through information.
1. The document outlines the four phases of the system development life cycle (SDLC): planning and selection, analysis, design, and implementation and operation.
2. It describes the roles and tasks of systems analysts in analyzing the needs of an organization and its users, studying current systems, designing alternative solutions, and overseeing the implementation of new systems.
3. Key analyst responsibilities include determining requirements, structuring and comparing alternatives, producing specifications, and designing system aspects like interfaces, databases and processes.
The document discusses the roles of various analysts involved in systems analysis and design. It describes the roles of business analysts, system analysts, infrastructure analysts, change management analysts, and project managers. It explains that business analysts focus on business issues and value, system analysts focus on improving business processes through information systems, and infrastructure analysts focus on system interfaces and standards. Change management analysts coordinate user training and adoption while project managers are responsible for schedules, budgets, and benefits delivery.
Chapter 1 Introduction to Systems Analysis and Design .pptxAxmedMaxamuudYoonis
This chapter introduces systems analysis and design and the role of information technology in business. It defines the components of an information system as hardware, software, data, processes, and people. It also explains the role of systems analysts in developing information systems using various methods like structured analysis, object-oriented analysis, and agile development. The chapter emphasizes that information technology and effective information systems are crucial for business success.
Information technology (IT) is vital for organizations to manage and make decisions. IT involves acquiring, processing, maintaining and distributing high-quality information. New technologies are impacting organizations and society through growing human-machine interactions. Effective IT provides the right information to the right people to help the organization gain competitive advantages through better customer service. Information systems follow a systematic development process involving investigation, analysis, design, implementation and maintenance to collect and transform data into useful information for decision-makers.
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.
There are three common tools for documenting information systems:
1. Data flow diagrams (DFDs) visually represent the flow of data between system processes, data stores, external entities, and destinations. DFDs use four basic symbols.
2. Flowcharts depict the steps in a process and use standard symbols to represent actions, data flows, and decisions. There are different types for different purposes.
3. Business process modeling notation (BPMN) diagrams show business processes through a set of graphical symbols. Documentation is important for accountants to understand system functions and evaluate internal controls.
The document discusses the system development life cycle (SDLC) process. It describes the key phases of SDLC including planning, analysis, design, implementation, testing, deployment, and maintenance. It provides details on various techniques used during analysis such as interviews, questionnaires, documentation review, and observation. It also discusses modeling approaches for system design like data flow diagrams, entity-relationship diagrams, and decision trees/tables. Overall, the document provides a comprehensive overview of the SDLC methodology for developing and maintaining information systems.
Taking AI to the Next Level in Manufacturing.pdfssuserfac0301
Read Taking AI to the Next Level in Manufacturing to gain insights on AI adoption in the manufacturing industry, such as:
1. How quickly AI is being implemented in manufacturing.
2. Which barriers stand in the way of AI adoption.
3. How data quality and governance form the backbone of AI.
4. Organizational processes and structures that may inhibit effective AI adoption.
6. Ideas and approaches to help build your organization's AI strategy.
Ocean lotus Threat actors project by John Sitima 2024 (1).pptxSitimaJohn
Ocean Lotus cyber threat actors represent a sophisticated, persistent, and politically motivated group that poses a significant risk to organizations and individuals in the Southeast Asian region. Their continuous evolution and adaptability underscore the need for robust cybersecurity measures and international cooperation to identify and mitigate the threats posed by such advanced persistent threat groups.
Fueling AI with Great Data with Airbyte WebinarZilliz
This talk will focus on how to collect data from a variety of sources, leveraging this data for RAG and other GenAI use cases, and finally charting your course to productionalization.
Generating privacy-protected synthetic data using Secludy and MilvusZilliz
During this demo, the founders of Secludy will demonstrate how their system utilizes Milvus to store and manipulate embeddings for generating privacy-protected synthetic data. Their approach not only maintains the confidentiality of the original data but also enhances the utility and scalability of LLMs under privacy constraints. Attendees, including machine learning engineers, data scientists, and data managers, will witness first-hand how Secludy's integration with Milvus empowers organizations to harness the power of LLMs securely and efficiently.
This presentation provides valuable insights into effective cost-saving techniques on AWS. Learn how to optimize your AWS resources by rightsizing, increasing elasticity, picking the right storage class, and choosing the best pricing model. Additionally, discover essential governance mechanisms to ensure continuous cost efficiency. Whether you are new to AWS or an experienced user, this presentation provides clear and practical tips to help you reduce your cloud costs and get the most out of your budget.
Your One-Stop Shop for Python Success: Top 10 US Python Development Providersakankshawande
Simplify your search for a reliable Python development partner! This list presents the top 10 trusted US providers offering comprehensive Python development services, ensuring your project's success from conception to completion.
Dive into the realm of operating systems (OS) with Pravash Chandra Das, a seasoned Digital Forensic Analyst, as your guide. 🚀 This comprehensive presentation illuminates the core concepts, types, and evolution of OS, essential for understanding modern computing landscapes.
Beginning with the foundational definition, Das clarifies the pivotal role of OS as system software orchestrating hardware resources, software applications, and user interactions. Through succinct descriptions, he delineates the diverse types of OS, from single-user, single-task environments like early MS-DOS iterations, to multi-user, multi-tasking systems exemplified by modern Linux distributions.
Crucial components like the kernel and shell are dissected, highlighting their indispensable functions in resource management and user interface interaction. Das elucidates how the kernel acts as the central nervous system, orchestrating process scheduling, memory allocation, and device management. Meanwhile, the shell serves as the gateway for user commands, bridging the gap between human input and machine execution. 💻
The narrative then shifts to a captivating exploration of prominent desktop OSs, Windows, macOS, and Linux. Windows, with its globally ubiquitous presence and user-friendly interface, emerges as a cornerstone in personal computing history. macOS, lauded for its sleek design and seamless integration with Apple's ecosystem, stands as a beacon of stability and creativity. Linux, an open-source marvel, offers unparalleled flexibility and security, revolutionizing the computing landscape. 🖥️
Moving to the realm of mobile devices, Das unravels the dominance of Android and iOS. Android's open-source ethos fosters a vibrant ecosystem of customization and innovation, while iOS boasts a seamless user experience and robust security infrastructure. Meanwhile, discontinued platforms like Symbian and Palm OS evoke nostalgia for their pioneering roles in the smartphone revolution.
The journey concludes with a reflection on the ever-evolving landscape of OS, underscored by the emergence of real-time operating systems (RTOS) and the persistent quest for innovation and efficiency. As technology continues to shape our world, understanding the foundations and evolution of operating systems remains paramount. Join Pravash Chandra Das on this illuminating journey through the heart of computing. 🌟
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdfMalak Abu Hammad
Discover how MongoDB Atlas and vector search technology can revolutionize your application's search capabilities. This comprehensive presentation covers:
* What is Vector Search?
* Importance and benefits of vector search
* Practical use cases across various industries
* Step-by-step implementation guide
* Live demos with code snippets
* Enhancing LLM capabilities with vector search
* Best practices and optimization strategies
Perfect for developers, AI enthusiasts, and tech leaders. Learn how to leverage MongoDB Atlas to deliver highly relevant, context-aware search results, transforming your data retrieval process. Stay ahead in tech innovation and maximize the potential of your applications.
#MongoDB #VectorSearch #AI #SemanticSearch #TechInnovation #DataScience #LLM #MachineLearning #SearchTechnology
Building Production Ready Search Pipelines with Spark and MilvusZilliz
Spark is the widely used ETL tool for processing, indexing and ingesting data to serving stack for search. Milvus is the production-ready open-source vector database. In this talk we will show how to use Spark to process unstructured data to extract vector representations, and push the vectors to Milvus vector database for search serving.
Salesforce Integration for Bonterra Impact Management (fka Social Solutions A...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on integration of Salesforce with Bonterra Impact Management.
Interested in deploying an integration with Salesforce for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
Ivanti’s Patch Tuesday breakdown goes beyond patching your applications and brings you the intelligence and guidance needed to prioritize where to focus your attention first. Catch early analysis on our Ivanti blog, then join industry expert Chris Goettl for the Patch Tuesday Webinar Event. There we’ll do a deep dive into each of the bulletins and give guidance on the risks associated with the newly-identified vulnerabilities.
How to Interpret Trends in the Kalyan Rajdhani Mix Chart.pdfChart Kalyan
A Mix Chart displays historical data of numbers in a graphical or tabular form. The Kalyan Rajdhani Mix Chart specifically shows the results of a sequence of numbers over different periods.
Digital Marketing Trends in 2024 | Guide for Staying AheadWask
https://www.wask.co/ebooks/digital-marketing-trends-in-2024
Feeling lost in the digital marketing whirlwind of 2024? Technology is changing, consumer habits are evolving, and staying ahead of the curve feels like a never-ending pursuit. This e-book is your compass. Dive into actionable insights to handle the complexities of modern marketing. From hyper-personalization to the power of user-generated content, learn how to build long-term relationships with your audience and unlock the secrets to success in the ever-shifting digital landscape.
Nunit vs XUnit vs MSTest Differences Between These Unit Testing Frameworks.pdfflufftailshop
When it comes to unit testing in the .NET ecosystem, developers have a wide range of options available. Among the most popular choices are NUnit, XUnit, and MSTest. These unit testing frameworks provide essential tools and features to help ensure the quality and reliability of code. However, understanding the differences between these frameworks is crucial for selecting the most suitable one for your projects.
Monitoring and Managing Anomaly Detection on OpenShift.pdfTosin Akinosho
Monitoring and Managing Anomaly Detection on OpenShift
Overview
Dive into the world of anomaly detection on edge devices with our comprehensive hands-on tutorial. This SlideShare presentation will guide you through the entire process, from data collection and model training to edge deployment and real-time monitoring. Perfect for those looking to implement robust anomaly detection systems on resource-constrained IoT/edge devices.
Key Topics Covered
1. Introduction to Anomaly Detection
- Understand the fundamentals of anomaly detection and its importance in identifying unusual behavior or failures in systems.
2. Understanding Edge (IoT)
- Learn about edge computing and IoT, and how they enable real-time data processing and decision-making at the source.
3. What is ArgoCD?
- Discover ArgoCD, a declarative, GitOps continuous delivery tool for Kubernetes, and its role in deploying applications on edge devices.
4. Deployment Using ArgoCD for Edge Devices
- Step-by-step guide on deploying anomaly detection models on edge devices using ArgoCD.
5. Introduction to Apache Kafka and S3
- Explore Apache Kafka for real-time data streaming and Amazon S3 for scalable storage solutions.
6. Viewing Kafka Messages in the Data Lake
- Learn how to view and analyze Kafka messages stored in a data lake for better insights.
7. What is Prometheus?
- Get to know Prometheus, an open-source monitoring and alerting toolkit, and its application in monitoring edge devices.
8. Monitoring Application Metrics with Prometheus
- Detailed instructions on setting up Prometheus to monitor the performance and health of your anomaly detection system.
9. What is Camel K?
- Introduction to Camel K, a lightweight integration framework built on Apache Camel, designed for Kubernetes.
10. Configuring Camel K Integrations for Data Pipelines
- Learn how to configure Camel K for seamless data pipeline integrations in your anomaly detection workflow.
11. What is a Jupyter Notebook?
- Overview of Jupyter Notebooks, an open-source web application for creating and sharing documents with live code, equations, visualizations, and narrative text.
12. Jupyter Notebooks with Code Examples
- Hands-on examples and code snippets in Jupyter Notebooks to help you implement and test anomaly detection models.
1. SYSTEM FLOW CHART
Case
CASE – Sales Order Processing
In a company, there are five departments present include :
Sales order processing
Credit
Finished goods
Shipping
Billing
Accounts Receivable
Sales Order Dept
Two copies of the Purchase order is received by the Sales order department from the Customer.
Credit
It is forwarded to the Credit Department for credit checking.
The PO after it is checked and okayed becomes Approved PO and is sent back to the Sales order Dept.
Sales Order Dept
Five copies of Sales Order is prepared.
The first copy of the SO is sent to the customer as acknowledgment
The fifth copy of the SO and the first copy of the PO is filed in the Sales order Dept in numerical order (by SO)
Finished Goods
The second and third copy of the SO is sent to the Finished Goods to check inventory
After inventory check is over and okayed the SO becomes Approved SO
The second copy of the ASO is posted in the Inventory Ledger and is then filed in the Finished Goods dept
Shipping Dept
The fourth copy of SO is merged with the ASO in the Shipping Dept
Three copies of Bill of Lading is prepared
The third copy of B/L is sent along with the goods
The second copy of B/L and the third copy of ASO is filed in numerical order in the Shipping Dept
Billing Dept
2. The second copy of the APO is sent to the Billing Dept
The first copy of the B/L and the fourth copy of ASO is merged with the APO in the Billing Dept
Three copies of Sales Invoice is prepared in the Billing Dept.
The information is posted in the Sales Journal
The first copy of SI is sent to the Customer as acknowledgement
The third copy of SI, first copy of B/L, fourth copy of ASO, second copy of APO is filed in numerical order in the Billing
dept
A/c Receivable Dept
The second copy of SI is sent to the A/c Receivables dept and posted in the A/R Ledger
The SI is then filed in the A/R dept in numerical order
3.
4. BA 9125 MANAGEMENT INFORMATION SYSTEM
INTRODUCTION
MANAGEMENT INFORMATION SYSTEM
A MIS is
an user integrated user-machine system
to providing information
to support Operations, Management Analysis and Decision Making functions in an organisation
The SYSTEM utilizes
Computer hardware and software
Manual procedures
Models for Analysis, Planning, Control and Decision Making
And a Database
COMPUTER BASED
INFORMATION SYSTEMS (CBIS)
Office Automation Systems (OAS)
Transaction Processing Systems (TPS)
Management Information Systems(MIS)
Decision Support System ( DSS )
Expert System ( ES )
Executive Information System ( EIS ) /
Executive Support System ( ESS )
Knowledge Management (KM )
5. Inputs – Processes - Outputs
Evolution of Information System
Evolutionary view
Evolution of Information System Contd
6. Contingency view
THREE LEVELS OF MANAGEMENT
STRATEGIC - BEYOND ONE YEAR
Company Diversification
New Product introduction
Mergers
Acquisitions
Fund flow, Capital Management
TACTICAL - LESS THAN ONE YEAR
Plant Layout
Budgeting
Cash flow management
Working capital
Labour relations
THREE LEVELS OF MANAGEMENT Contd
OPERATIONAL - DAY TO DAY DECISIONS
Variance Analysis
Controls
Target achievements
Inventory status
Cash on hand
7. Levels of Management
Information Requirements
3 Strategies using which users define Information Scharer (1981)
KITCHEN SINK STRATEGY
Users throws everything into the requirement definition – overstatement of needs such as over
abundance of reports, reflects lack of experience
SMOKE SCREEN STRATEGY
Sets up a smoke screen by requesting for several system features of which 1 or 2 is needed
SAME THING
Indicates users’ laziness, lack of knowledge, analyst little chance of succeeding, only user can fully
understand and discover the real needs and problems
• What is a System ?
• CHARACTERISTICS OF A SYSTEM
• SYSTEMS TRANSFORMS INPUT TO OUTPUT
• SYSTEMS ARE INTERDISCIPLINARY
• SYSTEMS ARE HOLISTIC
8. • SYSTEMS ARE DIFFERENTIATED
• SYSTEMS ARE SYNERGISTIC
• SYSTEMS ARE HIERARCHICAL
• SYSTEMS MUST BE REGULATED
• SYSTEMS MUST BE GOAL ORIENTED
• IT is inextricably intertwined
with business
• Technology is an expected way to conduct business
• Organizations are looking to apply technology to streamline existing processes
• Organizations are also looking to create new opportunities which are a source of competitive advantage
• McFarlan’s & McKenney Strategic Grid (1983)
•
• Support - uses IT primarily for support activities, such as payroll processing
• Turnaround - not heavily dependent upon IT at present, but may look to IT to improve competitive posture in
the market
• Factory - may use IT heavily for day-to-day operations, but IT not viewed as a competitive advantage
• Strategic - dependent now and in the future on IT for the performance of day-to-day operations and for
competitive advantage
9. • Systems Analysis and Design
• Systems Analysis and System Design
• System Analysis
• is the study of a current business system and its problem
10. • the definition of business needs and requirements
• and the evaluation of alternative solutions
• Systems Analysis and System Design
• System Design
• is the general and detailed specification of a computer based solution that was selected during systems
analysis
• Design specifications are typically sent to computer programmers for systems implementation
• System Analysis
• Analysis is the opposite of Synthesis
• A synthetic process builds the whole out of parts
whereas
• An analytic process identifies the parts of the whole the components of a system
• Where is creativity required more?
• Is it during systems analysis or during systems design
• Business People & Computer Programmers
• Business People
• Define the applications and problems to be solved by the computer
• Computer Programmers
• and technicians apply the technology to well defined applications and problems
Presently with IT explosion
Business Users do not fully understand the capabilities and limitations of modern computer technology
The potential of computers is not fully or even adequately realised in most business
• Business People & Computer Programmers
Computer Professionals – it is becoming increasingly difficult to keep up with new technological developments.
They do not understand the business application they are trying to computerize.
Business Users GAP Computer Professionals
• System Analyst
• The systems analyst is a key person analyzing the business, identifying opportunities for improvement, and
designing information systems to implement these ideas.
11. • It is important to understand and develop through practice the skills needed to successfully design and
implement new information systems.
• System Analyst
• studies the problems and needs of an organisation
• to determine how people, methods and computer technology can best accomplish improvements for the
business
• when computer technology is used the analyst is responsible for the efficient capture of data from its business
source, the flow of that data to the computer, the processing and storage of that data by the computer and the
flow of useful and timely information back to business users
• “How you gather, manage, and use information will determine whether you win or lose”
- Bill Gates
• People with whom the Analyst must work with
As facilitators of system development the analyst must work with many types of people, both technical and non
technical. The joint efforts of these professionals as coordinated by the analysts will result in successful computer
applications
• Key Ideas
• Many failed systems were abandoned because analysts tried to build wonderful systems without understanding
the organization.
• The primarily goal is to create value for the organization.
• Synonyms for Systems Analyst
• Systems Designer
• Systems Engineer
• Systems Consultant
• Management Consultant
12. • Operations Analyst
• Information Analyst
• Data Analyst
• Business Analyst
• Levels of an Analyst
• Lead Analyst
• Senior Analyst
• Analyst
• Junior Analyst
• Analyst Trainee
• Characteristics of an Analyst
• An IT person
• Knowledge of Software
• Knowledge of Hardware
• Knowledge of Technology
• Knowledge of Processes and Procedures
• An HR person
• Good communicator
• Good in Public relations
• Positive attitude, Assertive personality with problem solving and conflict resolution skills
• THE SYSTEMS DEVELOPMENT LIFE CYCLE
•
• Major Attributes of the Life Cycle
• The project --
• Moves systematically through phases where each phase has a standard set of outputs
• Produces project deliverables
• Uses deliverables in implementation
• Results in actual information system
13. • Uses gradual refinement
• Project Phases
• Planning (Why build the system? How should the team go about building it?)
• Analysis (Who uses system, what will it do, where and when will the system be used?)
• Design (How will the system work?)
• Implementation (System delivery)
• Planning
• Identifying business value
• Analyze feasibility
• Develop work plan
• Staff the project
• Control and direct project
• Analysis
• Analysis strategy
• Gathering business requirements
• Requirements definition use cases
• Process modeling
• Data modeling
• Design
• Design selection
• Architecture design
• Interface design
• Data storage design
• Program design
• Implementation
• Construction
• Program building
• Program and system testing
14. • Installation
• Conversion strategy
• Training plan
• Support plan
SYSTEM DEVELOPMENT LIFE CYCLE
• Processes and Deliverables
• Systems Development Life Cycle
• Project Planning
• System Analysis
• System Design
• Construction
15. • Integration and Testing
• Installation
• Operation & Maintenance
• SDLC Phases
• Project Planning
• Put project in context
• Small part of a much larger system?
• New system or modify old?
• System Analysis
• Define user requirements
• Analyze tasks
• Develop specifications
• System Design - Define the system to be built
• Logical design
• Physical design
• SDLC Phases (continued)
• Construction
• Write (or buy) the code
• Integration and Testing
• Unit testing, system testing, acceptance testing
• Installation
• Testing, training, conversion
• Operations & Maintenance
• Put into production
• Fix bugs, add facilities
• SYSTEM DEVELOPMENT METHODOLOGIES
•
• What Is a Methodology?
16. • A formalized approach to implementing the SDLC
• A series of steps and deliverables
• Methodology Categories
• Process-Centered
• Data-Centered
• Structured Design
• Rapid Application Development
• Agile Development
• Object-Oriented
• Waterfall Development Methodology
• Consists of a set of phases that a project progresses through in a sequential order.
• Each phase must be completed before the project can progress to the next phase.
• At the end of each phase is some form of gateway, usually a formal review where that decision is made.
• There is no overlap between phases.
• Straight forward, simple to understand and use.
• Deliverables are frozen at the end of each phase and server as the baseline for the following phases.
• You do not see the software until the end of the project (big bang software development).
• Changes are not supposed to happen or are limited or are tightly controlled.
• Strengths of the Waterfall Model
We can see that the waterfall model has many strengths when applied to a project for which it is well suited.
Some of these strengths are:
17. • The model is well known by nonsoftware customers and end-users (it is often used by other organizations to
track nonsoftware projects)
• It tackles complexity in an orderly way, working well for projects that are well understood but still complex.
• It is easy to understand, with a simple goal – to complete required activities.
• It is easy to use as development proceeds one phase after another.
• It provides structure to a technically weak or inexperienced staff.
• It provides requirements stability.
• It provides a template into which methods for analysis, ,design, code, test and support can be placed.
• Strengths of the Waterfall Model contd
• It works well when quality requirements dominate cost and schedule requirements.
• It allows for tight control by project management.
• When correctly applied, defects may be found early, when they are relatively inexpensive to fix.
• It is easy for the project manager to plan and staff.
• It allows staff who have completed their phase activities to be freed up for other projects.
• It defines quality control procedures. Each deliverable is reviewed as it is completed. The team uses procedure
to determine the quality of the system.
• Its milestones are well understood.
• It is easy to track the progress of the project using a timeline or Gantt Chart – the completion of each phased is
used as a milestone.
• Weaknesses of the Waterfall model
We can also note weakness of the model when it is applied to a project for which it is not well suited:
• It has an inherently linear sequential nature – any attempt to go back two or more phases to correct a problem
or deficiency results in major increases in cost and schedule.
• It does not handle the reality of iterations among phases that are so common in software development because
it is modeled after a conventional hardware engineering cycle.
• It doesn’t reflect the problem – solving nature of software development. Phases are tied rigidly to activities, not
how people or teams really work.
• It can present a false impression of status and progress – “35 percent done” is a meaningless metric for the
project manager.
18. • Integration happens in one big bang at the end. With a single pass through the process, integration problems
usually surface too late. Previously undetected errors or design deficiencies will emerge, adding risk with little
time to recover.
• There is insufficient opportunity for a customer preview the system until very late in the life cycle. There are no
tangible interim deliverables for the customer; user responses cannot be fed back to developers. Because a
completed product is not available until the end of the process, the user is involved only in the beginning, while
gathering requirements and at the end, during acceptance testing.
• Users can’t see quality until the end. They can’t appreciate quality if the finished product can’t be seen.
• It isn’t possible for the user to get used to the system gradually. All training must occur at the end of the life
cycle, when the software is running.
• Weaknesses of the Waterfall model
• It is possible for a project to go through the disciplined waterfall process, meet written requirements, but still
not be operational
• Each phase is a prerequisite for succeeding activities, making this method a risky choice for unprecedented
systems because it inhabits flexibility.
• Deliverables are created for each phase and are considered frozen – that is, they should not be changed later in
the life cycle of the product. If the deliverable of a phase changes, which often happens, the project will suffer
schedule problems because the model did not accommodate, nor was the plan based on managing a change
later in the cycle.
• All requirements must be known at the beginning of the life cycle, yet customers can rarely state all explicit
requirements at that time. The model is not equipped to handle dynamic changes in requirements over the life
cycle, as deliverables are “frozen.” The model can be very costly to use if requirements are not well known or
are dynamically changing during the course of the life cycle.
• Tight management and control is needed because there is no provision for revising the requirements.
• It is document – driven and the amount of documentation can be excessive.
• The entire software product is being worked on at one time. There is no way to partition the system for delivery
of pieces of the system. Budget problems can occur because of commitments to develop an entire system at
one time. Large sums of money are allocated, with little flexibility to reallocate the funds without destroying
the project in the process.
• There is no way to account for behind- the – scenes rework and iterations.
• Pros and Cons of the Waterfall Methodology
19. • Parallel Development Methodology
• Pros and Cons of Parallel Development Methodology
• Rapid Application Development
• Incorporate special techniques and tools:
• CASE tools
20. • JAD sessions
• Fourth generation/visualization programming languages
• Code generators
• Three RAD Categories
• Phased development
• A series of versions developed sequentially
• Prototyping
• System prototyping
• Throw-away prototyping
• Design prototyping
• Phased Development Methodology
• Pros and Cons of Phased Development Methodology
21. • How Prototyping Works
• Used to develop a quick implementation of the software prior to or during the software requirements phase.
• The customer uses the prototype and provides feedback to the software developers as to its strengths and
weaknesses.
• This feedback is used to refine or change the prototype to meet the real needs of the customer.
• Can either be evolutionary or throw away.
• Pros and Cons of Prototyping Methodology
• Prototyping Guidelines
• Throwaway Prototyping
22. • Pros and Cons of Throwaway Prototyping Methodology
• V-SHAPED MODEL
• The following list contains a brief description of each phase of the V-Shaped model, from project and
requirements planning through acceptance testing.
• Projects and requirements planning - Determines the system requirements and how the resources of the
organization will be allocated to meet them. (Where appropriate, this phase allocates functions to hardware
and software).
• Projects and requirements planning - Determines the system requirements and how the resources of the
organization will be allocated to meet them. (Where appropriate, this phase allocates functions to hardware
and software).
• Product requirements and specification analysis – Includes analysis of the software problem at hand and
concludes with a complete specification of the expected external behavior of the software system to be built.
• Architecture or high-level design – Defines how the software functions are to implement the design.
• V-SHAPED MODEL
• Detailed design – Defines and documents algorithms for each component that was defined during the
architecture phase. These algorithms will be translated into code.
23. • Coding – Transforms the algorithms defined during the detailed design phase into software..
• Unit testing – Checks each coded module for errors.
• Integration and testing – Interconnects the sets of previously unit-tested modules to ensure that the sets
behave as well as the independently tested modules did during the unit-testing phase.
• System and acceptance testing – Checks whether the entire software system (fully integrated) embedded in its
actual hardware environment behaves according to the software requirements specification.
• Production, operation and maintenance – Puts software into production and provides for enhancement and
corrections.
• Acceptance testing (not shown) – Allows the user to test the functionality of the system against the original
requirements. After final testing, the software and its surrounding hardware become operational.
Maintenance of the system follows.
• V-SHAPED MODEL
• Similar to waterfall except it emphasizes the importance of considering the testing activities up front instead of
later in the life cycle.
• Strengths of the V-Shaped Model
When applied to a project for which it is well suited, the V-shaped model offers several strengths;
• The model emphasizes planning for verification and validation of the product in the early stages of product
development. Emphasis is placed on testing by matching the test phase or process with the development
process . The unit testing phase validates detailed design. The integration and testing phases validate
architectural or high - level design. The system testing phase validates the product requirements and
specification phase.
• The model encourages verification and validation of all internal and external deliverables, not just the software
product.
24. • The V-Shaped model encourages definition of the requirements before designing the system, and it encourages
designing the software before building the components.
• It defines the products that the development process should generate; each deliverable must be testable.
• It enables project management to track progress accurately; the progress of the project follows a timeline, and
the completion of each phase is milestone.
• It is easy to use (When applied to a project for which it is suited).
• Weakness of the V-Shaped Model
When applied to a project for which it is not well suited, the weaknesses of the V-shaped model are evident:
• It does not easily handle concurrent events.
• It does not handle iterations of phases.
• The model is not equipped to handle dynamic changes in requirements throughout the life cycle.
• The requirements are tested too late in the cycle to make changes without affecting the schedule for the
project.
• The model does not contain risk analysis activities.
• Incremental Development
• Allows a project to construct the software in incremental stages where each stage adds additional functionality.
• Each stage consists of design, code and unit test, integration test and delivery.
• Allows you to put functional software into the hands of the customer much earlier than either the waterfall or V-
shaped model.
• You can plan the stages in such a way that you determine what functionality you do first.
• i.e. you may choose to deliver the most important functionality to the customer first.
• Provides tangible measures of progress.
• Requires careful planning at both the project management level and the technical level
• Iterative Development
25. • SPIRAL
• Developed by Barry Boehm.
• A risk-oriented software life cycle.
• Each spiral addresses major risks that have been identified.
• After all the risks have been addressed, the spiral model terminates as a waterfall software life cycle
• SPIRAL
26. • Spiral (Iterative) Model
• Agile Development: Extreme Programming
27. • Pros and Cons of Agile Methodologies
• Criteria for Selecting the Appropriate Methodology
• Clear user requirements
• Familiarity with technology
• Complexity of system
• Reliability of system
• Time schedule
• Schedule visibility
SYSTEMS ANALYSIS & SYSTEMS DESIGN TOOLS
SAD Tools
1. Process flow chart
2. System flow chart
3. Data flow diagram
28. 4. Document flow diagram
5. Structured English
6. Decision tree
7. Decision table
8. Warnier Orr Diagram
9. Hierarchical Input Process Output
10. Entity Relationship
SYSTEM FLOW CHART SYMBOLS
BASIC SYMBOLS
SPECIALIZED SYMBOLS
SYSTEM – INPUT/OUTPUT – EQUIPMENT SYMBOLS
29. CASE
In a company, there are five departments present:
Sales order processing
Credit
Finished goods
Shipping
Billing
Accounts Receivable
The processes involved include ….
Sales order processing Credit Finished goods Shipping Billing A/cs Receivable
CASE
In a company, there are five departments present include :
Sales order processing
Credit
Finished goods
Shipping
Billing
Accounts Receivable
Two copies of the Purchase order is received by the Sales order department from the Customer. It is forwarded to the
Credit Department for credit checking.
30. Two copies of the Purchase order is received by the Sales order department from the Customer. It is forwarded to the
Credit Department for credit checking.
CASE
In a company, there are five departments present include :
Sales order processing
Credit
Finished goods
Shipping
Billing
Accounts Receivable
Two copies of the Purchase order is received by the Sales order department from the Customer. It is forwarded to the
Credit Department for credit checking.
The PO after it is checked and okayed becomes Approved PO and is sent back to the Sales order Dept. Five copies of
Sales Order is prepared.
31. CASE … cont’d
The first copy of the SO is sent to the customer as acknowledgment
The fifth copy of the SO and the first copy of the PO is filed in the Sales order Dept in numerical order (by SO)
The first copy
of the SO is sent to the customer as acknowledgment
32. The second and
third copy of the SO is sent to the Finished Goods to check inventory
The second of
the ASO is posted in the Inventory Ledger and is then filed in the Finished Goods dept
SYSTEM FLOW CHART
Case
CASE – Sales Order Processing
In a company, there are five departments present include :
Sales order processing
Credit
33. Finished goods
Shipping
Billing
Accounts Receivable
Sales Order Dept
Two copies of the Purchase order is received by the Sales order department from the Customer.
Credit
It is forwarded to the Credit Department for credit checking.
The PO after it is checked and okayed becomes Approved PO and is sent back to the Sales order Dept.
Sales Order Dept
Five copies of Sales Order is prepared.
The first copy of the SO is sent to the customer as acknowledgment
The fifth copy of the SO and the first copy of the PO is filed in the Sales order Dept in numerical order (by SO)
Finished Goods
The second and third copy of the SO is sent to the Finished Goods to check inventory
After inventory check is over and okayed the SO becomes Approved SO
The second copy of the ASO is posted in the Inventory Ledger and is then filed in the Finished Goods dept
Shipping Dept
The fourth copy of SO is merged with the ASO in the Shipping Dept
Three copies of Bill of Lading is prepared
The third copy of B/L is sent along with the goods
The second copy of B/L and the third copy of ASO is filed in numerical order in the Shipping Dept
Billing Dept
The second copy of the APO is sent to the Billing Dept
The first copy of the B/L and the fourth copy of ASO is merged with the APO in the Billing Dept
Three copies of Sales Invoice is prepared in the Billing Dept.
The information is posted in the Sales Journal
The first copy of SI is sent to the Customer as acknowledgement
34. The third copy of SI, first copy of B/L, fourth copy of ASO, second copy of APO is filed in numerical order in the Billing
dept
A/c Receivable Dept
The second copy of SI is sent to the A/c Receivables dept and posted in the A/R Ledger
The SI is then filed in the A/R dept in numerical order
36. Symbols
Source/ Destination
Process
Data Store
Flow line
RULES OF THUMB
1. The DFD to be drawn from left to right, top to bottom
2. All processes to be numbered
3. The DFD will start with a Context diagram, then First level, Second level etc
4. The flow should match even when exploded
5. The source and destination when it is same should be indicated with a slash
6. The Source / Destination, Data store should be mentioned in CAPS, while the Process and Data line should be
mentioned in first letter Caps
7. Data should not go directly from
Source to Destination
Source/ Destination to File
42. INFORMATION SYSTEMS
FUNCTIONAL INFORMATION SYSTEM
MARKETING
HUMAN RESOURCE
FINANCIAL
PRODUCTION / OPERATIONAL
Why MKIS ?
MKIS provides strategies and solution with respect to product, price, promotion and place.
1. What is to produce?
2. What price is to be charged for a product?
3. How to promote your products?
4. Where to sale your products?
MKIS helps marketer to draw product strategy, pricing strategy, promotion strategy and geographical marketing
strategy under different circumstances.
MARKETING INFORMATION SYSTEM
MARKET RESEARCH
SALES FORECASTING
ADVERTISING AND PROMOTION
SALES ORDER PROCESSING
SALES MANAGEMENT
PRODUCT MANAGEMENT
MARKETING MANAGEMENT
Marketing Information System
43. Developing Marketing Information
Internal data is gathered via customer databases, financial records, and operations reports.
Advantages include quick and easy access to information.
Disadvantages stem from the incompleteness or inappropriateness of data to a particular situation.
Developing Marketing Information
Marketing intelligence is the systematic collection and analysis of publicly available information about competitors
and trends in the marketing environment.
Competitive intelligence gathering activities have grown dramatically.
Many sources of competitive information exist.
Developing Marketing Information
Marketing research is the systematic design, collection, analysis, and reporting of data relevant to a specific
marketing situation facing an organization.
Marketing models
For interpreting information in order to give direction to decision models are used. These models may be
computerised or may not. Some of them are
· Time series sales modes
· Linear programming
· Elasticity models (price, incomes, demand, supply,etc.)
44. · Regression and correlation models
· Analysis of Variance (ANOVA) models
· Sensitivity analysis
· Discounted cash flow
· Spreadsheet 'what if models
HUMAN RESOURCE MANAGEMENT
PERSONNEL RECORD KEEPING
LABOUR ANALYSIS
EMPLOYEE SKILLS INVENTORY
COMPENSATION ANALYSIS
TRAINING AND DEVELOPMENT ANALYSIS
PERSONNEL REQUIREMENTS
FORECASTING
FINANCE
CAPITAL MANAGEMENT
CASH MANAGEMENT
CREDIT MANAGEMENT
PORTFOLIO MANAGEMENT
FINANCIAL FORECASTING
FINANCIAL REQUIREMENTS ANALYSIS
FINANCIAL PERFORMANCE ANALYSIS
PRODUCTIONS / OPERATIONS
COMPUTER AIDED MANUFACTURING
MATERIAL REQUIRMENTS PLANNING
INVENTORY CONTROL
PURCHASING AND RECEIVING
PROCESS CONTROL
COMPUTER AIDED ENGINEERING
ROBOTICS
ACCOUNTING
45. BILLING AND ACCOUNTS RECEIVABLE
PAYROLL
ACCOUNTS PAYABLE
GENERAL LEDGER
FIXED ASSET ACCOUNTING
COST ACCOUNTING
TAX ACCOUNTING
BUDGETING
AUDITING
MARKETING INFORMATION SYSTEM
FINANCIAL INFORMATION SYSTEM
58. EXPERT SYSTEM
KNOWLEDGE ENGINEERING
Definition : Transforming knowledge from an expert to a computer program.
THE BAD NEWS
HUMAN EXPERTISE
Creative
Adaptive
Sensory Experience
Broad Focus
59. Commonsense knowledge
ARTIFICIAL EXPERTISE
Unspired
Needs to be told
Symbiotic input
Narrow focus
Technical knowledge
THE GOOD NEWS
HUMAN EXPERTISE
Perishable
Difficult to transfer
Difficult to document
Unpredictable
Expensive
ARTIFICIAL EXPERTISE
Permanent
Easy to transfer
Easy to document
Consistent
Affordable
EXPERT SYSTEM CAN
INTERPRET – interpretation of measurement data
FORECAST – forecasting of possible consequences of given situations
DIAGNOSE – Diagnosis of incorrect function
PLAN – Planning of complex sequence
MONITOR – Monitoring operations
REPAIR – Triggering of complex repair sequence
INSTRUCT – Intelligent training system
60. AN EXPERT is …
An Expert is a person who, because of training and experience, is able to do things the rest of us cannot, experts are
not only proficient but also smooth and efficient in the actions they take
PLAYERS OF EXPERT SYSTEM
COMPONENTS OF EXPERT SYSTEM
KNOWLEDGE REPRESENTATION
61. 1. Rule based
2. Frame based
3. Semantic Net based
RULE BASED
FACTS
Pertaining to the problem area
Explicitly classifying objects OR specify relationship between them
RULES
For manipulating the facts
IF .. THEN .. Type
RULE BASED examples
FACTS
A Car requires an Engine
An Engine generates Mechanical Power
Zen is a Maruti
Maruti is a Car
RULES
If ANTECENDENT then CONSEQUENT
If SITUATION then ACTION
INFERENCE ENGINE
FORWARD CHAINING
Start with set of Facts and look for Rules in the Knowledge base to match the Data
BACKWARD CHAINING
Start with the Goal to be proved, and try to establish the Facts needed to prove it
PROGRAMMING LANGUAGE
LISP, PROLOG,
62. ZETALISP, SMALLTALK-80
SOFTWARE PACKAGES : SHELLS
EXTRAN 7
RULE MASTER
SAVOIR
FORWARD CHAINING
Does ZEN have an ENGINE ?
BACKWARD CHAINING
Does ZEN have an ENGINE ?