Enterprise Architecture Quarter

Product Design Quarter (hereinafter, the Quarter) is the third of four lectures of Project Quadrivium (hereinafter, the Quadrivium):

• The Quarter is designed to introduce its learners to enterprise design, or, in other words, to concepts related to creating architecture for achieving enterprise goals; and
• The Quadrivium examines concepts of administering various types of enterprises known as enterprise administration as a whole.

The Quadrivium is the first of seven modules of Septem Artes Administrativi, which is a course designed to introduce its learners to general concepts in business administration, management, and organizational behavior.

Lecture outline

The predecessor lecture is Business Analysis Quarter.

Concepts

• Feature. A cohesive bundle of externally visible functionality that should align with business goals and objectives. Each feature is a logically related grouping of functional requirements or non-functional requirements described in broad strokes.

1. Product. A solution or component of a solution that is the result of a project.
   • Product vision statement. A brief statement or paragraph that describes the why, what, and who of the desired software product from a business point of view.
   • Product backlog. A set of user stories, requirements or features that have been identified as candidates for potential implementation, prioritized, and estimated.
   • Product scope. The features and functions that characterize a product, service or result.

• Agile development.
• System. A set of interrelated and interdependent parts arranged in a manner that produces a unified whole.
• Open system. A system that interacts with its environment.
• Closed system. A system that is not influenced by and does not interact with its environment.

1. Systems engineering.
   • Datapoint-device architecture.
   • Configuration management.
2. Informational architecture.
   • Graphic design.
   • Usability.
   • UX design.

• Action design. A change process based on systematic collection of data and then selection of a change action based on what the analyzed data indicate.
• Commitment concept. Plans should extend for enough to meet those commitments made when the plans were developed.
• Load chart. A modified Gantt chart that schedules capacity by entire departments or specific resources.
• Organizational development. A collection of planned change interventions, built on humanistic-democratic values, that seeks to improve organizational effectiveness and employee well-being.
• Organizational development. Change methods that focus on people and the nature and quality of interpersonal work relationships.
• Process. An action that individuals, groups, and organizations engage in as a result of inputs and that leads to certain outputs.

1. • Output. An immediate and direct result of a process.

• Statement of work (SOW). A narrative description of products or services to be supplied under contract.

1. • Statement of work (SOW). A formal document that defines the entire scope of the work that shall be completed in order to implement the proposed change.

• Input. A variable that leads to processes.

Practices

