Term
|
Definition
| describes software development cycle for a particular project by enumerating the places or stages of the project and breaking each into tasks or activities to be done |
|
|
Term
|
Definition
| the items that the customers expects to see during the project development |
|
|
Term
|
Definition
| part of development that takes place over a period of time |
|
|
Term
|
Definition
| a completion of an activity |
|
|
Term
|
Definition
| depicts the project as a set of pieces of work |
|
|
Term
|
Definition
| an event or set of events that must occur before the activity can begin; it describes the set of conditions that allows the activity to begin |
|
|
Term
|
Definition
| length of time needed to complete the activity |
|
|
Term
|
Definition
| date by which the activity must be completed, frequently determined by contractual deadlines |
|
|
Term
|
Definition
| usually milestone or deliverable |
|
|
Term
|
Definition
| the nodes of a graph are the project milestones, and the lines linking the nodes represent the activities involved |
|
|
Term
| Critical path method (CPM) |
|
Definition
| analyzing the paths among the milestone |
|
|
Term
|
Definition
| the estimated amount of time required for an activity to be completed |
|
|
Term
|
Definition
| the amount of time available in the schedule for the activity’s completion |
|
|
Term
|
Definition
| the difference between the available time and the real time |
|
|
Term
|
Definition
| depiction of the project where the activities are shown in parallel, with the degree of completion indicated by color or icon |
|
|
Term
|
Definition
| people who tell others their thoughts |
|
|
Term
|
Definition
| people who ask for suggestions from others before forming an opinion |
|
|
Term
|
Definition
| basing decision on feelings about and emotional reactions to a problem |
|
|
Term
|
Definition
| deciding primarily by examining facts and carefully considering all options |
|
|
Term
|
Definition
| one person is totally responsible for a system’s design and development |
|
|
Term
|
Definition
| everyone is held equally responsible |
|
|
Term
|
Definition
| unwanted event that has negative consequences |
|
|
Term
|
Definition
| understand and control the risks on their projects |
|
|
Term
|
Definition
| loss associated with a risk |
|
|
Term
|
Definition
| likelihood of the risk measured 0 (impossible) to 1 (certainty). |
|
|
Term
|
Definition
| a risk that is certain to happen. |
|
|
Term
|
Definition
| set of actions taken to reduce or eliminate a risk |
|
|
Term
|
Definition
| quantifying the effects of the risks |
|
|
Term
|
Definition
| common to all software projects |
|
|
Term
|
Definition
| threats that result from the particular vulnerabilities |
|
|
Term
|
Definition
| the assurance that existing functionality still works correctly |
|
|
Term
|
Definition
| the difference in risk exposure divided by the cost of reducing risk |
|
|
Term
|
Definition
|
|
Term
|
Definition
| a document of project details |
|
|
Term
|
Definition
| engineer belonged to a functional unit based on a type of skill |
|
|
Term
| Integrated product development |
|
Definition
| combining individuals from different functional groups into an interdisciplinary work unit |
|
|
Term
|
Definition
| common measure for comparing progress on different activities |
|
|
Term
|
Definition
| amount of time one person spends working on a software development project for one month |
|
|
