Chapter 9
Project stakeholder
Individuals and organizations actively involved in the project or whose interests might be affected as a result of project execution or project completion
waterfall methodology
A sequence of phases in which the output of each phase becomes the input for the next
prototype
A smaller-scale representation or working model of the users' requirements or a proposed design for an information system
Agile Methodology
Aims for customer satisfaction through early and continuous delivery of useful software components developed by an iterative process using the bare minimum requirements
project management office (PMO)
An internal department that oversees all organizational projects
Project deliverable
Any measurable, tangible, verifiable outcome, result, or item that is produced to complete a project or part of a project
Extreme programming (XP) methodology
Breaks a project into tiny phases, and developers cannot continue on to the next phase until the first phase is complete
Scrum
Uses small teams to produce small pieces of deliverable software using sprints, or 30-day intervals, to achieve an appointed goal
Work Breakdown Structure (WBS)
a plan that breaks down a project's goals into the many deliverables required to achieve it
Outsourcing
an arrangement by which one organization provides a service or services for another organization that chooses not to perform them in-house
legacy system
an old system that is fast approaching or beyond the end of its useful life within an organization
Iterative Development
consists of a series of tiny projects
software customization
modifies software to meet specific user or business requirements
feature creep
occurs when extra features are added to a project
Scope Creep
occurs when the scope of the project increases
Off-the-shelf application software
supports general business processes and does not require any specific software customization to meet the organization's needs
Conversion
the process of transferring information from a legacy system to a new system
the prototype is an essential part of the analysis phase when using a RAD methodology
true
in-sourcing(in house development)
uses the professional expertise within an organization to develop and maintain its information technology systems
rapid application development methodology (RAD)
Emphasizes extensive user involvement in the rapid and evolutionary construction of working prototypes of a system to accelerate the systems development process
Design Phase
Establishes descriptions of the desired features and operations of the system including screen layouts, business rules, process diagrams, pseudo code, and other documentation
testing phase
Involves bringing all the project pieces together into a special testing environment to eliminate errors and bugs, and verify that the system meets all of the business requirements defined in the analysis phase
maintenance phase
Involves performing changes, corrections, additions, and upgrades to ensure the system continues to meet its business goals
implementation phase
Involves placing the system into production so users can begin to perform actual business operations with it
Development Phase
Involves taking all of the detailed design documents from the design phase and transforming them into the actual system
Rational Unified Process (RUP)
Provides a framework for breaking down the development of software into four gates 1) inception 2) elaboration 3) construction 4) transition
SMART goals
Specific, Measurable, Attainable, Relevant, Timely(useful reminders on ensuring a project has understandable objectives)
Executive sponsor
The person or group who provides the financial resources for the project
