Enhanced system, method and medium for certifying and accrediting requirements compliance

[0001] This application is a continuation in part of application Ser. No. 09/822,868, filed Apr. 2, 2001, entitled “System, Method and Medium for Certifying and Accrediting Requirements Compliance” which in turn is a continuation in part of application Ser. No. 09/794,386, filed Feb. 28, 2001, entitled “System, Method And Medium For Certifying and Accrediting Requirements Compliance”, which in turn claims priority to application Ser. No. 60/223,982, filed Aug. 9, 2000, entitled “Web Certification and Accreditation System, Method and Medium”, each of which are assigned to the assignee of this application and incorporated herein by reference.

[0002] 1. Field of the Invention

[0003] The present invention relates generally to the field of certification and accreditation (C&A) and, more particularly, to a computer-implemented system method and medium for C&A that automates target system configuration discovery and enables users to tailor a sequence of requirements and/or activities that can be used to assess the risk of and/or determines the suitability of a target system to comply with at least one predefined standard, regulation and/or requirement.

[0004] 2. Background Description

[0005] The general purpose of C&A is to certify that automated information systems adequately protect information in accordance with data sensitivity and/or classification levels. In accordance with Department of Defense (DoD) Instruction 5200.40, dated Dec. 30, 1997, entitled DoD Information Technology Security Certification and Accreditation Process (DITSCAP), which is incorporated herein by reference in its entirety, certification can be defined as the comprehensive evaluation of the technical and non-technical features of an information technology (IT) system and other safeguards, made in support of the accreditation process, to establish the extent that a particular design and implementation meets a set of specified security requirements. Similarly, as used herein, accreditation can be defined as a formal declaration by a designated approving authority that an IT system is approved to operate in a particular security mode using a prescribed set of safeguards at an acceptable level of risk. In general, DISTSCAP is utilized by the DoD for identifying and documenting threats and vulnerabilities that pose risk to critical information systems. DITSCAP compliance generally means that security risk posture is considered acceptable and that potential liability for system “owners” is mitigated.

[0006] The C&A process typically involves a number of policies, regulations, guidelines, best practices, etc. that serve as C&A criteria. Conventionally, the C&A process is typically a labor intensive exercise that can require multiple skill sets over a period of time typically spanning 6-12 months. In particular, collecting data pertaining to a network configuration undergoing C&A is done manually by, for example, entering a system hardware configuration, operating system and/or application software package(s) associated with each node (e.g., IP address) on a network undergoing C&A. Several organizations and/or individuals may also be involved in the processes of selecting applicable standards, regulations and/or test procedures, and assembling test results and other information into a DITSCAP compliant package. There is therefore a need to substantially automate the network configuration data collection process, and format the data so that it can be used with, for example, a C&A system that substantially automates the process of performing security risk assessments, certification test procedure development, system configuration guidance, and residual risk acceptance.

[0007] To address the deficiencies of conventional schemes as indicated above, at least some embodiments of the present invention provide a system, method and medium that automates or substantially automates, and can provides users the ability to customize, the security C&A process in a manner that enhances and facilitates security risk assessments, certification test procedure development, system configuration guidance, and/or residual risk acceptance.

[0008] In an exemplary embodiment, the C&A process can be automated in accordance with, for example, any of DoD's DITSCAP requirements, National Information Assurance Certification and Accreditation Process (NIACAP) requirements, and U.S. Treasury/Internal Revenue Service (IRS) requirements. The present invention is not, however, limited to these requirements/standards, applications and/or environments, and may also be used in conjunction with other government and civilian/private sector organizations requiring risk management and guidance.

[0009] An exemplary embodiment according to the present invention contemplates a browser based solution that automates, for example, at least the DITSCAP, NIACAP, and IRS security processes. At least some embodiments of the present invention envision use of five primary elements: 1) gathering information, 2) analyzing requirements, 3) testing requirements, 4) performing risk assessment, and 5) generating certification documentation based on an assessment of the first four elements. In an exemplary first embodiment, predefined steps for executing these five elements are provided. In an exemplary second embodiment, users have the ability customize one or more of the five elements by, for example, selecting a portion of the predefined steps associated with one or more of the five primary elements associated with the first embodiment. Additional features of at least some embodiments of the present invention pertain to automatically sending e-mail alerts upon, for example, the occurrence of certain C&A-related events, a program management feature where one or more steps or events can be designated as being prerequisite to commencement of one or more other steps or events, and/or substantially automating network configuration discovery and formatting of the network configuration data for use with the five elements.

[0010] Still referring to the five elements mentioned above, the information gathered primarily relates to a description of a target system to be certified, and its respective components and operating environment (e.g., workstation manufacturer and model, operating system and version, secret, or top secret operating environment, etc.). The requirements analysis generally involves selecting a list of standards and/or regulations with which the system must or should comply. The user may optionally input his or her own standards/regulations and/or additional requirements. Once information is gathered and the requirements analysis is provided, the system intelligently selects a set of test procedures against which the system is tested. The user can also optionally add or delete test procedures to those initially selected by the system. Upon completion of testing, the risk assessment provides as output an estimate of the risk level for each individual test failed. Each of the failed tests are also collectively considered and used to evaluate the risk level of the target system as a whole. Then, documentation can be printed that includes information pertaining to the first four elements that would enable an accreditation decision to be made based on the inputs and outputs respectively provided and generated in the first four elements.

[0011] It is to be understood that the invention is not limited in its application to the details of construction and to the arrangements of the components set forth in the following (or previous) description or illustrated in the drawings. The invention is capable of other embodiments and of being practiced and carried out in various ways.

[0069] Referring now to the drawings, and more particularly to FIG. 1, a high level flow diagram is shown that provides an overview of the method according to the present invention. In the first step, information is gathered pertaining to the system or network undergoing C&A, as is indicated by block 100. The information gathered typically relates to a description of the system to be certified, and its respective components and operating environment (e.g., workstation manufacturer and model, operating system and version, secret, or top secret operating environment, etc.). As will be described in further detail herein, at least some embodiments of the present invention advantageously automate collection of certain information pertaining to the network undergoing C&A. Alternatively, the information pertaining to the network undergoing C&A can be manually entered.

[0070] As indicated above, aspects of at least some embodiments of the present invention are described in accordance with DoD's DITSCAP requirements. However, it should be understood that such description is only by way of example, and that the present invention contemplates use with regard to any number of types of requirements or environments. In addition, within its use with regard to DITSCAP requirements, it should be understood that many of the various aspects and selection options are also exemplary, as is the fact that information is shown as being entered via a web browser.

[0071] The requirements analysis generally involves selecting (by a human and/or some automated procedure) a list of standards and/or regulations that the system must, or should, comply with. This is indicated by block 102. Optionally, selection of additional standards/regulations and/or requirements by a user is also contemplated. At least some embodiments of the present invention then contemplate automatically displaying/listing each requirement that comprises the current security requirements traceability matrix (SRTM), which is derived from the selected set of standards and/or regulations that the system must comply with. Additionally, the user will be able to customize the current SRTM by either adding, editing and/or deleting requirements. As known to those skilled in the art, a SRTM can be a table used to trace project lifecycle activities (e.g., testing requirements) and/or work products to the project requirements. The SRTM can be used to establish a thread that traces, for example, testing and/or compliance requirements from identification through implementation. A SRTM can thus be used to ensure that project objectives and/or requirements are satisfied and/or completed.

[0072] Once information is gathered 100 and the requirements analysis 102 is provided, the system can intelligently select a set of test procedures against which the system is tested, as indicated by block 104. The test procedures are selected in a manner so that successful completion of the test procedures will render the system undergoing C&A to satisfy the SRTM requirements.

[0073] Upon completion of testing 104, the risk assessment step (as indicated by block 106) then involves assessing for each test failure (should any exist) the vulnerability of the system, as well as the level of the threat as determined by the information gathered. The risk assessment 106 provides as output an estimate of the risk level for each individual test failed. Each of the failed tests are also collectively considered and used to evaluate the risk level of the system as a whole. Then, documentation can be optionally printed 108 that includes information pertaining to the first four elements that would enable an accreditation decision to be made based on the inputs and outputs respectively provided and generated in the first four blocks (i.e., 100, 102, 104, 106). Each block shown in FIG. 1 (i.e., 100, 102, 104, 106 and 108) will be discussed in further detail herein. FIG. 2 is an exemplary screen shot corresponding to the blocks (100, 102, 104, 106, 108) provided in FIG. 1. Further information pertaining to the system and method according to the present invention can be found in the following document: WEB C&A™ 2001 User Guide DITSCAP/NIACAP, dated Aug. 27, 2001 (available from Xacta Corporation, Ashburn, Va.), which is incorporated herein by reference in its entirety.

[0074] FIG. 3 shows an exemplary access control screen shot (e.g., for access to some or all aspects of the present invention as indicated above). Each user can optionally be required to input a valid user name and password, which provides them with access to only the information for which they are responsible. The system can also optionally exclude the password and access feature, providing users access to a set of predetermined and/or default information.

[0075] FIGS. 4-5 show selected exemplary screen shots of aspects of the information gathering 100 process. Specifically, FIG. 4 shows project definition information, which is assumed to have been selected by tab 402. Fields such as project name 430, project version 432, project acronym 434, project description 436, department 438, and service 440 can be provided as being part of the project definition. The project name 430 field is preferably a read-only field, provided for information only. The project version field 432 enables the numeric version of the system undergoing C&A to be entered, if applicable. The project acronym field 434 is optionally used to provide an acronym for the project. The project description field 436 can be used to provide a detailed description of the project (e.g., mission statement, function, features, and/or capabilities of the system being accredited). The department field 438 can be used to identify the Government (or civilian) department under which this system is being accredited. As shown, the current choice is DoD. The service field 440 is used to identify the Service/Agency under which this system is being accredited. As shown, the current choices are Army, Navy, Marine Corps, Air Force, OSD, and Other. Each of the above-identified fields can be tailored to suit a particular need and/or application.

[0076] FIG. 5 shows how a user can select, via a conventional pulldown menu, either civilian or DoD service from field 438. As disclosed in application Ser. No. 09/794,386, other menus can be provided that, for example, enable a user to select a military service branch (e.g., Army, Air Force, Marine Corps, OSD, or other), and to input Information Technology Security (ITSEC) parameters (that can pertain to, for example, interfacing mode, processing mode, attribution mode, mission-reliance factor, accessibility factor, accuracy factor, information categories, system class level, and certification analysis level, as explained in DoD Instruction 5200.40) of the system being accredited. In addition, as disclosed in application Ser. No. 09/794,386, menus can also be provided that allow a user to, for example, select a security level (e.g., secret, unclassified, sensitive, etc.) and related information, and/or provide context sensitive help.

[0077] FIG. 6, shows a high level system diagram that provides an overview of the target system assessment aspect 600 (hereinafter system 600) and an associated network or target system 612 according to at least some embodiments of the present invention. As used herein, a network can be defined as two or more objects that are directly or indirectly interconnected. Referring now to FIG. 6, a network interface 608 provides an interface to one or more networks 612 having one or more network devices 614a-n operatively connected thereto. The network interface 608 can be a conventional RJ-11 or other similar connection to a personal computer or other computer that facilitates electronic interchange with the network 612.

[0078] As shown in FIG. 7, at least some embodiments of the present invention contemplate that the network discovery engine 606 comprises three separate modules: a network scanner 702, a host profiler 704, and a profile integrator 706. As will be discussed in further detail herein, the network discovery engine 606, via the network interface, collects information such as IP Address, hostname, media access control (MAC) address, operating system (OS), and OS version for one or more network devices (e.g., 614a-n).

[0079] The network scanner 702 scans a network segment 614 (comprised of network devices 614a-n) and reports the results to a network scan file 708 (e.g., a text file). Network devices 614a-n can be any devices that, for example, have an Internet Protocol (IP) address associated therewith (or that have some other mechanism by which the devices/components can be identified). The network scanner 702 can scan through a specified range of IP addresses associated with each respective network device 614a-e within the network segment 614.

[0080] The network discovery engine 606 can utilize conventional network topology discovery techniques such as transmission control protocol (TCP)/user datagram protocol (UDP) port interrogation, and/or simple network management protocol (SNMP) queries, and receive network configuration information provided by such technique(s). Network topology information can optionally be manually added via the user interface 602. Upon entering or providing one or more IP address (e.g., a range of IP addresses), the host name of a network device 614a-n can be obtained by using, for example, a getHostName (or similarly named) function that will query a network device 614a-n for a host name. Functionally, the getHostName function can scan one or more domain naming service (DNS) servers internally and optionally over, for example, the World Wide Web to try and resolve the IP address (i.e., match the IP address with its respective host name). In the case of a MAC address, the initial sweep of, for example, a network segment 614 can have one or more Internet Control Message Protocol (ICMP) requests. One such request can be a “ping request.” The packet returned from such a ping request can include, for example, the MAC address of the host device. Similarly, during a port sweep/interrogation, the OS family (e.g., Unix, Windows, etc.) and version can generally be determined. Regarding SNMP queries, if a queried network device 614a-n is SNMP enabled, additional information (e.g., device manufacturer, model, application software), etc. can generally be obtained. Finally, if a network device 614a-n utilizes (e.g., has installed thereon) an Enterprise Management (EM) software/system, the system 600 can scan the EM database (or an extract or portion thereof) associated with a particular network device 614a-n to obtain additional detailed information on each network device 614a-n in the IP range.

[0081] The network scanner 702 can obtain the following information relating to network devices 614a-e (which correspond to the network segment 614 under consideration): IP Address, hostname, media access control (MAC) address, operating system (OS), and OS version. This information can be written to a network scan text file 708. The MAC address, as used herein is a hardware address that uniquely identifies each node of a network. In IEEE 802 networks, for example, the Data Link Control (DLC) layer of the Open System Interconnection (OSI) Reference Model is divided into two sublayers: the Logical Link Control (LLC) layer and the Media Access Control (MAC) layer. The MAC layer interfaces directly with the network media. Consequently, each different type of network media requires a different MAC layer. On networks that do not conform to the IEEE 802 standards but do conform to the OSI Reference Model, the node address is called the Data Link Control (DLC) address.

[0082] The host profiler 704 can produce a host profile file 710 (e.g., a text file) containing information such as hardware configuration, operating system and patch levels, installed software list, etc. Host profilers 704 can optionally be provided to accommodate different classes of hosts (e.g., Windows-based machines, UNIX-based machines, etc.). The host profile can be conventional enterprise management software developed by, for example, Tivoli Systems Inc., Austin Tex., or by Computer Associates International, Inc., Islandia, N.Y.

[0083] Using conventional system commands, operating system application program interface (API) calls, registry calls, etc., the host profiler 704 can determine information about the hardware configuration, operating system options, installed software, etc. of each network device 614a-e within a particular network segment 614. This information for each host 614a-e can be recorded in the host profile file 710. The data in the host profile file 710 can then be used to supplement the information about the respective host in the network scan file 708. A host profile text file 710 can contain information about more than one host.

[0084] The profile integrator 706 enables information from host profile file 710 to be added to an existing network scan file 708. The profile integrator 706 takes the data in one or more host profile text files 710 and integrates the data into an existing network scan text file 708.

[0085] The network scan file 708 can utilize the conventional Microsoft .INI type file format. As will be appreciated by those skilled in the art, an .INI file is a file that contains startup information required to launch a program or operating system. In general, the network scan file 708, which can be an ASCII file, can identify particular network devices 614a-e by using the form <parameter>=<value>, where <parameter> is the name of the particular item of information, and <value> is the value of that item of information for the network device 614a-e under consideration. For example, as shown in FIG. 8 at 808a, the IP Address=192.168.0.10 indicates the identified host responded at the specified IP address.

[0086] As further shown in FIG. 8, the network scan file 708 can begin with a [Network] section 802 that describes the overall network being scanned. The network (e.g., network 612) name is Xacta, as indicated at 802a. Each network segment (e.g., 614) can be described by a [Segment] section 806. The network segment is called Office, as indicated at 807. At 806a, the network name Xacta is again provided. The Office segment has IP addresses in the 192.168.0.0-255 subnet, as indicated at 806b. The subnet was scanned twice: once on Dec. 1, 2000, and once on Dec. 15, 2000, as indicated at 806c and 806d, respectively.

