Documente Academic
Documente Profesional
Documente Cultură
Management Summary
The author investigates for Talking Trend (TT) what software exists within the
ILPS research Group of the University of Amsterdam. As such, nine applications
are recognized that are of interest to TT. One of these applications is the
FietsTas. The current document provides a detailed technical overview of the
application. The information provided is obtained through an interview with
Valentin Vijkoun from the ILPS group
Based on the data described in the detailed findings below, the following answers
can be given to the research questions stated by TT1:
2. What quality does the software have, what should be done to improve the
quality, such that the software can be used for commercial purposes?
The NER module needs to be replaced before the software can be applied
commercially.
The main attractiveness of FietsTas is that the functional quality of the
different modules from the ILPS group can be evaluated by TT without
having to install and combine them.
1
Contract between Stokman and Talking Trends of October 2009.
Detailed findings
The current section describes 50 answers to various technical questions:
General
1 What is the name of application?
FietsTas.
Architecture
10 What is the architecture of the application?
A high level overview of the architecture is given in Figure 1. FietsTas is
implemented as a Web service using a simple client-server stateless
protocol: an application sends requests using standard HTTP POST or
GET requests, and the FietsTas service responds by sending a
standardized XML response over HTTP.
15 Are there any platform limitations that may be reached in the foreseeable
future (e.g. maximum file size, maximum number of concurrent users?
The mySQL database has maximum number of connections, although this can
be configured. In case up scaling is required beyond the capacities of mySQL;
this may be achieved using other, commercial databases.
Programming languages
18 Which languages are used in the system?
The FietsTas application is developed in programming language Python. The
internal components are treated as black boxes.
Code generation
21 Are parts of the system generated?
No, source code is not generated. Also, FietsTas does not require training data.
22 How are parts of the system generated?
Not applicable (N. A.)
Data storage
23 Which type of storage is used?
Using a mySQL database.
25 How is the connection with the database and the marshalling of data
organized?
The application contains a special layer containing code to connect to a database
or to flat files. To access the database, standard Python libraries are used for
executing SQL commands.
User interface
26 Which kind of user interface does the system have (text, web, windows)
FietsTas provides a web interface for humans, accessible through a web
browser. The web interface allows users to manually upload documents. Only a
subset of the FietsTas functions is made available through this interface: users
can upload/list documents and generate simple annotations/clouds. This
interface can be used for testing purposes and for users to test applicability of the
system in their applications.
A simple (password-protected) web interface is also provided for FietsTas
developers. This interface allows developers to visualize internal objects of
FietsTas. It can also be used for debugging.
28 How is the connection between the user interface and the rest of the
application organized?
Using the programming language PHP.
Reporting
29 Are reporting facilities available in the application?
There is a monitor available which is written in Python
33 What is the current size of the data that can be handled by the
application?
This is not known explicitly. The FietsTas application is used extensively in
projects as Duoman, TNT (tracking of events in news), and Bridge (a project
together with Beeld en Geluid).
Documentation
Is any of the following documentation available?
36 Architecture description
An overview of the architecture is given in the Duoman document, Data collecting
and indexing infrastructure, STEVIN internal report, November 2008.
37 Functional documentation
Functional documentation is available. The document describes
• how users can obtain keys to use the service,
• the type of documents that can be and should be uploaded,
• the type of request that user scan ask FietsTas to perform
• How a user can provide feedback (this functionality is work in progress).
38 Technical documentation
At http://zookst5.science.uva.nl:8080/FietsTas/ there is developer
documentation. This link is not available from outside though.
Configuration management
42 Which version control system is used?
SVN.
45 How typical is the build process (i.e. would new developers know how this
works?)
There is a readme for step by step instruction. Installation by Valentin would take
a few days
Deployment process
46 Is the deployment process automatic?
No.
Testing
47 Does an automated daily test run exist?
No.