The Systems Development Environment Flashcards

1
Q

Information Systems Analysis and Design

A

is a complex, challenging, and stimulating organizational process that a team of business and systems professionals uses to develop and maintain computer-based information systems.

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

Application software

A

Computer software designed to support

organizational functions or processes.

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

Methodologies

A

are comprehensive, multiple-step approaches to systems development
that will guide your work and influence the quality of your final product

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

Techniques

A

are particular processes that you, as an analyst, will follow to help
ensure that your work is well thought out, complete, and comprehensible to others
on your project team.

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

Tools

A

are typically computer programs that make it easy to use and benefit
from techniques and to faithfully follow the guidelines of the overall development
methodology.

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

Systems analyst

A

The organizational role most responsible
for the analysis and design of information
systems.

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

Systems development methodology

A

A standard process followed in an organization to conduct all the steps necessary to analyze, design, implement, and maintain information systems.

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

SDLC

A

Systems development life cycle (SDLC)

The traditional methodology used to develop, maintain, and replace information systems.

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

Planning

A

The first phase of the SDLC in which an organization’s total information system needs are identified, analyzed, prioritized,
and arranged.

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

Analysis

A

The second phase of the SDLC in which system requirements are studied and structured.

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

Design

A

The third phase of the SDLC in which the description of the recommended solution is converted into logical and then physical
system specifications.

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

Logical design

A

The part of the design phase of the SDLC in which all functional features of the system chosen for development in analysis are
described independently of any compute platform.

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

Physical design

A

The part of the design phase of the SDLC in which the logical specifications of the system from logical design are transformed
into technology-specific details from which all programming and system construction can be accomplished.

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

Implementation

A

The fourth phase of the SDLC, in which the information system is coded, tested, installed, and supported in the organization.

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

Maintenance

A

The final phase of the SDLC, in which an information system is systematically repaired and improved.

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

The Traditional Waterfall SDLC problems

A

1-feedback came to be ignored in implementation
2-Once the milestone had been reached and the new phase
initiated, it became difficult to go back
3-locking users into requirements that had been previously determined, even though those requirements might have changed.
4-role of system users or customers was narrowly defined.
5-under the traditional waterfall approach, nebulous and intangible
processes such as analysis and design are given hard-and-fast dates for completion

17
Q

CASE tools

A

computer-aided software engineering

Software tools that provide automated support for some portion of the systems development process.

18
Q

AGILE Methodologies Key principles

A

(1) a focus on adaptive rather than predictive methodologies,
(2) a focus on people rather than roles
(3) a focus on self-adaptive processes.

19
Q

RAD

A

Rapid Application Development
Decreases design and implementation time
Involves: extensive user involvement, prototyping, integrated CASE tools, code generators
More focus on user interface and system function, less on detailed business analysis and system performance

20
Q

extreme programming

A

extreme Programming is an approach to software development. Key emphases of extreme Programming :
are its use of two-person programming teams, described later, and having a customer
on-site during the development process

21
Q

advantages of pair programming

A

(1) more (and better) communication among developers,
(2) higher levels of productivity,
(3) higher-quality code
(4) reinforcement of the other practices in extreme Programming, such as the code and- test discipline

22
Q

object-oriented analysis and design (OOAD)

A

Systems development methodologies and techniques based on objects rather than data or processes.

23
Q

Object

A

A structure that encapsulates (or packages) attributes and methods that operate on those attributes. An object is an abstraction of a real-world thing in which data and processes are placed together to model the structure and behavior of the real-world object.

24
Q

Object class

A

a logical grouping of objects sharing the same attributes and behaviors

25
Q

Inheritance

A

: hierarchical arrangement of classes enable subclasses to inherit properties of super classes

26
Q

Rational Unified Process (RUP)

A
An object-oriented systems development
methodology. RUP establishes four phases
of development: inception, elaboration,
construction, and transition. Each phase
is organized into a number of separate
iterations.
27
Q

inception phase

A

analysts define the scope, determine the feasibility of
the project, understand user requirements, and prepare a software development
plan.

28
Q

elaboration phase

A

analysts detail user requirements and develop a base

line architecture

29
Q

construction phase

A

software is actually coded, tested, and documented

30
Q

transition phase

A

the system is deployed, and the users are trained and supported.