[0087] A [Host] section 808, 810 can also be provided for each network device (e.g., 614a-e) within the network segment 614. The IP Address 808a, MAC 808b, Hostname 808c, OS 808d, and Version 808e are the basic information collected by the network scanner 702. At 810, the information collected by the host profiler 704, which has been integrated into the network scan file 708 by the profile integrator 706, includes: IP Address 810a, MAC 810b, Hostname 810c, OS 810d, and Version 810e, mfr 810f, model 810g, CPU 810h, CPU Qty 810i, CPU Speed 810j, RAM 810k, Disk Space 810l, and Software 810m-p. The host profile file 710 can use the same file format (e.g., .INI) as the network scan file 708. The profile integrator 706 can integrate one or more host profile files 710 with a network can file 708. Each [Host] sections (e.g., 810) can either have their own separate host profile files 710. Alternatively, two or more host sections 810 can be included in a host profile file.

[0088] FIG. 9 illustrates an exemplary schema 900 that can be used in conjunction with network discovery. As shown, the schema 900 comprises: platform categories 902 (comprising categories 902a-n), network 612 (comprising network devices 614a-n), and software inventory 906 (comprising application software programs/packages 906a-n).

[0089] Platform category elements 902a-n represent generic categories of equipment that lie within the accreditation boundary (e.g., network segment 614) that includes the components (e.g., network devices 614a-e) that are associated with the network segment 614 being accredited. Representative platform categories can include desktop computer, laptop computer, mainframe computer, handheld device, hub, etc. Platform categories generally represent typical configuration(s) of the network devices 614a-n that belong to a particular platform category. As used herein, an accreditation boundary can be defined as the network devices (e.g., 614a-e) that comprise the network segment 614 (or target system) being accredited. There can also be one or more devices that are associated with the network segment 614 being accredited, but that are outside of the accreditation boundary and thus not included in the accreditation. Equipment outside the accreditation boundary can include equipment/services as a DNS used to translate the host names to IP addresses.

[0090] With regard to platform category elements 902a-n, the typical office LAN might consist of the following platform categories: file server, mail server, network printer, router, switch, and workstation. Information about each platform category 902a-n can include hardware specifications (e.g., manufacturer, model, CPU, memory, etc.) and OS specifications (e.g., OS name, version, patches, etc.). Since the platform categories 902a-n are generic, and numerous actual network devices 614a-n generally exist, the hardware and OS specifications of a platform category 902a-n will represent the typical configuration expected of network devices that belong to a particular platform category (e.g., network devices 614a, 614b, 614c and 614i belong to equipment category 902b).

[0091] Network devices 614a-n represent actual pieces of equipment within the accreditation boundary. Each network device 614a-n belongs to one of the exemplary platform categories 902a-n, as discussed above. Upon assignment to a platform category 902a-n, each network device 614a-n can “inherit” (or is assumed to have) the generic information (e.g., hardware and OS specs) of its assigned category. A user, via user interface 602, can then optionally add, delete and/or edit information. Network devices 614a-n are assigned to a platform category (e.g., 902a) to facilitate test procedure generation, as will be discussed in further detail herein, particularly with regard to FIG. 17.

[0092] Software inventory elements 906a-n represent application programs (i.e., operating systems are not included). The system 600 can form an association between one or more software elements 906a-n and one or more platform category element 614a-n (e.g., an association is formed between software elements 906a, 906b, 906c and platform category 902a). When such an association is formed, the software is considered to be installed on all equipment in that platform category 902a-n. Similarly, the system 600 can form associations between a software element 906a-n and a network device 614a-n. Such an association indicates that the software is actually installed on the associated network device 614a-n, but that the software element is not necessarily installed on every network device in a given platform category 902a-n.

[0093] Network configuration information can also be manually entered into the system 600. For example, returning to FIG. 4, when project hardware tab 414 is activated, a menu as shown in FIG. 10 can be provided. The menu allows a user to, for example, edit information pertaining to the Platform Category 1002 via a Description field 1004. Information pertaining to the Estimated Quantity 1006, Test Strategy, and IP Address Range 1010 can be provided. As shown, the menu also allow a user to edit hardware specs 1014 such as the Hardware Family, Manufacturer, Model, Serial Number, Location, etc.

[0094] At least some embodiments according to the present invention contemplate a database structure with at least the following tables that can be utilized to accommodate the network scanning and profiling features. The exemplary data dictionary disclosed herein provides additional details pertaining to the following tables.

[0095] WCA_ProjPlatCat Table—contains a row for each defined platform category.

[0096] WCA_ProjEquipInven Table—contains a row for each piece of equipment.

[0097] WCA_ProjSWInven Table—contains a row for each defined software element.

[0098] WCA_ProjPlatSW Table—contains a row for each defined association between a software inventory element and a platform category (for each project); each such association indicates that the software element is typically installed on members of the associated platform category.

[0099] WCA_ProjEquipSW Table—contains a row for each defined association between a software inventory element and an equipment inventory element (for each project); each such association indicates that the software element is actually installed on that particular piece of equipment.

[0100] WCA_OSSource Table—contains a row for each ‘standard’ operating system, including family (NT, UNIX, or Other), manufacturer, name, version, etc.

[0101] WCA_SWSource Table—contains a row for each ‘standard’ software application, including family (e.g. database, network OS, etc.), manufacturer, name, version, etc.

[0102] Certification and Accreditation Engine

[0103] As will be explained in further detail herein, once information has been collected (either manually or via an automated process, each as described above) pertaining to devices 614a-e belonging to the network segment 614, the certification and accreditation engine 614, can select compliance requirements/standards and test procedures applicable to the C&A under consideration. A user can also select requirements/standards and/or test procedures by using, for example, user interface 602.

[0104] Additional Information Gathering

[0105] Returning again to FIG. 4, when project personnel tab 408 is activated, a menu (not shown) can be provided that enables a user to enter information identifying all the project personnel associated with the accreditation effort. The personnel are preferably identified by the role, as discussed below, that they serve in the accreditation process. At least one entry for each role is preferably defined for the project.

[0106] For example, the following fields can be provided in a menu (not shown) subsequent to clicking the personnel tab 408:

• • [0107] Role Name—The role associated with the accreditation team member. The available choices can be:
    • [0108] Accreditation Team Lead—The person in charge of the accreditation effort, usually the Project Manager.
    • [0109] Accreditation Team Member—All the members of the accreditation team (analysts, testers, etc.).
    • [0110] Certification Authority (CA)—Person in charge of the system certification.
    • [0111] Certification Authority POC—Point of Contact (POC) to the CA.
    • [0112] DAA—Designated Approving Authority. Person ultimately responsible for the accreditation of the system.
    • [0113] DAA POC—Point of Contact (POC) to the DAA.
    • [0114] ISSO—Information System Security Officer. Person responsible for the security implementation of the system being accredited.
  • [0115] Organization Responsible—Organization responsible for the design and development of the system being accredited.
  • [0116] Organization Responsible POC—Point of Contact to the Organization responsible.
  • [0117] Program Manager—Program manager of the system being accredited.
  • [0118] User Representative—Representative from the user community.
  • [0119] Title—The title associated with the accreditation team member (Mr., Ms. or Dr., etc.)
  • [0120] First Name—The first, middle initial, and last name of the accreditation team member.
  • [0121] Office—The office (e.g., Office of the Assistant Deputy for Policy and Planning) of the accreditation team member.
  • [0122] Office Designation—The office designation of the accreditation team member. For example, if the office is the Office of the Assistant Deputy for Policy and Planning, then the office designation may be ADS-P.
  • [0123] Organization—An organization that is associated with the accreditation team member.
  • [0124] Work Address—A work address if applicable for the accreditation team member (include city, state and zip code).
  • [0125] Work Phone—A work phone number for the accreditation team member.
  • [0126] Work Fax—A work fax number if applicable for the accreditation team member.
  • [0127] Email Address—An email address if applicable for the accreditation team member.

[0128] When the project schedule tab 412 of FIG. 4 is activated, a screen can appear (not shown) that provides the capability to describe and store each project milestones for the system being accredited. Fields such as milestone title, milestone date, and milestone description can be provided.

[0129] When project hardware tab 414 is activated, a menu as shown in FIG. 10 can be provided. The menu allows a user to, for example, Edit/Delete H/W 472, enter various Platform Information 474, CPU information 476, and/or Memory/Storage Information 478. This information can be modified to reflect changes in system configurations throughout the information gathering requirements analysis and testing phases.

[0130] When project operating system 416 is activated, a menu (not shown) that enables a user to manually, in addition to or in lieu of the automated process heretofore, describe and store operating systems associated with the system hardware is provided. The ability to enter information pertaining to multiple operating systems (OS) on each hardware platform can be provided. Fields are provided to enable a user to enter information pertaining to the OS Name (e.g., Windows NT, AIX, HP UX, etc.), OS Type (e.g., NT, UNIX, etc.), OS Manufacturer (e.g., Microsoft, Hewlett Packard, IBM, etc.), OS Version (the numeric value of the operating system version), OS Options (a list of all OS options (if any) obtained for this platform), OS Patches (a list of OS patches (if any) that have been installed on the platform), OS Description (a detailed description of the operating system, possibly including the basic features, and any functions unique to the system being accredited).

[0131] When project application tab 418 is activated, a project application screen appears (not shown) that can provide the analyst with the ability to manually, in addition to or in lieu of the automated process described heretofore, describe and store applications associated with the system hardware/OS combinations. The following exemplary fields can be provided: Application Name (the name of the application), Application Type (the type of application on the system being accredited—e.g., database, office automation, e-mail server, etc.), Application Manufacturer (the name of the application manufacturer), Application Version (the numeric version of the application), Application Options (a list of the options associated with the application (if any)), Application Patches (a list of the patches associated with the application), and Application Description (a detailed description of the application).

[0132] When system interfaces tab 420 is activated, a menu (not shown) is provided that provides the user the ability to describe and store the flow of information into and out of the accredited system. The system interfaces entries can describe each of the internal and external interfaces identified for the system. The following exemplary fields can be provided: Interface Name (an internal or external name associated with the system interface), and Interface Description (a detailed description of the internal or external system interface, which preferably includes a statement of the significant features of the interface as it applies to the entire system, as well as a high level diagram of the communications links and encryption techniques connecting the components of the information system, associated data communications, and networks).

[0133] When system data flow tab 422 is activated, a menu (not shown) is provided that can provide the user the ability to describe and store the flow of information within the accredited system. System data flow entries can describe the flow of information to each of the external interfaces identified for the system. The following exemplary fields can be provided: Data Flow Short Name (a brief user-defined name associated with the system data flow), and Data Flow Description (a detailed description of the data flow associated with the external interface, which preferably includes a statement of the purpose of the external interface and the relationship between the interface and the system, as well as the type of data and the general method for data transmission, if applicable).

[0134] When accreditation boundary tab 424 is activated, a menu (not shown) that provides the user with the ability to describe and store the identification of components that are associated with the system being accredited, but are outside of the accreditation boundary (i.e., not included in the accreditation). This category might include such equipment/services as, for example, a domain naming service (DNS) used to translate the host names to IP addresses. The DNS might not be part of the atomic system being accredited, but is required for most communication activities. The following exemplary fields can be provided: Accreditation Boundary Name (a name associated with the external system component), and Accreditation Boundary Description (a detailed description of the external system component, which preferably includes the function that this component/service provides the system being accredited and its relationship to the system).

[0135] When project threat tab 426 is activated, a menu (not shown) appears that provides the user the ability to quantify the threat environment where the system is intended to operate. If the system is targeted to operate in multiple locations, the environmental condition that results in the higher or highest level of risk can be selected. The following exemplary fields can be provided: Location (CONUS (CONtinental US) or OCONUS (Outside CONtinenal US) as the primary operating location for the system), System Communications (the primary means of information transfer to external systems, such as No LAN, Local LAN Only, SIPRNET (SECRET Internet Protocol Router Network), NIPRNET (Unclassified but Sensitive Internet Protocol Router Network), Internet, etc.), Connection (the types of connection—e.g., wireless, dial-up, or protected distribution system (PDS), etc.), Training Competency Level (e.g., administrator, maintenance personnel, user, etc.), Installation Facility (the operating environment of the system at its intended end site), Natural Disaster Susceptibility (e.g., fire, flood, lightning, volcano, earthquake, tornado, etc.), and Custom Components.

[0136] When project appendices tab 428 is activated, a menu (not shown) that provides the user the ability to identify external documents that are associated with the C&A is provided. These appendices can optionally include references to other documents, or consist of the contents of other documents that are accessible via a computer-implemented embodiment of the present invention. Representative appendices that may be derived are: System Concept of Operations, Information Security Policy, System Rules of Behavior, Incident Response Plan, Contingency Plans, Personnel/Technical Security Controls, Memoranda of Agreement, Security, Education, Training and Awareness Plan, and Certification and Accreditation Statement.

[0137] Tabs 402-428 can be activated in any order, and do not need to be activated sequentially. Also, each tab can be optionally customized to contain different, fewer, or additional fields relative to the fields discussed above. Further, the tabs (402-428) can be arranged differently. Fewer or additional tabs can also be provided to suit a particular application or need.

[0138] The system configuration captured in the step of block 100 of FIG. 1 is used as input for the determination of the requirements indicated by block 102. The process of editing and/or determining/selecting those requirements is shown in FIG. 11. In at least some embodiments contemplated by the present invention, the Requirements Analysis step is related to the Accreditation Type 404 and Project Security 406 information stored in the step indicated by block 100. In at least some embodiments, data is entered and saved in the Accreditation Type 404 and Project Security 406 fields provided before beginning the Requirements Analysis step indicated by block 102.

[0139] In an exemplary embodiment, a general purpose computer on which the present invention operates will have stored thereon or have access to a repository of security regulations and test procedures from various government and/or civilian departments, agencies, organizations, etc (e.g., such as those from DITSCAP). In step 1102 (FIG. 11a), and based at least in part on the information entered in step 100, pertinent regulations will be selected from this repository, upon which to build a security requirement traceability matrix (SRTM) for the C&A. The SRTM, as discussed above, can be a mapping of one or more test procedures to each individual requirement within a requirements document. Satisfactory completion of the respective one or more test procedures that can be mapped to each requirement is generally considered to render the requirement satisfied. However, the user has the flexibility to view and modify 1104 the SRTM as desired to meet the specific needs of the systems being accredited by, for example, adding and/or deleting one or more tests to/from the SRTM, and/or editing one or more of the test procedures to, for example, include additional testing requirements. If the user decides to modify a test procedure, the specified test procedure displayed 1106. The user can then modify and save the revised test procedure 1108. The user can then either end the editing process or continue to modify another security document 1110.

[0140] FIG. 12 shows an exemplary Generate Baseline SRTM screen shot. In at least some embodiments of the present invention, clicking the Requirements Analysis tab 1201 from the application menu will switch control to the Generate Baseline SRTM screen. As shown, FIG. 12 provides a menu that provides a list of pre-packaged (i.e., shipped with the application) regulations documents (1202-1222) for the user to select. Each regulations document (1202-1222) contains specific requirements, one or more of which may be utilized when performing the C&A. All unmarked check boxes (e.g., check boxes associated with documents 1202, 1206, 1210, 1212, 1214, 1216, and 1218) represent unselected Regulations Documents, and thus do not factor into the requirements analysis step 102 for the particular project under consideration.

[0141] After selections have been made, either by the user by, for example, clicking the appropriate boxes associated with documents (e.g., 1204, 1208, 1220 and 1224), and/or by the system, the application will provide a Display SRTM screen as shown in FIG. 13. Additionally, FIG. 13 may display any optional user-defined requirements as determined at FIG. 12, 1226. FIG. 13 particularly shows pertinent portions of DoD 5200.5, selected in FIG. 12 (1208), that are applicable to the C&A at hand.

[0142] With the security requirements traceability matrix in place (a portion of which is illustratively shown in FIG. 13), the user proceeds to the testing step 104. In at least some embodiments of the present invention, user interfaces will be provided, in accordance with the steps shown in FIG. 14, for the user to have the system 600 generate one or more test procedures, and/or add and/or edit test plan information 1402, associate all the requirements to test procedures 1404, add and/or edit test procedures 1406, enter test results 1408, and/or publish test results 1410. Any of the above steps can optionally be repeated as needed, as indicated in decision step 1412. Each of these steps will be discussed in further detail herein.

[0143] An Edit Test Plan Information screen, corresponding to step 1402, is shown in FIG. 15. The exemplary input fields on the screen are Expected Date of Test 1502, Planned Location of Procedure 1504, Test Resources 1506, Test Personnel 1508, and Remarks 1510.

