With the real life test, it is not the intention to test the system behaviour in separate situations, but to simulate the realistic usage of the system in a statistically responsible way. This test mainly focuses on characteristics, such as effectivity, connectivity, continuity and performance of the system under test. To be able to test whether a system can handle realistic usage of it, that usage should be somehow specified. This also serves as a test basis and, in this context, is often referred to as the profile. The two most common types are: operational profile and load profile. The following questions may constitute an explicit part of the review within the framework of the real life test:
• Has the expected frequency of use been described on a function level?
• Has it been described for each type of user which functions may be carried out?
• Has it been described for each function when it will be used (daily, weekly, annually, daytime, evening)?
• Is there insight in the relationship between the various batch procedures across the (sub) systems?
• Has the configuration for the production environment been described (hardware, network, system software, DBMS, etc.)?
• Have specific requirements been set for the performance of online functionality?
• Is a distinction being made between the response time when starting up a function and the screen change within a function?
• Have specific performance requirements been set for data retrieval and manipulation?
• Have specific performance requirements been set for batch functionality?
• Have specific requirements been set for memory usage?
• Are there any requirements for the number of database calls per transaction?
• Are there any requirements for the maximum page and buffer sizes?
• Are there any requirements for the size of the application and/or the database?
• Has the expected frequency of use been described on a function level?
• Has it been described for each type of user which functions may be carried out?
• Has it been described for each function when it will be used (daily, weekly, annually, daytime, evening)?
• Is there insight in the relationship between the various batch procedures across the (sub) systems?
• Has the configuration for the production environment been described (hardware, network, system software, DBMS, etc.)?
• Have specific requirements been set for the performance of online functionality?
• Is a distinction being made between the response time when starting up a function and the screen change within a function?
• Have specific performance requirements been set for data retrieval and manipulation?
• Have specific performance requirements been set for batch functionality?
• Have specific requirements been set for memory usage?
• Are there any requirements for the number of database calls per transaction?
• Are there any requirements for the maximum page and buffer sizes?
• Are there any requirements for the size of the application and/or the database?
Thanks
0 comments:
Post a Comment