Chapter 5 Notes | IST 445 - Managing Information Systems Projects, Quizzes of Information Technology

terms Class: IST 445 - Managing Information Systems Projects; Subject: Information Studies; University: Syracuse University; Term: Spring 2010;

Typology: Quizzes

Pre 2010

Uploaded on 02/05/2010

tmorioka
tmorioka 🇺🇸

9 documents

1 / 5

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
TERM 1
analogy approach
DEFINITION 1
creating a WBS by using a similar project's WBS as a starting
point
TERM 2
bottom-up approach
DEFINITION 2
creating a WBS by having a team members identify as many
specific tasks related to the project as possible and then
grouping them into higher level categories.
TERM 3
decomposition
DEFINITION 3
subdividing project deliverables into smaller pieces
TERM 4
deliverable
DEFINITION 4
a product, such as a report or segment of software code,
produced as part of a project
TERM 5
Joint Application Design
DEFINITION 5
using highly organized and intensive workshops to bring
together project stakeholders - the sponsor, users, business
analysis, programmers, and so on - to jointly define and
design information systems
pf3
pf4
pf5

Partial preview of the text

Download Chapter 5 Notes | IST 445 - Managing Information Systems Projects and more Quizzes Information Technology in PDF only on Docsity!

analogy approach

creating a WBS by using a similar project's WBS as a starting point TERM 2

bottom-up approach

DEFINITION 2 creating a WBS by having a team members identify as many specific tasks related to the project as possible and then grouping them into higher level categories. TERM 3

decomposition

DEFINITION 3 subdividing project deliverables into smaller pieces TERM 4

deliverable

DEFINITION 4 a product, such as a report or segment of software code, produced as part of a project TERM 5

Joint Application Design

DEFINITION 5 using highly organized and intensive workshops to bring together project stakeholders - the sponsor, users, business analysis, programmers, and so on - to jointly define and design information systems

project scope management

the processes involved in defining and controlling what work is or is not included in a project TERM 7

project scope statement

DEFINITION 7 a document that includes, at a minimum, a description of the project, including its overall objectives and justification, detailed descriptions of all project deliverables, and the characteristics and requirements of products and services products as part of the project. TERM 8

prototyping

DEFINITION 8 developing a working replica of the system or some aspect of the system to help define user requirements TERM 9

requirement

DEFINITION 9 a condition or capability that must be met or possessed by a system, product, service, result , or component to satisfy a contract, standard, specification, or other formal document TERM 10

requirements management plan

DEFINITION 10 a plan that describes how project requirements will be analyzed, documented, and managed

use case modeling

a process for identifying and modeling business events, who initiated them, and how the system should respond to them. TERM 17

variance

DEFINITION 17 the difference between planned and actual performance TERM 18

WBS dictionary

DEFINITION 18 a document that describes detailed information about each WBS item TERM 19

work breakdown structure

DEFINITION 19 a deliverable-oriented grouping of the work involved in a project that defines the total scope of the project TERM 20

work package

DEFINITION 20 a task at the lowest level of the WBS