Modeling Clases

---

Detailed Description

EOSimulator is divided in four modules: Core, Dist, Statics and Utils. In order to build a simulation, you have to implement subclasses of Core’s abstract classes. Those abstract classes are Model, BEvent, CEvent, Entity and EntityComp (if needed). You may use collections defined in Utils, pseudo-random number generators or distributions from Dist or output data collector from Statics.

Model Building

This is a main activity in the process of simulating a system. EOSimulator provides the user with five abstract classes that have to be derived properly to build a specific system. For most models you have to implement:

• one subclass of eosim::core::Model,
• one subclass of eosim::core::BEvent for each bounded event in your system,
• one subclass of eosim::core::CEvent for each conditional event in your system if you are using three phase approach,
• one subclass of eosim::core::Entity for each kind of entity in your system
• as many eosim::core::EntityComp subclasses as priority queues your system have.

Although, there are some implementation issues that you must pay attention while modeling your system with EOSimulator, otherwise it won’t run properly or it won’t run at all. If you don’t follow these instructions and try to execute a simulation, it might abort displaying an error message.

Classes
class	eosim::core::BEvent
	B Events. More...
class	eosim::core::CEvent
	C Events. More...
class	eosim::core::Entity
	Entity. More...
class	eosim::core::EntityComp
	Entities Abstract Comparator. More...
class	eosim::core::Model
	System Model. More...

---