ch.12- Systems development: Investigation and analysis Flashcards

1
Q

• Systems Design Life Cycle (SDLC) method- 5 phases in developing information systems:

A
  1. Investigation
    2. Analysis
    3. Design
    4. Implementation
    5. Maintenance and review
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

stakeholders

A

PPL in organization who themselves or through org. they represent benefit from the systems development project

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

USers

A

ppl who interact with the system regularly

○ Employees, managers, suppliers

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

systems analyst

A

professional who specializes in analyzing and designing business systems
○ Play various roles while interacting with the stakeholders and users, mgmt, vendors, suppliers, external companies, programmers, other IS support personnel

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

programmer

A

specialist responsible for modifying or developing programs to satisfy user requirements
○ Takes plans from systems analyst and builds or modifies necessary software

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

individual systems developper

A

person who performs all the systems development roles- systems analyst, programmer, technical specialist, etc….
○ Can create applications for group or entire org.
○ May specialize in developing applications for individuals (apps for smartphones etc…)

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

individual users

A

acquire applications for both personal and professional use.

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

end user systems development

A

And systems development project in which the primary effort is undertaken by combination of business managers and users

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

Information systems planning

A

translating strategic and organizational goals in to systems development initiatives

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

creative analysis

A

investigation of new approaches to existing problems.

Looking at problems in new or different ways, introducing innovative methods to solve them

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

critical analysis

A

unbiased and careful questioning of whether system elements are related I the most effective ways
○ Critical analysis in systems development involves:
§ Questioning statements
§ Identifying and resolving objectives and orientations that conflict

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

mission critical system

A

systems that play pivotal role in an org. continued operations and goal attainment

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

critical success factors (CSF)

A

factors that are essential to the success of a functional area of an org.

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

SYSTEMS INVESTIGATION

A

-problems/ opportunities identified

○ Considered in light of the goals of the business

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

SYSTEMS ANALYSIS

A

study of existing systems and work processes to identify strengths , weaknesses and opportunities for improvement

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

SYSTEMS DESIGN

A

how the information system will do what it must do to obtain solution
- ○ Details systems outputs, inputs, user interfaces
○ Specifies hardware, software, database, telecommunications, personnel, procedure components and shows how these components are related

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

SYSTEMS IMPLEMENTATION

A

Creation or acquisition of various system components detailed in the system design, assembling them, and placing the new modified systems in to operation

  • ○ To train the users
    ○ Results in installed, operational information system that meets business needs.

Can also involve phasing out/ removing old system.

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

SYSTEMS MAINTENANCE AND REVIEW

A

: ensures the system operates , modifies system so it continues to meet changing business needs

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

PROTOTYPING

A

iterative approach to the systems development process
○ At each iteration requirements and alternative solutions identified and analyzed, new solutions are designed, portion of the systems is implemented.

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

PROTOTYPING- CLASSIFICATIONS (2)

A

§ Operational: prototype that works

§ Non- operational: a mock up or model that incl input and output specifications

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

Rapid application development (RAD)

A

system development approach that employs tools, techniques, and methodologies designed to speed application development.

  • ○ Can also be used to make systems development projects more flexible and agile to be able to rapidly change with changing conditions ad environments
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
22
Q

AGILE DEVELOPMENT

A

requires cooperation and frequent face to face meetings with all participants

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

EXTREME PROGRAMMING (XP)

A

uses pairs of programmers who work together to design, test, code parts of the systems they develop

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

ADAPTIVE SOFTWARE DEVELOPMENT (ASD)

A

grew out of rapid application development

