User Test Plan for the ObservationsPreparation Subsystem. Authors: L.Testi, A.Bridger Version: 2004-june-1 The goal of the user tests is to provide feedback from potential users in order to reduce acceptance risks and to ensure that the subsystem will adequately cover the needs of different type of projects. These tests will be performed during the development of the software. it will be important, before each test session, to define the focus of the tests in such a way to avoid useless testing of software components that are not yet mature enough for testing and to identify the areas where feedback from testers is required. The focus of each test session will be identified by the subsystem scientist and the subsystem lead in consultation with the team. TestCases have been (are being) developed to guide the tests, however, at least for the first rounds of testing, these TestCases will be much more detailed than the real tests, which will instead be limited to the test focus identified for each test session. The proposed structure of the test plan is based on one major (UserTest or UT) and one minor (AuxilliaryTest or AT) test session each year immediately following the major and minor software releases. The scheme is such that there will be four major test sessions (UT1 to UT4) and three minor test sessions (AT1 to AT3), UT4 will be the last test session after the ReadinessReview and prior to the Preliminary Acceptance (no minor test session is foreseen after UT4 in this plan); given that RR and CPA are very close, this last test session may happen just after PAR. The major test sessions are expected to provide timely feedback to the team for possible upgrades in the following minor release of the software. Minor session will be followup of the major session possibly providing further tests and input to the team toward the next major release. Major test sessions will be performed by a team of testers coordinated by the subsystem scientist, the team should not bee to large, typically 8 people or less will be enough. Minor test sessions will be performed by a reduced team of 2 people: the subsystem scientist and the SSR test plan coordinator. The results of each major test session will be collected in a written report following a discussion within the test team, each tester will be required to provide written feedback in the form of answers to a questionnaire. For each minor test session the subsystem scientist will provide a short written summary to the team. The results of both test sessions and the possible response of the team may be discussed at the CDR preceeding each major release, if required. DueDate Software TestPlan Comments Development ------------------------------------------------------------------------------ 2003-09-30 Test Focus - Is your favourite ALMA **Complete for R1 defined project supported by the current design? If no explain why, what are you missing, etc. - Items for test focus: see below - Note: it is essential to define the focus in such a way to keep the tester effort relatively low, otherwise it will be difficult to find the testers... 2003-10-01 Major SW **Complete Rel - R1 ******************************************************************************** 2003-12-01 UT1: MajorTestSession - TestTeam: LTe, DSS + few 2004-01-09 Report Ready (2-3) selected individuals **Complete - Expected effort: <=2 days in period Dec01-Dec19 ******************************************************************************** 2004-01-10 Test Results **Complete discussed within the ObsPrep team Test focus for - This should not be very different minor test from the major test 2004-04-01 Minor SW **Complete Rel - R1.1 2004-07-08 CDR2 ******************************************************************************** 2004-07-19 AT1 MinorTestSession - TestTeam: LTe+DSS+PS (PS = Philippe Salome) 2004-08-31 Report Ready Effort: <=1 day/tester Test goals: Review interface design, Review project overview information, Evaluate changes made from recommendations in Test1, Check preliminary implementation of some expert mode capabilities. Test will run to 2004-07-30. - The new granular requirements will be graded by testers at the end of their test. 2004-08-31 Possible feedback into next SW release discussed ******************************************************************************** Repeat same scheme for R2 (UT2) R2.1 (AT2), R3 (UT3), and R3.1 (AT3) test focus and test group will change according to the needs. Note that R3 is the realease originally scheduled for beta-testing. It is expected to keep the test team small and mainly restricted to ALMA or "close-to-"ALMA people for R1 and R2, a larger beta tester group may be considered for R3 or R3.1. A final major test session (UT4) is expected after R4 and before or around CPA. This plan should be considered as a living document and will certainly be modified to refine test focuses and test dates. Test Focus for UT1: - OT appearance and basic project setup. * Note: only some very basic functionalities will be available the idea is to have a feedback on the GUI design and on the project tree presentation and how all this fit for different kind of projects. - Save/recover programmes - Insert very basic inputs via GUI - Creation of SBs - Test the ETC Test Focus for AT1: TBD Test Focus for UT2: TBD Test Focus for AT2: TBD Test Focus for UT3: TBD Test Focus for AT3: TBD Test Focus for UT4: TBD