Information Business Systems

Information Business Systems

• Systems collect, process, store, and distribute information.
• Supports business operations and decision-making.
• Systems range from simple databases to complex ERP systems.
• Crucial for managing data, automating processes, and improving business efficiency.
• Components include hardware, software, data, people, and processes.
• Hardware is physical components like servers, workstations, and network devices.
• Software includes system software like OS and DBMS, and application software.
• Data is structured and unstructured information the system uses.
• People are users, developers, analysts, and managers.
• Processes are defined procedures and workflows the system supports.
• Types include TPS, MIS, DSS, and EIS.
• TPS record and process daily transactions.
• MIS provide summarized reports.
• DSS aid in decision-making with analytical tools.
• EIS provide high-level strategic information for executives.
• Key functions are data management, process automation, reporting, and collaboration.
• Challenges are data security, system integration, scalability, and user adoption.

Cloud Computing

• Delivers computing services over the internet.
• Includes servers, storage, databases, networking, software, analytics, and intelligence.
• Cloud computing offers on-demand access to computing resources on a pay-as-you-go basis.
• Cloud models: IaaS, PaaS, and SaaS.
• IaaS provides virtualized computing resources over the internet.
• PaaS provides a platform to develop, run, and manage applications without managing infrastructure.
• SaaS delivers software applications over the internet on demand, typically on a subscription basis.
• Cloud deployment models: public, private, hybrid, and community cloud.
• Public cloud infrastructures are owned and operated by a third-party provider, offering resources to the general public.
• Private cloud infrastructures are used exclusively by a single organization.
• Hybrid cloud combines public and private clouds, allowing data and applications to be shared between them.
• Community cloud infrastructures are shared by organizations with similar interests.
• Benefits include cost savings, scalability, flexibility, disaster recovery, and automatic updates.
• Challenges include security, compliance, vendor lock-in, and internet dependency.
• Key technologies: Virtualization, containerization, and SOA.
• Virtualization allows multiple virtual machines to run on a single physical server.
• Containerization packages software and dependencies into isolated containers.
• SOA designs software as a collection of loosely coupled services.

Business Process Modeling

• Represents processes of an enterprise to analyze or improve the current process.
• Involves creating a visual representation to understand, analyze, and improve a business process.
• Common modeling languages are BPMN, UML, and EPC.
• BPMN is a graphical notation for specifying business processes in a BPD.
• UML is a standardized general-purpose modeling language in software engineering.
• EPC is a flowchart-based business process modeling technique.
• Key elements are activities, events, gateways, and sequence flows.
• Activities represent work performed in the process.
• Events represent triggers or outcomes in the process.
• Gateways control the flow of the process based on conditions.
• Sequence flows define the order of activities.
• Tools include Microsoft Visio, Bizagi Modeler, and Signavio Process Manager.
• Benefits are improved understanding, process optimization, better communication, and compliance enforcement.
• Challenges include complexity, resistance to change, and maintaining accuracy.
• Process analysis techniques are value stream mapping, root cause analysis, and process simulation.
• Value stream mapping analyzes the flow of materials and information required to bring a product or service to a customer.
• Root cause analysis identifies the fundamental causes of a problem.
• Process simulation models the behavior of a process to identify bottlenecks and improve performance.

System Architecture

• A conceptual model that defines the structure, behavior, and views of a system.
• Encompasses the components, relationships, and principles governing design and evolution.
• Provides a blueprint for the system development and deployment.
• Types are monolithic, client-server, distributed, and microservices.
• Monolithic architecture combines all components into a single deployable unit.
• Client-server architecture distributes processing between clients and servers.
• Distributed architecture spreads components across multiple machines.
• Microservices architecture structures an application as a collection of small, autonomous services, modeled around a business domain.
• Key architectural patterns include MVC, layered architecture, and event-driven architecture.
• MVC separates an application into three interconnected parts: model, view, and controller.
• Layered architecture organizes components into layers, each providing a specific set of services.
• Event-driven architecture uses events to trigger communication between components.
• Principles are modularity, scalability, maintainability, and security.
• Modularity designs systems as a collection of independent modules.
• Scalability ensures the system can handle increasing workloads.
• Maintainability ensures the system can be easily modified and updated.
• Security protects the system from unauthorized access and threats.
• Tools include UML modeling tools, enterprise architecture frameworks (e.g., TOGAF), and cloud architecture tools (e.g., AWS CloudFormation).
• TOGAF provides a comprehensive approach to designing, planning, implementing, and governing an enterprise information architecture.
• CloudFormation provides a way to describe and provision all the infrastructure resources in your cloud environment.
• Benefits are reduced complexity, improved reliability, faster development, and better alignment with business goals.
• Challenges include evolving requirements, technology changes, and integration complexities.