1. Ontologies Reasoning Components Agents Simulations Project Topics: MCI 2006 Jacques Robin

2. Simulation Generation Phase > GameEnvironment > EnvironmentReasoningTraceGenerator > Player > AgentReasoningTraceGenerator > channel > ActionPercept get():action send(percept,agent) > PerceptAction get():percept send(action) > Simulate

3. Batch Simulation Analysis Phase > AgentReasoningTrace > EnvironmentReasoningTrace > GameEnvironment > EnvironmentReasoningTraceGenerator > Player > AgentReasoningTraceGenerator > AgentAnalysisUserCommands > TeamAnalysisUserCommands > EnvironmentAnalysisUserCommands > ReplayGUI > Replay

4. Batch Simulation Analysis Phase GUI > AgentAnalysisView > TeamAnalysisView > EnvironmentAnalysisView > TeamAnalysisController > EnvironmentAnalysisController > AgentAnalysisController > AgentAnalysisCommandOptions > TeamAnalysisCommandOptions > EnvironmentAnalysisCommandOptions > ReplayGUI

5. Topics  Topic 1: Agent Ricardo, Vitor, Patricia, Uilma 1.PerceptAction interface; 2.AgentAnalysisUserCommands interface; 3.AgentReasoningTrace interface; 4.Player agent; 5.AgentReasoningTraceGenerator aspect.  Topic 2: Environment Marcos, Fabrício, Sandra, Eduardo 1.ActionPercept interface; 2.Channel; 3.EnvironmentAnalysisUserCommands interface; 4.EnvironmentReasoningTrace interface; 5.Game environment agent; 6.Simulate component; 7.EnvironmentReasoningTraceGenerator aspect.  Topic 3: Agent Analyzer João, Daniel, Priscila, 1.AgentAnalysisCommandOptions interface; 2.EnvironmentAnalysisCommandOptions interface; 3.AgentAnalysisView component; 4.AgentAnalysisController component; 5.EnvironmentAnalysisView component; 6.EnvironmentAnalysisController component;  Topic 4: Team Analyzer Gustavo, Paulo, Rafael, Luiz 1.TeamAnalysisUserCommands interface; 2.TeamAnalysisCommandOptions interface; 3.TeamAnalysisView component; 4.TeamAnalysisController component; 5.ReplayGUI component; 6.Replay component.

6. Deliverables Calendar  06/07:  Version 1 model UML/OCL of interfaces  Version 1 architecture UML/OCL of components  18/07:  Version 2 model UML/OCL of interfaces  Version 2 architecture UML/OCL of components  Version 1 complete specification UML/OCL of components  Version 1 UML/OCL specification of component tests  27/07:  Version 2 complete specification UML/OCL of components  Version 1 Java-CHORD implementation and tests of interfaces and components  ??:  Version 2 Java-CHORD implementation and tests of interfaces and components

7. Artifacts for UML/OCL Models for each (sub)-component  Specification (what does it do?)  Compulsory:  Class diagram and object diagram with component’s interface and ports showing its connections in the assembly of its containing component  In that class diagram, classes and associations defining the type of each operation parameter and return value in terms of UML2 primitive types and OCL library types  For each component, interface or class, OCL classifier invariants  For each attribute, OCL default and derived values  For each operation from each interface, OCL pre-conditions  For each query operation from each interface, OCL body,  For each state altering operation from each interface, OCL post-conditions  If needed:  Use-case diagram to define at a high-level of abstraction the services provided by the component  Protocol state machine in case which interface operations of the component class can be invoked is restricted in terms of the component’s state in a way that is too complex to express by a simple pre-condition

8. Artifacts for UML/OCL Models for each (sub)-component  Realization (how does it do it?), all compulsory:  Class diagram and object diagram with component’s interface and ports showing its internal assembly in terms of embedded, finer-grained components, classes and associations  In that class diagram, classes and associations defining the type of each operation parameter and return value in terms of UML2 primitive types and OCL library types  For each component, interface or class, OCL classifier invariants  For each attribute, OCL default and derived values  For each operation from each interface, OCL pre-condition  For each query operation from each interface:  OCL body under 10 lines, or  Activity diagrams with OCL expressions as actions, all under 10 lines  For each state altering operation from each interface:  OCL post-condition under 10 lines or  Activity diagrams with OCL expressions as actions, all under 10 lines  Activity diagram with OCL expressions as actions and objects, to specify each operation body or post-condition that would require over 10 lines of OCL

9. Artifacts for UML/OCL Models for each (sub)-component  Testing, all compulsory:  Class diagrams and object diagrams with  Testing interface, allowing its client components to run tests that access its internal state  For each server component which services it requires, tester sub-component to generate tests, run them by connecting itself to the server component testing interface and check their results based on the server’s interface operation pre and post-conditions  In that class diagram:  Classes and associations defining the type of each operation parameter and return value in terms of UML2 primitive types and OCL library types  For each component, interface or class, OCL classifier invariants  For each attribute, OCL default and derived values  For each operation from each interface, OCL pre-condition  For each query operation from each interface, OCL body,  For each state altering operation from each interface, OCL post-conditions