Our business process is driven by a serious of documents that insure a smooth development process.

Requirements Document (Download require_template.doc)

A Requirements Document is a two-way insurance policy that assures that both you the client and Amino Integration understand the other's requirements from that perspective at a given point in time.

The document itself states in precise and explicit language those functions and capabilities a software system (i.e., a software application, an eCommerce Web site) must provide, as well as states any required constraints by which the system must abide. The SRS also functions as a blueprint for completing a project with as little cost growth as possible.

Specifications Document (Download spec_template.doc)

A specification document describes how something is supposed to be done. This document may be very detailed, defining the minutia of the implementation; for example, a specifications document may list out all of the possible error states for a certain form, along with all of the error messages that should be displayed to the user. The specifications may describe the steps of any functional interaction, and the order in which they should be followed by the user. A requirements document, on the other hand, would state that the software must handle error states reasonably and effectively, and provide explicit feedback to the users. The specifications show how to meet this requirement.

Specifications may take several forms. They can be a straightforward listing of functional attributes, they can be diagrams or schematics of functional relationships or flow logic, or they can occupy some middle ground. Specifications can also be in the form of prototypes, mockups, and models.

User Interface Design Prototypes

User interface (UI) prototyping is an iterative analysis technique in which users are actively involved in the mocking-up of the UI for a system. 

It is critical to understand that you don’t need to create a prototype for the entire system.  It is very common to prototype a small portion of the user interface, perhaps a single screen or HTML page, before moving on to implementing it.  

Testing and Validation Plans

Software verification and validation can reduce business costs and improve software performance. The core concept of validation is to prove that a system meets the requirements for its intended use. Done effectively, verification and validation accomplish more than compliance because they affect the cost of system ownership and, as such, are good for business.  This result is accomplished through two primary verification and validation outcomes: defect reduction and improved focus on the key purposes of the system.

Testing checklist:
1) Functionality Testing
2) Usability testing
3) Interface testing
4) Compatibility testing
5) Performance testing
6) Security testing

Although there may be several ways to test a particular area of functionality, tests should ensure, at a minimum, that the most common use of the functionality is exercised. In other words, be sure to test the primary intended use of the system before testing less-likely usage scenarios.

Contracts (Download amino.contract.doc)
Review a sample of our project contract.  

  Learn more about Advice and Planning

    Fill out a  Quote Request Form

    Contact us Via Email Form

    See Some of our Work

.