Saint-Petersburg State University ITMO 1Projects in SPb IFMO Yartsev Boris [email protected]...

Saint-PetersburgState University ITMO

Projects in SPb IFMO 1

Yartsev [email protected]

Computer Technology Department,

Saint-Petersburg State University ofInformation Technology, Mechanics and Optics.

Russia

Overview of the projects, developed by the students of SPb IFMO under the supervision of professor A.A.Shalyto



Projects in SPb IFMO

• Managed under the supervision of professor A.A.Shalyto

• Developed in the context of automata programming and open project documentation

• Are available from the Informatic Systems dept. site – http://is.ifmo.ru



Project development

• Students work at the projects in the third year of studies

• During the third course students regulary meet their scientific advisor A.A.Shalyto and discuss new ideas and documentation

• There are 45 projects, that have already been developed, they are available from the site

• All the documentation is written in russian language. There is an abstract in english.



Documentation structure

• Introduction• The formulating of the tasks• The description of the approach• Screenshots of the programs• Class diagrams• Automata documents• Conclusion• Source code



Automata documents

For each automata:• Verbal description (declaration of intent)• Scheme of automata connections

(automata interfaces)• State transition diagram• Code, isomorphic to the diagramFor the whole system:• Scheme of automata intercommunication



Overview of several projects

The most interesting and maniford

projects are presented here



Examples of the projects

• Traffic lights controller

• SMTP protocol implementation

• CodeRally project

• Robocode project

• Automata graph designer

• Translator between different Japanese alphabets



Traffic lights controller

• Developed by A. Distel and D. Kobak

• Demonstrates the simple critical object control program

• Handles the malfunctioning – automatically switches to blinking yellow



Traffic lights. Conclusions

• Automata approach can be used in critical objects control



SMTP protocol implementation

• K. Agafonov and D. Poroh implemented the SMTP protocol.

• Windows gui and command line client, Unix command line client and server

• Handles several exceptions – connect termination and server shutdown




• The usage of logging• Standartized logging protocol for all the

classes• Three modes – silent, full, only open/close

connection events. Different automata can be logged

• Via logging, one can quickly find the place in the code, where the execution went wrong.



SMTP procotol implementation. Conclusions

• Automata approach can be used in server side programming

• Debugging of services is quite hard. Logging eases it



CodeRally

• Developed by gold-winner of ACM 2003 finals Eugene Yuzhakov

• The game created by Alphaworks company (IBM)

• Emulates the track for several little cars• Cars acquire points by passing through

checkpoints and shooting• The winner is the car with maximum points

at the end of the round.



Coderally

• In the documentation the author makes global strategy analysis, on which the code of the program is based.

• The analysis is supported by pictures, describing the way of movement as it is shown on the pictures



Screenshot from the game



Coderally

• Automata state transition diagram of the car controller.The states and events are named with short identificators



Events and states

• The explanation is given before the graph in the following form –

• z0 – choosing the optimal checkpoint

• z1 – choosing the optimal trajectory

• z2 – moving towards the refuelling station

• e3 – the car was hit by the bullet

• ... And so on



Coderally. Conclusions

• There was no open documentation available for this game

• The conclusion and the source code go at the end of the documentation.

• In the conclusion the author tells about the accomplishments and drawbacks of the project. The conclusion is created after the documentation has been written and the program has been developed

• The automata diagram for this project is simple, the main attention is paid to the mathematical aspect of the game



Robocode ver. 1 and 2

• The Robocode project is pretty much the same as the CodeRally. But on it’s example the ease of refactoring of the open source code and open documentation can be shown.

• Robocode is the Java game, created by Alphaworks company (IBM). The aim is to program the artificial intelligence of the tank




• Several tanks fight on the field

• They can shoot and move

• With radar they can scan the bullets and other tanks

• The winner is the tank, that destroys all other tanks.




• Originally it was developed by N. I. Tukkel and A.A. Shalyto

• Then Denis Kuznetcov, the gold-winner of the 2001 ACM finals, modified the original version

• The ease of modification proved the advantages of open project documentation and automata programming



The graph model for the ver. 1



The graph model for the ver. 2



Robocode. Conclusions

• To modify the logic of the program there is no need to look through the source codes

• Such approach eases the support of the software in the companies

• The time needed for the adaptation of the new member of the team decreases



Robocode. Conclusions

• Cynical was the best tank at the robocode competition for several weeks

• During the year it still remained in the top list of the tanks

• The authors aim was not the creation of the best tank in the world, they wanted to create the best technology in the world =)



Robocode. Conclusions. Javadoc and OPD




• Javadoc does not provide the enough information for the developer to understand the logic of the program

• However javadoc can be used as the supporting tool



Automata graph designer

• Developed by I. Anichkin

• Designed to work with automata graphs

• Faster and easier to use than Microsoft Visio and Rational software



Automata graph designer. Conclusions

• GUI applications can be programmed with automata approach



Japanese translator

• Developed by Ekaterina Lysenko and Pavel Skakov

• Four different system of written language in Japan

• The program makes the transliteration between the systems



Japanese translator

• This translator shows, how the automata can deal with the strings and lexemes.



Japanese translator



Japanese translator. Conclusions



Conclusions

• Simplicity needs projection and good taste. L. Torvalds

• It is a mistake to think that programmers wares are programs. Programmers have to produce trustworthy solutions and present it in the form of cogent arguments. Programs source code is just the accompanying material to which these arguments are to be applied to. E. Dijkstra



Conclusions

• The introducted approach, as we think, satisfies the requirements given before.

Saint-Petersburg State University ITMO 1Projects in SPb IFMO Yartsev Boris [email protected]...

Documents

Transcript of Saint-Petersburg State University ITMO 1Projects in SPb IFMO Yartsev Boris [email protected]...