C954 - Section 4: IT Projects and Processes

0.0(0)
studied byStudied by 0 people
GameKnowt Play
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
Card Sorting

1/47

encourage image

There's no tags or description

Looks like no tags are added yet.

Study Analytics
Name
Mastery
Learn
Test
Matching
Spaced

No study sessions yet.

48 Terms

1
New cards

maintenance phase

In this phase, the organization performs changes, corrections, additions, and upgrades to ensure the system continues to meet business goals

2
New cards

prototyping

An experimental process where design teams implement ideas into tangible forms from paper to digital; increases the chance for successful implementation as well as the chance of detecting errors early on

3
New cards

preventative maintenance

Makes a system change to reduce the chance of future system failures

4
New cards

methodology

A set of policies, procedures, standard processes, practice tools, and techniques that people apply to TECO management challenges

5
New cards

waterfall methodology

A sequence of phases in which the output of each phase becomes the input for the next

6
New cards

discovery prototyping

Building a small-scale representation or working model of the system to ensure it meets the user and business requirement

7
New cards

iterative development

Consist of a series of tiny projects

8
New cards

agile methodology

Achieves customer satisfaction through early and continual delivery of useful software components; developed by an iterative process with design points that use the bare minimum requirement to produce working code or function

9
New cards

rapid application development (RAD)

Also called rapid prototyping methodology; emphasizes extensive user involvement in the rapid and evolutionary construction of a working prototype of a system to accelerate the system's development process

10
New cards

extreme program (XP) methodology

It breaks a project into tiny phases; developers cannot continue to the next phase until the first phase is completed

11
New cards

Rational Unified Process (RUP) methodology

Provides a framework for breaking down the development of software into four or five phases

12
New cards

scrum methodology

Uses small teams to produce small pieces of deliverable software, using sprints or 30-day intervals to achieve an appointed goal

13
New cards

web service

An open-standard way of supporting the interoperability of technology systems.

14
New cards

cascading style sheet (CSS)

A markup language for web documents containing structured information

15
New cards

loose coupling

The capability of services to be joined on demand

16
New cards

service-oriented architecture (SOA)

A business-driven enterprise architecture that supports integrating a business as linked repeatable activities task or service

17
New cards

service-oriented architecture (SOA) service

A business task, such as checking a potential customer's credit rating, when opening a new account

18
New cards

tangible benefit

Easy to quantify and typically measure to determine the success or failure of a project

19
New cards

intangible benefits

Benefits that are difficult to quantify or measure

20
New cards

kill switch

A trigger that enables a project's manager to close the project prior to completion

21
New cards

feasibility

The measure of the tangible and intangible benefit of an information system

22
New cards

program evaluation and review technique (PERT) charg

A graphical network model that depicts a project's tasks and the relationship between those tasks

23
New cards

dependency

A series of tasks that are interrelated, such as the logical relationship that exists between a project task and a milestone

24
New cards

critical path

The longest stretch of dependent activities, which are measure from start to finish

25
New cards

testing phase

Involves bringing all the project pieces together into a special testing environment to test for errors, bugs, and interoperability and to verify that the system meets the business requirements defined in the analysis phase

26
New cards

bug

Defects in the code of an information system

27
New cards

test condition

The detailed steps the system must perform along with the expected results of each step

28
New cards

implementation phase

Placing the system into production so users can begin to perform actual business operations with the system

29
New cards

user documentation

Documents that include how to use the system and troubleshoot issues or problems

30
New cards

online training

Training delivered via the Internet in order to allow employees to complete the materials at their own pace

31
New cards

workshop training

Held in a classroom environment and led by an instructor

32
New cards

help desk

A group of people who respond to internal system user questions

33
New cards

Gantt chart

A simple bar chart that lists project tasks vertically against the projects time frame listen horizontially

34
New cards

in-sourcing, in-house development

A common approach using the professional expertise within and organization to develop and maintain the organization's information technology systems

35
New cards

outsourcing

It is an arrangement by which one organization provides services for another organization that chooses not the perform them in-house. Benefits include cost savings and extended work resources. Drawbacks include a loss of corporate knowledge and confidentiality.

36
New cards

onshore outsourcing

The process of engaging another company within the same country for services

37
New cards

nearshore outsourcing

Contracting an outsourcing agreement with a company in a nearby country

38
New cards

offshore outsourcing

Using organizations from developing countries to write code and develop systems

39
New cards

communication plan

It defines the how, what, when, and who in the flow of project information to stakeholders. It is key for managing expectations

40
New cards

executive sponsor

The person or group who provides the financial resources for the project

41
New cards

project constraint

A specific factor that can limit options within a project

42
New cards

project assumption

A factor that is considered to be true, real, or certain without proof or demonstration

43
New cards

project deliverable

Any measurable, tangible, and verifiable outcome, result, or item that is produced to completed a project or part of a project.

44
New cards

project management office (PMO)

An internal department that oversees all organizational projects

45
New cards

project milestone

Represents key dates when certain groups of activities must be performed

46
New cards

project objective

Quantifiable criteria that must be met for the project to be considered a success

47
New cards

project requirements

Defines the specification for product output of the project document and is key for managing expectations, controlling scope, and completing other planning efforts

48
New cards

project scope statement

Identifies the resources, timeline, and outcomes for the project; includes statements on how the project supports the organization's business goals