The success of our clients and their projects is our main objective. For this reason, our process helps us identify and clarify the key aspects of the project.
During this initial phase, system requirements are collected to determine the feature set and needs of users. Spending enough time and creating thorough functional requirements documentation is critical during this phase. The functional specifications also define the corresponding tests that will be implemented during testing stages.
Functional Specifications Document
The purpose of this document is to define the functional specifications that that the system has to meet in order to accomplish the customer requirements.
The Functional Specification establishes the intended purpose of the SYSTEM, its associated constraints and operating environments, the operational and performance features, and the permissible flexibility in attaining those objectives.
General Requirements
Must the system fit into an specific housing? What type of motors must the drive be able to control? Must all components be on one side of the PCB for cost-reduction? These are some of the questions we will define in this section.
| Req ID | Description | Severity |
| Approach | ||
| GR1 | The subsystem must not include any housing. | |
| GR2 | The subsystem must not include any packaging. | |
| GR3 | The subsystem must be implemented using SMD components (only the connectors use thought-hole technology) | |
| Technology | ||
| GR4 | The subsystem must not include any housing. | |
| GR5 | The subsystem must not include any housing. |
Physical Requirements
In most cases one of the key design requirements for our customers is the form factor. This helps them have a perfectly integrated system. In this section we will define the dimensions and heat dissipation properties of the board as well as the connectors position and mounting method.
