USABILITY ANALYSIS | SINGLE POINT OF CONTACT | ADHERING TO MILESTONES | SMALL TEAM DEVELOPMENT | ONGOING INVOLVEMENT |
CLIENT PARTNERSHIP


IT IS VITAL TO YOU THAT ANY SOFTWARE APPLICATION AND SYSTEM BUILT FOR YOU IS ACCEPTED AND USED BY YOUR TEAMS. A KEY ASPECT OF OUR DESIGN AND BUILD PROCESS IS TO TEST THE USABILITY AND LOGICAL WORKFLOW OF THE SYSTEM AGAINST WHAT THE USER NEEDS TO DO HIS OR HER JOB PROPERLY.

Programs designed by programmers can be very unfriendly to use. That's why we always ensure that the non programmers of our team design the user elements of the software application. This is backed up by our liaising with your team to ensure that the system remains user friendly.

Our Usability Analysis consists of the following steps:

1. From the outset of the design and build process, we look at your existing systems and working methods and work out with you what should be kept and what should be dumped.

2. Depending upon the size of the project and your requirements, it is usually appropriate for us to meet with the users of the system to find out what works and doesn't work with the existing system.

3. From steps 1 and 2 we build out how the software application's inputs and outputs should be managed in terms of sources of input, screen layout, pre-population of screens, what assumptions should be made, tabbing order etc. In terms of outputs, we help the users define what is required in terms of display of information, report requirements etc

4. The look and feel of the screens is agreed so that the user interface is made as friendly as possible. In terms of output screen and report layouts, these are discussed and agreed with your teams so that we minimise frustrating the future users of the application system.

5. Online, context sensitive help is built into our software systems and applications and this backed up by good training.










 
JOIN US | COPYRIGHT | FEATURES | SITEMAP