Read the summary and the most important questions on PDDs and modeling patterns

• 2 Documenting PDDs

  This is a preview. There are 2 more flashcards available for chapter 2
  Show more cards here

• What has to be present for a PDD?

  For a PDD an activity table and concept table have to be present.

• How many activity and concept table are used in case for one study multiple PDDs are produced?

  In case for one study multiple PDDs are produced, then all are documented in one activity table and one concept table.

• Where are additional rules or unclarities documented?

  Additional rules or unclarities are documented in an additional statement.

• 2.1 Activity table

  This is a preview. There are 1 more flashcards available for chapter 2.1
  Show more cards here

• How are the descriptions composed?

  The descriptions are short but comprehensive.

• 2.2 Concept table

  This is a preview. There are 1 more flashcards available for chapter 2.2
  Show more cards here

• What is also included in the concept table?

  - In the concept table references are included
  - cross-references can be made. 

• 3 Meta-modeling Patterns

• 3.1 Version-dependent data

  This is a preview. There are 1 more flashcards available for chapter 3.1
  Show more cards here

• What is an important fact to consider in meta-data modeling about product versions?

  Products have different versions that vary over time, so the meta-data model should accommodate that in case it is essential.

• What are examples of version-dependent data?

  - Different versions of a Release Definition, Functional Design;
  - Tracing and tracking of requirements in the release history.

• 4 Method Fragments

  This is a preview. There are 2 more flashcards available for chapter 4
  Show more cards here

• What is the definition of method fragments?

  A method fragment is any coherent building block of a method, technique or tool.

• What are examples of method fragments?

  Process perspective:
  - Phase: Feasibility, Deployment, Beta Test;
  - Activity: Create Data model, Verify Release plan.
  
  Product perspective:
  - Deliverable: Functional Design, Test plan;
  - Technique: Use Cases, State diagram;
  - Concept: Entity, Class, Action, Test.

• 4.1 Method evolution

  This is a preview. There are 1 more flashcards available for chapter 4.1
  Show more cards here

• How to adapt the process to suit your circumstance?

  This can be done by making use of Method evolution.