Concept v/s. Characteristics
Introduction
In every Product Lifecycle Modeling (PLC), there is a set of designated features that the product possesses. These features are sellable in quantity as well as quality. The concept vs characteristics table can also be classified as quantitative and qualitative analysis. Such a table of a hypothetical product is shown here below:
Concept \ Characteristics
Wheel Drum
Fully Automatic Y | N
Spinning Y | N
Hot Water Y | N
Top Load
Fully Automatic Y | N
Spinning Y | N
Hot Water Y | N
Temperature Sensor
Fully Automatic Y | N
Spinning Y | N
Hot Water Y | N
Drainage Sink
Fully Automatic Y | N
Spinning Y | N
Hot Water Y | N
Can you guess what the product is?
This is the basis of developing a product, what we call specifications of the product, will be shown for the customer to search through them.
The conceptual phase essentially breaks down into two cyclical major components:
- The generation of solutions to meet the stated need.
- The evaluation of these solutions to select the one that is most suited to matching the PDS (product Design Specification).
Concepts are often best generated by individuals; concept selection and enhancement are often best presented in groups.
In a conceptual phase of the design core, there exists three primary components:
- Concept generation and expression by individuals, based on the Product Design Specification (PDS)
- Criteria generation in groups
- Evaluation of concepts as a group activity
Conclusion
The difference between a PDS and Requirements Specification is that the PDS consists of sellable components whereas Requirements Specification deals with the quality of the software that is built. The concept vs characteristics modelling is essential for improvement of component design in the design phase.
In software project management (SPM), the stories are initially pitched against the stakeholders and the clients to value that software in the Project Blast-off or Ice Breaker stage.