• Abstraction. The ability of engineers to think of design concepts that are not dependent on specific solutions.
• Boundary. A separation between the interior of a system and what lies outside.
• Context. The users, other systems and other features of the environment of the system that the system will interact with.
• Customer. The organization or individual that has requested (and will pay for) a product or service.
• Engineering. The application of scientific principles to practical ends.
• Feedback. Information about the output of a system that can be used to adjust it.
• Gantt Chart. A project management tool in the form of a bar chart showing the start and finish dates of activities.
• Input. A material, service or support item that is processed by the system.
• Interdisciplinarity. People from different disciplines working together to design systems.
• Lifecycle. Important phases in the development of a system from initial concept through design, testing, use, maintenance, to retirement.
• Mission. An undertaking that is supported by the system to be designed to be successful (e.g. space mission).
• Optimization. The process of choosing the best alternative that will satisfy the needs of the stakeholders under the constraints given (e.g. cost, schedule and available technology).
• Output. What is produced by a system.
• Process. A set of activities used to convert inputs into desired outputs.
• Project. An activity having goals, objectives, a beginning and an end.
• Requirement. A statement of required behavior, performance and other characteristics of the system to be developed.
• Risk Management. A process of identifying what can go wrong and making plans that will enable a system to achieve its goals.
• Specifications. The technical requirements for systems design.
• Stakeholder. An individual or group affected in some way by the undertaking. Stakeholders are valuable sources for requirements.
• System. A set of interrelated components working together to produce a desired result.
• Systems Approach. The application of a systematic disciplined engineering approach that considers the system as a whole, its impact on its environment and continues throughout the lifecycle of a project.
• System Design. The identification of all the necessary components, their role, and how they have to interact for the system to fulfill its purpose.
• System Integration. The activity of integrating all the components of a system to make sure they work together as intended.
• Systems Engineering. The orderly process of bringing a system into being using a systems approach.
• Trade-off. losing one quality or aspect of something in return for gaining another quality or aspect.
• Value. The benefit enjoyed by the stakeholders of the system when the system is in operation.
• Validation. Testing to insure that the created system actually provides the value intended to its stakeholders. (Did we build the right system?).
• Verification. The process of proving that a finished product meets specifications and requirements. (Did we build the system right?)
• 3-Click Rule. A theory of website navigation prevalent in the early 2000s suggesting that a user of a website should be able to find any information with no more than three mouse clicks or they would leave out of frustration. It’s now widely accepted as nonsense; usability studies disprove the theory’s link to user satisfaction or success rates and instead link these to ‘information scent’.
• 5 Second Test. As the name suggests, the 5-Second Test involves showing users a single content page for a quick 5 seconds. The aim is to gather a participant’s initial impressions and assess the screen’s clarity and conciseness using simple questions like "What is the most important information on the page?" or "How would you go about achieving your goal on this screen?". The setup is similar to a standard usability test, and may sometimes be combined with one.
• Adaptive web design. Like Responsive web design it is an approach to web design aimed at crafting sites to provide an optimal viewing and interaction experience on different screen and devices. The difference is that adaptive design is less fluid then RWD, and ‘serves’ few fixed width versions of the design depending on viewport size. It can utilise server side techniques to ‘detect’ viewport size prior to rendering html. The advantage for designer is that it gives more control over images and typography, and hence is easier approach to ‘retrofit’ fixed width websitest to work on mobile devices.
• Affinity diagramming. A business tool used to organise a large number of ideas, sorting them into groups based on their natural relationships, for review and analysis.
• Agile software development methodology. A methodology fundamentally incorporating iteration and continuous feedback to refine and deliver a software system. It involves continuous planning, testing, integration, and other forms of continuous evolution of both the project and the software.
• Analysis stage. The stage of the UX process where insights are drawn from data collecting during the earlier Research stage. Capturing, organising and making inferences from the “what” can help UX designers begin to understand the “why”.
• Analytics. A broad term that encompasses a variety of tools, techniques and processes used for extracting useful information or meaningful patterns from data.
• Axure. A wireframing and interactive prototyping tool, available for both Windows and Mac.
• Balsamiq Mockups. A wireframing and interactive prototyping tool, available for both Windows and Mac.
• Beta launch. The limited launch of a software product with the goal of finding bugs before final launch.
• Branding. The process of creating and marketing a consistent idea or image of a product, so that it is recognisable by the public.
• Card sorting. A technique using either actual cards or software, whereby users generate an information hierarchy that can then form the basis of an information architecture or navigation menu.
• Content Management System (CMS). Software that allows publishing, editing and maintaining content from a central interface. See also: Content management
• Collaborative design. Inviting input from users, stakeholders and other project members.
• Competitor analysis. Performing an audit or conducting user testing of competing websites and apps; writing a report that summarises the competitive landscape.
• Comparative analysis. Performing an item by item comparison of two or more websites or apps to determine trends or patterns.
• Content management. The suite of processes and technologies that support the collection, management, and publication of information in any medium.
• Contextual enquiry. Interviewing users in the location that they use the website or app, in order to understand their tasks and challenges.
• Content audit. Reviewing and cataloguing a client’s existing repository of content.
• Customer Journey Map. an holistic, visual representation of your users’ interactions with your organisation when zoomed right out (usually captured on a large canvas). See also: Experience Map
• Design stage. The stage in a user-centred design process where ideas for potential solutions are captured and refined visually, based on the analysis and research performed in earlier stages.
• Diary Study. Asking users to record their experiences and thoughts about a product or task in a journal over a set period of time.
• Experience Map. An experience map is an holistic, visual representation of your users’ interactions with your organisation when zoomed right out (usually captured on a large canvas). See also: Customer Journey Map
• Heuristic review. Evaluating a website or app and documenting usability flaws and other areas for improvement.
• Human Computer Interaction (HCI). HCI involves the study, planning, and design of the interaction between people (users) and computers.
• High-fidelity prototype. A prototype which is quite close to the final product, with lots of detail and a good indication of the final proposed aesthetics and functionality.
• Human factor. Also called ergonomics. The scientific discipline of studying interactions between humans and external systems, including human-computer interaction. When applied to design, the study of human factors seeks to optimise both human well-being and system performance.
• Industrial design. The application art and science to a product, in order to improve its aesthetics, ergonomics, functionality, and usability.
• Information architecture (IA). The art and science of organising and labeling websites, intranets, online communities and software to support usability.
• Information scent. An important concept in information foraging theory referring to the extent to which users can predict what they will find if they persue a certain path through a website. As animals rely on scents to indicate the chances of finding food, so do humans rely on various cues in the information environment to acheieve their goals.
• Interaction design (IxD). Sometimes referred to as IxD, interaction design strives to create meaningful relationships between people and the products and services that they use.
• Interaction model. A design model that binds an application together in a way that supports the conceptual models of its target users. It defines how all of the objects and actions that are part of an application interrelate, in ways that mirror and support real-life user interactions.
• Iterate. The act of repeating a process with the aim of approaching a desired goal, target or result. Each repetition of the process is also called an iteration.
• Iterative design. A methodology based on a cyclic process of prototyping, testing, analysing, and refining a product or process. Based on the results of testing the most recent iteration of a design, changes are made. This process is intended to ultimately improve the quality and functionality of a design.
• Lean UX. Inspired by Lean and Agile development theories, Lean UX speeds up the UX process by putting less emphasis on deliverables and greater focus on the actual experience being designed.
• Low-fidelity prototype. A quick and easy translation of high-level design concepts into tangible and testable artefacts, giving an indication of the direction that the product is heading.
• Mood Board. A collage, either physical or digital, which is intended to communicate the visual style a direction is heading.
• Needfinding. Needfinding is the art of talking to people and discovering their needs—both those they might explicitly state, and those hidden beneath the surface. It is only in truly understanding people that we can gain meaningful insights to inspire and inform a final, impactful design.
• Paper prototype. A rough, often hand-sketched, drawing of a user interface, used in a usability test to gather feedback. Participants point to locations on the page that they would click, and screens are manually presented to the user based on the interactions they indicate.
• Personas. A fictitious identity that reflects one of the user groups for who you are designing.
• Production stage. The stage at which the high-fidelity design is fleshed out, content and digital assets are created, and a high-fidelity version of the product is validated with stakeholders and end-users through user testing sessions. The role of the UX Designer shifts from creating and validating ideas to collaborating with developers to guide and champion the vision.
• Project kick-off. The formally recognised start of a project.
• Progressive disclosure. An interactive design technique that helps maintain the focus of a user’s attention by reducing clutter, confusion, and cognitive workload. It improves usability by presenting only the minimum data required for the task at hand. The principle is also used in journalism’s ‘inverted pyramid’ style, learning’s ‘spiral approach’, and the game ‘twenty questions’.
• Prototype. A rough guide for the layout of a website or app, giving an indication of the direction that the product is heading.
• Questionnaires. A research instrument consisting of a series of questions and other prompts for the purpose of gathering information from respondents.
• Red route. The frequent and critical activities that users will perform on your site. They are complete activities, not single tasks, and will probably require several pages to execute. Defining the red routes for your site means that you’ll be able to identify and eliminate any usability obstacles on the key user journeys. (Important roads in London are known as ‘red routes’ and Transport for London do everything in their power to make sure passenger journeys on these routes are completed as smoothly and quickly as possible.)
• Research stage. Often referred to as the Discovery stage. Complex projects will comprise significant user and competitor research activities, while small projects may require nothing more than some informal interviews and a survey.
• Responsive design. A design approach that responds to the user’s behavior and environment based on screen size, platform and orientation. The practice consists of a mix of flexible grids and layouts, images and an intelligent use of CSS media queries.
• Scenario. A narrative describing “a day in the life of” one of your personas, and probably includes how your website or app fits into their lives.
• Service design. The practice of designing a product according to the needs of users, so that the service is user-friendly, competitive and relevant to the users.
• Silverback app. Usability testing software (Mac-only)
• Sitemap. A complete list of all the pages available on a website.
• Strategy stage. The stage during which the brand, guiding principles, and long-term vision of an organisation are articulated. The strategy underpinning a UX project will shape the goals of the project—what the organisation is hoping to achieve with the project, how its success should be measured, and what priority it should have in the grand scheme of things.
• Storyboard. A tool inspired by the filmmaking industry, where a visual sequence of events is used to capture a user’s interactions with a product. Depending on the audience, it may be an extremely rough sketch, purely for crystallising your own ideas.
• Survey. An online form designed to solicit feedback from current or potential users.
• Stakeholder Interviews. Conversations with the key contacts in the client organisation funding, selling, or driving the product.
• Technical communication. The practice of creating easily accessible information for a specific audience.
• Usability. Is the ease of use and learnability of an object, such as a book, software application, website, machine, tool or any object that a human interacts with.
• Usability engineering. The practice of assessing and making recommendations to improve the usability of a product.
• User-centred design (UCD). A design process during which the needs of the user is considered at all times. Designers consider how a user is likely to use the product, and they then test the validity of their assumptions in real world tests with actual users.
• User feedback loop. Ideas are put in front of users, who provide their feedback, which is used to refine the design, and then the process repeats.
• User journey. The step by step journey that a user takes to reach their goal.
• User interview. Used for understanding the tasks and motivations of the user group for whom you are designing, user interviews may be formally scheduled, or just informal chats.
• User research. Observation techniques, task analysis, and other feedback methodologies which are used to focus on understanding user behaviors, needs, and motivations.
• Usability test. A user sits in front of your website or app and you have them perform tasks and think out loud while doing so.
• Visual design. Also called communication design. A discipline which combines design and information development in order to develop and communicate a media message to a target audience.
• Waterfall model of software development. A sequential design process where progress is seen as flowing steadily downwards through the phases of Conception > Initiation > Analysis > Design > Construction > Testing > Implementation > Maintenance.
• Wireframe. A rough guide for the layout of a website or app, either done with pen and paper or with wireframing software.
• Workflow diagram. A graphical representation of activities and actions conducted by users of a system. (Sometimes called an activity diagram.)
• Activity diagram. A model that illustrates the flow of processes and/or complex use cases by showing each activity along with information flows and concurrent activities. Steps can be superimposed onto horizontal swimlanes for the roles that perform the steps.
• Activity. A unit of work performed as part of an initiative or process.
• Association. A link between two elements or objects in a diagram.
• Assumption. Assumptions are influencing factors that are believed to be true but have not been confirmed to be accurate.
• Attribute. A data element with a specified data type that describes information associated with a concept or entity.
• Benchmarking. A comparison of a process or system's cost, time, quality, or other metrics to those of leading peer organizations to identify opportunities for improvement.
• Brainstorming. Brainstorming is a team activity that seeks to produce a broad or diverse set of options through the rapid and uncritical generation of ideas.
• Business analysis approach. The set of processes, templates, and activities that will be used to perform business analysis in a specific context.
• Business analysis communication plan. A description of the types of communication the business analyst will perform during business analysis, the recipients of those communications, and the form in which communication should occur.
• Business analysis plan. A description of the planned activities that the business analyst will execute in order to perform the business analysis work involved in a specific initiative.
• Business architecture. A subset of the enterprise architecture that defines an organization's current and future state, including its strategy, its goals and objectives, the internal environment through a process or functional view, the external environment in which the business operates, and the stakeholders affected by the organization's activities.
• Business case. An assessment of the costs and benefits associated with a proposed initiative.
• Business constraint(s). Business constraints are limitations placed on the solution design by the organization that needs the solution. Business constraints describe limitations on available solutions, or an aspect of the current state that cannot be changed by the deployment of the new solution. See also technical constraint.
• Business domain model. A conceptual view of all or part of an enterprise focusing on products, deliverables and events that are important to the mission of the organization. The domain model is useful to validate the solution scope with the business and technical stakeholders. See also model.
• Business event. A system trigger that is initiated by humans.
• Business goal. A state or condition the business must satisfy to reach its vision.
• Business policy. A business policy is a non-actionable directive that supports a business goal.
• Business process. A set of defined ad-hoc or sequenced collaborative activities performed in a repeatable fashion by an organization. Processes are triggered by events and may have multiple possible outcomes. A successful outcome of a process will deliver value to one or more stakeholders.
• Business rule(s). A business rule is a specific, actionable, testable directive that is under the control of the business and supports a business policy.
• Capability. A function of an organization that enables it to achieve a business goal or objective.
• Cardinality. The number of occurrences of one entity in a data model that are linked to a second entity. Cardinality is shown on a data model with a special notation, number (e.g., 1), or letter (e.g., M for many).
• Change control board (CCB). A small group of stakeholders who will make decisions regarding the disposition and treatment of changing requirements.
• Change-driven methodology. A methodology that focuses on rapid delivery of solution capabilities in an incremental fashion and direct involvement of stakeholders to gather feedback on the solution's performance.
• Class. A descriptor for a set of system objects that share the same attributes, operations, relationships, and behavior. A class represents a concept in the system under design. When used as an analysis model, a class will generally also correspond to a real-world entity.
• Class model. A type of data model that depicts information groups as classes.
• Code. A system of programming statements, symbols, and rules used to represent instructions to a computer.
• Commercial-off-the-shelf software (COTS). Software developed and sold for a particular market.
• Competitive analysis. A structured process which captures the key characteristics of an industry to predict the long-term profitability prospects and to determine the practices of the most significant competitors.
• Constraint. A constraint describes any limitations imposed on the solution that do not support the business or stakeholder needs.
• Context diagram. An analysis model that illustrates product scope by showing the system in its environment with the external entities (people and systems) that give to and receive from the system.
• Cost-benefit analysis. Analysis done to compare and quantify the financial and non-financial costs of making a change or implementing a solution compared to the benefits gained.
• Data dictionary. An analysis model describing the data structures and attributes needed by the system.
• Data entity. A group of related information to be stored by the system. Entities can be people, roles, places, things, organizations, occurrences in time, concepts, or documents.
• Data flow diagram (DFD). An analysis model that illustrates processes that occur, along with the flows of data to and from those processes.
• Data model. An analysis model that depicts the logical structure of data, independent of the data design or data storage mechanisms.
• Decision analysis. An approach to decision-making that examines and models the possible consequences of different decisions. Decision analysis assists in making an optimal decision under conditions of uncertainty.
• Decision table. An analysis model that specifies complex business rules or logic concisely in an easy-to-read tabular format, specifying all of the possible conditions and actions that need to be accounted for in business rules.
• Decision tree. An analysis model that provides a graphical alternative to decision tables by illustrating conditions and actions in sequence.
• Decomposition. A technique that subdivides a problem into its component parts in order to facilitate analysis and understanding of those components.
• Defect. A deficiency in a product or service that reduces its quality or varies from a desired attribute, state, or functionality. See also requirements defect.
• Deliverable. Any unique and verifiable work product or service that a party has agreed to deliver.
• Desired outcome. The business benefits that will result from meeting the business need and the end state desired by stakeholders.
• Dialog hierarchy. An analysis model that shows user interface dialogs arranged as hierarchies.
• Dialog map. An analysis model that illustrates the architecture of the system's user interface.
• Domain. The problem area undergoing analysis.
• Domain subject matter expert (SME). A person with specific expertise in an area or domain under investigation.
• Enterprise. An organizational unit, organization, or collection of organizations that share a set of common goals and collaborate to provide specific products or services to customers.
• Enterprise architecture. Enterprise architecture is a description of an organization’s business processes, IT software and hardware, people, operations and projects, and the relationships between them.
• Entity-relationship diagram. An entity-relationship diagram is a graphical representation of the entities relevant to a chosen problem domain, the relationships between them, and their attributes.
• Evaluation. The systematic and objective assessment of a solution to determine its status and efficacy in meeting objectives over time, and to identify ways to improve the solution to better meet objectives. See also metric, indicator and monitoring.
• Event. An event is something that occurs to which an organizational unit, system, or process must respond.
• Event response table. An analysis model in table format that defines the events (i.e., the input stimuli that trigger the system to carry out some function) and their responses.
• Evolutionary prototype. A prototype that is continuously modified and updated in response to feedback from users.
• External interface. An interface with other systems (hardware, software, and human) that a proposed system will interact with.
• Feasibility study. An evaluation of proposed alternatives to determine if they are technically possible within the constraints of the organization and whether they will deliver the desired benefits to the organization.
• Fishbone diagram. A diagramming technique used in root cause analysis to identify underlying causes of an observed problem, and the relationships that exist between those causes.
• Force field analysis. A graphical method for depicting the forces that support and oppose a change. Involves identifying the forces, depicting them on opposite sides of a line (supporting and opposing forces) and then estimating the strength of each set of forces.
• Glossary. A list and definition of the business terms and concepts relevant to the solution being built or enhanced.
• Impact analysis. An impact analysis assesses the effects that a proposed change will have on a stakeholder or stakeholder group, project, or system.
• Implementation subject matter expert (SME). A stakeholder who will be responsible for designing, developing, and implementing the change described in the requirements and have specialized knowledge regarding the construction of one or more solution components.
• Incremental delivery. Creating working software in multiple releases so the entire product is delivered in portions over time.
• Indicator. An indicator identifies a specific numerical measurement that indicates progress toward achieving an impact, output, activity or input. See also metric.
• Initiative. Any effort undertaken with a defined goal or objective.
• Inspection. A formal type of peer review that utilizes a predefined and documented process, specific participant roles, and the capture of defect and process metrics. See also structured walkthrough.
• Interface. A shared boundary between any two persons and/or systems through which information is communicated.
• Interoperability. Ability of systems to communicate by exchanging data or services.
• Interview. A systematic approach to elicit information from a person or group of people in an informal or formal setting by asking relevant questions and documenting the responses.
• Knowledge area. A group of related tasks that support a key function of business analysis.
• Lessons learned process. A process improvement technique used to learn about and improve on a process or project. A lessons learned session involves a special meeting in which the team explores what worked, what didn't work, what could be learned from the just-completed iteration, and how to adapt processes and techniques before continuing or starting anew.
• Metadata. Metadata is information that is used to understand the context and validity of information recorded in a system.
• Methodology. A set of processes, rules, templates, and working methods that prescribe how business analysis, solution development and implementation is performed in a particular context.
• Metric. A metric is a quantifiable level of an indicator that an organization wants to accomplish at a specific point in time.
• Model(s). A representation and simplification of reality developed to convey information to a specific audience to support analysis, communication and understanding.
• Monitoring. Monitoring is a continuous process of collecting data to determine how well a solution is implemented compared to expected results. See also metric and indicator.
• Objective. A target or metric that a person or organization seeks to meet in order to progress towards a goal.
• Object-oriented modeling. An approach to software engineering where software is comprised of components that are encapsulated groups of data and functions which can inherit behavior and attributes from other components; and whose components communicate via messages with one another. In some organizations, the same approach is used for business engineering to describe and package the logical components of the business.
• Operational support. A stakeholder who helps to keep the solution functioning, either by providing support to end users (trainers, help desk) or by keeping the solution operational on a day-to-day basis (network and other tech support).
• Operative rule(s). The business rules an organization chooses to enforce as a matter of policy. They are intended to guide the actions of people working within the business. They may oblige people to take certain actions, prevent people from taking actions, or prescribe the conditions under which an action may be taken.
• Opportunity analysis. The process of examining new business opportunities to improve organizational performance.
• Optionality. Defining whether or not a relationship between entities in a data model is mandatory. Optionality is shown on a data model with a special notation.
• Organization. An autonomous unit within an enterprise under the management of a single individual or board, with a clearly defined boundary that works towards common goals and objectives. Organizations operate on a continuous basis, as opposed to an organizational unit or project team, which may be disbanded once its objectives are achieved.
• Organization modeling. The analysis technique used to describe roles, responsibilities and reporting structures that exist within an organization.
• Organizational process asset. All materials used by groups within an organization to define, tailor, implement, and maintain their processes.
• Organizational readiness assessment. An assessment that describes whether stakeholders are prepared to accept the change associated with a solution and are able to use it effectively.
• Organizational unit. Any recognized association of people in the context of an organization or enterprise.
• Plan-driven methodology. Any methodology that emphasizes planning and formal documentation of the processes used to accomplish a project and of the results of the project. Plan-driven methodologies emphasize the reduction of risk and control over outcomes over the rapid delivery of a solution.
• Prioritization. The process of determining the relative importance of a set of items in order to determine the order in which they will be addressed.
• Problem statement. A brief statement or paragraph that describes the problems in the current state and clarifies what a successful solution will look like.
• Process map. A business model that shows a business process in terms of the steps and input and output flows across multiple functions, organizations, or job roles.
• Process model. A visual model or representation of the sequential flow and control logic of a set of related activities or actions.
• Project. A temporary endeavor undertaken to create a unique product, service or result.
• Project charter. A 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 organizational resources to project activities.
• Project scope. The work that must be performed to deliver a product, service, or result with the specified features and functions. See also scope.
• Regulator. A stakeholder with legal or governance authority over the solution or the process used to develop it.
• Relationship. A defined association between concepts, classes or entities. Relationships are usually named and include the cardinality of the association.
• Relationship map. A business model that shows the organizational context in terms of the relationships that exist among the organization, external customers, and providers.
• Repository. A real or virtual facility where all information on a specific topic is stored and is available for retrieval.
• Return on investment. A measure of the profitability of a project or investment.
• Risk. An uncertain event or condition that, if it occurs, will affect the goals or objectives of a proposed change.
• Root cause analysis. Root cause analysis is a structured examination of an identified problem to understand the underlying causes.
• Scenario. An analysis model that describes a series of actions or tasks that respond to an event. Each scenario is an instance of a use case.
• Scope. The area covered by a particular activity or topic of interest. See also project scope and solution scope.
• Scope model. A model that defines the boundaries of a business domain or solution.
• Sequence diagram. A type of diagram that shows objects participating in interactions and the messages exchanged between them.
• Service. Work carried out or on behalf of others.
• Span of control. Span of control is the number of employees a manger is directly (or indirectly) responsible for.
• Stakeholder analysis. The work to identify the stakeholders who may be impacted by a proposed initiative and assess their interests and likely participation.
• Stakeholder list, roles, and responsibility designation. A listing of the stakeholders affected by a business need or proposed solution and a description of their participation in a project or other initiative.
• State diagram. An analysis model showing the life cycle of a data entity or class.
• Structural rule. Structural rules determine when something is or is not true or when things fall into a certain category. They describe categorizations that may change over time.
• Structured walkthrough. A structured walkthrough is an organized peer review of a deliverable with the objective of finding errors and omissions. It is considered a form of quality assurance.
• Subject matter expert (SME). A stakeholder with specific expertise in an aspect of the problem domain or potential solution alternatives or components.
• Swimlane. The horizontal or vertical section of a process model that show which activities are performed by a particular actor or role.
• SWOT analysis. SWOT is an acronym for Strengths, Weaknesses, Opportunities and Threats. It is a model used to understand influencing factors and how they may affect an initiative.
• System. A collection of interrelated elements that interact to achieve an objective. System elements can include hardware, software, and people. One system can be a sub-element (or subsystem) of another system.
• Technical constraint(s). Technical constraints are limitations on the design of a solution that derive from the technology used in its implementation. See also business constraint.
• Technique. Techniques alter the way a business analysis task is performed or describe a specific form the output of a task may take.
• Temporal event. A system trigger that is initiated by time.
• Timebox. A fixed period of time to accomplish a desired outcome.
• Unified modeling language (UML). A non-proprietary modeling and specification language used to specify, visualize, and document deliverables for object-oriented software-intensive systems.
• Variance analysis. Analysis of discrepancies between planned and actual performance, to determine the magnitude of those discrepancies and recommend corrective and preventative action as required.
• Work breakdown structure (WBS). A deliverable-oriented hierarchical decomposition of the work to be executed by the project team to accomplish the project objectives and create the required deliverables. It organizes and defines the total scope of the project.

The successor lecture is Project Management Quarter.