rendaoyuan 2007-3-29 09:03
Testing activity
[align=center][b][size=12pt][color=#000000][font=Times New Roman]Testing [b]activity[/b][/font][/color][/size][/b][/align]
[align=center][b][size=12pt][color=#000000][font=Times New Roman]
[/font][/color][/size][/b][color=#000000][font=Wingdings][size=8.5pt][b]u[/b][/size][/font][b][size=3][font=Times New Roman]Testing is an integral component of the software process[/font][/size][/b][/color][/align]
[color=#000000][font=Wingdings][size=8.5pt][b]u[/b][/size][/font][b][size=3][font=Times New Roman]Testing is a critical element of software quality assurance[/font][/size][/b][/color]
[color=#000000][font=Wingdings][size=8.5pt][b]u[/b][/size][/font][b][size=3][font=Times New Roman]Testing is an activity that must be carried out throughout the software development life cycle[/font][/size][/b][/color]
[b][font=Times New Roman][size=3][color=#000000][/color][/size][/font][/b]
[b][size=12pt][font=Times New Roman][color=#000000][/color][/font][/size][/b]
[align=left][color=#000000][font=Times New Roman][size=14pt]What Should Be Tested?[/size][size=14pt][/size][/font][/color][/align]
[font=Times New Roman][size=3][color=#000000][/color][/size][/font]
[align=left][size=14pt][font=Times New Roman][size=3][color=#000000][/color][/size][/font][font=Times New Roman][color=#000000]Correctness[/color][/font][/size][size=14pt][/size][/align]
[size=14pt][font=Times New Roman][color=#000000][/color][/font][color=#000000][font=Times New Roman]Utility [/font][/color][/size]
[size=14pt][font=Times New Roman][color=#000000][/color][/font][color=#000000][font=Times New Roman]Performance[/font][/color][/size]
[size=14pt][font=Times New Roman][color=#000000][/color][/font][color=#000000][font=Times New Roman]Robustness[/font][/color][/size]
[size=14pt][font=Times New Roman][color=#000000][/color][/font][color=#000000][font=Times New Roman]Reliability[/font][/color][/size]
[align=center][color=#000000][font=Times New Roman][b][size=12pt]Correctness[/size][/b][b][size=12pt][/size][/b][/font][/color][/align]
[size=10.5pt][size=3][color=#000000][font=Times New Roman]The extent to which a program satisfies its specification and fulfills the customer’s mission objectives.[/font][/color][/size][/size]
[size=10.5pt][size=3][color=#000000][font=Times New Roman]If input that satisfies the input specifications is provided and the product is given all the resources it needs, then the product is correct if the output satisfies the output specification.[/font][/color][/size][/size]
[size=10.5pt][size=3][color=#000000][font=Times New Roman]If a product satisfies its specification, then this product is correct.[/font][/color][/size][/size]
[align=left][size=3][color=#000000][font=Arial][size=10.5pt]Questions:[/size][/font][font=Arial][size=10.5pt][/size][/font][/color][/size][/align]
[font=Arial][size=10.5pt][size=3][color=#000000]Suppose a product has been tested successfully against a broad variety of test data. Does this mean that the product is acceptable?[/color][/size][/size][/font]
[b][font=Arial][size=12pt][color=#000000][/color][/size][/font][/b]
[size=12pt]Utility[/size][size=12pt][/size][size=10.5pt][b][size=3][color=#000000][font=Times New Roman]Utility is the extent to which a user’s needs are met when a correct product is used under condition permitted by its specifications.[/font][/color][/size][/b][/size]
[size=10.5pt][b][size=3][color=#000000][font=Times New Roman]It focus on[i][u] how easy[/u][/i] the product is to use, whether the product performs [i][u]useful functions[/u][/i], and whether the product is [i][u]cost effective[/u][/i] compared to competing products.[/font][/color][/size][/b][/size]
[align=left][size=3][color=#000000][font=Times New Roman][size=10.5pt][b]If the product is not [u]cost effective[/u], there is no point in buying it.[/b][/size][size=10.5pt][/size][/font][/color][/size][/align]
[size=10.5pt][b][size=3][color=#000000][font=Times New Roman]And unless the product is easy to use, it will not be used at all or it will be used incorrectly. [/font][/color][/size][/b][/size]
[size=10.5pt][b][size=3][color=#000000][font=Times New Roman]Therefore, when considering buying an existing product, the utility of the product should be tested first; and if the product fails on that score, testing should stop.[/font][/color][/size][/b][/size]
[b][font=Arial][size=10.5pt][size=3][color=#000000][/color][/size][/size][/font][/b]
[align=center][b][font=Arial][size=12pt][color=#000000]Performance[/color][/size][/font][/b][/align]
[size=10.5pt][b][size=3][color=#000000][font=Times New Roman]It is the extent to which the product meets its constraints with regard to response [i][u]time[/u][/i] or [i][u]space[/u][/i] requirements. [/font][/color][/size][/b][/size]
[size=10.5pt][b][size=3][color=#000000][font=Times New Roman]Performance is measured by processing speed, response time, resource consumption, throughput and efficiency.[/font][/color][/size][/b][/size]
[size=10.5pt][b][font=Times New Roman][size=3][color=#000000][/color][/size][/font][/b][/size]
[size=10.5pt][b][size=3][color=#000000][font=Times New Roman]Performance: For example, a nuclear reactor control system may have to sample the temperature of the core and process the data every 10th of a second. If the system is not fast enough to be able to handle interrupts from the temperature sensor every 10th of a second, then data will be lost and there is no way of ever recovering the data; the next time that the system receives temperature data, they will be the current temperature, not the reading that was missed. If the reactor is on the point of a meltdown, then it is critical that all relevant information be both received and processed as laid down in the specifications.
[/font][/color][/size][/b][/size]
[size=10.5pt][b][font=Times New Roman][size=3][color=#000000][/color][/size][/font][/b][/size]
[size=10.5pt][b][size=3][color=#000000][font=Times New Roman]With all real-time system, the performance must meet every time constraint listed in the specifications.[/font][/color][/size][/b][/size]
[b][font=Arial][size=10.5pt][size=3][color=#000000][/color][/size][/size][/font][/b]
[b][size=12pt][font=Times New Roman][color=#000000][/color][/font][/size][/b][b][font=Times New Roman][size=3][color=#000000][/color][/size][/font][/b]
[align=center][b][size=12pt][color=#000000][font=Times New Roman]Reliability[/font][/color][/size][/b][/align]
[color=#000000][font=Wingdings][size=7pt][b]u[/b][/size][/font][b][size=3][font=Times New Roman]If a program repeatedly and frequently fails to perform, it matters little whether other software quality factors are acceptable.[/font][/size][/b][/color]
[color=#000000][font=Wingdings][size=7pt][b]u[/b][/size][/font][b][size=3][font=Times New Roman]Software Reliability is defined in statistical terms as “the probability of failure-free operation of a computer program in a specified environment for a specified time.”[/font][/size][/b][/color]
[color=#000000][font=Wingdings][size=7pt][b]u[/b][/size][/font][b][size=3][font=Times New Roman]It is necessary to know how often the product fails. (MTBF)[/font][/size][/b][/color]
[color=#000000][font=Wingdings][size=7pt][b]u[/b][/size][/font][b][size=3][font=Times New Roman]When a product fails, an important issue is how long it takes, on average , to repair it. (MTTR)[/font][/size][/b][/color]
[color=#000000][font=Wingdings][size=7pt][b]u[/b][/size][/font][b][size=3][font=Times New Roman]Measure of Reliability:
MTBF = MTTF + MTTR[/font][/size][/b][/color]
[color=#000000][font=Wingdings][size=7pt][b]u[/b][/size][/font][b][size=3][font=Times New Roman]MTBF: mean-time-between-failure[/font][/size][/b][/color]
[color=#000000][font=Wingdings][size=7pt][b]u[/b][/size][/font][b][size=3][font=Times New Roman]MTTF: mean-time-to-failure[/font][/size][/b][/color]
[color=#000000][font=Wingdings][size=7pt][b]u[/b][/size][/font][b][size=3][font=Times New Roman]MTTR: mean-time-to-repair[/font][/size][/b][/color]
[color=#000000][font=Wingdings][size=7pt][b]u[/b][/size][/font][b][font=Times New Roman][size=3] [/size][/font][/b][/color]
[color=#000000][font=Wingdings][size=7pt][b]u[/b][/size][/font][b][size=3][font=Times New Roman]Software availability is the probability that a program is operating according to requirements at a given point in time. [/font][/size][/b][/color]
[color=#000000][font=Wingdings][size=7pt][b]u[/b][/size][/font][b][size=3][font=Times New Roman]Measure of Reliability:[/font][/size][/b][/color]
[color=#000000][font=Wingdings][size=7pt][b]u[/b][/size][/font][b][size=3][font=Times New Roman]
MTBF = MTTF + MTTR[/font][/size][/b][/color]
[color=#000000][font=Wingdings][size=7pt][b]u[/b][/size][/font][b][size=3][font=Times New Roman]Measure of Availability:[/font][/size][/b][/color]
[color=#000000][font=Wingdings][size=7pt][b]u[/b][/size][/font][b][size=3][font=Times New Roman]
Availability = [MTTF/(MTTF + MTTR)] * 100%[/font][/size][/b][/color]
[color=#000000][font=Wingdings][size=7pt][b]u[/b][/size][/font][b][font=Times New Roman][size=3] [/size][/font][/b][/color]
[align=center][size=12pt][size=4]北京地区对软件测试感兴趣的朋友可以加我qq交流:306513768[/size][/size][/align]
[[i] 本帖最后由 rendaoyuan 于 2007-3-30 11:37 编辑 [/i]]
200605200000 2007-3-29 14:15
学习中
rendaoyuan 2007-6-15 11:20
sdlkfj6
jialebihaidao 2007-8-30 07:50
有中英文对照就好了