Studio:What are some specific methodologies or efficiencies enabled by STRIDE?

STRIDE’s interface-centric approach and ability to break dependencies promotes parallel development. First, developers can verify and pre-integrate components without waiting for missing underlying dependencies. Customers employing this approach, upon availability of all components, often achieved successful integration on their very first attempt.

In addition, as long as application interfaces have been defined, STRIDE supports parallel development of features and tests – one set of developers can focus on feature implementation, while another group focuses on developing the associated test scripts. Test developers can implement and verify scripts even without the availability of software; they can simply model the interfaces-under-test to verify their test scripts.

STRIDE enables engineering organizations to incorporate agile methods like test-driven development and continuous integration into the development process. STRIDE Studio™, through its ability to interactively exercise code without writing any test code, promotes rapid code/test/refactor cycles. Developers can thus practice agile principles as part of their daily development activities. Continuous integration is enabled via STRIDE with continual regression testing, by reusing and automating developers’ test cases.

STRIDE also provides an effective strategy for verifying and integrating the deliverables from various external software sources, such as outsourcers, third-party vendors, and remote developers. By specifying and providing a uniform framework (a set of policies, conventions, guidelines, and templates), these parties can deliver test scripts along with their software. By adhering to the framework, these scripts can be easily re-executed and reused as part of a collective regression suite. In addition, companies can provide STRIDE test scripts to external parties as conformance or acceptance criteria.