1     Organization and Formatting

1.1    General (same as for other B-sheets; follow this link for easy reference)

1.2    Sheet-Specific — Making it All Fit

How you lay out the information on the sheet is up to you.  The example provided is simply an example.  Depending on the relative sizes of tables, etc., rearranging may be needed.  One exception, which hopefully is seen as logical, is that the Page Input textbox should be at the top left and the Page Output textbox should remain at the bottom, better yet at the bottom right if at all possible.

2     Content Presentation

• Commence the sheet by populating the Page Input In this case, the page input are those sources that have provided information that is crafted into the engineering requirements and their quantification.  List the party by party (e.g., customer, end-user) those that have a vested interest in defining requirements, and briefly state why.  Some examples that should be included are (shown below as they may be written, but you should likely expand upon and/or be more specific than these examples):
  • Customer contact (John Doe): he is responsible for the project and its eventual transition to the field.
  • End-users (multiple): the people who will be using the solution have certain needs for its safe and efficient setup and use.
  • Codes and standards (ASME XXXXXX): this code addresses xxxxxxxxx.
• Insert graphical renderings of the engineering constraints and engineering objectives tables from the DP Manager Excel workbook.  You should first sort each table in a logical way; that is, use the buttons provided as doing so will invoke code that will assure no behind-the-scenes formulas (i.e., in hidden rows/columns) or formatting rules get messed up.  Then use the copy table buttons on the respective Excel worksheet (typically the “Copy Table with Heading” button for use in the TAD).  The code the button triggers places a good resolution picture graphic on the clipboard for then pasting into any other destination.
• For each set of requirements (constraints and objectives), there is a pre-titled End-User, Customer… Provide here what you heard from your sources and put in square brackets the one or more requirements it influenced.  You may also include clarifications that complement the information in the respective table, not a repetition of information in the table.  Note that “measurement descriptions” in the tables should (typically, 19 of 20 times) be sufficiently descriptive as concisely presented in the space provided in the table.  The following should be clear to a reader:
  • why an engineering requirement is a requirement, that is, why is it necessary.
  • reasoning that supports its quantification (limits for constraints, target for objectives).
  • any other relevant notes that support information summarized in the table.
• Complete the page by populating the Page Output textbox.  In this case, the page output is a brief description of where this information is next used and for what or how it is used (hint: many places, including functional decomposition and recomposition to main system functions, system-level concept assessment, and verification planning).

3     Examples of Great Work

Do a great job and be the first!

_{Excel is a registered trademark of Microsoft Corporation.}