Our Design Process
In every case our process begins with the Client approaching us with a problem or
an opportunity for which they need help. Our response is to work with the Client
and spend the time necessary to understand the Client’s needs to the point where
we can recommend a solution. In order to do this we work closely with each Client
to help them formulate a requirements specification which defines the Client’s needs
in detail. Once we understand the Client’s needs we are able to produce an estimate
so the Client can weigh the benefits and cost. If the Client decides to move forward
with the project we will produce a design specification which outlines how we will
satisfy the Client’s requirements and once we have a signoff from the Client work
can begin. To learn more about what goes into creating a requirements specification
for each of our services, read below.
Windows Software
Windows Software is best suited to applications where the user will regularly be
using the same workstation for long periods of time and ease of use and performance
are of the highest importance. Frequently used tasks should be easily accessible,
intuitive and require a minimal number of steps to complete.
Key Questions When Designing Windows Software:
- What is the primary purpose of the software?
- How many users will be using the software?
- Will the software be used from multiple work stations?
- Will the software require an internet connection?
- Will the software utilize a local or central database?
- Should users be required to login?
- Will this application need to interact with any hardware peripherals (i.e. Printer,
scanner, card swipe, biometrics, etc…)?
Web Applications
The biggest benefit of a web application is that it is accessible from any computer
or mobile phone with a web browser and an internet connection and they are also
well suited to large numbers of users over a distributed area where installing software
on each workstation isn’t practical. Because the application is widely accessible
security is of the utmost importance and you will often have users with different
security privileges depending on the role they play.
Key Questions When Designing Web Applications:
- What is the primary purpose of the web application?
- How many users will be using the application?
- How many web pages will you need?
- What sort of information will be on each web page?
- What sort of information will need to be stored in the central database?
- Which real-time reports will be needed to manage the application?
- How many different security roles will be required?
Self Service Kiosk Applications
Self Service Kiosks have a wide range of applications and all have the potential
to save you man hours and increase sales. Self service kiosks are well suited for
providing a service to the public when an attendant is unavailable or over-utilized.
Simple intuitive touch screen interfaces allow even the most novice user to interact
with your kiosk and do business with little to no assistance.
Key Questions When Designing Self Service Kiosk Applications:
- What is the primary purpose of the self service kiosk application?
- How many kiosks will be required?
- What does the user demographic look like?
- Which real-time reports will be needed to manage the kiosks?
- Will the kiosk be accepting cash or credit card payments?
- Which peripherals will be integrated into the kiosk (i.e. Card Readers, Receipt
Printers, Barcode Readers, Thumb Prints, Facial Recognition, Webcams, Card Dispensers,
etc…)?
Windows Mobile Applications
Mobile applications are best suited for doing business on the go and when ease of
accessibility is a top priority. We can take your mission critical applications
mobile and optionally make them work both when connected to the internet and when
offline. Mobile applications are more about convenience on the go than ease of use
since screen and keypad size on a mobile phone are limited.
Key Questions When Designing Windows Mobile Applications:
- What is the primary purpose of the mobile application?
- How many users will be using the mobile application?
- Which models of mobile phone should the application run on?
- How many users will be using the mobile application?
- Will the mobile application require an internet connection?
- Will the mobile application utilize a local or central database?
- Should users be required to login?
APIs and Web Services
APIs (Application Programming Interface) are the ideal way to share data and services
and occupy a variety of online spaces simultaneously. By publishing your API, you
give potential and existing partners the ability to create applications that use
your data and engage customers in new ways. When developing an API it’s important
to plan which data and services you want to share and who should have access.
Key Questions When Designing APIs and Web Services:
- What is the primary purpose for publishing your API?
- Which data and/or services do you want to share?
- Who should have access to your API?
- How much usage will your API receive
- Do you intend to charge for
- Which real-time reports will be needed to manage API usage?
- How will you share the API with users?