Solidware Resources
Solidware Resources
Brochures
SWaudit for Java, Version 2.0, Product Overview
SWaudit for Java Version 2.0: Automating Intelligence
SWaudit for Java now now includes dependency mapping, advanced architectural integrity analysis and enhanced analytics, for a better and more action-oriented understanding of project risk than ever before.
» Download now
Open Source Report
Software Quality Audit of Apache Ant 1.7.0
A sample report that uses SWaudit for Java to assess the quality of the open source build tool, Apache Ant 1.7.0.
» Download now
Investor Brief
Explore Solidware's Market, Vision, Technology, and Corporate Horizon
Request our 1-page investor briefing, and begin a conversation with Solidware concerning
the opportunity to invest in the future of software quality engineering.
»
White Papers
White Paper
Automating Software Audit: A Statistical Approach to Assessing Product Readiness
Abstract | Software projects face more challenges then ever in
effectively triangulating amongst features, schedule and quality. Shipping product
continues to be the driving force behind decision making often resulting in compromised
quality and or de-featured products. Escalating complexity and scale of software systems,
characterized by endless feature creep and deteriorating architectural integrity, are
drastically increasing the demands placed upon quality assurance professionals and
software test, i.e., the 'do-more-with-less' philosophy which has characterized the
dot-bomb era. Yet, a wealth of information exists within development environments
and within the code itself. This paper discusses a new approach which deploys Adaptive
Analysis Technology to derive quantitative quality indices and indicators, which
combined with finite element analysis (FEA) techniques provide an effective mechanism
to assess, visualize and navigate software quality attributes. Adaptive analysis can
be performed at any constituent component level within the context of the software
topology - from project-level assessment all the way down to identifying method-level
refactoring priorities.
» Download now