[0144] FIG. 16 is an Associate Requirements screen, corresponding to step 1404, which illustrates how a user can manually select a test procedure to associate it with at least one requirement selected. As indicated in the descriptive text block 1602, a user can select a source requirements document 1604. Upon clicking on the associate icon 1606, a list of test procedures (not shown) can be displayed. The user can then select one or more of the test procedures within the test procedure database (as discussed above) and associate it/them with the selected source document 1604. A user can also create a new security test and evaluation procedure (ST&E) 1608 or certification test and evaluation (CT&E) procedure 1610, by clicking on the respective icon. After the user enters the respective CT&E and/or ST&E information into a form presented on a new menu (not shown), the user can save the procedure(s) and optionally associate the procedure(s) via the Associate icon, as described above. As discussed in application Ser. No. 09/794,386, the process described in FIG. 16 can also be automated.

[0145] The certification and accreditation (C&A) engine 604 can generate test procedures, corresponding to step 1406, in accordance with the method shown in FIG. 17. In an exemplary embodiment of the system 600, the C&A engine 604 receives network configuration information from the network discovery engine 606 and compare the network configuration information with approved hardware and/or software standards, which can advantageously provide a substantially continuous and dynamic risk management process.

[0146] The system 600 can select one or more tests associated with each standard, regulation, etc. selected as discussed with regard to FIG. 12. For each selected test 1702 and for each platform category 1704, the C&A engine 604 can determine whether there is a test strategy associated therewith 1706. For each given platform category 902a-n, test strategies can include, for example, test one network device 614a-n associated with the platform category, test some network devices 614a-n associated with that category, or test all network devices 614a-n associated with the platform category.

[0147] If there is not a test strategy associated with the platform category 902a-n currently under consideration, the process terminates 1718 without generating an instance of the test 1702 currently under consideration. If there is a test strategy associated with the platform category 902a-n currently under consideration, then a determination is made 1708 as to whether there are any network devices 614a-n associated with the platform category 902a-n selected at block 1704. If there are no network devices 614a-n associated with the platform category selected at block 1704, then one test procedure can be generated 1710 for the test category. The test procedure generated can be a generic test procedure that would cover all or substantially all of any network devices 614a-n that may be added to the platform category in the future. If there is at least one network device 614a-n associated with the platform category selected at block 1704, a determination is made as to whether the network device is to be tested 1712. If no, the process ends 1718; if yes, a test procedure is generated for that equipment piece 1714. The test procedure that will be generated can depend upon the hardware configuration, operating system, and application programs for the particular network device 614a-n, as determined by business rules and/or decision logic within the certification and accreditation engine 604. Finally, a determination is made as to whether there is additional equipment 1716. If no, the process ends 1718; if yes, the process returns to decision step 1712.

[0148] FIG. 18 is a screen illustrating how a user can enter a new test procedure. As shown, the input fields on the screen are Test Title 1802, Category 1804, I, O, T, D (where I represents interview, O represents observation, T represents text, and D represents documentation review) 1806, Test Procedure 1808, and Expected Result 1810. If Associate 1812 is selected, then a new row is preferably created in the test procedure data base with the data entered in the input fields provided.

[0149] As previously discussed, the certification and accreditation engine 604 contains decision logic whereby test procedures can be intelligently selected for the C&A at hand by using the system information specified in step 100 and the requirements analysis step 102. As discussed above in the context of the SRTM, one or more test procedures within the test procedure database can be mapped to, linked with, and/or otherwise associated with each of the individual requirements within each respective requirements document (FIG. 12). As shown in FIG. 19, one or more of the test procedures intelligently selected by the present invention for the C&A at hand can be edited. In a preferred embodiment, the user will be able to edit any of fields 1802, 1804, 1806, 1808 and/or 1810. As disclosed in application Ser. No. 09/794,386, the user can also edit the test procedure once it has been entered.

[0150] FIG. 20A is a screen that enable a user to enter test results. As shown, at least some embodiments of the present invention contain the following exemplary columns: Category 2002, Test Title 2004, Operating System (OS) 2006, Hardware 2008, Test Procedure 2010 (which enables a user to view the details of the test procedure), Associate Requirements 2012 (which allows the user to view which requirements a particular test procedure is associated with), Enter Results 2014, Complete 2016 (which provides an indication of whether the test procedure has been completed), and Result 2018 (which provides an indication of whether the test procedure has passed or failed). (It should be appreciated, however, that various embodiments of the present invention contemplate that the present invention automatically initiates the test, and obtains the results, without the need for any additional manual entry steps).

[0151] FIG. 20B is an exemplary screen that appears when the Enter Results 2014 icon is pressed that is associated with a particular test procedure. For example, in FIG. 20A, if icon 2014a is pressed, the a screen appearing similar in format to FIG. 20B will appear with the Test Title 1802 corresponding to the test contained in row 2002a of FIG. 20A (e.g., Cannot Log On Directly as Root from Remote System/Terminal). As shown, the Test Title 1802, Category 1804, Equipment Under Test 1901, I, 0, T, D 1806, Test Procedure 1808 and/or Expected Result 1810 and fields also preferably appear within this screen. Also, Result field 2020 appears, which allows the user to enter the test result (e.g., pass or fail). Tester field 2022 enables the tester to provide his name, and Date 2024 that the test was conducted. Finally, the tester is able to enter any Notes pertaining to the test 2026.

[0152] Once the testing step 104 has been completed and the results recorded, the risk assessment step 106 commences, as indicated by sub-headings a-d below.

[0153] a) Generate Project Threat Profile (Step 2102)

[0154] As shown in FIG. 21, at step 2102, at least some embodiments of the present invention generate a project threat profile, which is a score for each of the generic threat elements (e.g., fire, flood, hardware, power, software design error, etc.) as will be discussed in further detail herein. In at least some embodiments, the user performing the C&A is presented with a series of questions pertaining to the environment for which the C&A will be performed. (This information could also be obtained in an automated fashion using any number of known techniques). The present invention will then estimate the threat level based on the operators' answer. The value assigned to each of the generic threat elements is applicable to each test procedure associated with the particular system undergoing C&A. A user can optionally change any of the system determined threat element scores for one or more of the generic threat elements. Exemplary values for generic threat elements are as follows:

[0155]

Threat Element Score	Interpretation
N	Threat element is not applicable to
	this project or has negligible
	likelihood of occurrence
L	Threat element has low likelihood
	of occurrence for this project
M	Threat element has medium
	likelihood of occurrence for this
	project
H	Threat element has high likelihood
	of occurrence for this project

[0156] For example, generic threat elements 1-29, as defined in FIG. 22, may have a project threat profile as follows:
MHNLLLLMMMMMLLLMMMMLLLLLLLLNN

[0157] corresponding, respectively, to elements 1-29. For this project threat profile, the threat of a flood is thus considered high.

[0158] FIG. 23 shows an exemplary Threat Environment screen, which shows the calculated level of risk based on the information that was provided in step 100. As per at least some embodiments, the present invention automatically calculates the risk, which is indicated under the Calculated Value 2302 heading. This could be accomplished in any number of ways based upon data obtained during the current and/or testing phase, as indicated above. The User Defined Value 2234 preferably defaults to the corresponding Calculated Value 2302 for a given threat environment element (e.g., 1, 2, 3, etc.). However the user/analyst has the opportunity to optionally override the calculated risk rating by clicking on the User Defined Value 2204 for each corresponding threat element. As previously discussed, exemplary available choices are negligible, low, medium, or high, although they could also be, e.g., numerical in nature.

[0159] b) Threat Correlation String (step 2104)

[0160] In step 2104, a threat correlation for each failed test procedure is accessed. Specifically, each test procedure used in the C&A for the system being evaluated is, in at least some embodiments of the present invention, coded with a threat correlation string, with each character in the string representing one of the generic threat elements in the same order as they exist in the project threat profile as shown, for example, in FIG. 22. The test procedure database preferably contains these codes. Each character in the threat correlation string contains a score that indicates the relative potential of a given threat to exploit a vulnerability caused by failure of this particular test. An exemplary scoring system is as follows:

[0161]

Threat Correlation Score	Interpretation
N	Threat element is not applicable to
	this vulnerability (or has negligible
	potential to exploit it)
L	Threat element has low potential
	for exploit of this vulnerability
M	Threat element has medium exploit
	potential for this vulnerability
H	Threat element has high exploit
	potential for this vulnerability

[0162] Thus, for example, failure of a particular test may mean that the system being tested is highly vulnerable to Floods. To indicate this, the character in the threat correlation string corresponding to Floods would contain a score of “H.”

[0163] c) Determine Risk Profile for Each Failed Test Procedure (Step 2106)

[0164] As indicated at step 2106, the risk profile for each test procedure is determined. Specifically, for each test failure, the threat correlation string contained within each test procedure, as determined at step 2104, is applied against the project threat profile as determined at step 2102.

[0165] For example, the project threat profile above, given as:
MHNLLLLMMMMMLLLMMMMLLLLLLLLNN

[0166] may have a test procedure with the following threat correlation sting:
HHNMHLMNHHHMLNNNHLMLHNNLHHLMH

[0167] In this case, in accordance with an exemplary process according to at least some embodiments of the present invention, the combined risk profile string as determined in accordance with FIG. 24 would be:
MHNLMLLNMMMMLLLNMLMLMLLMMLNN

[0168] For a given row of FIG. 24, and given the first two values contained in the first two columns corresponding to that row, we have discovered and determined that the values contained in the third column of the row can be used a measure or risk.

[0169] The highest risk level in the combined string for a given test procedure is preferably used as the risk level for the failure of that test procedure. Thus, for the combined string above, the risk level for a failure of the test procedure is high, since there is an H in the second position. Similarly, if M were the highest risk level that appears in a combined string, then the risk level for a failure of that test procedure would be medium, etc.

[0170] d) Determine Overall System Level Risk (Step 2108)

[0171] In addition to the individual risk level scores for each test failure as determined in step 2106, an overall risk level for the project is also determined as indicated by step 2108. As shown in FIG. 25, in at least some embodiments, of the present invention, the overall system risk level is defined as the highest of the individual risk elements. Thus, if it is determined that any element in the risk profile associated with the failure of any given test procedure is “high” (as indicated by decision block 2502), then the overall risk for the system is high as indicated by a block 2504. If the risk profile associated with the failure of any given test procedure is “medium” (as indicated by decision block 2506), then the overall risk for the system is medium as indicated by a block 2508 when no high risk test failures are present. If the risk profile associated with the failure of any given test procedure is “low” (as indicated by decision block 2510), then the overall risk for the system is low when no high risk or medium risk failures are present, as indicated by a block 2512. If the risk profile associated with the failure of any given test procedure is “negligible” then the overall risk for the system is negligible, as indicated by a block 2514, when no high risk, medium risk, or low risk failures are present. The user also can have the ability to override the overall system risk level as determined in accordance with the above methodology. In such a case, the user will also be able to optionally provide explanatory text to accompany the overall user-defined system risk level.

[0172] Publishing

[0173] In the publishing step 108, the present invention collates the results of the certification process and optionally generates the documents needed for accreditation. The present invention takes the information gathered during the steps corresponding to blocks 100, 102, 104 and 106, and reformats the information by, for example, organizing it into to appropriate documents, document subsections or subparagraphs, sections and/or appendices, etc.

[0174] As shown in FIG. 26, the invention allows a user to select a document or subsection thereof for publishing 2602, and to optionally input and/or review the information thereof 2604. As shown in FIG. 27, to view the document subsection thereof, the user simply clicks on the section name 2702. As shown in FIG. 28, the user can then edit the selection subsection 2702. The user can optionally edit, input information, or review the existing text 2604 or add to it, or even upload graphics if desired to further customize the final document. If the user chooses to publish the document or subsection under consideration 2606, the publishing function 2808, as shown in FIG. 29, can also, as previously discussed, generate any Appendices desired by the user and/or required by, for example, the DITSCAP (DoD Instruction 5200.40). At decision step 2810, the process can either be repeated for another document or subsection, or terminated. FIG. 30 shows an exemplary screen shot that enables a user to publish 2902 the acronym list 2902 selected in FIG. 29. The present invention also contemplates that accreditation can be automated, so that no accreditation agency is needed. In this embodiment, when sufficient test related results and/or information is provided to the computer 3102, the method according to the present invention can automatically determine that accreditation requirements have been satisfied.

[0175] At least some embodiments of the present invention provide a “front end” (called Work Product Manager (WPM)) that, inter alia, allows a user to customize a C&A and/or add workflow functionality to the C&A process. By using the WPM, work products (a unit of work) can be defined. Each one of these work products can, for example, be opened, submitted, and approved by a user (e.g., an analyst). When one of these events takes place, an e-mail or other electronic notification can be sent to the appropriate user(s). The present invention thus provides an e-mail Notification Setup Graphical User Interface (GUI) that enables users to define and enter, for example, Role/Title, Users, and work product notifications in support of the e-mail notification functionality.

[0176] In accordance with at least some embodiments of the present invention, the WPM provides, for example, electronic control and authorization of access to documents, notification of designated individuals when a predefined event occurs, document approval, tracking, status reporting, and tracking of edits and/or document revisions. The WPM of the present invention also advantageously provides for the revision, approval, and release of documents in a collaborative environment. In addition, the WPM of the present invention also can help ensure that published content (e.g., a C&A report or portion thereof) is accurate and timely, providing for the automated document release and/or user notification for time-sensitive documents or content.

[0177] The WPM enables users to define a Work Breakdown Structure (WBS) (collection of units of work) that resemble a company's best practices. WPM provides a GUI that can be used to notify users when the state of a Work Product changes.

[0178] The following terms and associated definitions associated with the WPM are provided:

[0179] Process Step (PS): A unit of work that normally corresponds, for example, to a screen display.

[0180] Work Product (WP): A unit of work within WPM that consists, for example, of one or more PSs.

[0181] Work Breakdown Structure (WBS): A set of WPs that can comprise the complete work flow for a project (e.g., a C&A).

[0182] Submittal: When work is completed on a WP, an analyst with appropriate permission can submit it for approval. Submittal can also lock the information in the WP so no further change can take place.

[0183] Approval: An analyst with appropriate permission can approve a submitted WP. In accordance with at least some embodiments of the present invention, when a WP is approved, its content preferably remains locked. Subsequent WPs may then become available for work.

[0184] Disapproval: An analyst with appropriate permission can disapprove a submitted WP. In accordance with at least some embodiments of the present invention, when a WP is disapproved, its content is unlocked so that further work may be done to complete it.

[0185] Prerequisite: WPs within a WBS can be set up with dependencies. In accordance with at least some embodiments of the present invention, any given WP may be configured so that it only becomes available for work when certain prerequisite WPs have been approved.

[0186] Reopening: An analyst with appropriate permission can reopen an already-approved WP if new information has become available and the WP must be revised. In accordance with at least some embodiments of the present invention, reopening preferably unlocks the information in the WP so that it may be revised. Subsequent WPs with dependencies may once again become unavailable for work.

[0187] FIG. 31 is an exemplary screen shot of the WPM that enables the addition of one or more organizations (e.g., a corporation (and/or one or more divisions and/or subsidiaries thereof), a non-profit organization (and/or one or more components thereof), government department or agency (and/or one or more portions thereof)), each of which can have, for example, one or more projects (e.g., a C&A) associated therewith. FIG. 31 thus conveniently enables one or more projects to be associated with one or more organizations (or portions thereof).

[0188] The WBS generally defines the process flow for the project. FIG. 31, associated with Site Administration tab 3101a, enables a system administrator, for example, to add an organization via button 3102. When button 3102 is selected, a subsequent screen(s) (not shown) appears that enables an administrator to enter information such as a customer ID 3106 and/or Organization 3108 name. A list of Users 3110 for the organization, existing organization Projects 3112, and Audit 3114 information (which can also be viewed by selecting tab 3101f) enables a user to select and/or search for a project name by, for example, entering the project name and/or other parameters associated with the project (e.g., the date that the project was created and/or worked on). A project name can also be entered via Projects 3112. The system can provide to the user, based upon the user entered data, any changes made, for example, to any project PSs and/or other information (e.g., Test Procedures). A complete list of all changes made to a project can be provided via Audit 3114 icon (and/or Audit tab 3101f). A list of Master Administrators who can, for example, add an organization can also be viewed via button 3104.

[0189] Once an organization has been added, Users 3110 associated with the organization can add a WBS by, for example, selecting the Project 3112 icon associated with the Organization 3108 of interest, which will take the user to an exemplary screen shot such as shown in FIG. 32. Via FIG. 32, a user can select one of the Add WBS buttons 3204, as will be explained in further detail with regard to FIGS. 33-36. Once an organization has been entered, information pertaining to the WBS (Work Breakdown Structure) 3208 and Publishing Format 3210 are preferably displayed. A user can also Edit 3212 and/or Delete 3214 a WBS once it has been entered.

