This is still work on progress
Component/Feature - Attributes
Note: I might use component/feature interchangeably, I will stick with the component, essentially I am referring to a building block of our product.
Intro
Design is an iterative process, and thus product is expected to be always in a continus process of change. A change in product is not only in regard of its features but also in regard of its characteristics and this document focus is on the later.
What is the goal of this
To define how to measure product characteristics
To provide a mechansim to measure where a component/feateur of the product is on our quality bar.
To detect/predict weakness or area of imporvment in component(s) of the product.
To suggest list of attributes which can help in mesuring quality of product component(s).
Open Questions:
Data Sources: Making data drivin decision is easy, but getting the data might not be that simple for some attributes, mainly usage.
What is our quality bar. Does this document needs to define it, or shuold it rely on external resources, like other estabilied OEPs, and in case such reference doesn’t, what to do about that…
What what is the smallest unit or building block of the product, and how does it relate or mapped to the techical product. (While I try to call it componenet, no matter if we agree about the name/notion it would be important to explicity define it, and list it… Can it be taken from mindmap, and if yes then at which level
Do We need to group them per technical context to group them per technical core it would simplify the measurability of attributes,( i.e. you measure an attribue of techncial core componenet, then it would affect all product compoenent that uses that technical core compoenent)
In case when different stackholders have different priority, or would optimize for different attribute, how can that be resolved?
For example enterprise scale provider of Open edX might not be concern if a change/featuer increase maintainability cost in terms of (human or/and IT resources), because they can afford that however other porivder would find it a blocker.
How does this relate to different use cases (ref Use Cases and MindMaps )
How does this relate to different use bases ( small scale, higher scale…etc)
In order to convert product components into artifact we propose to create a list of attributes, that would belong to product componenets. Just as Open edX Proposal #57: Core Product is defining what are the componenets of the product are, this is defining their attributes.
What do we mean by an Attribute:
An attribute can be though of as a signal, a character of the component, or for the product as a whole. As the product is a compostion of its componenets, its attrubtue or characteristics are a composistion of its every componenet. Simply put on other words, an attribute can be defined eitehr at the compoenent or level or at the product level.
Characteristics of Attributes
Just as each compoenet product has a collection of attributes, each of its attribute can be defined as its attributes, or meta attribute, those are just
An attribute must be measurable so that we can define its criteria. We should aim for the quantitative nonsubjective type of data. But it might not be always the case; i.e. what does the UX look like? might be a subjective opinion, in such cases, we can try to revert to the census agreement or/and for the subject matter expert.
Attributes might conflict with each other, for example optimizing for modularity might affect the performance or/and maintainability.
We might try to overcome this by setting the importance of each attribute relative to other attributes.
Rearchitecture: Can we rebuild it in a way that is try to take the best of each attribute…does the overall cost worth the outcome
When developing new features/components it's important to take the previous point into consideration, i.e. we should strive to that adding a new component does not affect attributes of other components in a negative way, unless there is a strong need to. i.e. Adding more MFEs improves the modernity of UX but decreases the efficacy/performance of the dev tool.
Some attributes might have well-defined OEP, which is a good thing, in that case, we don’t want to redefine that OEP but rather utilizes for PoV
Component Attributes
Below are example of suggested list of attribute.
Performace
Modernity
a11y
i18n/l10n
Modularity
Maintainability
Adoption Rate
Usability
Scalability
Developer Friendliness
Can it be deployed and enabled in the stable releases? (cf MFEs)
Is development active on it?
How many different community members depend on it? Is there collaboration on it?
Documentation - does it exist? Is it up to date?
User awareness - do users know about it?
Refs
To get overview of product featuers/componentes) https://www.mindmeister.com/map/2385779758?t=FnCLcUqgZ7
Table/Sheet example for Componenets/Attributes https://docs.google.com/spreadsheets/d/1fVKuxeNYwZNjR2roTQ-WJjqxlnZQa9dzNLWL8jBXmhw/edit?usp=sharing
Visual detaling realtion between product features and characteristics https://lucid.app/lucidchart/15ea9319-9aad-423f-b2bd-f43845702e1f/edit?viewport_loc=-448%2C-27%2C2729%2C1374%2C0_0&invitationId=inv_7ac311d4-d0af-4d9b-926f-720181a5d87f