ESIM Dictionary Flashcards

1
Q

What is B2B?

A

Business to business

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What is B2C?

A

Business to customer

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What is ERD?

A

An Entity-Relationship Diagram (ERD) visually represents the data structure of a system, focusing on the entities (data objects), their attributes (properties), and the relationships between them. It helps in designing and understanding the database schema or logical structure of a system.

It is the one often used in DBUD with the boxes with entities(like a book), Attributes(like bookID, Title, Author), relationship(book gets loaned bt member) and the amount of times it happens ( many to one)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Functional Models

A

Functional Models
Purpose: Focus on what the system does or needs to do.

Key Idea: Represents the functions or processes within a system and their interactions.

Tools/Diagrams:
Data Flow Diagrams (DFD): Show the flow of data between processes, data stores, and external entities.

Use Case Diagrams: Represent user interactions and high-level functions of the system. ( we used this)

Example: In an e-commerce system, a functional model might describe processes like “Add to Cart,” “Checkout,” or “Process Payment.”

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

What are these?
TPS
MIS
DSS
MMS

A

These are the things from the colures triangle

TPS feeds raw data (e.g., daily sales).

MIS organizes this into reports (e.g., weekly sales trends).

DSS analyzes and explores scenarios (e.g., demand forecasting).

ESS aggregates everything for strategic decisions (e.g., product expansion plans).

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

What is Structural Models?

A

Structural Models:

Purpose: Focus on what the system is by identifying its components and their relationships.

Key Idea: Represents the static structure of the system, including its entities, their attributes, and their relationships.

Tools/Diagrams:
Entity-Relationship Diagrams (ERD): Show entities, attributes, and relationships.

Class Diagrams (from UML): Define classes, their attributes, methods, and relationships like inheritance and association.

Example: In the e-commerce system, a structural model might define entities like “Product,” “Customer,” and “Order,” and the relationships between them.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Behavioral Models

A

Behavioral Models

Purpose: Focus on how the system behaves over time and in response to events.

Key Idea: Describes the dynamic aspects of the system, such as interactions and state changes.

Tools/Diagrams:
State Machine Diagrams: Represent how an entity changes state in response to events.

Sequence Diagrams: Show the interactions between objects or components in a time-ordered sequence.

Activity Diagrams: Map workflows or processes.

Example: In the e-commerce system, a behavioral model might depict how an order transitions through states like “Pending,” “Processing,” “Shipped,” and “Delivered.”

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

What is Business processes?

A

It refers to the manner in which work is organized, coordinated, and focused to produce a valuable product or service. supported by flows of
material, information, and knowledge among the participants.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

What is TPS (Transaction processing systems) ?

A

A system that keeps track of the elementary activities and transactions of the organization, such as sales, receipts, cash deposits, payroll, credit decisions, and the flow of materials in a factory.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

What is Enterprise systems integration

A

Enterprise systems integration means connecting all the different parts of a business (data, technology, processes) so they work together smoothly. Instead of each department working separately (siloed operations), everything is connected.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

What is BIS (Business intelligence system) ?

A

It helps with monitoring, controlling, decision-making, and administrative activities

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

What is a SMD ( State Machine Diagram)

A

State Machine Diagram
Definition: A UML diagram that shows how an object moves between different states based on events or conditions.
Example: We have one in our paper about payment options.

It’s great for modeling the behavior of systems like workflows, software, or devices.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

What is Business Intelligence?

A

Business intelligence is a modern term for
data and software tools for organizing,
analyzing, and providing access to data to
help managers and other enterprise users
make more informed decisions.
* Business intelligence addresses the
decision-making needs of all levels of
management.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

What is a Collaboration system

A

“Collaborative systems are defined as information systems used to facilitate managerial activities by allowing efficient sharing of data between various projects and departments, sharing knowledge and experiences at various levels within the organizations and among teams”

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

What is a class diagram?

A

