* Support holistic systems and software design to define and communicate how product, users, and the environment truly interact * Manage requirements from cradle-to-grave to ensure customer needs and quality expectations are met * Streamline compliance to reduce product risk * Engineer product lines to deliver variation and optimize commonality and reuse, improving time-to-market * Manage the evolution and release of strategic software assets * Address quality early and often by validating and verifying requirements and designs * Share best practices that can be easily tailored, managed and improved over time

* Subversion versions directories as first-class objects, just like files. * Copying and deleting are versioned operations. Renaming is also a versioned operation, albeit with some quirks. * Subversion allows arbitrary metadata ("properties") to be attached to any file or directory. These properties are key/value pairs, and are versioned just like the objects they are attached to. Subversion also provides a way to attach arbitrary key/value properties to a revision (that is, to a committed changeset). These properties are not versioned, since they attach metadata to the version-space itself, but they can be changed at any time. * No part of a commit takes effect until the entire commit has succeeded. Revision numbers are per-commit, not per-file, and commit's log message is attached to its revision, not stored redundantly in all the files affected by that commit. * Branching and tagging are cheap (constant time) operations. * Merge tracking, File locking, symbolic links can be versioned. * Executable flag is preserved. * …and a lot more!