OpsCons vs ConOps..

OpsCons focus on the system under development from a stakeholder perspective.

ConOps focus on how the system fits into the bigger system of which it is a part and will
be developed, tested, and operated.

 A document describing the characteristics of a proposed system from the viewpoint of the
people who will use it.  - Concept of Operations (ConOps) Document

Configuration Management

Configuration Management is the process of maintaining systems, such as

computer hardware and software, in a desired state. Configuration Management
(CM) is also a method of ensuring that systems perform in a manner consistent with
expectations over time.

It's a way to make sure that a system performs as it's expected to as changes are made
over time.

Change Management

Configuration and change management (CCM) is the process of maintaining the

integrity of hardware, software, firmware, and documentation related to the
configuration and change management process.

Configuration and change management (CCM) is the process of maintaining the integrity of
hardware, software, firmware, and documentation related to the configuration and change
management process. CCM is a continuous process of controlling and approving changes to
information or technology assets or related infrastructure that support the critical services of
an organization. This process includes the addition of new assets, changes to assets, and the
elimination of assets.

Requirement Attribute:

A requirement attribute is a descriptive property associated with a requirement.

Requirement attributes are either user-defined attributes (defined by the project owner)
or system attributes (defined by Rational® RequisitePro® or an integrated Rational
product).
House of Quality :

The foundation of the house of quality is the belief that products should be designed to
reflect customers' desires and tastes—so marketing people, design ...

The “house of quality,” the basic design tool of the management approach known as
quality function deployment (QFD), originated in 1972 at Mitsubishi’s Kobe shipyard
site. Toyota and its suppliers then developed it in numerous ways. The house of quality
has been used successfully by Japanese manufacturers of consumer electronics, home
appliances, clothing, integrated circuits, synthetic rubber, construction equipment, and
agricultural engines. Japanese designers use it for services like swimming schools and
retail outlets and even for planning apartment layouts.

A set of planning and communication routines, quality function deployment focuses and
coordinates skills within an organization, first to design, then to manufacture and
market goods that customers want to purchase and will continue to purchase. The
foundation of the house of quality is the belief that products should be designed to
reflect customers’ desires and tastes—so marketing people, design engineers, and
manufacturing staff must work closely together from the time a product is first
conceived.

The house of quality is a kind of conceptual map that provides the means for
interfunctional planning and communications. People with different problems and
responsibilities can thrash out design priorities while referring to patterns of evidence
on the house’s grid.

What is the Kano model?

Quality Glossary Definition: Kano model

It's commonly believed that customers don’t really know what they want; they have to be
told.

The truth is customers do know what they want, but they may not be proficient at
describing their needs. By understanding the three types of customer needs and how to
reveal them, you’ll better know your customers' true needs and how to address them.

The Kano model is useful in gaining a thorough understanding of a customer’s

needs. You can translate and transform the resulting verbatims using the voice of the
customer table that, subsequently, becomes an excellent input as the whats in a quality
function deployment (QFD) House of Quality.

The model involves two dimensions:

 Achievement (the horizontal axis), which goes from the supplier didn’t do it at all to the
supplier did it very well.
 Satisfaction (the vertical axis), which goes from total dissatisfaction with the product or
service to total satisfaction with the product or service.

The KJ-Method

The KJ-Method or KJ Technique, is an idea generating and prioritizing technique

named after its inventor, Jiro Kawakita. This technique is one of the most popular
brainstorming variations for design, team, retrospective, and project meetings.

===========================================

Requirements engineering

In requirements engineering, requirements elicitation is the practice of researching

and discovering the requirements of a system from users, customers, and other
stakeholders. The practice is also sometimes referred to as "requirement gathering".

Requirement elicitation is the process of communicating and collaborating with key

stakeholders to assemble the insight and identify the project's needs.

What is requirements elicitation and why is it important?

Elicitation is an active effort to extract project-related information from all relevant

stakeholders. The objective is to clearly define the business or project objectives.
Requirements elicitation uses various analytics and techniques that allow for complete,
concise and clear requirements to be gathered.

What is elicitation process?

In business analysis, elicitation, however, does not involve magic or trickery. It refers
to a structured approach aimed to "draw out" information and forge a consensus
among Subject Matter Experts (SMEs) regarding the requirements of
application/software development.01-Feb-2021
 What is requirements elicitation and analysis?

Requirements Elicitation & Analysis

It's a process of interacting with customers and end-users to find out about the
domain requirements, what services the system should provide, and the other
constraints.13-Sept-2016

What are the types of elicitation?

List of elicitation techniques

 Interviews.
 Existing System.
 Project Scope.
 Brain Storming.
 Focus Groups.
 Exploratory Prototypes.
 User Task Analysis.
 Observation.

What are examples of elicitation?

 Simple elicitation techniques include the use of visual items such as pictures,

photographs, freehand drawing and real objects to draw vocabulary from
the class. Other examples include using mime, dialogue and example sentences
on the whiteboard to encourage the student's input.

What are the goals of requirements elicitation?

Introduction. A major goal of Requirements Elicitation is to avoid the confusions

between stakeholders and analysts. This will often involve putting significant sort into
requirements elicitation.
 What are the 5 stages of requirement gathering?

Requirements Gathering Steps

 Step 1: Understand Pain Behind The Requirement. ...
 Step 2: Eliminate Language Ambiguity. ...
 Step 3: Identify Corner Cases. ...
 Step 4: Write User Stories. ...
 Step 5: Create a Definition Of “Done”

System engineering boundary diagram

Featured snippet from the web

A boundary diagram is a graphical illustration of the relationships between the
subsystems, assemblies, subassemblies, and components within the object as well as
the interfaces with the neighboring systems and environments.

system boundary is a rectangle that you can draw in a use-case diagram to
separate the use cases that are internal to a system from the actors that are
external to the system. A system boundary is an optional visual aid in the diagram; it
does not add semantic value to the model.

WBS (Work Breakdown Structure)

The Work Breakdown Structure is used for many different things. Initially, it serves as
a planning tool to help the project team plan, define and organize scope ...

A work-breakdown structure in project management and systems engineering is a

deliverable-oriented breakdown of a project into smaller components. A work
breakdown structure is a key project deliverable that organizes the team's work into
manageable
What is Work Breakdown Structure?

A work breakdown structure (WBS) is a project management tool that takes a step-
by-step approach to complete large projects with several moving pieces. By
breaking down the project into smaller components, a WBS can integrate scope, cost
and deliverables into a single tool.25-Mar-2022

Difference between SEMP & PMP

The main difference is that the PMP includes all activities to be integrated and
controlled during the life of the program, whereas the SEMP emphasizes the SE
activities that are important to the program and individual projects.

What is in a program management plan (PMP) ?

Purpose of Program Management Plan

It contains the overall program governance, information on components (initiatives and

projects), benefits realization, related management plans and procedures, timelines,
and the methods used to plan, monitor, and control the program as it progresses.