A design patterns analysis of the umbra simulation framework

Abstract

NOTICE. This report was preparedas an accountof work sponsoredby an agencyoftheUnitedStates Government.Neither theUnitedStates Government, nor any agencythereof, nor any oftheir employees, nor any oftheir contractors, subcontractors, or their employees, make any warranty, expressor implied, or assume any legal liability or responsibilif orthe accuracy, completeness, or usefulness of any information, apparatus, product,or processdisclosed, or represent thatits use would notinfringe privately owned rights. Reference herein to any specflccommercialproduct,process,or serviceby trade name, trademark, manufacturer, or otherwise, doesnotnecessarily constitute or imply itsendorsement, recommendation, orfavoring by theUnitedStates Government, any agencythereof, orany oftheir contractors orsubcontractors. The viewsand opinions expressed hereindo notnecessarily state or reflect thoseoftheUnited States Government,any agencythereof, orany oftheir contractors. Printed intheUnitedStates ofAmerica. Thisreport has been reproduced directly fromthebestavailable copy.

Design theoretic analysis of three system modeling frameworks.

“…World Modules create child modules by using the Factory design pattern described in the literature. 33,34 Worlds can act as data repositories (e.g., black boards), react to events posted by their children and schedule events for their children. Like Swarm agents, World Modules retain all the properties of regular modules and parent-child relationships can be nested.…”