[0190] Upon selecting one of the Add WBS buttons 3204, an exemplary display such as shown in FIG. 33 preferably appears, where a user begins the process of creating a tailored sequence of PSs. The user can enter a New WBS Name* 3304. The asterisk (*) can optionally be utilized to indicate to the user that data entry is mandatory. While creating a tailored sequence of PSs, the user can also optionally use either a predefined (e.g., shipped with the system) sequence of PSs, or base the new sequence of PSs of a sequence of tailored sequence steps that the user has previously defined. WBS A associated with each or any of the DITSCAP, NIACAP and/or Treasury/IRS methodologies can therefore be a predefined sequence of PSs, whereas WBS B associated with each or any of the DITSCAP, NIACAP and/or Treasury/IRS methodologies can be a tailored sequence steps that the user has previously defined. Any number WBSs that use either predefined or tailored sequence steps can be associated with each of the DITSCAP, NIACAP and/or Treasury/IRS methodologies. This feature of the present invention advantageously allows a user to customize his own WBS, by utilizing an existing WBS to expedite the process.

[0191] In this regard, the user can select, for example, a predefined or user-tailored DISTCAP 3306, NIACAP 3308, or Treasury/IRS 3310 Work Breakdown Structure (WBS) upon which to base the WBS entered at 3304. Thus, if the user wants to model the WBS after one of the DITSCAP 3306, NIACAP 3308, or Treasury/IRS Work Breakdown Structures (e.g., WBS A 3312), the user could select one of the six shown WBSs (with two being shown under each of the DITSCAP 3306, NIACAP 3308, and Treasury/IRS 3310 WBSs). Alternatively, the user can create a new WBS that is not based on a DITSCAP, NIACAP, or Treasury/IRS WBS by selecting the OK button 3314 without selecting one of the six shown WBSs.

[0192] As shown in FIG. 34, once a WBS 3401 has been added, Work Products (WPs) for the WBS 3401 can be added by selecting one of the Add Work Product 3402 buttons. When an Add Work Product 3402 button is selected, an exemplary display such as shown in FIG. 35 appears, where a user can enter a Work Product Name 3504. The Available Process Steps are shown in window 3506, from which the user can select which Process Steps he wishes to associate with the Work Product Name 3504. The Selected Process Steps are shown in window 3508. The user can add process steps via window 3506 one at a time by selecting button 3514, or add all available process steps by selecting button 3518. Selected process steps can similarly be removed from window 3508 by clicking buttons 3516 and 3520, respectively.

[0193] The user can also select Prerequisite Work Products that are displayed in window 3510, which, when selected, are the WPs that must be completed before the Work Product entered at 3504 can begin. One or more prerequisite work products individually can be added via button 3522, whereas all prerequisite work products can simultaneously be added via button 3526. Prerequisite work products can be similarly removed by selecting buttons 3524 and 3528, respectively. Selections can be saved by selecting button 3530, canceled by selecting button 3532, and reset by selecting button 3534. Selecting cancel button 3532 can, for example, return the user to the previous screen, whereas selecting reset button 3534 can reset FIG. 35 to its default.

[0194] Returning now to FIG. 34, the user can enter a Description 3408 for a selected WP. By selecting an Edit icon 3410, the user will be returned to FIG. 35, where the WP can be edited. The user can also delete a WP by selecting the Delete 3412 icon associated with the WP that the user wishes to delete. The user can either save the WP(s) by selecting the Save 3404 icon, or cancel any changes by selecting the Cancel 3406 icon. Finally, the user can run an integrity check by selecting icon 3414, which will display a screen such as (but not necessarily the one) shown in FIG. 36.

[0195] FIG. 36 shows an illustrative user-defined workflow. As shown, WP Definition 3602 must be completed before starting the Requirements 3604 and Components 3606 WPs. The Requirements 3604 and Components 3606 WPs, in turn, must be completed before starting the Cert Level 3608 WP. The remaining listed WPs follow the same prerequisite pattern. FIG. 36 can be used by a user to ensure that prerequisites are properly defined, and to avoid a situation such as defining a project where two WPs are prerequisites for each other.

[0196] FIG. 37 is an exemplary screen shot that enables a user to add and/or edit information pertaining to Roles/Titles 3702 and/or Reactors (e.g., a user) for a particular Organization 3706. FIG. 37 can appear by selecting, for example, React tab 3101b. If a user selects the Roles/Titles icon 3702, he will preferably be taken to an exemplary screen such as shown in FIG. 38.

[0197] Exemplary roles can be, for example, at least one of: certification and accreditation analyst, computer security incident response capabilities representative, privacy advocates office representative, disclosure office representative, vulnerabilities office representative, technical contingency planning document representative, request for information system originator, owner of business system, certification and accreditation request for information system coordinator, critical infrastructure protection representative, system point of contact, principal accrediting authority, certification and accreditation administrator, and certification and accreditation chief.

[0198] With regard to FIG. 38, any Role(s) and/or Title(s) associated with the Organization 3706 are shown. Specifically, in FIG. 38, the Role/Title 3806 of Approver is shown, as is a Description 3808 of the Role/Title 3808. By selecting Edit icon 3810, the user can edit information pertaining to the Role/Title 3806 and/or Description 3808 thereof. By selecting the Delete 3812 icon, the user can delete a user-defined Role/Title (e.g., Approver). By selecting the Add Role/Title button 3804, the user will be advanced to an exemplary screen such as shown by FIG. 39.

[0199] FIG. 39 is an exemplary screen shot that enables a user to add a Role/Title. In order to define a Title*, the user must provide a role/title name in text box 3904. The asterisk (*) indicates that the field is mandatory. Other symbols and/or characters can also be used to designate mandatory fields. In the Description: text box 3906, the user can optionally enter a description of the Title (e.g., Approver). The user can save the results by selecting the Save button 3908. Selecting the Reset button 3910 can reset the screen, for example, to its default condition. Clicking Cancel button 3912 can return the user to, for example, the previous screen.

[0200] FIG. 40 is an exemplary screen shot that shows a reactor (e.g., user) associated with a particular organization. The First Name 4004, Last Name 4006, Email 4008, Telephone 4010, and Title 4012 of each user is displayed. Additional or less information for each user can also be displayed. By selecting Edit icon 4014, the user can edit information pertaining to a reactor. By selecting the Delete 4016 icon, the user can delete a reactor (e.g., Robert Jones). By selecting the Add Reactor button 4002, the user will be taken to an exemplary screen such as shown by FIG. 41, which allows a user to add a reactor. Via text boxes 4104, 4106, 4108 and 4110, a user can add information pertaining to the reactor's First Name, Last Name, Email, and Telephone, respectively. Via, for example, pull down menu 4112, the user can also associate a title/role with the reactor. As previously discussed, roles/titles can be defined, for example, via FIG. 39. As previously noted, an asterisk (*) next to a field name (e.g., First Name*) indicates that the user must provide information associated therewith. The user can save the results by selecting the Save button 4114. Selecting the Reset button 4116 will preferably reset the screen to its default condition. Selecting the Cancel button 4118 can return the user to, for example, the previous screen.

[0201] FIG. 42 is an exemplary screen shot that allows a user to view projects and/or add a project. FIG. 42 can appear when a user, for example, selects Projects tab 3101c. To add a project, the use can select the Add Project button 4202, which will preferably take the user to an exemplary screen as shown in FIG. 43. Via text boxes 4302 and 4304, a user can add information pertaining to the Project Name*, and Description*, respectively. In one embodiment of the present invention, users can also be provided (by, for example, the assignor and/or licensor of the present invention) a Subscription Key* 4306, which can be used, for example, to unlock the application (e.g., the FIGS. described herein pertaining to, for example, screen shots). In at least some embodiments, a system administrator, for example, can assign a client/user a matching (e.g., paired) subscription key and organization, each of which must be correctly entered to gain access to the system. Similarly, a project name can also be associated with a subscription key. In addition, in accordance with at least some embodiments, the Subscription Key* 4306 can also encompass the expiration date (e.g., the date at which a user's and/or organization's access terminates), publishing format (e.g., DITSCAP, NIACAP, or Treasury/IRS), and department/services name (e.g., DoD/Navy, Treasury/IRS). Via the Status* field 4307, a user can designate whether the project is Active or Inactive. In accordance with at least some embodiments of the present invention, users can access at least a portion of one or more projects (e.g., one or more PSs) to which they have been granted user rights, whereas users (other than, for example, a system administrator) would not be granted access to any portion of a project having an inactive status. If a user selects the Copy from an existing project box 4308, the user can use another project as the baseline for the project currently being defined. The user can select the Reset button 4312, which will reset the screen to its default condition. Clicking Cancel button 4118 can return the user to, for example, the previous screen. If the user selects the Continue button 4310, the user can be advanced to, for example, a subsequent screen, such as shown in FIG. 44, which allows a user to select, for example, a project using either the DITSCAP Classic 4402 (generally associated with, for example, FIGS. 1-30) or DITSCAP Workflow 4404 methodology (generally associated with, for example, FIGS. 31-55).

[0202] FIG. 45 is an exemplary screen shot that allows a user to define project access for a given Project 4502 and WBS 4404 associated therewith. For each WP shown at 4501 (e.g., Definition, Requirements, etc.), the user can determine whether other users associated with the project can Read 4506, Write 4508, Submit 4512, or Approve 4514 each respective WP. If the user checks None 4510, other users will preferably not have access to any of the Read 4506, Write 4508, Submit 4512, or Approve 4514 functions. The user can save the results by selecting the Save button 4516. Selecting the Reset button 4518 will reset the screen to its default condition. Clicking Cancel button 4520 can return the user to, for example, the previous screen.

[0203] FIG. 46 is an exemplary screen shot, similar to FIG. 42, that shows two projects, the WPM Project and Project A. The Set Notifications 4208 icon, Project Analysts 420 icons, and Assign Analysts 4212 icons appear in accordance with how the projects have been defined. Specifically, the absence of a Set Notification 2408 icon for Project A indicates that no users associated with Project A will receive an electronic notification upon the occurrence of a predefined event.

[0204] FIG. 47 is an exemplary screen shot that allows a user to set project notification by selecting, for example, a Set Notification 4208 icon such as shown in FIG. 48. As shown in FIG. 47, notification can be set for each Work Product 4706. For example, by selecting the Set Notification 4708 icon associated with the WP Definition 4710, the user can be advanced to a screen such as shown in FIG. 48, which allows a user to view project notification for a particular user, and/or add additional notification parameters. As shown, the WP, which has been illustratively selected via FIG. 47, is Definition 4802. FIG. 48 shows that user Robert Jones will be notified (as indicated by the five Ys) when the WP Definition is opened by another user 4808, submitted by another user 4810, reopened by another user 4812, or disapproved 4816. In accordance with at least some embodiments of the present invention, the notifications shown in FIG. 48 (and other notifications generally) can be implemented by, for example, using state changes in the WP. For example, upon approval of a WP, state changes for the approved WP (and/or additional WPs) could trigger the opening of any successor WPs.

[0205] Selecting the Edit 4816 icon associated with a user (e.g., Robert Jones) will allow a user to edit the notifications for that particular user (e.g., change one or more Y to an N, which would indicate that the user would not be notified upon the occurrence of the event for which no has been selected). A user can also delete all notifications for a user (e.g., Robert Jones) associated with a WP (e.g., Definition), by selecting the Delete icon 4820 for that particular user. If the user selects the Add Notification icon, he will preferably be advanced to a screen such as shown in FIG. 49.

[0206] FIG. 49 is an exemplary screen shot that allows a user to set notification parameters for a particular user. The WP Definition remains under consideration, as indicated at 4802. Via, for example, the pulldown menu at 4904, the user can select the Title (User)* for which he wishes to set notification(s) 4904. As shown at 4906, the user (e.g., Robert Jones) can either be notified, or not notified, when the WP Definition is Opened, Submitted, Re-Opened, Approved, or Disapproved. The user can save the results by selecting the Save button 4910. Selecting the Reset button 4912 will reset the screen to its default condition. Clicking Cancel button 4914 can return the user to, for example, the previous screen.

[0207] FIG. 50 is an exemplary flow diagram of the WPM process. At decision step 5002, the user determines whether to add a WBS. If no WBS is added, the process ends 5024. If the user decides to add a WBS, at decision step 5004 the user determines whether to base the new WBS on an existing WBS. If the user bases the new WBS on an existing WBS, the user selects an existing WBS at block 5006 (by, for example, FIG. 33). If the user does not base the new WBS on an existing WBS, the user indicates that an existing WBS will not be used (by for example, clicking on the OK button 3314 in FIG. 33 without selecting a DISTCAP 3306, NIACAP 3308, or Treasury/IRS 3310 WBS). At block 5010, the user adds one or more WPs to the WBS and, at decision step 5012, determines whether there will be any prerequisite WPs before beginning another WP. If, as discussed, for example, with regard to FIG. 35, there are prerequisite steps, the user adds the prerequisite steps at block 5014. If there are no prerequisite steps, or after block 5014, the user adds roles associated with the WBS (as discussed, for example, with regard to FIGS. 38-39). At block 5018, the user adds reactors to the WBS (as discussed, for example, with regard to FIGS. 40-41). At decision step 5020, the user determines whether any of the reactors need to be notified upon, for example, the opening, completion, or commencement of a WP. If it is determined that any of the reactors should be notified, the user sets user notification(s) (as discussed, for example, with regard to FIGS. 47-49). If no user notification is required, or after user notification is set at block 5022, the process ends 5024.

[0208] The techniques of the present invention may be implemented on a computing unit such as that depicted in FIG. 51. In this regard, FIG. 51 is an illustration of a computer system which is also capable of implementing some or all of the computer processing in accordance with at least some computer implemented embodiments of the present invention. The procedures described herein are presented in terms of program procedures executed on, for example, a computer or network of computers (as shown, for example, in FIG. 54).

[0209] Viewed externally, in FIG. 51, a computer system designated by reference numeral 5100 has a computer portion 5102 having disk drives 5104 and 5106. Disk drive indications 5104 and 5106 are merely symbolic of a number of disk drives which might be accommodated by the computer system. Typically, these could include a floppy disk drive 5104, a hard disk drive (not shown externally) and a CD ROM indicated by slot 5106. The number and type of drives vary, typically with different computer configurations. Disk drives 5104 and 5106 are in fact optional, and for space considerations, are easily omitted from the computer system used in conjunction with the production process/apparatus described herein.

[0210] The computer system 5100 also has an optional display 5108 upon which information, such as the screens illustrated in, for example, FIGS. 4-10, etc. may be displayed. In some situations, a keyboard 5110 and a mouse 5112 are provided as input devices through which input may be provided, thus allowing input to interface with the central processing unit 5102. Then again, for enhanced portability, the keyboard 5110 is either a limited function keyboard or omitted in its entirety. In addition, mouse 5112 optionally is a touch pad control device, or a track ball device, or even omitted in its entirety as well, and similarly may be used as an input device. In addition, the computer system 5100 may also optionally include at least one infrared (or radio) transmitter and/or infrared (or radio) receiver for either transmitting and/or receiving infrared signals.

[0211] Although computer system 5100 is illustrated having a single processor, a single hard disk drive and a single local memory, the system 5100 is optionally suitably equipped with any multitude or combination of processors or storage devices. Computer system 5100 is, in point of fact, able to be replaced by, or combined with, any suitable processing system operative in accordance with the principles of the present invention, including hand-held, laptop/notebook, mini, mainframe and super computers, as well as processing system network combinations of the same.

[0212] FIG. 52 illustrates a block diagram of the internal hardware of the computer system 5100 of FIG. 51. A bus 5202 serves as the main information highway interconnecting the other components of the computer system 5100. CPU 5204 is the central processing unit of the system, performing calculations and logic operations required to execute a program. Read only memory (ROM) 5206 and random access memory (RAM) 5208 constitute the main memory of the computer 5102. Disk controller 5210 interfaces one or more disk drives to the system bus 5202. These disk drives are, for example, floppy disk drives such as 5104 or 5106, or CD ROM or DVD (digital video disks) drive such as 5212, or internal or external hard drives 5214. As indicated previously, these various disk drives and disk controllers are optional devices.

