NIEM 200 - NIEM Project ManagementThis course provides managers and architects with the information necessary to create and manage projects that involve the National Information Exchange Model (NIEM). This course will discuss Information Exchange Package Documentation (IEPD) development in the context of managing a NIEM-based information exchange from requirements gathering to implementation. Managers and architects will be shown best practices for rating the complexity of an IEPD, creating an IEPD project plan, as well as best practices in managing resources and gate reviews on these projects. Also, this course covers techniques for increasing NIEM adoption and best practices for implementing NIEM-conformant information exchanges across organizations. Prerequisites: It is requested that course participants take the NIEM Executive Seminar (NIEM 100) and have project management experience, training, or certifications (PMP, etc.) prior to enrolling in this course. b8f03bca-0134-47ed-a0d7-4a51e122f757Course ParticipantsNIEM AdoptionIdentify NIEM adoption techniques that can be used in the participant’s organization PerformerBeneficiaryIEPD Lifecycle DifferentiationDifferentiate the phases of the IEPD lifecycle and its place in information exchange developmentPerformerBeneficiaryNIEM Project ManagementApply NIEM to project management conceptsPerformerBeneficiaryIEPD Deliverables and Risk IdentificationIdentify IEPD deliverables and the risks associated with each deliverablePerformerBeneficiaryProject ManagersProject LeadershipNeed to lead the project from conception to implementationProgram ManagersTarget AudienceBeneficiaryArchitectsIEPD DesignerNeed to design a NIEM-conformant information exchange according to IEPD specifications and put the foundation in place for developmentBeneficiaryPerformerImplementersTechnical Artifact DevelopmentNeed to transform the design specifications for an information exchange into technical artifactsBeneficiaryPerformer563bb1cb-21c2-4ceb-bd75-66fa715810e2This course will enable program and project managers to successfully coordinate information sharing projects using NIEM.37d49f63-d6a3-4ce0-8bc8-b139b592b041Scenario PlanningPlan the project, establish the process, and identify information exchange business requirements. 1d4559a5-d31f-4a90-b19e-b17e48a28b061Purpose: Complete the initial tasks associated with defining an information exchange and understanding the business requirements for the exchange. Key Considerations: * Deliverables in the "€œScenario Planning"€ phase will drive the business goals of the exchange and will have a large impact on the technical deliverables * Prior documentation can be used to support the development phase * Use cases should be checked by technical or non-technical stakeholders on each side of the exchange * Sequence diagrams should be checked by multiple technical stakeholders on each side of the exchange Project Manager Meeting FacilitationFacilitate working group meetings between exchange partners, developers, and architects PerformerDeliverable ReviewReview IEPD deliverables for scope, detail, and accuracy PerformerWork PlanningIf necessary, establish granular work plans for more complicated IEPD deliverablesPerformerBusiness ProcessesTextual or graphical representation of the activities involved in an exchange, similar to a workflow 07c4e2c3-643c-4d95-a32c-84ca84352e1d1.1de12c8a4-2f5a-4a34-a040-1365e6600312To be determinedTo be reportedUse CasesA graphical representation of the functionality of a particular information exchange as perceived through an external observeraaad414e-7c7f-4a92-8676-bf27b4ea55951.2de12c8a4-2f5a-4a34-a040-1365e6600312To be determinedTo be reportedSequence DiagramsA graphical representation of the messages sent sequentially within an information exchange 7d2d3b4e-baf5-4b0e-8949-4d923d91c9b31.3de12c8a4-2f5a-4a34-a040-1365e6600312To be determinedTo be reportedRequirements AnalysisAnalyze requirements4b953fb9-d932-4abd-b49e-76ae8b31bc122Selected information exchange is further elaborated to understand and document the business context and data requirements. Purpose: Information exchanges are researched and analyzed further to understand and document the business context and data requirements Project ManagerGuideline EstablishmentEstablish guidelines for business rules and requirements that align to organizational and NIEM standards PerformerRequirements ReviewReview requirements upon completion and continuously revisit throughout the entire development process PerformerInterviewing & Consensus BuildingIf necessary, schedule interviews and consensus meetings to gather requirements from stakeholdersBusiness RulesA specific qualification for data that refers to how it should be structured (field lengths, data constraints, etc.) 92e8ffa8-3d9f-489c-8743-850792e06e982.1de12c8a4-2f5a-4a34-a040-1365e6600312To be determinedTo be reportedBusiness RequirementsA business driver for an information exchange that is primarily an operational or functional requirement18bdac73-f944-4a20-9aac-f221ba589ee92.2Key Considerations: * Stakeholders on both sides of the exchange should be involved in as many activities as possible * As with all requirement gathering efforts, this process is iterative and most likely will be visited again * Reaching agreement on IEPD business rules and requirements can be difficult with more sharing partners * S.M.A.R.T. is a proven method for gathering and analyzing requirements (Specific, Measurable, Agreed-upon, Realistic, Time-bound) de12c8a4-2f5a-4a34-a040-1365e6600312To be determinedTo be reportedMap & ModelAssociate local objects with types and elements in NIEM. 0abb733d-0d7b-40b6-b0eb-65912354bed83This process is called mapping a domain model to NIEM. Purpose: Create an exchange content model; associate local data objects with types and elements in NIEM Key Considerations: * Reusing NIEM elements increases consistency and promotes reuse * Each data object should be mapped to an element or type in NIEM, if possible; Do not force the mapping if it does not make sense * Implementers will create "extensions" to the NIEM data model for elements that do not directly map to NIEM data objects There are a number of tools currently available and being developed that support various stages of IEPD development. NIEM.gov Tools: Capability includes searching the NIEM data model, artifact generation, mapping to NIEM, and more. Available through NIEM.gov. NIEM Wayfarer: Capability includes advanced searching of the NIEM data model. Publically available online.* XML Software: Standard XML editing software can greatly aid the development of NIEM schemas. Free, open source XML software is available in addition to software distributed by vendors. Project ManagerExpectation EstablishmentEstablish expectations for exchange content model development, including how business requirements and rules are reflected in the model PerformerCommunicationCommunicate with architects to discover how closely business needs map to the NIEM data modelPerformerCoordinationCoordinate review of the exchange content model and mapping document with multiple technical stakeholdersPerformerExchange Content ModelGraphical representation of the data and relationships involved in the information exchange bda2560b-8278-4035-bf2a-800765422ec03.1Exchange content models consist of objects, their related elements, and the associations between those objectsde12c8a4-2f5a-4a34-a040-1365e6600312To be determinedTo be reportedMapping DocumentA standardized spreadsheet used to document how exchange data maps to equivalent NIEM data objectsecb496a4-c048-463c-bff4-d5430f26170e3.2de12c8a4-2f5a-4a34-a040-1365e6600312To be determinedTo be reportedBuild & ValidateCreate a set of exchange-specific NIEM conformant XML schemas that implement the data model created for the exchange.999a421b-93b3-49bf-bda4-fa2525ec9f0a4Purpose: Create a set of exchange-specific NIEM conformant XML schemas based upon the mapping values; these schemas will implement the data model created for the exchange Key Considerations: *Schema development inherently poses a schedule risk associated with the possibility of unforeseen problems in development  * Risks are often known by technical team members and constant communication with these team members will help expose these risks * Consistent communication during schema development (with stakeholders) is important * Short timeframe between milestones in the project plan prevents procrastination and project slips Project ManagerRisk CommunicationCommunicate with implementers about risks to the project plan associated with schema developmentPerformerProgress ReportingCommunicate project progress and risk frequentlyPerformerXML Document ReviewEstablish a review of NIEM XML documents by an external technical stakeholderPerformerXML SchemasA type of XML document used to structure and constrain the data of an information exchange (e.g. exchange, subset, extension, and constraint schemas) afc7534f-c097-43b7-9778-2bbfd6c7586c4.1de12c8a4-2f5a-4a34-a040-1365e6600312To be determinedTo be reportedXML Wantlist5d84cd0f-b959-4b13-814f-672179a4a4b54.2Other XML Documents: Additional XML artifacts are included within an IEPD (Wantlist, XML Instance, and Stylesheet)de12c8a4-2f5a-4a34-a040-1365e6600312To be determinedTo be reportedAssemble & DocumentPrepare and package all required files for this IEPD into a single self-contained, self-documented, portable archive file.6e52651c-ef3c-45f3-b280-573e7184a9b45Purpose: Complete IEPD documentation and package all required artifacts for this IEPD into a single self-contained, self-documented, portable archive file Key Considerations: * IEPD Master Document should accurately reflect the business needs of the exchange * Review the IEPD package as well as the individual artifacts for conformance to NIEM standards * Multiple technical reviewers, or one very experienced reviewer, of an IEPD will help to identify issues of non-conformance within an IEPD Project ManagerResource AssignmentAssign technical and non-technical resources to IEPD Master Document and package creationPerformerReview ManagementManage internal review and if possible, external review of the IEPDPerformerMaster Document ReviewReview the IEPD Master Document for accuracyPerformerIEPD ReviewFinal review of entire IEPD PackagePerformerIEPD Master DocumentA document that captures a detailed description of a specific IEPD and its artifacts, including business and technical context 176f3bb6-a2d7-4a94-9486-502e6d2ec8ea5.1de12c8a4-2f5a-4a34-a040-1365e6600312To be determinedTo be reportedIEPD Catalog & IEPD Metadata2e533682-e185-4ddd-af57-4542e6003cf55.2IEPD Package: Collection of IEPD artifacts organized with standard naming conventions and file structure into a ZIP file IEPD Metadata: Information that describes characteristics of an IEPD such as the author and organizationde12c8a4-2f5a-4a34-a040-1365e6600312To be determinedTo be reportedSample XML Instancesf97c1d6f-bb6d-4524-b501-de1eee48199b5.3de12c8a4-2f5a-4a34-a040-1365e6600312To be determinedTo be reportedXML Stylesheetsd7bba47c-e201-42c6-a3cf-bb795b0e42805.4de12c8a4-2f5a-4a34-a040-1365e6600312To be determinedTo be reportedPublish & ImplementPublish IEPD for search, discovery, and reuse3ece2a8e-be66-4366-be33-1cf2b7ec958a6No required artifacts. Publish the IEPD to a repository and implement the exchange. Purpose: Publish the completed IEPD to an online repository and then implement the information exchange in the production environment Additional Insight: Publish: IEPD implementers have the option to publish their IEPDs to their own repository, to a national repository, such as the IEPD Clearinghouse, or they can register and publish them through NIEM.gov  Implement: NIEM intentionally does not provide implementation specifications in order to maintain interoperability. Therefore, architects have MANY different options to publish and implement an IEPD and these decisions will largely be decided upon by available resources and organizational constraints. Key Considerations: * The IEPD review process might be iterative and could concurrently be completed with implementation * Multiple IEPD publication repositories exist; project managers should decide on publication locations that maximize IEPD reuse * Implementation of an information exchange is outside the scope of NIEM and will require additional software development along with necessary hardware Project ManagerManage the IEPD Review Process and requested IEPD changes Decide on IEPD publication location(s) Manage the implementation of the exchange 7b0a5e62-d37a-443b-b7e8-f7fcff4df8fdde12c8a4-2f5a-4a34-a040-1365e6600312To be determinedTo be reportedClose OutClosing out a project is an important step to move forward with sustainment activities and recognizing the completion of the necessary deliverables. 16d78b7f-5916-4fef-9b09-4e27b538f4b07Project ManagerUpon closing out the project, project managers should: VerificationVerify that project objectives were met and deliverables have been completedPerformerAcceptanceAcquire formal acceptance/approval of deliverables from leadershipPerformerDocumentationDocument final lessons learned from the project and NIEMPerformerResource ReleaseRelease project resourcesPerformerdd6f31d0-7cad-4136-ad1d-e0c54fc3df11de12c8a4-2f5a-4a34-a040-1365e6600312To be determinedTo be reportedMaintenanceAfter the project is officially complete, the information exchange and IEPD need to be maintained throughout their existence.960f342d-accd-4363-aced-58404940c1838Choosing to NOT maintain the IEPD results in poor documentation and limited reuse within and outside the organization UpdatesUpdate changes made to the information exchange in the IEPD and update the new version of the IEPD within online repositoriesa3b71f8d-6e83-487e-b0fe-bdba32c7b3ae8.1de12c8a4-2f5a-4a34-a040-1365e6600312To be determinedTo be reportedTechnical ArchitectureOver time, the technical architecture of the information exchange is likely to change; update the IEPD to reflect these changesa757c058-8cd3-46fe-a862-41eb741751468.2de12c8a4-2f5a-4a34-a040-1365e6600312To be determinedTo be reportedGovernanceA governance process should be established to actively manage the changes made to the information exchange and IEPDd8b0ce91-7b4a-44f7-a1ec-4c40bc6b6ea78.3de12c8a4-2f5a-4a34-a040-1365e6600312To be determinedTo be reported2011-10-29http://xml.fido.gov/stratml/cusson/NIEM200wStyle.xmlOwenAmburOwen.Ambur@verizon.net