ENEL 589 – Group 5Haysam Alsayed

Lucian AronTatyana Rabinovitch

Brooks Riley

MAS-UML-MODELER

Motivation Behind the Project Report #1

• Detailed Design• Acceptance Test Plan

Report #2• Test Report• Project Documentation

System Demonstration Conclusions and Questions

OUTLINE

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

PRODUCT MOTIVATION: BACKGROUND

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

REPORT 1: DETAILED DESIGN

Figure 1 – System Overview

IMPORTER & CONVERTER DETAILS

Importing MaSE Diagrams:i. Use AgentTool3, integrated in Eclipse – Java and MASE based.ii. Create .agent and .protocol artifacts.iii. Use “JDOM” API to create in-memory data structure of XML files.iv. Parse through data-structure to extract information needed by the

MAS-UML Modeler.v. Construct data structure of artifacts for use by the converter.vi. Verify for errors in input(Missing tags/Bad XML/Invalid data)

Converting Process:vii. Use only 1 agent file, and any number of protocol files.viii. Protocol files map to violet UML sequence diagram files.(1to1)ix. Map roles to agents.x. Create message structure.xi. Organize message sequence.xii. Create a final data structure ready to be sent to be converted by

Violet.

Violet Sequence Diagram: XML Based Open Source Rendering Application

Lifeline Nodes

Activation Bars

Messages

DETAILED DESIGN: Converter

Figure 1 – System Overview

Converter Manager Module

Violet Converter Definition

Hus’ demo for the fair: Hampster-Fights

Bring your own hampster – Min 50$ to enter fight

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

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

REPORT 1: ACCEPTANCE TEST PLANFunctional 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

REPORT 1: ACCEPTANCE TEST PLANNon-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.

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.

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).

REPORT 1: ACCEPTANCE TEST PLAN

Test Equipment The test tools and test software which is required for the

performance of the tests is described below:

Tool ID Test Environment Software

T01 Windows Operating System

T02 Eclipse SDK Version: 3.3.1.1

T03 JAVA Runtime Environment (JVM) 1.5

T04 Windows Task Manager

T05 ASUS PC Probe II (monitors fan rotations, temp, voltages, hard disk space, memory

usage, CPU type and processor speed)

T06 JUnit Testing Framework

Figure 6 – Test Tools

REPORT 2: TEST REPORT

The documented summary of all the testing results:

Figure 7 – Test Results

Requirement ID Requirement Description

Test ID Observation Result

REQ-F01 Generates UML 2.0 compliant sequence

diagram in XML format

TEST-F01 Valid UML diagrams are produced upon

inspection

PASS

REQ-F02 Output written to a user specified file

TEST-F02 As specified by users a user defined file will store system output

PASS

REQ-F03 Create a new project TEST-F03 Blank projects creation works

PASS

REQ-F04 Save/Open project TEST-F04 Save/Open specific project files functions

accordingly

PASS

REQ-F05 Close the project TEST-F05 Project termination functions as expected (no corrupted data

produced)

PASS

REQ-F06 Loads input files TEST-F06 Input files are loaded appropriately

PASS

REQ-F07 Detects malformed/incorrect

input

TEST-F07 Incorrect system input is detected with error

message

PASS

REQ-F08 Allow user to search and read task help

functions

TEST-F08 Help document is present and complete

PASS

REPORT 2: TEST REPORT

Figure 7 – Test Results

Requirement ID Requirement Description

Test ID Observation Result

REQ-F09 The system must be designed to run on

the Windows platform

TEST-F09 The system runs on both Windows 2000

and Windows XP environments

PASS

REQ-NF01 Response Time TEST-NF01.0 4.29 < 15 minutes and acceptable

PASS

REQ-NF01 Response Time TEST-NF01.1 < 15 minutes and acceptable CPU

usage of 54%

PASS

REQ-NF02 Reliability TEST-NF02.0 MTBF = 270.27 hours/failure < 1000

hours

PASS

REQ-NF03 Resource Constraints- Program Size

TEST-NF03.0 Program size = 1.75 MB < 50 MB

PASS

REQ-NF04 Resource Constraints

TEST-NF04.0 All resource constraints are accepted by the program which

functions as expected

PASS

REQ-NF05 Resource Constraints-

Memory Consumption

TEST-NF05.0 Memory Consumption = 26

MB < 256 MB

PASS

REPORT 2: USER MANUAL DOCUMENTATIONUsing the MAS-UML-Modeler ApplicationOpening 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:

i. Select New Projectii. Choose a Working Directory (Where Created UML Diagrams

will be stored)

REPORT 2: USER MANUAL DOCUMENTATIONUser Interface Layout:

Area 1 – The MAS-UML-Modeler Console Area 4 – The UML Artifact TreeArea 2 – The MaSE Artifact Tree Area 5 – The UML Artifact ViewerArea 3 – The MaSE Artifact Viewer

REPORT 2: USER MANUAL DOCUMENTATION

Adding MaSE Diagrams:i. Select a MaSE artifact type in the MaSE artifact treeii. Click the Add MaSE Diagram Buttoniii. Browse to the correct file and hit “Open”

Converting Diagrams:iv. For Sequence Diagram:

1. Ensure that you have an Agent Class Diagram imported2. Ensure that you have one or more Sequence Diagrams imported3. Select the Sequence Diagram you wish to covert in the MaSE artifact

tree4. Click Generate -> Sequence Diagram5. A message will be displayed in the MAS-UML-Modeler Console

regarding the status of the conversionv. Other Diagrams:

1. Functionality stubs for future releases

REPORT 2: USER MANUAL DOCUMENTATION

Saving Project:i. Click File -> Saveii. Browse to the location you wish to save the projectiii. Enter a name for the projectiv. Hit Save to File

Opening Project:v. Click File -> Openvi. Browse to the location where a project is savedvii. Select a file with the extension *.MaSE or *.UML viii. Hit Open

Closing the Application:ix. Click File -> Close Project Orii. Click the X in the Top Right Corner

SYSTEM DEMONSTRATION

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

QUESTIONS?