Return to Answer

I'd actually like to see another SE site created that is specifically for checking of work. This would be similar to the way the programming/software engineering discipline is broken into a subset of sites.

Since the sites related to this discipline are arguably the most mature and most developed area within the SE universe, I think we can look at their model as emulable for other disciplines.

As it relates to "check my work" questions, the programming sphere of SE has this handled pretty well I think - we can look at emulating the division between StackOverflow and CodeReview, and could create our own sub-divisions by having EngineeringOverflow and EngineeringReview sites. If we follow this model a step further we could create a third site Engineers as the parallel to the Programmers site.

I see this multi-site subset of Engineering comprised as:

• EngineeringOverflow : for specific questions regarding engineering challenges you are trying to overcome.

• EngineeringReview : where you can post up working solutions for peer review and get suggestions for improvements (check my work questions, continuous improvement questions, etc. would go here)

• Engineers : for discussing general Engineering concepts, theories, and practices.

Examples:

• Question: I'm putting together a test plan, and struggling with determining the number of samples needed. I want to ask a question on how to determine the number of test samples needed to reach a 95% confidence level on mean time between failures (MTBF) for an unknown (infinite) population size.

  On-Topic for: EngineeringOverflow. This is a specific question regarding calculations related to reliability engineering and construction of test plans.

• Question: I'm a design engineer at a small company. One of the design requirements is that the product must achieve a specific minimum mean time between failures in the field. As a small company, we don't have a reliability engineer in house and I've been asked to design this test plan since I'm the cognizant engineering on the project. I've created a test plan, but since this is a little outside my normal scope of work, and this is a high visibility project, I'd like to get some peer review on my approach before presenting my plan to the man in charge.

  On-Topic for: EngineeringReview. I have a solution and would like to have it peer reviewed.

• Question: Same scenario as above, but before creating my plan I'd like to get some general advice on distinguishing between mean time between failures (MTBF) and mean time to failure (MTTF), and where to draw the line on "repairable" vs "non-repairable" failure modes. This will help me decide whether or not MTBF is the appropriate metric to focus on, or if MTTF is what we really need (as I suspect it is).

  On-Topic for: Engineers. Looking for advice on the general topics of test plan scope and data categorization, as well as defining industry terminology.

I'd actually like to see another SE site created that is specifically for checking of work. This would be similar to the way the programming/software engineering discipline is broken into a subset of sites.

Since the sites related to this discipline are arguably the most mature and most developed area within the SE universe, I think we can look at their model as emulable for other disciplines.

As it relates to "check my work" questions, the programming sphere of SE has this handled pretty well I think - we can look at emulating the division between StackOverflow and CodeReview, and could create our own sub-divisions by having EngineeringOverflow and EngineeringReview sites. If we follow this model a step further we could create a third site Engineers as the parallel to the Programmers site.

I see this multi-site subset of Engineering comprised as:

• EngineeringOverflow : for specific questions regarding engineering challenges you are trying to overcome.

• EngineeringReview : where you can post up working solutions for peer review and get suggestions for improvements (check my work questions, continuous improvement questions, etc. would go here)

• Engineers : for discussing general Engineering concepts, theories, and practices.

Examples:

• Question: I'm putting together a test plan, and struggling with determining the number of samples needed. I want to ask a question on how to determine the number of test samples needed to reach a 95% confidence level on mean time between failures (MTBF) for an unknown (infinite) population size.

  On-Topic for: EngineeringOverflow. This is a specific question regarding calculations related to reliability engineering and construction of test plans.

• Question: I'm a design engineer at a small company. One of the design requirements is that the product must achieve a specific minimum mean time between failures in the field. As a small company, we don't have a reliability engineer in house and I've been asked to design this test plan since I'm the cognizant engineering on the project. I've created a test plan, but since this is a little outside my normal scope of work, and this is a high visibility project, I'd like to get some peer review on my approach before presenting my plan to the man in charge.

  On-Topic for: EngineeringReview. I have a solution and would like to have it peer reviewed.

• Question: Same scenario as above, but before creating my plan I'd like to get some general advice on distinguishing between mean time between failures (MTBF) and mean time to failure (MTTF), and where to draw the line on "repairable" vs "non-repairable" failure modes. This will help me decide whether or not MTBF is the appropriate metric to focus on, or if MTTF is what we really need (as I suspect it is).

  On-Topic for: Engineers. Looking for advice on the general topics of test plan scope and data categorization, as well as defining industry terminology.

