Depending on the Client's needs, we may offer the requirements analysis service at the following levels:

• system vision - defining the Client's needs and processes taking place at the company, which should be supported by the system; it offers support for your business in taking decisions about the shape of the future system,
• preliminary analysis - defining functional requirements for the system on a general level in order to arrive at a preliminary project cost estimation; it will also constitute an input for further works,
• specific analysis - defining highly detailed functional and non-functional requirements. The outcome of the analysis will be the background for designers, programmers and testers, used to produce detailed project pricing and timing.

Our approach to analysis is based on an iterative process through which:

• We familiarise ourselves with your business
  Based on the provided source materials, discussions and frequent consultation with you, we acquire knowledge of your goals, we learn about ideas and actual problems to set the direction for further development.
• We engineer the acquired information
  Together we search for optimal solutions for the encountered problems, we share our know-how and long experience with you, and we offer a fresh view of the issues we discuss.
• We model the system
  We use specific techniques in our work, to ascertain the exact requirements and facilitate management of requirements, including UML language. In modelling a system, we ensure that our deliverables are comprehensible both for the team of IT developers and for business representatives.
• We produce documentation
  We record our precise and clearly defined functional and non-functional requirements in requirements specification document based on IEEE 830; this document is later transformed into a form of contract between the authors of software and the client hiring them.
• We create a visualization system
  A general layout of the system scope and user interface (built as static mock-ups or an interactive prototype) will enable you to verify the current arrangements and "see" the system before implementation work begins.
• We offer support with follow-up
  An analyst's participation in the software production process does not end with drafting a requirements specification document. As the person who knows most about the client's requirements, our analyst will also attend the process of software development (implementation), supporting the team through consultancy, clarifying uncertainties and verifying the system's compliance with your requirements during the testing stage. If necessary, we may also offer change management (including documentation updates) during and after the project execution.

Requirements engineering is not necessary to build a system and you may perceive it as an unnecessary project cost. However, as shown by the experience of thousands of companies worldwide, engaged in various types of IT projects, this is an incorrect assumption. Requirements analysis is one of the initial project stages, to achieve the following results:

• minimise the risk of exceeding the time and budget allocated to the project,
• define the scope of work properly so that the system will meet your expectations and you will not have to introduce any post-implementation adjustments,
• verify the business processes taking place at your company, which will enable you to optimise them,
• create a better IT project implementation plan (define priorities for execution, divide the project into stages and prepare an execution schedule, estimate the system costs),
• receive professional system documentation, enabling you expand your system if necessary,
• freely decide who will execute your system and what technology they will use (our methodology does not impose any mandatory execution methods),
• retain in your organisation the business knowledge and IT knowledge you have acquired through the analysis.

Therefore, if you decide to choose the requirements analysis, you may be sure that your software will work properly after investing a lot of effort and money.

Would you like to learn more about our experience in the field of ongoing projects? Take a look at the section our competences