1systems development life cycle
A methodology for the design and implementation of an information system, which may contain different phases depending on the methodology deployed, but generally addresses the investigation, analysis, design, implementation, and maintenance of an information system.
2methodology
A formal approach to solving a problem based on a structured sequence of procedures.
3waterfall model
A type of SDLC in which each phase of the process “flows from” the information gained in the previous phase, with multiple opportunities to return to previous phases and make adjustments.
4software assurance
A methodological approach to the development of software that seeks to build security into the development life cycle rather than address it at later stages.
5project management
The process of identifying and controlling the goals, objectives, tasks, scheduling, and resources of a project.
6project plan
The documented instructions for participants and stakeholders in a project that provide details on its goals, objectives, tasks, scheduling, and resource management.
7work breakdown structure (WBS)
A list of the tasks to be accomplished in a project, the skill sets or individual employees needed to perform the tasks, the start and end dates for tasks, the estimated resources required, and the dependencies among tasks.
8projectitis
A situation in project planning in which a project manager spends more time manipulating and adjusting aspects of the project management software than accomplishing meaningful project work.
9gap analysis
The process of comparing measured results against expected results and then using the resulting “gap” as a measure of project success and as feedback for project management.
10direct changeover conversion strategy
The conversion strategy that involves stopping the old system and starting the new one without any overlap.
11phased implementatin conversion strategy
The conversion strategy that involves a measured rollout of the planned system; only part of the system is brought out and disseminated across an organization before the next piece is implemented.
12pilot implementation conversion strategy
The conversion strategy that involves implementing the entire system into a single office, department, or division and dealing with issues that arise before expanding to the rest of the organization.
13parallel operations conversion strategy
The conversion strategy that involves running the new system concurrently with the old system.
14bull's-eye model
A method for prioritizing a program of complex change that requires issues to be addressed from the general to the specific and focuses on systematic solutions instead of individual problems.
15technology governance
A process that organizations use to manage the effects and costs of technology implementation, innovation, and obsolescence.
16change control
A method of regulating the modification of systems within the organization by requiring formal review and approval for each change.