Graphic Interface for
Organizations in IPDS
Presentation 2
Donald 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
Product attributes
Required software reliability
Size of application database
Complexity of the product
Hardware attributes
Run-time performance constraints
Memory constraints
Volatility of the virtual machine environment
Required turnabout time
Personnel attributes
Analyst capability
Applications experience
Software engineer capability
Virtual machine experience
Programming language experience
Project attributes
Application of software engineering methods
Use of software tools
Required development schedule
Rating
Value
Nominal
Nominal
High
1
1
1.15
Nominal
Nominal
High
Low
1
1
1.15
0.87
High
High
High
High
High
0.86
0.91
0.86
0.9
0.95
Very
High
Nominal
Nominal
0.82
1
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 List
Inspection Item
The components specified are
consistent with the Model-ViewPresenter (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
H44
H45
H46
H47
N43
Agent List

H44

H44_F

H45

H45_F

H46

H46_F

H47

H47_F

N43

N43_F

N43_Fin43

N43inN43
Test Case Sample – Test Form
Expected Outcome
If one or more agents
are considered
offline, unavailable or
paused; then the IPDS
vertex should be
colored Yellow.
If all agents are
considered online;
then the IPDS vertex
should be colored
Green.
If all agents are
considered offline,
unavailable or
paused; then the IPDS
vertex should be
colored Red.
If vertex selected,
JPanel showing agent
list/information
acquires the
corresponding vertex
selected.
Functionality Tested
SF3, DF3
SF3, DF3
SF3, DF3
SF1, DF1, SF7
Actual Outcome
Pass/Failed/Incomplete
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?