M1S2 System Development Cycle Flashcards

1
Q

Methodologies or set of activities that analysts,designers, and users carry out to develop and implement information system.

A

System Development Life Cycle

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

SDLC

A

System Development Life Cycle

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

Why is it necessary to follow a specific methodology in system development?

A

To develop high quality or effective information systems.
To accomplish information systems on time.

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

The basis for the candidate system to recognize the need to improve an information system or a procedure.

A

Project Selection

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

Top management, the user, the analyst, or someone within the organization may feel the need to update existing applications or improve procedures.

A

Problem Definition

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

Environment-based ideas from the customers, vendors, government, sources, and the like.

A

Impetus for System Change

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

Force of change

A

Impetus

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

Two Sources of System Ideas

A

Organization based
Environment based

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

Major Sources of Change

A

OTUS GCUC

Organization-based

Organization
Top Management
User
System Analyst

Environment Based

Government
Consumer
Union
Competition

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

Five Stages of SDLC

A

Planning
Analysis
Design
Implementation
Testing and Integration/ Deployment and Maintenance/ Support

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

Obtain approval for the project, initiate, assess feasibility, plan, and schedule

A

Planning Stage

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

Also known as the feasibility stage

A

Planning Stage

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

Planning Stage outputs

A

Feasibility Report, Project Schedule.

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

Output of Analysis Stage

A

Software Requirement SpecificationDocument

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

Understanding business needs and processing needs

A

Analysis Stage

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

A document containing the system’s software, hardware, and network requirements.

A

SRS Document

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

Transform the SRS document into a logical structure.

A

Design Stage

15
Q

Define solution system based on requirement and analysis decisions and processing needs

A

Design Stage

16
Q

Conceptual frameworks and models.

A

Design Stage

16
Q

Create a contingency, training, maintenance, and operation plan.

A

Design Stage

17
Q

Output of Design Stage

A

Design Document
Design Specification Document

18
Q

Construct and implement the design into source code through coding.

A

Implementation Stage

19
Q

Coding, software product and compilers

A

Implementation Stage

20
Q

Integrate the information system into its environment and install the new system

A

Testing and Deployment/Integration Stage

20
Q

Combine all the modules into a training environment that detects errors and defects

A

Testing and Deployment/Integration Stage

21
Q

Keeps the system healthy and improve

A

Maintenance/Support Stage

22
Q

contains errors is prepared through a test plan that includes test-related tasks such as test case generation, testing criteria, and resource allocation for testing.

A

test report

23
Q

Output of Testing and Deployment/Integration Stage

A

Test Report

24
Q

A system project may be dropped at any time before implementation

A

Project Termination

25
Q

Becomes more difficult (and costly) when it goes past the design phase

A

Project Termination

26
Q

Projects are dropped after a review process

A

Project Termination

27
Q

During this phase, the system’s threats, constraints, integration, and security are also considered.

A

Planning Stage

28
Q

Overview of the new system and determine its objectives.

A

Planning Stage

29
Q

Define the problem and scope of the existing system.

A

Planning Stage

30
Q

Gather, analyze, and validate the information.

A

Analysis Stage

31
Q

examine the information needs of end-users and enhance the system goal.

A

Analysis Stage

31
Q

Define the requirements and prototypes for the new system.

A

Analysis Stage

32
Q

Include all the activities such as phone support or physical on-site support for users that are required once the system is installed.

A

Maintenance/Support

33
Q

Implement the changes that software might undergo over a period of time or implement any new requirements after the software is deployed at the customer location.

A

Maintenance/Support

34
Q

It also includes handling the residual errors and resolving any issues that may exist in the system even after the testing phase.

A

Maintenance/Support

35
Q

Maintenance and support may be needed for a longer time for large systems and for a short time for smaller systems.

A

Maintenance/Support