ENEL 589 – Group 5 Haysam Alsayed Lucian Aron Tatyana Rabinovitch Brooks Riley

1. ENEL 589 – Group 5 Haysam Alsayed Lucian Aron Tatyana Rabinovitch Brooks Riley MAS-UML-MODELER

2. OUTLINE • Motivation Behind the Project • Report #1 • Detailed Design • Acceptance Test Plan • Report #2 • Test Report • Project Documentation • System Demonstration • Conclusions and Questions

3. PRODUCT MOTIVATION: BACKGROUND Product Description • A software application that accepts as its input specifications from a Multiagent system, producing a suitable behavioral model diagram, compliant with UML 2.0 as its output. MASE UML 2.0

4. Motivation for designing a software that depicts the way a Multiagent system behaves? MAS analysis is complicated, therefore, development is hard. MAS are generally strictly a research topic but with this project potential is gained for acceptance in industry. Applicability of MAS: MAS enhance the adaptability of IT systems in 2 ways: Facilitates “external” maintenance Increases their own capabilities to perform necessary adaptations by themselves PRODUCT MOTIVATION: BACKGROUND

5. REPORT 1: DETAILED DESIGN Figure 1 – System Overview

6. IMPORTER & CONVERTER DETAILS Importing MaSEDiagrams: • Use AgentTool3, integrated in Eclipse – Java and MASE based. • Create .agent and .protocol artifacts. • Use “JDOM” API to create in-memory data structure of XML files. • Parse through data-structure to extract information needed by the MAS-UML Modeler. • Construct data structure of artifacts for use by the converter. • Verify for errors in input(Missing tags/Bad XML/Invalid data) Converting Process: • Use only 1 agent file, and any number of protocol files. • Protocol files map to violet UML sequence diagram files.(1to1) • Map roles to agents. • Create message structure. • Organize message sequence. • Create a final data structure ready to be sent to be converted by Violet.

7. Violet Sequence Diagram: XML Based Open Source Rendering Application Lifeline Nodes Activation Bars Messages

8. DETAILED DESIGN: Converter Converter Manager Module Violet Converter Definition Figure 1 – System Overview

9. Hus’ demo for the fair: Hampster-Fights Bring your own hampster – Min 50$ to enter fight

10. REPORT 1: ACCEPTANCE TEST PLAN Functional Requirement Tests (1) REQ-F01: Generates UML 2.0 compliant sequence diagram in XML format TEST-F01: Verification by inspection of system output diagrams REQ-F02: Output written to a user specified file TEST-F02: Verification by operation of the system and inspection of the user specified file REQ-F03: Create a new project TEST-F03: Verification by operation of the system

11. REPORT 1: ACCEPTANCE TEST PLAN Functional Requirement Tests (2) REQ-F04: Save/Open project TEST-F04: Verification by operation of the system REQ-F05: Close the project TEST-F05: Verification by operation of the system REQ-F06: Loads input files TEST-F06: Verification by operation of the system and inspection of the system input displays

12. REPORT 1: ACCEPTANCE TEST PLAN Functional Requirement Tests (3) • REQ-F07: Detects malformed/incorrect input • TEST-F07: Verification by inspection of the system with various incompatible inputs. Error messages from: • A random text input • Diagrams not belonging to the MASE methodology • REQ-F08: Allow user to search and read task help functions • TEST-F08: Verification by operation of the system and inspection for working system search functions • REQ-F09: The system must primarily be designed to run on the Windows platform • TEST-F09: Verification by operation of the system on Windows 2000 and Windows XP

13. REPORT 1: ACCEPTANCE TEST PLAN Non-Functional Requirement Tests (1) • REQ-NF01: Response Time • The system output must be updated within 15 minutes • TEST-NF01.0: Record several timings of the program, from input to system output. • TEST-NF01.1: Run ASUS PC Probe. Monitor the processor speeds, if output is not produced within 15 minutes conduct JUnit testing on each main system component. Re-check processor speeds. • REQ-NF02: Reliability • Mean Time Between Failure (MTBF) of 1000 hours or less • TEST-NF02.0: A certification of reliability will be performed.

