Almonix's development approach is based on many concepts.
Business requirements
A software application exists only to support one or many business needs. The starting point of our approach is defining them. Business needs are translated into software functional and non-functional requirements that are used to guide software development and validation.
Modeling
A model is a communication tool. Models provide stakeholders with an overview of the software to create. Stakeholders can use this overview to evaluate and modify the software before a single line of code is written.
A model is a complexity management tool. Models provide a simplified representation of a software to create. Each model adopts a particular perspective emphasizing specific elements of the software and omitting elements that are not associated with that perspective.
Agility
An agile approach is based on a set of principles. It must produce regular deliveries of functional software within short iterations. It must manage changes at any step of the development process. An agile approach favors a continuous contact with the client informing him regularly on the evolution of the project and allowing him to intervene at any time.
User Interface
The user interface is the communication point between the user and the software. An important part of the business value brought by the software resides on the way the user interacts with it. Knowledge about the user and his work environment will guide the design of the user interface in a way that the user will be able to achieve his tasks effectively and efficiently.
Software Architecture
A software is composed of a complex set of interrelated components. Selection and design of components responsible determining the software smoothness are critical tasks. Software architecture is a solution to the the problem presented by nonfunctional requirements.