Menu

SCR/DCR

Help
2003-02-04
2003-03-20
  • Nobody/Anonymous

    What does SCR/DCR stand for? You can read some description on it in "Process Dashboard Users Manual."

    The section "1.8.5. Features new in version 1.2 (released April 20, 2001)" includes:

        With the addition of the standard PSP processes, the SCR/DCR processes
        are no longer shipped with the dashboard. If are a current dashboard
        user, and you have been using the SCR/DCR processes, your existing
        SCR/DCR projects WILL still work. If you wish to continue creating
        projects that use the SCR/DCR processes in the future, please download
        the SCR/DCR process separately.

     
    • David Tuma

      David Tuma - 2003-02-05

      SCR stands for "Software Change Request" and I believe DCR stands for "Design Change Request".

      The Process Dashboard is based upon a tool originally written within the U.S. Air Force.  The organization that developed the dashboard had documented processes for completing a software change request (SCR) or design change request (DCR).  When members of the organization began using the PSP, they created PSP-like variants of these processes and built the Process Dashboard around them.  In fact, version 1.0 of the dashboard only contained process definitions for the SCR, DCR, and PSP2.1 processes.

      As the dashboard developed, we added the definitions of each of the PSP processes, PSP0 - PSP3.  This made the dashboard support much more of PSP "out of the box".  Because some of our earliest users had begun using the SCR and DCR processes in the dashboard, we wanted to continue supporting those processes; but since so few people were interested in them, we moved them into an add-on process set as of Process Dashboard version 1.2.

      For legal reasons, the SCR and DCR processes were removed from the dashboard altogether with the release of Process Dashboard 1.4.1.  For more information about this change, see the "Frequently Asked Questions" topic in the Process Dashboard Users Manual.

       
      • Nobody/Anonymous

        The description in the FAQ section of the Users Manual interests me. Let me raise a question on it.

        I understand you needed some legal permission from Addison-Wesley for the purpose of continuing your development and distribution of the dashboard, and succeeded in your attempts to obtain it from them.

        Question:

        What permission did you obtain from Addison-Wesley? What constraints did they place on you in your conduction of the dashboard businesses? What were the key issues in your business talk with Addison-Wesley for this permission?

        Thanks in advance.

         
        • David Tuma

          David Tuma - 2003-03-20

          Sorry I haven't replied to this message;  I am currently in the middle of renegotiating this permission from Addison-Wesley, so I cannot answer this question at this time.

           

Log in to post a comment.

MongoDB Logo MongoDB