My last post showed my initial implementation of the DODAF in the PowerDesigner framework. This post will look at how i collected in the information within the process to create the OV3 matrix report.
There were three steps to collect the content. The first was generating the OV2 model as the starting the point. Once this model is created with some of the operational nodes defined, there is an opportunity to add a meta model extension to collect additional information that can be leveraged to automatically generate the OV3 report. Here is the metadata extension that I started for OV2.
This extension process was covered in a previous post here, so to do this, look in the archive. As for the report, PowerDesigner creates list reports through the use of a wizard, so if all the information you need has been collected, spitting it out is a basic task. here is the final report that i generated in HTML format, for review online by our COTR.
Hope this helps, until next time.
2 comments:
Hi,
I'm playing PD 15 now, your DoDAF in PD is very interesting.
But I wonder that PD can "fully support" DoDAF? or support DoDAF matrix only?
I know we can use EA and SA (both are products) to draw DoDAF, but I can not find anything from PD project to support DoDAF.
So, PD must creaet DoDAF project template by myself, right?
yes, that is right. after you create the project, then the matrix, all the model artifacts are in the product, but the meta data for those products are not, so you need to extend the metamodel as well to include design attributes like InformationElement or Object:Service to be DODAF compliant.
Post a Comment