ISO 15288 covers the System lifecycle, while ISO 12207 covers the Software lifecycle. As of 2008, the two are "harmonized for concurrent use". For instance, 12207 can be used "either alone or in conjunction with ... 15288"
In a bit more detail, what this means is that 15288 covers all aspects of developing a system, where examples of system components are ...
I'd suggest a standalone hard drive duplicator.
Very easy to use - attach the two hard drives, press a button to clone from one drive to the other. Also has the advantage of not tying up a computer during the duplication process.
Does anyone have an idea of what might be a good tool for this job in
I've used lots of different methods in the past. But these days, I rely pretty much exclusively on Virtual Machines for this job.
It's easy to set up a baseline. It's easy to restore it when needed.
What you are asking for is a fault injection. Unfortunatelly, you are not enough specific in what kind of error you want to reach and there is a lot of different states from bad blocks causing read-write errors to no rights or disconnected devices during the process, etc.
This answer on another project will make you happy under Linux: https://unix....
You don't automate the device testing
There are two reasons for this:
You have no control over the device firmware. That is written by, provided by, and (hopefully) tested by Verifone.
You have no control over the payment gateway. That is also written by, provided by, and (hopefully) tested by the payment provider the devices use.
The piece you can ...
Here are some of the issues which may you will face with Chromebook.
Chrome Os is Frequently crashing for No discernible reason
Chrome cannot properly load a web page, it will give you an odd “aw snap!” error that means the web page tried to load but crashed instead.
Sometimes unnoticed issues like plugged-in headphones that may need to be removed before ...
As for all metrics, it's a matter of definition, e.g. in unit tests you distinguish between
One line of code can have many conditions, of which not all are evaluated due to short-circuiting.
In your case, test coverage could be defined as
function coverage (a block has several functions)
The term "test ...
The test would have to be based on the requirement, since all random number generators are "pseudo-random". Here are some questions I would ask:
How random does it have to be? A children's game and a jury pool selection application would have different randomness requirements.
Once that is established, you would have to run a large enough statistical ...
Based on my experience, (which will vary from person to person) that automation tends to bottleneck on CPU. This lends itself to working better on actual physical hardware than on virtual hardware.
For that money I would by 13 mac minis and build a test grid. The mac mini gives you the option of running windows, mac os as well as virtualised linux, windows ...
I'm coming into this a bit late, but here's some thoughts for you:
What is the total run-time of all your tests? For instance, if you can schedule your suites to run in sequence overnight and have all your results waiting for you the next morning, you may only need one system to manage testing.
What levels of IO do your tests require? Tests with a ...