› Forums › IoTStack › News (IoTStack) › Write a good technical specification for an embedded product
Tagged: Development_G5, Tips_G9
- This topic has 1 voice and 0 replies.
-
AuthorPosts
-
-
October 12, 2019 at 5:39 am #35291
#News(IoTStack) [ via IoTGroup ]
Headings…
Write a good technical specification for an embedded product
Technical Specification should have following details:
1. Purpose of the design/product
2. Block diagram
3. Prerequisite Design Requirements
Environmental Conditions
Compliances Required
Target BOM cost
Expected Production Volume
Product AvailabilityAuto extracted Text……
A detailed technical design requirement specification document should be created.
Product spec should cover the main things like the purpose of the product, block diagram, main features, environmental conditions, manufacturing requirements, etc.
Technical Specification should also cover the specifics required for a particular product design.
1. Purpose of the design/product
For high volume production, consider making design which is faster to produce.
Also, it is quite impractical to test all field conditions, so there might be a need to fix a bug or provide a feature update to improve user experience when the product is already in the field.
If the product is already having a connectivity interface like BLE, WiFi, GPRS, etc.
Also in any scenario there should not be a need to open the product enclosure and do the software upgrade.
Make a list of features which will improve the whole user experience while operating the product.
Enclosure design will also be driven by environmental conditions, compliance requirements & thermal management needs.
5. Production
Proper test plan need to be created both for the validation and for the production testing.
A proper plan will help designer ensure that the product is easy to test in both the scenarios.
Design the product in such a way that all test points are accessible and the automated test setup takes the least amount of time to setup and test the product with maximum coverage.
It is impossible to design a circuit which doesn’t fail, so better to think about the scenarios in which product could fail and then how to handle them.
This information is useful for design engineers when designing the product and taking various decisions which will influence reliability nand repairability of the product.
This provides user necessary information which enables them to compare product vs their requirement.
How easy and intuitive your product’s user interface is, will define how much support will be required
Read More..
AutoTextExtraction by Working BoT using SmartNews 1.0299999999 Build 26 Aug 2019
-
-
AuthorPosts
- You must be logged in to reply to this topic.