[0213] A display interface 5218 interfaces display 5208 and permits information from the bus 5202 to be displayed on the display 5108. Again as indicated, display 5108 is also an optional accessory. For example, display 5108 could be substituted or omitted. Communications with external devices, for example, the other components of the system described herein, occur utilizing communication port 5216. For example, optical fibers and/or electrical cables and/or conductors and/or optical communication (e.g., infrared, and the like) and/or wireless communication (e.g., radio frequency (RF), and the like) can be used as the transport medium between the external devices and communication port 5216. Peripheral interface 5220 interfaces the keyboard 5110 and the mouse 5112, permitting input data to be transmitted to the bus 5202.

[0214] In alternate embodiments, the above-identified CPU 5204, may be replaced by or combined with any other suitable processing circuits, including programmable logic devices, such as PALs (programmable array logic) and PLAs (programmable logic arrays). DSPs (digital signal processors), FPGAs (field programmable gate arrays), ASICs (application specific integrated circuits), VLSIs (very large scale integrated circuits) or the like.

[0215] In general, it should be emphasized that the present invention can be implemented in hardware, software or a combination thereof. In such embodiments, the various components and steps would be implemented in hardware and/or software to perform the functions of the present invention. Any presently available or future developed computer software language and/or hardware components can be employed in such embodiments of the present invention. For example, at least some of the functionality mentioned above could be implemented using Visual Basic, C, C++, or any assembly language appropriate in view of the processor(s) being used. It could also be written in an interpretive environment such as Java and transported to multiple destinations to various users.

[0216] One of the implementations of the invention is as sets of instructions resident in the random access memory 5208 of one or more computer systems 5100 configured generally as described above. Until required by the computer system, the set of instructions may be stored in another computer readable memory, for example, in the hard disk drive 5214, or in a removable memory such as an optical disk for eventual use in the CD-ROM 5212 or in a floppy disk (e.g., floppy disk 5302 of FIG. 53) for eventual use in a floppy disk drive 5104, 5106. Further, the set of instructions (such as those written in Java, HyperText Markup Language (HTML), Extensible Markup Language (XML), Standard Generalized Markup Language (SGML), and/or Structured Query Language (SQL)) can be stored in the memory of another computer and transmitted via a transmission medium such as a local area network or a wide area network such as the Internet when desired by the user. One skilled in the art knows that storage or transmission of the computer program medium changes the medium electrically, magnetically, or chemically so that the medium carries computer readable information.

[0217] FIG. 54 is an exemplary network implementation of (and/or utilized by) at least some embodiments of the present invention. As shown, one or more computer systems 5100 can be operationally connected to a network 5401 such the Internet, a LAN, WAN, or the like. The network implementation of at least some embodiments of the present invention enables two or more users to collaboratively work, via the network 5401, on one or more C&As. The computer portion 5102a comprises a WEB C&A component 5402 (generally corresponding, for example to FIGS. 1-30) and a Work Product Manager (WPM) component 5405 (generally corresponding, for example, to FIGS. 31-55). WEB C&A component 5402 and WPM component 5404 are shown separately to indicate that the WPM is an optional aspect of the WEB C&A component, and is not required for the operation thereof.

[0218] FIG. 55 shows an alternative structure of WEB C&A component 5402 and WPM component 5404. Specifically, the WEB C&A component 5402 and the WPM component can be combined into a single module 5502. Module 5502, in turn, can comprise process step module 5504, test procedure module 5506, threat element score generation module 5508, risk assessment module 5510, and printing module 5512. In accordance with at least some embodiments of the present invention, process step module 5504 enables the user to choose one or more of the plurality of predefined process steps pertaining to collecting information descriptive of at least one aspect of the target system hardware and/or software, and/or a physical environment in which the target system operates. In accordance with at least some embodiments of the present invention, test procedure module 5506 enables the system and/or user to select at least one test procedure against which the target system is tested to satisfy at least one predefined standard, regulation and/or requirement. In accordance with at least some embodiments of the present invention, threat element score generation module 5508 generates a score for each of a plurality of threat elements, each score indicating a likelihood of that threat element affecting and/or impacting the target system. In accordance with at least some embodiments of the present invention, risk assessment module 5510 obtains a threat correlation indication associated with the one or more test procedures, and determines a risk assessment by comparing each score generated by threat element score generation module 5508 with a corresponding threat correlation indication. The threat correlation indication indicates a relative potential of one or more given threats to exploit a vulnerability caused by a failure of said at least one test procedure. Finally, in accordance with at least some embodiments of the present invention, printing module 5512 can be used to print a documentation package that will enable a determination to be made whether the target system complies with the at least one predefined standard, regulation and/or requirement. Of course, it should be understood that the present invention contemplates other configurations of modules, and is not limited to the specific structural implementation noted above. For example, the modules do not necessarily have to have the discrete or “bright line functionality” as discussed above; that is the modules may predominately have the functionality as described, but also include some functionality of another module or modules (e.g. process step module 5504 may, in certain embodiments, include a portion of the functionality of, for example, the test procedure module 5506 and/or the threat element score generation module).

[0219] FIG. 56 is an entity relationship diagram (ERD) that describes the attributes of entities and the relationships among them, and illustrates the basic data abstraction of an embodiment of the system. As known to those skilled in the art, an ERD is a conceptual representation of real world objects and the relationships between them. It defines information that the systems create, maintain, process, and delete, as well as the inherent relationships that are supported by the database (i.e., data store).

[0220] At least some embodiments of the present invention can utilize a relational database to store and organize all information such as, for example, test procedures, standards/regulations, and user entered information. The design of an embodiment of the database is provided in the ERD shown in FIG. 56. The database is initially populated with security requirements, test procedures and related information to facilitate the operation of the system. As information is entered by the user and calculated by the system, it is also recorded in the database. At least some embodiments of the present invention produce output documentation that can be formatted in accordance with, for example, DITSCAP and/or NIACAP standard(s).

[0221] The ERD shown in FIG. 56 uses conventional notation. Each entity, as shown in FIG. 56, comprises a rectangular box. A one-to-one (1:1) relationship indicates that each occurrence of entity A is related to only one of entity B and each occurrence of B is related to only one occurrence of A. A 1:1 relationship is indicated by a single line connecting two entities.

[0222]

[0223] A one-to-many (1:M) relationship indicates that each occurrence of entity A is related to one or more occurrences of entity B, but each occurrence of entity B is related to only one occurrence of entity A. The two vertical lines shown below indicate that entity A is associated only with entity B. If the two vertical lines are not present, entity A can be associated with two or more entities (e.g., B, C and/or D).

[0224]

[0225] A many-to-many (N:M) relationship shows that each occurrence of entity A is related to one or more occurrences of entity B, and each occurrence of entity B is related to one or more occurrences of entity A.

[0226]

[0227] If there can be occurrences of one entity that are not related to at least one occurrence of the other entity, then the relationship is optional and this is shown by the use of a dashed line.

[0228]

[0229] As known to those skilled in the art, a data dictionary, as provided below, defines and specifies the data elements in the system. The data dictionary shown below can be used either as a stand-alone system or as an integral part of the database. Data integrity and accuracy is better ensured in the latter case.

[0230] An instance of an entity shown in FIG. 56 will represent one or more lines associated with the Table column in the data dictionary provided below (i.e., an entity shown in FIG. 56 can have many data items/attributes). These data items, representing an attribute of each respective entity to which it belongs, are shown in each line of the data dictionary. The data dictionary also provides the DataType (e.g., varchar, bit, decimal, char, text, int, etc.), and Length (in characters) of the field. The Precision column is applicable only to numerical data and represents the maximum number of significant digits. The Null column indicates whether the field defaults to a null value. FIG. 56 and the data dictionary can be used to produce, for example, the SQL code required to create the data structures in the database.

[0231] The tables below provides an exemplary data dictionary that can be used with the ERD of FIG. 56.

[0232]

TABLE REPORT
Database summary
Target DBMS: Microsoft SQL Server
Number of tables: 104
Number of columns: 731
Number of indexes: 8
Number of foreign keys: 69
Last map date: Jan. 1, 1970
Extended attributes: PRIMARY
Tables	Columns	Indexes	Foreign keys	Notes
WPM_WPSrc	5	0	0
WPM_WPPrereqSrc	3	0	0
WPM_WBSSrc	5	0	0
WPM_StateTranLkp	3	0	0
WPM_State	2	0	0
WPM_PSSrc	7	0	1
WPM_ProjXEE	6	0	1
WPM_ProjWPHistory	7	0	1
WPM_ProjWP	6	0	1
WPM_ProjPS	7	0	2
WPM_ProjPrereq	3	0	1
WPM_ProjEventRules	4	0	1
WPM_ProjDefPerm	3	0	1
WPM_ProjAnalystPerm	4	0	2
WPM_OrgWP	6	0	1
WPM_OrgWBS	5	0	1
WPM_OrgPS	8	0	1
WPM_OrgPrereq	4	0	1
WPM_OrgEventRules	5	0	1
WPM_EventRulesSrc	4	0	0
WCA_TestProcSrc	17	0	0
WCA_SysUserCategory	3	0	0
WCA_SWSource	7	0	0
WCA_SwFamilyLookup	4	0	0
WCA_StaticLookup	1	0	0
WCA_StaticLkpDtl	3	0	1
WCA_Stages	2	0	0
WCA_SecRqmtSrc	13	0	1
WCA_SecReqCritQ	3	0	0
WCA_SecRegSrc	13	0	1
WCA_RiskLvlCode	2	0	0
WCA_RiskDetermin	3	1	1
WCA_PublishFmt	2	0	0
WCA_ProjUserAccess	4	0	2
WCA_ProjUser	2	0	1
WCA_ProjThreatEnv	21	0	1
WCA_ProjTestProc	34	0	1
WCA_ProjSysThreat	5	0	1
WCA_ProjSystemUser	8	0	1
WCA_ProjSysLvlRisk	4	0	1
WCA_ProjSysInterf	4	0	1
WCA_ProjSWInven	9	0	0
WCA_ProjRqmt	23	1	1
WCA_ProjRiskElem	18	0	1
WCA_ProjReference	12	0	1
WCA_ProjPlatSW	3	0	1
WCA_ProjPlatCat	30	0	1
WCA_ProjPersonnel	19	0	1
WCA_ProjParaFig	9	0	1
WCA_ProjMilestone	6	0	1
WCA_ProjFileData	4	0	1
WCA_ProjFile	6	0	1
WCA_ProjEventStatus	7	0	1
WCA_ProjEquipSW	3	0	1
WCA_ProjEquipInven	30	0	1
WCA_Project	21	1	1
WCA_ProjDocTTL	8	0	1
WCA_ProjDocPara	7	0	1
WCA_ProjDefinitions	4	0	1
WCA_ProjDefAccess	3	0	2
WCA_ProjDataFlow	4	0	1
WCA_ProjConTestRes	23	1	1
WCA_ProjCleanStat	5	0	1
WCA_ProjCkListRes	4	0	1
WCA_ProjCharDtl	4	0	2
WCA_ProjAppdxFile	11	0	1
WCA_ProjAcronym	4	0	1
WCA_ProjAcBoundary	4	0	1
WCA_PageAttrs	6	0	0
WCA_OSSource	7	0	0
WCA_OsFamilyLookup	4	0	0
WCA_OrgUser	2	1	1
WCA_Organization	3	0	0
WCA_MLSecClass	6	0	0
WCA_MinSeCkListSrc	6	0	0
WCA_MarkerLookup	4	0	0
WCA_LookupMgr	8	0	0
WCA_LevelDetermin	6	0	0
WCA_InfoCategory	5	0	0
WCA_HwFamilyLookup	4	0	0
WCA_HelpExampleSrc	13	0	0
WCA_DocTmplSrc	6	0	0
WCA_DocParaTTLSrc	6	0	0
WCA_DeptServCode	4	1	0
WCA_DefSecRegSrc	3	0	1
WCA_DefinitionSrc	5	0	1
WCA_ClassWeight	5	0	0
WCA_CharSrc	1	0	0
WCA_AuditObjects	4	0	0
WCA_AuditLog	19	0	0
WCA_ApplEventSrc	5	0	0
WCA_AppdxTTLSrc	5	0	0
WCA_AcronymSrc	5	0	1
UserRole	3	0	2
UserPwdHistory	3	0	1
TableKeys	3	0	0
RoleLogin	4	0	0
RCT_ProjWPActor	11	0	2
RCT_OrgTitleDefn	4	0	1
RCT_OrgActorDefn	7	0	2
InstallHistory	2	1	0
dtproperties	7	0	0
AppUser	8	1	0
AppProps	4	0	0

[0233]

AppProps
Owner: dbo
Target DB name: WCA310_D
Number of columns: 4
Number of indexes: 0
Number of foreign keys: 0
Extended attributes:
OnFileGroup PRIMARY
Clustered PK Yes
Columns	Data type	Allow NULLs	Value/Range
PropName	varchar(255)	Not allowed
PropVal	varchar(255)	Allowed
AppName	varchar(20)	Not allowed
PropDate	datetime	Allowed
Column Details
1. PropName
Physical data type: varchar(255)
Allow NULLs: Not allowed
2. PropVal
Physical data type: varchar(255)
Allow NULLs: Allowed
3. AppName
Physical data type: varchar(20)
Allow NULLs: Not allowed
4. PropDate
Physical data type: datetime
Allow NULLs: Allowed

[0234]

AppUser
Owner: dbo
Target DR name: WCA310_D
Number of columns: 8
Number of indexes: 1
Number of foreign keys: 0
Extended attributes:
OnFileGroup PRIMARY
Clustered PK No
Columns	Data type	Allow NULLs	Value/Range
userID	decimal(18.0)	Not allowed
userName (U1)	varchar(25)	Not allowed
userPassword	varchar(50)	Not allowed
firstName	varchar(20)	Allowed
lastName	varchar(20)	Allowed
phoneNumber	varchar(30)	Allowed
pwdLastChanged	datetime	Allowed
userEmail	varchar(50)	Allowed
	Indexes	Columns	Sort Order
	IX_AppUser_UserName (U1)	userName	Ascending
Foreign Keys	Child	Parent
FK_UserPwdHistory_	UserPwdHistory.userID	userID
AppUser
FK_UserRole_User	UserRole.userID	userID
FK_WPM_ProjAnalyst-	WPM_ProjAnalystPerm.userID	userID
Perm_AppUser
Column Details
1. userID
Physical data type: decimal(18.0)
Allow NULLs: Not allowed
2. userName (U1)
Physical data type: varchar(25)
Allow NULLs: Not allowed
3. userPassword
Physical data type: varchar(50)
Allow NULLs: Not allowed
4. firstName
Physical data type: varchar(20)
Allow NULLs: Allowed
5. lastName
Physical data type: varchar(20)
Allow NULLs: Allowed
6. phoneNumber
Physical data type: varchar(30)
Allow NULLs: Allowed
7. pwdLastChanged
Physical data type: datetime
Allow NULLs: Allowed
8. userEmail
Physical data type: varchar(50)
Allow NULLs: Allowed
Index details
IX_AppUser_UserName
Column(s): userName (Asc)
Unique: Yes
Extended attributes:
OnFileGroup PRIMARY
CLUSTERED No
IGNORE_DUP_KEY No
FILLFACTOR 90
PAD_INDEX No
DROP_EXISTING No
STATISTICS_NORECOMPUTE No

[0235]

dtproperties
Owner: dbo
Target DB name: WCA310_D
Number of columns: 7
Number of indexes: 0
Number of foreign keys: 0
Extended attributes:
OnFileGroup PRIMARY
TextImageOnGroup PRIMARY
Clustered PK Yes
Columns	Data Type	Allow NULLs	Value/Range
id	int identity	Not allowed
objectid	int	Allowed
property	varchar(64)	Not allowed
value	varchar(255)	Allowed
lvalue	image	Allowed
version	int	Not allowed
uvalue	nvarehar(255)	Allowed
Column Details
1. id
Physical data type: int identity
Allow NULLs: Not allowed
2. objectid
Physical data type: int
Allow NULLs: Allowed
3. property
Physical data type: varchar(64)
Allow NULLs: Not allowed
4. value
Physical data type: varchar(255)
Allow NULLs: Allowed
5. lvalue
Physical data type: image
Allow NULLs: Allowed
6. version
Physical data type: int
Allow NULLs: Not allowed
7. uvalue
Physical data type: nvarchar(255)
Allow NULLs: Allowed

[0236]

