Skip to main content

Requirements Engineering

We support you in translating your visions and goals into clear, consistent and complete specifications of our future solution.

The Challenge

Usually, our clients have a vision about their future solution: they know what goals they want to achieve and what issues they want to solve. Now they need to explain to solution designers what they want and how they want it. They need to fully and properly understand all requirements in order to design a solution that transforms the client’s vision into reality.

The processes and activities to translate imprecise, incomplete needs and wishes into complete, precise and formal specifications which act as the major guideline for developing the envisaged solution are called Requirements Engineering.

In the waterfall model, Requirements Engineering is presented as the first phase of the development process. In agile development, Requirements Engineering is applied iteratively during development and continues through the lifetime of a system.

Our Approach

In order to enable our solution designers to transform our clients’ visions into reality, we help and support clients in defining, documenting and maintaining

  • business processes which provide a business perspective, describe business activities or needs and are independent of technology,

  • use cases which describe the actor’s or user’s perspective, define software functions and describe the behavior of the technology, and

  • functional, technical and other requirements.

Our Services

Requirements exploration: icentic’s consultants inquire the client concerning his needs and wants regarding the target solution.

Requirements analysis and negotiation: icentic’s experts support the client to identify use cases and requirements (including new ones if the development is iterative) and resolve conflicts with stakeholders. Both written and graphical tools are successfully used as aids.

Requirements specification: icentic’s experts document use cases and requirements in a formal artifact called a specification, which will become official only after validation. A specification usually contains both written and graphical information.

Requirements validation: The client checks if the documented requirements and models are consistent and meet his needs. Only if the final draft passes the validation process, the specification becomes official.

Requirements management: icentic manages all the activities related to the requirements since inception (including changes and extensions).

Examples

For one of the world’s leading manufacturers of heating and solar products, icentic’s consultants defined and specified the functional and technical requirements for the end used IoT device (gateway) of a new smart energy platform, and recommended and specified the service architecture and processes for the 1st and 2nd level support organization.

For a German alternative energy services provider, icentic’s experts identified, described in BPMN and mapped according to eTOM all relevant business processes for a new IoT connectivity and asset management platform, compiled and formally described in UML all relevant uses cases, and derived all requirements enabling our architects to design the target solution.

In the waterfall model, Requirements Engineering is presented as the first phase of the development process. In agile development, Requirements Engineering is applied iteratively during development and continues through the lifetime of a system.

Please contact us by to info@icentic.com or phone for more information or to schedule a call.