Updated Due date: Tuesday 3 March 2009 before 23:55
Team size == 2 (pair design/programming) !
Each team submits only one full solution.
Use the index.html template provided on the
assignments page. Use exactly this
format to specify names and IDs of the team members.
The other team member must submit a single
index.html file containing only the coordinates of
both team members. This will allow us to put in grades for
both team members in WebCT.
Beware: after the submission deadline
there is no way of adding the other team member's
index.html file and thus no way of entering a grade !
Your submission must be in the form of a simple HTML
file (index.html) with explicit references to
all submitted files as well as inline inclusion of
images. See the general assignments page for an
In this assignment, you will use UML Class Diagrams, UML Sequence Diagrams,
Regular Expressions, and
State Automata to design and verify a communication protocol of a client-server
system. The client part of the system has a user interface from which the user
can input messages and send them. The client also receives messages from
a chat room which it has subscribed to. A chat room is a server.
It receives messages from its clients and broadcasts these messages to subscribed
clients. A chat room can have 0 or more clients. A client can
be connected to 0 or more chat rooms at any time. In your design,
there will be no actual interaction with the human user.
Rather, the clients simulate human operations
(i.e., sending connection requests and sending messages) in a
The assignment is divided into two major parts.
In Part 1, you are given
an implementation along with the object-interaction trace (in a file) obtained from the existing implementation.
You need to model first a set of Regular Expressions, and then a set of FSAs, which you will
subsequently encode, to automatically verify whether
the system implementation complies with the system (protocol)
specification given in the requirements below (and modelled visually in Sequence Diagram form).
In Part 2, you need to model, synthesize and test
your own solution to the requirements. To do this, use BoUML and
model your implementation as a UML Class Diagram (including the method bodies).
Then, through BoUML, you will generate the Python code implementing the design. Your implementation must satisfy the same
requirements as Part 1. Verify your implementation by running the code, producing an output
trace, and then testing it using the same method employed in Part 1.
Warning: Both parts of the assignment will require considerable effort. Expect part 2 to take at least
as much time as part 1, and schedule your work accordingly. Given that there are two weeks available, a good
schedule would be to complete part 1 the first week, and part 2 the second week.
The following is a textual description of a simple protocol:
There are 6 clients and 2 chat rooms in the system. The clients
must be connected to a chat room before they can randomly send
The system works in a round-robin fashion.
In each round, a random client will connect or send a message to
a random chat room.
Initially, the clients are not connected. They try to connect to
a random chat room in each round. The requested chat room immediately
receives the request (no network delays).
A chat room can accept at most 3 clients. It accepts a
connection request if and only if its capacity is not exceeded.
The requesting client receives acceptance or rejection from the
chat room immediately (no network delays).
When connected, a client sends random messages to the chat room
in each round. The chat room immediately receives the message.
It processes the message and broadcasts it to all the other clients
(except the sender) connected to it.
The clients immediately receive the broadcast messages.
For simplicity, disconnection and reconnection need not be modelled.
Adding an association class between Clients and Chat rooms which
can record connections is not a bad idea.
It could be easier to model dynamic system behaviour if you define
two phases in a client's life: connecting and communicating.
Interaction behaviour to be verified (use cases):
When a client sends a connection request to a chat room, the
chat room immediately responds by printing to the output.
On receiving a connection request, the chat room immediately
makes a decision whether to accept the client or reject it.
When a chat room accepts a client, the client immediately
receives the acceptance and dumps to the output.
When a chat room rejects a client, the client also immediately
dumps the rejection.
When a client sends a message, the chat room immediately
receives it and prints the message to the output.
When a chat room receives a message, it broadcasts it to all
connected clients except the sender.
The sender cannot receive its own message after it sends it.
Six tasks you need to finish step by step:
Design the dynamic interaction behaviour in UML Sequence Diagrams for ONLY use cases 2 and 7 in BoUML;
Write regular expressions (refer to the format of the given output trace)
for verifying the above use cases (in this assignment, you only need to verify TWO use cases: use case 2 and use case 7);
the following is an example:
Regular expression pattern for rule 1:
##[^\n]*\n\(CL (\d+)\) RS (\d+)\.\n##[^\n]*\n\(CR \2\) RR \1\.\n
The following output will match the above pattern (multiple lines!):
## (Client 2) A connection request is sent to chat room 1.
(CL 2) RS 1.
## (Chat room 1) Received connection request from client 2.
(CR 1) RR 2.
Clarification: the above uses a Regular Expression notation commonly used in UNIX Regular Expressions
(as used in the stream editor sed for example) which differs from the examples given in class.
In addition to the slightly different notation, the expressive power of these Regular Expressions
is also higher as it allows for memory of matched expressions making the patterns context dependent.
[eE] stands for eorE.
[a-z] stands for one of the characters in the range a to z.
^ means "match at the beginning of a line/string".
$ means "match at the end of the line/string".
[^x] means notx, so
##[^\n]*\n matches a comment line: ## followed
by 0 or more non-newline characters, followed by newline.
. matches any single character.
X? matches 0 or 1 repititions of X.
X* matches 0 or more repititions of X.
X+ matches 1 or more repititions of X.
\ is used to escape meta-characters such as (.
If you want to match the character (, you need the pattern \(.
The ( and ) meta-characters are used to memorize
a match for later use. They can be used around arbitrarily complex patterns.
The first (\d+) in the above regular expression matches any non-empty sequence of
digits (assuming d has been defined elsewhere as [0-9]).
The matched pattern is memorized and can be referred to later by using
\1. Following matched bracketed patterns are referred to by \2, \3, etc.
Note that you will need to encode powerful features such as this one by
adding appropriate actions (side-effects) to your automaton encoding the regular
expression. This can easily be done by storing a matched pattern in a variable
and later referring to it again.
Design a FSA which encodes the regular expressions for verification in BoUML;
Implement this FSA for verification in the provided code framework (see scanner.py);
Run this FSA implementation (which in turn implements the Regular Expressions
which in turn encode the checking of interaction behaviour use cases which were modelled as Sequence Diagrams)
on the given output trace to verify the specification.
There is an intentional bug in the implementation (chatprotocol.py)
which makes it fail to satisfy the system specification.
You need to figure it out by verifying the output trace with your FSA implementation, and fix it (just one line).
The output trace generated from the above program: output
To make life easier, we use abbreviations to shorten the messages that you need to recognize in your RegExp/FSA. Here are the mappings:
CL := Client
CR := Chat room
RS := A connection request is sent to chat room
RR := Received connection request from client
AC := Accepted client
AB := Accepted by chat room
RC := Rejected client
RB := Rejected by chat room
SY := Says
RM := Received message from client
SM := Sent message to all connected clients except client
As you can see, any message in the output file which starts with "##" is some comments to make the output readable.
You need to ignore these messages when you do verification.
Programs used to implement FSA: the scanner is in scanner.py
which requires an input stream class CharacterStream found in charstream.py.
You must use BoUML in synthesizing your own implementation. A guide has been written to help you use BoUML. The program can be
tricky, and the guide will come in useful.
First, you will need to create your UML class diagram of the system. Do this in BoUML.
Analyze the requirements, and decide what classes you will need in your implementation. Create these classes in your diagram.
Your classes will need attributes and operations. Work from the requirements to decide what is needed.
Using the output from the existing implementation can be helpful.
Start filling in the bodies of the methods. Once again, the requirements and to a lesser extent the existing (ugly)
implementation will be helpful.
Generate code. BoUML uses a template for classes, attributes, procedures, and associations. This template allows BoUML to
generate code that uses the properties you have defined in your UML diagram. Operations are completed using the body you entered.
An error in the diagram will appear in the code, and thus you will need to carefully examine your generated code.
You may need to edit some of the templates that BoUML uses to generate code for specific procedures, associations, properties,
etc.--you should not assume that BoUML will always generate correct code! This will probably take many iterations before your code is
runnable, and more iterations before you are satisfied with the result. Likely, it will be the most time consuming step in Part 2.
Note that the benefit of this approach is that once one has set up the proper templates, any modification of the design allows
instant code synthesis. So, no need to go into the code and edit.
Continue working with code generation until you are comfortable that the code generated by BoUML is correct. While editing
generated code may be a convenient method to debug, it MUST be the case that the code you finally use is generated
with a single click from your UML diagram in BoUML.
Run your program and create a trace.
Use your existing testing framework (from Part 1) to verify that your code is correct. Repeat the test cases
given in part 1. If a test fails, you must go back into your UML diagram, correct the error, and repeat the test until your
implementation satisfies all requirements.
Submit your BoUML project, your code, and test results in the format described above.