Graphic Interface for Organizations in IPDS

Presentation 2Donald Lee

Overview

• Action Items• Project Plan• Architectural Design• Formal Specifications• Technical Inspection Checklist• Test Plan• Prototype Demonstration• Technical Risks• Questions/Comments

Action Items

• Requirement Changes for Project– Focused on the Graphical Interface for

Organization Tree in Simulation.– Moved away from creating the IPDS from ground

up.• Modified COCOMO and Gnatt Chart to fit new

requirements

Project Plan – Updated Gnatt Chart

Adjusted COCOMO Estimates

• Effort Applied (E) = = 3.39 • Development Time (D) = = 3.96 Months

Cost Drivers Rating ValueProduct attributesRequired software reliability Nominal 1Size of application database Nominal 1Complexity of the product High 1.15Hardware attributes Run-time performance constraints Nominal 1Memory constraints Nominal 1Volatility of the virtual machine environment High 1.15Required turnabout time Low 0.87Personnel attributesAnalyst capability High 0.86Applications experience High 0.91Software engineer capability High 0.86Virtual machine experience High 0.9Programming language experience High 0.95Project attributes

Application of software engineering methods Very High 0.82

Use of software tools Nominal 1Required development schedule Nominal 1

Project Plan – Phase 3 Deliverables

• Final Source Code• Component Design• User Manuel• Assessment Evaluation• Testing Evaluation• Technical Inspection Letters• Project Evaluations• References

Architectural Design• 3 Main Components

– Follows Model-View-Presenter Architeture.– IPDS (Model)

• Runs the Simulation and contains Agent Information

– Simulation Presenter• Provides the logic behind the View Component• Reads Model Information and Passes it to the View Component

– Simulation View• GUI Interface (Using Java Forms and Panels)

– Provides Graphical Interface for Organization Tree in Simulation

• Allows user to interact with graph and request additional information (each agent status, name of IPDS, etc.)

• Emphasis on View and Presenter– Model provided already provided.

Architecture Design – Component Design

Architectural Design – Class Diagram

User Interaction Sequence Diagram

Formal Specifications

Formal Specifications (Contraints)

Formal Specifications (Method Constraints)

Technical Inspection ListInspection Item

The components specified are consistent with the Model-View-Presenter (MVP) pattern including interfaces and description of responsibilities.

All symbols used in the class diagram conform to UML 2.x standards.

All symbols used in the component diagram conform to UML 2.x standards.

All symbols used in sequence/use case diagrams conform to UML 2.x standards.

The high-level class diagram is consistent with the project structure and clearly describes it.

All specifications in regards to interface operations including pre & post conditions are specified and consistent.

The OCL specifications are consistent with the high-level class diagram.

Test Plan

• Black Box Testing for All Test Cases.• Graph and agent information panel used to

determine outputted result and compared to expected result.

• Focused on the SimulationPresenter and SimulationView.

• 6 Test Case to Test each Display Functionality and Specific Functionality as well as Scalability

Test Case Sample - Inputs

IPDS Agent ListH44 H44

H44_FH45 H45

H45_FH46 H46

H46_FH47 H47

H47_FN43 N43

N43_F N43_Fin43 N43inN43

Test Case Sample – Test FormExpected Outcome Functionality Tested Actual Outcome Pass/Failed/IncompleteIf one or more agents are considered offline, unavailable or paused; then the IPDS vertex should be colored Yellow.

SF3, DF3

If all agents are considered online; then the IPDS vertex should be colored Green.

SF3, DF3

If all agents are considered offline, unavailable or paused; then the IPDS vertex should be colored Red.

SF3, DF3

If vertex selected, JPanel showing agent list/information acquires the corresponding vertex selected.

SF1, DF1, SF7

Prototype Demonstration

• Creates Graph from the IPDS Model through the Presenter– Includes creating each vertex to represent each

IPDS.– Includes creating each edge between each

connection• Mouse Selection Functionality and Drop Down

Box for User Interaction.

Technical Risks

• Listeners and Observers– Implementing Listeners to monitor each IPDS

object

Questions / Comments?