Search Results for "remote software automation"

Multi-Syntax-Version and Multi-Implementation API reference documentation generator. Supports local and remote sources.

The ‘setupdocx‘ provides a control layer for continuous documentation by the simplified creation, packaging, and installation of documentation. The provided commands are distributed as entry points and optional base classes for further customization into 'setup.py' - setuptools / distutils. Manages arbitrary document templates for the supported builder, supports multiple builds with arbitrary document layouts, designs, and patched contents. The current release supports the following...

Professional environments focus on high development standards in Source Code Management. E.g. by usage of server side commit hooks to check for minimum acceptance levels on code and documentation quality including commit message structure and content. TortoiseSVN offers only a free form text field to edit inside the Commit Dialog. Developers might recall situations when struggling with commit message structure and fighting the server side commit hooks instead of focusing on message...

SLOCCount is an easy-to-use tool that counts Source Lines of Code (SLOC). It auto-determines the language(s) (inc. C, C++, Ada, Assembly, shell, COBOL, C#, Fortran, Haskell, Java, LISP/Scheme, Perl, PHP, Python, Ruby, SQL). It also estimates cost & time.

A Python programming environment providing memory sizing, profiling and analysis, and a specification language that can formally specify aspects of Python programs and generate tests and documentation from a common source.

AFMS is an Artefact Management System to manage some of the artefacts appearing in the development process of a product. Artefacts are for example requirements, use cases or test cases. AFMS contains an artefact editor and a test execution tool.

Lightweight requirements management tool, with export, search and traceability functions. Uses plain text files as backend.

Doceval is a software that allows to discover the documentation included in a tarball. Basically it serves to identify if a given software project has doc at all and helps with a report to evaluate how much documentation it has and how good it is.

Gathering requirements should be fun. It's the brainstorming process refined. It shouldn't get in the way of productivity or creativity. Harvest is about gathering requirements in the most intuitive, least intrusive way possible.