J
Jagadeesh Reddy
Hi, Can any one share your stratagies on Testing any Operating System, I need to release a Operating System to the market after through Testing is done.
Hello Jagadeesh! Welcome to the Cove!
I am not a software evaluator, so your questions interested me. I found two site on the Internet that looked relevant to your topic:
http://www.opengroup.org/testing/testsuites/VSXgen.htm
http://www.networkworld.com/topics/operating-systems.html
Also, I found a thread with some information that may be helpful:
http://elsmar.com/Forums/showthread.php?t=10732&highlight=testing+operating+systems
1. Are you part of an organization that typically develops operating systems?
2. Is this "rollout" for your organization, or one that you will offer to the public for resale?
3. Is this a completely new operating system, or a revision change?
I would think that you should have a master plan of sorts in-place. In my opinion, your plan should have something to document what currently is in place, what actions are being taken to install the new operating system, and what transpired.
I am familar with the PADDIE plan that I learned in my information systems class:
Plan
Assess
Design
Develop
Implement
Evaluate
The planning/ assessing phases are the most important.
I would think that you would have already validated the operating system on a standalone computer. This should help you work out the first wave of problems.
Anyway, my
I am not a software evaluator, so your questions interested me. I found two site on the Internet that looked relevant to your topic:
http://www.opengroup.org/testing/testsuites/VSXgen.htm
http://www.networkworld.com/topics/operating-systems.html
Also, I found a thread with some information that may be helpful:
http://elsmar.com/Forums/showthread.php?t=10732&highlight=testing+operating+systems
1. Are you part of an organization that typically develops operating systems?
2. Is this "rollout" for your organization, or one that you will offer to the public for resale?
3. Is this a completely new operating system, or a revision change?
I would think that you should have a master plan of sorts in-place. In my opinion, your plan should have something to document what currently is in place, what actions are being taken to install the new operating system, and what transpired.
I am familar with the PADDIE plan that I learned in my information systems class:
Plan
Assess
Design
Develop
Implement
Evaluate
The planning/ assessing phases are the most important.
I would think that you would have already validated the operating system on a standalone computer. This should help you work out the first wave of problems.
Anyway, my