InstallHistory
Owner: dbo
Target DR name: WCA310_D
Number of columns: 2
Number of indexes: 1
Number of foreign keys: 0
Extended attributes:
OnFileGroup PRIMARY
Clustered PK No
Columns	Data type	Allow NULLs	Value/Range
InstallDesc (I1)	varchar(50)	Not allowed
InstallDate (I1)	datetime	Not allowed
	Indexes	Columns	Sort order
	IX_InstallHistory (I1)	InstallDesc	Ascending
		InstallDate	Ascending
	Column Details
	1. InstallDesc (I1)
	Physical data type: varchar(50)
	Allow NULLs: Not allowed
	2. InstallDate (I1)
	Physical data type: datetime
	Allow NULLs: Not allowed
	Index details
	IX_InstallHistory
	Column(s): InstallDesc (Ase)
	InstallDate (Asc)
	Unique: No
	Extended attributes:
	OnFileGroup PRIMARY
	CLUSTERED No
	IGNORE_DUP_KEY No
	FILLFACTOR 0
	PAD_INDEX No
	DROP_EXISTING No
	STATISTICS_NORECOMPUTE No

[0237]

RCT_OrgActorDefn
Owner: dbo
Target DB name: WCA310_D
Number of columns: 7
Number of indexes: 0
Number of foreign keys: 2
Extended attributes:
OnFileGroup PRIMARY
Clustered PK Yes
Columns	Data type	Allow NULLs	Value/Range
actorID	int	Not allowed
titleID (FK)	int	Not allowed
fName	varchar(50)	Not allowed
Iname	varchar(30)	Not allowed
email	varchar(50)	Not allowed
phoneNumber	varchar(50)	Allowed
orgID (FK)	decimal(18.0)	Not allowed
Foreign keys	Child	Parent
FK_RCT_Actor-	titleID	RCT_OrgTitle-
Defn_RCT_TitleDefn		Defn.titleID
FK_RCT_Actor-	orgID	WCA_Organization.orgID
Defn_WCA_Organization
FK_RCT_WP-	RCT_ProjWP-	actorID
Actor_RCT_ActorDefn	Actor.actorID
Column details
1. actorID
Physical data type: int
Allow NULLs: Not allowed
2. titleID (FK)
Physical data type: int
Allow NULLs: Not allowed
3. fName
Physical data type: varchar(50)
Allow NULLs: Not allowed
4. Iname
Physical data type: varchar(30)
Allow NULLs: Not allowed
5. email
Physical data type: varchar(50)
Allow NULLs: Not allowed
6. phoneNumber
Physical data type: varchar(50)
Allow NULLs: Allowed
7. orgID (FK)
Physical data type: decimal(18.0)
Allow NULLs: Not allowed
Foreign keys
FK_RCT_ActorDefn_RCT_TitleDefn
Definition: Child Parent
titleID RCT_OrgTitleDefn.titleID
Relationship type: Non-Identifying
Cardinality: One-to-Zero-or-More
Allow NULLs: Not allowed
Verb phrase: hasFK_RCT_ActorDefn_RCT_TitleDefn
Inverse phrase: is of
Ref. Integrity on update: No Action
Ref. Integrity on delete: No Action
FK_RCT_ActorDefn_WCA_Organization
Definition: Child Parent
orgID WCA_Organization.orglD
Relationship type: Non-Identifying
Cardinality: One-to-Zero-or-More
Allow NULLs: Not allowed
Verb phrase: hasFK_RCT_ActorDefn_WCA_Organization
Inverse phrase: is of
Ref. Integrity on update: No Action
Ref. Integrity on delete: No Action

[0238]

RCT_OrgTitleDefn
Owner: dbo
Target DB name: WCA310_D
Number of columns: 4
Number of indexes: 0
Number of foreign keys: 1
Extended attributes:
OnFileGroup PRIMARY
Clustered PK Yes
Columns	Data type	Allow NULLs	Value/Range
titleID	int	Not allowed
titleDesc	varchar(100)	Not allowed
titleAcronym	varchar(20)	Not allowed
orgID (FK)	decimal(18.0)	Not allowed
Foreign keys	Child	Parent
FK_RCT_Title-	orgID	WCA_Organi-
Defn_WCA_Organization	zation.orgID
FK_RCT Actor-	RCT_Org-	titlelD
Defn_RCT_TitleDefn	ActorDefn.titleID
Columns details
1. titleID
Physical data type: int
Allow NULLs: Not allowed
2. titleDesc
Physical data type: varchar(100)
Allow NULLs: Not allowed
3. titleAcronym
Physical data type: varchar(20)
Allow NULLs: Not allowed
4. orgID (FK)
Physical data type: decimal(18.0)
Allow NULLs: Not allowed
Foreign keys details (child)
FK_RCT_TitleDefn_WCA_Oganization
Definition: Child Parent
orgID WCA_Organization.orgID
Relationship type: Non-Identifying
Cardinality: One-to-Zero-or-More
Allow NULLs: Not allowed
Verb phrase: hasFK_RCT_TitleDefn_WCA_Organization
Inverse phrase: is of
Ref. Integrity on update: No Action
Ref. Integrity on delete: No Action

[0239]

RCT_ProjWPActor
Owner: dbo
Target DB name: WCA310_D
Number of columns: 11
Number of indexes: 0
Number of foreign keys: 2
Extended attributes:
OnFileGroup PRIMARY
Clustered PK Yes
Columns	Data type	Allow NULLs	Value/Range
PID (FK)	decimal(18.0)	Not allowed
WPID	decimal(18.0)	Not allowed
actorID (FK)	int	Not allowed
openNotify	char(1)	Not allowed
submitNotify	char(1)	Not allowed
approveNotify	char(1)	Not allowed
disapproveNotify	char(1)	Not allowed
openAttachment	varchar(100)	Allowed
submitAttachment	varchar(100)	Allowed
approveAttachment	varchar(100)	Allowed
disapproveAttachment	varchar(100)	Allowed
Foreign keys	Child	Parent
FK_RCT_WPActor_RCT_ActorDefn	actorID	RCT_OrgActor-
		Defn.actorID
FK_RCT_WPActor_WCA_Project	PID	WCA_Project.PID
Column details
1. PID (FK)
Physical data type: decimal(18.0)
Allow NULLs: Not allowed
2. WPID
Physical data type: decimal(18.0)
Allow NULLs: Not allowed
3. actorID (FK)
Physical data type: int
Allow NULLs: Not allowed
4. openNotify
Physical data type: char(1)
Allow NULLs: Not allowed
5. submitNotify
Physical data type: char(1)
Allow NULLs: Not allowed
6. approveNotify
Physical data type: char(1)
Allow NULLs: Not allowed
7. disapproveNotify
Physical data type: char(1)
Allow NULLs: Not allowed
8. openAttachment
Physical data type: varchar(100)
Allow NULLs: Allowed
9. submitAttachment
Physical data type: varchar(100)
Allow NULLs: Allowed
10. approveAttachment
Physical data type: varchar(100)
Allow NULLs: Allowed
11. disapproveAttachment
Physical data type: varchar(100)
Allow NULLs: Allowed
Foreign key details (child)
FK_RCT_WPActor_RCT_ActorDefn
Definition: Child Parent
actorID RCT_OrgActorDefn.actorID
Relationship type: Identifying
Cardinality: One-to-Zero-or-More
Allow NULLs: Not allowed
Verb phrase: hasFK_RCT_WPActor_RCT_ActorDefn
Inverse phrase: is of
Ref. Integrity on update: No Action
Ref. Integrity on delete: No Action
FK_RCT_WPActor_WCA_Project
Definition: Child Parent
PID WCA_Project.PID
Relationship type: Identifying
Cardinality: One-to-Zero-or-More
Allow NULLs: Not allowed
Verb phrase: hasFK_RCT_WPActor_WCA_Project
Inverse phrase: is of
Ref. Integrity on update: No Action
Ref. Integrity on delete: No Action

[0240]

RoleLogin
Owner: dbo
Target DB name: WCA310_D
Number of columns: 4
Number of indexes: 0
Number of foreign keys: 0
Extended attributes:
OnFileGroup PRIMARY
Clustered PK No
Columns	Data type	Allow NULLs	Value/Range
roleID	varchar(10)	Not allowed
dbRoleName	varchar(255)	Not allowed
dbRolePassword	varchar(255)	Not allowed
dbPwdLastChanged	datetime	Allowed
	Foreign keys	Child	Parent
	FK_UserRole_RoleLogin	UserRole.roleID	roleID
Column details
1. roleID
Physical data type: varchar(10)
Allow NULLs: Not allowed
2. dbRoleName
Physical data type: varchar(255)
Allow NULLs: Not allowed
3. dbRolePassword
Physical data type: varchar(255)
Allow NULLs: Not allowed
4. dbPwdLastChanged
Physical data type: datetime
Allow NULLs: Allowed

[0241]

TableKeys
Owner: dbo
Target DB name: WCA310_D
Number of columns: 3
Number of indexes: 0
Number of foreign keys: 0
Extended attributes:
OnFileGroup PRIMARY
Clustered PK No
Columns	Data type	Allow NULLs	Value/Range
TableName	varchar(30)	Not allowed
ColumnName	varchar(30)	Not allowed
KeyValue	decimal(18.0)	Not allowed
Column details
1. TableName
Physical data type: varchar(30)
Allow NULLs: Not allowed
2. ColumnName
Physical data type: varchar(30)
Allow NULLs: Not allowed
3. KeyValue
Physical data type: decimal(18.0)
Allow NULLs: Not allowed

[0242]

UserPwdHistory
Owner:	dbo
Target DB name:	WCA310_D
Number of columns:	3
Number of indexes:	0
Number of foreign keys:	1
Extended attributes:
OnFileGroup	PRIMARY
Clustered PK	No
Columns	Data type	Allow NULLs	Value/Range
userID (FK)	decimal(18, 0)	Not allowed
userPassword	varchar(50)	Not allowed
lastModified	datetime	Not allowed
Foreign keys	Child	Parent
FK_UserPwdHistory_AppUser	userID	AppUser.userID
Column details
1. userID (FK)
Physical data type:    decimal(18, 0)
Allow NULLs:   Not allowed
2. userPassword
Physical data type:    varchar(50)
Allow NULLs:   Not allowed
3. lastModified
Physical data type:    datetime
Allow NULLs:   Not allowed
Foreign key details (child)
FK_UserPwdHistory_AppUser
Definition:	Child	Parent
userID   AppUser.userID
Relationship type:	Identifying
Cardinality:	One-to-Zero-or-More
Allow NULLs:	Not allowed
Verb phrase:	hasFK_UserPwdHistory_AppUser
Inverse phrase:	is of
Ref. Integrity on update:	No Action
Ref. Integrity on delete:	No Action

[0243]

UserRole
Owner:	dbo
Target DB name:	WCA310_D
Number of columns:	3
Number of indexes:	0
Number of foreign keys:	2
Extended attributes:
OnFileGroup	PRIMARY
Clustered PK	No
Columns	Data type	Allow NULLs	Value/Range
userID (FK)	decimal(18, 0)	Not allowed
roleID (FK)	varchar(10)	Not allowed
status	char(1)	Allowed
	Foreign keys	Child	Parent
	FK_UserRole_User	userID	AppUser.userID
	FK_UserRole_RoleLogin	roleID	RoleLogin.roleID
Column details
1. userID (FK)
Physical data type:    decimal(18, 0)
Allow NULLs:   Not allowed
2. roleID (FK)
Physical data type:    varchar(10)
Allow NULLs:   Not allowed
3. status
Physical data type:    char(1)
Allow NULLs:   Allowed
Foreign key details (child)
FK_UserRole_User
Definition:	Child	Parent
userID   AppUser.userID
Relationship type:	Identifying
Cardinality:	One-to-Exactly-1
Allow NULLs:	Not allowed
Verb phrase:	hasFK_UserRole_User
Inverse phrase:	is of
Ref. Integrity on update:	No Action
Ref. Integrity on delete:	No Action
FK_UserRole_RoleLogin
Definition:	Child	Parent
roleID   RoleLogin.roleID
Relationship type:	Non-Identifying
Cardinality:	One-to-Zero-or-More
Allow NULLs:	Not allowed
Verb phrase:	hasFK_UserRole_RoleLogin
Inverse phrase:	is of
Ref. Integrity on update:	No Action
Ref. Integrity on delete:	No Action

[0244]

WCA_AcronymSrc
Owner:	dbo
Target DB name:	WCA310_D
Number of columns:	5
Number of indexes:	0
Number of foreign keys:	1
Extended attributes:
OnFileGroup	PRIMARY
TextImageOnGroup	PRIMARY
Clustered PK	No
	Columns	Data type	Allow NULLs	Value/Range
	acronym	varchar(50)	Not allowed
	asDescription	text	Allowed
	department (FK)	int	Not allowed
	service (FK)	int	Not allowed
	applPubFormat	varchar(50)	Allowed
Foreign keys	Child	Parent
FK_WCA_AcronymSrc_WCA_DeptServCode	department	WCA_DeptServCode.department
	service
		WCA_DeptServCode.service
Column details
1. acronym
Physical data type:    varchar(50)
Allow NULLs:   Not allowed
2. asDescription
Physical data type:    text
Allow NULLs:   Allowed
3. department (FK)
Physical data type:    int
Allow NULLs:   Not allowed
4. service (FK)
Physical data type:    int
Allow NULLs:   Not allowed
5. applPubFormat
Physical data type:    varchar(50)
Allow NULLs:   Allowed
Foreign key details (child)
FK_WCA_AcronymSrc_WCA_DeptServCode
Definition:	Child	Parent
department	WCA_DeptServCode.department
service   WCA_DeptServCode.service
Relationship type:	Non-Identifying
Cardinality:	One-to-Zero-or-More
Allow NULLs:	Not allowed
Verb phrase:	hasFK_WCA_AcronymSrc_WCA_DeptServCode
Inverse phrase:	is of
Ref. Integrity on update:	No Action
Ref. Integrity on delete:	No Action

[0245]

WCA_AppdxTTLSrc
Owner:	dbo
Target DB name:	WCA310_D
Number of columns:	5
Number of indexes:	0
Number of foreign keys:	0
Extended attributes:
OnFileGroup	PRIMARY
Clustered PK	No
Columns	Data type	Allow NULLs	Value/Range
document	varchar(50)	Allowed
title	varchar(255)	Allowed
letter	varchar(50)	Allowed
applPubFormat	varchar(50)	Not allowed
appendixType	varchar(50)	Not allowed
Column details
1. document
Physical data type:    varchar(50)
Allow NULLs:   Allowed
2. title
Physical data type:    varchar(255)
Allow NULLs:   Allowed
3. letter
Physical data type:    varchar(50)
Allow NULLs:   Allowed
4. applPubFormat
Physical data type:    varchar(50)
Allow NULLs:   Not allowed
5. appendixType
Physical data type:    varchar(50)
Allow NULLs:   Not allowed

[0246]

WCA_ApplEventSrc
Owner: dbo
Target DB name: WCA310_D
Number of columns: 5
Number of indexes: 0
Number of foreign keys: 0
Extended attributes:
OnFileGroup PRIMARY
Clustered PK No
Columns	Data type	Allow NULLs	Value/Range
EventlD	varchar(50)	Not allowed
StageName	varchar(50)	Allowed
Category	varchar(50)	Allowed
Severity	char(30)	Allowed
PubFormat	varchar(10)	Allowed
Column details
1. EventID
Physical data type: varchar(50)
Allow NULLs: Not allowed
2. StageName
Physical data type: varchar(50)
Allow NULLs: Allowed
3. Category
Physical data type: varchar(50)
Allow NULLs: Allowed
4. Severity
Physical data type: char(30)
Allow NULLs: Allowed
5. PubFormat
Physical data type: varchar(10)
Allow NULLs: Allowed

[0247]