Class Diagram
Definition: A UML structure diagram that shows the structure of a system by representing its classes, attributes, methods, and relationships.

In our work
A class diagram is chosen to show the structure of the Course Application Process (CAP) because it focuses on the system’s core components. It shows:

Classes: Key parts of the system (e.g., courses, applications).
Attributes: Details of each class (e.g., course name, applicant ID).
Relationships: How classes connect (e.g., applicants apply for courses).
The diagram helps us:

Visualize the entire course application and creation process.
Identify components for the prototype and define requirements.
Reduce duplicate data and make integration smoother when building the final system.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

What is MIS
(management information systems) ?

A

MIS summarize and report on the company’s basic operations using data
supplied by transaction processing systems. The basic transaction data from TPS are compressed and usually presented in reports that are produced on a regular schedule (Most MIS use simple routines, such as summaries and comparisons, as opposed to sophisticated mathematical models or statistical techniques)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

What is DSS (Decision-support systems) ?

A

Try to answer questions such as these: What would be the impact on production schedules if we were to double sales in the month of December? What would happen to our return on investment if a factory schedule were delayed for six months? (Usually combine info from TPS And MIS with external info)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

What is ESS (Executive support systems) ?

A

Address nonroutine decisions requiring judgment, evaluation,
and insight because there is no agreed-on procedure for arriving at a solution (For Senior Management)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

What is enterprise applications?

A

Systems that span functional areas, focus on executing business processes across the business firm, and include all levels of management.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

What is SCM (Supply Chain Management Systems) ?

A

systems help suppliers, purchasing firms, distributors, and logistics companies share information about orders, production, inventory levels, and delivery of products and services so they can source, produce, and deliver goods and services efficiently.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

What is CRM (Customer Relationship Management Systems) ?

A

CRM systems provide information to coordinate all of the business processes that deal with customers in sales, marketing, and service to optimize revenue, customer satisfaction, and customer retention. This information helps firms identify, attract, and retain the most profitable customers; provide better service to existing customers; and increase sales.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
22
Q

What is an ERP

A

ERP System (Enterprise Resource Planning)
Definition: Software that integrates core business processes into one system.
Example: An ERP system manages inventory, accounting, and HR in a single platform.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
23
Q

Data Integration

A

Data Integration
Definition: The process of combining data from different sources into a unified view.
Example: A company merges customer data from its sales system, marketing platform, and support database to get a single customer profile.

It helps improve data consistency, decision-making, and system efficiency.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
24
Q

What is Data Standardization

A

Data Standardization
Definition: The process of formatting data into a consistent structure for easy use and analysis.
Example: Converting all date formats in a database to “YYYY-MM-DD” ensures consistency.

It improves data quality and simplifies integration.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
25
Q

What is ERP vs Enterprise system?

A

ERP System (Enterprise Resource Planning)
Focus: Integrates core business processes (e.g., accounting, inventory, HR).

Scope: Primarily internal operations, ensuring departments work seamlessly.

Example: SAP or Oracle ERP managing inventory and payroll in one platform.

Enterprise System

Focus: Broader term for all large-scale software supporting enterprise activities (e.g., ERP, CRM, SCM).

Scope: Includes ERP but also extends to external-facing systems like customer relationship management (CRM) and supply chain management (SCM).

Example: An enterprise system may include ERP for internal operations, CRM for managing customers, and SCM for coordinating suppliers.

Summary:
ERP is a subset of enterprise systems, focusing on internal processes, while enterprise systems cover both internal and external operations.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
26
Q

What is KMS (Knowledge Management Systems) ?

A

enable organizations to better manage processes for capturing and applying knowledge and expertise. These systems collect all relevant knowledge and experience in the firm and make it available wherever and whenever it is needed to improve business processes and management decisions. They also link the firm to external sources of knowledge.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
27
Q

What is an Enterprise systems

A

It’s a systems that can integrate departments and functions across organizations

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
28
Q

