Business Information Systems Overview 2024-2025

Course Information

• Course title: Business Information Systems
• Academic year: 2024-2025
• Professor: Alexandre Thys

Course Overview

• Topics include:
  • Introduction
  • Basic concepts
  • Algorithms
  • Programming
  • Functionalities
  • Project management
  • Databases
  • Informatics in a business context
  • Enterprise applications
  • New business models
  • Current trends in IT

Developing an IT Application

• Key considerations:
  • Activities and their order
  • Required information
  • Resources (financial, human, technology, knowledge)

Systems Development Lifecycle

• General overview:
  • Planning
  • Analysis
  • Design
  • Implementation
  • Testing
  • Go-live
  • Maintenance

Planning

• IT project complexity mandates thorough planning, including:
  • Scoping
  • Alignment with IT/business goals
  • Cost-benefit analysis
  • Risk analysis and mitigation
  • Task and resource planning
• Resulting in a formal business case for approval
• Initial working schedule must be detailed, specifying tasks, durations, personnel, interdependencies, and costs.
• Techniques such as work breakdown structures (WBS), PERT charts, and Gantt charts are helpful.

Work Breakdown Structure (WBS)

• Table/figure outlining all tasks necessary for project completion, including:
  • Tasks and subtasks
  • Duration
  • Allocation
  • Dependencies

PERT Chart

• Visualizes dependencies between tasks.
• Calculates early start/end, late start/end, and critical path.
• Aids resource allocation.

Gantt Chart

• Tracks project timeline visually.
• Allows project managers to monitor progress against schedule.
• Enables identification of potential delays.

Analysis

• Focuses on identifying the precise requirements of the IT system.
• Must be more specific than the planning phase.
• It involves gathering information from stakeholders (internal and external business users, customers, management, executives, technicians, etc.) to determine system functionality and gather relevant issues.
• Sources of information may include existing documents, interviews, questionnaires, and observations.
• Workshops/brainstorming sessions can further clarify requirements.
• The analysis should synthesize insights into models and artifacts (use cases, data models, process models).

Design

• Defines the application's overall architecture and functional requirements.
• Involves determining necessary building blocks, integration methods between components, and interfacing with external applications.
• It also involves choosing appropriate frameworks and technologies and defining necessary algorithms (e.g., route calculation, sorting).
• Technical details are integrated into the design models.

Implementation

• Translates the design into actual programming code.
• Implementation can be done through in-house programmers, hired consultants, or outsourcing.
• Off-the-shelf applications can also be modified or configured.

Testing

• Evaluates whether the application conforms to specified requirements.
• Types of tests may include validation (to ensure system meets user expectations) and verification (to confirm functionality matches requirements).
• Testing includes unit tests, system tests, security controls, and an examination of inputs, processes, and outputs.
• Testing plans are documented for a clear understanding of scope, the approach, resourcing, and schedule. Expected vs. actual results are compared.

Go-Live

• Strategies for deployment include "big bang" (simultaneous deployment to all users), parallel (running old and new systems concurrently), pilot study (limited rollout), and gradual (phased rollout).
• Consideration of fallback plans and training is crucial.

Maintenance

• Software is updated, bugs are fixed, and enhancements are added.
• Types include corrective (fixing errors), perfective (adding functionalities), and adaptive (keeping up with technological changes).
• The goal is to maintain system functionality and usability while adhering to industry standards and best practices.

Project Management

• IT projects are complex endeavors requiring proper planning.
• Crucial aspects include project goals, timeline constraints, budget, resource allocation, and quality standards.
• Project failure factors include incomplete requirements, limited user involvement, lack of executive support, poor planning, unclear objectives, and inadequate resources.
• Key success factors include clear requirements, substantial user involvement, top management support, detailed planning, realistic schedules, and milestones.

SWOT Analysis

• A strategic planning tool used to identify strengths, weaknesses, opportunities, and threats for a project or organization.
• Used to assess project viability through an internal and external evaluation of factors that may affect the project.

This quiz tests your knowledge on Business Information Systems for the academic year 2024-2025. It covers essential topics such as systems development lifecycle, project management, and current trends in IT. Prepare to gauge your understanding of key concepts in the field.