Minutes of Meeting - FER-a

outstandingmaskΔιαχείριση Δεδομένων

29 Νοε 2012 (πριν από 8 χρόνια και 8 μήνες)

340 εμφανίσεις

1


Minutes of Meeting





Project

Profile Analysis and Reconciliation Tool

Date

October 6
th
,

2011



Start
-
end
time

12:00


13:00

Responsible

Robert Borošak

Location
/type

Zagreb, Radnička
cesta 39, Kapsch


Attended by

Location

Remarks

Marin Orlić

Con
f. room
, Zagreb

Attended whole meeting

Davor Perić

Conf. room
, Zagreb

Attended whole meeting

Matija Hanžić

Conf. room
, Zagreb

Attended whole meeting

Igor Rutkowski

Conf. room
, Zagreb

Attended whole meeting

Robert Borošak

Conf. room
, Zagreb

Attended who
le meeting





1.

Architecture of the fraud management system


Mr. Beslać showed

us

the
architecture

of the fraud management system so we could better
understand the project requirements.


CONCLUSION:
After
understanding the system
s

architecture

we were rea
dy to hear the project
requirements
.


2.

PARTool requirements

and discussion about the project


Mr. Beslać told us the project requirem
ents and then we discussed about them.


CONCLUSION:
We agreed on some technologies we will be using and if we finish the pro
ject
earlier

then predicted we will get more requirements like automatic comparison of profiles.

We agreed that

we will use:




Apache web server



PostgreSQL

Database



Debian OS


We can choose the programming language our selves.


The main requirements of the
project are:




The application

should
display in a
graphical and numeric format

selected subscriber(s)
behavior profile(s).



Visualization of the
profiles
should be created on the
user

request



Which elements will define a profile should be definable in the application parameter
selection frame



We need to implement some kind of
authentication



A
pplication should be compatible

with

new web browsers


2



W
e

should expect, that agents don
'
t have access t
o I
nternet (so no external web

services

should be used
)



We
mustn't

send any cdr data
to

the

client


At this point
autmatic comparis
on of profiles is not requi
red.


ACTION:
Team members will further discuss those requirements and propose some ideas about t
he
system
architecture
. Team will dec
ide which programming languages and tools will be used.