MIT Modeling Research Under NASA/AATT

Format of Model Reviews (Revision 2; 12/28/95)

Item 1: Primary Model Category: The models is assigned to one of six model categories: (i) System-wide models; (ii) airfield and terminal airspace models; (iii) en route sector traffic and workload modeling; (iv) risk evaluation and safety models; (v) human factor and automation models; (vi) economic and cost-benefit models. Appropriate modifiers can be indicated to povide a better classification of the model and additional categories may be indicated as secondary ones. Item 2: Summary: Provide a brief description of the model (one to three paragraphs). This can consist of the “abstract” provided in the model developer’s documentation, if adequate, or a summary prepared by the evaluators. This section should include an identification of some of the fundamental features of the model, specifically: (i) primary methodology (e.g., analytical model, fast-time simulation, real-time simulation, AI/knowledge-based model, etc.); (ii) level of detail (microscopic vs. macroscopic approach); (iii) principal "competing" models (identifies other models in the same area). Item 3: Input Requirements: Identifies the most important inputs necessary to run/use the model. Also identifies, when applicable, databases accompanying the model, availability of default inputs, etc. Item 4: Outputs: Identifies the major outputs obtainable from the model. Item 5: Major Assumptions: Lists the major assumptions of the model with remarks, when appropriate, on their reasonableness. Also notes aspects of real-world operations which are omitted by the model. Item 6: Computational Characteristics: Indicates whether a computer program has been written to implement the model in question. If a computer program does exist, the items that should be covered (whenever such information is available) include: computer language used; hardware and software requirements; typical running times for the model; graphics or other interfaces; quality of model documentation; model support by sponsoring organization; amount of effort needed to learn how to use the model and to set up inputs for computer runs. To assist in compiling this information a brief questionnaire has been prepared that would preferably be filled out by the developer of the model or someone very familiar with it. The questionnaire can be found at the end of this document. Item 7: Modularity and Flexibility: An indication as to how easily the model can be extended to include additional considerations and extensions. Comments may also be made on the possibility of combining the model with others to provide a tool of expanded scope. Item 8: Status of Model: Indicates, whenever this information is available, whether the model in question is being actively used at this time, whether further model development is in progress, etc. Item 9: Extent of Model Validation: Information on whether or not the model has been validated, and if yes, in what way. Item 10: Principal applications: Identifies the types of issues that the model is best suited to address. Also provides examples, if any, of projects in which the model has been used in the past. Item 11: Model Availability: Identifies model's vendor, if applicable, or model's sponsoring organization. Costs are given, if appropriate. Contact person(s) are identified if possible. Item 12: Information Base for Model Evaluation: Identifies the means employed to prepare the evaluation of the model (interview(s), papers reviewed, other documentation reviewed, hands-on experience, etc.). Documents describing the model should be identified in detail (title; author(s); organization generating the report; report number; date; other identification information --such as NTIS number or sponsoring government agency, if any). Item 13: Summary Evaluation: Offers the evaluator's appraisal of the value and usefulness of the model on an absolute basis and, if possible, by comparing it to other models in the same area. Specific strong and weak features of the model should be listed to provide guidance and assistance to potential users of the models or to future researchers in this area. Computational Characteristics 1. Does code exist? ( Y / N ) 2. Required operating system(s) 3. Hardware requirements (if multiple items are listed, indicate AND or OR): Platform(s): Memory (RAM and hard drive) Other (tape drive, input devices, monitors) 4. Software / compiler requirements: 5. Contact / availability of support: 6. Evaluations (list major deficiencies / strengths): Documentation ( Poor / Adequate / Good ) Startup effort / default inputs ( Low / Moderate / High) User interface ( Poor / Adequate / Good ) Typical run time: Name: __________________ Date: ___________________