What is a Non-Functional Requirements

A

A set of specifications that describe the system’s operation capabilities and constraints: This could be security, performance, usability, adaptability etc. An easy understandeble example. An elevators FUNCTIONAL requirement is to elevate people to a certain floor. Whereas the NON-FUNCTIONAL is that it has to do this fast and safe. To measure this we vould say that it has to reach a floor within 30 seconds. → (defined by Glinz) how well does the system perform certain functions. The requirements describe the quality attributes, performance criteria and constraints under which the system performs. nonfunctional requirements addresses aspects such as usability, reliability, performance, scalability, security and maintainability

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
29
Q

What is a Functional requirements:?

A

(Defined by Glinz) What should the system do? Describes the behaviour of the system in terms of its functions and features. Outlining the tasks, operations, or services that the system must perform, including both input and output.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
30
Q

What is SRS?

A

Software Requirements Specifications → includes in-depth descriptions of the software that will be developed

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
31
Q

What is SyRS?

A

System Requirements Specification → collects information on the requirements for a system.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
32
Q

What is requirement specification?

A

Agreement between customers and developers about the target system.

We used it to make the perfect prototype

Benefits
* Establish agreement between customers and
suppliers
* Reduce the development effort
* Provide a basis for cost and schedule estimation
* Provide a basis for validation and verification
* Facilitate transfer
* Serve as a basis for enhancement

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
33
Q

What is Requirements Determination

A

Purpose:
to convert high level business requirements (from the system request) into
detailed requirements that can be used as inputs for creating models

What is a requirement?
A statement of what the system must do or a characteristic it must have
Will later evolve into a technical description of how the system will be
implemented

Types:
Functional: relates to a process or data
Quality: relates to performance or usability
Constraints: relates to conditions beyond the project scope

34
Q

What is UML?

A

Unified Modeling Language (UML)
Definition: A visual language for designing and understanding systems.
Example: Use a UML diagram to show how customers, orders, and products relate in an online store.

35
Q

What is CRC

A

CRC (Class-responsibility-collaboration)
Definition: A model for designing object-oriented systems using cards to define classes, their responsibilities, and collaborators.
Example: A “Customer” class card might list “place order” as a responsibility and “Order” as a collaborator.

36
Q

What are the diffrent boxes/stages in The Work Systems Life Cycle Model

A

Initiation
Development
Implementation
Operation

Initiation: beginning of the work system, conducting feasibility studies, defining the scope and objectives of the work system, and securing the necessary resources

Development: software development, software acquisition, software configuration, creation of new procedures, creation of documentation

Implementation: deployment, data migration, training its users, and testing

Operation: Maintenance and support, apply updates, and make improvements as necessary to keep the work system running smoothly

37
Q

What is Enterprise Architecture?

A

Enterprise Architecture (EA)

A way of simplyfing the complexity of the landscape + helping us to understand how businesses and It work together

Enterprise Architecture is a conceptual framework (management tool and organizational blueprint) that describes how the business is constructed

How a business operates; Work system, business processes what capabilities are supported, what information is used… It’s more or less, how do they do what they do.

the four domains of EA:

  1. Business architecture is about capturing how a business operates
  2. Application architecture - the software solutions, the development and adaption of these
  3. Data Architecture - data, the modeling of this data in correct ways
  4. Technology architecture - the underlaying technology that makes everything go

… cloud vendors what to makes the three domains go away from the business and into the cloud

38
Q

What’s Ontological Overlap (OO)

A

Ontological Overlap (OO):
This is when different models (or diagrams) share the same information.

Good: A little overlap helps connect ideas across models.
Bad: Too much overlap repeats information and confuses people.

39
Q

Combined Ontological Completeness (COC):

A

Combined Ontological Completeness (COC):
This means the models together cover everything about the topic.

Good: Ensures nothing important is left out.
Bad: If it’s too detailed or poorly organized, it can overwhelm users.

40
Q

