Click here to make tpub.com your Home Page

Page Title: Extraction of Design Information
Back | Up | Next

Click here for thousands of PDF manuals

Google


Web
www.tpub.com

Home

   
Information Categories
.... Administration
Advancement
Aerographer
Automotive
Aviation
Construction
Diving
Draftsman
Engineering
Electronics
Food and Cooking
Logistics
Math
Medical
Music
Nuclear Fundamentals
Photography
Religion
   
   

 



DOESTD107393
Although they differ in scope, the comprehensive and smart searches should be essentially the same in
terms of their methods of document identification and retrieval (see Figure 33). Of course, the
methodology for document screening, labeling, and sorting developed for the smart search may be
refined for the comprehensive search on the basis of lessons learned.
3.2.2 EXTRACTION OF DESIGN INFORMATION
After the source documents are identified, retrieved, cataloged, and sorted, they are reviewed to extract
the design information they contain. The documents should be directed to the technical reviewers who
have expertise in the systems and disciplines reviewed. If documents are sorted incorrectly, the
technical reviewer should relabel them and direct them to the appropriate reviewer. The technical
reviewer should handle each assigned document only once, for this Is the most efficient and effective
approach to extracting design information. For each document reviewed, the technical reviewer
identifies and differentiates design requirements and design basis Information. Extracted design
information is also identified as to the applicable facility SSCs, types of SSCs, and technical topic area.
Categorizing design requirements by type may also be performed efficiently during the technical
extraction process. Differentiating the various design requirement types should be easiest during the
review of source documents. Often, source documents merely state design attributes that are not
requirements of the design process; that is, they are not safety, environmental, or mission design
requirements. Incorrectly classifying these design attributes as primary design requirement types can
impose undue constraints on engineering activities in connection with design changes or other
evaluations.
Different methods of extracting the design requirements and design basis information are acceptable.
The reviewer may enter the information directly into a holding database, computer or otherwise, for
storage prior to verification and technical validation. Alternatively, the reviewer may highlight the
information for a clerk to enter into a holding database. The former approach allows for some
summarizing or paraphrasing of design document words to capture their intent exactly, but it involves
more of the reviewer's time. Whichever method is chosen, to ensure its effectiveness, the appropriate
procedures and training should be provided.
The following actions promote the successful extraction of design information:
Select a small, dedicated group of personnel.
Select personnel with facility experience and familiarity.
Provide clear written procedures.
Provide thorough training.
Provide a standard list of SSCs.
Provide standard definitions of design basis and design requirements.
Provide extensive examples of design basis and design requirements.
Provide standard definitions and examples to differentiate design requirement types.
Use checklists.
Maintain focus on the format and contents of the final products.
Maintain strong controls on DR information databases.
3.3 EVALUATION, VERIFICATION, AND VALIDATION OF DESIGN
INFORMATION
The objective of the evaluation function is to determine whether retrieved design information is accurate
and complete. This function includes verification of the extraction process; technical validation of the
II-70


Privacy Statement - Press Release - Copyright Information. - Contact Us

Integrated Publishing, Inc. - A (SDVOSB) Service Disabled Veteran Owned Small Business