Noat define and write functional and technical specifications for various scenarios, mainly for the development of new software systems or the understanding of current legacy software systems. Think of noat as providing a similar output to structural engineers or architects – the blueprints or plans. These functional specifications and technical specifications can then be used by our clients as a
development plan for their project, reference material to maintain their systems or as due diligence confirming the value or the functionality of their systems. The formation of noat is relatively new, however the core team has been working together for over ten years so we have an abundant wealth of experience and expertise to rely upon. Noat will empower our clients by enabling them to understand the split between functional and technical design and the implementation of these specifications – whether by an in house team or via a third party (potentially offshore) development team. You don’t need to have the specifications developed by the same organisation as the development and depoyment – in fact it’s better to use two different organisations for better control. Even though noat has come from the software world we actively pursue projects outside our software background developing and defining logical documentation for a range of business processes and policies. High quality technical documentation is often a casualty of the development process. This happens because the production of documentation is typically left to development companies that may either lack the motivation or skills to produce comprehensive technical documentation, or attempt to reduce overheads on the project by glossing over documentation. This can adversely impact both effective planning and your ability to manage and maintain the software upon delivery. We therefore believe that separating the production of IT documentation from the software development process not only produces higher quality IT documentation, but also better software systems. Comprehensive planning and documentation should include:
System architecture
API design specifications
Integration specifications (where required)
Functional design specifications
Technical design specifications
Test plans
The legacy of poor documentation
Because developers may gloss over essential documentation stages, companies can be left operating and maintain expensive legacy software that is not fully understood by company employees, is not leveraged to its full potential, and that may even be redundant. Assessing existing legacy software, plugging documentation gaps, and potentially leveraging the software for additional functions can significantly impact the value that this software offers your company. What we offer
With extensive experience in software development and the creation of technical documentation, noat is able to provide the following services:
Technical document writing and planning
Legacy systems assessment
Consultancy
Project management
