Changes between Version 72 and Version 73 of ExDescLang
- Timestamp:
- Nov 8, 2010 9:32:59 AM (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ExDescLang
v72 v73 44 44 = Domain Knowledge = 45 45 46 The entire system has a domain knowledge databasethat contains domain-specific information, such as:46 The entire system has a domain library that contains domain-specific information, such as: 47 47 * Context: This will probably be expressed in a mix of [CurrentlyProposedLanguage] and regular expressions 48 48 * what is an IP address … … 56 56 * for each type of object and each type of event in any metadescription what kind of parameters can be defined. E.g., for HTTP request this would be timing of requests and content of requests (type=GET/PUT/POST, filename). Note that this is divorced from the actual generator of such event, parameters are strictly related to events, regardless of how they are generated. 57 57 58 The context part would be mostly populated by us. The parameterization and relationship parts would be seeded by us but then extended by other experts that create meta-descriptions. There is an automated way of identifying unknowns from a meta-description that must be defined in the knowledge DB.58 The context part would be mostly populated by us. The parameterization and relationship parts would be seeded by us but then extended by other experts that create meta-descriptions. There is an automated way of identifying unknowns from a meta-description that must be defined in the domain library. 59 59 60 60 = Generator Library = … … 65 65 * URL of the manual for the generator 66 66 * What is the type of its output (e.g. Topology) - the types mentioned here are from the same enum list as object types in the logical topology 67 * What parameters users can customize - these come from the same list as parameters in the parameterization part of the knowledge DB. A generator may have some parameters specific to itself, we don't care about those in this item. We care about parameters that describe a certain event/object and which of them we can manipulate if we choose this generator.67 * What parameters users can customize - these come from the same list as parameters in the parameterization part of the domain library. A generator may have some parameters specific to itself, we don't care about those in this item. We care about parameters that describe a certain event/object and which of them we can manipulate if we choose this generator. 68 68 * How the parameters can be customized, e.g., randomized, input by user, selected from a list ... 69 69 * Other inputs of the generator, their range of values and their relationship to the parameters from the above two items … … 80 80 81 81 During experiment design the system identifies all the objects and events in the metadescription and tries to map them to possible generators. This mapping should occur by the following formula: 82 * For each object and each event find out what parameters it may have from the parameterization part of the knowledge DB82 * For each object and each event find out what parameters it may have from the parameterization part of the domain library 83 83 * Highlight those that we actually plan to customize based on the meta-description 84 84 * Find a set of generators that can customize these parameters (how the customization is done is also important but it's a little vague to me yet how to formalize this part of spec)
