Process Asset Templates are a natural evolution of guidance in SWEs and Topics. They typically start out as checklists, process step lists, document content structures, or other content and evolve into templates that can be used in project activities or as prototypes to be modified, tailored, and improved before being used in a project. Process Asset Templates is a general category of pages. Any page that is not a SWE, topic, or the Introduction page is eligible for inclusion here. These pages include: A PAT will be numbered so that existing code in templates and macros for references and tools can be reused. The PAT number series will be included in the first 7 characters of the page title. The PATs are being developed in two spaces on the SWEHB site: SITE, and SWEHBVD The description below explains how the first two PATs were implemented. The output of this implementation is: This describes all of the initial setup. see Maintenance for details of ongoing maintenance, adding PATs, etc. Each PAT needs to have a simple structure that can be used by project teams. To ensure this reusability aspect, Assets will be created and saved as Word, Excel, or other editable format, not as a PDF. Each should have a simple minimalist structure for the user to embellish as they see fit. See section 3.1 Configuring an Asset as a PAT below for the full details on standardization. The creation of new user macros requires using HTML instead of Wiki Markup. Since most of the legacy macros are in Wiki Markup, new macros cannot be created easily. They must be created in HTML. This creates a future problem. Eventually, Wiki Markup macros will not work and everything will need to be rewritten in HTML. Workaround: Build a report that uses a manual method for selecting content. This is working effectively for pages under Topic 7.18. It needs to be implemented for all pages under 7.18 and 8.16. Strategy: I will investigate a method for converting Wiki Markup macros to HTML. There are some promising ways of doing this on the internet. Confluence is supposed to support attachments from pages in one space being referenced in another space. This has proven to be difficult to do as documented by Atlassian. Workaround: Every asset that becomes a Process Asset Template in SWEHB gets it's own page in the SITE space. From this location, the PAT can be: Each Process Asset Template goes through a life cycle where it is created, implemented in a SWEHB page, updated, and finally retired or replaced. Expand the items below as needed to complete items in the PAT flow.
See edit history of this section
Post feedback on this section
1.Design and Development
1.1 Definition of Process Asset Templates
1.2 Layout of PATs
In SITE space
In SWEHBVD space
2. Initial Implementation
2.1 Initial Structure
2.2 First asset in SWE-084
2.3 Asset Standardization
2.4 Challenges and Workarounds
2.4.1 Creation of report macros for Resource tabs
2.4.2 Including a PAT in pages outside of SITE space
3. PAT Maintenance
3.1 Assets in a PAT
3.2 PAT Life cycle
3.2 Building / Updating PAT Pages
4.
Process Asset Templates
Web Resources
View this section on the websiteUnknown macro: {page-info}