Methodology
The path from the customer's presentation of a problem to the customized start of operation of a software solution is long and often times very complex.
Our systematic approach complies with internationally accepted standards on the basis of standard IEEE 830 Software Requirements Specification (SRS) of the Institute of Electrical and Electronic Engineers. The base structure that is specified by this method is the acceptance of the customer requirements and the description of the development requirements with regard to the software that is to be delivered.
1. Research and Analysis
The exact definition of a project is frequently a critical issue. That is why trying to understand the individual corporate philosophy is the basis of any project work. Understanding the corporate philosophy will lead to an understanding of corporate-specific processes and also to an understanding of the corporate identity.
In the first phase we -in cooperation with the client- collect and assess all available information in regard to the market situation but we also evaluate the functional and technical aspects, thereby creating a common, comprehensive understanding of the project goals and conditions.
The definitions of the tasks should be catering to the individual users. They should be phrased accurately but not too restrictively or else the opportunity to discover innovative solutions is already voided in this early stage of the project.
2. Conception and Strategy
After a thorough analysis of the problem and its environment in the first phase, the second phase is all about turning up solutions to solve the problem. It is a phase of producing ideas by reviewing the analytical results and by anticipating potential solutions. It is in this stage of conception that we create a wide spectrum of rough solution alternatives. The structured data of the preceding research and analysis serves as the basis for this process. The goal is to break down the superordinate solution concepts into partial solutions and to join together the details to achieve a coherent master plan.
The goals as pronounced by the project definition, frequently a bundle of complex, interwoven issues is thereunto being restructured and partitioned into main and auxiliary functions, thereby turning into a manageable affair for all instances. Once that a solution approach has been found for individual details, the detail solutions can be joined together in consideration of the previously developed conception briefing.

