The Requirements Specification
"In the beginning was the Word ..." (Gospel of John, Chapter 1)
At the start of every project, we want to hear from you what you have in mind. We want to understand your business model and the in-house processes that make your company unique. Ideally, you have already put together a requirements brief for us describing the planned project – very much in the spirit of "In the beginning was the Word ..."
The Functional Specification with Effort Estimate and Cost Proposal
We respond to your requirements with a functional specification (Software Requirements Specification). In it, we describe the conceivable implementation by breaking individual activities down into different phases of the development process. You will receive a quote from us in advance for drawing up the functional specification. There are essentially two approaches:
The Waterfall Model: In this model, each phase has a defined start and end point. Milestones mark the intermediate steps. The waterfall model is generally advantageous where requirements, deliverables and workflows can be described relatively precisely during the planning phase.
The Spiral Model: Here, we aim to integrate risk assessment into the software development process on completely new territory. The spiral model describes software development as an iterative process involving cyclical repetition of the individual phases. The project gradually approaches its goals, even as those goals evolve over the course of the project (also known as an incremental and iterative process model).