Systems Design Chpt 1 & 2

Front 1

Transaction Processing Systems (TPS)

Back 1

Processes large amounts of data for routine business transactions. boundary spanning. supports day to day operations of the company. Examples: process payroll, inventory management

Front 2

Office Automation Systems (OAS)

Back 2

The court date on workers to share information but do not usually create new knowledge EX: word processing, spreadsheets, desktop publishing, electronic scheduling, etc

Front 3

knowledge work systems (KWS)

Back 3

Supports professional workers such as scientists and engineers and doctors. Examples: computer aided design systems, Virtual Reality system, investment workstation

Front 4

Management Information Systems (MIS)

Back 4

Supports a broad spectrum of organizational tasks including decision analysis and decision making. Examples: profit margin by sales region, expenses versus budget

Front 5

Decision support management

Back 5

Aid decision makers in making of decision

Front 6

Expert Systems & A. I.

Back 6

Capture and uses of knowledge of an expert for solving a particular problem which leads to a conclusion or recommendation.
researching understanding natural language and ability to reason through a problem to its logical conclusion

Front 7

Executive Support Systems (ESS)

Back 7

Helps executives to make unstructured strategic decisions in an informed way

Front 8

Group Decision Support System

Back 8

Permit group members to interact with electronic support

Front 9

Computer Supported Collaborative Work System

Back 9

A general term for GDSS.
may include software support called groupware for team collaboration via network computers

Front 10

Enterprise Resource Planning System (ERP)

Back 10

Performance integration of many information systems existing on different management levels and within different functions

Front 11

System Development Life Cycle

Back 11

The systems development life cycle is a phased approach to solving business problems
Developed through the use of specific cycle of analyst and user activities
each phase has unique user activities

Front 12

Human Computer Interaction (HCI)

Back 12

The demand for analysts who are capable of incorporating HCI into the system development process keeps increasing, as companies begin to realize that the quality of systems and the quality of work life can be improved by taking a human centered approach at the outset of a project

Front 13

CASE Tools

Back 13

Productivity tools for system analysis that have been created explicitly to improve their routine work through the use of automated support

Front 14

Upper Case tools

Back 14

Create and modify the system design
help in modeling organizational requirements and defining system boundaries

Front 15

Lower Case Tools

Back 15

Generate computer source code from the case design
source code is usually generated in several languages
decreases maintenance time generates error free code

Front 16

Agile Approach Stages

Back 16

Exploration
Planning
Iterations to the first release
Productionizing
Maintenance

Front 17

Process

Back 17

Some action or group of action takes place. curved square

Front 18

Entity

Back 18

A person, group, department, or anything system that either receives or originates information or data. square with black shading upper left corner

Front 19

Data Flow

Back 19

Shows that information is being passed from or to a process
an arrow

Front 20

Communicates

Back 20

An actor is connected to a use case using a line with no arrowheads

Front 21

Includes

Back 21

A use case contains a behavior that is common to more than one other use case the arrow points the common use case

Front 22

Extends

Back 22

A different use case handles exceptions from the basic use case the arrow points from the extended to the basic use case

Front 23

Generalizes

Back 23

1 UML thing is more general then another thing the arrow points to the general thing with open arrow head

Front 24

4 steps to creating a use case

Back 24

Use agile stories, problem definition objective, user requirements, or a features list
Ask about the tasks that must be done
Determine if there are any looping actions
The use case ends when the customer goal is complete

Front 25

Operations Controls

Back 25

Make decisions using predetermined rules that have predictable outcomes
Oversees the operating details of the organization

Front 26

Managerial Planning and Contols

Back 26

Make short term planning and control decisions about resources and organizational objectives
Decisions may be partly operational and partly strategic

Front 27

Strategic Management

Back 27

Look outward from the organization to the future
Make decisions that will guide middle and operations managers
Work in highly uncertain decision-making environment
Define the organization as a whole

Front 28

Attributive Entity

Back 28

An entity that describes attributes such as repeating groups is called

Front 29

Associative Entity

Back 29

An entity that joins two other entities is called

Front 30

Analyzing System needs

Back 30

In which phase of the SDLC are data flow diagrams constructed

Front 31

1:1

Back 31

In an organisation with many employees and many cubicles with each employee having a unique phone extension is said to be a blank relationship

Front 32

Strategic

Back 32

Which level of management is most dependent on external information

Front 33

Triangle

Back 33

Which of the following symbols is not used in the context level data flow diagram

Front 34

Feedback

Back 34

Which of these is most clearly associated with system control

Front 35

Decision Support System*

Back 35

Which of these is the most personalized