14. REPORT 1: ACCEPTANCE TEST PLAN Non-Functional Requirement Tests (2) • REQ-NF03: Resource Constraints – Program Size • The client application executable must not exceed 50 MB • TEST-NF03.0: Find the size indicator in the properties information screen by right click on the program executable. • REQ-NF04: Resource Constraints • Minimum requirements including processor (Pentium III), memory (256MB of RAM), disk space (50MB) and Java Virtual Machine 1.5.0 or higher • TEST-NF04.0: Check for presence of minimum system requirements and run the application to test if the system operates a sample run to completion.

15. REPORT 1: ACCEPTANCE TEST PLAN Non-Functional Requirement Tests (3) • REQ-NF05: Resource Constraints – Memory Consumption • The client application executable must not exceed 256 MB • TEST-NF05.0: Run the application by using a sample input set. Click on the Windows platform desktop and run the Ctrl-Alt-Delete command. A Windows Task Manager should appear on the screen. Record the presented Mem Usage Value (this indicates the application memory consumption).

16. REPORT 1: ACCEPTANCE TEST PLAN Figure 6 – Test Tools Test Equipment The test tools and test software which is required for the performance of the tests is described below:

17. REPORT 2: TEST REPORT The documented summary of all the testing results: Figure 7 – Test Results

18. REPORT 2: TEST REPORT Figure 7 – Test Results

19. REPORT 2: USER MANUAL DOCUMENTATION Using the MAS-UML-Modeler Application Opening the Application: MAS-UML-Modeler is packaged in a JAR archive, to launch the application simply double-click on MAS-UML-Modeler.Jar and open the application with the installed Java Platform. Starting a new Conversion Project: • Select New Project • Choose a Working Directory (Where Created UML Diagrams will be stored)

20. REPORT 2: USER MANUAL DOCUMENTATION User Interface Layout: Area 1 – The MAS-UML-Modeler Console Area 4 – The UML Artifact Tree Area 2 – The MaSE Artifact Tree Area 5 – The UML Artifact Viewer Area 3 – The MaSE Artifact Viewer

21. REPORT 2: USER MANUAL DOCUMENTATION Adding MaSE Diagrams: • Select a MaSE artifact type in the MaSE artifact tree • Click the Add MaSE Diagram Button • Browse to the correct file and hit “Open” Converting Diagrams: • For Sequence Diagram: • Ensure that you have an Agent Class Diagram imported • Ensure that you have one or more Sequence Diagrams imported • Select the Sequence Diagram you wish to covert in the MaSE artifact tree • Click Generate -> Sequence Diagram • A message will be displayed in the MAS-UML-Modeler Console regarding the status of the conversion • Other Diagrams: • Functionality stubs for future releases

22. REPORT 2: USER MANUAL DOCUMENTATION Saving Project: • Click File -> Save • Browse to the location you wish to save the project • Enter a name for the project • Hit Save to File Opening Project: • Click File -> Open • Browse to the location where a project is saved • Select a file with the extension *.MaSE or *.UML • Hit Open Closing the Application: • Click File -> Close Project Or • Click the X in the Top Right Corner

23. SYSTEM DEMONSTRATION

24. REFERENCES [1] Bergenti, Gleizes, & Zambonelli. (2004). METHODOLOGIES AND SOFTWARE ENGINEERING FOR AGENT SYSTEMS: The Agent-Oriented Software Engineering Handbook. BOSTON, MA: KLUWER ACADEMIC PUBLISHERS. [2] Henderson-Sellers & Giorgini (Ed.). (2005). Agent-Orientated Methodologies. Hershey, PA: IDEA Group Publishing. [3] Heaton. (2007). Unified Modeling Language: Superstructure. Retrieved from http://www.omg.org/docs/formal/07-02-03.pdf [4] Bredemeyer & Malan. (2001). Defining Non-Functional Requirements. Retrieved October 17, 2007, from http://www.bredemeyer.com/pdf_files/NonFunctReq.PDF [5] Hammer. (1998). Software Metrics and Reliability. Retrieved October 18, 2007, from http://satc.gsfc.nasa.gov/support/ISSRE_NOV98/software_metrics_and_reliability.html [6] R. Grady. Practical Software Metrics for Project Management and Process Improvement. Prentice Hall, 1992

25. Questions?