Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

IT261 Systems Design - Illinois State University > System Design Chapter 04 > Flashcards

System Design Chapter 04 Flashcards

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

Analysis Activities

A

Gather info - Define Sys Req - Prioritize Requirements - Prototype for Feasibility & discovery - Generate & evaluation alternatives - Review recommendations with Management

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

Gathering Info

A

interviewing users - watching users - review planning docs - review policy statements - study documentation from existing system

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

Define System Requirements

A

Uses modeling to help define system requirements

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

Logical Model

A

Any model that shows what the system is required to do without committing to any one technology

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

Physical Model

A

Any model that shows how the system will actually be implemented

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

Scope Creep

A

system requirements tend to expand as users make more suggestions

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

Prioritize Requirements

A

Identify the most essential requirements of the new system

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

Prototype for Feasibility and Discovery

A

used to better understand the user’s needs. Checks the feasibility of certain approaches to the business need.

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

Generate and Evaluate Alternatives

A

Many alternatives exist that will need to be evaluated for the best match

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

Review Recommendations with Management

A

When all other analysis activities are complete the review with management will happen to decide if best to proceed or not

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

System Requirements

A

Specifications that define the functions to be provided by the system

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

Functional Requirements

A

a system requirement that describes and activity or process that the system must perform

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

Non-functional requirement

A

other than activities -such as technology-performance - usability - reliability and security

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

Non-func req: Technical Requirement

A

describes an operational characteristic related to an org’s environment - hardware - and software

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

Non-func req: Performance Requirement

A

describes an operational characteristic related to workload measures such as throughput and response time.

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

non-func req: Usability Requirement

A

describes an operational characteristic related to users - such as the user interface - work procedures - online help and documentation

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

non-func req: Security requirement

A

describes users access to certain functions and the conditions under which access is granted.

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

Models

A

representation of some aspect of the system being built

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

Mathematical Model

A

series of formulas that describe technical aspects of a system.

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

Descriptive Models

A

narrative memos - reports or lists that describe some aspect of a system.

22
Q

Graphical Model

A

diagrams and schematic representations of some aspect of a system

23
Q

Stakeholders

A

all the people who have an interest in the success of a new system the users the clients (paying for it) the technical staff

24
Q

Horizontal user needs

A

Info flow across multiple departments

25
Q

Vertical user needs

A

clerical - middle management and senior executives

26
Q

transaction

A

single occurrence of a piece of work or activity done in an organization

27
Q

business users

A

uses the system to perform day to day operations

28
Q

Information users

A

pulls info form the system on a daily - weekly - monthly and annual schedule - may not have access to edit info

29
Q

Management users

A

pulls statistics and summary info from the system..

30
Q

Executive users

A

more interested in strategic issues as well as daily issues

31
Q

External users

A

customers may access through internet. Suppliers may have access to check inventory and initiate billing.

32
Q

Client Stakeholders

A

Sometimes same as the executive users. May also be separate. In charge of the money

33
Q

Technical Stakeholders

A

maintain - support and provide guidance for the system

34
Q

Information Gathering Techniques-old style

A

learned existing system - extracted the logical functions - converted to new system - defined the new system - also called pave the cow paths as they basically just automate the old system

35
Q

Information Gathering Techniques-new style

A

goal is to develop a set of logical system requirements for the new system immediately while sometimes referring to the old sys

36
Q

Question Themes

A

What are the business operation sand processes (to user - what do you do) - How should those operations be performed? (to user how do you do it - what steps do you follow) - What information is needed to perform those operations (to user: what information do you use - what forms or reports do you use)

37
Q

Effective Interviews

A

Prepare for interview - conduct the interview - follow-up the interview

38
Q

Preparing for Interview

A

Determine Objective - Decide on what users to attend - Prepare detailed questions - Make final interview arrangements and communicate to all participants

39
Q

Conducting the Interview

A

Dress/time arrival - limit the time of interview - look for exception and error conditions - i.e. what ifs - take detailed notes

40
Q

Follow up the interview

A

process the info from the interview and return to interviewees to confirm the information.

41
Q

Observing

A

observing the business processes in action will help you understand the business function. Can include walk throughs or doing the task yourself

42
Q

Workflow

A

is a sequence of processing steps that completely handles one business transaction or customer request.

43
Q

Activity Diagram

A

type of workflow diagram that describes the user activities and their sequential flow

44
Q

Synchronization Bar

A

A symbol in an activity diagram to control the splitting or uniting of sequential paths

45
Q

Swimlane

A

a rectangular area on an activity diagram representing the activities of a single agent.

46
Q

Prototype

A

a preliminary working model of a larger system

47
Q

Mock-up

A

an example of a final product that is for viewing only and is not executable.

48
Q

Joint Application Design sessions or JAD

A

technique to define requirements or design a system in a single session by having all necessary people participate

49
Q

Group support system GSS

A

computer sys that allows multiple people to participate with comments at the same time from their own computer

50
Q

Research Vendor Solutions

A

Technical specifications - a demo or trial system - references of existing clients who might allow you to view their system - on site visit - print out of screens and reports

51
Q

Structured Walkthrough to validate info

A

review of the findings from your investigation and of the models built based on those findings.

IT261 Systems Design - Illinois State University (9 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2024 Bold Learning Solutions. Terms and Conditions