Printing Requirements for Multiple Projects

Caliber allows you to print requirements for more than one Caliber project using Document factory. You can select multiple projects or multiple baselines and combine requirements that span more than one Caliber project into a single output.

To do this, use the command $MULTIPLE_PROJECT. Whenever this command is used, it is understood that the template is for multiple projects and multiple baselines.

Document Factory reads the $MULTIPLE_PROJECT command and checks for $PROJECT & $BASELINE commands. If these commands are not present, Document Factory prompts you to specify the project and baseline to be used. The project and baseline will be used for global keywords and global commands (meaning they can be used anywhere in the document, including headers and footers), if required.

To print requirements for multiple projects:

  1. Open the template document in Microsoft Word.

    Enter syntax as shown in the example below. All project and baseline specific commands such as $BEGIN_PROJECT_DISCUSSION can work in two ways as shown in example 1 and example 2.

    Note: The global commands must always be followed by an input parameter such as project name inside a pair of brackets. However, if you do not use a pair of parenthesis followed by the command $BEGIN_PROJECT_DISCUSSION, then you must use input to command $PROJECT and $BASELINE in order to begin discussion.

    In the example below, all data will be retrieved from the project “Order Processing”.

    $PROJECT{Order Processing}
    …………………………………….
    $BEGIN_PROJECT_DISCUSSIONS
    Subject: <<Subject>>
    From: <<From>>
    Is Read: <<Is_Read>>
    Date: <<Discussion_Date>>
    Body: <<Body>>
    $END_PROJECT_DISCUSSIONS
    
  2. Represent global keywords using following notations:

    <<Project_Name.Keyword>>

    For example, a name is named Order Processing, and user wants to print Order Processing project description using the keyword <<Project_Description>>. Then the syntax used to accomplish this is Order Processing.Project_Description.

    Note: You can also represent global keywords using existing notations in which no project name is attached. In such cases, only the global keywords are replaced by the parameters that have been passed as input to $BASELINE command and $PROJECT command
  3. Use the $FILTER command to gather and print requirements.
    $FILTER {filter: myfilter}

    Where myfilter is user defined filter. In this case, requirements are printed in document factory output based on how user defined filter is defined. If $FILTER is not used at all then all requirements from all projects and all baseline are gathered and printed.

  4. To sort requirements, use $SORT command:
    $SORT {fieldname, keyword}

    The following keywords can be used in a sort command: Type, Command, ID_Number, Version, Status, Priority, Hierarchy, Name. If you use ONLY the keywords in the SORT command (as before), requirements are gathered from various projects and are sorted depending on the keywords used with the SORT command. Requirements from different projects are sorted and printed together without being separated by project. If you want to sort projects other than alphabetical order, specify different sections for different projects.

    For example, there are three projects, Project1, Project2 and Project3, and you want to list requirements organized per each project. Use different sections from different projects as follows:

    $BEGIN_SECTION(Order Processing,Baseline1)
    $filter {filter: myfilter} 
    $INDENTION_LEVEL{3}
    $INDENTION_SIZE{.5}
    ……………………
    $END_SECTION
    
    $BEGIN_SECTION(Address Book,Baseline1)
    $filter{filter: myfilter}
    $INDENTION_LEVEL{3}
    $INDENTION_SIZE{.5}
    ……………………
    $END_SECTION
    
  5. Save the template document.
  6. Launch Document Factory.
  7. Follow the wizard procedures.
  8. Click Finish.