SDLC Flashcards

1
Q

What does SDLC stand for

A

Systems (or in some sources, Software) Development Life Cycle

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

This refers to the process of developing software through business needs, analysis, design, implementation and maintenance. Software has to go through various phases before it is born which are as follows:

A

SDLC

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

The SDLC focuses on the ____, _____, and ______ for building and/or implementing the IT solution.

A

software engineering phases, processes, tools and techniques

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

According to Satzinger et al, ______ is a systematic approach to solving business problems

A

SDLC

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

_____ involves identifying and responding to a problem or opportunity and incorporates the project management and system development processes and activities.

A

Planning

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

a formal ______ process ensures that the goal, scope, budget, schedule, technology, and system development processes, methods, and tools are in

A

Planning

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

__________ attempts to delve into the problem or opportunity more fully

A

Analysis

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

Analysis: For example, the project team may document the current system to develop an _____ model to understand the system currently in place.

A

“as is”

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

Analysis: Systems analysts will meet with various stakeholders (users, managers, customers, etc.) to learn more about the problem or opportunity. This work is done to ______________ or bottlenecks associated with the current

A

identify and document any problems

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

Analysis: Requirements can be developed through a number of means— ______

A

interviewing, joint applications development (JAD), conducting surveys, observing work processes, and reading company

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

Analysis: Using modeling techniques, the current system, user requirements, and logical design of the future system called the ___ system are represented and documented

A

“to be”

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

what is the purpose of Analysis?

A

To analyze the business situation thoroughly to determine and structure the requirements and to select between competing system features.

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

What is the deliverable in Analysis?

A

The functional specifications for a system that meets user requirements and is feasible to develop and implement

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

The project team uses the requirements and “to be” logical models as input for designing the architecture to support the new information system

A

Design

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

This phase is concerned with how the system functionality is to be provided by the components of the system.

A

Design

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

Design: Analyze the requirements and organize them into related groups.

A

Partition requirements

17
Q

Design: ______ that can individually or collectively meet the requirements.

A

Identify sub-systems

18
Q

Design: Limitations of externally purchased sub- systems may mean that you have to change the requirements to accommodate these constraints.

A

Assign requirements to sub-systems

19
Q

Design: You should specify the specific functions provided by each sub-system. You should also try to identify relationships between sub-systems at this stage.

A

Specify sub-system functionality.

20
Q

Design: Define the interfaces that are provided and required by each sub-system.

A

Define sub-system

21
Q

Includes the development or construction of the system, testing, and installation

A

Implementation

22
Q

Implementation: Three stages of System Testing

A

Unit Testing, System Testing, Acceptance Testing

23
Q

Implementation: individual programs are separately tested

A

Unit Testing

24
Q

Implementation: the entire system as a whole is tested to determine whether program modules are interacting as planned

A

System testing

25
Q

Implementation: the system undergoes final certification by the end-users to ensure that it is ready for installation.

A

Acceptance Testing

26
Q

Four Strategies of Implementation

A

Direct Cutover, Parallel Strategy, Pilot Stategy, Phased Approach

27
Q

Implementation: The old system is terminated and the new system takes over as the system of record without any traditional period. This approach is rapid but very risky since there is no other system to fall back on in the event of errors. Costs of corrections are potentially enormous.

A

Direct Cutover

28
Q

Implementation: Run the old system and the new in tandem until it can be ascertained that the new system performs correctly. This is a safe but expensive and operationally time-consuming strategy. Two systems must be monitored, compared and coordinated.

A

Parallel Strategy

29
Q

Implementation: Introduce the new system to only one part of the organization. Install the pilot when validated, in stages or simultaneously to the rest of the organization. This strategy is safer than direct cutover but somewhat more risky than a parallel strategy. There may be no fallback system when the pilot is installed in the rest of the organization, and it takes time to install and evaluate the pilot before converting the rest of the organization.

A

Pilot Strategy

30
Q

Implementation: Introduce the new system in stages. This approach is safer than direct cutover but somewhat more risky than a parallel strategy. There may be no fallback for the parts of the system that are first installed. There is no way to validate beforehand how the system performs as a whole.

A

Phased Approach

31
Q

Maintenance and Support: Once the system has been implemented, it is said to be in production and becomes a _____

A

legacy system

32
Q

Changes to the system, in the form of maintenance and enhancements, are often requested to fix any discovered errors (i.e., bugs) within the system, to add any features that were not incorporated into the original design, or to adjust to a changing business environment.

A

Maintenance and Support