CSA (Computer Software Assurance) A move from Traditional CSV

Traditionally, FDA’s CSV (Computer System Validation) focuses on documentation, followed by testing activities, assurance needs, and critical thinking. Whereas, in the new CSA model it focuses first on critical thinking and then on assurance needs, testing activities, and documentation

CSA Approach:

• Critical Thinking: Risk definition for each Software Features
• Assurance: Demonstrate if the feature & functionality is working as desired
• Testing Activities: Leverage and define the different test methods like Scripted and Unscripted testing

The new FDA guidance intends to focus on more testing and considerably less documentation. Let us have a brief overview of the FDA’s CSA approach for Scripted and Unscripted testing.

Testing Activities – Scripted and Unscripted Testing:

When we go by the definition of Unscripted Testing, it is a type of software testing in which the tester is free to select any possible methodology to test the software. As per the typical definition of unscripted testing, software developers / Testers use their skills and abilities to test the software developed by themselves.

Let’s take an Example of Scripted and Unscripted Testing:

When we consider of LMS (Learning management software) and applying critical thinking

• Training need generation, Training Session management can be considered as unscripted testing.
• The scenario wherein a production executive working in critical area has been failed 3 times in the certification, the executive should be automatically barred from entering the production areas. Since, this has an impact on product quality, we need to check this feature as high risk and must need to execute the proper test script and record the evidence. This scenario will be considered as scripted testing.

During unscripted testing there is always a possibility that few scenarios are missed by the Developers / Testers. So, performing Unscripted testing during the Requirements Phase involving the Business User’s will makes Developers / Testers to test the features, allows them to think more logically and help in adding them as new and required features. To achieve the assurance of such software features, imagine the adoption of LOW CODE PLATFORMS and applying Critical thinking and Unscripted Testing

FDA is proposing the adoption of the Smarter Techniques in Software delivery. Research firms like Gartner Predicts that by 2024, low-code application development will be responsible for more than 65% of application development activity

LOW CODE PLATFORMS:

Low-code Delivery approach helps organizations deliver software as efficiently by maximizing reuse and minimizing the need for hand-coding. Freed from the complexities of low-level implementation details, teams can focus on high-level, strategic work that adds business value – with increased creativity and collaboration.

Imagine a situation where business User dictates user stories and the Software service provider develop the software on the fly. The adoption of LOW CODE delivery approach will add value to the CSA Approach.

How Low Code Platform can help you achieve the CSA approach bypassing the Traditional Software service model?