SAS® Data Query and Edit Checks with HTML5 - PharmaSUG

More documents

Recommendations

Info

5.4 Syview OQ - Query Data Step Instruction Expected Result 1 1. Open a web browser and navigate to the location of the Syview installation. An example is: http://sasserver 2. Enter the following value for the user name - password such as "admin - admin". 3. Click on the "Login" button. 4. Verify that the main screen "SAS Data Management" is displayed. 2 1. Select on CM dataset from the hierarchy and then click on the View button on the right panel. 2. Verify that the "View Data" screen is opened, note the total observations this dataset has. 3 1. Click on the Back button on the bottom. 2. Navigate to the menu Tools > Query. 3. Verify that the Query SAS Dataset screen is displayed. Verified that the main screen "SAS Data Management" is displayed. Verified that the "View Data" screen is opened. Noted the total observations this dataset has. Verified that the Query SAS Dataset screen is displayed. 4 Does Actual Result Match Expected Result? Yes No Yes No Yes No Result Pass Fail Deviation Initial/Date Pass Fail Deviation Initial/Date Pass Fail Deviation Initial/Date The test script is written to function with sample data that comes with the installation. This allows the testing to verify specific functionality with the ability to verify against expected results. This can be time consuming so the project manger needs to allocate resources and sufficient time to ensure for comprehensive testing, including all key functional area. STEP 4 – Performance Qualification (PQ) – The performance qualification evaluates how the system performs on large datasets with multiple simultaneous users. It simulates a stress test of the system including three users accessing a large set of data. A portion of the PQ test script is shown here: 3 Syview 4.0 PQ – Performance Qualification The PQ testing will be performed on a dataset that is considered one of the largest data that users will encounter. It will also simulate three simultaneous users to push the system to see how well it performs. When processing large files between multiple users, it should not take more than two minutes for each request. There will be three users with the first one being the administrator. The second and third users of this test will be assigned at the time of testing and is referred to in this document as “user 2” and “user 3”. It is recommended that the script is written with general descriptions and user roles since the actual testing may require changes and specific user assignments. This test is based upon the OQ so some instructions can be reused. The main differences is that the PQ test scripts are applied with multiple users upon large data.
Validation of software is a standard process that can be applied in a similar way for different implementations. What makes this validation project unique is that there are many graphical user interface elements compared to the traditional batch processing of SAS. Thus, this process requires more testing with interactive user interactions via a web browser. The testing included detailed instructions for the navigation and selection of graphical elements that are more visual compared to a pure scripting test script. SOFTWARE IMPLEMENTATION Syview can be implemented for data managers so that they can query SAS datasets without having to write SAS scripts. Access to the SAS datasets can be centrally managed by an administrator. Therefore, Syview provides a managed approach to SAS data access, while also extending to data managers a way of easily querying SAS datasets. Moreover, data managers cannot use Syview to write-over existing SAS datasets. They can only query SAS datasets and are not allowed to edit or update the same data. This allows for Syview to comply with 21 CFR Part 11 regulations from a change control perspective. In this particular implementation, the software was deployed on a Windows 2003 server running SAS 9.2. The core technology is SAS but since this is delivered to a thin client, a CGI program was used and that was developed in C. The remaining logic on the server was SAS code used to generate HTML5, which will described in the following steps. STEP 1 – User Access For secured data access, the first screen that is presented is a user login screen. The SAS program on the server is invoked to generate the HTML5 code for the login screen. This HTML code contains only a couple of user input fields. User Name Password Forgot Password? The HTML also contains calls to a couple of JavaScript functions to perform error checking. This method of checking is more responsive for the user since the software does not need to connect to the server to validate missing credentials. The JavaScript is inserted along with the HTML so it is delivered to the browser at the same time. 5
Page 1 and 2: PharmaSUG2012 - Paper AD03 SAS ® D
Page 3: This form is a useful tool for comm
Page 7 and 8: … endsubmit; This method efficien
Page 9 and 10: The HTML table includes a call to a
Page 11 and 12: The use of a popup calendar is acco
Page 13 and 14: The metadata for this query is mana
Page 15 and 16: Unique Subject Identifier (usubjid)
Page 17: CONTACT INFORMATION Your comments a

SAS® Data Query and Edit Checks with HTML5 - PharmaSUG

Create successful ePaper yourself

Delete template?

Save as template?