Unit 4 Flashcards

1
Q

Project Identification and Selection

A

Projects are triggered when someone sees an opportunity to create business value (cost reduction, new products and services, improved productivity) from using information technology.

Users of Current System
IT/MIS group
Top Management
Externally imposed

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

System Request

Lists key elements of the project

A
Lists key elements of the project
Project name
Project sponsor
Business need (Symptoms)
Functionality (Objectives)
Expected value
Special issues or constraints (Scope)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Confirming Project Feasibility

A
Technological feasibility
CanWe Build It?
Economic feasibility
ShouldWe Build It?
Organizational and cultural feasibility
If we build it, will they come?
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Systems Analysis Activities

A

Gather Detailed Information about current system

Interviews, questionnaires, documents, observing business processes, researching vendors, comments and suggestions
Model the current (As-is) System
Analyze the Model to identify solutions to problems
Define Requirements
functional requirements and non-functional requirements
Develop a model for the proposed (to-be) system
Prepare a functional specification document

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

What Are Requirements?

A

System Requirements =
Functional requirements
Non-functional requirements

Functional Requirements–the activities the system must perform
Business uses, functions the users carry out

Non-Functional Requirements–other system characteristicsConstraints and performance goals

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

FURPS+ Requirements Acronym

A
Functional requirements
Usability requirements
Reliability requirements
Performance requirements
Security requirements
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Look at FURPS+ Requirements Acronym Diagram

A

Do it

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

Information Gathering

A

1background information such as company’s overall objectives, goals, organization structure etc.

  1. employees, their duties and responsibilities within the unit.
  2. processes performed, process triggers, who performs those activities, what inputs/data are used, sources of inputs/data, how they are used, what outputs are produced, where those outputs are sent, who uses the outputs
  3. the sequence of processes
  4. volume and frequency of data and processes
  5. controls over input, process, and output.
  6. system boundaries
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Information-Gathering Methods

A

Review existing reports, forms, and procedure descriptions
Interview and discuss processes with users
Observe and document business processes
Build prototypes
Distribute and collect questionnaires
Conduct joint application design (JAD) sessions

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

Review Existing Reports, Forms, and Procedure Descriptions

A

Source: External industry-wide professional organizations and trade publications

Source: Existing business documents and procedure descriptions within organization

Identify business rules, discrepancies, and redundancies
Obtain preliminary understanding of processes
Use as guidelines/visual cues to guide interviews
Look for user additions to forms/reports
Look for unused form/report elements

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

Conduct Interviews and Discussions with Users

A

Effective way to understand business functions and rules
Time consuming and resource expensive
May require multiple sessions to
Meet all users
Understand all processing requirements
Can meet with individuals or groups of users
List of detailed questions prepared

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

Observe and Document Business Processes

A

Varies from office walkthroughs to performing actual tasks
Not necessary to observe all processes at same level of detail
May make users nervous, so use common sense

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

Build Prototypes

A

Preliminary working model of a larger, more complex system component
Discovery, design, evolving prototypes
Prototype should be
Operative •Working model to provide “look and feel”
Focused to accomplish single objective
Quick•Built and modified rapidly with CASE tools

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

Distribute and Collect Questionnaires

A

Limited and specific information from a large number of stakeholders
Preliminary insight into business
Confirm understanding of the system with large user base
Not well suited for gathering detailed process information

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

Joint Application Design

A

Session leader trained in group dynamics and JAD group facilitation
Knowledgeable business and system users and policy makers
Technical staff representatives to handle
Computer and network configurations
Operating environments
Security issues
Project team members

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

Look at A JAD Facility Diagram

A

DO IT