What is Work System Theory?

A

Work System Theory (WST)

Definition: WST is a framework for understanding, analyzing, and improving systems in which humans and machines work together to produce products or services.

Framework: Have nine elements.
Snapshot: is the static overview for understanding.
Lifecycle Model is the dynamic evolution.
WS Method: Analysis and design method: “As-is” & “To-be”(re-imagine and opportunites).

41
Q

What is Work sytem Framework

A

Process with all its elements and influences. Both the as-is-view as well as the natural evolution and implementation. Uses both internal and external key points.

It is the triangle picture

The elements
1. Participants: People who perform the work.
2. Information: Data and knowledge used and generated by the system.
3. Technologies: Tools, machines, and software used in the work.
4. Processes and Activities: The sequence of tasks and procedures to achieve objectives.
5. Products and Services: The outcomes produced by the system.
6. Environment: The broader context in which the work system operates.
7. Infrastructure: The supporting systems, tools, and facilities.
8. Strategies: The goals and policies guiding the work system.

42
Q

What is a work system and what is Enterprise systems?

A

Work system:
A work system is a system in which human participants and/or machines perform work (processes and activities) using information, technology, and other resources to produce specific products/services for specific internal and/or external customers. (Alter, 2013)

Enterprise systems:
… is purposed-designed computer software used to satisfy the needs of an organization rather than individual users” (Wikipedia) … is intended to solve an enterprise-wide problem, rather than a departmental problem.” (Fowler 2002)

43
Q

Which is work system and which is IT-system?

Sundhedsplatformen
Patient treatment
Invoicing
Mentimeter -
SAP ERP -
Customer Support Processes
Microsoft Teams
Order Fulfillment
Salesforce CRM
Inventory Management
Zoom - IT system
Employee Onboarding Process
Product Development

A

Sundhedsplatformen - IT system
Patient treatment - Work system
Invoicing - Work system
Mentimeter - IT system
SAP ERP - IT system
Customer Support Processes - Work system
Microsoft Teams - IT system
Order Fulfillment - Work system
Salesforce CRM - IT system
Inventory Management - Work system
Zoom - IT system
Employee Onboarding Process - Work system
Product Development - Work system

44
Q

Good things about Work System theory?

A

?

45
Q

Bad things about Work System theory?

A

?

46
Q

Facts about Work System theory (WST)?

A

Work system Theory is a system in which human participants and/or machines perform work.

A work system is a system in which human participants and/or machines perform work (processes and activities) using information, technology, and other resources to produce specific products/services for specific internal and/or external customers.
Is not the same as a IT-system.

It involves three elements of work system theory:

Work systems framework (static model)

Work systems snapshot (short analysis based on the 6 core dimensions of the work system framework)

Work systems lifecycle model (dynamic model)

it also has Work System Methode (WSM)

WST offers a comprehensive theory for understanding work systems, while WSM provides a method for applying that theory in practice. Together, they help organizations improve their processes, technologies, and overall efficiency.

47
Q

Good thing about Improving work systems?

A

?

48
Q

bad thing/changes about improving work system?

A

15: Minimize effort consumed by technology (The whole problem was that we had to much dobbelt work)

What we could include in alters 21 work
#13: Protect information from inappropriate use (GPR)

49
Q

Facts about Improving work systems

A

there are a few ways of improving work system

Four strategies for identifying problems and changes
1. Your informants tell you
2. Violations of alignment in WST
3. Violations of Alter’s work system principles
4. Matthiasen et al.’s suggestions for creating ideas during analysis and design

50
Q

Good things about Requirements determination specification

A
  • Establish agreement between customers and
    suppliers
  • Reduce the development effort
  • Provide a basis for cost and schedule estimation
  • Provide a basis for validation and verification
  • Facilitate transfer
  • Serve as a basis for enhancement
51
Q

Bad things about Requirements determination specification

A

?

52
Q

Facts about Requirements determination specification

