| Work Product (Artifact): Platform Specific Model |
|
 |
| The Platform Specific Model is an adaptation of a Platform Independent Model (PIM) for execution on a specific target through the selection of technologies, design solutions, or design patterns. |
|
Purpose
| The purpose of the Platform-Specific Model (PSM) is to provide an optimized, targeted implementation of a Platform
Independent Model (PIM). |
Relationships
| Contained Artifacts |
|
| Input To | Mandatory:
| Optional:
| External:
|
Main Description
| The PSM is a model of the system that contains both the essential elements from the PIM and technologies, design
patterns, and design solutions meant to optimize the PSM. In the Harmony/Embedded process, design is all about
optimization. While the PIM executes the required functionality of the system, it does so in an un-optimized fashion.
Specific technologies, architectures, design patterns, and other design decisions are added to provide the PIM functional
in a fashion optimized for the intended use and target platform(s). |
Properties
| Optional |  |
| Planned | |
Key Considerations
| The PSM must support the functionality of its parent PIM while at the same time making design and technology decisions that
optimize its properties against various design criteria, including QoS. |
Tailoring
| Impact of not having | The PSM provides an optimized solution that meets the functional needs of the system, so not having a PSM means that while
the basic functionality may be met, it is certainly likely to be un-optimized and may not meet the system's required QoS
requirements. |
| Reasons for not needing | In early prototypes (builds) there is usually more emphasis on key concepts (analysis, requirements, and architecture
concepts) while later prototypes focus more on fine-tuning, optimization, and deployment concerns. Thus, early prototypes
may have very little optimization present. |
More Information
| Checklists |
|
| Concepts |
|
| Guidelines |
|
|
