A requirements analysis should constitute the starting point of every software development. However, this analysis depends mostly on what you as a customer have already invensted in preparing your project. Together with you we will analyse the possibilities and how best to achieve the desired results.
1. You already have a rough idea which kind of software you require? In this case it makes sense to arrange a non-committal appointment first in order to discuss the feasibility and to clarify open questions. Afterwards, we have to define in a workshop all the necessary functions the software shall provide. These functions are then recorded in a requirements specification. From this we then develop a technical specification that serves as a basis for the development. Furthermore, the technical specification helps us to submit an individual offer to you.
2. If you already have a requirements specification we should arrange a non-committal appointment first in order to talk about the requirements specification, incorporate new suggestions and clarify open questions. After that we would start preparing a technical specification.
3. You are already well prepared and dispose of a technical specification? This constitutes the ideal, but also rarest case. Here, it would be sufficient to make a further appointment after having reviewed the technical specification in order to discuss further proposals and other open questions.
You must not underestimate the relevance of this step! Software is something very individual and everybody has his own ideas of it. Especially when it comes to the operation and execution of processes the communication between you and us is essential so that we get a detailed impression of your ideas in order to develop the best possible software for you.
A possibility to reduce the requirements analysis is the agile software development (also see development).