A

It’s about
Requirements Determination
Requirement specification
Functional vs non functional requirements

What is a requirement?
A statement of what the system must do or a characteristic it must have.

Purpose of determination:
to convert high level business requirements (from the system request) into detailed requirements that can be used as inputs for creating models

Requirement specification:
Agreement between customers and developers about the target system.

Determination: is about finding out “what” is needed.
Specification: is about defining “how” the requirements should be met in detail.

Functional
What should the system do? Describes the behaviour of the system in terms of its functions and features. Outlining the tasks, operations, or services that the system must perform, including both input and output.

Non-functional:
Types:
Functional: relates to a process or data
Quality: relates to performance or usability
Constraints: relates to conditions beyond the project scope

53
Q

Good things about Conceptual modelling

A

?

54
Q

Bad things about Conceptual modelling

A

?

55
Q

Facts about Conceptual modelling

A

Conceptual modeling is the process of creating an abstract, simplified representation of a real-world system, process, or idea to help people understand, analyze, or communicate its essential aspects. It focuses on capturing the system’s key concepts and relationships without delving into technical details or implementation.

It has UML which is Class diagrams , Use Case Diagram and Activity Diagram

Then it has
Functional Models
Structural Models
Behavioural Models

56
Q

Good things about Business cases?

A

?

57
Q

Bad things about Business cases?

A

?

58
Q

Facts about Business cases?

A

The business case defines what is to be done, why,
and what are the timescales and costs involved.

There are 6 stages of developing a bussines case ( Ward et. al)
Define business drivers and invest objectives
Identify benefits, measures and owners
Structure the benefits
Identify organizational changes enabling benefits
Determine the explicit value of ach benefit
Identify costs and risks

59
Q

Good things about Enterprise systems?

A

?

60
Q

Bad things about Enterprise systems?

A

Challenges of implementing enterprise systems:

User resistance: user resistance is the biggest challenge with implementation.

Knowledge barriers: Users experiencing a hard time unlearning processes, using time on work around rather than learning new system, hiring college student – easier to teach someone somethings new, resisting the implementation

Assimilation (having the adapt new processes) barriers: training the personnel – 15-20% of the budget assigned to the training

Confirguation (setup of system) barriers: using consultents/core teams – the best form the department

61
Q

Facts about Enterprise systems?

A

It as:
​​ ​​ERP = enterprise ressource planning systems
SCM – Supply chain management systems
CRM – Customer relationship management systems
EA – Enterprise architecture: concept desiring how a business is constructed

4 way to implement a Enterprise system

Adoption: First there is adoption where the users adopt a program and make it into what it actually needs to be used for by diffrent factores

Lerning: is by simply make your employees learn the new system the way it’s build and therefore get new values

Affordance: When one system is set up and used, it creates new possibilities for other systems or features to be used. It’s about what the system can do and how users make use of those abilities.

Power: refers to how power and influence within the organization affect the system. It’s about who controls resources and how their roles and relationships shape decisions.

62
Q

Good things about Collaboration systems?

A

Enhance team productivity through steamlines communication and reduces meetings, improved information accecibility and knowledge sharing (KMS), promoting hybrid teams (geographical, national/cross-departmental), better tracking of work processes

63
Q

Bad things about Collaboration systems?

A

?

64
Q

Facts about Collaboration systems?

A

It’s about Communication * Knowledge Sharing * Collaboration

KMS – Knowledge management system
Implementation consideration:

65
Q

Good things about Decision support systems

A

?

66
Q

Bad things about Decision support systems?

A

?

67
Q

Facts about Decision support systems?

A

Decision Support System (DSS)

Definition: A computer-based tool that helps analyze data to support decision-making.

Example: A DSS forecasts sales trends to help a manager decide how much inventory to stock.

