Development Testing

Eric Scaraglino - Developement Testing related articles:

Article: Selenium contents of Portuguese commercial and wild edible mushrooms

Ruiling Shen, Shuangqun Luo, Jilin Dong, Application of oat dextrine for fat substitute in mayonnaise, Food Chemistry, Volume 126, Issue 1, 1 May 2011, Pages 65-71, ISSN 0308-8146, DOI: 10.1016/j.foodchem.2010.10.072.

Selenium contents of mushrooms may be higher than other mushrooms. A experiment was developed and concluded that it was not significantly higher than other mushrooms.
There were basic steps that were shown throughout development testing that we can apply to our PTM experiment:
1. Stating materials and chemicals used
2. Samples
3. Preparation (Procedure)
4. Validation (Permission to use equipment and samples)
5. Number of trials (precision and accuracy)
6. Statistical analysis
7. Results and discussion
8. Conclusion
(Summary of article, what I learned from it, and what methods we can apply)

Article: Application of oat dextrine for fat substitute in mayonnaise
Filipe Costa-Silva, Guilhermina Marques, Carlos C. Matos, Ana I.R.N.A. Barros, Fernando M. Nunes, Selenium contents of Portuguese commercial and wild edible mushrooms, Food Chemistry, Volume 126, Issue 1, 1 May 2011, Pages 91-96, ISSN 0308-8146, DOI: 10.1016/j.foodchem.2010.10.082.

Mayonnaise low-fat product was introduced using oat dextrine as a fat substitute. A developement testing was performed to find evidence that it is a good substitute source.
Like "Selenium contents of Portuguese commercial and wild edible mushrooms" article (see above), a series of steps were demonstrated throughout development testing:

1. Introduction (What is mayonnaise, the contents of it, and the studies of it)
2. Materials and methods (Preparations)
3. Analysis (There were many different types of analysis which are composition analysis, colour measurement, textural characteristics, viscosity measurements, optical microscope observation, sensory analysis, and statistical analysis)
4. Results and discussion (included plot graph, evaluations, and mathematical explanatory)
5. Conclusion (final answer)

Ashley Miller : 2 articles on Development Testing

Article One:

Lim, Andrew, et al. “New concepts for activity float in resource-constrained project management.” Science Direct. N.p., June 2011. Web. 15 Dec. 2010.



The backbone to this article is the general idea that within large projects multiple things must be tested and that each test closely relates to others within the project. More specifically, this article seeks to find out how changing the duration of testing within one piece of a project effects and changes the duration of other parts within the same project. As a foundation, it is established that the float of a project is the amount of time that testing can be extended without altering the final completion of the project, that a critical activity is an activity with zero float and that all of these terms can be related in sets or groups to relate multiple pieces of a larger project. Going off of this foundation, this experiment pushed the limits of the floats of projects and studied the impact that this manipulation had on the overall project. Coming up with the conclusion that flexibility is key in developmental testing and that buffer times are essential to make up for any error that could occur, this experiment could easily apply to what we are doing within class. Our PTM project is easily described as a project with multiple pieces and multiple steps, so the timing of everything must align in some way in order to arrive at our final goal. The experiment in this article looked carefully at situations such as ours and found that flexibility it alright as long as careful planning is maintained. Within our class we keep set calendars and allow for some time in case things go wrong, but do we really know what those key steps are that would throw us off? If something went wrong with structure, how would camera be impacted, or if something just wasn’t working for illumination would the software groups be able to test their software? Defining our critical activities and loosely naming the floats for certain tasks may be of use to us; if we know what is of greater importance we will be able to make sure that these tasks are targeted more closely than others with greater float time.

Article Two:

Lai, Kuei-Kuei, et al. “A Case Study of Increasing Market Competitiveness through Shortening the Research and Development Cycle.” IEEE Explore. N.p., n.d. Web. 15 Dec. 2010. <__‌stamp/‌stamp.jsp?tp=&arnumber=4599735&tag=1__>.

In order to test the hypothesis that a shorter development time leads to greater efficiency in putting things out into the market a research team constructed and tested a set number of cars within a limited time. Finding that the time was inefficient for certain tests, the research was concluded to be a bit indecisive. Still, they were able to find that cars built under a limited time maintained strong ratings within specific endurance and stress tests, and that they, at the same time, were able to fulfill the desires of the current technology market. Thought this case is specific to cars, I believe that the general basis for testing could easily relate to our PTM’s development. How much time do we want to spend developing our product when the market is waiting? Is there a way to shorten the developmental time, while still remaining accurate, in order to get more test time with the actual PTM? I think these are definitely questions that can be targeted and I feel like our main goal is really to have the PTM to work with. While certain aspects may weaken under a shortened time frame, I feel that cutting back on some things within our developmental stages could easily allow us to have a working PTM faster.

Stefano Prezioso: Development Testing Article Precis

Paget, M.D.G.; , "The evaluation procedure for the testing of intruder detection equipment," Security Technology, 1998. Proceedings., 32nd Annual 1998 International Carnahan Conference on , vol., no., pp.201-205, 12-14 Oct 1998
doi: 10.1109/CCST.1998.723790

In this article, the testing methods for intruder detection systems are explained. The general process that is used for testing the systems can be generalized and applied to many different situations. First, standards are either looked up or created that, if met, characterize the equipment as passable for that specific test. Then, after all the standards are allocated, a method for testing the equipment in a controlled, standardized way is developed. The next step is testing. After testing has concluded and data is gathered, a report is written summarizing the results for each piece of equipment. The results for each test is given, compared to the standards set forth in the beginning, and an overall conclusion about that piece of equipment is made. This process will be very important for us as we begin to test new cameras, lighting, software, etc.

Dachao Zou; Yayu Liu; Li Liu; Fei Ma; Shilin Qu; , "The Research and Website Development of Software Related the General Testing Equipment or System on Energy Supply System of Building," Energy and Environment Technology, 2009. ICEET '09. International Conference on , vol.3, no., pp.652-654, 16-18 Oct. 2009
doi: 10.1109/ICEET.2009.626

In this article, difficulties of testing specific types of energy supply systems for buildings is outlined, and their way of overcoming these problems is also discussed. The issue with the current method of testing is that, even though it is simple and straightforward, it is time consuming, and there is no way to produce a large enough quantity of test results. To overcome this issue, the researchers developed a method of virtual testing, which in detail is irrelevant to the Imaging Science project. What is relative however is the thought process and innovation to create new methods of testing, or even developing new testing instruments to figure out the testing data that is needed. This can apply to testing both the Phase 1 and 2 cameras, the different lighting used, efficiency of the software, etc.