The Kinetic Jump site navigation header requires JavaScript to be enabled and the latest version of the Macromedia Flash Player. If you are you using a browser with JavaScript disabled please enable it now. Otherwise, please update your version of the free Flash Player by downloading here.

 
Iterative Software Specifications with AppLife DNA
Nothing in software is harder than deciding and communicating exactly what to build. Nothing is more critical to the success of a project than good specifications to develop against.

Far too many software teams treat their specification as a document. The problem with this is that documents are written for completion, and completed documents are not maintained. The document approach simply doesn’t compliment the software creation process.
Software Creation is Iterative
It’s built in stages, and as soon as it’s built, chances are good that there is room for improvement. The entire agile software movement is a testament to this. Too many software teams do not maintain their software specifications during development, putting their projects at risk. So we’re building a tool that transforms specification authoring from a document into an iterative process that lives and grows as your application evolves.

We are very excited about the application we're building and look forward to bringing you a solution that can make a profound positive impact on your software product team.

We anticipate a preview release in late summer.

Major features of AppLife DNA include:
  • Continuously capture and maintain software requirements
  • Prioritize requirements based on multiple factors
  • Maintain a road map or requirement implementation plan across software release targets
  • Generate documentation in multiple formats of your current application specification process.
  • Generate difference documentation that expedites the iterative specification review process
  • Intuitive and familiar user interface that's as easy to use as your favorite word processor
  • Search, sort, group, manipulate and report on your application requirements.
  • Create snapshots of your specification state for later comparison, merge or rollback.
  • Expand your requirements into specifications. Write explicitly about requirements and how your software will meet them.
  • Maintain specifications for multiple release targets simultaneously