element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • About Us
  • Community Hub
    Community Hub
    • What's New on element14
    • Feedback and Support
    • Benefits of Membership
    • Personal Blogs
    • Members Area
    • Achievement Levels
  • Learn
    Learn
    • Ask an Expert
    • eBooks
    • element14 presents
    • Learning Center
    • Tech Spotlight
    • STEM Academy
    • Webinars, Training and Events
    • Learning Groups
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents Projects
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • Project Groups
  • Products
    Products
    • Arduino
    • Avnet Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • Store
    Store
    • Visit Your Store
    • Choose another store...
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
  • Settings
RoadTests & Reviews
  • Products
  • More
RoadTests & Reviews
RoadTest Forum Typical Road Test Plan for an SBC like Raspberry Pi4
  • Blog
  • RoadTest Forum
  • Documents
  • RoadTests
  • Reviews
  • Polls
  • Files
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Join RoadTests & Reviews to participate - click to join for free!
Actions
  • Share
  • More
  • Cancel
Forum Thread Details
  • State Not Answered
  • Replies 14 replies
  • Subscribers 2551 subscribers
  • Views 3061 views
  • Users 0 members are here
  • review plan
  • dougw
  • review estimate
  • road test estimate
  • road test plan
Related

Typical Road Test Plan for an SBC like Raspberry Pi4

dougw
dougw over 2 years ago

 rscasny  asked  "How Long Would It Take for You to RoadTest the Raspberry Pi 4 Model B". I did a bit of a work up to see what it might take, but it was too long to fit in a comment under his question, so I made this discussion.

The times and tasks could vary a lot from these values, but it provides a bit of perspective on what it might take...

Chapter Time-Hours Tasks
1 3

Organize and setup the project

  • Setup project directories
  • Research the product
  • Gather links, datasheets and example material
  • Find and store some images
  • Read the datasheets
  • Work out a project plan
2 3 Introduction of reviewer
  • Introduction of product
  • history
  • reason for review
  • key features
  • mention factoids
  • Design frontispiece image
3 3 Unboxing video
  • Write narration
  • Explain all visual features
  • Shoot and edit video
  • Publish video
4 3 System description
  • Describe system features
  • Design expanded image with call-outs
  • Describe peripherals and their hookup
  • Discuss power requirements
  • Discuss packaging and thermal considerations
5 4 Software setup video(operating system installation)
  • Demonstrate and discuss boot-up
  • Discuss where to get software and how to install
  • Download resources
  • Describe software setup requirements
  • List step-by-step process
  • Discuss GUI and CLI user interfaces
  • Write narrative
  • Video the process & edit & publish
6 4 Benchmark demos
  • Download benchmarks for
    • processor performance
    • graphics performance
    • power consumption
    • thermal performance
  • Video benchmark installation
  • Video benchmarks being run
  • edit and publish videos
  • discuss benchmarks comparing to similar products
7 4 Application software
  • Demonstrate built-in applications
  • List other sources of application software
  • Discuss application software
8 3 Peripherals
  • Discuss available peripherals and their operation
  • Discuss the expansion connector and its applications
9 4 Programming
  • Discuss programming environments and languages
  • Demonstrate workflows
  • Show how to create an autoboot program
10 20 Build a real application or system
  • Publish code
  • Document hardware, packaging and thermal
  • Demonstrate application in action
11 2 Discussion & Conclusions
  • Comparison of features
  • What was done well
  • What was problematic, what were the issues
  • What could be improved
  • Who should buy one
  • Discussion of cost & value
Total 53

Please add any tasks I missed or elaborate on the time estimates in the comments below.

  • Sign in to reply
  • Cancel