WCA_AuditLog
Owner: dbo
Target DB name: WCA310_D
Number of columns: 19
Number of indexes: 0
Number of foreign keys: 0
Extended attributes:
OnFileGroup PRIMARY
TextImageOnGroup PRIMARY
Clustered PK No
Columns	Data type	Allow NULLs	Value/Range
id	int	Not allowed
PID	int	Allowed
ProjectName	varchar(250)	Allowed
TableName	varchar(25)	Allowed
KeyValues	varchar(250)	Allowed
StageName	varchar(50)	Allowed
ProcessStep	varchar(255)	Allowed
PageID	varchar(50)	Allowed
UserID	decimal(18, 0)	Allowed
IPAddress	varchar(16)	Not allowed
ActionDesc	text	Allowed
ActionStatus	char(20)	Allowed
ActionTime	datetime	Not allowed
EventType	varchar(50)	Allowed
ErrorMessage	text	Allowed
UserName	varchar(25)	Allowed
orgID	decimal(18, 0)	Allowed
orgName	varchar(50)	Allowed
sessionID	varchar(50)	Allowed
Column details
1. id
Physical data type: int
Allow NULLs: Not allowed
2. PID
Physical data type: int
Allow NULLs: Allowed
3. ProjectName
Physical data type: varchar(250)
Allow NULLs: Allowed
4. TableName
Physical data type: varchar(25)
Allow NULLs: Allowed
5. KeyValues
Physical data type: varchar(250)
Allow NULLs: Allowed
6. StageName
Physical data type: varchar(50)
Allow NULLs: Allowed
7. ProcessStep
Physical data type: varchar(255)
Allow NULLs: Allowed
8. PageID
Physical data type: varchar(50)
Allow NULLs: Allowed
9. UserID
Physical data type: decimal(18, 0)
Allow NULLs: Allowed
10. IPAddress
Physical data type: varchar(16)
Allow NULLs: Not allowed
11. ActionDesc
Physical data type: text
Allow NULLs: Allowed
12. ActionStatus
Physical data type: char(20)
Allow NULLs: Allowed
13. ActionTime
Physical data type: datetime
Allow NULLs: Not allowed
14. EventType
Physical data type: varchar(50)
Allow NULLs: Allowed
15. ErrorMessage
Physical data type: text
Allow NULLs: Allowed
16. UserName
Physical data type: varchar(25)
Allow NULLs: Allowed
17. orgID
Physical data type: decimal(18, 0)
Allow NULLs: Allowed
18. orgName
Physical data type: varchar(50)
Allow NULLs: Allowed
19. sessionID
Physical data type: varchar(50)
Allow NULLs: Allowed

[0248]

WCA_AuditObjects
Owner:	dbo
Target DB name:	WCA310_D
Number of columns:	4
Number of indexes:	0
Number of foreign keys:	0
Extended attributes:
OnFileGroup	PRIMARY
Clustered PK	No
Columns	Data type	Allow NULLS	Value/Range
id	int	Not allowed
tblName	varchar(25)	Allowed
tblKeys	varchar(4000)	Allowed
tblAction	varchar(25)	Not allowed
Column details
1. id
Physical data type:    int
Allow NULLs:   Not allowed
2. tblName
Physical data type:    varchar(25)
Allow NULLs:   Allowed
3. tblKeys
Physical data type:    varchar(4000)
Allow NULLs:   Allowed
4. tblAction
Physical data type:    varchar(25)
Allow NULLs:   Not allowed

[0249]

WCA_CharSrc
Owner:	dbo
Target DB name:	WCA310_D
Number of columns:	1
Number of indexes:	0
Number of foreign keys:	0
Extended attributes:
OnFileGroup	PRIMARY
Clustered PK	No
Columns	Data type	Allow NULLs	Value/Range
charName	varchar(50)	Not allowed
Foreign keys	Child	Parent
FK_WCA_ProjCharDtl—	WCA_ProjCharDtl.charName	charName
WCA_CharSrc
Column details
1. charName
Physical data type:    varchar(50)
Allow NULLs:   Not allowed

[0250]

WCA_ClassWeight
Owner:	dbo
Target DB name:	WCA310_D
Number of columns:	5
Number of indexes:	0
Number of foreign keys:	0
Extended attributes:
OnFileGroup	PRIMARY
Clustered PK	No
Columns	Data type	Allow NULLs	Value/Range
ID	int	Not allowed
characteristic	varchar(255)	Allowed
alternative	varchar(255)	Allowed
weight	float	Allowed
applPubFormat	varchar(50)	Not allowed
Column details
1. ID
Physical data type:    int
Allow NULLs:   Not allowed
2. characteristic
Physical data type:    varchar(255)
Allow NULLs:   Allowed
3. alternative
Physical data type:    varchar(255)
Allow NULLs:   Allowed
4. weight
Physical data type:    float
Allow NULLs:   Allowed
5.applPubFormat
Physical data type:    varchar(50)
Allow NULLs:   Not allowed

[0251]

WCA_DefinitionSrc
Owner:	dbo
Target DB name:	WCA310_D
Number of columns:	5
Number of indexes:	0
Number of foreign keys:	1
Extended attributes:
OnFileGroup	PRIMARY
TextImageOnGroup	PRIMARY
Clustered PK	No
	Columns	Data type	Allow NULLs	Value/Range
	term	varchar(255)	Not allowed
	definition	text	Allowed
	department (FK)	int	Not allowed
	service (FK)	int	Not allowed
	applPubFormat	varchar(50)	Allowed
Foreign keys	Child	Parent
FK_WCA_DefinitionSrc_WCA_DeptServCode	department	WCA_DeptServCode.department
	service
		WCA_DeptServCode.service
Column details
1. term
Physical data type:    varchar(255)
Allow NULLs:   Not allowed
2. definition
Physical data type:    text
Allow NULLs:   Allowed
3. department (FK)
Physical data type:    int
Allow NULLs:   Not allowed
4. service (FK)
Physical data type:    int
Allow NULLs:   Not allowed
5. applPubFormat
Physical data type:    varchar(50)
Allow NULLs:   Allowed
Foreign key details (child)
FK_WCA_DefinitionSrc_WCA_DeptServCode
Definition:	Child	Parent
department	WCA_DeptServCode.department
service  WCA_DeptServCode.service
Relationship type:	Non-Identifying
Cardinality:	One-to-Zero-or-More
Allow NULLs:	Not allowed
Verb phrase:	hasFK_WCA_DefinitionSrc_WCA_&DeptServCode
Inverse phrase:	is of
Ref. Integrity on update:	No Action
Ref. Integrity on delete:	No Action

[0252]

WCA_DefSecRegSrc
Owner:	dbo
Target DB name:	WCA310_D
Number of columns:	3
Number of indexes:	0
Number of foreign keys:	1
Extended attributes:
OnFileGroup	PRIMARY
Clustered PK	No
Columns	Data type	Allow NULLs	Value/Range
department	int	Not allowed
service	int	Not allowed
regID (FK)	int	Not allowed
Foreign keys	Child	Parent
FK_WCA_DefSecReg_Src_WCA—	regID	WCA_SecRegSrc.regID
SecReg_Src
Column details
1. department
Physical data type:    int
Allow NULLs:   Not allowed
2. service
Physical data type:    int
Allow NULLs:   Not allowed
3. regID (FK)
Physical data type:    int
Allow NULLs:   Not allowed
Foreign key details (child)
FK_WCA_DefSecReg_Src_WCA_SecReg_Src
Definition:	Child	Parent
regID   WCA_SecRegSrc.regID
Relationship type:	Identifying
Cardinality:	One-to-Zero-or-More
Allow NULLs:	Not allowed
Verb phrase:	hasFK_WCA_DefSecReg_Src—
	WCA_SecReg_Src
Inverse phrase:	is of
Ref. Integrity on update:	No Action
Ref. Integrity on delete:	No Action

[0253]

WCA_DeptServCode
Owner:	dbo
Target DB name:	WCA310_D
Number of columns:	4
Number of indexes:	1
Number of foreign keys:	0
Extended attributes:
OnFileGroup	PRIMARY
Clustered PK	No
	Columns	Data type	Allow NULLs	Value/Range
	department	int	Not allowed
	service	int	Not allowed
	departmentName (U1)	varchar(50)	Not allowed
	serviceName (U1)	varchar(50)	Not allowed
	Indexes	Columns	Sort order
	IX_WCA_DeptServCode (U1)	departmentName	Ascending
		serviceName	Ascending
Foreign keys	Child	Parent
FK_WCA_AcronymSrc_WCA_DeptservCode	WCA_AcronymSrc.department	department
		service
	WCA_AcronymSrc.service
FK_WCA_DefinitionSrc_WCA_DeptServCode	WCA_DefinitionSrc.department	department
		service
	WCA_DefinitionSrc.service
FK_WCA_SecRegSrc_WCA_DeptServCode	WCA_SecRegSrc.department	department
		service
	WCA_SecRegSrc.service
Column details
1. department
Physical data type:    int
Allow NULLs:   Not allowed
2. service
Physical data type:    int
Allow NULLs:   Not allowed
3. departmentName (U1)
Physical data type:    varchar(50)
Allow NULLs:   Not allowed
4. serviceName (U1)
Physical data type:    varchar(50)
Allow NULLs:   Not allowed
Index details
IX_WCA_DeptServCode
Column(s):	departmentName (Asc)
serviceName (Asc)
Unique: Yes
Extended attributes:
OnFileGroup	PRIMARY
CLUSTERED No
IGNORE_DUP_KEY	No
FILLFACTOR	90
PAD_INDEX No
DROP_EXISTING	No
STATISTICS_NORECOMPUTE	No

[0254]

WCA_DocParaTTLSrc
Owner:	dbo
Target DB name:	WCA310_D
Number of columns:	6
Number of indexes:	0
Number of foreign keys:	0
Extended attributes:
OnFileGroup	PRIMARY
Clustered PK	No
Columns	Data type	Allow NULLs	Value/Range
title	varchar(60)	Not allowed
paragraph	varchar(50)	Not allowed
document	varchar(50)	Not allowed
applPubFormat	varchar(50)	Not allowed
paragraphLevel	int	Not allowed
paragraphType	varchar(50)	Allowed
Column details
1. title
Physical data type:    varchar(60)
Allow NULLs:   Not allowed
2. paragraph
Physical data type:    varchar(50)
Allow NULLs:   Not allowed
3. document
Physical data type:    varchar(50)
Allow NULLs:   Not allowed
4. applPubFormat
Physical data type:    varchar(50)
Allow NULLs:   Not allowed
5. paragraphLevel
Physical data type:    int
Allow NULLs:   Not allowed
6. paragraphType
Physical data type:    varchar(50)
Allow NULLs:   Allowed

[0255]

WCA_DocTmplSrc
Owner:	dbo
Target DB name:	WCA310_D
Number of columns:	6
Number of indexes:	0
Number of foreign keys:	0
Extended attributes:
OnFileGroup	PRIMARY
TextImageOnGroup	PRIMARY
Clustered PK	No
Columns	Data type	Allow NULLs	Value/Range
instance	int	Not allowed
dtsText	text	Allowed
notes	varchar(50)	Allowed
document	varchar(50)	Not allowed
paragraph	varchar(255)	Not allowed
applPubFormat	varchar(50)	Not allowed
Column details
1. instance
Physical data type:    int
Allow NULLs:   Not allowed
2. dtsText
Physical data type:    text
Allow NULLs:   Allowed
3. notes
Physical data type:    varchar(50)
Allow NULLs:   Allowed
4. document
Physical data type:    varchar(50)
Allow NULLs:   Not allowed
5. paragraph
Physical data type:    varchar(255)
Allow NULLs:   Not allowed
6. applPubFormat
Physical data type:    varchar(50)
Allow NULLs:   Not allowed

[0256]

WCA_HelpExampleSrc
Owner:	dbo
Target DB name:	WCA310_D
Number of columns:	13
Number of indexes:	0
Number of foreign keys:	0
Extended attributes:
OnFileGroup	PRIMARY
TextImageOnGroup	PRIMARY
Clustered PK	Yes
Columns	Data type	Allow NULLs	Value/Range
ID	int	Not allowed
page	varchar(50)	Allowed
applPubFormat	varchar(50)	Not allowed
type	varchar(50)	Allowed
title	varchar(100)	Allowed
helptext	text	Allowed
height	int	Not allowed
width	int	Not allowed
seeAlso	int	Allowed
pageID	varchar(50)	Not allowed
heading	varchar(100)	Not allowed
stgID	decimal(18, 0)	Allowed
paragraph	varchar(50)	Allowed
Column details
1. ID
Physical data type:    int
Allow NULLs:   Not allowed
2. page
Physical data type:    varchar(50)
Allow NULLs:   Allowed
3. applPubFormat
Physical data type:    varchar(50)
Allow NULLs:   Not allowed
4. type
Physical data type:    varchar(50)
Allow NULLs:   Allowed
5. title
Physical data type:    varchar(100)
Allow NULLs:   Allowed
6. helptext
Physical data type:    text
Allow NULLs:   Allowed
7. height
Physical data type:    int
Allow NULLs:   Not allowed
8. width
Physical data type:    int
Allow NULLs:   Not allowed
9. seeAlso
Physical data type:    int
Allow NULLs:   Allowed
10. PageID
Physical data type:    varchar(50)
Allow NULLs:   Not allowed
11. heading
Physical data type:    varchar(100)
Allow NULLs:   Not allowed
12. stgID
Physical data type:    decimal(18, 0)
Allow NULLs:   Allowed
13. paragraph
Physical data type:    varchar(50)
Allow NULLs:   Allowed

[0257]

WCA_HwFamilyLookup
Owner:	dbo
Target DB name:	WCA310_D
Number of columns:	4
Number of indexes:	0
Number of foreign keys:	0
Extended attributes:
OnFileGroup	PRIMARY
Clustered PK	No
Columns	Data type	Allow NULLs	Value/Range
hwFamily	varchar(50)	Not allowed
rank	int	Not allowed
type	char(10)	Not allowed
hwID	decimal(18, 0)	Not allowed
Column details
1. hwFamily
Physical data type:    varchar(50)
Allow NULLs:   Not allowed
2. rank
Physical data type:    int
Allow NULLs:   Not allowed
3. type
Physical data type:    char(10)
Allow NULLs:   Not allowed
4. hwID
Physical data type:    decimal(18, 0)
Allow NULLs:   Not allowed

[0258]

WCA_InfoCategory
Owner:	dbo
Target DB name:	WCA310_D
Number of columns:	5
Number of indexes:	0
Number of foreign keys:	0
Extended attributes:
OnFileGroup	PRIMARY
Clustered PK	No
Columns	Data type	Allow NULLs	Value/Range
infoCatID	int	Not allowed
infoCatName	varchar(60)	Allowed
infoCatValue	varchar(5)	Allowed
rank	int	Allowed
weight	float	Not allowed
Column details
1. infoCatID
Physical data type:    int
Allow NULLs:   Not allowed
2. infoCatName
Physical data type:    varchar(60)
Allow NULLs:   Allowed
3. infoCatValue
Physical data type:    varchar(5)
Allow NULLs:   Allowed
4. rank
Physical data type:    int
Allow NULLs:   Allowed
5. weight
Physical data type:    float
Allow NULLs:   Not allowed

[0259]

WCA_LevelDetermin
Owner:	dbo
Target DB name:	WCA310_D
Number of columns:	6
Number of indexes:	0
Number of foreign keys:	0
Extended attributes:
OnFileGroup	PRIMARY
Clustered PK	No
Columns	Data type	Allow NULLs	Value/Range
ID	int	Not allowed
weightedTotalMin	float	Allowed
weightedTotalMax	float	Allowed
class	int	Allowed
description	varchar(255)	Allowed
applPubFormat	varchar(50)	Not allowed
Column details
1. ID
Physical data type:    int
Allow NULLs:   Not allowed
2. weightedTotalMin
Physical data type:    float
Allow NULLs:   Allowed
3. weightedTotalMax
Physical data type:    float
Allow NULLs:   Allowed
4. class
Physical data type:    int
Allow NULLs:   Allowed
5. description
Physical data type:    varchar(255)
Allow NULLs:   Allowed
6. applPubFormat
Physical data type:    varchar(50)
Allow NULLs:   Not allowed

[0260]

WCA_LookupMgr
Owner:	dbo
Target DB name:	WCA310_D
Number of columns:	8
Number of indexes:	0
Number of foreign keys:	0
Extended attributes:
OnFileGroup	PRIMARY
Clustered PK	No
Columns	Data type	Allow NULLs	Value/Range
webCaLookupsID	decimal(18, 0)	Not allowed
tableName	varchar(50)	Not allowed
columnName	varchar(50)	Not allowed
lkupDescription	varchar(50)	Allowed
wlSize	decimal(18, 0)	Allowed
displayable	char(1)	Allowed
required	char(1)	Allowed
valuesLkTabName	varchar(30)	Allowed
Column details
1. webCaLookupsID
Physical data type:    decimal(18, 0)
Allow NULLs:   Not allowed
2. tableName
Physical data type:    varchar(50)
Allow NULLs:   Not allowed
3. columnName
Physical data type:    varchar(50)
Allow NULLs:   Not allowed
4. lkupDescription
Physical data type:    varchar(50)
Allow NULLs:   Allowed
5. wlSize
Physical data type:    decimal(18, 0)
Allow NULLs:   Allowed
6. displayable
Physical data type:    char(1)
Allow NULLs:   Allowed
7. required
Physical data type:    char(1)
Allow NULLs:   Allowed
8. valuesLkTabName
Physical data type:    varchar(30)
Allow NULLs:   Allowed

[0261]

