Project Constraint

...

Document Properties Marker

override	false

Short Description	Project Constraints limit the options of a project.
Doctype	doctype	hide
Name	Project Constraint
ID	`project-constraint`
Suite	Software Development
Set	Software Development

hide

Parent

Parent Property

parent-doctype	topic
property-name	Name

Audience

Name List

doctype	role
render-no-hits-as-blank	true
property	Audience

Documentation Type

Name List

doctype	doctype-type
render-no-hits-as-blank	true
names	Q2 - Project
property	Documentation Type

Tags

Tag List

names	Software Development

Iteration

value	finished

hide

Sort Key

hide

Section

index	true
title	Description

Project constraints limit the options of a project. It is important to note them for further reference. Usually these constraints cannot be changed or cannot be changed easily. Everyone on the team should have quick access to this fundamental information.

Section

title	Properties

Transclusion

document	Note Box referencing common Document Properties
ids	Box

Section

level	2
title	Constraint Type

Define the type of the constraint for grouping and selecting constraints.

Compact Definition List

;technical:The constraint is based on technical issues.
;business:The constraint is based on business issues.
;legal:The constraint is based on legal issues.
;other:The constraint is based on issues not related to technical, business, or legal issues.

Tip Box
You may also remove the macro value and replace it with a Name List Macro and its own type.

-transclusionmacro

projectdoc

-

document	Note Box referencing common Document Properties
ids	Box

projectdoc-section

title	Sections

Section

level	2
title	Description

Describe the constraint that defines fundamental and unmodifiable facts demanded by the customer.

This includes technical constraints (software version, etc.), business constraints (business rules, etc.) and legal constraints (law, etc.). In opposition to requirements, project constraints do not change - and if they actually change, will demand a huge amount of work and may imply that a new product has to be started.

Section

title	Summary

Transclusion

document	Summary
ids	Designation

Section

level	2
title	Subordinate Constraints

You may subdivide a constraint and describe each part individually.

Section

level	2
title	Justification

Provide information about the reason or intent of the constraint. To know what is meant may make it easier to follow the demanded constraint.

Section

level	2
title	Impact

Describe the concrete impact on the project. What has to be done to meet the constraint.

Section

level	2
title	Consequences

Describe the consequences if the project fails to meet this constraint.

This description is only relevant if the consequence is different to "the project fails".

Transclusion

taget-heading-level	2
document	Document Sections
ids	standard-sections-bottom

...

Section

title	References

Section

title	Resources

Piwik Set Multiple Custom Variables

Name	Value
Department	projectdoc
Category	projectdoc-doctype
Type	swdev-analysis

Space shortcuts

Page tree

Docs

Support

Free Blueprints

Tooling for Blueprints

Free Extensions

Spaces

Plugins for Maven

Incubator

Libraries for Java

Incubator

Add-ons for Confluence

Tools

Support

Team

Legal

Versions Compared

Old Version 1

New Version Current

Key

About

Keep up-to-date!

Powered by