Start with some sights of what (where) are the goals of the modularization? The concern is to avoid re-work of Ship APs in the future before they have become IS. Modularization, presently, requires that after 2003 release 3 will become mandatory, which can pose a threat for the development and publication of the Ship APs.
Participation on the modularization development may be necessary to pass to the group the experiences and requirements of the Ship Team. Should we rise the problem as necessary for active participation (Building block approach is one of the modularization proposals). The case of modularization will be put in the issues log and a description to ensure and see if it can be guaranteed that T23 is represented in there.
Generally speaking the modularization approach is thought as a way to simplify the work to produce an AP. Different modules can be developed separately and the AP would be built from those modules. The problem is that the criteria, requirements and methods for the modularization approach are not fixed, which can bring difficulties for ongoing projects. There are several documents that explain how the modularization approach works and is for, refer to Resolution E of San Francisco meeting.
3.2 Quality plan for APs (by Pete Lazo and Jesse Crussey)
QCチェックリストが出来上がり、web上で閲覧できるようになった。AP215/216/217/218は2000年3月で登録抹消となるため、Shipチーム内で分担して文書のチェックを行うこととした。エディターはAP文書の完成を早め、reviewerに原稿を送り、reviewerはチェックリストに従いチェックを実施する。New Orleansにて完成文書とする予定。
SC4 View
Enterprise information available in digital form, when and where it is required
・Without ambiguity or loss of completeness.
・Within and between enterprises.
・Throughout the lifecycle.
How? Deliver a consistent and coherent set of standards.
Why? For the purpose of capturing, storing, exchanging, sharing, and archiving in the neutral form.
Discussions of quality plan for the APs were developed.
Check lists have been created that creates a consistent process in 10303. Signing off from the convener. New documents to be concerned at are QCN108, QCN109, QCN110, SC4 N915, QCN111, QCN112.
・QCN 108 is for convener,
・QCN 109 project leader
・QCN 110 internal review document for development team.
・QCN 111 identifies changes that will be in the SC4 handbook.
・QCN 112 is a manual with the various steps you go through in the process.
・The checklists are on the web
It is now a requirement that we will have an interpretation report that accompanies the validation report. It will explain why a particular path was chosen when there were other choices. Checklist for the convener has to contain the symmetry data, validation report, and validation of scope, ARM and AIM. Interpretation report that has to define the rationale specific, how the AP is going to be tested, etc.