I'd actually like to see another SE site created that is specifically for checking of work. This would be similar to the way the programming/software engineering discipline is broken into a subset of sites.

Since the sites related to this discipline are arguably the most mature and most developed area within the SE universe, I think we can look at their model as emulable for other disciplines.

As it relates to "check my work" questions, the programming sphere of SE has this handled pretty well I think - we can look at emulating the division between StackOverflow and CodeReview, and could create our own sub-divisions by having EngineeringOverflow and EngineeringReview sites. If we follow this model a step further we could create a third site Engineers as the parallel to the Programmers site.

I see this multi-site subset of Engineering comprised as:

• EngineeringOverflow : for specific questions regarding engineering challenges you are trying to overcome.

• EngineeringReview : where you can post up working solutions for peer review and get suggestions for improvements (check my work questions, continuous improvement questions, etc. would go here)

• Engineers : for discussing general Engineering concepts, theories, and practices.

Examples:

• Question: I'm putting together a test plan, and struggling with determining the number of samples needed. I want to ask a question on how to determine the number of test samples needed to reach a 95% confidence level on mean time between failures (MTBF) for an unknown (infinite) population size.

  On-Topic for: EngineeringOverflow. This is a specific question regarding calculations related to reliability engineering and construction of test plans.

• Question: I'm a design engineer at a small company. One of the design requirements is that the product must achieve a specific minimum mean time between failures in the field. As a small company, we don't have a reliability engineer in house and I've been asked to design this test plan since I'm the cognizant engineering on the project. I've created a test plan, but since this is a little outside my normal scope of work, and this is a high visibility project, I'd like to get some peer review on my approach before presenting my plan to the man in charge.

  On-Topic for: EngineeringReview. I have a solution and would like to have it peer reviewed.

• Question: Same scenario as above, but before creating my plan I'd like to get some general advice on distinguishing between mean time between failures (MTBF) and mean time to failure (MTTF), and where to draw the line on "repairable" vs "non-repairable" failure modes. This will help me decide whether or not MTBF is the appropriate metric to focus on, or if MTTF is what we really need (as I suspect it is).

  On-Topic for: Engineers. Looking for advice on the general topics of test plan scope and data categorization, as well as defining industry terminology.

I'd actually like to see another SE site created that is specifically for checking of work. This would be similar to the way the programming/software engineering discipline is broken into a subset of sites.

Since the sites related to this discipline are arguably the most mature and most developed area within the SE universe, I think we can look at their model as emulable for other disciplines.

As it relates to "check my work" questions, the programming sphere of SE has this handled pretty well I think - we can look at emulating the division between StackOverflow and CodeReview, and could create our own sub-divisions by having EngineeringOverflow and EngineeringReview sites. If we follow this model a step further we could create a third site Engineers as the parallel to the Programmers site.

I see this multi-site subset of Engineering comprised as:

• EngineeringOverflow : for specific questions regarding engineering challenges you are trying to overcome.

• EngineeringReview : where you can post up working solutions for peer review and get suggestions for improvements (check my work questions, continuous improvement questions, etc. would go here)

• Engineers : for discussing general Engineering concepts, theories, and practices.

Examples:

• Question: I'm putting together a test plan, and struggling with determining the number of samples needed. I want to ask a question on how to determine the number of test samples needed to reach a 95% confidence level on mean time between failures (MTBF) for an unknown (infinite) population size.

  On-Topic for: EngineeringOverflow. This is a specific question regarding calculations related to reliability engineering and construction of test plans.

• Question: I'm a design engineer at a small company. One of the design requirements is that the product must achieve a specific minimum mean time between failures in the field. As a small company, we don't have a reliability engineer in house and I've been asked to design this test plan since I'm the cognizant engineering on the project. I've created a test plan, but since this is a little outside my normal scope of work, and this is a high visibility project, I'd like to get some peer review on my approach before presenting my plan to the man in charge.

  On-Topic for: EngineeringReview. I have a solution and would like to have it peer reviewed.

• Question: Same scenario as above, but before creating my plan I'd like to get some general advice on distinguishing between mean time between failures (MTBF) and mean time to failure (MTTF), and where to draw the line on "repairable" vs "non-repairable" failure modes. This will help me decide whether or not MTBF is the appropriate metric to focus on, or if MTTF is what we really need (as I suspect it is).

  On-Topic for: Engineers. Looking for advice on the general topics of test plan scope and data categorization, as well as defining industry terminology.

