Задача: Генерация системных требований

This task generates the system requirements for the "system to be" from the stakeholder requirements.

Дисциплины: System Engineering Requirements

Взаимосвязи

Родительские практики выполнения	Системная инженерия - прецедентный подход
Роли	Основной исполнитель: Инженер требований	Дополнительные исполнители: Заинтересованное лицо
Входы	Обязательный: Спецификация требований заинтересованных лиц	Необязательный: Нет
Выходы	Документ интерфейса управления Спецификация системных требований

Основное описание

The main objective of this task is to ensure that the System Requirements are expressed in a formal, structured, verifiable, unambiguous manner (this is the Engineering part of the process), to maximize the chance that the system to be developed is exactly the system the Stakeholders need (asked for).

This is a definition of the solution to the problem, at the level of what the system has to do, rather than how it will do it (which is design). It is likely that changes will be proposed during this task.

Шаги

Create structure for specification

Decide what structure will be used for the System Requirements Specification. If you are not using an existing specification, then you should preferably follow a template or a previous specification as a starting point. Create the outline specification following the chosen structure. You may be adding to an existing specification, in which case the default would be to use that.

Transform stakeholder requirements

Review the Stakeholder Requirements Specification and Use-Case Model. Convert problem-oriented statements into solution-oriented statements.

For example, from:

"The mechanic shall be able to update the EMS software."

To:

"The EMS diagnostic equipment shall have a function for downloading a selected EMS software version onto the EMS via the diagnostic interface."

Constraints are often transferred without change. There may be many system requirements per stakeholder requirement – and vice-versa.

Generate interface control document

Review the Stakeholder Requirements Specification and Use-Case Model to identify external interfaces. Capture the specification of these interfaces in the Interface Control Document.

Дополнительные сведения

Руководства по инструментам	Creating Documents in DOORS Creating Requirements in Rhapsody Creating Traceability Links in Rhapsody Exporting Requirements Traceability Links from Rhapsody to Doors Importing Requirements from DOORS into Rhapsody Maintaining System Requirements in DOORS Maintaining the Glossary in DOORS