Midterm 1 Flashcards

1
Q

What are the 5 stages of the System Development Life Cycle

A

Planning, Analysis, Design, Implementation, and Maintenance

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

What is the role of a systems analyst?

A

They are the bridge between organizational problem and a technical solution

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

Which SDLC phases may be addressed by a “systems analyst”.

A

the first 2-3 phases (planning, analysis, and design)

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

Desired Characteristics of a Systems Analyst:

A

Good combo of business and technical knowledge

good communication skills

can work well in a team

open to learning

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

Explain the Planning stage of SDLC:

A

Identify potential projects

Feasibility of the project

see how well the potential project fits the company strategy.

Approval for project

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

Explain the Analysis Stage of SDLC: (big question???)

A

The big question: what?

document system requirements

find where it can be built (in-house, outsource, or buy/rent a pre-built system)

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

Explain the Design Stage of SDLC: (big question???)

A

The Big Question: How???

how are we going to organize the data
how do users interact with the system
how are we going to make the system requirements a reality

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

Explain the Implementation Stage of SDLC:

A

Write the software/build the system

test the system

training/Education

get the system deployed out to the company

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

Explain the Maintenance Stage of SDLC:

A

Upgrade hardware
tweaks to software
feedback from users

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

What are the subphases of the planning stage of SDLC?

A
  1. Project ID and Selection (3 steps)
  2. Project initiation and planning (4 steps)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Planning Phase: Project ID and Selection

A

1: identify potential projects for further review
2: classify and rank potential IS projects
(gain a basic understanding of each project and perform a screening assessment of each project).
3: select potential IS project(s)
(only projects that have the most potential to help the organization make the first cut. select projects for further consideration).

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

What types of feasibility issues are explored during Planning?

A

Economic- do we have the money?
Technical- does the software exist? can the hardware handle it?
Operational- strategic fit (business strategy)? operational fit (how comfortable are people?
Scheduling- can we get it done by the time we need it to be.
Political- will the company culture be ok with this change?

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

Planning Phase: Project Initiation and Planning

A

1: conduct a more detailed evaluation of the selected proposed IS project(s).
(business requirements “mini analysis”, costs, benefits, risks, resource management)

2: Assess feasibility: economic, technical, operational fit, scheduling, political.

3: present findings to the decision makers. “go/no go decision”. (standard review format).

4: If the project gets approval, prepare a detailed plan for project (scheduling, staffing, project management).

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

What is the objective of the analysis phase?

A

conduct a very detailed “analysis”

find out exactly what the users want the system to do.

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

What are the deliverables of the analysis phase:

A

detailed set of user requirements

recommended approach for system acquisition

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

What is the orientation of the analysis phase?

A

business-oriented

15
Q

What are the key activities of the analysis stage:

A
  1. fact-finding
  2. document/communicate user requirements
  3. clarification/Revision (review findings with users, modify?
  4. investigate alternatives for system acquisition.
16
Q

What are the components of a DFD?

A

Processes
Data Flows
Data Stores
External Entities outside the system.

17
Q

What is a Context DFD:

A

“top level” dfd
only one process system (“black box”)
shows inputs and outputs of system

18
Q

What is a Level - 0 DFD?

A

decomposes the Context DFD

shows high-level details inside the “black box: of the context process.

Depicts the major processes and data store(s) of system

19
Q

Construction Steps of a Context DFD

A

Step 1: process symbol (round rectangle labeled 0- use the full name of the system)

Step 2: External Entities (generic names- i.e. customer, restaurant manager, etc)

Step 3: Data flows (use the generic name to describe the packet of data, simple, no verb)

Step 4: Diagram Information (Context DFD: Name of system, Prepared by: Version #1, Date)

20
Q

Construction Steps of a Level 0- DFD

A

Step 1: Process symbols (for each major sub-component of the system) (use verb-object name, update inventory, etc. NO MORE THAN 7).

Step 2: External Entities (generic names- i.e. customer, restaurant manager, etc) (SAME AS CONTEXT DFD)

Step 3: Data flows- make sure data flow labels are consistent. add data flows between processes.

Step 4: Data stores- add data stores and flows into and out. Describe the data in the store, not how it is stored (inventory file (good) vs black file cabinet (bad)). D1, D2, etc.

Step 5: Diagram Information (Level-0 DFD: Name of system, Prepared by: Version #1, Date).

21
Q

Definition of DFD Decomposition

A

Break DFD processes into smaller, more detailed pieces.

22
Q

DFD Decomposition: Functional Primitive:

A

Process that requires no decomposition

Designate a FP with a “*” or a “P” at the end of process label

23
Q

DFD Decomposition: Functional Primitive: When do we stop decomposing?

A

“one page” guideline: can process be described in one page or less?

Decomposition stops when all processes decomposed to FPs.

24
Q

How many levels should a dfd have? (dfd decomposition?)

A

depends on the complexity of system

How many levels should we expect?
Small system= 2-3 levels
Medium system = 3-6 levels
Large system= 5-8 levels

25
Q

How to show levels of a dfd decomposition to a user?

A

usually top down, start with context, then level -0, level -1, etc.

26
Q

What are the values of DFDs:

A

supports communication
user friendly
provides structure to the project
helps analysts and users better understand the system processes
etc.

27
Q

what are the limitations of DFDs:

A

may not always show sequencing of processing

do not indicate timing of processing

specifics about processing logic with functional primitives is not provided.

Specifics about the data components in data flows and data stores are not provided.

28
Q

Definition of Structured English:

A

Modified form of English

Similar to pseudocode, but more user oriented

Ex. Conditional statement, repetition.

29
Q

Structured English Conventions:

A

Concise Sentences

Pay attention to format and layout

mathematical operations are allowed (=,+)

use terms that are consistent with DFDs and project dictionary.

30
Q

Process Specification: Background

A

describes procedures associated with a functional primitive. (other names: mini-specification, transform description).

31
Q

Key requirements of a process specification:

A

key requirements must be expressed in a form that can be:

verified by the user and analyst
communicated effectively to a varied audience

SHOULD BE ONE PAGE OR LESS

32
Q

What does a process specification describe?

How many pages should each process specification take up?

Where are the process specifications saved?

A

the logic “inside” a functional primitive

one page

project dictionary.