I'd actually like to see another SE site created that is specifically for checking of work. This would be similar to the way the programming/software engineering discipline is broken into a subset of sites.

Since the sites related to this discipline are arguably the most mature and most developed area within the SE universe, I think we can look at their model as emulable for other disciplines.

As it relates to "check my work" questions, the programming sphere of SE has this handled pretty well I think - we can look at emulating the division between StackOverflow and CodeReview, and could create our own sub-divisions by having EngineeringOverflow and EngineeringReview sites. If we follow this model a step further we could create a third site Engineers as the parallel to the Programmers site.

I see this multi-site subset of Engineering comprised as:

• EngineeringOverflow : for specific questions regarding engineering challenges you are trying to overcome.

• EngineeringReview : where you can post up working solutions for peer review and get suggestions for improvements (check my work questions, continuous improvement questions, etc. would go here)

• Engineers : for discussing general Engineering concepts, theories, and practices.

Examples:

• Question: I'm putting together a test plan, and struggling with determining the number of samples needed. I want to ask a question on how to determine the number of test samples needed to reach a 95% confidence level on mean time between failures (MTBF) for an unknown (infinite) population size.

  On-Topic for: EngineeringOverflow. This is a specific question regarding calculations related to reliability engineering and construction of test plans.

• Question: I'm a design engineer at a small company. One of the design requirements is that the product must achieve a specific minimum mean time between failures in the field. As a small company, we don't have a reliability engineer in house and I've been asked to design this test plan since I'm the cognizant engineering on the project. I've created a test plan, but since this is a little outside my normal scope of work, and this is a high visibility project, I'd like to get some peer review on my approach before presenting my plan to the man in charge.

  On-Topic for: EngineeringReview. I have a solution and would like to have it peer reviewed.

• Question: Same scenario as above, but before creating my plan I'd like to get some general advice on distinguishing between mean time between failures (MTBF) and mean time to failure (MTTF), and where to draw the line on "repairable" vs "non-repairable" failure modes. This will help me decide whether or not MTBF is the appropriate metric to focus on, or if MTTF is what we really need (as I suspect it is).

  On-Topic for: Engineers. Looking for advice on the general topics of test plan scope and data categorization, as well as defining industry terminology.

I'd actually like to see another SE site created that is specifically for checking of work. This would be similar to the way the programming/software engineering discipline is broken into a subset of sites.

Since the sites related to this discipline are arguably the most mature and most developed area within the SE universe, I think we can look at their model as emulable for other disciplines.

As it relates to "check my work" questions, the programming sphere of SE has this handled pretty well I think - we can look at emulating the division between StackOverflow and CodeReview, and could create our own sub-divisions by having EngineeringOverflow and EngineeringReview sites. If we follow this model a step further we could create a third site Engineers as the parallel to the Programmers site.

I see this multi-site subset of Engineering comprised as:

• EngineeringOverflow : for specific questions regarding engineering challenges you are trying to overcome.

• EngineeringReview : where you can post up working solutions for peer review and get suggestions for improvements (check my work questions, continuous improvement questions, etc. would go here)

• Engineers : for discussing general Engineering concepts, theories, and practices.

Examples:

• Question: I'm putting together a test plan, and struggling with determining the number of samples needed. I want to ask a question on how to determine the number of test samples needed to reach a 95% confidence level on mean time between failures (MTBF) for an unknown (infinite) population size.

  On-Topic for: EngineeringOverflow. This is a specific question regarding calculations related to reliability engineering and construction of test plans.

• Question: I'm a design engineer at a small company. One of the design requirements is that the product must achieve a specific minimum mean time between failures in the field. As a small company, we don't have a reliability engineer in house and I've been asked to design this test plan since I'm the cognizant engineering on the project. I've created a test plan, but since this is a little outside my normal scope of work, and this is a high visibility project, I'd like to get some peer review on my approach before presenting my plan to the man in charge.

  On-Topic for: EngineeringReview. I have a solution and would like to have it peer reviewed.

• Question: Same scenario as above, but before creating my plan I'd like to get some general advice on distinguishing between mean time between failures (MTBF) and mean time to failure (MTTF), and where to draw the line on "repairable" vs "non-repairable" failure modes. This will help me decide whether or not MTBF is the appropriate metric to focus on, or if MTTF is what we really need (as I suspect it is).

  On-Topic for: Engineers. Looking for advice on the general topics of test plan scope and data categorization, as well as defining industry terminology.