Information Systems

Front 1

What is a system?

Back 1

Collection of components,
Has some structure,
Possible outside interaction,
Exhibits purposeful behaviour,
May have subsystems/be a subsystem.

Front 2

What is information system?

Back 2

A: Collection of interacting computer programs that supply information to human decision makers.
B: Collection of interacting computers and humans that make management decisions within an organization.

Front 3

What levels of management there are?

Back 3

Executive - Strategic Planning
Middle - Management Control
Supervisory - Operational Control

Front 4

What is information?

Back 4

Data proccessed for a purpose.

Front 5

Qualities of good info?

Back 5

Brief, Appropriate and Precise.
Accurate.
Timely and Up to Date.

Front 6

MIS?

Back 6

Management Information System. (for middle mgmt level). Takes data from TPS, produces summaries, statistics.

Front 7

TPS?

Back 7

Transaction Proccessing System.
At Supervisory level.

Front 8

DSS?

Back 8

Decision Support System.
Used at Executive level. Takes data from TPS and MIS

Front 9

Define eCommerce.

Back 9

Any exchange of information or business transaction that is facilitated by the use of information and communications technologies.

Front 10

System Development Lifeycle

Back 10

Recognise Opportunity
Feasibility Study
Analyse Requirements
Design Solution
Implement Design
Use & Evaluate System
"Maintenance"

Front 11

What is Use Case composed of?

Back 11

Should have :Primary Actor, Goal, Scope, Main Sequence with extensions and variations at every step.
Guarantee (Success and Minimum).
May also have: Other Stakeholders and their interests,
Trigger event, Preconditions, Constraints

Front 12

What is the purpose of a System Analyst?

Back 12

Understanding and communicating user-requirements to programmers.

Front 13

Explain the difference between Business Use Case and System Use Case.

Back 13

Business Use Case - Interaction with Human activity system
System Use Case - Interaction with an Information System

Front 14

WIMP?

Back 14

Windows, Icons, Menus, Pointers

Front 15

What are Use Cases used for?

Back 15

To identify functional requirements of a system.

Front 16

Explain terms : Stakeholder, Internal/Supporting/Primary Actor, Trigger, Pre-condition, Guarantee

Back 16

Stakeholder - someone with interest in the success of the use case.
Primary actor - who start it off.
Supporting actor - required external support ex: Stock control, banks
Internal actor : visible inside the system
Trigger - what causes the actor to start it.
Pre-condition - what must be true before the use case can occur.
Guarantee - what must be true after the use case had occured.

Front 17

What is Methodology?

Back 17

A coherent set of methods used in carrying out some complex activity.

Front 18

Explain Cohesion

Back 18

Assesses how well a subsystem is focused on a single activity. High(functional) - focused, has only one function
Low(logical) - not focused

Front 19

Explain Coupling

Back 19

Assesses how independent a sub-system is from the rest of the system. Low coupling (good) means that a subsystem has few interactions with others and unaffected by changes in them

Front 20

Explain the Waterfall Methodology.

Back 20

Sequential model (no going back), fixed deliverables.

Front 21

Explain Top-Down design.

Back 21

Breaking up of bigger (and more abstract) components into smaller (and more physical) ones.

Front 22

RAD vs. Waterfall Model.

Back 22

Waterfall:
-Requirements set first
-Delivery when ready
-Resources expand to meet demand
-Low user engagement
Rapid Application Development:
-Resources are fixed first
-Delivery on deadline
-Requirements change to fit
-High user engagement

Front 23

Explain Incremental Delivery, Evolutionary Delivery.

Back 23

-Delivers parts of the whole project.
-Iteratively extends the existing project

Front 24

What is .csv ?

Back 24

Comma Separated Values

Front 25

Agile Software Development Manifesto

Back 25

Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan

Front 26

Characteristics in Stakeholder theory.

Back 26

Power, Legitimacy, Urgency

Front 27

CATWOE.

Back 27

Customers
Actors
Transformation processes
Worldview
Owner
Environment

Front 28

SSM?

Back 28

"Soft" Systems Method

Understanding User Needs.

Uses CATWOE and Rich Pictures for identification and understanding of problem (conflicting views etc.), root definition of system.

Front 29

SSADM

Back 29

Strutured Systems Analysis and Design Methodology

"Hard" methodology

Front 30

ETHICS

Back 30

Effective Technical and Human Implementation of Computer-based Systems.

Socio-Technical Analysis.

Front 31

Multiview.

Back 31

Hybrid methodology based on SSM, ETHICS and SSADM.

Front 32

RAD

Back 32

Rapid Application Development

Iterative development based on prototyping.
Fixed Resources.
High user involvement.

Front 33

DSDM

Back 33

Dynamic Systems Development Method

Extension of RAD.
Principles: User Involvement, team can make decisions, frequent delivery, iterative and incremental development, acceptance according to curret business needs, all changes are reversible, high level scope, testing throughout, communication

Front 34

XP

Back 34

eXtreme Programming

Front 35

CASE

Back 35

Computer-Aided Software Engineering

Front 36

Primary Activities of Value Chain Model

Back 36

Inbound Logistics
Operations
Outbound Logistics
Marketing and Sales
Service

Front 37

Support Activities of Value Chain Model

Back 37

Organisation Structure
Human Resource Management
Technology (Research & Development)
Procurement

Front 38

Explain Supply Chain

Back 38

A set of organizations, people, technology, information, activities, resources, involved in movaing a product/service from supplier to customer.

Front 39

Purpose of Value Chain Model

Back 39

Idetifies activities that the business must carry out in orer to function effectively. These activities add value to the final product and give advantage over the competitors if performed at lower cost or used to create a better product.

Front 40

Explain the Five Forces Model

Back 40

Suppliers
Customers
Substitute products
New entrants
Competitor rivalry

Front 41

EDI

Back 41

Electronic Data Interchange

Front 42

CRM

Back 42

Customer Relationship Management

Front 43

Explain PEST analysis

Back 43

Political
Economic
Social
Technological

Front 44

CAD/CAM

Back 44

Computer Aided Design/Manufacturing

Front 45

ERP

Back 45

Eterprise Resource Planning

Software system that integrates all functions of the organization under one system.