Further Explanation:
DSS systems are designed to assist with complex, unstructured decisions by providing data analysis, simulations, or recommendations. For instance, in healthcare, a DSS might analyze patient data and suggest potential treatments based on past cases. It complements human judgment by offering insights but doesn’t make decisions on its own.

68
Q

What can you tell me about
Ramesh, B., Cao, L., & Baskerville, R. (2010). Agile requirements engineering practices and challenges: an empirical study.

A

Focus: Agile application and practices.
Method: Qualitative study of agile practices.

A framework for evaluating impact and appropriateness of
requirements engineering practices by relating them to
requirements engineering risks.

This paper reinforced our choice of an Agile Requirements Engineering Approach for the system design. Agile’s flexibility and adaptability align well with the evolving needs of our project.
We incorporated this into the Requirements Specifications and Prototype Development sections.

It has a model in the text. The model has 3 circles on top explaing that agile requirement engerning is diffrent for normal requirement engering for 3 reasons.
(Check if in doubt)

After this it has a box with a few practises that should be adapted in order to fulfill the agile approaches driven factor
Agile RE emphasizes face-to-face communication, iterative refinement, prioritizing minimum viable products, adaptable planning, prototyping for insights, and review meetings with user acceptance tests to ensure clarity and alignment with requirements.

Last there is some challenges when doing agile RE. That’s the last box. This box talked about that even flexibility has problems and challenges

Agile challenges include cost estimation, inadequate architecture, neglected non-functionals, limited customer involvement, single-dimension prioritization, minimal documentation, and insufficient requirements verification.

69
Q

How can we use Ramesh, B., Cao, L., & Baskerville, R. (2010). Agile requirements engineering practices and challenges: an empirical study.?

A

Agile approach to requirement, making sure that the system keep being up-to-date. Beneficial in its adaptive and iterative nature - aligns with the dynamic needs of the system. The flexibility allows us to respond to changing requirements, as we learn more about user needs and system constraints.

70
Q

What can you tell me about Jabbari, M., Recker, J., Green, P. & Werder, K. (2022). How do Individuals Understand Multiple Conceptual Modeling Scripts? Journal of the Association for Information Systems?

A

Focus: Understanding domain representation via multiple conceptual modeling scripts.
Method: Mixed-method approach including two laboratory experiments with eye-tracking analysis.

What was studied?
The text wanna show how people reach to many being shown many (conceptual) models. Does it help or does it make it more difficult? They used an Eye tracker to find out.

Moderate Ontological Overlap Improves Understanding:
Combined Ontological Completeness Alone is Insufficient:

71
Q

Why is Jabbari, M., Recker, J., Green, P. & Werder, K. (2022). How do Individuals Understand Multiple Conceptual Modeling Scripts? Journal of the Association for Information Systems relevant for our assignment?

A

IT is relevant since we use models in our assignment. We want to use them in a way that helps the reader understand the best. This is by having moderate Ontological Overlap (OO) and Combined Ontological Completeness (COC).

You could also argue that it does in someway consulters are important with the new system cause when implementing a system you have to educate you staff in how to probably read the models. Otherwise we should train the users to how to read it.

72
Q

What can you tell me about Lehrig, T., Krancher, O., & Dibbern, J. (2017). How users perceive and actualize affordances: An exploratory study of collaboration platforms?

A

Focus:
Users’ understanding of actualizing affordances.

Keywords:
Knowledge sharing, affordances, perception of affordances, actualization of affordances, collaboration platform

There is an important model that focuses on Affordance perception(when a user realizes an action is possible) andAffordance actualization (when they try to use it).
Users notice affordances through three main processes:

  1. Imitating others.
  2. Exploring by trial and error.
  3. Transferring knowledge from other experiences.
  • After recognizing affordances, users often need to configure the platform:
    1. Delegated configuration: getting help from others.
    2. Guided configuration: following instructions or guidance.
    3. Autonomous configuration: setting things up independently.

It uses the example of Susan who imitated, Marvin while exploring and George who already had knowlage about other systems

73
Q

