topleft
topright

Login Form






Lost Password?
No account yet? Register
How We Work PDF Print E-mail

ImageHow we work with you depends very much on the nature of the product development . Electrical systems tend to be very well defined prior to development however software or electronic products may be loosely defined as a concept or vision. Over many projects we have carefully adapted our processes both to fit with ISO9001, and just as importantly to offer flexibility,excellence and dynamism in our designs. 

We can offer many advantages over 'in-house' development due to our focus, broad experience and skills, efficiency and disciplined approach.

 

Our software development team works to the following principles:-

  • Simplicity
  • Projects are built around motivated individuals, who should be trusted
  • Customer satisfaction achieved by rapid, continuous delivery of useful software
  • Working software is delivered frequently (weeks rather than months)
  • Working software is the principal measure of progress.
  • Even late changes in requirements are welcomed.
  • Close cooperation between clients and developers
  • Clear, regular communication is essential
  • Continuous attention to technical excellence and good design.
  • Self-organizing teams
  • Regular adaptation to changing circumstances.
  • We hold project post-reviews to ensure continual improvement.

 

Project inputs

We can begin work based on any of the following being supplied:-
  • Draft outline of concept or idea (feasibility)

    This is where a concept exists that may or may not be technically possible. Our role would be to capture the requirements and prove the concept. The outcome could be a feasibility report detailing any technical limitations and budgetary costs for the product and/or a physical prototype. A concept model can be used to generate initial interest in a product or obtain quick feedback on its suitability, particular features or usability
  • Marketing Requirements or Product Requirements and features

    Our role here would be to produce a functional requirements specification to detail how each feature would work prior to any development work beginning. The level of detail would depend on the size and complexity of the project. After the functionality is agreed, we would propose design options and encourage frequent prototyping and demonstration of ideas throughout the development as these often have a much more significant impact than a specification. We have a particular interest in user interfaces and the usability of a product.
  • Detailed Product Specification

    This is where a highly detailed specification exists which the product can be directly designed from.

Last Updated ( Thursday, 07 June 2007 )
 
< Prev   Next >
(c) 2007 All Rights Reserved. Practical Control Ltd. Designers of Electronics, Embedded Software and Systems