- Acceptance: one of four possible strategies for response planning with regard to an identified risk. - indicates the impact of the risk that can be tolerated at its identified level.. - Administrative closure: the activities of the project team necessary to collect project records, analyze proj- ect success or failure, gather lessons learned, and archive project information for future use. - Application architecture: part of the enterprise architecture that shows how the various software applica- tions interact.. - factor believed to be true but not confirmable or factor known to be true but that could change during the project.. - indicates that risk cannot be tolerated to any degree and must be prevented from having any impact on the project.. - Baseline: project’s point of reference for requirements changes. - established at the point of plan approval and should not be changed except in response to significant, approved change in the project scope.. - Business architecture: part of the enterprise architecture that shows the structure of the enterprise (that is, divisions, locations, etc.) and its product or service strategy.. - Business constraints: limitations imposed on the solution related to business activities, (i.e. - Business objective: defines why the project is important to the business and what the business needs to get from the project for the investment to be successful.. - Business requirement: stated from the viewpoint of the business function and using that terminology.. - Business risk: eventualities that could threaten the project. - positive (opportunities) or negative impacts the project could have on the business.. - Business rules: static modeling technique that looks at the rules governing business processes and decisions (regulation, company policy, etc.).. - Capability: the functionality of the specified system.. - Class model: static modeling technique that looks at representations of each entity in a system, showing the attributes and activities of each. - Communications Management: one of nine Knowledge Areas identified in the PMBOK® Guide. - Communications planning: the process of determining what information will flow into and out of the proj- ect and who wants or needs that information.. - Constraints: any limitations imposed on the project or solution. - Cost/benefit analysis: technique focused on the identification of the associated costs and the related benefits.. - Cost Management: one of nine Knowledge Areas identified in the PMBOK ® Guide. - focuses on planning, esti- mating, budgeting, and controlling costs so that the project is successful.. - Critical path: the longest path through the project network. - the sequence of activities that defines the mini- mum time required to complete the project.. - Customer: person or organization that will use the project’s product, service, or result.. - Data dictionary: static modeling technique that provides a detailed description of each data element, includ- ing its source (for primary elements) or how it is derived or computed (for composite elements).. - Data-flow diagram: dynamic modeling technique that shows how data is shared among the various activi- ties and entities in a system.. - Data transformation/mapping: static modeling technique that shows the changes data elements go through.. - Delphi: consensus-based estimating technique using anonymous inputs from the team working on the project.. - Earliest completion date: first date the project can be finished by. - determined by adding the time to com- plete all of the activities on the critical path.. - Enterprise Analysis: one of six knowledge areas identified by the BABOK. - static modeling technique that looks at the data entities in a system and how they relate to each other.. - Event identification: dynamic modeling technique that shows the events the system must respond to, and what its response should be to each.. - Executive sponsor: ultimate authority on the project.. - Expectation gap: results from clients, sponsors, and the team, each holding different views of the project.. - External dependencies: dependencies that exist between schedule activities and factors outside of the project, like the output from another project or goods and services provided by vendors.. - allow for early priority and scope management and for getting a high-level sense of the stakeholders view of the solution.. - Finish-to-finish precedence relationship: similar to start-to-start relationships, except that the point of relationship is at the end of the activity. - Float: amount of time an activity can be delayed without affecting the project end date.. - provides a basis for weighing the importance of the forces affecting the decision. - Functional design: observable behaviors of the solution. - Human Resource Management: one of nine Knowledge Areas identified by the PMBOK® Guide. - focuses on organizing and managing the project team members.. - Information architecture: part of the enterprise architecture that shows how data flows within the organization.. - Integration Management: one of nine Knowledge Areas identified by the PMBOK ® Guide. - focuses on the processes that integrate the various elements of project management that are identified, defined, combined, unified, and coordinated in the project management process groups.. - Lessons learned: identified at the end of each stage of the project and collected for cumulative analysis;. - the latest time an activity can begin without jeopardizing the project end date.. - characterized by a required order in the relationship between the activities.. - Milestone: significant point or event in the project. - point in time of significant accomplishment in the project.. - Mitigation: one of four possible strategies for response planning with regard to an identified risk. - Optional dependencies: relationships in which the project manager has some influence over the sequence of the relationship. - based on Pareto’s study of the concentration of wealth in Italy that found 80 percent of the wealth was held by 20 percent of the people.. - PMBOK ® Guide: Abbreviation for PMI’s Guide to the Project Management Body of Knowledge.. - Product metrics: based on the product scope and requirements. - Project charter: document issued by the project initiator or sponsor that formally. - authorizes the existence of a project, and provides the project manager with the authority to apply organiza- tional resources to project activities.. - Project metrics: based on the project’s goals and give insight into whether the project is likely to achieve those goals.. - Project objectives: definition of what the project will accomplish.. - Project risk: things that may impact the project’s ability to meet stakeholder expectations. - uncertainty (both positive and negative) that matters to the project.. - Quality Management: one of nine Knowledge Areas identified by the PMBOK ® Guide. - focuses on ensuring that the project will satisfy the needs for which it was undertaken.. - structure that relates the project organizational breakdown structure to the WBS to ensure that each element of the scope of work is assigned.. - Requirements Analysis and Documentation: one of six knowledge areas identified in the BABOK. - mak- ing sense of the information that is elicited, organizing it, and documenting it in appropriate forms (that is, words, tables, models, and prototypes). - identifies gaps in the information and defines the capabilities of the solution.. - Requirements Communication: one of six knowledge areas identified in the BABOK. - Requirements Elicitation: one of six knowledge areas identified by the BABOK. - Requirements planning and management: one of six knowledge areas identified by the BABOK;. - Scope: sum of the products, services, and results to be provided as a project.. - Scope exclusions: specifically indicate what work falls outside of the project boundaries.. - Scope inclusions: indicate what the project is about and what it will do.. - Scope Management: one of nine Knowledge Areas identified by the PMBOK ® Guide. - focuses on ensuring that the project includes all the work required, and only the work required, to successfully complete the project.. - Security architecture: part of the enterprise architecture that shows the security needs and practices within the organization.. - Sequence diagram: dynamic modeling technique that shows the exact steps for a specific scenario. - Sign off: formal, written approval gained throughout the project management processes at the end of a phase.. - Solution Assessment and Validation: one of six knowledge areas identified by the BABOK. - focuses on collaborating with the technical and quality assurance teams to ensure that the solution built satisfies the requirements and collaborating with business users to plan acceptance and rollout of the solution.. - Solution owner: major supplier of requirements information, and is often an approver of the requirements;. - Sponsor: person or group that provides the financial resources for the project.. - Stakeholder: persons or organizations that are actively involved in the project, or whose interests may be positively or negatively affected by execution or completion of the project, or who can exert influence in proj- ect decisions.. - State Machine Diagram: dynamic modeling technique that shows all the states the system can be in, and the possible transitions among those states.. - Technical constraints: limitations imposed on the solution related to business activities (i.e. - Technical risk: technological changes that could impact the project or technologies that may not work as expected.. - Technology architecture: part of the enterprise architecture that shows how different technologies sup- port the business.. - Time Management: one of nine Knowledge Areas identified by the PMBOK ® Guide. - focuses on ensuring that the project is completed in a timely manner.. - Transference: one of four possible strategies for response planning with regard to an identified risk. - User interface designs: usage-modeling technique that is similar to storyboards and screen flows, but used much earlier in the analysis process.. - User profile: usage-modeling technique that lists the end users of a system, including relevant attributes of each.. - User story: usage-modeling technique that is similar to use case descriptions, but with much less detail.. - deliverable-oriented, hierarchical decomposition of project elements that defines the total work scope of the project.. - Work package: deliverable or project work component at the lowest level of each branch of the WBS.. - Workflow models: dynamic modeling technique that diagrams the flow of activities among responsible parties.. - PMI, PMP, CAPM, PMBOK and the PMI Registered Education Provider logo are registered trademarks of the Project Management Institute, Inc.
Xem thử không khả dụng, vui lòng xem tại trang nguồn hoặc xem
Tóm tắt