What can you tell me about Volkoff, O., Strong, D. M., & Elmes, M. B. (2005). Understanding enterprise systems-enabled integration.

A

Focus: The process of enterprise systems-enabled integration within organizations.

Method: Qualitative research, including case studies and interviews, to explore real-world integration challenges and strategies.

Enterprise integration

Types of integration

Data integration - ES enable shared access to data across departments, reducing data redundancy + inconsistency

Functional integration - by aligning business processes ES supports seamless crossfunctional workflows

Technical integration - focused on ensuring that the IT infrastructure is compatible, allows for smooth data exchange + communication across platforms
Challenges:

Complexity: Hard to design a system for all departments.
Change Management: New roles and workflows face resistance.
Data Quality: Inconsistent data leads to poor decisions.

Advantages:

Better Decisions: Real-time data improves choices.
Efficient Workflows: Fewer manual tasks and delays.
Improved Service: Clearer customer data.

74
Q

How did we use Volkoff, O., Strong, D. M., & Elmes, M. B. (2005). Understanding enterprise systems-enabled integration.?

A

How we Applied This in Your Text:
We used their idea of database integration by connecting your system to an external database (CVR - Virk).

This mirrors their unifying databases technique to reduce data redundancy (having the same data repeated in different places).
They focused on internal databases, but you needed an external one since Central Perk might not have a centralized system.

75
Q

What can you tell me about Robey, D., Ross, J. W., & Boudreau, M. C. (2002). Learning to implement enterprise systems: An exploratory study of the dialectics of change.

A

Focus: Knowledge barriers and methods to overcome them (Configuration & Assimilation, Piecemeal & Concerted).
Method: Comparative study of 13 industrial firms that implemented ERP systems.

The text does teach us about diffrent knowlage barriers and how we can overcome them

Fx. Configuration (where you set up a system (Need the best people)) & Assimilation ( Adapting a new process(Needing to train your own people))

Then there is Piecemeal(Setting up system step by step(Takes longer but les risk and don’t need as qualified people)) & Concerted( Change everything at the same time(More risk and you need more qualified people))

There will be resistance when applying a new system, but once seeing the benefit there will be support for new system

Challenges
- Managing Change: Balancing the need for new systems while keeping operations stable.
- Overcoming Resistance:Helping staff accept and adapt to new processes.
- Ongoing Support: Keeping the system updated and ensuring people stay engaged.
- Continuous Adaptation: Both the system and the organization’s needs change over time, requiring constant adjustments.

76
Q

How did we use this text in our assignment?
Robey, D., Ross, J. W., & Boudreau, M. C. (2002). Learning to implement enterprise systems: An exploratory study of the dialectics of change.

A

Specific Use:
This text helped us consider potential challenges in implementation, like unlearning old processes or creating workarounds.
We used this to argue why these challenges wouldn’t pose significant issues in our case, given the small scale of the new system. This was highlighted in the Implementation Plan.

77
Q

What can you tell me about Strong, D. M., Johnson, S. A., Tulu, B., Trudel, J., Volkoff, O., Pelletier, L. R., … & Garber, L. (2014). A theory of organization-EHR affordance actualization?

A

Focus: Affordance actualization in organizations at hospital.

Method: Grounded theory using interviews and observations at a multi-site group medical practice in the northeastern US.

Keywords: Affordance actualization, user adaption, system interoperability, data security and privacy.

The text looks at Hospitales and the Work system they use. They use EHR (Electronic Health Records) to better manage data, patients and manegment. The sytem does not work well if the users don’t know how to use it .
What problems did they accure. Older doctores preferred the legacy system. If people were not trained they made cheap workarounds and didn’t fully utilize the system

78
Q

How we use it in our text/How could we use it:
Strong, D. M., Johnson, S. A., Tulu, B., Trudel, J., Volkoff, O., Pelletier, L. R., … & Garber, L. (2014). A theory of organization-EHR affordance actualization?

