UNIFIED DEVELOPMENT GUIDELINES
This disclosure relates to creating, facilitating, or otherwise managing unified development guidelines. Software for managing development guidelines can comprise computer readable instructions operable when executed to, in response to a trigger, identify a first guideline rule and a second guideline rule based, at least in part, on the trigger, where the guideline rules are at least partially stored in a central rules repository for a development group and each rule is associated with a validity period. This software then generates a development guideline using the identified first guideline rule and the second guideline rule.
1 . Software for managing development guidelines comprising computer readable instructions embodied on media and operable when executed to:
in response to a trigger, identify a first guideline rule and a second guideline rule based, at least in part, on the trigger, the guideline rules at least partially stored in a central rules repository for a development group and each rule associated with a validity period; and
generate a development guideline using the identified first guideline rule and the second guideline rule.
2 . The software of claim 1 , the first guideline rule comprising a released rule and the software further operable to receive a change to the released rule via an interface.
3 . The software of claim 2 further operable to:
provide the changed first guideline rule for review; and
change the validity period of the first guideline rule to begin after a review date.
4 . The software of claim 2 , the second guideline rule comprising a proven rule and the software further operable to reject proposed changes to the second guideline rule.
5 . The software of claim 4 , the proven rule associated with a plurality of triggers.
6 . The software of claim 5 , the proven rule further associated with a plurality of applications.
7 . The software of claim 4 , the software rejecting the proposed changes only upon reaching a time threshold in a development process associated with the trigger.
8 . The software of claim 1 , the development guideline associated with a plurality of triggers and operable to be reused for a second of the triggers, the second trigger associated with a different portion of the development group than the first trigger.
9 . The software of claim 1 further operable to present the generated development guideline to a plurality of clients associated with the trigger.
10 . The software of claim 1 , the trigger comprising a code implementation cycle.
11 . The software of claim 1 , the first guideline rule comprising a wiki that includes:
a unique rule identifier;
a keyword;
a priority field;
an approval status;
a responsible field;
a rule body; and
a rationale field.
12 . The software of claim 11 , the rule identifier comprising a first structure associated with a development process, a second structure associated with a rule number, and a version number.
13 . A computer implemented method comprising:
in response to a trigger, identifying a first guideline rule and a second guideline rule based, at least in part, on the trigger, the guideline rules at least partially stored in a central rules repository for a development group and each rule associated with a validity period; and
receiving a generated development guideline, associated with the identified first guideline rule and the second guideline rule, via an interface.
14 . The method of claim 13 , the first guideline rule comprising a released rule and the method further comprising applying a change to the released rule via the interface.
15 . The method of claim 14 further comprising providing the changed first guideline rule for review, the validity period of the first guideline rule automatically changing to begin after a review date.
16 . The method of claim 14 , the second guideline rule comprising a proven rule and the software further operable to reject proposed changes to the second guideline rule.
17 . The method of claim 16 , the proven rule associated with a plurality of triggers and further associated with a plurality of applications.
18 . The method of claim 16 , rejecting the proposed changes only upon reaching a time threshold in a development process associated with the trigger.
19 . The method of claim 13 , the trigger comprising a first trigger, the development guideline associated with a plurality of triggers and operable to be reused for a second of the triggers, the second trigger associated with a different portion of the development group than the first trigger.
20 . The method of claim 13 , the trigger comprising a code implementation cycle.
21 . The method of claim 13 , the first guideline rule comprising a wiki that includes:
a unique rule identifier, the rule identifier comprising a first structure associated with a development process, a second structure associated with a rule number, and a version number;
a keyword;
a priority field;
an approval status;
a responsible field;
a rule body; and
a rationale field.
22 . The method of claim 21 further comprising adding a new rule to the central rules repository using the interface, the new rule comprising the wiki format and the new rule's approval status comprising a new status.
23 . The method of claim 22 further comprising updating the approval status of the new rule using the interface from new to under review.
24 . A system for managing inter-process development guidelines comprising:
memory storing:
a first guideline rule, a second guideline rule, and a third guideline rule, each rule associated with a validity period; and
a development guideline based on the first and second guideline rules, the development guideline associated with a plurality of subsets of a development group; and
one or more processors providing an interface operable to manage the guideline rules and to present the development guideline.