○ Stresses iterative process that involves analysis, design, implementation at each cycle iteration

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
25
Leab software development
comes from lean manufacturing ○ Stresses continuous learning, just in time decision making, empowering systems development teams, and elimination of waste
26
RATIONAL UNIFIED DEVELOPMENT (RUP)
○ Uses iterative approach to software development that stresses quality as the software is changed and updated over time.
27
FEATURE DRIVEN DEVELOPMENT (FDD)
iterative systems development approach that stresses the features of new or modified system, - developing overall model, - creating list of features, - planning by features, - designing by features, - building by features
28
CRYSTAL METHODOLOGIES
-family of systems development approaches, -concentrates on effective team work, reduction of paper work, bureaucracy to make development projects faster and more efficient.
29
PROJECT SCHEDULE
detailed description of what is to be done
30
PROJECT MILESTONE
critical date for completion of major part of the project
31
PROJECT DEADLINE
date the entire project is to be completed and operational
32
CRITICAL PATH
activities that , if delayed, would delay entire project
33
Program Evaluation and Review Technique
- formalized approach for developing project schedule - 3 estimates for an activity: shortest , most likely, longest possible time -
34
GANTT CHART
graphical tool used for planning, monitoring, coordinating projects
35
COMPUTER AIDED SOFTWARE ENGINEERING (CASE)
automate many of the tasks req in a systems development effort and encourage adherence to SDLC
36
Upper case tools
provide automated tools to assist with systems investigation, analysis, design activities
37
lower case tools
focus on the later implementation stage so systems development, automatically generate program code
38
Object oriented systems development (OOSD)
approach to systems development | ○ combines logic of systems development life cycle with the power of object oriented modelling and programming
39
SYSTEM REQUEST FORM
document filled out by someone that wants IS department to initiative system investigations. ○ Helps rationalize and prioritize the activities of IS department
40
FEASIBILITY ANALYSIS
assessment of technical, economic, legal, operational, and schedule feasibility pf project.
41
TECHNICAL FEASIBILITY
assessment of whether the hardware, software, and other systems components can be acquired or developed to solve the problem.
42
ECONOMIC FEASIBILITY
determination of whether the project makes financial sense and whether predicted benefits offset the cost and time needed to obtain them.
43
LEGAL FEASIBILITY
determination of whether laws or regulations may prevent or limit a system development project
44
OPERATIONAL FEASIBILITY
measure whether the project can be put in to action or operation.
45
SCHEDULE FEASIBILITY
determination of whether the project can be completed in a reasonable amount of time
46
SYSTEMS INVESTIGATION REPORT
Summary of the results of the systems investigation + process of feasibility analysis and recommendation of a course of action.
47
STEERING COMMITTEE
Advisory group consisting of senior mgmt and users from IS department and other functional areas. - ○ Helps IS personnel with their decisions about use of information systems
48
STRUCTURED INTERVIEWS
questions written in advance
49
UNSTRUCTURED INTERVIEWS
questions not written in advance
50
DIRECT OBSERVATION
directly observing the existing system in action by one or more members of the analysis team -discover how data flows
51
QUESTIONNAIRES
-Method of gathering data when the data sources spread over a wide geographic area. ○ Can be structured or unstructured
52
STATISTICAL SAMPLING
selecting random sample of data and applying the characteristics of the sample to the whole group. ○ Assume the sample applies to entire population
53
DATA ANALYSIS
Manipulation of collected data so that the development team members who are participating in systems analysis can use the data -
54
DATA FLOW DIAGRAM
model of objects, associations, activities, that describes how data can flow between and around various objects
55
DATA FLOW LINE
arrows that show the direction of data element movement
56
PROCESS SYMBOL
represents function that is performed
57
ENTITY SYMBOL
source or destination of data element
58
DATA STORE
storage location for data
59
APPLICATION FLOW CHARTS
diagrams that show relationships among applications or systems
60
GRID CHART
table that shows relationships among the various aspects of a systems development effort. ○ Shows which applications use common databases
61
CASE REPOSITORY
database of system descriptions, parameters, objectives
62
REQUIREMENTS ANALYSIS
determination of user, stakeholder, org. needs
63
ASKING DIRECTORY
approach to gather data that asks users, stakeholders, other managers about what they want in and expect from new modified system
64
SCREEN LAYOUT
technique that allows designer to quickly and efficiently design the features, layout, and format of a display screen More data for infrequent users; less data for freq users
65
REPORT LAYOUT
allows designers to diagram and format printed reports