Top Replies

  • Jan Cumps
    Jan Cumps over 2 years ago +5
    In this case, I'd probably take it from a different angle. If it was a new style of Linuxy SBC, I'd compare it to the better know ones, then try to find differences and poke into those. To prevent that…
  • robogary
    robogary over 2 years ago +4
    Dougw , your checklist list is a pretty thorough and accurate, nice. The disclaimer on variables pretty much covers everything. One bullet that could be added just as a holding spot is learning curve…
  • baldengineer
    baldengineer over 2 years ago in reply to robogary +4
    holding spot is learning curve investigations (going down the rabbit hole) "Learning curve investigations" is going to be my new name for rabbit holes.
  • ntewinkel
    0 ntewinkel over 2 years ago

    Good idea to break it down like that, dougw ! Once you get into the details it becomes so much more clear why it’s so easy to spend so many hours!

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • Jan Cumps
    0 Jan Cumps over 2 years ago

    In this case, I'd probably take it from a different angle.

    If it was a new style of Linuxy SBC, I'd compare it to the better know ones, then try to find differences and poke into those. To prevent that I'd end up with a story on how Linux works on another board. Try to get the unique things out of the hardware and supporting libraries.

    If it'd a Pi 4, I'd only focus on where it's different with the Pi3. And if that changes anything for a user (good or bad). Really focus on the design decisions and differentiators.

    The longer I do road tests, the less time I spend on verifying manufacturer claims. I want to see how useful it is for a user (me).

    • Cancel
    • Vote Up +5 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • robogary
    0 robogary over 2 years ago in reply to Jan Cumps

    100% Agree. The manufacturer's engineering team already knows the measured performance if it's a charlie release. I myself rarely operate equipment at it's corner points, old schoolers add fudge factors.

    In fact, I'd be more interested in the user's perceived performance difference of a RPi4  1 Gb, 2GB, 4 Gb, and 8 Gb models.  

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • robogary
    0 robogary over 2 years ago

    Dougw , your checklist list is a pretty thorough and accurate, nice.  The disclaimer on variables pretty much covers everything. 

    One bullet that could be added just as a holding spot is learning curve investigations (going down the rabbit hole). Especially in your description Chapter 1, 9, & 10  I'll always have time spent on investigating things I didnt know, that I didnt know....fixing stuff I broke......and things I thought should take 10 minutes that take 10 hours.    

      

    • Cancel
    • Vote Up +4 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • baldengineer
    0 baldengineer over 2 years ago in reply to robogary

    holding spot is learning curve investigations (going down the rabbit hole)

    "Learning curve investigations" is going to be my new name for rabbit holes.

    • Cancel
    • Vote Up +4 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • robogary
    0 robogary over 2 years ago in reply to baldengineer

    I formally adopted the term "multitasking" when it was used in online meetings as a polite synonym for "sorry, please repeat, I was getting real work done and wasnt paying attention". 

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • BigG
    0 BigG over 2 years ago in reply to robogary
    robogary said:
    I'll always have time spent on investigating things I didnt know, that I didnt know

    Love it... those unknown unknowns...

    Yes, I would agree with you that this is pretty thorough.

    To cater for our unknown unknowns, I personally like to add in some contingency, even though it invariably gets eaten up. The amount of contingency very much depends on how familiar I am with similar products and whether this is a trailblazing new product with little to rely on or whether it's an improvement on an earlier version.

    • Cancel
    • Vote Up +2 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • dougw
    0 dougw over 2 years ago in reply to BigG

    Contingency is definitely missing and you are right - it always gets eaten up. 

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • Jan Cumps
    0 Jan Cumps over 2 years ago in reply to dougw

    Project manager tip: Do not plan for contingency. Or use a fixed number, like 15%, and consider it taken .

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • robogary
    0 robogary over 2 years ago in reply to Jan Cumps

    https://www.indeed.com/hire/c/info/what-is-a-contingency-plan   A contingency plan helps you prepare for unanticipated occurrences that might otherwise cost you time, money or even your entire business. Sounds pretty severe.

    For a Road Test, contingency really isnt the right vocabulary word, but anticipating and showing some time spent for exploring unknowns, tester learning, and flat out playing is part of the road test. Doug's task list is a good organized "proof"  for the estimated hours spent on a road test, tho adding in a bit for exploring time depending on the road test product's complexity, is food for thought. 

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
>
element14 Community

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2025 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

ICP 备案号 10220084.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube