Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

Introduction to IT > Section 7 > Flashcards

Section 7 Flashcards

1
Q

What is IT governance

A

the system of processes that ensures the effective and efficient use of IT to enable an organization to achieve its business goals and to add value to key stakeholders in an organization

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

What are the 4 phases of the project management life cycle

A

initiation, planning, execution, and closure.

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

What happens in the project initiation phase of the PM life cycle

A

usually begins with a business case followed by a feasibility study. stakeholders provide input in the analysis of the business case and feasibility study which results in a initiation document that outlines the business needs, the stakeholders, and the business case

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

What happens in the project planning phase of the PM life cycle

A

This phase starts with setting the project goals, commonly using the SMART or CLEAR frameworks and defines the project scope and drafts a PM plan

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

What happens in the project execution phase of the PM life cycle

A

Tasks typically include developing the project team, assigning resources, setting up tracking systems, conducting status meetings, and monitoring the project timetable. Performance is constantly monitored.

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

What happens in the project closure phase of the PM life cycle

A

project is declared complete and the project team is dissolved.

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

What are risks in execution during PM

A

typically revolve around budget, people, technology, equipment, and stakeholder support.

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

What are risks of integration after a project is completed

A

the project is not successfully integrated into employee workflow

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

Scope creep - PM

A

uncontrolled change of a project’s scope, typically adding tasks and increased, unplanned costs to the project

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

Budget risk - PM

A

budget control issues, such as underestimated or improper allocation of cost

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

Resistance to change - PM

A

departments and individuals resist organizational changes resulting from the project

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

Resource risk - PM

A

inability to secure sufficient resources for the project

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

Contract risk - PM

A

a vendor fails to deliver on contractual obligations

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

Project dependencies - PM

A

especially when completion of some tasks is dependent on the completion of other tasks

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

Project assumptions risk - PM

A

when assumptions about the project are invalidated during project development

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

Benefit shortfall - PM

A

the project meets the requirements but delivers fewer benefits than outlined in the business case

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

Requirements quality risk - PM

A

requirements have not been properly validated or documented

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

Force majeure risk - PM

A

the chance of a major negative event beyond human control, such as a natural disaster

19
Q

What is requirements analysis in PM

A

starts with a feasibility study or a market study to determine if the project is feasible or valid. it describes the system that will be created and what it should do

20
Q

What is a system requirement specification (SRS)

A

a written agreement between all parties that records the system requirements and guides system development. organizations such as IEEE and large systems clients, such as the U.S. Department of Defense, have adopted standards for requirement specifications.

21
Q

What happens during the implementation phase of the SDLC

A

when the system is built - including such things as developing programs and databases and creating data files.

22
Q

What are the steps of the SDLC

A

requirements analysis, design, implementation, testing, development, use, maintenance

23
Q

what happens during the system maintenance phase of the SDLC

A

the system is monitored, evaluated, and modified as needed. System maintenance is a continuous phase that covers a wide variety of activities, including troubleshooting application errors and incompatibilities, updating documentation, and providing end-user support.

24
Q

What are the 4 primary categories of software maintenance

A

corrective, adaptive, perfective, and preventive

25
Q

what is corrective maintenance

A

to remove errors to ensure functionality of the system.

26
Q

what is adaptive maintenance

A

when organizational changes affect system requirements, such as changes in the organizational procedures, forms, or system controls and security needs.

27
Q

what is perfective maintenance

A

performed when new components are introduced, or existing components are improved, to enhance overall system performance.

28
Q

what is preventive maintenance

A

refers to changes made to increase the life span of systems and could include restructuring, optimizing code, or updating documentation that impacts the scalability, stability, and maintainability of the system.

29
Q

what is the Pareto principle

A

based on the theory that 80% of errors come from 20% of the system, meaning most errors can be identified by testing carefully selected groups of samples.

30
Q

What is white-box testing

A

having developers test internal structures of software.

31
Q

What is black-box testing and what are the methodologies

A

focused on the user experience (UX). alpha testing, beta testing, user acceptance testing

32
Q

What happens during alpha testing

A

developers and/or an internal UX team test a preliminary version of the software, providing feedback about performance and functionality.

33
Q

what happens during beta testing

A

the system is given to a segment of end users for similar testing from their perspective before the final version is released.

34
Q

what happens during user acceptance testing

A

users test the system in an operational setting to make sure the system continues to align with business objectives and meet the goals of the stakeholders.

35
Q

what are the 3 types of system documentation

A

user documentation, system documentation, and technical documentation

36
Q

what does user documentation consist of

A

explains the system to users and may include information such as how to access certain features, frequently asked questions (FAQs), and contact information for customer support.

37
Q

what does system documentation consist of

A

describes the system’s internal configuration so the system can be maintained later in its life cycle.

38
Q

what does technical documentation consist of

A

describes how to install and maintain the system, including information about installing updates and providing feedback to the development team.

39
Q

what is the waterfall model of system engineering

A

following the development process sequentially: first requirements analysis, then design and implementation, and finally testing. Each step needed to be finished before moving on to the next.

40
Q

what is prototyping

A

building and evaluating basic versions of a proposed system.

41
Q

What is the Scrum system/methodology

A

an agile framework for PM

  1. The system owner makes a prioritized wish list.
  2. The scrum team selects an item toward the top of the wish list and plans the implementation during an event called “sprint.”
  3. The team completes the list of objectives while assessing progress in daily meetings called scrums.
  4. The sprint ends with the system ready to be released.
  5. A new sprint starts, using another item on the wish list.
  6. This process continues until the prioritized wish list is clear.
42
Q

what is the extreme programming (XP) model

A

systems are developed by a team of fewer than a dozen individuals working in a communal workspace, where they freely share ideas and assist each other in the development project.

43
Q

What is the purpose of a business continuity plan

A

To enable an organization to continue offering critical services in the event of disruptions

44
Q

What is mobile computing

A

the use of handheld devices, such as laptops, smartphones, and tablets.

Introduction to IT (7 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2024 Bold Learning Solutions. Terms and Conditions