A

The text talks a lot about how a system is only as good as those using it. In our text we say that MR4 is only used as an CRM system, when MR4 is closer to an ERP system.

79
Q

What can you tell me about Brhel, M., Meth, H., Maedche, A. & Werder, K. (2015). Exploring principles of user-centered agile software development: A literature review. Information and Software Technology,

A

Focus: The text looks at agile vs user-centered design and Hybrid development models, referred to as “user-centered agile software development” (UCASD) in this article, propose to combine the merits of both approaches in order to design software that is both useful and usable.

What is UCASD?
Agile Development (ASD) – Focuses on being flexible and making quick changes during development.
User-Centered Design (UCD) – Focuses on making the software easy to use by understanding user needs through feedback and testing.

Process integration - taking the processes form both ASD and UCD and combining them both

Practices integration - the same as above. integration practices from both practices

people integration - refers to taking the experts from the different aspects and making them work together

social integration - sharing knowledge

technology integration - using technological means to support both the practices and the integration

It has 5 principles to follow:
1. Separate product discovery and product creation (Understand user needs and define the problem clearly before starting to build the product.)

  1. Iterative and incremental design and development (Build and improve the product step by step with user feedback.)
  2. Parallel interwoven creation tracks (Design slightly ahead of development to guide coding effectively.)
  3. Continuous stakeholder involvement (Keep users and stakeholders involved throughout the project.)
  4. Artifact-mediated communication (Use visuals and prototypes to align understanding among all team members.)
80
Q

How have we used Brhel, M., Meth, H., Maedche, A. & Werder, K. (2015). Exploring principles of user-centered agile software development: A literature review. Information and Software Technology?

A

We have not mentioned it in the paper but we used it indirectly.

We created plan-based requirements to ensure a baseline for the requirements but implemented a more agile requirement specification afterwards to ensure that we can change and adapt to changes.

So our business driver was from an plan based standpoint

After we found the driver, then we started with agile approach where we wanna revisit the business driver with the feedback and go through it again like SCRUM

81
Q

What can you tell me about Kim, H. W., & Kankanhalli, A. (2009). Investigating user resistance to information systems implementation: A status quo bias perspective.

A

It is the adoption perspective.
Focus: User resistance to information system (IS) implementation.
Method: Survey of 375 organizations around the world relating to user resistance.

Key Concepts (Why Users Resist Change):

Rational Decision-Making:
Users compare benefits vs. risks before accepting new systems.

Psychological Commitment:
Sunk Costs: People resist change if they’ve invested time and effort in the old system.
Control: Fear of losing control over familiar tasks.
Social Norms: Colleague opinions can influence resistance.

Cognitive Perception:
Loss Aversion: Users often focus more on potential losses than the gains of the new system.

82
Q

The model in What can you tell me about Kim, H. W., & Kankanhalli, A. (2009). Investigating user resistance to information systems implementation: A status quo bias perspective? What does to show

A

The diagram explains why someone will have resistance of a new system tho it may be beneficial.

On the left it has Status Quo Bias Theory that shows

Loss Aversion: Fear the new system might perform worse.

Net Benefits: Users weigh if the new system will improve work.
Transition Costs: Time and effort to learn the new system.
Uncertainty Costs: Not knowing if the new system will work better.
Sunk Costs: Time already invested in the old system.

Sunk Costs: Time and effort already spent on the old system.
Social Norms: Resistance because others prefer the old system.
Control: Feeling forced into change without enough control.

Switching Benefits: If the benefits (like automation) outweigh the costs, users are more likely to accept the system.
Perceived Value: Users evaluate if the new system adds value to their tasks.

Switching Costs: If learning the system feels too
difficult, users resist adoption.

Colleague Opinion: The views of peers influence acceptance.

Self-Efficacy for Change: Users’ confidence in learning the system.
Organizational Support for Change: Providing training, resources, and encouragement to reduce resistance.