WCA_MarkerLookup
Owner:	dbo
Target DB name:	WCA310_D
Number of columns:	4
Number of indexes:	0
Number of foreign keys:	0
Extended attributes:
OnFileGroup	PRIMARY
Clustered PK	No
Columns	Data type	Allow NULLs	Value/Range
marker	varchar(50)	Not allowed
sqlStatement	varchar(1000)	Not allowed
retrievalType	varchar(50)	Not allowed
errorMessageText	varchar(255)	Allowed
Column details
1. marker
Physical data type:    varchar(50)
Allow NULLs:   Not allowed
2. sqlStatement
Physical data type:    varchar(1000)
Allow NULLs:   Not allowed
3. retrievalType
Physical data type:    varchar(50)
Allow NULLs:   Not allowed
4. errorMessageText
Physical data type:    varchar(255)
Allow NULLs:   Allowed

[0262]

WCA_MinSeCkListSrc
Owner:	dbo
Target DB name:	WCA310_D
Number of columns:	6
Number of indexes:	0
Number of foreign keys:	0
Extended attributes:
OnFileGroup	PRIMARY
TextImageOnGroup	PRIMARY
Clustered PK	No
Columns	Data type	Allow NULLs	Value/Range
sectionName	varchar(255)	Not allowed
question	varchar(50)	Not allowed
testText	text	Allowed
questionSort	decimal(18, 0)	Allowed
applPubFormat	varchar(50)	Allowed
validQuestion	char(1)	Allowed
Column details
1. sectionName
Physical data type:    varchar(255)
Allow NULLs:   Not allowed
2. question
Physical data type:    varchar(50)
Allow NULLs:   Not allowed
3. testText
Physical data type:    text
Allow NULLs:   Allowed
4. questionSort
Physical data type:    decimal(18, 0)
Allow NULLs:   Allowed
5. applPubFormat
Physical data type:    varchar(50)
Allow NULLs:   Allowed
6. validQuestion
Physical data type:    char(1)
Allow NULLs:   Allowed

[0263]

WCA_MLSecClass
Owner:	dbo
Target DB name:	WCA310_D
Number of columns:	6
Number of indexes:	0
Number of foreign keys:	0
Extended attributes:
OnFileGroup	PRIMARY
Clustered PK	No
Columns	Data type	Allow NULLs	Value/Range
ID	int	Allowed
maxDateClass	varchar(255)	Allowed
minUserClear	varchar(255)	Allowed
case1	varchar(255)	Allowed
case2	varchar(255)	Allowed
case3	varchar(255)	Allowed
Column details
1. ID
Physical data type:    int
Allow NULLs:   Allowed
2. maxDateClass
Physical data type:    varchar(255)
Allow NULLs:   Allowed
3. minUserClear
Physical data type:    varchar(255)
Allow NULLs:   Allowed
4. case1
Physical data type:    varchar(255)
Allow NULLs:   Allowed
5. case2
Physical data type:    varchar(255)
Allow NULLs:   Allowed
6. case3
Physical data type:    varchar(255)
Allow NULLs:   Allowed

[0264]

WCA_Organization
Owner:	dbo
Target DB name:	WCA310_D
Number of columns:	3
Number of indexes:	0
Number of foreign keys:	0
Extended attributes:
OnFileGroup	PRIMARY
Clustered PK	No
	Columns	Data type	Allow NULLs	Value/Range
	orgID	decimal(18, 0)	Not allowed
	orgName	varchar(50)	Not allowed
	orgDescription	varchar(255)	Not allowed
Foreign keys	Child	Parent
FK_RCT_ActorDefn_WCA_Organization	RCT_OrgActorDefn.orgID	orgID
FK_RCT_TitleDefn_WCA_Organization	RCT_OrgTitleDefn.orgID	orgID
FK_WCA_OrgUser_WCA_Organization	WCA_OrgUser.orgID	orgID
FK_WCA_Project WCA_Organization	WCA_Project.orgID	orgID
FK_WPM_OrgEventRules_WCA_Organization	WPM_OrgEventRules.orgID	orgID
FK_WPM_OrgPrereq_WCA_Organization	WPM_OrgPrereq.orgID	orgID
FK_WPM_OrgPS_WCA_Organization	WPM_OrgPS.orgID	orgID
FK_WPM_OrgWBS_WCA_Organization	WPM_OrgWBS.orgID	orgID
FK_WPM_OrgWP_WCA_Organization	WPM_OrgWP.orgID	orgID
Column details
1. orgID
Physical data type:    decimal(18, 0)
Allow NULLs:   Not allowed
2. orgName
Physical data type:    varchar(50)
Allow NULLs:   Not allowed
3. orgDescription
Physical data type:    varchar(255)
Allow NULLs:   Not allowed

[0265]

WCA_OrgUser
Owner:	dbo
Target DB name:	WCA310_D
Number of columns:	2
Number of indexes:	1
Number of foreign keys:	1
Extended attributes:
OnFileGroup	PRIMARY
Clustered PK	No
Columns	Data type	Allow NULLs	Value/Range
orgID (FK, I1)	decimal(18, 0)	Not allowed
userID	int	Not allowed
	Indexes	Columns	Sort order
	IX_WCA_OrgUser (I1)	orgID	Ascending
Foreign keys	Child	Parent
FK_WCA_OrgUser_WCA_	orgID	WCA_Organization.orgID
Organization
Column details
1. orgID (FK, I1)
Physical data type:    decimal(18, 0)
Allow NULLs:   Not allowed
2. userID
Physical data type:    int
Allow NULLs:   Not allowed
Index details
IX_WCA_OrgUser
Column(s):	orgID (Asc)
Unique: No
Extended attributes:
OnFileGroup	PRIMARY
CLUSTERED	No
IGNORE_DUP_KEY	No
FILLFACTOR	90
PAD_INDEX	No
DROP_EXISTING	No
STATISTICS_NORECOMPUTE	No
Foreign key details (child)
FK_WCA_OrgUser_WCA_Organization
Definition:	Child	Parent
orgID	WCA_Organization.orgID
Relationship type:	Non-Identifying
Cardinality:	One-to-Zero-or-More
Allow NULLs:	Not allowed
Verb phrase:	hasFK_WCA_OrgUser_WCA_Organization
Inverse phrase:	is of
Ref. Integrity on update:	No Action
Ref. Integrity on delete:	No Action

[0266]

WCA_OsFamilyLookup
Owner:	dbo
Target DB name:	WCA310_D
Number of columns:	4
Number of indexes:	0
Number of foreign keys:	0
Extended attributes:
OnFileGroup	PRIMARY
Clustered PK	No
Columns	Data type	Allow NULLs	Value/Range
osFamily	varchar(50)	Not allowed
rank	int	Not allowed
type	char(10)	Not allowed
osID	decimal(18, 0)	Not allowed
Column details
1. osFamily
Physical data type:    varchar(50)
Allow NULLs:   Not allowed
2. rank
Physical data type:    int
Allow NULLs:   Not allowed
3. type
Physical data type:    char(10)
Allow NULLs:   Not allowed
4.osID
Physical data type:    decimal(18, 0)
Allow NULLs:   Not allowed

[0267]

WCA_OSSource
Owner:	dbo
Target DB name:	WCA310_D
Number of columns:	7
Number of indexes:	0
Number of foreign keys:	0
Extended attributes:
OnFileGroup	PRIMARY
Clustered PK	No
Columns	Data type	Allow NULLs	Value/Range
osReference	varchar(50)	Not allowed
osFamily	varchar(20)	Allowed
osMfr	varchar(50)	Allowed
osName	varchar(50)	Allowed
osVersion	varchar(50)	Allowed
osPatchLevel	varchar(50)	Allowed
Type	char(1)	Allowed
Column details
1. osReference
Physical data type:    varchar(50)
Allow NULLs:   Not allowed
2. osFamily
Physical data type:    varchar(20)
Allow NULLs:   Allowed
3. osMfr
Physical data type:    varchar(50)
Allow NULLs:   Allowed
4. osName
Physical data type:    varchar(50)
Allow NULLs:   Allowed
5. osVersion
Physical data type:    varchar(50)
Allow NULLs:   Allowed
6. osPatchLevel
Physical data type:    varchar(50)
Allow NULLs:   Allowed
7. Type
Physical data type:    char(1)
Allow NULLs:   Allowed

[0268]

WCA_PageAttrs
Owner:	dbo
Target DR name:	WCA310_D
Number of columns:	6
Number of indexes:	0
Number of foreign keys:	0
Extended attributes:
OnFileGroup	PRIMARY
Clustered PK	Yes
Columns	Data type	Allow NULLs	Value/Range
pageID	varchar(50)	Not allowed
stgID	decimal(18, 0)	Not allowed
appPageTitle	varchar(50)	Not allowed
appPageHeading	varchar(50)	Allowed
processStep	varchar(50)	Not allowed
servlet	varchar(255)	Not allowed
Foreign keys	Child	Parent
FK_WPM_ProjPS_WCA_PageAttrs	WPM_ProjPS.pageID	pageID
FK_WPM_PSSrc_WCA_PageAttrs	WPM_PSSrc.pageID	pageID
Column details
1. pageID
Physical data type:    varchar(50)
Allow NULLs:   Not allowed
2. stgID
Physical data type:    decimal(18, 0)
Allow NULLs:   Not allowed
3. appPageTitle
Physical data type:    varchar(50)
Allow NULLs:   Not allowed
4. appPageHeading
Physical data type:    varchar(50)
Allow NULLs:   Allowed
5. processStep
Physical data type:    varchar(50)
Allow NULLs:   Not allowed
6. servlet
Physical data type:    varchar(255)
Allow NULLs:   Not allowed

[0269]

WCA_ProjAcBoundary
Owner:	dbo
Target DB name:	WCA31O_D
Number of columns:	4
Number of indexes:	0
Number of foreign keys:	1
Extended attributes:
OnFileGroup	PRIMARY
TextImageOnGroup	PRIMARY
Clustered PK	No
Columns	Data type	Allow NULLs	Value/Range
PID (EK)	decimal(18, 0)	Not allowed
pabName	varchar(50)	Not allowed
pabDescription	text	Not allowed
adID	decimal(18, 0)	Not allowed
	Foreign keys	Child	Parent
	FK_WCA_ProjAcBound	PID	WCA_Project.PID
Column details
1. PID (FK)
Physical data type:    decimal(18, 0)
Allow NULLs:   Not allowed
2. pabName
Physical data type:    varchar(50)
Allow NULLs:   Not allowed
3. pabDescription
Physical data type:    text
Allow NULLs:   Not allowed
4. adID
Physical data type:    decimal(18, 0)
Allow NULLs:   Not allowed
Foreign key details (child)
FK_WCA_ProjAcBound
Definition:	Child	Parent
PID	WCA_Project.PID
Relationship type:	Non-Identifying
Cardinality:	One-to-Zero-or-More
Allow NULLs:	Not allowed
Verb phrase:	hasFK_WCA_ProjAcBound
Inverse phrase:	is of
Ref. Integrity on update:	No Action
Ref. Integrity on delete:	No Action

[0270]

WCA_ProjAcronym
Owner:	dbo
Target DB name:	WCA310_D
Number of columns:	4
Number of indexes:	0
Number of foreign keys:	1
Extended attributes:
OnFileGroup	PRIMARY
TextImageOnGroup	PRIMARY
Clustered PK	No
Columns	Data type	Allow NULLs	Value/Range
ID	int	Not allowed
PID (FK)	decimal(18, 0)	Not allowed
acronym	varchar(50)	Allowed
description	text	Allowed
	Foreign keys	Child	Parent
	FK_WCA_ProjAcronym	PID	WCA_Project.PID
Column details
1. ID
Physical data type:    int
Allow NULLs:   Not allowed
2. PID (FK)
Physical data type:    decimal(18, 0)
Allow NULLs:   Not allowed
3. acronym
Physical data type:    varchar(50)
Allow NULLs:   Allowed
4. description
Physical data type:    text
Allow NULLs:   Allowed
Foreign key details (child)
FK_WCA_ProjAcronym
Definition:	Child	Parent
PID   WCA_Project.PID
Relationship type:	Non-Identifying
Cardinality:	One-to-Zero-or-More
Allow NULLs:	Not allowed
Verb phrase:	hasFK_WCA_ProjAcronym
Inverse phrase:	is of
Ref. Integrity on update:	No Action
Ref. Integrity on delete:	No Action

[0271]

WCA_ProjAppdxFile
Owner:	dbo
Target DB name:	WCA310_D
Number of columns:	11
Number of indexes:	0
Number of foreign keys:	1
Extended attributes:
OnFileGroup	PRIMARY
Clustered PK	No
Columns	Data type	Allow NULLs	Value/Range
ID	decimal(18, 0)	Not allowed
PID (FK)	decimal(18, 0)	Not allowed
letter	varchar(50)	Not allowed
title	varchar(255)	Allowed
shortTitle	varchar(255)	Allowed
author	varchar(255)	Allowed
afDate	varchar(255)	Allowed
version	varchar(50)	Allowed
url	varchar(255)	Allowed
appendixCFlag	char(10)	Allowed
fileID	decimal(l8, 0)	Not allowed
	Foreign keys	Child	Parent
	FK_WCA_ProjAppdxFiile	PID	WCA_Project.PID
Column details
1. ID
Physical data type:    decimal(18, 0)
Allow NULLs:   Not allowed
2. PID (FK)
Physical data type:    decimal(18, 0)
Allow NULLs:   Not allowed
3. letter
Physical data type:    varchar(50)
Allow NULLs:   Not allowed
4. title
Physical data type:    varchar(255)
Allow NULLs:   Allowed
5. shortTitle
Physical data type:    varchar(255)
Allow NULLs:   Allowed
6. author
Physical data type:    varchar(255)
Allow NULLs:   Allowed
7. afDate
Physical data type:    varchar(255)
Allow NULLs:   Allowed
8. version
Physical data type:    varchar(50)
Allow NULLs:   Allowed
9. url
Physical data type:    varchar(255)
Allow NULLs:   Allowed
10. appendixCFlag
Physical data type:    char(10)
Allow NULLs:   Allowed
11. fileID
Physical data type:    decimal(18, 0)
Allow NULLs:   Not allowed
Foreign key details (child)
FK_WCA_ProjAppdxFile
Definition:	Child	Parent
PID   WCA_Project.PID
Relationship type:	Non-Identifying
Cardinality:	One-to-Zero-or-More
Allow NULLs:	Not allowed
Verb phrase:	hasFK_WCA_ProjAppdxFile
Inverse phrase:	is of
Ref. Integrity on update:	No Action
Ref. Integrity on delete:	No Action

[0272]

WCA_ProjCharDtl
Owner:	dbo
Target DB name:	WCA310_D
Number of columns:	4
Number of indexes:	0
Number of foreign keys:	2
Extended attributes:
OnFileGroup	PRIMARY
Clustered PK	No
Columns	Data type	Allow NULLs	Value/Range
PID (FK)	decimal(18, 0)	Not allowed
charName (FK)	varchar(50)	Not allowed
stringValue	varchar(50)	Not allowed
weight	float	Allowed
Foreign keys	Child	Parent
FK_WCA_ProjCharDtl—	charName	WCA_CharSrc.charName
WCA_CharSrc
FK_WCA_ProjCharDtl—	PID	WCA_Project.PID
WCA_Project
Column details
1. PID (FK)
Physical data type:    decimal(18, 0)
Allow NULLs:   Not allowed
2. charName (FK)
Physical data type:    varchar(50)
Allow NULLs:   Not allowed
3. stringValue
Physical data type:    varchar(50)
Allow NULLs:   Not allowed
4. weight
Physical data type:    float
Allow NULLs:   Allowed
Foreign key details (child)
FK_WCA_ProjCharDtl_WCA_CharSrc
Definition:	Child	Parent
charName	WCA_CharSrc.charName
Relationship type:	Identifying
Cardinality:	One-to-Zero-or-More
Allow NULLs:	Not allowed
Verb phrase:	hasFK_WCA_ProjCharDtl_WCA_CharSrc
Inverse phrase:	is of
Ref. Integrity on update:	No Action
Ref. Integrity on delete:	No Action
FK_WCA_ProjCharDtl_WCA_Proiect
Definition:	Child	Parent
PID   WCA_Project.PID
Relationship type:	Identifying
Cardinality:	One-to-Zero-or-More
Allow NULLs:	Not allowed
Verb phrase:	hasFK_WCA_ProjCharDtl_WCA_Project
Inverse phrase:	is of
Ref. Integrity on update:	No Action
Ref. Integrity on delete:	No Action