What is the difference between a Software Item Spec and a Task in Ketryx?

What is a Software Item Spec in Ketryx?

A Software Item Spec is a configuration item that describes how a system or software will meet requirements. It provides detailed descriptions of functionality, behavior, and characteristics necessary to fulfill stated requirements, bridging high-level requirements and actual implementation. Software Item Specs are part of the software architecture and detailed design phases of development.
Software Item Specs are "long-lived" items with both "Introduced in version" and "Obsolete in version" fields, meaning they span multiple versions.

What is a Task in Ketryx?

A Task is a configuration item that describes "What needs to be done to make it happen?" The task is the work that must be completed to implement or support the specification. Tasks are "point-wise" (short-lived) items with only an "Introduced in version" field, making them relevant only to the specific version they're introduced in.

What is the key difference between them?

Software Item Specs define how it should function, while Tasks define how to implement those specifications. The software item spec is akin to the design, and the task is an action item. Software Item Specs are part of the design documentation, while Tasks are implementation instructions that don't appear in regulatory submissions.

How do Software Item Specs and Tasks relate to each other?

In Ketryx's traceability model, a Software Item Spec is implemented by Tasks, and Tasks implement Software Item Specs. This relationship creates clear traceability between design specifications and implementation work.

When should I use a Software Item Spec versus a Task?

Use Software Item Specs to define your software's detailed design. Use Tasks to assign developers specific implementation work that needs to be traced back to requirements or specifications, but shouldn't appear in regulatory documentation.

Related to

Configuration Items