The analysis process commences with several preliminary requirements analysis meetings held with the appropriate customer representatives. eWave's project manager and team meet with all relevant personnel, as prioritized by the customer.  The product of these meetings is a specification document characterizing all features of the system and how they will be implemented. The spec document is presented in a DR (design review) meeting for client approval.

The process includes: 

• Studying the current system/workflow 
• Analyzing competing/parallel systems and businesses 
• Defining users, scenarios, services and modules 
• Characterizing APIs (application programming interfaces) with existing systems 
• Customizing the system to meet business needs and project objectives

The user interface is an essential factor for end users. We believe that the “package design” of a system is a key to its usability and the ease of deployment.
We create the UI assuming that end users have only basic knowledge in computer use and Web browsing, emphasizing simplicity, user friendliness, and intuitive interface.

The UI design process includes: 

• Understanding customer preferences and needs 
• Studying end user processes 
• Creating UI sketches 
• Presenting the UI concept to the customer 
• Creating UI scenarios of main screens 
• Developing the detailed design of all system screens 
• Presenting a mockup version of the product. The mockup presents the system screens and workflow without the business logic. This phase enables the client to review and confirm the design prior to system development.

eWave's user-centered design approach, which is implemented in every project, is a philosophy and a process. It is a philosophy that places the user at the center; it is a process that focuses on human cognitive factors (such as perception, memory, learning, problem-solving, etc.) as they come into play during interactions with the application.
 
The UCD focuses on both usefulness and usability.
• Usefulness:  Relates to relevance; making sure that the functions, information, etc., match what the user actually needs.
• Usability: Relates to ease-of-use - a simple concept, but not always easy or intuitive to implement.

International Organization for Standardization - ISO 13407 and ISO TR 18529
The UCD implements two worldwide ISO standards, which, when combined, offer a complete solution to all aspects of UI. ISO 13407 and ISO TR 18529 standards address the product development process, with specific focus on the design process.

ISO 13407 (1999) Human-centered design processes for interactive systems
This standard provides guidance on human-centered design activities throughout the development lifecycle of interactive computer-based systems. It is a tool for managing design processes and provides guidance on sources of information and standards relevant to the human-centered approach.

Human-centered design is described as a multidisciplinary activity, incorporating human factors and ergonomics knowledge and techniques with the objective of enhancing effectiveness and efficiency, improving human working conditions, and counteracting possible adverse effects of use on human health, safety and performance.

The following cycle outlines the activities in this ISO standard: 

 
ISO TR 18529 (2000) Ergonomics of human-system interaction - Human-centered lifecycle process descriptions
This technical document contains a structured and formalized definition of the human-centered processes described in the ISO standard to:

1. Ensure HCD content in system strategy
2. Plan and manage the HCD process
3. Specify the user and organizational requirements
4. Understand and specify the context of use
5. Produce design solutions
6. Evaluate designs against requirements
7. Introduce and operate the system