Acme Simulator

1
Acme Simulator
Team Members
Karthik Vivekanandan
Rajeshwari Parthasarathy
Ramya Ramamurthi Ravi
Ranjan Vikram Ramadoss
2
Who are we why are we here?
3
Roles Responsibilities
4
Roles Responsibilities

• Karthik Vivekanandan
• Process Quality Manager
• Requirements Analyst
• Rajeshwari Parthasarathy
• Designer Architect
• Developer
• Ramya Ramamurthi
• Project Manager
• Developer

5
Roles Responsibilities

• Ravi Ranjan
• Configuration Testing Manager
• Developer
• Vikram Ramadoss
• Requirements Analyst
• Developer

6
Agenda

• Product Vision
• Goals
• Proposed Enhancements
• Milestones
• Integration Challenges
• Risks
• Demo

7
Stakeholder Summary

• Dr. Shawn Butler Faculty CMU
• Dr. Lynn Robert Carter Principal Fellow
  CMU-West
• Peter Cornett Prasad Mettu from Boeing,
  CMU-West MSSD Students
• Dr.Bradley Schmerl

8
Product Vision

• Acme Simulator will facilitate
• Performance evaluation of software architectures.
• Evaluate effect of changes in architecture on
  performance and security.
• Threat Modeling
• Incorporating other quality attributes.

9
Goals

• Port the existing Architecture Simulator into the
  ACME Studio.
• Develop an enhanced (new) version of ACME
  Simulator
• Develop a security module for the ACME Simulator.
• Threat Modeling analysis

10
Goal 1 Porting ArchSim in ACME
ECLIPSE
ACME Studio
Architecture Simulator
11
Product Release 1 can ?

• Define performance properties
• Transaction Complexity
• Response Range

12
Product Release 1 can ?

• Create Component System transactions
• Simulation
• Reporting

13
Goal 2 - Simulation Enhancements

• Enhanced Simulation
• Queuing Model
• Multi threading
• Load Generation
• Probability Distribution
• System Load
• Error Handling
• Errors and Failures
• Reporting

14
Goal 3 Incorporating Security

• Effect of security components and connectors on
  performance
• Classification of security components
  connectors

15
Goal 4 Threat Modeling

• Identification of Threats Assets
• Modeling and Analysis of Threats
• Rating of threats based upon simulation and
  analysis.

16
Milestones
1st Nov 04
1st March05
30th June05
10th Aug05
Project Start Date
Team leaves for India
Release 1
Release 2
Release 2
7th March
10th Jan05
11th Feb
27th May
20th June
30th June
C1 C2
Construction
Transition
Inception
Closure activities for Release 1 transition to
CMU Pittsburgh
Elaboration
17
Integration Challenges

• Synchronization of various resources across
  multiple acme models
• Concurrency issues
• Used asynchronous execution blocks provided by
  eclipse platform

18
Risks

• Release 1
• Remote stakeholders
• No design document for ACME Studio
• Release 2
• Lack of experience in simulation
• Team Attrition

19
Looking forward

• Develop a scalable simulation framework.
• Creating extensible system that can be enhanced
  in future to capture interoperability of other
  architectural quality attributes.
• Threat modeling will need a demonstrable proof of
  concept.

20
Lessons Learned

• Prototyping in the early stages of project and
  mitigating technical risks
• UI prototypes in discussing requirements with
  remote stakeholders
• Importance of meeting all stakeholders together

21
Demo
22
Discussion