Chapter 1 Flashcards

1
Q

What is SDLC?

A

The systems development life cycle (SDLC) is the process of understanding how an information system (IS) can support business needs by designing a system, building it, and delivering it to users.

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

What is a systems analyst?

A

The key person in the SDLC is the systems analyst, who analyzes the business situation, identifies opportunities for improvements, and designs an information system to implement them.

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

What are the 4 fundamental phases of SDLC?

A

planning, analysis, design, and implementation

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

What is the planning phase?

A

The planning phase is the fundamental process of understanding why an information system should be built and determining how the project team will go about building it.

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

What is project initiation?

A

Identifying the system’s business value to the organization

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

What is a system request?

A

A system request presents a brief summary of a business need, and it explains how a system that supports the need will create business value.

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

Feasibility analysis

A

The feasibility analysis examines key aspects of the proposed project:

The idea’s technical feasibility (Can we build it?)
The economic feasibility (Will it provide business value?)
The organizational feasibility (If we build it, will it be used?)

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

What is project management?

A

During project management, the project manager creates a workplan, staffs the project, and puts techniques in place to help the project team control and direct the project through the entire SDLC.

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

What is a project plan

A

The deliverable for project management is a project plan, which describes how the project team will go about developing the system.

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

2 steps of planning

A

project initiation and project management

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

What is the analysis phase?

A

The analysis phase answers the questions of who will use the system, what the system will do, and where and when it will be used. During this phase, the project team investigates any current system(s), identifies opportunities for improvement, and develops a concept for the new system.

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

3 steps of analysis

A

analysis strategy, requirements gathering, system proposal

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

What is analysis strategy?

A

An analysis strategy is developed to guide the project team’s efforts. Such a strategy usually includes an analysis of the current system (called the as-is system) and its problems and then ways to design a new system (called the to-be system).

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

What is requirements gathering?

A

interviews or questionnaires

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

What are business analysis models?

A

describe how the business will operate if the new system is developed. The set of models typically includes models that represent the data and processes necessary to support the underlying business process.

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

What is a system proposal?

A

The analyses, system concept, and models are combined into a document called the system proposal, which is presented to the project sponsor and other key decision makers (e.g., members of the approval committee) who decide whether the project should continue to move forward.

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

What is the design phase?

A

The design phase decides how the system will operate, in terms of the hardware, software, and network infrastructure; the user interface, forms and reports; and the specific programs, databases, and files that will be needed.

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

What steps are in the design phase?

A

Design strategy, architecture design, database and file specifications, and program design.

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

What is design strategy?

A

It clarifies whether the system will be developed by the company’s own programmers, whether the system will be outsourced to another firm (usually a consulting firm), or whether the company will buy an existing software package.

19
Q

What is architecture design?

A

Describes the hardware, software, and network infrastructure to be used.

20
Q

What is interface design?

A

specifies how the users will move through the system (e.g., navigation methods such as menus and on-screen buttons) and the forms and reports that the system will use.

21
Q

What are database and file specifications?

A

These define exactly what data will be stored and where they will be stored.

22
Q

What is program design?

A

defines the programs that need to be written and exactly what each program will do

23
Q

What is system specification?

A

This collection of deliverables (architecture design, interface design, database and file specifications, and program design) is the system specification that is handed to the programming team for implementation.

24
Q

What is the implementation phase?

A

The final phase in the SDLC is the implementation phase, during which the system is actually built (or purchased, in the case of a packaged software design).

25
Q

What steps are in the implementation phase?

A

construction, installation, support plan

26
Q

What is construction?

A

The system is built and tested to ensure it performs as designed.

27
Q

What is installation?

A

Installation is the process by which the old system is turned off and the new one is turned on.

28
Q

What is a training plan?

A

to teach users how to use the new system and help manage the changes caused by the new system.

29
Q

What is a support plan?

A

This plan usually includes a formal or informal post-implementation review as well as a systematic way for identifying major and minor changes needed for the system.

30
Q

What is a methodology?

A

A methodology is a formalized approach to implementing the SDLC (i.e., it is a list of steps and deliverables).

31
Q

Process -centred methodology

A

A process-centered methodology emphasizes process models as the core of the system concept.

32
Q

Data-centered methodology

A

Data-centered methodologies emphasize data models as the core of the system concept.

33
Q

Object-oriented methodology

A

object-oriented methodologies attempt to balance the focus between process and data by incorporating both into one model.

34
Q

What are the different classes of system development methodologies?

A

structured design, rapid application development, and agile development.

35
Q

What are the structured design methodologies?

A

Waterfall Development and Parallel Development

36
Q

What is waterfall development?

A

the analysts and users proceed in sequence from one phase to the next. The key deliverables for each phase are typically very long (often hundreds of pages in length) and are presented to the project sponsor for approval as the project moves from phase to phase. Once the sponsor approves the work that was conducted for a phase, the phase ends and the next one begins.

37
Q

2 key advantages of waterfall development

A

it identifies system requirements long before programming begins and it minimizes changes to the requirements as the project proceeds.

38
Q

2 key disadvantages of waterfall development

A

the design must be completely specified before programming begins and that a long time elapses between the completion of the system proposal in the analysis phase and the delivery of the system (usually many months or years).

39
Q

What is parallel development?

A

Parallel development methodology attempts to address the problem of long delays between the analysis phase and the delivery of the system. Instead of doing design and implementation in sequence, it performs a general design for the whole system and then divides the project into a series of distinct subprojects that can be designed and implemented in parallel. Once all subprojects are complete, the separate pieces are integrated and the system is delivered

40
Q

Advantage of parallel development

A

it can reduce the time to deliver a system; thus, there is less chance of changes in the business environment causing rework.

41
Q

Disadvantages of parallel development

A

the approach still suffers from problems caused by paper documents. It also adds a new problem: Sometimes the subprojects are not completely independent; design decisions made in one subproject can affect another, and the end of the project can require significant integration efforts.

42
Q

What is Rapid Application Development (RAD)?

A

RAD-based methodologies attempt to address both weaknesses of structured design methodologies by adjusting the SDLC phases to get some part of the system developed quickly and into the hands of the users. In this way, the users can better understand the system and suggest revisions that bring the system closer to what is needed

43
Q

Advantage of RAD-based methodology

A

The combination of the changed SDLC phases and the use of these tools and techniques improves the speed and quality of systems development

44
Q

Disadvantage of RAD-based methodology

A

Owing to the use of the tools and techniques that can improve the speed and quality of systems development, user expectations of what is possible can change dramatically. As a user better understands the information technology (IT), the systems requirements tend to expand. This was less of a problem when using methodologies that spent a lot of time thoroughly documenting requirements.

45
Q

3 RAD categories

A

Phased Development, Prototyping, Throwaway Prototyping

46
Q
A