VirtuCo

1
VirtuCo

• Technical specification

2
Contents

• Overview
• Communicates selected architecture and design in
  high level
• Architecture
• Server
• Physical view
• Software components view
• Subsystems view
• Messaging view
• Client
• Component view
• MIDP1.0 MIDP2.0 separate solutions

3
Contents (contd.)

• Design
• Server
• Daemon implementation and client proxies
• JMS usage
• General service structure
• Message handling example
• MultiUserSessionService
• Client

4
Legend description
The border between VirtuCo system and the rest of
the world
An interfaced component having a specific
responsibility
An upper concept for all parts of the system
JMS based functionality that delivers
messages between the components using its services
Messages are passed between the components
JMS provides the implementation of this component
5
Server architecture
6
Server architecture Physical view

• Purpose Communicate physical layout of VirtuCo
  system and its relationships to other systems

7
Server architecture Physical view
8
Server architecture SW Components view

• Purpose Describe different software components
  that forms the server side VirtuCo system

9
Server architecture SW Components view
10
Server architecture Subsystems view

• Purpose Communicate which subsystems interact
  with each other

11
Server architecture Subsystems view (contd.)

• Description and responsibilities of layers
  (subsystems)
• Transport
• Provide client-server communications
• Services (Conversation, File transfer etc.)
• Value-adding services for users.
• User Management
• Provide user management services (lookup,
  persistence etc.)

12
Server architecture SW Components view
13
Server architecture Messaging view

• Purpose Communicate how JMS Provider of JBoss is
  used for message transportation and how messages
  flow through system.

14
Server architecture Messaging view

• The Message broker is based on a JMS topic that
  filters messages based on the JMS clients
  identifiers. Thus, messages are delivered to the
  correct destinations.
• It is also possible to broadcast messages using
  special broadcast ids that correspond to the
  servers internal component types, i.e. services
  and client proxies.

15
Client architecture
16
Client architecture Component view

• Purpose Communicate different components inside
  client subsystem

17
Client architecture Component view (contd.)

• Description and responsibilities of components
• Connection
• Handles communications to VirtuCo server
  application (HTTP / Socket)
• Controller
• Handles starting and destroying of the client
  application
• ConversationService
• Provides conversational features to user on
  client side
• Other service(s)
• Other services like User Management (Buddy list
  management etc.)
• View(s)
• Handles presentation of service specific
  information on client device

18
Client architecture Component view
19
Server design
20
Server design Daemon implementation and
client proxies
21
Server design JMS usage
22
Server design General service structure
23
Server design Message handling example
24
Server design MultiUserSessionService
25
Server design MultiUserSessionService
(contd.)