ICO wiki - User contributions [en]

Talk:KKMK

2013-06-04T18:31:57Z

Vevainu: /* Meeskond „V“ retsensioon meeskond „KKMK“ teenuse kohta – 4.06.2013 */

==Retsensioon meeskonna "KKMK" XML ülesande kohta==
Meeskond KKMK on teinud XMLi genereeruvaks C# koodi kaudu, mis on väga lahe kuna tiim on ilmselgelt vaeva näinud. Sellegipoolest tekib küsimus, et miks on vaja sellist asja luua, sest ilmselgelt antud ülesande juures oleks käsitsi selle XMLi tegemine tunduvalt kiirem olnud. Üldiselt on C# kood siiski selge ja arusaadav.
Koodi poolt genereeritud XML fail on korrektne ja täidab ka antud ülesande nõudmisi.
Stiilifail 1 on hästi tehtud, see väljastab korrektse HTMLi ja lisab sinna ka stiilid. Muidu inline stiilid ei ole küll viisakad, aga sellega demonstreeris tegija oma CSS oskusi, mis on alati teretulnud (näiteks antud ülesandes polnud neid isegi nõutud) – tulemuseks on ilus HTML leht.
Stiilifail 2 ja 3 annavad vastuse XML kujul ja ülesanne on täidetud, kuid jällegi ei saa aru miks ei oleks võinud vastused olla lihtsalt HTML kujul nagu esimese stiilifaili puhul.
XML vastab nii automaatselt kui ka manuaalselt genereeritud skeemifailile ehk ülesanne täidab oma eesmärki. Skeemifaili juures kiidaks meeskonda selle puhul, et nad on lisaks automaatselt genereeritud skeemifailile teinud ka ise skeemifaili.
Kokkuvõtteks võib öelda, et meeskond on oma ülesannetega küll väga hästi hakkama saanud, kuid samas leiame, et nad on teinud palju üleliigset ja ebavajalikku tööd.

Meeskond: "[[BitByBit]]"

=Meeskond „[[V]]“ retsensioon meeskond „KKMK“ teenuse kohta – 4.06.2013=
Meeskons KKMK on teinud WCF teenuse mille eesmärk on pakkuda foorumite haldamise võimekust. Teenuse host osast on eraldatud teenuse meetodite täitevosa. Meetodite realisatsioon on omakorda viidud eraldi repositooriumitesse, nagu autorid neid sisaldavat kausta nimetavad. Membership, Role, Forum jm. päringute jaoks on tehtud eraldi klass, mis muudab nende päringute muutmise ja haldamise tulevikus väga lihtsaks.

Eraldatud päringute klassid on küll hea, kuid mingil põhjusel pole nendest meetoditest tehtud staatilisi meetodeid, seega on nende välja kutsumiseks vaja esmalt luua alati meetodeid sisaldav klass. Autoritel võis selleks mingi põhjus olla, kuid koodist seda otseselt välja ei loe ning see tundub hetkel lihtsalt üleliigse koodina. Eraldatud päringute klassides hakkab ka silma päringu (query) tulemuse kontrollimine „null“´iga võrdlemise meetodil, mitmese (list) tüüpi tulemusega päring ei ole aga kunagi null, mingil põhjusel on aga selline kood sisse jäetud.

Teenuse jaoks on loodud klass nimega „firstQueries“, mis arvatavasti on mõeldud esmase käivitamiseks ehk esimese foorumi ja kasutaja loomiseks. Antud klassist suurem osa on üks try-catch lause, milles veahaldus on lahendatud „huvitavalt“. Igasugune veahaldus on vast siiski positiivne nähtus. Antud esmakäivituse puhul vea tekkimisel, näiteks kasutaja loomisel, on juba eelnevalt foorum ning aplikatsioon juba loodud ning pärast vea kõrvaldamist ei saa enam sama foorumi nime kasutada. Antud juhul oleks võinud ebaõnnestumisel ka eelnevalt andmebaasi loodud andmed kustutada, sest ilma ühe osata ei ole väärtust ka teistel.

Mudelite juures hakkab silma, et enamustel on korduvalt väljad loomise, uuendamise ja kustutamise kuupäevade jaoks, need oleks võinud minu hinnangul eraldi baasklassi viia. Mudelid on meeskond loonud, et kaardistada ümber LinqToSql andmekihist tulevaid klasse. Kuna aines käsitleti ka Entity Framework kood enne lähenemist, siis oodanud, et kasutatakse seda. Kood enne lähenemisel on kerge viia andmebaasi sisse muudatusi mida tihtipeale arenduse käigus tuleb teha, kuid samas võisid meeskonnal andmebaasitabelit olla korralikult läbi mõeldud.

Teenuses on kasutusel ka asp.net´i sisseehitatud kasutajatehaldus ning see põimitud otse foorumi andmeid sisaldavasse baasi. Teenuses puudub võimekus kasutajate päringute logimiseks ning seega ka nende hulga piiramiseks. Samuti ei ole päringud teenuse poolelt kuidagi rollidega piiratud, seega saab reaalselt ligi kõikidele teenuse poolt väljastatud andmetele sõltumata rollist ning ka neid redigeerida ja kustutada.
Kokkuvõttes on foorumite teenuse pakkumise idee majanduslikku perspektiivi omav ning ilmselgelt ka kogukondi kaasav. Teenuse juures on küll asju mida võiks täiustada, kuid tehtud algusest jääb mulje, et asi on läbi mõeldud ning mõninga lisaajaga oleks saavutatud enamatki.

Meeskond "[[V]]"

=Meeskond „[[V]]“ retsensioon meeskond „KKMK“ klientrakenduse kohta – 4.06.2013=
Meeskond on loonud klientrakenduse enda pakutavale Forumite teenusele ning teostanud selle ASP.NET MVC4 baasil. Esmasel klientrakenduse käivitamisel näeme tühja lehte ilma ühegi navigeerimisvõimaluseta, kuid pärast pilku meeskonna wiki kasutusjuhendisse saame teada, et esmasel käivitusel tuleb navigeerida „setup“ lehele. Setup lehele andmete sisestamine tulemus on aga erinevad veateated kuni lõpuks ilmub „Epic Fail“ veateade. Iseenesest on veahalduse tegemine hea asi, kuid esimsele korral saadud veateada „Error when creating the membership“ ei olnud minu hinnangul piisavalt informatiivne. Esmase foorumi lisamine õnnestus siiski lõpuks pärast teenuse poolelt veateadete uurimist, millest tuli välja, et minu sisestatud parool ei vasta nõuetele. Antud klientrakenduses oleks võinud sel kohal olla ka sisendite valideerimine.

Kui foorum edukalt loodud, siis edasine kategooriate, teemade ja postituste lisamine tundus edukalt töötavat. Administraatorina on võimalik mul ka kasutajaid hallata, mis sisaldab nende pehmet kustutamist (kustutamiskuupäeva sättimine) ja profiilide muutmist, uusi kasutajaid ei saa administraator luua. Kasutajate kustutamise järel on võimalik neid ka taastada, kuid katsetamisel selgus, et selleks pole vajadust, sest kasutajaid saavad ka kustutatud olekus sisse logida ja rõõmsalt postitusi teha.(See viga on ühe autori andmetel nüüdseks parandatud 04.06.2013 - 20:50) Kustutamisel aga blokeeritakse kasutaja redigeerimine, seega selle üritamine tagastab „kollase surmaekraani“ koos huvitava informatsiooniga.

Olles ühe foorumi juba infoga täitnud, selle sulgenud ja uue loonud, satutakse olukorda, kus eelmisse foorumisse enam ei pääse ja uude samuti mitte. Olles aadressiribale kustutatud foorumi nime kirjutanud, siis pääseb sellele taas ligi, kuid uuele foorumile ei tundu olevat mingit võimalus administraatori ligipääsu luua. Samas positiivselt küljelt niipalju, et administraatori osa tundub olevat korralikult turvatud, erinevalt kasutajate poolest. Näiteks postitusi saab teha, redigeerida ja kustutatada igaüks, kusjuures igaühe postitusi.

Rakendus vajaks küll veel testimist, kuid esmamulje hindaks siiski heaks. Rakenduse koodi poolelt on teretulnud nähtus, et vaadetesse antakse info ette vaatemudelite kaudu, mitte niinimetatud vaatekotis (viewbag). Mõnes kohas koodis tekkis esmapilgul küsimusi, et milleks just nii ning mida see koodiosa nüüd teeb. Seega oleks lihtsama arusaamise nimel võinud kasutada kommenteerimist, seda enam, et projekt oli teostatud meeskonna peale. Hea on näha, et kohati on kasutatud ka javascripti, ilma milleta tänapäeval veebilehti tehes tihtipeale ei saa.

Kokkuvõtteks on tegemist siiski asjaliku rakendusega, mis täidab esmased ootused ehk foorumi loomine, haldamine ja sellesse postitamine. Eelnevalt olen toonud välja küll vigu, aga nagu meeskond ise oma wiki lehel mainis, siis arenemisruumi on tõesti. Veelgi enam, et vigu leida ja neid välja tuua on kerge, kuid välisel vaatlusel hinnata inimeste panust (loe: valatud verd ja higi) on keeruline.

Meeskond "[[V]]"

Talk:KKMK

2013-06-04T18:01:16Z

Vevainu: /* Meeskond „V“ retsensioon meeskond „KKMK“ klientrakenduse kohta – 4.06.2013 */

Talk:KKMK

2013-06-04T17:57:50Z

Vevainu: /* Meeskond „V“ retsensioon meeskond „KKMK“ klientrakenduse kohta – 4.06.2013 */

V

2013-06-04T16:52:16Z

Vevainu: /* Klientrakendus */

[[Category:Võrgurakendused II: hajussüsteemide ehitamine]]
=Liige=
Veiko Vainu D21
=Retsensioonid=
==XML==
[https://wiki.itcollege.ee/index.php/Talk:Meeskond_%22asdasdasd%22 Retsensioon meeskond „asdasdasd“ XML-i kohta – 24.03.2013]

[https://wiki.itcollege.ee/index.php/Talk:SaanEndagaH%C3%A4stiL%C3%A4bi Retsensioon meeskond „SaanEndagaHästiLäbi“ XML-i kohta – 24.03.2013]
==Teenus==
[https://wiki.itcollege.ee/index.php/Talk:KK_without_K Retsensioon meeskond „KK without K“ teenuse kohta – 3.06.2013]

[https://wiki.itcollege.ee/index.php/Talk:KKMK Retsensioon meeskond „KKMK“ teenuse kohta – 4.06.2013]

==Klientrakendus==
[https://wiki.itcollege.ee/index.php/Talk:KK_without_K Retsensioon meeskond „KK without K“ klientrakenduse kohta – 3.06.2013]

[https://wiki.itcollege.ee/index.php/Talk:KKMK Retsensioon meeskond „KKMK“ klientrakenduse kohta – 4.06.2013]

=XML fail=
==XML andmefail==
*[http://enos.itcollege.ee/~vevainu/XML/armeeXML.xml XML andmefail]

==XML skeemifail==
*[http://enos.itcollege.ee/~vevainu/XML/armeeXML.xsd XML skeemifail]

==XML stiilifailid==
XML to HTML - Kuvab vasakul pool lehte kogu XML-i sisu nn. puuvaates. Paremal pool on otsing, mis otsib sõduri ees- ja perekonnanimest vastavat stringi.
* [http://enos.itcollege.ee/~vevainu/XML/xmlTOhtml.xslt XML to HTML]
* [http://enos.itcollege.ee/~vevainu/XML/xmlTOhtml.xml Näidis]

XML to XML - Trükib välja kõik sõdurid sorteerides perekonnanime ja seejärel eesnime järgi. Igale sõdurile on lisatud ka uus atribuut ID, mis koosneb sõduri ID-st ja tema rühma, allüksuse ja väeosa ID-st.
* [http://enos.itcollege.ee/~vevainu/XML/xmlTOxml.xslt XML to XML]
* [http://enos.itcollege.ee/~vevainu/XML/xmlTOxml.xml Näidis]

XML to Excel - Loob workbooki iga allüksuse jaoks oma worksheeti kuhu kuvatakse selle üksuse isikkooseis sorteeritult Auastme tähestikulises järjekorras.
* [http://enos.itcollege.ee/~vevainu/XML/xmlTOxlsx.xslt XML to Excel]
* [http://enos.itcollege.ee/~vevainu/XML/xmlTOxlsx.xml Näidis XML]
* [http://enos.itcollege.ee/~vevainu/XML/xmlTOxlsxNAIDE.xlsx Näidis EXCEL]
* Kuidas - tuleb xml faili lisada viide vastavale xslt stylesheetile, seejärel tuleb xml fail Excelis avada ja valida, et kasutatakse vastavat stiilifaili.

==XML kõik ühes (.rar)==
*[http://enos.itcollege.ee/~vevainu/XML/XML.rar Kõik failid ühes (.rar)]

=Veebiteenus=

Loodud sai kontaktiraamatu teenus, mis põhineb õppejõu "Telefoniraamatu teenus" näidisteemal.

Teenus on loodud WCF baasil ja kasutab Asp.Net kasutajate autentimist, mille jaoks on vastavad membership- ja roleprovider. Teenus võimaldab ka logimist, mis toimub enne sissetuleva päringu täitmist ning kus kontrollitakse ka kasutaja päringu limiidi ületamist. Teenuse päringud teostatakse Ninject süstimise abil läbi uow (unit-of-work) konteineri, mis omakorda sisaldab repositooriume. Kogu andmekiht on üles ehitatud Entity Framework Code First meetodil.

Teenus pakub järgmisi meetodeid:
* User methods 
** AuthenticateUser - Tries to authenticate the user based on credentials.
*** returns > User object of the user or null if authentication failed.
** GetAuthenticatedMyContact - Gets personal contact object of the querying user.
*** returns > A contact object.
** AddUpdateContact - Add or update contacts infromation.
*** param name="contact" > Contact object to add or update.
*** returns > A contact object with updated fields.
** AddUpdateContactInfo - Add or update contacts contact infromation.
*** param name="contactInfo" > Contact information object to add or update.
*** returns > A contact information object with updated fields.
** AddUpdateContactPicture - Add or update a contacts picture.
***param name="contactId" > Id of the contact to whom we wish to add a picture to or update/replace and existing one.
***param name="picture" > File object of containing the picture we wish to add to a contact.
***returns > A file object with updated fields.
** DeleteContact - Deletes a contact by contact object.
***param name="contact" > Contact object of the contact to delete.
***returns > True if deleteion was successful. False if deletion was unsuccessful.
** DeleteContactById - Deletes a contact by id.
***param name="id" > Id of the contact to delete.
***returns > True if deleteion was successful. False if deletion was unsuccessful.
** DeleteContactInfo - Deletes a contacts contact information by contact information object.
***param name="contact" > ContactInfo object of the contact information to delete.
***returns > True if deleteion was successful. False if deletion was unsuccessful.
** DeleteContactInfoById - Deletes a contacts contact information by contact information id.
***param name="id" > Id of the contact information to delete.
***returns > True if deleteion was successful. False if deletion was unsuccessful.
** GetAllContacts - Gets a list of all contacts of the querying user.
***returns > A list of contact objects.
** GetAllContactInfoTypes - Gets a list of contact information types.
***returns > A list of contactinfotype objects.
** GetAllContactInfoesByContactId - Gets a list of a contacts contact information.
***param name="contactId" > Id of a contact whose contactinformation to retrieve.
***returns > A list of contactinfo objects.
** GetByIdContact - Returns a contacts information.
***param name="id" > Id of the contact whose information to retrieve.
***returns > A contact object
** GetByIdContactPicture - Returns a file object, containing a picture in binary form, of a contact.
***param name="id" > Id of the contact whose picture to retrieve.
***returns > A file object of the contacts picture.
** SearchContactByAny - Searches contacts by name or by contacts information, depending on given input.
***param name="any" > Symbol combination to search by.
***param name="type" > Contact info type name to search by, or all to search by everything.
***returns > A list of contacts matching the search criteria.
** SearchContactByAnyPublic - Searches contacts by name or by contacts information, depending on given input. Also searches publicly available contact (contacts that have IsPublic=True).
***param name="any" > Symbol combination to search by.
***param name="type" > Contact info type name to search by, or all to search by everything.
***returns > A list of contacts matching the search criteria.
* Administrators methods 
** AdminAddUpdateUser - Administrator method, adds or updates a user.
***param name="user" > User object to add or update.
***returns > A user object with updated fields.
** AdminDeleteUser - Administrator method, deletes a user by id. (Sets DeletedOn date to now)
***param name="userId" > Id of the user to delete.
***returns > True if deletion was successful. False if deletion was unsuccessful.
** AdminGetAllUsers - Administrator method, gets a list of all users.
***returns > A list of user objects.
** AdminGetAllUserRoles - Administrator method, gets all possible user roles.
***returns > A list of type user role objects
** AdminGetByIdUser - Administrator method, gets the user object by id.
***param name="userId" > Id of the user whose user data we wish to retrieve.
***returns > A user object.
** AdminGetLogsByUserId - Administrator method, gets a list of logs by user id. Get only the logs from the last 24 hours.
***param name="userId" > Id of the user whose logs to get.
***returns > A list of log objects.

Raskuskohad olid injectimine, nii et ei tekiks konflikte, ning kasutajate päringute hulga ilus piiramine, hetkel lihtsaltkatkestatakse kasutajaga ühendus.

=Klientrakendused=
Klientrakendus on tehtud WPF baasil kasutades peamiselt MVVM (Model-View-ViewModel) lähenemist, mille puhul View kood on enamjaolt tühi. Teenuse kasutamisel igakordse parooli ja kasutajanime sisestamise vältimiseks on teenuse kanali loomine eraldi kapseldatud.

Loodud klientrakendus võimaldab järgnevat:
*Kasutajaid tuvastada
*Kasutajad rolli põhjal eristada ja kuvada erinevaid menüüsid
*Kasutajal kontake lisada ja redigeerida
*Kontaktidele kontaktandmeid lisada ja redigeerida
*Kontaktidele pilte lisada, otse arvutist kui ka veebilinki ette andes
*Kontakte otsida kontakti nime ning kontaktandmete sisu järgi
*Kontakte otsida vaid kindla kontaktandmete tüübi sisu järgi
*Kontakte otsida ka nn. avalike ehk teiste kasutajate kontaktide seast
*Kontaktide määrata avalikuks (teistele nähtav) või mitte-avalikuks
*Administraatoritel lisada ja redigeerida kasutajaid
*Administraatoritel muuta maksimaalsete päringute arvu
*Administraatoritel näha iga kasutaja viimase 24 tunni päringuid (logi)

Raskuskohad olid teenuse asünkroonne kasutamine rakenduses ning võimalike veateadete haldamine.
=Klientrakenduse ja teenuse kasutamine=
Klientrakendus ja teenus asuvad koos [http://enos.itcollege.ee/~vevainu/TeenusJaKlient.rar SIIN]

Et teenus suudaks kliendiga suhelda tuleb luua sertifikaadid ja nende "Thumbprint" kood asendada vastavalt "ServiceHost" ja "ServiceClientWPF" konfiguratsioonifailides, vastavalt "Web.config" ja "App.config". Õpetus kuidas sertifikaate luua ja nende "Thumbprint" leida on õppejõu poolt jagatud videos [http://echo360.e-uni.ee/ess/echo/presentation/75e01210-2016-44a5-a48a-8a861c1b9799 SIIN]

Hetkel on "ServiceHost" seadistatud kasutama internetist kättesaadavat andmebaasi, kui soovite selle lokaalse vastu vahetada tuleb muuta "ContactBookConnection" nimeline connectionstring.

Kui on soovi kasutada omaenda kohalikku andmebaasi, siis saab EF andmebaasi loomiseks ja testandmete sisestamiseks kasutada "DALTestConsole" programmijuppi, kus tuleb siis asendada "ContactBookConnection" nimeline connectionstring. Et testandmeid suudetaks sisestada tuleb teha järgmist:
*DAL>ContactBookContext.cs - välja kommenteerida "this.Configuration.ProxyCreationEnabled = false;"
*Models>aBaseHistory.cs - sisse kommenteerida konstruktor, kus väärtustatakse kuupäeva väljad
*DAL>User-/Contact-/ContactInfoRepository - Välja kommenteerida "Add" ja "Update" meetodid
Pärast testandmete genereerimist tuleks muudatused tagasi keerata (Undo!)

=Logi=
*2013.03.13 – Sai paika pandud XML faili struktuur ja loodud seda genereeriv rakendus.
*2013.03.14 – XSLT faili loomine, lisatud „Puuvaade“ näitamaks kõiki sisendeid.
*2013.03.15 – XSLT failile inimeste otsing vastavalt kasutaja sisendile lisatud (ainult IE). Sai tehtud XSLT fail XML-i transformeerimiseks teistsuguseks XML-iks ja ka XSLT fail XML-i exceli vorminduse jaoks.
*2013.03.20 – XML to HTML otsing töötab nüüd IE, Chrome ja Firefoxiga
**wiki leht loodud,XML wiki lehele lisatud, tehtud stiilifailide näidised
*2013.03.24 – Teiste tiimide XML tööde retsenseerimine
*2013.04.25 – Alustatud teenuse loomist.
** Teenusele lisatud autentimine.
** Esialgsed mudelid ja DAL (Data-Access-Layer) loodud.
*2013.04.26 – Repositooriumite loomine ja baasrepositooriumi täitmine.
** Esialgsete testandmete automaatsisestamise loomine.
*2013.04.27 – Autentimine üle viidud isevalmistatud membership- ja role providerite peale.
** Alustatud teenuse meetodite kirjapanemisega.
*2013.04.28 – DI (Dependency-Injection) kasutusele võtmine.
** Esimesed teenuse meetodid kirja pandud.
*2013.05.02 – Tavakasutajatele mõeldud meetodid kirja pandud, alustatud administraatori meetoditega.
*2013.05.04 – Alustatud klientrakenduse loomist. Valmis navigeerimine ja käskluste põhi.
*2013.05.07 – Klientrakenduses valmis kõikide kontaktide kuvamise vaade. Teenusele lisatud piltide/failide lisamise/pärimise võimalus.
*2013.05.12 – WCF asünkroonsed meetodid asendatud asünkroonsete tööde klientrakenduse poolel.
*2013.05.13 – Otsimise võimalus lisatud.
**Administraatori vaade (kasutajate haldus) klientrakendusele lisatud.
**Logimine andmebaasi lisatud.
**Logimise põhjal päringute arvu piirangud lisatud.
*2013.05.15 – Klientrakendusele üldine veahalduse lisatud.
*2013.05.16 – Teenuse meetodid kommenteeritud.
**Teenuse ja klientrakenduse kohta käiv info Wikisse lisatud.
**Selle logi kirjutamine...

V

2013-06-04T16:51:53Z

Vevainu: /* Teenus */

[[Category:Võrgurakendused II: hajussüsteemide ehitamine]]
=Liige=
Veiko Vainu D21
=Retsensioonid=
==XML==
[https://wiki.itcollege.ee/index.php/Talk:Meeskond_%22asdasdasd%22 Retsensioon meeskond „asdasdasd“ XML-i kohta – 24.03.2013]

[https://wiki.itcollege.ee/index.php/Talk:SaanEndagaH%C3%A4stiL%C3%A4bi Retsensioon meeskond „SaanEndagaHästiLäbi“ XML-i kohta – 24.03.2013]
==Teenus==
[https://wiki.itcollege.ee/index.php/Talk:KK_without_K Retsensioon meeskond „KK without K“ teenuse kohta – 3.06.2013]

[https://wiki.itcollege.ee/index.php/Talk:KKMK Retsensioon meeskond „KKMK“ teenuse kohta – 4.06.2013]

==Klientrakendus==
[https://wiki.itcollege.ee/index.php/Talk:KK_without_K Retsensioon meeskond „KK without K“ klientrakenduse kohta – 3.06.2013]

=XML fail=
==XML andmefail==
*[http://enos.itcollege.ee/~vevainu/XML/armeeXML.xml XML andmefail]

==XML skeemifail==
*[http://enos.itcollege.ee/~vevainu/XML/armeeXML.xsd XML skeemifail]

==XML stiilifailid==
XML to HTML - Kuvab vasakul pool lehte kogu XML-i sisu nn. puuvaates. Paremal pool on otsing, mis otsib sõduri ees- ja perekonnanimest vastavat stringi.
* [http://enos.itcollege.ee/~vevainu/XML/xmlTOhtml.xslt XML to HTML]
* [http://enos.itcollege.ee/~vevainu/XML/xmlTOhtml.xml Näidis]

XML to XML - Trükib välja kõik sõdurid sorteerides perekonnanime ja seejärel eesnime järgi. Igale sõdurile on lisatud ka uus atribuut ID, mis koosneb sõduri ID-st ja tema rühma, allüksuse ja väeosa ID-st.
* [http://enos.itcollege.ee/~vevainu/XML/xmlTOxml.xslt XML to XML]
* [http://enos.itcollege.ee/~vevainu/XML/xmlTOxml.xml Näidis]

XML to Excel - Loob workbooki iga allüksuse jaoks oma worksheeti kuhu kuvatakse selle üksuse isikkooseis sorteeritult Auastme tähestikulises järjekorras.
* [http://enos.itcollege.ee/~vevainu/XML/xmlTOxlsx.xslt XML to Excel]
* [http://enos.itcollege.ee/~vevainu/XML/xmlTOxlsx.xml Näidis XML]
* [http://enos.itcollege.ee/~vevainu/XML/xmlTOxlsxNAIDE.xlsx Näidis EXCEL]
* Kuidas - tuleb xml faili lisada viide vastavale xslt stylesheetile, seejärel tuleb xml fail Excelis avada ja valida, et kasutatakse vastavat stiilifaili.

==XML kõik ühes (.rar)==
*[http://enos.itcollege.ee/~vevainu/XML/XML.rar Kõik failid ühes (.rar)]

=Veebiteenus=

Loodud sai kontaktiraamatu teenus, mis põhineb õppejõu "Telefoniraamatu teenus" näidisteemal.

Teenus on loodud WCF baasil ja kasutab Asp.Net kasutajate autentimist, mille jaoks on vastavad membership- ja roleprovider. Teenus võimaldab ka logimist, mis toimub enne sissetuleva päringu täitmist ning kus kontrollitakse ka kasutaja päringu limiidi ületamist. Teenuse päringud teostatakse Ninject süstimise abil läbi uow (unit-of-work) konteineri, mis omakorda sisaldab repositooriume. Kogu andmekiht on üles ehitatud Entity Framework Code First meetodil.

Teenus pakub järgmisi meetodeid:
* User methods 
** AuthenticateUser - Tries to authenticate the user based on credentials.
*** returns > User object of the user or null if authentication failed.
** GetAuthenticatedMyContact - Gets personal contact object of the querying user.
*** returns > A contact object.
** AddUpdateContact - Add or update contacts infromation.
*** param name="contact" > Contact object to add or update.
*** returns > A contact object with updated fields.
** AddUpdateContactInfo - Add or update contacts contact infromation.
*** param name="contactInfo" > Contact information object to add or update.
*** returns > A contact information object with updated fields.
** AddUpdateContactPicture - Add or update a contacts picture.
***param name="contactId" > Id of the contact to whom we wish to add a picture to or update/replace and existing one.
***param name="picture" > File object of containing the picture we wish to add to a contact.
***returns > A file object with updated fields.
** DeleteContact - Deletes a contact by contact object.
***param name="contact" > Contact object of the contact to delete.
***returns > True if deleteion was successful. False if deletion was unsuccessful.
** DeleteContactById - Deletes a contact by id.
***param name="id" > Id of the contact to delete.
***returns > True if deleteion was successful. False if deletion was unsuccessful.
** DeleteContactInfo - Deletes a contacts contact information by contact information object.
***param name="contact" > ContactInfo object of the contact information to delete.
***returns > True if deleteion was successful. False if deletion was unsuccessful.
** DeleteContactInfoById - Deletes a contacts contact information by contact information id.
***param name="id" > Id of the contact information to delete.
***returns > True if deleteion was successful. False if deletion was unsuccessful.
** GetAllContacts - Gets a list of all contacts of the querying user.
***returns > A list of contact objects.
** GetAllContactInfoTypes - Gets a list of contact information types.
***returns > A list of contactinfotype objects.
** GetAllContactInfoesByContactId - Gets a list of a contacts contact information.
***param name="contactId" > Id of a contact whose contactinformation to retrieve.
***returns > A list of contactinfo objects.
** GetByIdContact - Returns a contacts information.
***param name="id" > Id of the contact whose information to retrieve.
***returns > A contact object
** GetByIdContactPicture - Returns a file object, containing a picture in binary form, of a contact.
***param name="id" > Id of the contact whose picture to retrieve.
***returns > A file object of the contacts picture.
** SearchContactByAny - Searches contacts by name or by contacts information, depending on given input.
***param name="any" > Symbol combination to search by.
***param name="type" > Contact info type name to search by, or all to search by everything.
***returns > A list of contacts matching the search criteria.
** SearchContactByAnyPublic - Searches contacts by name or by contacts information, depending on given input. Also searches publicly available contact (contacts that have IsPublic=True).
***param name="any" > Symbol combination to search by.
***param name="type" > Contact info type name to search by, or all to search by everything.
***returns > A list of contacts matching the search criteria.
* Administrators methods 
** AdminAddUpdateUser - Administrator method, adds or updates a user.
***param name="user" > User object to add or update.
***returns > A user object with updated fields.
** AdminDeleteUser - Administrator method, deletes a user by id. (Sets DeletedOn date to now)
***param name="userId" > Id of the user to delete.
***returns > True if deletion was successful. False if deletion was unsuccessful.
** AdminGetAllUsers - Administrator method, gets a list of all users.
***returns > A list of user objects.
** AdminGetAllUserRoles - Administrator method, gets all possible user roles.
***returns > A list of type user role objects
** AdminGetByIdUser - Administrator method, gets the user object by id.
***param name="userId" > Id of the user whose user data we wish to retrieve.
***returns > A user object.
** AdminGetLogsByUserId - Administrator method, gets a list of logs by user id. Get only the logs from the last 24 hours.
***param name="userId" > Id of the user whose logs to get.
***returns > A list of log objects.

Raskuskohad olid injectimine, nii et ei tekiks konflikte, ning kasutajate päringute hulga ilus piiramine, hetkel lihtsaltkatkestatakse kasutajaga ühendus.

=Klientrakendused=
Klientrakendus on tehtud WPF baasil kasutades peamiselt MVVM (Model-View-ViewModel) lähenemist, mille puhul View kood on enamjaolt tühi. Teenuse kasutamisel igakordse parooli ja kasutajanime sisestamise vältimiseks on teenuse kanali loomine eraldi kapseldatud.

Loodud klientrakendus võimaldab järgnevat:
*Kasutajaid tuvastada
*Kasutajad rolli põhjal eristada ja kuvada erinevaid menüüsid
*Kasutajal kontake lisada ja redigeerida
*Kontaktidele kontaktandmeid lisada ja redigeerida
*Kontaktidele pilte lisada, otse arvutist kui ka veebilinki ette andes
*Kontakte otsida kontakti nime ning kontaktandmete sisu järgi
*Kontakte otsida vaid kindla kontaktandmete tüübi sisu järgi
*Kontakte otsida ka nn. avalike ehk teiste kasutajate kontaktide seast
*Kontaktide määrata avalikuks (teistele nähtav) või mitte-avalikuks
*Administraatoritel lisada ja redigeerida kasutajaid
*Administraatoritel muuta maksimaalsete päringute arvu
*Administraatoritel näha iga kasutaja viimase 24 tunni päringuid (logi)

Raskuskohad olid teenuse asünkroonne kasutamine rakenduses ning võimalike veateadete haldamine.
=Klientrakenduse ja teenuse kasutamine=
Klientrakendus ja teenus asuvad koos [http://enos.itcollege.ee/~vevainu/TeenusJaKlient.rar SIIN]

Et teenus suudaks kliendiga suhelda tuleb luua sertifikaadid ja nende "Thumbprint" kood asendada vastavalt "ServiceHost" ja "ServiceClientWPF" konfiguratsioonifailides, vastavalt "Web.config" ja "App.config". Õpetus kuidas sertifikaate luua ja nende "Thumbprint" leida on õppejõu poolt jagatud videos [http://echo360.e-uni.ee/ess/echo/presentation/75e01210-2016-44a5-a48a-8a861c1b9799 SIIN]

Hetkel on "ServiceHost" seadistatud kasutama internetist kättesaadavat andmebaasi, kui soovite selle lokaalse vastu vahetada tuleb muuta "ContactBookConnection" nimeline connectionstring.

Kui on soovi kasutada omaenda kohalikku andmebaasi, siis saab EF andmebaasi loomiseks ja testandmete sisestamiseks kasutada "DALTestConsole" programmijuppi, kus tuleb siis asendada "ContactBookConnection" nimeline connectionstring. Et testandmeid suudetaks sisestada tuleb teha järgmist:
*DAL>ContactBookContext.cs - välja kommenteerida "this.Configuration.ProxyCreationEnabled = false;"
*Models>aBaseHistory.cs - sisse kommenteerida konstruktor, kus väärtustatakse kuupäeva väljad
*DAL>User-/Contact-/ContactInfoRepository - Välja kommenteerida "Add" ja "Update" meetodid
Pärast testandmete genereerimist tuleks muudatused tagasi keerata (Undo!)

=Logi=
*2013.03.13 – Sai paika pandud XML faili struktuur ja loodud seda genereeriv rakendus.
*2013.03.14 – XSLT faili loomine, lisatud „Puuvaade“ näitamaks kõiki sisendeid.
*2013.03.15 – XSLT failile inimeste otsing vastavalt kasutaja sisendile lisatud (ainult IE). Sai tehtud XSLT fail XML-i transformeerimiseks teistsuguseks XML-iks ja ka XSLT fail XML-i exceli vorminduse jaoks.
*2013.03.20 – XML to HTML otsing töötab nüüd IE, Chrome ja Firefoxiga
**wiki leht loodud,XML wiki lehele lisatud, tehtud stiilifailide näidised
*2013.03.24 – Teiste tiimide XML tööde retsenseerimine
*2013.04.25 – Alustatud teenuse loomist.
** Teenusele lisatud autentimine.
** Esialgsed mudelid ja DAL (Data-Access-Layer) loodud.
*2013.04.26 – Repositooriumite loomine ja baasrepositooriumi täitmine.
** Esialgsete testandmete automaatsisestamise loomine.
*2013.04.27 – Autentimine üle viidud isevalmistatud membership- ja role providerite peale.
** Alustatud teenuse meetodite kirjapanemisega.
*2013.04.28 – DI (Dependency-Injection) kasutusele võtmine.
** Esimesed teenuse meetodid kirja pandud.
*2013.05.02 – Tavakasutajatele mõeldud meetodid kirja pandud, alustatud administraatori meetoditega.
*2013.05.04 – Alustatud klientrakenduse loomist. Valmis navigeerimine ja käskluste põhi.
*2013.05.07 – Klientrakenduses valmis kõikide kontaktide kuvamise vaade. Teenusele lisatud piltide/failide lisamise/pärimise võimalus.
*2013.05.12 – WCF asünkroonsed meetodid asendatud asünkroonsete tööde klientrakenduse poolel.
*2013.05.13 – Otsimise võimalus lisatud.
**Administraatori vaade (kasutajate haldus) klientrakendusele lisatud.
**Logimine andmebaasi lisatud.
**Logimise põhjal päringute arvu piirangud lisatud.
*2013.05.15 – Klientrakendusele üldine veahalduse lisatud.
*2013.05.16 – Teenuse meetodid kommenteeritud.
**Teenuse ja klientrakenduse kohta käiv info Wikisse lisatud.
**Selle logi kirjutamine...

V

2013-06-04T16:51:47Z

Vevainu: /* Teenus */

[[Category:Võrgurakendused II: hajussüsteemide ehitamine]]
=Liige=
Veiko Vainu D21
=Retsensioonid=
==XML==
[https://wiki.itcollege.ee/index.php/Talk:Meeskond_%22asdasdasd%22 Retsensioon meeskond „asdasdasd“ XML-i kohta – 24.03.2013]

[https://wiki.itcollege.ee/index.php/Talk:SaanEndagaH%C3%A4stiL%C3%A4bi Retsensioon meeskond „SaanEndagaHästiLäbi“ XML-i kohta – 24.03.2013]
==Teenus==
[https://wiki.itcollege.ee/index.php/Talk:KK_without_K Retsensioon meeskond „KK without K“ teenuse kohta – 3.06.2013]
[https://wiki.itcollege.ee/index.php/Talk:KKMK Retsensioon meeskond „KKMK“ teenuse kohta – 4.06.2013]

==Klientrakendus==
[https://wiki.itcollege.ee/index.php/Talk:KK_without_K Retsensioon meeskond „KK without K“ klientrakenduse kohta – 3.06.2013]

=XML fail=
==XML andmefail==
*[http://enos.itcollege.ee/~vevainu/XML/armeeXML.xml XML andmefail]

==XML skeemifail==
*[http://enos.itcollege.ee/~vevainu/XML/armeeXML.xsd XML skeemifail]

==XML stiilifailid==
XML to HTML - Kuvab vasakul pool lehte kogu XML-i sisu nn. puuvaates. Paremal pool on otsing, mis otsib sõduri ees- ja perekonnanimest vastavat stringi.
* [http://enos.itcollege.ee/~vevainu/XML/xmlTOhtml.xslt XML to HTML]
* [http://enos.itcollege.ee/~vevainu/XML/xmlTOhtml.xml Näidis]

XML to XML - Trükib välja kõik sõdurid sorteerides perekonnanime ja seejärel eesnime järgi. Igale sõdurile on lisatud ka uus atribuut ID, mis koosneb sõduri ID-st ja tema rühma, allüksuse ja väeosa ID-st.
* [http://enos.itcollege.ee/~vevainu/XML/xmlTOxml.xslt XML to XML]
* [http://enos.itcollege.ee/~vevainu/XML/xmlTOxml.xml Näidis]

XML to Excel - Loob workbooki iga allüksuse jaoks oma worksheeti kuhu kuvatakse selle üksuse isikkooseis sorteeritult Auastme tähestikulises järjekorras.
* [http://enos.itcollege.ee/~vevainu/XML/xmlTOxlsx.xslt XML to Excel]
* [http://enos.itcollege.ee/~vevainu/XML/xmlTOxlsx.xml Näidis XML]
* [http://enos.itcollege.ee/~vevainu/XML/xmlTOxlsxNAIDE.xlsx Näidis EXCEL]
* Kuidas - tuleb xml faili lisada viide vastavale xslt stylesheetile, seejärel tuleb xml fail Excelis avada ja valida, et kasutatakse vastavat stiilifaili.

==XML kõik ühes (.rar)==
*[http://enos.itcollege.ee/~vevainu/XML/XML.rar Kõik failid ühes (.rar)]

=Veebiteenus=

Loodud sai kontaktiraamatu teenus, mis põhineb õppejõu "Telefoniraamatu teenus" näidisteemal.

Teenus on loodud WCF baasil ja kasutab Asp.Net kasutajate autentimist, mille jaoks on vastavad membership- ja roleprovider. Teenus võimaldab ka logimist, mis toimub enne sissetuleva päringu täitmist ning kus kontrollitakse ka kasutaja päringu limiidi ületamist. Teenuse päringud teostatakse Ninject süstimise abil läbi uow (unit-of-work) konteineri, mis omakorda sisaldab repositooriume. Kogu andmekiht on üles ehitatud Entity Framework Code First meetodil.

Teenus pakub järgmisi meetodeid:
* User methods 
** AuthenticateUser - Tries to authenticate the user based on credentials.
*** returns > User object of the user or null if authentication failed.
** GetAuthenticatedMyContact - Gets personal contact object of the querying user.
*** returns > A contact object.
** AddUpdateContact - Add or update contacts infromation.
*** param name="contact" > Contact object to add or update.
*** returns > A contact object with updated fields.
** AddUpdateContactInfo - Add or update contacts contact infromation.
*** param name="contactInfo" > Contact information object to add or update.
*** returns > A contact information object with updated fields.
** AddUpdateContactPicture - Add or update a contacts picture.
***param name="contactId" > Id of the contact to whom we wish to add a picture to or update/replace and existing one.
***param name="picture" > File object of containing the picture we wish to add to a contact.
***returns > A file object with updated fields.
** DeleteContact - Deletes a contact by contact object.
***param name="contact" > Contact object of the contact to delete.
***returns > True if deleteion was successful. False if deletion was unsuccessful.
** DeleteContactById - Deletes a contact by id.
***param name="id" > Id of the contact to delete.
***returns > True if deleteion was successful. False if deletion was unsuccessful.
** DeleteContactInfo - Deletes a contacts contact information by contact information object.
***param name="contact" > ContactInfo object of the contact information to delete.
***returns > True if deleteion was successful. False if deletion was unsuccessful.
** DeleteContactInfoById - Deletes a contacts contact information by contact information id.
***param name="id" > Id of the contact information to delete.
***returns > True if deleteion was successful. False if deletion was unsuccessful.
** GetAllContacts - Gets a list of all contacts of the querying user.
***returns > A list of contact objects.
** GetAllContactInfoTypes - Gets a list of contact information types.
***returns > A list of contactinfotype objects.
** GetAllContactInfoesByContactId - Gets a list of a contacts contact information.
***param name="contactId" > Id of a contact whose contactinformation to retrieve.
***returns > A list of contactinfo objects.
** GetByIdContact - Returns a contacts information.
***param name="id" > Id of the contact whose information to retrieve.
***returns > A contact object
** GetByIdContactPicture - Returns a file object, containing a picture in binary form, of a contact.
***param name="id" > Id of the contact whose picture to retrieve.
***returns > A file object of the contacts picture.
** SearchContactByAny - Searches contacts by name or by contacts information, depending on given input.
***param name="any" > Symbol combination to search by.
***param name="type" > Contact info type name to search by, or all to search by everything.
***returns > A list of contacts matching the search criteria.
** SearchContactByAnyPublic - Searches contacts by name or by contacts information, depending on given input. Also searches publicly available contact (contacts that have IsPublic=True).
***param name="any" > Symbol combination to search by.
***param name="type" > Contact info type name to search by, or all to search by everything.
***returns > A list of contacts matching the search criteria.
* Administrators methods 
** AdminAddUpdateUser - Administrator method, adds or updates a user.
***param name="user" > User object to add or update.
***returns > A user object with updated fields.
** AdminDeleteUser - Administrator method, deletes a user by id. (Sets DeletedOn date to now)
***param name="userId" > Id of the user to delete.
***returns > True if deletion was successful. False if deletion was unsuccessful.
** AdminGetAllUsers - Administrator method, gets a list of all users.
***returns > A list of user objects.
** AdminGetAllUserRoles - Administrator method, gets all possible user roles.
***returns > A list of type user role objects
** AdminGetByIdUser - Administrator method, gets the user object by id.
***param name="userId" > Id of the user whose user data we wish to retrieve.
***returns > A user object.
** AdminGetLogsByUserId - Administrator method, gets a list of logs by user id. Get only the logs from the last 24 hours.
***param name="userId" > Id of the user whose logs to get.
***returns > A list of log objects.

Raskuskohad olid injectimine, nii et ei tekiks konflikte, ning kasutajate päringute hulga ilus piiramine, hetkel lihtsaltkatkestatakse kasutajaga ühendus.

=Klientrakendused=
Klientrakendus on tehtud WPF baasil kasutades peamiselt MVVM (Model-View-ViewModel) lähenemist, mille puhul View kood on enamjaolt tühi. Teenuse kasutamisel igakordse parooli ja kasutajanime sisestamise vältimiseks on teenuse kanali loomine eraldi kapseldatud.

Loodud klientrakendus võimaldab järgnevat:
*Kasutajaid tuvastada
*Kasutajad rolli põhjal eristada ja kuvada erinevaid menüüsid
*Kasutajal kontake lisada ja redigeerida
*Kontaktidele kontaktandmeid lisada ja redigeerida
*Kontaktidele pilte lisada, otse arvutist kui ka veebilinki ette andes
*Kontakte otsida kontakti nime ning kontaktandmete sisu järgi
*Kontakte otsida vaid kindla kontaktandmete tüübi sisu järgi
*Kontakte otsida ka nn. avalike ehk teiste kasutajate kontaktide seast
*Kontaktide määrata avalikuks (teistele nähtav) või mitte-avalikuks
*Administraatoritel lisada ja redigeerida kasutajaid
*Administraatoritel muuta maksimaalsete päringute arvu
*Administraatoritel näha iga kasutaja viimase 24 tunni päringuid (logi)

Raskuskohad olid teenuse asünkroonne kasutamine rakenduses ning võimalike veateadete haldamine.
=Klientrakenduse ja teenuse kasutamine=
Klientrakendus ja teenus asuvad koos [http://enos.itcollege.ee/~vevainu/TeenusJaKlient.rar SIIN]

Et teenus suudaks kliendiga suhelda tuleb luua sertifikaadid ja nende "Thumbprint" kood asendada vastavalt "ServiceHost" ja "ServiceClientWPF" konfiguratsioonifailides, vastavalt "Web.config" ja "App.config". Õpetus kuidas sertifikaate luua ja nende "Thumbprint" leida on õppejõu poolt jagatud videos [http://echo360.e-uni.ee/ess/echo/presentation/75e01210-2016-44a5-a48a-8a861c1b9799 SIIN]

Hetkel on "ServiceHost" seadistatud kasutama internetist kättesaadavat andmebaasi, kui soovite selle lokaalse vastu vahetada tuleb muuta "ContactBookConnection" nimeline connectionstring.

Kui on soovi kasutada omaenda kohalikku andmebaasi, siis saab EF andmebaasi loomiseks ja testandmete sisestamiseks kasutada "DALTestConsole" programmijuppi, kus tuleb siis asendada "ContactBookConnection" nimeline connectionstring. Et testandmeid suudetaks sisestada tuleb teha järgmist:
*DAL>ContactBookContext.cs - välja kommenteerida "this.Configuration.ProxyCreationEnabled = false;"
*Models>aBaseHistory.cs - sisse kommenteerida konstruktor, kus väärtustatakse kuupäeva väljad
*DAL>User-/Contact-/ContactInfoRepository - Välja kommenteerida "Add" ja "Update" meetodid
Pärast testandmete genereerimist tuleks muudatused tagasi keerata (Undo!)

=Logi=
*2013.03.13 – Sai paika pandud XML faili struktuur ja loodud seda genereeriv rakendus.
*2013.03.14 – XSLT faili loomine, lisatud „Puuvaade“ näitamaks kõiki sisendeid.
*2013.03.15 – XSLT failile inimeste otsing vastavalt kasutaja sisendile lisatud (ainult IE). Sai tehtud XSLT fail XML-i transformeerimiseks teistsuguseks XML-iks ja ka XSLT fail XML-i exceli vorminduse jaoks.
*2013.03.20 – XML to HTML otsing töötab nüüd IE, Chrome ja Firefoxiga
**wiki leht loodud,XML wiki lehele lisatud, tehtud stiilifailide näidised
*2013.03.24 – Teiste tiimide XML tööde retsenseerimine
*2013.04.25 – Alustatud teenuse loomist.
** Teenusele lisatud autentimine.
** Esialgsed mudelid ja DAL (Data-Access-Layer) loodud.
*2013.04.26 – Repositooriumite loomine ja baasrepositooriumi täitmine.
** Esialgsete testandmete automaatsisestamise loomine.
*2013.04.27 – Autentimine üle viidud isevalmistatud membership- ja role providerite peale.
** Alustatud teenuse meetodite kirjapanemisega.
*2013.04.28 – DI (Dependency-Injection) kasutusele võtmine.
** Esimesed teenuse meetodid kirja pandud.
*2013.05.02 – Tavakasutajatele mõeldud meetodid kirja pandud, alustatud administraatori meetoditega.
*2013.05.04 – Alustatud klientrakenduse loomist. Valmis navigeerimine ja käskluste põhi.
*2013.05.07 – Klientrakenduses valmis kõikide kontaktide kuvamise vaade. Teenusele lisatud piltide/failide lisamise/pärimise võimalus.
*2013.05.12 – WCF asünkroonsed meetodid asendatud asünkroonsete tööde klientrakenduse poolel.
*2013.05.13 – Otsimise võimalus lisatud.
**Administraatori vaade (kasutajate haldus) klientrakendusele lisatud.
**Logimine andmebaasi lisatud.
**Logimise põhjal päringute arvu piirangud lisatud.
*2013.05.15 – Klientrakendusele üldine veahalduse lisatud.
*2013.05.16 – Teenuse meetodid kommenteeritud.
**Teenuse ja klientrakenduse kohta käiv info Wikisse lisatud.
**Selle logi kirjutamine...

Talk:KKMK

2013-06-04T16:51:08Z

Vevainu:

V

2013-06-03T10:17:59Z

Vevainu: /* XML */

[[Category:Võrgurakendused II: hajussüsteemide ehitamine]]
=Liige=
Veiko Vainu D21
=Retsensioonid=
==XML==
[https://wiki.itcollege.ee/index.php/Talk:Meeskond_%22asdasdasd%22 Retsensioon meeskond „asdasdasd“ XML-i kohta – 24.03.2013]

[https://wiki.itcollege.ee/index.php/Talk:SaanEndagaH%C3%A4stiL%C3%A4bi Retsensioon meeskond „SaanEndagaHästiLäbi“ XML-i kohta – 24.03.2013]
==Teenus==
[https://wiki.itcollege.ee/index.php/Talk:KK_without_K Retsensioon meeskond „KK without K“ teenuse kohta – 3.06.2013]
==Klientrakendus==
[https://wiki.itcollege.ee/index.php/Talk:KK_without_K Retsensioon meeskond „KK without K“ klientrakenduse kohta – 3.06.2013]

=XML fail=
==XML andmefail==
*[http://enos.itcollege.ee/~vevainu/XML/armeeXML.xml XML andmefail]

==XML skeemifail==
*[http://enos.itcollege.ee/~vevainu/XML/armeeXML.xsd XML skeemifail]

==XML stiilifailid==
XML to HTML - Kuvab vasakul pool lehte kogu XML-i sisu nn. puuvaates. Paremal pool on otsing, mis otsib sõduri ees- ja perekonnanimest vastavat stringi.
* [http://enos.itcollege.ee/~vevainu/XML/xmlTOhtml.xslt XML to HTML]
* [http://enos.itcollege.ee/~vevainu/XML/xmlTOhtml.xml Näidis]

XML to XML - Trükib välja kõik sõdurid sorteerides perekonnanime ja seejärel eesnime järgi. Igale sõdurile on lisatud ka uus atribuut ID, mis koosneb sõduri ID-st ja tema rühma, allüksuse ja väeosa ID-st.
* [http://enos.itcollege.ee/~vevainu/XML/xmlTOxml.xslt XML to XML]
* [http://enos.itcollege.ee/~vevainu/XML/xmlTOxml.xml Näidis]

XML to Excel - Loob workbooki iga allüksuse jaoks oma worksheeti kuhu kuvatakse selle üksuse isikkooseis sorteeritult Auastme tähestikulises järjekorras.
* [http://enos.itcollege.ee/~vevainu/XML/xmlTOxlsx.xslt XML to Excel]
* [http://enos.itcollege.ee/~vevainu/XML/xmlTOxlsx.xml Näidis XML]
* [http://enos.itcollege.ee/~vevainu/XML/xmlTOxlsxNAIDE.xlsx Näidis EXCEL]
* Kuidas - tuleb xml faili lisada viide vastavale xslt stylesheetile, seejärel tuleb xml fail Excelis avada ja valida, et kasutatakse vastavat stiilifaili.

==XML kõik ühes (.rar)==
*[http://enos.itcollege.ee/~vevainu/XML/XML.rar Kõik failid ühes (.rar)]

=Veebiteenus=

Loodud sai kontaktiraamatu teenus, mis põhineb õppejõu "Telefoniraamatu teenus" näidisteemal.

Teenus on loodud WCF baasil ja kasutab Asp.Net kasutajate autentimist, mille jaoks on vastavad membership- ja roleprovider. Teenus võimaldab ka logimist, mis toimub enne sissetuleva päringu täitmist ning kus kontrollitakse ka kasutaja päringu limiidi ületamist. Teenuse päringud teostatakse Ninject süstimise abil läbi uow (unit-of-work) konteineri, mis omakorda sisaldab repositooriume. Kogu andmekiht on üles ehitatud Entity Framework Code First meetodil.

Teenus pakub järgmisi meetodeid:
* User methods 
** AuthenticateUser - Tries to authenticate the user based on credentials.
*** returns > User object of the user or null if authentication failed.
** GetAuthenticatedMyContact - Gets personal contact object of the querying user.
*** returns > A contact object.
** AddUpdateContact - Add or update contacts infromation.
*** param name="contact" > Contact object to add or update.
*** returns > A contact object with updated fields.
** AddUpdateContactInfo - Add or update contacts contact infromation.
*** param name="contactInfo" > Contact information object to add or update.
*** returns > A contact information object with updated fields.
** AddUpdateContactPicture - Add or update a contacts picture.
***param name="contactId" > Id of the contact to whom we wish to add a picture to or update/replace and existing one.
***param name="picture" > File object of containing the picture we wish to add to a contact.
***returns > A file object with updated fields.
** DeleteContact - Deletes a contact by contact object.
***param name="contact" > Contact object of the contact to delete.
***returns > True if deleteion was successful. False if deletion was unsuccessful.
** DeleteContactById - Deletes a contact by id.
***param name="id" > Id of the contact to delete.
***returns > True if deleteion was successful. False if deletion was unsuccessful.
** DeleteContactInfo - Deletes a contacts contact information by contact information object.
***param name="contact" > ContactInfo object of the contact information to delete.
***returns > True if deleteion was successful. False if deletion was unsuccessful.
** DeleteContactInfoById - Deletes a contacts contact information by contact information id.
***param name="id" > Id of the contact information to delete.
***returns > True if deleteion was successful. False if deletion was unsuccessful.
** GetAllContacts - Gets a list of all contacts of the querying user.
***returns > A list of contact objects.
** GetAllContactInfoTypes - Gets a list of contact information types.
***returns > A list of contactinfotype objects.
** GetAllContactInfoesByContactId - Gets a list of a contacts contact information.
***param name="contactId" > Id of a contact whose contactinformation to retrieve.
***returns > A list of contactinfo objects.
** GetByIdContact - Returns a contacts information.
***param name="id" > Id of the contact whose information to retrieve.
***returns > A contact object
** GetByIdContactPicture - Returns a file object, containing a picture in binary form, of a contact.
***param name="id" > Id of the contact whose picture to retrieve.
***returns > A file object of the contacts picture.
** SearchContactByAny - Searches contacts by name or by contacts information, depending on given input.
***param name="any" > Symbol combination to search by.
***param name="type" > Contact info type name to search by, or all to search by everything.
***returns > A list of contacts matching the search criteria.
** SearchContactByAnyPublic - Searches contacts by name or by contacts information, depending on given input. Also searches publicly available contact (contacts that have IsPublic=True).
***param name="any" > Symbol combination to search by.
***param name="type" > Contact info type name to search by, or all to search by everything.
***returns > A list of contacts matching the search criteria.
* Administrators methods 
** AdminAddUpdateUser - Administrator method, adds or updates a user.
***param name="user" > User object to add or update.
***returns > A user object with updated fields.
** AdminDeleteUser - Administrator method, deletes a user by id. (Sets DeletedOn date to now)
***param name="userId" > Id of the user to delete.
***returns > True if deletion was successful. False if deletion was unsuccessful.
** AdminGetAllUsers - Administrator method, gets a list of all users.
***returns > A list of user objects.
** AdminGetAllUserRoles - Administrator method, gets all possible user roles.
***returns > A list of type user role objects
** AdminGetByIdUser - Administrator method, gets the user object by id.
***param name="userId" > Id of the user whose user data we wish to retrieve.
***returns > A user object.
** AdminGetLogsByUserId - Administrator method, gets a list of logs by user id. Get only the logs from the last 24 hours.
***param name="userId" > Id of the user whose logs to get.
***returns > A list of log objects.

Raskuskohad olid injectimine, nii et ei tekiks konflikte, ning kasutajate päringute hulga ilus piiramine, hetkel lihtsaltkatkestatakse kasutajaga ühendus.

=Klientrakendused=
Klientrakendus on tehtud WPF baasil kasutades peamiselt MVVM (Model-View-ViewModel) lähenemist, mille puhul View kood on enamjaolt tühi. Teenuse kasutamisel igakordse parooli ja kasutajanime sisestamise vältimiseks on teenuse kanali loomine eraldi kapseldatud.

Loodud klientrakendus võimaldab järgnevat:
*Kasutajaid tuvastada
*Kasutajad rolli põhjal eristada ja kuvada erinevaid menüüsid
*Kasutajal kontake lisada ja redigeerida
*Kontaktidele kontaktandmeid lisada ja redigeerida
*Kontaktidele pilte lisada, otse arvutist kui ka veebilinki ette andes
*Kontakte otsida kontakti nime ning kontaktandmete sisu järgi
*Kontakte otsida vaid kindla kontaktandmete tüübi sisu järgi
*Kontakte otsida ka nn. avalike ehk teiste kasutajate kontaktide seast
*Kontaktide määrata avalikuks (teistele nähtav) või mitte-avalikuks
*Administraatoritel lisada ja redigeerida kasutajaid
*Administraatoritel muuta maksimaalsete päringute arvu
*Administraatoritel näha iga kasutaja viimase 24 tunni päringuid (logi)

Raskuskohad olid teenuse asünkroonne kasutamine rakenduses ning võimalike veateadete haldamine.
=Klientrakenduse ja teenuse kasutamine=
Klientrakendus ja teenus asuvad koos [http://enos.itcollege.ee/~vevainu/TeenusJaKlient.rar SIIN]

Et teenus suudaks kliendiga suhelda tuleb luua sertifikaadid ja nende "Thumbprint" kood asendada vastavalt "ServiceHost" ja "ServiceClientWPF" konfiguratsioonifailides, vastavalt "Web.config" ja "App.config". Õpetus kuidas sertifikaate luua ja nende "Thumbprint" leida on õppejõu poolt jagatud videos [http://echo360.e-uni.ee/ess/echo/presentation/75e01210-2016-44a5-a48a-8a861c1b9799 SIIN]

Hetkel on "ServiceHost" seadistatud kasutama internetist kättesaadavat andmebaasi, kui soovite selle lokaalse vastu vahetada tuleb muuta "ContactBookConnection" nimeline connectionstring.

Kui on soovi kasutada omaenda kohalikku andmebaasi, siis saab EF andmebaasi loomiseks ja testandmete sisestamiseks kasutada "DALTestConsole" programmijuppi, kus tuleb siis asendada "ContactBookConnection" nimeline connectionstring. Et testandmeid suudetaks sisestada tuleb teha järgmist:
*DAL>ContactBookContext.cs - välja kommenteerida "this.Configuration.ProxyCreationEnabled = false;"
*Models>aBaseHistory.cs - sisse kommenteerida konstruktor, kus väärtustatakse kuupäeva väljad
*DAL>User-/Contact-/ContactInfoRepository - Välja kommenteerida "Add" ja "Update" meetodid
Pärast testandmete genereerimist tuleks muudatused tagasi keerata (Undo!)

=Logi=
*2013.03.13 – Sai paika pandud XML faili struktuur ja loodud seda genereeriv rakendus.
*2013.03.14 – XSLT faili loomine, lisatud „Puuvaade“ näitamaks kõiki sisendeid.
*2013.03.15 – XSLT failile inimeste otsing vastavalt kasutaja sisendile lisatud (ainult IE). Sai tehtud XSLT fail XML-i transformeerimiseks teistsuguseks XML-iks ja ka XSLT fail XML-i exceli vorminduse jaoks.
*2013.03.20 – XML to HTML otsing töötab nüüd IE, Chrome ja Firefoxiga
**wiki leht loodud,XML wiki lehele lisatud, tehtud stiilifailide näidised
*2013.03.24 – Teiste tiimide XML tööde retsenseerimine
*2013.04.25 – Alustatud teenuse loomist.
** Teenusele lisatud autentimine.
** Esialgsed mudelid ja DAL (Data-Access-Layer) loodud.
*2013.04.26 – Repositooriumite loomine ja baasrepositooriumi täitmine.
** Esialgsete testandmete automaatsisestamise loomine.
*2013.04.27 – Autentimine üle viidud isevalmistatud membership- ja role providerite peale.
** Alustatud teenuse meetodite kirjapanemisega.
*2013.04.28 – DI (Dependency-Injection) kasutusele võtmine.
** Esimesed teenuse meetodid kirja pandud.
*2013.05.02 – Tavakasutajatele mõeldud meetodid kirja pandud, alustatud administraatori meetoditega.
*2013.05.04 – Alustatud klientrakenduse loomist. Valmis navigeerimine ja käskluste põhi.
*2013.05.07 – Klientrakenduses valmis kõikide kontaktide kuvamise vaade. Teenusele lisatud piltide/failide lisamise/pärimise võimalus.
*2013.05.12 – WCF asünkroonsed meetodid asendatud asünkroonsete tööde klientrakenduse poolel.
*2013.05.13 – Otsimise võimalus lisatud.
**Administraatori vaade (kasutajate haldus) klientrakendusele lisatud.
**Logimine andmebaasi lisatud.
**Logimise põhjal päringute arvu piirangud lisatud.
*2013.05.15 – Klientrakendusele üldine veahalduse lisatud.
*2013.05.16 – Teenuse meetodid kommenteeritud.
**Teenuse ja klientrakenduse kohta käiv info Wikisse lisatud.
**Selle logi kirjutamine...

Talk:KK without K

2013-06-03T10:14:47Z

Vevainu: Created page with '=Meeskond „V“ retsensioon meeskond „KK without K“ teenuse kohta – 3.06.2013= Meeskond KK_without_K on võtnud eesmärgiks luua teenus LanParty haldamiseks, kahjuks …'

=Meeskond „[[V]]“ retsensioon meeskond „KK without K“ teenuse kohta – 3.06.2013=
Meeskond KK_without_K on võtnud eesmärgiks luua teenus LanParty haldamiseks, kahjuks on teenuse pakkumise eesmärgid wikis väga lühidalt kirjeldatud ning rohkem ei täpsustata. Esmalt tekib kohe küsimus, mis on teenuse skoop, kas vaid kohapeal kohtunike jaoks või ka kasutajate registreerimiseks. Wikis on siiski kirjeldatud kõik teenuse meetodid, millest kahjuks samuti ei loe välja täpsemat skoopi.
Teenuse meetodite dokumentatsioonist loeb välja, et teenus võimaldab kasutajate tuvastamist, haldamist, rollihaldust ning samuti mängude, võistluste ja meeskondade haldamist. Dokumentatsioon on hästi struktureeritud.

Teenuse lähtekoodi uurima asudes ilmneb, et teenuse loomisel on kasutatud Entity Framework kood enne lähenemist ning seega on teenuse ja andmekiht selgelt eraldatud. Andmemudeleid uurides jääb silma, et enamus string väljadel on maksimaalne pikkus määratud, kuid mudelite kood võinuks olla paremini struktureeritud, näiteks klassi atribuudid ning viited eraldada. Lisaks on mudelitel enamjaolt puudu niinimetatud navigeerimisväljad, mis on mingil põhjusel välja kommenteeritud. Samuti ei ole kasutatud laiska väärtustamist ning puudub ka võimalus niiöelda virtuaalseks kustutamiseks, sest puudub kustutamise kuupäeva väli.
Andmekihi projektis on kasutusel repositooriumite muster ning iga andmemudeli jaoks on loodud oma repositoorium, mis põhineb baas-repositooriumil. Repositoorimite puhul kasutatakse ka korralikult liideseid. Web API teenuses on kasutatud niinimetatud sõltuvuse süstimise mustrit, täpsemalt siis Ninject nimelist lisa.

Controllerites riivab pisut silma repode rohkus ning nende mitte-konstantne nimetamine. Samuti jääb silma „ContestControlleris“ üksiku Contest objekti pärimisel selle alamobjektide täitmine otse kontrolleris, minu arvamusel oleks selleks olnud õige koht repositoorium, kus oleks saanud asja palju elegantsemalt lahendada. Märkata võib ka, et kontrollerid on peamiselt Visual Studio poolt automaatselt genereeritud ning „DbContext“ asendatud repositooriumitega. Viimane teguviis näitab, et tuntakse Visual Studiot ning keskenduti vajalikule, kuid samas on ka siit tulenevaid kummalisi koodiosi. Näiteks Contest objekti pärimisel päritakse see esmalt repositoorimist ja seejärel täidetakse selle alamobjektid (Games, Teams jms), selles täitmisest edasi on aga kontroll „if(contest == null)“.

„LoginController“´is on samuti näha, et parooli hashimine, et võrrelda seda andmebaasis oleva hashitud parooliga, on samuti otse kontrolleris ja oleks võinud olla paigutatud repositooriumi. Hea külg asjal on, et paroole üldse hashitakse, seega on nende hoidmise turvalisusele mõeldud. Küll aga tekib küsimus miks ei kasutata .net raamistiku poolt pakutavaid autentimise vahendeid täielikult ära. Kasutatud on küll rollide haldamist, kuid rolle lisada ei ole võimalik ning rollidesse lisamine toimub hetkel kasutajanime alusel : „if (user.UserName != "Karhu") Roles.AddUserToRole(user.UserName, "User"); else Roles.AddUserToRole(user.UserName, "Admin");“. Samuti ei ole teenuse poolel kuskil näha teenuse piiramist vastavalt rollile. Kasutatud on osaliselt ka sisseehitatud kasutajahaldust, kuid samas on kasutajate info dubleeritud ka teenuse autorite poolt genereeritud andmebaasi ja klassidesse.

Teenuse poolelt on puudu ka turvaline ühendus (sertifikaatidega) ja kasutajate päringute/tegevuste logimine ning sellele vastavalt teenuse kasutamise piiramine. Seetõttu jääb selle osa retsenseerimine puudu. Samuti jääb mitmes kohas silma väljakommenteeritud koodi ning üldine ülesehitus on kohati häiriv.
Samas on võimalik Wiki logist välja lugeda, et teenus on välja töötatud enamjaolt 7 päeva jooksul. Mis iganes põhjused autoritel sellele porjektile suhteliselt vähese aja pühendamiseks olid,siis lühikese aja kohta hindaksin ise saavutatut siiski päris heaks, kuid kulunud aega mitte arvestades oleks autoritel veel tükk tööd, et jõuda asjaliku teenuse pakkumiseni.

Meeskond "[[V]]"

=Meeskond „[[V]]“ retsensioon meeskond „KK without K“ klientrakenduse kohta – 3.06.2013=
Meeskond on loonud WPF rakenduse, mis kasutab nende endi loodud Web API teenust. WPF rakenduses on hea tava kasutada MVVM (Model-View-ViewModel) mustrit, millest on C# programmeerimise aines korduvalt räägitud. Antud WPF rakenduses aga MVVM mustrit järgitud pole, mis on suureks miinuseks.

Rakenduse kihtideks jaotamisest tundub olevat tehtud niipalju, et vaated ja kollektsioonid on pandud eraldi kausta. Esmapilgul jääb arusaamatuks miks kollektsioonide jaoks on tehtud eraldi klassid, kuid lähemal uurimisel selgub, et igale kollektsioonile, antud kaustas, on lisatud üks meetod „CopyFrom“, mis võtab sisendiks „IEnumerable<T>“ tüüpi listi ja tõstab sellest ükshaaval T objektid „ObservableCollection<T>“ tüüpi listi ümber, siinkohal T on kindel tüüp ning iga rakenduses oleva tüübi kohta tundub olevat eraldi kollektsioon. Siinkohal oleks kindlasti võinud kasutada üld-klassi ehk niinimetatud „Generic“ tüüpi. Tagasi põhjuse juurde, miks rakenduse autorid on teinud, siis jääb mulje, et põhjuseks ongi „IEnumerable" tüüpi listi sisu kopeerimine „ObservableCollection“ sisse, millele ei ole vist muud lahendust leitud. Lahenduseks oleks olnud ka märksa lihtsam kood: „ObservableCollection<T> list = new ObservableCollection<T>(Siia IEnumerable tüüpi list);“, mille võib leida kiirelt google abiga.

Leidnud, et kollektsioonid on tegelikult antud rakenduses üleliigsed siis teine eraldamine ehk vaadete eraldi kausta panemine on igati hea otsus. Vaateid lähemalt uurides selgub, et nende visuaalne pool on üles ehitatud väga korrapäratult, jääb mulje, et elemendid on enamjaolt lihtsalt paika lohistatud ja suurus samuti hiirega paika tõmmatud. Leidub mõni üksik näide StackPanel´i kasutamisest, kuid oleks WPF rakenduse vaate disainimisel oodanud Grid´i kasutamist. Antud juhul on sellise XAML koodi tulemusel disaini muutmine tulevikus kohmakas ning aeganõudev. Positiivse poole pealt, vaadetes on kasutatud sidumist ehk „Binding“.
Lisaks vaadete kaustas olevatele vaadetele on veel põhivaated. Põhivaates on näha taas sidumise kasutamist, kuid jällegi on XAML elementidest alakasutatud Grid võimekust ning selle asemel pistetud elemendid StackPaneli sisse. Autorid on kasutanud erinevate vaadete jaoks TabControl elementi mille tulemusel on kõikide vaadete kood ühes XAML failis. Koodi parema loetavuse mõttes oleks võinud iga vaate koodi tõsta siiski eraldi faili ja TabControl elemendis neile viidata. Põhivaated on samuti dubleeritud, eraldi vaatefail tavakasutaja ja administraatori jaoks. Siinkohal oleks võinud kindlasti mõelda koodi taaskasutuse peale, kuid mingil põhjusel on autorid läinud teist teed.

Vaadates teenusega suhtlemist, siis positiivne on, et on kasutatud baasaadressi lisamist ning koodis kutsutakse välja vaid kindel kontroller, mitte ei trükita igalpool täispikka aadressi. Ebamugav on aga vaadata vaadetes korduva struktuuriga proovi-püüa ehk „Try-Catch“ lauset, mille oleks võinud kindlasti viia eraldi meetodite klassi ning ehk isegi kasutada „Generic“ tüüpi, et koodi taaskasutada.

Rakendust käivitades ja natuke testides ilmneb, et mõnes kohas on tehtud ka kontrollid, et rakendus kokku ei jookseks. Näiteks antakse veateadet, kui üritatakse ühtki mängu valimata mängu redigeerima hakata. Kuid kahjuks ei ole veahaldusega ning veateadetega eriti kaugele jõutud. Rakendust natuke uurides tekib probleeme mängu lisamisega, sest mängu lisamiseks on tarvis valida ka mängu žanr, kuid viimast ei ole võimalik rakenduses endas lisada või vähemalt minul ei õnnestunud antud kohta leida. Žanri taha jääb kinni mängu lisamine, viimase puudumisel takerdub ka võistluse loomine ning nende kahe puudumisel ei ole ka meeskondadel mingit mõtet.

Kokkuvõttes on tegemist kasutuskõlbmatu rakendusega, milles on küll võimalik autorite endi poolt loodud teenust kasutatud, kuid mitte täisväärtuslikult. Kood on rakenduses samuti halvasti loetav, sest puudub korralik struktuur. Oodates retsenseerimisest ka millegi uue õppimist, siis antud juhul pidin kahjuks pettuma.

Meeskond "[[V]]"

Category:Võrgurakendused II: hajussüsteemide ehitamine

2013-05-27T13:46:42Z

Vevainu: /* Projekti kaitsmisele registreerumine */

=Võrgurakendused II: hajussüsteemide ehitamine=
==Eesmärk==
Õppeaine eesmärgiks on tutvustada õppijale XML märgendikeelel baseeruvaid hajuslahendusi ja nende loomise võimalusi ning arendada õppijates .Net raamistiku vahenditega tarkvara arendamisoskuseid

==Lühitutvustus==
Õppeaines käsitletakse XML märgendikeelt ning veebiteenuseid. Kursuse käigus disainitakse, koostatakse ja testitakse veebiteenustel ning XML märgendikeelel põhinevaid lahendusi.

==Õpiväljundid==
* Õppija oskab kasutada XML märgendikeelt keerulisema strukuuriga andmete hoidmiseks ja esitamiseks struktureeritud kujul.
* Õppija oskab avalikult kättesaadavate juhendite abil koostada lihtsamaid klientrakendusi levinud veebiteenustele.
* Õppija oskab luua lihtsamaid veebiteenuseid kasutades selleks .Net raamistiku tehnoloogiaid ning vahendeid.
* Õppija teab veebiteenuste turvamiseks kasutatavaid tehnoloogiaid ja vahendeid ning oskab leid tavaolukorras rakendada.
* Õppija teab ning oskab kirjeldada hajusrakenduste kasutusvaldkondi ning nende arhitektuure.
* Õppija oskab töötada 3-5 liikmelises meeskonnas.

==Õppejõud==
Mait Poska
* mait.poska<ät> itcollege.ee
* Skype: minamait
* +372 53 469 734

==Hinne==
Aine hinde kujunemine:
* Eeldused (mille eest ei saa punkte)
** Kohal tuleb käia vähemalt '''50% praktikumidest'''
*** Kes seda nõuet ei täida peavad viimases praktikumis sooritama komplekstesti, mis sisaldab endas praktilisi ülesandeid.
**<ins>Grupitöö kõik osad on realiseeritud minimaalse tulemusega 51%</ins>



* <ins>Hinne</ins> ('''100p / 100%''') - Hinde kujunemisel arvestatakse kahte tööd:
** [[Kodutöö aines "Võrgurakendused II: hajussüsteemide ehitamine" 2012]], mis moodustab hindest 55%. '''55p''' (koosneb kolmest osast)
*** XML (xsd, xslt) '''10p'''
**** Retsensioonid kahe grupi XLM-i kohta '''2p+3p'''
*** Veebiteenus '''15p'''
**** Retsensioonid kahe grupi Veebiteenuse kohta '''2p+3p'''
*** Klientrakendused veebiteenusele '''15p'''
**** Retsensioonid kahe grupi Klientrakenduse kohta '''2p+3p'''
** <ins>Individuaalne teadmiste kontroll</ins> '''45p'''
*** Teooria (Test) '''20p''' (tulemus vähemalt 51%)
*** Praktiline (Programmeerimine) '''25p''' (tulemus vähemalt 51%)




[[Võrgurakendused II: 2011 kevadel valminud kodutööd]]

==Tähtajad==


* '''XML fail''' [https://wiki.itcollege.ee/index.php/Kodut%C3%B6%C3%B6_aines_%22V%C3%B5rgurakendused_II:_hajuss%C3%BCsteemide_ehitamine%22_2013#XML_andmefail NB! Täpsem info]
** XML fail, stiilifail ja skeemifail peavad olema valmis ja wikilehel kirjeldatud hiljemalt '''23. märts 2013'''.
** Retsensioonid XML-failide kohta peavad tehtud olema '''30. märts 2013'''.

* '''Veebiteenus''' [https://wiki.itcollege.ee/index.php/Kodut%C3%B6%C3%B6_aines_%22V%C3%B5rgurakendused_II:_hajuss%C3%BCsteemide_ehitamine%22_2013#Veebiteenus NB! Täpsem info]
** Veebiteenus peab olema valmis, esitatud ja ja wikilehel kirjeldatud hiljemalt '''26. mai 2013'''.
** Retsensioonid veebiteenuste kohta peavad tehtud olema '''4. juuni 2013'''.

* '''Klientrakendused''' [https://wiki.itcollege.ee/index.php/Kodut%C3%B6%C3%B6_aines_%22V%C3%B5rgurakendused_II:_hajuss%C3%BCsteemide_ehitamine%22_2013#Klientrakendus NB! Täpsem info]
** Klientrakendused peavad olema valmis, esitatud ja ja wikilehel kirjeldatud hiljemalt '''26. mai 2013'''.
** Retsensioonid klientrakenduste kohta peavad tehtud olema '''4. juuni 2013'''.



==Retsensioonid==

Iga grupp peab tegema lisaks igale grupitööle vastavalt ka 2 retsensiooni. Retsensioonid võib teha vabalt valitud gruppide tööde kohta. Tingimuseks on see, et ühe töö kohta saab teha maksimaalselt kolm retsensiooni.

Seega kokku tuleb esitada 6 retsensiooni ühel grupil.

Kui grupp on teinud vaid ühe retsensiooni, siis selle eest saab 2 punkti. Kui sellele lisandub ka teine retsensioon, siis teise retsensiooni eest saab 3 punkti. Kokku 5 punkti.

<ins>Lisaks tuleb silmas pidada retsensioonide minimaalseid pikkusi projektide kohta.</ins> [https://wiki.itcollege.ee/index.php/Kodut%C3%B6%C3%B6_aines_%22V%C3%B5rgurakendused_II:_hajuss%C3%BCsteemide_ehitamine%22_2012#Retsensioonid Retsensioonide minimaalsed pikkused]

==Meeskonnad==
Ühte meeskonda võib kuuluda 3 kuni 4 tudengit. Gruppi kuuluvate tudengite nimekiri kinnitatakse esimese projekti esitamisega.

==Projekti kaitsmisele registreerumine==

Siia ilmuvad kuupäevad ja kellaajad, millal on võimalik oma projekti kaitsta.

'''NB!''' Kõige tublimad teevad ka slaidiesitluse, kus selgub:
*Iga meeskonnaliikme panus ja liikmed
*Projekti üleüldine eesmärk
*Tööde kava
*Teostatud funktsionaalus
*Teostamata osad
*Enda arvamus projektist ning hindesoov
*Raskemad osad projekti juures
*Mida uut juurde õpiti

Esmaspäev 27.05.2013
*12:00 - [[Meeskond "asdasdasd"]]
*12:15 - AFFA2
*12:30 - X-Ladu
*12:45 - [[Bleh]]
*13:00 -
*13:15 -

 Teisipäev 28.05.2013
*10:00 - [[SaanEndagaHästiLäbi]]
*10:15 - V
*10:30 -
*10:45 -
*11:00 -
*11:15 -

 Neljapäev 30.05.2013
*10:00 - BitByBit
*10:15 - REMS
*10:30 - GOW
*10:45 - [[KK_without_K]]
*11:00 - Mardo, Madis ja Kristi
*11:15 - [[KKMK]]

=Teemad=
=XML failivorming ja sellega seotud tehnoloogiad=

==XML failivorming==
===Loengusalvestused===

===Teooria===
* XML failid
** Kippar, J. "XML rakendused", TLU:2009 http://minitorn.tlu.ee/~jaagup/kool/java/kursused/10/xmlrak/trykk/xmlrak.pdf
** XMLi rakendused ainekursuse leht by Jaagup Kippar http://minitorn.tlu.ee/~jaagup/kool/java/kursused/10/xmlrak/juht.html
** Introduction to XML by w3schools.com http://www.w3schools.com/xml/xml_whatis.asp
* XSLT - XML failide transformeerimine ehk stiilifailid
** XSLT Tutorial by w3schools.com http://www.w3schools.com/xsl/default.asp

===Praktika===


* [[Praktikum: XML failide loomine, VR2.1]]
*[[Praktikum: XML andmefailidest päringute tegemine VR2.2]]
* [[Praktikum: XML failide valideerimine (XSD, DTD) ning XML stiilide (XSLT) loomine , VR2.3]]

=Veebiteenused=
==Loengud==

==Veebiteenuste loomine==
* ASP.NET Web Services http://msdn.microsoft.com/en-us/library/t745kdsh.aspx
* Creating and Consuming .NET Web Services in 5 Easy Steps http://articles.sitepoint.com/article/net-web-services-5-steps

==Andmebaasiga ühendumine==
* Database Connectivity using WebService http://www.c-sharpcorner.com/UploadFile/raj1979/DatabaseWebService01142008011107AM/DatabaseWebService.aspx

==Veebiteenuste turvamine==
* Securing ASP.Net Web Services with Forms Authentication http://dotnetslackers.com/articles/aspnet/Securing-ASP-Net-Web-Services-with-Forms-Authentication.aspx

==Praktika==
*[[Praktikum VR 2.4 OOP meeldetuletus]]
*[[Praktikum VR 2.5 Päringud Andmebaasist]]

=Veebiteenuste kasutamine=
==Praktika==

[[Praktikum: Flickr'i veebiteenusele klientrakenduse loomine]]
=Arhiiv=
==2012 Kevad==
===Loengud===
* '''Esimese loengu salvestus, kus räägiti XML andmefailist asub siin: http://echo360.e-uni.ee/ess/echo/presentation/d590aaa6-2d08-4852-9db6-42041cc7e438 '''
* '''Teise loengu salvestus, kus räägiti XML skeemidest ja transformatsioonidest asub siin: http://echo360.e-uni.ee/ess/echo/presentation/fa1431fb-3b80-42a3-a7de-f18fe6a1d3ae '''
**Teises loengus tehtud näited, asuvad siin: http://enos.itcollege.ee/~mposka/Vorgurakendused_II_2012/Paevaope/Loengud/Loeng2/

* '''Kolmas loeng, kus räägiti LINQ'st: http://echo360.e-uni.ee/ess/echo/presentation/bbb940ea-fb20-49b4-9d5b-7b2e41f1ac39 '''
**Kolmandas loengus tehtud näited asuvad siin: http://enos.itcollege.ee/~mposka/Vorgurakendused_II_2012/Paevaope/Loengud/Loeng3/
* ''' Neljas loeng: http://echo360.e-uni.ee/ess/echo/presentation/7b97f540-e6e1-4bbb-99c3-04e9833b690b '''
* ''' Viies loeng. Lihtsa veebiteenuse loomise algus: http://echo360.e-uni.ee/ess/echo/presentation/7babae6b-fd76-4564-b60b-d30f82d3d2cf
* ''' Kuues loeng. Windows Communication Foundation: http://echo360.e-uni.ee/ess/echo/presentation/78ee4f6d-e7d5-47e0-92b9-824331027bbd
* ''' [http://echo360.e-uni.ee/ess/echo/presentation/c5abc659-5d25-4e7c-bbdb-f054dfd99c3f Loeng 12.03.2012]
* ''' [http://echo360.e-uni.ee/ess/echo/presentation/8c5b7bba-7f5f-4a2c-b143-473ea810ac34 Loeng 19.03.2012]
* ''' [http://echo360.e-uni.ee/ess/echo/presentation/c5abc659-5d25-4e7c-bbdb-f054dfd99c3f Loeng 02.04.2012 - WCF Turvalisus]
* ''' [http://echo360.e-uni.ee/ess/echo/presentation/6aba1a81-fab2-418d-bb70-969dbe97de9e Loeng 09.04.2012]
* ''' [http://echo360.e-uni.ee/ess/echo/presentation/ecce8a28-6bed-4164-9443-3cd784197489 Loeng 16.04.2012]
* ''' [http://echo360.e-uni.ee/ess/echo/presentation/4115cf45-538e-42d3-bf1f-f28504e3a18e Loeng 23.04.2012 - Bing teenuse kasutamine]
* ''' [http://echo360.e-uni.ee/ess/echo/presentation/1f36208f-fa14-41c2-bb7e-75f7a4ffd765 Loeng 07.05.2012(Asjalikum jutt algab 40min kandist]
* ''' [http://echo360.e-uni.ee/ess/echo/presentation/bdfcb5f2-698d-4429-a485-a40d51c74ded Loeng 14.05.2012 Gunnar]
===Praktikumid===
* [[Praktikum: XML failide loomine, VR2.1]]
* [[Linq_päringukeel|Praktikum: LINQ päringute tegemine XML-i peal, VR2.2]]
** [http://enos.itcollege.ee/~kraspel/VRII/%5b2012.02.09%5d%20Praktikum%202%20/ Praktikumi näide]
* [[Praktikum: XML failide valideerimine (XSD, DTD) ning XML stiilide (XSLT) loomine , VR2.3]]
** [http://enos.itcollege.ee/~kraspel/VRII/%5b2012.02.16%5d%20Praktikum%203/ Praktikumi näide]
* [[Praktikum: XML failidega töötamine (kokkuvõttev praktikum), VR2.4]]
** [http://enos.itcollege.ee/~kraspel/VRII/%5b2012.02.23%5d%20Praktikum%204/ Praktikumi näide]
* [[Praktikum: Lihtne andmebaasil veebiteenus, VR2.6]]
** [http://enos.itcollege.ee/~kraspel/VRII/%5b2012.03.08%5d%20Praktikum%206/ Praktikumi näide]
* [[Praktikum: Veebiteenuse loomine Windows Communication Foundation abil, VR2.7]]
** [http://enos.itcollege.ee/~kraspel/VRII/%5b2012.03.15%5d%20Praktikum%208/ Praktikumi näide]
* Praktikum: Object Orientated crash, VR2.8
** [http://enos.itcollege.ee/~kraspel/VRII/%5b2012.03.22%5d%20Praktikum%209/ Praktikumi näide]
* [[Praktikum: Windows Communication Foundation teenuse turvamine, VR2.9]]
** [http://enos.itcollege.ee/~kraspel/VRII/%5b2012.04.05%5d%20Praktikum%2010/ Praktikumi näide]
* [[Praktikum: Windows Communication Foundation teenuse turvamine jätk, VR2.10]]
** [http://enos.itcollege.ee/~kraspel/VRII/%5b2012.04.13%5d%20Praktikum%2011/ Praktikumi näide]
* [[Praktikum: Lihtne andmebaasil veebiteenus, VR2.6]]

===Meeskonnad 2012===
*[[Hello Kitty]]
*[[TTiim]]
*[[Meeskond "Harold"|Harold]]
*[[Meeskond "WP"]]

*Meeskond "[[-.-]]"*
** Erki Miilberg (projektijuht)
** Kalev Vallsalu
** Oliver Naaris
** Margo Kuustik

* Meeskond "[[PhoneBook]]"
**Lauri Jansen
**Tanel Jüris
**Madis Rääk

*Meeskond "[[LLL]]"
** Joonas Püüa
** Janno Toomingas
** Janek Kople
** Roland Krindal

*Meeskond "[[Peeter VR2]]"
** Lennart Lüsi
** Kairo Koik
** Marek Kikas
** Kaivar Kull

*[[Meeskond ".NOT"]]
** Martin Kosk
** Kalmer Tart
** Martin Aarne
** Gert Glükmann

V

2013-05-16T14:06:57Z

Vevainu: /* Klientrakendused */

[[Category:Võrgurakendused II: hajussüsteemide ehitamine]]
=Liige=
Veiko Vainu D21
=Retsensioonid=
==XML==
[https://wiki.itcollege.ee/index.php/Talk:Meeskond_%22asdasdasd%22 Retsensioon meeskond „asdasdasd“ XML-i kohta – 24.03.2013]

[https://wiki.itcollege.ee/index.php/Talk:SaanEndagaH%C3%A4stiL%C3%A4bi Retsensioon meeskond „SaanEndagaHästiLäbi“ XML-i kohta – 24.03.2013]

=XML fail=
==XML andmefail==
*[http://enos.itcollege.ee/~vevainu/XML/armeeXML.xml XML andmefail]

==XML skeemifail==
*[http://enos.itcollege.ee/~vevainu/XML/armeeXML.xsd XML skeemifail]

==XML stiilifailid==
XML to HTML - Kuvab vasakul pool lehte kogu XML-i sisu nn. puuvaates. Paremal pool on otsing, mis otsib sõduri ees- ja perekonnanimest vastavat stringi.
* [http://enos.itcollege.ee/~vevainu/XML/xmlTOhtml.xslt XML to HTML]
* [http://enos.itcollege.ee/~vevainu/XML/xmlTOhtml.xml Näidis]

XML to XML - Trükib välja kõik sõdurid sorteerides perekonnanime ja seejärel eesnime järgi. Igale sõdurile on lisatud ka uus atribuut ID, mis koosneb sõduri ID-st ja tema rühma, allüksuse ja väeosa ID-st.
* [http://enos.itcollege.ee/~vevainu/XML/xmlTOxml.xslt XML to XML]
* [http://enos.itcollege.ee/~vevainu/XML/xmlTOxml.xml Näidis]

XML to Excel - Loob workbooki iga allüksuse jaoks oma worksheeti kuhu kuvatakse selle üksuse isikkooseis sorteeritult Auastme tähestikulises järjekorras.
* [http://enos.itcollege.ee/~vevainu/XML/xmlTOxlsx.xslt XML to Excel]
* [http://enos.itcollege.ee/~vevainu/XML/xmlTOxlsx.xml Näidis XML]
* [http://enos.itcollege.ee/~vevainu/XML/xmlTOxlsxNAIDE.xlsx Näidis EXCEL]
* Kuidas - tuleb xml faili lisada viide vastavale xslt stylesheetile, seejärel tuleb xml fail Excelis avada ja valida, et kasutatakse vastavat stiilifaili.

==XML kõik ühes (.rar)==
*[http://enos.itcollege.ee/~vevainu/XML/XML.rar Kõik failid ühes (.rar)]

=Veebiteenus=

Loodud sai kontaktiraamatu teenus, mis põhineb õppejõu "Telefoniraamatu teenus" näidisteemal.

Teenus on loodud WCF baasil ja kasutab Asp.Net kasutajate autentimist, mille jaoks on vastavad membership- ja roleprovider. Teenus võimaldab ka logimist, mis toimub enne sissetuleva päringu täitmist ning kus kontrollitakse ka kasutaja päringu limiidi ületamist. Teenuse päringud teostatakse Ninject süstimise abil läbi uow (unit-of-work) konteineri, mis omakorda sisaldab repositooriume. Kogu andmekiht on üles ehitatud Entity Framework Code First meetodil.

Teenus pakub järgmisi meetodeid:
* User methods 
** AuthenticateUser - Tries to authenticate the user based on credentials.
*** returns > User object of the user or null if authentication failed.
** GetAuthenticatedMyContact - Gets personal contact object of the querying user.
*** returns > A contact object.
** AddUpdateContact - Add or update contacts infromation.
*** param name="contact" > Contact object to add or update.
*** returns > A contact object with updated fields.
** AddUpdateContactInfo - Add or update contacts contact infromation.
*** param name="contactInfo" > Contact information object to add or update.
*** returns > A contact information object with updated fields.
** AddUpdateContactPicture - Add or update a contacts picture.
***param name="contactId" > Id of the contact to whom we wish to add a picture to or update/replace and existing one.
***param name="picture" > File object of containing the picture we wish to add to a contact.
***returns > A file object with updated fields.
** DeleteContact - Deletes a contact by contact object.
***param name="contact" > Contact object of the contact to delete.
***returns > True if deleteion was successful. False if deletion was unsuccessful.
** DeleteContactById - Deletes a contact by id.
***param name="id" > Id of the contact to delete.
***returns > True if deleteion was successful. False if deletion was unsuccessful.
** DeleteContactInfo - Deletes a contacts contact information by contact information object.
***param name="contact" > ContactInfo object of the contact information to delete.
***returns > True if deleteion was successful. False if deletion was unsuccessful.
** DeleteContactInfoById - Deletes a contacts contact information by contact information id.
***param name="id" > Id of the contact information to delete.
***returns > True if deleteion was successful. False if deletion was unsuccessful.
** GetAllContacts - Gets a list of all contacts of the querying user.
***returns > A list of contact objects.
** GetAllContactInfoTypes - Gets a list of contact information types.
***returns > A list of contactinfotype objects.
** GetAllContactInfoesByContactId - Gets a list of a contacts contact information.
***param name="contactId" > Id of a contact whose contactinformation to retrieve.
***returns > A list of contactinfo objects.
** GetByIdContact - Returns a contacts information.
***param name="id" > Id of the contact whose information to retrieve.
***returns > A contact object
** GetByIdContactPicture - Returns a file object, containing a picture in binary form, of a contact.
***param name="id" > Id of the contact whose picture to retrieve.
***returns > A file object of the contacts picture.
** SearchContactByAny - Searches contacts by name or by contacts information, depending on given input.
***param name="any" > Symbol combination to search by.
***param name="type" > Contact info type name to search by, or all to search by everything.
***returns > A list of contacts matching the search criteria.
** SearchContactByAnyPublic - Searches contacts by name or by contacts information, depending on given input. Also searches publicly available contact (contacts that have IsPublic=True).
***param name="any" > Symbol combination to search by.
***param name="type" > Contact info type name to search by, or all to search by everything.
***returns > A list of contacts matching the search criteria.
* Administrators methods 
** AdminAddUpdateUser - Administrator method, adds or updates a user.
***param name="user" > User object to add or update.
***returns > A user object with updated fields.
** AdminDeleteUser - Administrator method, deletes a user by id. (Sets DeletedOn date to now)
***param name="userId" > Id of the user to delete.
***returns > True if deletion was successful. False if deletion was unsuccessful.
** AdminGetAllUsers - Administrator method, gets a list of all users.
***returns > A list of user objects.
** AdminGetAllUserRoles - Administrator method, gets all possible user roles.
***returns > A list of type user role objects
** AdminGetByIdUser - Administrator method, gets the user object by id.
***param name="userId" > Id of the user whose user data we wish to retrieve.
***returns > A user object.
** AdminGetLogsByUserId - Administrator method, gets a list of logs by user id. Get only the logs from the last 24 hours.
***param name="userId" > Id of the user whose logs to get.
***returns > A list of log objects.

Raskuskohad olid injectimine, nii et ei tekiks konflikte, ning kasutajate päringute hulga ilus piiramine, hetkel lihtsaltkatkestatakse kasutajaga ühendus.

=Klientrakendused=
Klientrakendus on tehtud WPF baasil kasutades peamiselt MVVM (Model-View-ViewModel) lähenemist, mille puhul View kood on enamjaolt tühi. Teenuse kasutamisel igakordse parooli ja kasutajanime sisestamise vältimiseks on teenuse kanali loomine eraldi kapseldatud.

Loodud klientrakendus võimaldab järgnevat:
*Kasutajaid tuvastada
*Kasutajad rolli põhjal eristada ja kuvada erinevaid menüüsid
*Kasutajal kontake lisada ja redigeerida
*Kontaktidele kontaktandmeid lisada ja redigeerida
*Kontaktidele pilte lisada, otse arvutist kui ka veebilinki ette andes
*Kontakte otsida kontakti nime ning kontaktandmete sisu järgi
*Kontakte otsida vaid kindla kontaktandmete tüübi sisu järgi
*Kontakte otsida ka nn. avalike ehk teiste kasutajate kontaktide seast
*Kontaktide määrata avalikuks (teistele nähtav) või mitte-avalikuks
*Administraatoritel lisada ja redigeerida kasutajaid
*Administraatoritel muuta maksimaalsete päringute arvu
*Administraatoritel näha iga kasutaja viimase 24 tunni päringuid (logi)

Raskuskohad olid teenuse asünkroonne kasutamine rakenduses ning võimalike veateadete haldamine.
=Klientrakenduse ja teenuse kasutamine=
Klientrakendus ja teenus asuvad koos [http://enos.itcollege.ee/~vevainu/TeenusJaKlient.rar SIIN]

Et teenus suudaks kliendiga suhelda tuleb luua sertifikaadid ja nende "Thumbprint" kood asendada vastavalt "ServiceHost" ja "ServiceClientWPF" konfiguratsioonifailides, vastavalt "Web.config" ja "App.config". Õpetus kuidas sertifikaate luua ja nende "Thumbprint" leida on õppejõu poolt jagatud videos [http://echo360.e-uni.ee/ess/echo/presentation/75e01210-2016-44a5-a48a-8a861c1b9799 SIIN]

Hetkel on "ServiceHost" seadistatud kasutama internetist kättesaadavat andmebaasi, kui soovite selle lokaalse vastu vahetada tuleb muuta "ContactBookConnection" nimeline connectionstring.

Kui on soovi kasutada omaenda kohalikku andmebaasi, siis saab EF andmebaasi loomiseks ja testandmete sisestamiseks kasutada "DALTestConsole" programmijuppi, kus tuleb siis asendada "ContactBookConnection" nimeline connectionstring. Et testandmeid suudetaks sisestada tuleb teha järgmist:
*DAL>ContactBookContext.cs - välja kommenteerida "this.Configuration.ProxyCreationEnabled = false;"
*Models>aBaseHistory.cs - sisse kommenteerida konstruktor, kus väärtustatakse kuupäeva väljad
*DAL>User-/Contact-/ContactInfoRepository - Välja kommenteerida "Add" ja "Update" meetodid
Pärast testandmete genereerimist tuleks muudatused tagasi keerata (Undo!)

=Logi=
*2013.03.13 – Sai paika pandud XML faili struktuur ja loodud seda genereeriv rakendus.
*2013.03.14 – XSLT faili loomine, lisatud „Puuvaade“ näitamaks kõiki sisendeid.
*2013.03.15 – XSLT failile inimeste otsing vastavalt kasutaja sisendile lisatud (ainult IE). Sai tehtud XSLT fail XML-i transformeerimiseks teistsuguseks XML-iks ja ka XSLT fail XML-i exceli vorminduse jaoks.
*2013.03.20 – XML to HTML otsing töötab nüüd IE, Chrome ja Firefoxiga
**wiki leht loodud,XML wiki lehele lisatud, tehtud stiilifailide näidised
*2013.03.24 – Teiste tiimide XML tööde retsenseerimine
*2013.04.25 – Alustatud teenuse loomist.
** Teenusele lisatud autentimine.
** Esialgsed mudelid ja DAL (Data-Access-Layer) loodud.
*2013.04.26 – Repositooriumite loomine ja baasrepositooriumi täitmine.
** Esialgsete testandmete automaatsisestamise loomine.
*2013.04.27 – Autentimine üle viidud isevalmistatud membership- ja role providerite peale.
** Alustatud teenuse meetodite kirjapanemisega.
*2013.04.28 – DI (Dependency-Injection) kasutusele võtmine.
** Esimesed teenuse meetodid kirja pandud.
*2013.05.02 – Tavakasutajatele mõeldud meetodid kirja pandud, alustatud administraatori meetoditega.
*2013.05.04 – Alustatud klientrakenduse loomist. Valmis navigeerimine ja käskluste põhi.
*2013.05.07 – Klientrakenduses valmis kõikide kontaktide kuvamise vaade. Teenusele lisatud piltide/failide lisamise/pärimise võimalus.
*2013.05.12 – WCF asünkroonsed meetodid asendatud asünkroonsete tööde klientrakenduse poolel.
*2013.05.13 – Otsimise võimalus lisatud.
**Administraatori vaade (kasutajate haldus) klientrakendusele lisatud.
**Logimine andmebaasi lisatud.
**Logimise põhjal päringute arvu piirangud lisatud.
*2013.05.15 – Klientrakendusele üldine veahalduse lisatud.
*2013.05.16 – Teenuse meetodid kommenteeritud.
**Teenuse ja klientrakenduse kohta käiv info Wikisse lisatud.
**Selle logi kirjutamine...

V

2013-05-16T13:40:14Z

Vevainu: /* Logi */

[[Category:Võrgurakendused II: hajussüsteemide ehitamine]]
=Liige=
Veiko Vainu D21
=Retsensioonid=
==XML==
[https://wiki.itcollege.ee/index.php/Talk:Meeskond_%22asdasdasd%22 Retsensioon meeskond „asdasdasd“ XML-i kohta – 24.03.2013]

[https://wiki.itcollege.ee/index.php/Talk:SaanEndagaH%C3%A4stiL%C3%A4bi Retsensioon meeskond „SaanEndagaHästiLäbi“ XML-i kohta – 24.03.2013]

=XML fail=
==XML andmefail==
*[http://enos.itcollege.ee/~vevainu/XML/armeeXML.xml XML andmefail]

==XML skeemifail==
*[http://enos.itcollege.ee/~vevainu/XML/armeeXML.xsd XML skeemifail]

==XML stiilifailid==
XML to HTML - Kuvab vasakul pool lehte kogu XML-i sisu nn. puuvaates. Paremal pool on otsing, mis otsib sõduri ees- ja perekonnanimest vastavat stringi.
* [http://enos.itcollege.ee/~vevainu/XML/xmlTOhtml.xslt XML to HTML]
* [http://enos.itcollege.ee/~vevainu/XML/xmlTOhtml.xml Näidis]

XML to XML - Trükib välja kõik sõdurid sorteerides perekonnanime ja seejärel eesnime järgi. Igale sõdurile on lisatud ka uus atribuut ID, mis koosneb sõduri ID-st ja tema rühma, allüksuse ja väeosa ID-st.
* [http://enos.itcollege.ee/~vevainu/XML/xmlTOxml.xslt XML to XML]
* [http://enos.itcollege.ee/~vevainu/XML/xmlTOxml.xml Näidis]

XML to Excel - Loob workbooki iga allüksuse jaoks oma worksheeti kuhu kuvatakse selle üksuse isikkooseis sorteeritult Auastme tähestikulises järjekorras.
* [http://enos.itcollege.ee/~vevainu/XML/xmlTOxlsx.xslt XML to Excel]
* [http://enos.itcollege.ee/~vevainu/XML/xmlTOxlsx.xml Näidis XML]
* [http://enos.itcollege.ee/~vevainu/XML/xmlTOxlsxNAIDE.xlsx Näidis EXCEL]
* Kuidas - tuleb xml faili lisada viide vastavale xslt stylesheetile, seejärel tuleb xml fail Excelis avada ja valida, et kasutatakse vastavat stiilifaili.

==XML kõik ühes (.rar)==
*[http://enos.itcollege.ee/~vevainu/XML/XML.rar Kõik failid ühes (.rar)]

=Veebiteenus=

Loodud sai kontaktiraamatu teenus, mis põhineb õppejõu "Telefoniraamatu teenus" näidisteemal.

Teenus on loodud WCF baasil ja kasutab Asp.Net kasutajate autentimist, mille jaoks on vastavad membership- ja roleprovider. Teenus võimaldab ka logimist, mis toimub enne sissetuleva päringu täitmist ning kus kontrollitakse ka kasutaja päringu limiidi ületamist. Teenuse päringud teostatakse Ninject süstimise abil läbi uow (unit-of-work) konteineri, mis omakorda sisaldab repositooriume. Kogu andmekiht on üles ehitatud Entity Framework Code First meetodil.

Teenus pakub järgmisi meetodeid:
* User methods 
** AuthenticateUser - Tries to authenticate the user based on credentials.
*** returns > User object of the user or null if authentication failed.
** GetAuthenticatedMyContact - Gets personal contact object of the querying user.
*** returns > A contact object.
** AddUpdateContact - Add or update contacts infromation.
*** param name="contact" > Contact object to add or update.
*** returns > A contact object with updated fields.
** AddUpdateContactInfo - Add or update contacts contact infromation.
*** param name="contactInfo" > Contact information object to add or update.
*** returns > A contact information object with updated fields.
** AddUpdateContactPicture - Add or update a contacts picture.
***param name="contactId" > Id of the contact to whom we wish to add a picture to or update/replace and existing one.
***param name="picture" > File object of containing the picture we wish to add to a contact.
***returns > A file object with updated fields.
** DeleteContact - Deletes a contact by contact object.
***param name="contact" > Contact object of the contact to delete.
***returns > True if deleteion was successful. False if deletion was unsuccessful.
** DeleteContactById - Deletes a contact by id.
***param name="id" > Id of the contact to delete.
***returns > True if deleteion was successful. False if deletion was unsuccessful.
** DeleteContactInfo - Deletes a contacts contact information by contact information object.
***param name="contact" > ContactInfo object of the contact information to delete.
***returns > True if deleteion was successful. False if deletion was unsuccessful.
** DeleteContactInfoById - Deletes a contacts contact information by contact information id.
***param name="id" > Id of the contact information to delete.
***returns > True if deleteion was successful. False if deletion was unsuccessful.
** GetAllContacts - Gets a list of all contacts of the querying user.
***returns > A list of contact objects.
** GetAllContactInfoTypes - Gets a list of contact information types.
***returns > A list of contactinfotype objects.
** GetAllContactInfoesByContactId - Gets a list of a contacts contact information.
***param name="contactId" > Id of a contact whose contactinformation to retrieve.
***returns > A list of contactinfo objects.
** GetByIdContact - Returns a contacts information.
***param name="id" > Id of the contact whose information to retrieve.
***returns > A contact object
** GetByIdContactPicture - Returns a file object, containing a picture in binary form, of a contact.
***param name="id" > Id of the contact whose picture to retrieve.
***returns > A file object of the contacts picture.
** SearchContactByAny - Searches contacts by name or by contacts information, depending on given input.
***param name="any" > Symbol combination to search by.
***param name="type" > Contact info type name to search by, or all to search by everything.
***returns > A list of contacts matching the search criteria.
** SearchContactByAnyPublic - Searches contacts by name or by contacts information, depending on given input. Also searches publicly available contact (contacts that have IsPublic=True).
***param name="any" > Symbol combination to search by.
***param name="type" > Contact info type name to search by, or all to search by everything.
***returns > A list of contacts matching the search criteria.
* Administrators methods 
** AdminAddUpdateUser - Administrator method, adds or updates a user.
***param name="user" > User object to add or update.
***returns > A user object with updated fields.
** AdminDeleteUser - Administrator method, deletes a user by id. (Sets DeletedOn date to now)
***param name="userId" > Id of the user to delete.
***returns > True if deletion was successful. False if deletion was unsuccessful.
** AdminGetAllUsers - Administrator method, gets a list of all users.
***returns > A list of user objects.
** AdminGetAllUserRoles - Administrator method, gets all possible user roles.
***returns > A list of type user role objects
** AdminGetByIdUser - Administrator method, gets the user object by id.
***param name="userId" > Id of the user whose user data we wish to retrieve.
***returns > A user object.
** AdminGetLogsByUserId - Administrator method, gets a list of logs by user id. Get only the logs from the last 24 hours.
***param name="userId" > Id of the user whose logs to get.
***returns > A list of log objects.

Raskuskohad olid injectimine, nii et ei tekiks konflikte, ning kasutajate päringute hulga ilus piiramine, hetkel lihtsaltkatkestatakse kasutajaga ühendus.

=Klientrakendused=
Klientrakendus on tehtud WPF baasil kasutades peamiselt MVVM (Model-View-ViewModel) lähenemist, mille puhul View kood on enamjaolt tühi. Teenuse kasutamisel igakordse parooli ja kasutajanime sisestamise vältimiseks on teenuse kanali loomine eraldi kapseldatud.

Loodud klientrakendus võimaldab järgnevat:
*Kasutajaid tuvastada
*Kasutajad rolli põhjal eristada ja kuvada erinevaid menüüsid
*Kasutajal kontake lisada ja redigeerida
*Kontaktidele kontaktandmeid lisada ja redigeerida
*Kontaktidele pilte lisada, otse arvutist kui ka veebilinki ette andes
*Kontakte otsida kontakti nime ning kontaktandmete sisu järgi
*Kontakte otsida vaid kindla kontaktandmete tüübi sisu järgi
*Kontakte otsida ka nn. avalike ehk teiste kasutajate kontaktide seast
*Kontaktide määrata avalikuks (teistele nähtav) või mitte-avalikuks
*Administraatoritel lisada ja redigeerida kasutajaid
*Administraatoritel muuta maksimaalsete päringute arvu
*Administraatoritel näha iga kasutaja viimase 24 tunni päringuid (logi)

Raskuskohad olid teenuse asünkroonne kasutamine rakenduses ning võimalike veateadete haldamine.

=Logi=
*2013.03.13 – Sai paika pandud XML faili struktuur ja loodud seda genereeriv rakendus.
*2013.03.14 – XSLT faili loomine, lisatud „Puuvaade“ näitamaks kõiki sisendeid.
*2013.03.15 – XSLT failile inimeste otsing vastavalt kasutaja sisendile lisatud (ainult IE). Sai tehtud XSLT fail XML-i transformeerimiseks teistsuguseks XML-iks ja ka XSLT fail XML-i exceli vorminduse jaoks.
*2013.03.20 – XML to HTML otsing töötab nüüd IE, Chrome ja Firefoxiga
**wiki leht loodud,XML wiki lehele lisatud, tehtud stiilifailide näidised
*2013.03.24 – Teiste tiimide XML tööde retsenseerimine
*2013.04.25 – Alustatud teenuse loomist.
** Teenusele lisatud autentimine.
** Esialgsed mudelid ja DAL (Data-Access-Layer) loodud.
*2013.04.26 – Repositooriumite loomine ja baasrepositooriumi täitmine.
** Esialgsete testandmete automaatsisestamise loomine.
*2013.04.27 – Autentimine üle viidud isevalmistatud membership- ja role providerite peale.
** Alustatud teenuse meetodite kirjapanemisega.
*2013.04.28 – DI (Dependency-Injection) kasutusele võtmine.
** Esimesed teenuse meetodid kirja pandud.
*2013.05.02 – Tavakasutajatele mõeldud meetodid kirja pandud, alustatud administraatori meetoditega.
*2013.05.04 – Alustatud klientrakenduse loomist. Valmis navigeerimine ja käskluste põhi.
*2013.05.07 – Klientrakenduses valmis kõikide kontaktide kuvamise vaade. Teenusele lisatud piltide/failide lisamise/pärimise võimalus.
*2013.05.12 – WCF asünkroonsed meetodid asendatud asünkroonsete tööde klientrakenduse poolel.
*2013.05.13 – Otsimise võimalus lisatud.
**Administraatori vaade (kasutajate haldus) klientrakendusele lisatud.
**Logimine andmebaasi lisatud.
**Logimise põhjal päringute arvu piirangud lisatud.
*2013.05.15 – Klientrakendusele üldine veahalduse lisatud.
*2013.05.16 – Teenuse meetodid kommenteeritud.
**Teenuse ja klientrakenduse kohta käiv info Wikisse lisatud.
**Selle logi kirjutamine...

V

2013-05-16T13:20:42Z

Vevainu: /* Veebiteenus */

[[Category:Võrgurakendused II: hajussüsteemide ehitamine]]
=Liige=
Veiko Vainu D21
=Retsensioonid=
==XML==
[https://wiki.itcollege.ee/index.php/Talk:Meeskond_%22asdasdasd%22 Retsensioon meeskond „asdasdasd“ XML-i kohta – 24.03.2013]

[https://wiki.itcollege.ee/index.php/Talk:SaanEndagaH%C3%A4stiL%C3%A4bi Retsensioon meeskond „SaanEndagaHästiLäbi“ XML-i kohta – 24.03.2013]

=XML fail=
==XML andmefail==
*[http://enos.itcollege.ee/~vevainu/XML/armeeXML.xml XML andmefail]

==XML skeemifail==
*[http://enos.itcollege.ee/~vevainu/XML/armeeXML.xsd XML skeemifail]

==XML stiilifailid==
XML to HTML - Kuvab vasakul pool lehte kogu XML-i sisu nn. puuvaates. Paremal pool on otsing, mis otsib sõduri ees- ja perekonnanimest vastavat stringi.
* [http://enos.itcollege.ee/~vevainu/XML/xmlTOhtml.xslt XML to HTML]
* [http://enos.itcollege.ee/~vevainu/XML/xmlTOhtml.xml Näidis]

XML to XML - Trükib välja kõik sõdurid sorteerides perekonnanime ja seejärel eesnime järgi. Igale sõdurile on lisatud ka uus atribuut ID, mis koosneb sõduri ID-st ja tema rühma, allüksuse ja väeosa ID-st.
* [http://enos.itcollege.ee/~vevainu/XML/xmlTOxml.xslt XML to XML]
* [http://enos.itcollege.ee/~vevainu/XML/xmlTOxml.xml Näidis]

XML to Excel - Loob workbooki iga allüksuse jaoks oma worksheeti kuhu kuvatakse selle üksuse isikkooseis sorteeritult Auastme tähestikulises järjekorras.
* [http://enos.itcollege.ee/~vevainu/XML/xmlTOxlsx.xslt XML to Excel]
* [http://enos.itcollege.ee/~vevainu/XML/xmlTOxlsx.xml Näidis XML]
* [http://enos.itcollege.ee/~vevainu/XML/xmlTOxlsxNAIDE.xlsx Näidis EXCEL]
* Kuidas - tuleb xml faili lisada viide vastavale xslt stylesheetile, seejärel tuleb xml fail Excelis avada ja valida, et kasutatakse vastavat stiilifaili.

==XML kõik ühes (.rar)==
*[http://enos.itcollege.ee/~vevainu/XML/XML.rar Kõik failid ühes (.rar)]

=Veebiteenus=

Loodud sai kontaktiraamatu teenus, mis põhineb õppejõu "Telefoniraamatu teenus" näidisteemal.

Teenus on loodud WCF baasil ja kasutab Asp.Net kasutajate autentimist, mille jaoks on vastavad membership- ja roleprovider. Teenus võimaldab ka logimist, mis toimub enne sissetuleva päringu täitmist ning kus kontrollitakse ka kasutaja päringu limiidi ületamist. Teenuse päringud teostatakse Ninject süstimise abil läbi uow (unit-of-work) konteineri, mis omakorda sisaldab repositooriume. Kogu andmekiht on üles ehitatud Entity Framework Code First meetodil.

Teenus pakub järgmisi meetodeid:
* User methods 
** AuthenticateUser - Tries to authenticate the user based on credentials.
*** returns > User object of the user or null if authentication failed.
** GetAuthenticatedMyContact - Gets personal contact object of the querying user.
*** returns > A contact object.
** AddUpdateContact - Add or update contacts infromation.
*** param name="contact" > Contact object to add or update.
*** returns > A contact object with updated fields.
** AddUpdateContactInfo - Add or update contacts contact infromation.
*** param name="contactInfo" > Contact information object to add or update.
*** returns > A contact information object with updated fields.
** AddUpdateContactPicture - Add or update a contacts picture.
***param name="contactId" > Id of the contact to whom we wish to add a picture to or update/replace and existing one.
***param name="picture" > File object of containing the picture we wish to add to a contact.
***returns > A file object with updated fields.
** DeleteContact - Deletes a contact by contact object.
***param name="contact" > Contact object of the contact to delete.
***returns > True if deleteion was successful. False if deletion was unsuccessful.
** DeleteContactById - Deletes a contact by id.
***param name="id" > Id of the contact to delete.
***returns > True if deleteion was successful. False if deletion was unsuccessful.
** DeleteContactInfo - Deletes a contacts contact information by contact information object.
***param name="contact" > ContactInfo object of the contact information to delete.
***returns > True if deleteion was successful. False if deletion was unsuccessful.
** DeleteContactInfoById - Deletes a contacts contact information by contact information id.
***param name="id" > Id of the contact information to delete.
***returns > True if deleteion was successful. False if deletion was unsuccessful.
** GetAllContacts - Gets a list of all contacts of the querying user.
***returns > A list of contact objects.
** GetAllContactInfoTypes - Gets a list of contact information types.
***returns > A list of contactinfotype objects.
** GetAllContactInfoesByContactId - Gets a list of a contacts contact information.
***param name="contactId" > Id of a contact whose contactinformation to retrieve.
***returns > A list of contactinfo objects.
** GetByIdContact - Returns a contacts information.
***param name="id" > Id of the contact whose information to retrieve.
***returns > A contact object
** GetByIdContactPicture - Returns a file object, containing a picture in binary form, of a contact.
***param name="id" > Id of the contact whose picture to retrieve.
***returns > A file object of the contacts picture.
** SearchContactByAny - Searches contacts by name or by contacts information, depending on given input.
***param name="any" > Symbol combination to search by.
***param name="type" > Contact info type name to search by, or all to search by everything.
***returns > A list of contacts matching the search criteria.
** SearchContactByAnyPublic - Searches contacts by name or by contacts information, depending on given input. Also searches publicly available contact (contacts that have IsPublic=True).
***param name="any" > Symbol combination to search by.
***param name="type" > Contact info type name to search by, or all to search by everything.
***returns > A list of contacts matching the search criteria.
* Administrators methods 
** AdminAddUpdateUser - Administrator method, adds or updates a user.
***param name="user" > User object to add or update.
***returns > A user object with updated fields.
** AdminDeleteUser - Administrator method, deletes a user by id. (Sets DeletedOn date to now)
***param name="userId" > Id of the user to delete.
***returns > True if deletion was successful. False if deletion was unsuccessful.
** AdminGetAllUsers - Administrator method, gets a list of all users.
***returns > A list of user objects.
** AdminGetAllUserRoles - Administrator method, gets all possible user roles.
***returns > A list of type user role objects
** AdminGetByIdUser - Administrator method, gets the user object by id.
***param name="userId" > Id of the user whose user data we wish to retrieve.
***returns > A user object.
** AdminGetLogsByUserId - Administrator method, gets a list of logs by user id. Get only the logs from the last 24 hours.
***param name="userId" > Id of the user whose logs to get.
***returns > A list of log objects.

Raskuskohad olid injectimine, nii et ei tekiks konflikte, ning kasutajate päringute hulga ilus piiramine, hetkel lihtsaltkatkestatakse kasutajaga ühendus.

=Klientrakendused=
Klientrakendus on tehtud WPF baasil kasutades peamiselt MVVM (Model-View-ViewModel) lähenemist, mille puhul View kood on enamjaolt tühi. Teenuse kasutamisel igakordse parooli ja kasutajanime sisestamise vältimiseks on teenuse kanali loomine eraldi kapseldatud.

Loodud klientrakendus võimaldab järgnevat:
*Kasutajaid tuvastada
*Kasutajad rolli põhjal eristada ja kuvada erinevaid menüüsid
*Kasutajal kontake lisada ja redigeerida
*Kontaktidele kontaktandmeid lisada ja redigeerida
*Kontaktidele pilte lisada, otse arvutist kui ka veebilinki ette andes
*Kontakte otsida kontakti nime ning kontaktandmete sisu järgi
*Kontakte otsida vaid kindla kontaktandmete tüübi sisu järgi
*Kontakte otsida ka nn. avalike ehk teiste kasutajate kontaktide seast
*Kontaktide määrata avalikuks (teistele nähtav) või mitte-avalikuks
*Administraatoritel lisada ja redigeerida kasutajaid
*Administraatoritel muuta maksimaalsete päringute arvu
*Administraatoritel näha iga kasutaja viimase 24 tunni päringuid (logi)

Raskuskohad olid teenuse asünkroonne kasutamine rakenduses ning võimalike veateadete haldamine.

=Logi=
*2013.03.13 – Sai paika pandud XML faili struktuur ja loodud seda genereeriv rakendus.
*2013.03.14 – XSLT faili loomine, lisatud „Puuvaade“ näitamaks kõiki sisendeid.
*2013.03.15 – XSLT failile inimeste otsing vastavalt kasutaja sisendile lisatud (ainult IE). Sai tehtud XSLT fail XML-i transformeerimiseks teistsuguseks XML-iks ja ka XSLT fail XML-i exceli vorminduse jaoks.
*2013.03.20 – XML to HTML otsing töötab nüüd IE, Chrome ja Firefoxiga
**wiki leht loodud,XML wiki lehele lisatud, tehtud stiilifailide näidised
*2013.03.24 – Teiste tiimide XML tööde retsenseerimine

V

2013-05-16T12:39:37Z

Vevainu: /* Klientrakendused */

[[Category:Võrgurakendused II: hajussüsteemide ehitamine]]
=Liige=
Veiko Vainu D21
=Retsensioonid=
==XML==
[https://wiki.itcollege.ee/index.php/Talk:Meeskond_%22asdasdasd%22 Retsensioon meeskond „asdasdasd“ XML-i kohta – 24.03.2013]

[https://wiki.itcollege.ee/index.php/Talk:SaanEndagaH%C3%A4stiL%C3%A4bi Retsensioon meeskond „SaanEndagaHästiLäbi“ XML-i kohta – 24.03.2013]

=XML fail=
==XML andmefail==
*[http://enos.itcollege.ee/~vevainu/XML/armeeXML.xml XML andmefail]

==XML skeemifail==
*[http://enos.itcollege.ee/~vevainu/XML/armeeXML.xsd XML skeemifail]

==XML stiilifailid==
XML to HTML - Kuvab vasakul pool lehte kogu XML-i sisu nn. puuvaates. Paremal pool on otsing, mis otsib sõduri ees- ja perekonnanimest vastavat stringi.
* [http://enos.itcollege.ee/~vevainu/XML/xmlTOhtml.xslt XML to HTML]
* [http://enos.itcollege.ee/~vevainu/XML/xmlTOhtml.xml Näidis]

XML to XML - Trükib välja kõik sõdurid sorteerides perekonnanime ja seejärel eesnime järgi. Igale sõdurile on lisatud ka uus atribuut ID, mis koosneb sõduri ID-st ja tema rühma, allüksuse ja väeosa ID-st.
* [http://enos.itcollege.ee/~vevainu/XML/xmlTOxml.xslt XML to XML]
* [http://enos.itcollege.ee/~vevainu/XML/xmlTOxml.xml Näidis]

XML to Excel - Loob workbooki iga allüksuse jaoks oma worksheeti kuhu kuvatakse selle üksuse isikkooseis sorteeritult Auastme tähestikulises järjekorras.
* [http://enos.itcollege.ee/~vevainu/XML/xmlTOxlsx.xslt XML to Excel]
* [http://enos.itcollege.ee/~vevainu/XML/xmlTOxlsx.xml Näidis XML]
* [http://enos.itcollege.ee/~vevainu/XML/xmlTOxlsxNAIDE.xlsx Näidis EXCEL]
* Kuidas - tuleb xml faili lisada viide vastavale xslt stylesheetile, seejärel tuleb xml fail Excelis avada ja valida, et kasutatakse vastavat stiilifaili.

==XML kõik ühes (.rar)==
*[http://enos.itcollege.ee/~vevainu/XML/XML.rar Kõik failid ühes (.rar)]

=Veebiteenus=

Loodud sai kontaktiraamatu teenus, mis põhineb õppejõu "Telefoniraamatu teenus" näidisteemal.

Teenus on loodud WCF baasil ja kasutab Asp.Net kasutajate autentimist, mille jaoks on vastavad membership- ja roleprovider. Teenus võimaldab ka logimist, mis toimub enne sissetuleva päringu täitmist ning kus kontrollitakse ka kasutaja päringu limiidi ületamist. Teenuse päringud teostatakse Ninject süstimise abil läbi uow (unit-of-work) konteineri, mis omakorda sisaldab repositooriume. Kogu andmekiht on üles ehitatud Entity Framework Code First meetodil.

Teenus pakub järgmisi meetodeid:
* User methods 
** AuthenticateUser - Tries to authenticate the user based on credentials.
*** returns > User object of the user or null if authentication failed.
** GetAuthenticatedMyContact - Gets personal contact object of the querying user.
*** returns > A contact object.
** AddUpdateContact - Add or update contacts infromation.
*** param name="contact" > Contact object to add or update.
*** returns > A contact object with updated fields.
** AddUpdateContactInfo - Add or update contacts contact infromation.
*** param name="contactInfo" > Contact information object to add or update.
*** returns > A contact information object with updated fields.
** AddUpdateContactPicture - Add or update a contacts picture.
***param name="contactId" > Id of the contact to whom we wish to add a picture to or update/replace and existing one.
***param name="picture" > File object of containing the picture we wish to add to a contact.
***returns > A file object with updated fields.
** DeleteContact - Deletes a contact by contact object.
***param name="contact" > Contact object of the contact to delete.
***returns > True if deleteion was successful. False if deletion was unsuccessful.
** DeleteContactById - Deletes a contact by id.
***param name="id" > Id of the contact to delete.
***returns > True if deleteion was successful. False if deletion was unsuccessful.
** DeleteContactInfo - Deletes a contacts contact information by contact information object.
***param name="contact" > ContactInfo object of the contact information to delete.
***returns > True if deleteion was successful. False if deletion was unsuccessful.
** DeleteContactInfoById - Deletes a contacts contact information by contact information id.
***param name="id" > Id of the contact information to delete.
***returns > True if deleteion was successful. False if deletion was unsuccessful.
** GetAllContacts - Gets a list of all contacts of the querying user.
***returns > A list of contact objects.
** GetAllContactInfoTypes - Gets a list of contact information types.
***returns > A list of contactinfotype objects.
** GetAllContactInfoesByContactId - Gets a list of a contacts contact information.
***param name="contactId" > Id of a contact whose contactinformation to retrieve.
***returns > A list of contactinfo objects.
** GetByIdContact - Returns a contacts information.
***param name="id" > Id of the contact whose information to retrieve.
***returns > A contact object
** GetByIdContactPicture - Returns a file object, containing a picture in binary form, of a contact.
***param name="id" > Id of the contact whose picture to retrieve.
***returns > A file object of the contacts picture.
** SearchContactByAny - Searches contacts by name or by contacts information, depending on given input.
***param name="any" > Symbol combination to search by.
***param name="type" > Contact info type name to search by, or all to search by everything.
***returns > A list of contacts matching the search criteria.
** SearchContactByAnyPublic - Searches contacts by name or by contacts information, depending on given input. Also searches publicly available contact (contacts that have IsPublic=True).
***param name="any" > Symbol combination to search by.
***param name="type" > Contact info type name to search by, or all to search by everything.
***returns > A list of contacts matching the search criteria.
* Administrators methods 
** AdminAddUpdateUser - Administrator method, adds or updates a user.
***param name="user" > User object to add or update.
***returns > A user object with updated fields.
** AdminDeleteUser - Administrator method, deletes a user by id. (Sets DeletedOn date to now)
***param name="userId" > Id of the user to delete.
***returns > True if deletion was successful. False if deletion was unsuccessful.
** AdminGetAllUsers - Administrator method, gets a list of all users.
***returns > A list of user objects.
** AdminGetAllUserRoles - Administrator method, gets all possible user roles.
***returns > A list of type user role objects
** AdminGetByIdUser - Administrator method, gets the user object by id.
***param name="userId" > Id of the user whose user data we wish to retrieve.
***returns > A user object.
** AdminGetLogsByUserId - Administrator method, gets a list of logs by user id. Get only the logs from the last 24 hours.
***param name="userId" > Id of the user whose logs to get.
***returns > A list of log objects.

=Klientrakendused=
Klientrakendus on tehtud WPF baasil kasutades peamiselt MVVM (Model-View-ViewModel) lähenemist, mille puhul View kood on enamjaolt tühi. Teenuse kasutamisel igakordse parooli ja kasutajanime sisestamise vältimiseks on teenuse kanali loomine eraldi kapseldatud.

Loodud klientrakendus võimaldab järgnevat:
*Kasutajaid tuvastada
*Kasutajad rolli põhjal eristada ja kuvada erinevaid menüüsid
*Kasutajal kontake lisada ja redigeerida
*Kontaktidele kontaktandmeid lisada ja redigeerida
*Kontaktidele pilte lisada, otse arvutist kui ka veebilinki ette andes
*Kontakte otsida kontakti nime ning kontaktandmete sisu järgi
*Kontakte otsida vaid kindla kontaktandmete tüübi sisu järgi
*Kontakte otsida ka nn. avalike ehk teiste kasutajate kontaktide seast
*Kontaktide määrata avalikuks (teistele nähtav) või mitte-avalikuks
*Administraatoritel lisada ja redigeerida kasutajaid
*Administraatoritel muuta maksimaalsete päringute arvu
*Administraatoritel näha iga kasutaja viimase 24 tunni päringuid (logi)

Raskuskohad olid teenuse asünkroonne kasutamine rakenduses ning võimalike veateadete haldamine.

=Logi=
*2013.03.13 – Sai paika pandud XML faili struktuur ja loodud seda genereeriv rakendus.
*2013.03.14 – XSLT faili loomine, lisatud „Puuvaade“ näitamaks kõiki sisendeid.
*2013.03.15 – XSLT failile inimeste otsing vastavalt kasutaja sisendile lisatud (ainult IE). Sai tehtud XSLT fail XML-i transformeerimiseks teistsuguseks XML-iks ja ka XSLT fail XML-i exceli vorminduse jaoks.
*2013.03.20 – XML to HTML otsing töötab nüüd IE, Chrome ja Firefoxiga
**wiki leht loodud,XML wiki lehele lisatud, tehtud stiilifailide näidised
*2013.03.24 – Teiste tiimide XML tööde retsenseerimine

V

2013-05-16T12:22:59Z

Vevainu: /* Veebiteenus */

Team Robo

2013-04-05T08:25:17Z

Vevainu: /* Results */

Team page for [[Deploying IT Infrastructure Solutions]].

==Team Members==
* Veiko Vainu, IT College
* Andreas Plado, IT College
* Giorgos Ioannidis, T.E.I. of Crete, Department Of Applied Informatics And Multimedia
* Konstantinos Michailidis, T.E.I. of Crete, Department Of Applied Informatics And Multimedia

==Goal==
*System design description, including:
**Component diagram
**Database diagram
**Sequence diagram
*Suggestion on database, programming language and reusable components.
*Creating a project time plan with at least two scenarios:
**Full scope
**Minimum scope
*BONUS:
**Prototype solution covering some part of the system.

==Activity==
===Monday - 25.03.13===
Things what we did that day
* Participate in lectures
* Learn
* We get to know each other through the exercises.

===Tuesday - 26.03.13===
Things what we did that day
* Composed a set of questions for the client.
* Started making a draft scenario for the client.
* Researched similar systems.

Problems what we faced:
* Lack of project details

Things what we plan to do:
* Client meeting

===Wednesday - 27.03.13===
Things what we did that day
* Met with the client
* Clarified project details
* We made the activity chart
* We divided roles

Problems what we faced:
* We didn't have problems today

Questions and answers from client:
* We asked the basic structure of the outcome
The outcome supposed to be the analysis part of the software.

Things what we plan to do:
* Continiue with undertaking the subtasks of the project
* [https://wiki.itcollege.ee/images/9/97/Tasks.pdf Tasks List.pdf]

===Thursday - 28.03.13===
Things what we did that day
* Analyse the whole scenario
* Started making the use-case diagram

Problems what we faced:
* We didn´t expect the scenario to be so complicated

Things what we plan to do:
* Finish the use-case diagram
* Start with class-diagram

===Friday - 29.03.13===
Things what we did that day
* Finalized the use-case diagrams
* Completed the first draft of the class diagram
* Design the ERD diagram
* Started creating the final analysis documentation

Problems what we faced:
* The database was more complicated than we expected

Things what we plan to do:
* Finalize the class diagram
* Finalize the first draft of final documentation as a deliverable for our client meeting

===Monday - 01.04.13===
Things what we did that day:
*Finalized the system class diagram
*Completed the ERD diagram
*Continue creating the final analysis documentation
*Start creating mockups with mock up builder tool for each one of use cases

Problems what we faced:

Things what we plan to do:
*Finalize the documentation
*Meeting with customer at 19:00 today and find out next steps of the Project

===Tuesday- 02.04.13===
Things what we did that day:
*(Yesterday)Met with the client to get feedback on what has been done so far, and what should we do from here on.
*Finalized the description of the use-cases
*Made changes to the ERD diagram
*Made changes to the system class diagram
*Completed most of the final analysis documentation
*Researched information about possible prototype implementation

Problems what we faced:
*One of our team members computer malfunctioned

Things what we plan to do:
*Make a presentation for the final client meeting
*Practice presenting the final work
*Finalize the documentation
*Make a prototype of a part of the system (double elimination tree generation)

===Wednesday- 03.04.13===
Things what we did that day:
*Complete documentation
*Some prototype about match score editing and double elimination tree editing.
*Scoreboard with static array (NO database implemented)

We made improvements in the documentation:
*Finalizing mockups
*Find some useful information about prototype implementation

Things what we plan to do:
*Prototype about double elimination tree and match editing
*Finalizing documentation

===Thursday- 04.04.13===

Things what we did that day:
*SPS Documentation:Done
*Prototype about double elimination tree editing:Done in C sharp
*Sample in Html Web Page for double elimination tree
*Complete the Final Presentation

Things what we plan to do:
*Deliver Documentation,vpp files and Html Page

==Results==
First we have made the uses, cases, ERD-diagram, Class diagram, which are all in one Visual Paradigm project file. All of this is also described in more detail in the final documentation.

[http://www.upload.ee/files/3206025/Robotic_Project_v3.vpp.html Visual Paradigm project files]

Second we made a time plan in the form of a Task List.

[http://www.upload.ee/files/3206026/Task_List.xls.html Task List]

Third we have a prototype for creating double-elimination tree structure.

[http://www.upload.ee/files/3206023/DITS2013.zip.html Java source for creating elimination tree]

===Final documentation===

[https://wiki.itcollege.ee/images/c/c4/Final_RoboTeam_documentation.pdf SRS Documentation (IEEE Std 830-1998)]

==IP Feed-back==

===Konstantinos Michailidis===
First of all, I would like to thank everyone, which has participated to organize the program, for our accomodation etc...
I was the SE project manager of the Robotics team. Also I participate in the developing section as well.
I make the activity chart, some use case diagrams and the class diagram.
At last, I participate to create the final documentation and presentation and export the final edition of its one.
The most important part of this new experience was the collaboration with other students, that we did not know but the too intensive schedule did not let us come closer and have fun...

===Giorgos Ioannidis===
Many thanks to everyone which has participate and organize this program!
I was just a brick on the wall..As always,i like to help/learn in/from several tasks.
So,in the Robotics System team i had the opportunity to work in a real time Software Analysis/Implementation with multicultural persons.
I create:
*Class Diagrams(part)
*Use Cases(part)
*Software Requirements Specification Documentation
*Tasks Listing
*some Java programming & Html(part)
*the intro of the final Presentation.
*Wiki Page(part)

The most important part of this team work that took place with other students, was to learn-share-live experiences from Life & Technology.
That's all folks!

===Andreas Plado===
I would like to thank all of our teammates for the great job. During this course i learned a lot about software analysis. At first i was bit disappointed doing only documentation during the software making process. But later on i get used to it and i had also opportunity to learn some programming. Also i learned to communicate with different nationalities around the Europe and i saw their culture and different point of views. It can be said that i had overcome with one of my biggest fears - doing live presentations in front of the audience. I think this course was really helpful for me and i would like to use more opportunities to take part of that kind of studies. If i take part of these kind of studies i hope to do actual programs to be more satisfied with the project. Unfortunately time limitations are big problem in that kind of projects.

===Veiko Vainu===
At first we started making the use case´s, all together, as they´re the cornerstone of a good analysis. When we had the initial use case´s done, we started dividing upcoming tasks to finish them faster. I had a decent part in creating the ERD-diagram, and also the major role in describing the uses case´s through the scenarios. My final and biggest input, in my opinion, was the creation of the prototype. The prototype, in our case, was a bonus task and was supposed to be a proof of concept, and not in any way an implementable part of the system.

From the start, after a few days I realized that our projects main goal, the analysis part, isn´t going to be only a few hours of work. At first this was unanticipated, but at the end when we started to do an implementation I could see the analysis part speeding up and easing the process. The analysis helped, but we also started to see flaws in it, we should have starting making implementations based on the analysis earlier. Overall I really liked the experience of working in a multicultural team and communication in a non-native language, English. For the lectures that we had, I personally think that a few of them were a bit too general and could have been more deep/advanced, though I understand that with a large amount of students with different backgrounds this could´ve been risky. Overall I had a good time while working and during leisure activities. I´d like to thank the organizers for this interesting and rich experience.

Team Robo

2013-04-05T08:08:57Z

Vevainu: /* Results */

Team page for [[Deploying IT Infrastructure Solutions]].

==Team Members==
* Veiko Vainu, IT College
* Andreas Plado, IT College
* Giorgos Ioannidis, T.E.I. of Crete, Department Of Applied Informatics And Multimedia
* Konstantinos Michailidis, T.E.I. of Crete, Department Of Applied Informatics And Multimedia

==Goal==
*System design description, including:
**Component diagram
**Database diagram
**Sequence diagram
*Suggestion on database, programming language and reusable components.
*Creating a project time plan with at least two scenarios:
**Full scope
**Minimum scope
*BONUS:
**Prototype solution covering some part of the system.

==Activity==
===Monday - 25.03.13===
Things what we did that day
* Participate in lectures
* Learn
* We get to know each other through the exercises.

===Tuesday - 26.03.13===
Things what we did that day
* Composed a set of questions for the client.
* Started making a draft scenario for the client.
* Researched similar systems.

Problems what we faced:
* Lack of project details

Things what we plan to do:
* Client meeting

===Wednesday - 27.03.13===
Things what we did that day
* Met with the client
* Clarified project details
* We made the activity chart
* We divided roles

Problems what we faced:
* We didn't have problems today

Questions and answers from client:
* We asked the basic structure of the outcome
The outcome supposed to be the analysis part of the software.

Things what we plan to do:
* Continiue with undertaking the subtasks of the project
* [https://wiki.itcollege.ee/images/9/97/Tasks.pdf Tasks List.pdf]

===Thursday - 28.03.13===
Things what we did that day
* Analyse the whole scenario
* Started making the use-case diagram

Problems what we faced:
* We didn´t expect the scenario to be so complicated

Things what we plan to do:
* Finish the use-case diagram
* Start with class-diagram

===Friday - 29.03.13===
Things what we did that day
* Finalized the use-case diagrams
* Completed the first draft of the class diagram
* Design the ERD diagram
* Started creating the final analysis documentation

Problems what we faced:
* The database was more complicated than we expected

Things what we plan to do:
* Finalize the class diagram
* Finalize the first draft of final documentation as a deliverable for our client meeting

===Monday - 01.04.13===
Things what we did that day:
*Finalized the system class diagram
*Completed the ERD diagram
*Continue creating the final analysis documentation
*Start creating mockups with mock up builder tool for each one of use cases

Problems what we faced:

Things what we plan to do:
*Finalize the documentation
*Meeting with customer at 19:00 today and find out next steps of the Project

===Tuesday- 02.04.13===
Things what we did that day:
*(Yesterday)Met with the client to get feedback on what has been done so far, and what should we do from here on.
*Finalized the description of the use-cases
*Made changes to the ERD diagram
*Made changes to the system class diagram
*Completed most of the final analysis documentation
*Researched information about possible prototype implementation

Problems what we faced:
*One of our team members computer malfunctioned

Things what we plan to do:
*Make a presentation for the final client meeting
*Practice presenting the final work
*Finalize the documentation
*Make a prototype of a part of the system (double elimination tree generation)

===Wednesday- 03.04.13===
Things what we did that day:
*Complete documentation
*Some prototype about match score editing and double elimination tree editing.
*Scoreboard with static array (NO database implemented)

We made improvements in the documentation:
*Finalizing mockups
*Find some useful information about prototype implementation

Things what we plan to do:
*Prototype about double elimination tree and match editing
*Finalizing documentation

===Thursday- 04.04.13===

Things what we did that day:
*SPS Documentation:Done
*Prototype about double elimination tree editing:Done in C sharp
*Sample in Html Web Page for double elimination tree
*Complete the Final Presentation

Things what we plan to do:
*Deliver Documentation,vpp files and Html Page

==Results==
First we have made the uses, cases, ERD-diagram, Class diagram, which are all in one Visual Paradigm project file. All of this is also described in more detail in the final documentation.
[http://www.upload.ee/files/3206025/Robotic_Project_v3.vpp.html Visual Paradigm project files]

Second we made a time plan in the form of a Task List.
[http://www.upload.ee/files/3206026/Task_List.xls.html Task List]

Third we have a prototype for creating double-elimination tree structure.
[http://www.upload.ee/files/3206023/DITS2013.zip.html Java source for creating elimination tree]

===Final documentation===

[https://wiki.itcollege.ee/images/c/c4/Final_RoboTeam_documentation.pdf SRS Documentation (IEEE Std 830-1998)]

==IP Feed-back==

===Konstantinos Michailidis===
First of all, I would like to thank everyone, which has participated to organize the program, for our accomodation etc...
I was the SE project manager of the Robotics team. Also I participate in the developing section as well.
I make the activity chart, some use case diagrams and the class diagram.
At last, I participate to create the final documentation and presentation and export the final edition of its one.
The most important part of this new experience was the collaboration with other students, that we did not know but the too intensive schedule did not let us come closer and have fun...

===Giorgos Ioannidis===
Many thanks to everyone which has participate and organize this program!
I was just a brick on the wall..As always,i like to help/learn in/from several tasks.
So,in the Robotics System team i had the opportunity to work in a real time Software Analysis/Implementation with multicultural persons.
I create:
*Class Diagrams(part)
*Use Cases(part)
*Software Requirements Specification Documentation
*Tasks Listing
*some Java programming & Html(part)
*the intro of the final Presentation.
*Wiki Page(part)

The most important part of this team work that took place with other students, was to learn-share-live experiences from Life & Technology.
That's all folks!

===Andreas Plado===
I would like to thank all of our teammates for the great job. During this course i learned a lot about software analysis. At first i was bit disappointed doing only documentation during the software making process. But later on i get used to it and i had also opportunity to learn some programming. Also i learned to communicate with different nationalities around the Europe and i saw their culture and different point of views. It can be said that i had overcome with one of my biggest fears - doing live presentations in front of the audience. I think this course was really helpful for me and i would like to use more opportunities to take part of that kind of studies. If i take part of these kind of studies i hope to do actual programs to be more satisfied with the project. Unfortunately time limitations are big problem in that kind of projects.

===Veiko Vainu===
At first we started making the use case´s, all together, as they´re the cornerstone of a good analysis. When we had the initial use case´s done, we started dividing upcoming tasks to finish them faster. I had a decent part in creating the ERD-diagram, and also the major role in describing the uses case´s through the scenarios. My final and biggest input, in my opinion, was the creation of the prototype. The prototype, in our case, was a bonus task and was supposed to be a proof of concept, and not in any way an implementable part of the system.

From the start, after a few days I realized that our projects main goal, the analysis part, isn´t going to be only a few hours of work. At first this was unanticipated, but at the end when we started to do an implementation I could see the analysis part speeding up and easing the process. The analysis helped, but we also started to see flaws in it, we should have starting making implementations based on the analysis earlier. Overall I really liked the experience of working in a multicultural team and communication in a non-native language, English. For the lectures that we had, I personally think that a few of them were a bit too general and could have been more deep/advanced, though I understand that with a large amount of students with different backgrounds this could´ve been risky. Overall I had a good time while working and during leisure activities. I´d like to thank the organizers for this interesting and rich experience.

Team Robo

2013-04-05T07:16:19Z

Vevainu: /* Results */

Team page for [[Deploying IT Infrastructure Solutions]].

==Team Members==
* Veiko Vainu, IT College
* Andreas Plado, IT College
* Giorgos Ioannidis, T.E.I. of Crete, Department Of Applied Informatics And Multimedia
* Konstantinos Michailidis, T.E.I. of Crete, Department Of Applied Informatics And Multimedia

==Goal==
*System design description, including:
**Component diagram
**Database diagram
**Sequence diagram
*Suggestion on database, programming language and reusable components.
*Creating a project time plan with at least two scenarios:
**Full scope
**Minimum scope
*BONUS:
**Prototype solution covering some part of the system.

==Activity==
===Monday - 25.03.13===
Things what we did that day
* Participate in lectures
* Learn
* We get to know each other through the exercises.

===Tuesday - 26.03.13===
Things what we did that day
* Composed a set of questions for the client.
* Started making a draft scenario for the client.
* Researched similar systems.

Problems what we faced:
* Lack of project details

Things what we plan to do:
* Client meeting

===Wednesday - 27.03.13===
Things what we did that day
* Met with the client
* Clarified project details
* We made the activity chart
* We divided roles

Problems what we faced:
* We didn't have problems today

Questions and answers from client:
* We asked the basic structure of the outcome
The outcome supposed to be the analysis part of the software.

Things what we plan to do:
* Continiue with undertaking the subtasks of the project
* [https://wiki.itcollege.ee/images/9/97/Tasks.pdf Tasks List.pdf]

===Thursday - 28.03.13===
Things what we did that day
* Analyse the whole scenario
* Started making the use-case diagram

Problems what we faced:
* We didn´t expect the scenario to be so complicated

Things what we plan to do:
* Finish the use-case diagram
* Start with class-diagram

===Friday - 29.03.13===
Things what we did that day
* Finalized the use-case diagrams
* Completed the first draft of the class diagram
* Design the ERD diagram
* Started creating the final analysis documentation

Problems what we faced:
* The database was more complicated than we expected

Things what we plan to do:
* Finalize the class diagram
* Finalize the first draft of final documentation as a deliverable for our client meeting

===Monday - 01.04.13===
Things what we did that day:
*Finalized the system class diagram
*Completed the ERD diagram
*Continue creating the final analysis documentation
*Start creating mockups with mock up builder tool for each one of use cases

Problems what we faced:

Things what we plan to do:
*Finalize the documentation
*Meeting with customer at 19:00 today and find out next steps of the Project

===Tuesday- 02.04.13===
Things what we did that day:
*(Yesterday)Met with the client to get feedback on what has been done so far, and what should we do from here on.
*Finalized the description of the use-cases
*Made changes to the ERD diagram
*Made changes to the system class diagram
*Completed most of the final analysis documentation
*Researched information about possible prototype implementation

Problems what we faced:
*One of our team members computer malfunctioned

Things what we plan to do:
*Make a presentation for the final client meeting
*Practice presenting the final work
*Finalize the documentation
*Make a prototype of a part of the system (double elimination tree generation)

===Wednesday- 03.04.13===
Things what we did that day:
*Complete documentation
*Some prototype about match score editing and double elimination tree editing.
*Scoreboard with static array (NO database implemented)

We made improvements in the documentation:
*Finalizing mockups
*Find some useful information about prototype implementation

Things what we plan to do:
*Prototype about double elimination tree and match editing
*Finalizing documentation

===Thursday- 04.04.13===

Things what we did that day:
*SPS Documentation:Done
*Prototype about double elimination tree editing:Done in C sharp
*Sample in Html Web Page for double elimination tree
*Complete the Final Presentation

Things what we plan to do:
*Deliver Documentation,vpp files and Html Page

==Results==
Summary of what we did and solution what we developed

[http://www.upload.ee/files/3206025/Robotic_Project_v3.vpp.html Visual Paradigm project files]

[http://www.upload.ee/files/3206026/Task_List.xls.html Task List]

[http://www.upload.ee/files/3206023/DITS2013.zip.html Java source for creating elimination tree]

===Final documentation===

[https://wiki.itcollege.ee/images/c/c4/Final_RoboTeam_documentation.pdf SRS Documentation (IEEE Std 830-1998)]

==IP Feed-back==

===Konstantinos Michailidis===
First of all, I would like to thank everyone, which has participated to organize the program, for our accomodation etc...
I was the SE project manager of the Robotics team. Also I participate in the developing section as well.
I make the activity chart, some use case diagrams and the class diagram.
At last, I participate to create the final documentation and presentation and export the final edition of its one.
The most important part of this new experience was the collaboration with other students, that we did not know but the too intensive schedule did not let us come closer and have fun...

===Giorgos Ioannidis===
Many thanks to everyone which has participate and organize this program!
I was just a brick on the wall..As always,i like to help/learn in/from several tasks.
So,in the Robotics System team i had the opportunity to work in a real time Software Analysis/Implementation with multicultural persons.
I create:
*Class Diagrams(part)
*Use Cases(part)
*Software Requirements Specification Documentation
*Tasks Listing
*some Java programming & Html(part)
*the intro of the final Presentation.
*Wiki Page(part)

The most important part of this team work that took place with other students, was to learn-share-live experiences from Life & Technology.
That's all folks!

===Andreas Plado===
I would like to thank all of our teammates for the great job. During this course i learned a lot about software analysis. At first i was bit disappointed doing only documentation during the software making process. But later on i get used to it and i had also opportunity to learn some programming. Also i learned to communicate with different nationalities around the Europe and i saw their culture and different point of views. It can be said that i had overcome with one of my biggest fears - doing live presentations in front of the audience. I think this course was really helpful for me and i would like to use more opportunities to take part of that kind of studies. If i take part of these kind of studies i hope to do actual programs to be more satisfied with the project. Unfortunately time limitations are big problem in that kind of projects.

===Veiko Vainu===
At first we started making the use case´s, all together, as they´re the cornerstone of a good analysis. When we had the initial use case´s done, we started dividing upcoming tasks to finish them faster. I had a decent part in creating the ERD-diagram, and also the major role in describing the uses case´s through the scenarios. My final and biggest input, in my opinion, was the creation of the prototype. The prototype, in our case, was a bonus task and was supposed to be a proof of concept, and not in any way an implementable part of the system.

From the start, after a few days I realized that our projects main goal, the analysis part, isn´t going to be only a few hours of work. At first this was unanticipated, but at the end when we started to do an implementation I could see the analysis part speeding up and easing the process. The analysis helped, but we also started to see flaws in it, we should have starting making implementations based on the analysis earlier. Overall I really liked the experience of working in a multicultural team and communication in a non-native language, English. For the lectures that we had, I personally think that a few of them were a bit too general and could have been more deep/advanced, though I understand that with a large amount of students with different backgrounds this could´ve been risky. Overall I had a good time while working and during leisure activities. I´d like to thank the organizers for this interesting and rich experience.

File:Task List.xls

2013-04-05T07:03:14Z

Vevainu:

Team Robo

2013-04-05T06:50:47Z

Vevainu: /* Veiko Vainu */

Team page for [[Deploying IT Infrastructure Solutions]].

==Team Members==
* Veiko Vainu, IT College
* Andreas Plado, IT College
* Giorgos Ioannidis, T.E.I. of Crete, Department Of Applied Informatics And Multimedia
* Konstantinos Michailidis, T.E.I. of Crete, Department Of Applied Informatics And Multimedia

==Goal==
*System design description, including:
**Component diagram
**Database diagram
**Sequence diagram
*Suggestion on database, programming language and reusable components.
*Creating a project time plan with at least two scenarios:
**Full scope
**Minimum scope
*BONUS:
**Prototype solution covering some part of the system.

==Activity==
===Monday - 25.03.13===
Things what we did that day
* Participate in lectures
* Learn
* We get to know each other through the exercises.

===Tuesday - 26.03.13===
Things what we did that day
* Composed a set of questions for the client.
* Started making a draft scenario for the client.
* Researched similar systems.

Problems what we faced:
* Lack of project details

Things what we plan to do:
* Client meeting

===Wednesday - 27.03.13===
Things what we did that day
* Met with the client
* Clarified project details
* We made the activity chart
* We divided roles

Problems what we faced:
* We didn't have problems today

Questions and answers from client:
* We asked the basic structure of the outcome
The outcome supposed to be the analysis part of the software.

Things what we plan to do:
* Continiue with undertaking the subtasks of the project
* [https://wiki.itcollege.ee/images/9/97/Tasks.pdf Tasks List.pdf]

===Thursday - 28.03.13===
Things what we did that day
* Analyse the whole scenario
* Started making the use-case diagram

Problems what we faced:
* We didn´t expect the scenario to be so complicated

Things what we plan to do:
* Finish the use-case diagram
* Start with class-diagram

===Friday - 29.03.13===
Things what we did that day
* Finalized the use-case diagrams
* Completed the first draft of the class diagram
* Design the ERD diagram
* Started creating the final analysis documentation

Problems what we faced:
* The database was more complicated than we expected

Things what we plan to do:
* Finalize the class diagram
* Finalize the first draft of final documentation as a deliverable for our client meeting

===Monday - 01.04.13===
Things what we did that day:
*Finalized the system class diagram
*Completed the ERD diagram
*Continue creating the final analysis documentation
*Start creating mockups with mock up builder tool for each one of use cases

Problems what we faced:

Things what we plan to do:
*Finalize the documentation
*Meeting with customer at 19:00 today and find out next steps of the Project

===Tuesday- 02.04.13===
Things what we did that day:
*(Yesterday)Met with the client to get feedback on what has been done so far, and what should we do from here on.
*Finalized the description of the use-cases
*Made changes to the ERD diagram
*Made changes to the system class diagram
*Completed most of the final analysis documentation
*Researched information about possible prototype implementation

Problems what we faced:
*One of our team members computer malfunctioned

Things what we plan to do:
*Make a presentation for the final client meeting
*Practice presenting the final work
*Finalize the documentation
*Make a prototype of a part of the system (double elimination tree generation)

===Wednesday- 03.04.13===
Things what we did that day:
*Complete documentation
*Some prototype about match score editing and double elimination tree editing.
*Scoreboard with static array (NO database implemented)

We made improvements in the documentation:
*Finalizing mockups
*Find some useful information about prototype implementation

Things what we plan to do:
*Prototype about double elimination tree and match editing
*Finalizing documentation

===Thursday- 04.04.13===

Things what we did that day:
*SPS Documentation:Done
*Prototype about double elimination tree editing:Done in C sharp
*Sample in Html Web Page for double elimination tree
*Complete the Final Presentation

Things what we plan to do:
*Deliver Documentation,vpp files and Html Page

==Results==
Summary of what we did and solution what we developed

===Final documentation===

[https://wiki.itcollege.ee/images/c/c4/Final_RoboTeam_documentation.pdf SRS Documentation (IEEE Std 830-1998)]

==IP Feed-back==

===Konstantinos Michailidis===
First of all, I would like to thank everyone, which has participated to organize the program, for our accomodation etc...
I was the SE project manager of the Robotics team. Also I participate in the developing section as well.
I make the activity chart, some use case diagrams and the class diagram.
At last, I participate to create the final documentation and presentation and export the final edition of its one.
The most important part of this new experience was the collaboration with other students, that we did not know but the too intensive schedule did not let us come closer and have fun...

===Giorgos Ioannidis===
Many thanks to everyone which has participate and organize this program!
I was just a brick on the wall..As always,i like to help/learn in/from several tasks.
So,in the Robotics System team i had the opportunity to work in a real time Software Analysis/Implementation with multicultural persons.
I create:
*Class Diagrams(part)
*Use Cases(part)
*Software Requirements Specification Documentation
*Tasks Listing
*some Java programming & Html(part)
*the intro of the final Presentation.
*Wiki Page(part)

The most important part of this team work that took place with other students, was to learn-share-live experiences from Life & Technology.
That's all folks!

===Andreas Plado===
I would like to thank all of our teammates for the great job. During this course i learned a lot about software analysis. At first i was bit disappointed doing only documentation during the software making process. But later on i get used to it and i had also opportunity to learn some programming. Also i learned to communicate with different nationalities around the Europe and i saw their culture and different point of views. It can be said that i had overcome with one of my biggest fears - doing live presentations in front of the audience. I think this course was really helpful for me and i would like to use more opportunities to take part of that kind of studies. If i take part of these kind of studies i hope to do actual programs to be more satisfied with the project. Unfortunately time limitations are big problem in that kind of projects.

===Veiko Vainu===
At first we started making the use case´s, all together, as they´re the cornerstone of a good analysis. When we had the initial use case´s done, we started dividing upcoming tasks to finish them faster. I had a decent part in creating the ERD-diagram, and also the major role in describing the uses case´s through the scenarios. My final and biggest input, in my opinion, was the creation of the prototype. The prototype, in our case, was a bonus task and was supposed to be a proof of concept, and not in any way an implementable part of the system.

From the start, after a few days I realized that our projects main goal, the analysis part, isn´t going to be only a few hours of work. At first this was unanticipated, but at the end when we started to do an implementation I could see the analysis part speeding up and easing the process. The analysis helped, but we also started to see flaws in it, we should have starting making implementations based on the analysis earlier. Overall I really liked the experience of working in a multicultural team and communication in a non-native language, English. For the lectures that we had, I personally think that a few of them were a bit too general and could have been more deep/advanced, though I understand that with a large amount of students with different backgrounds this could´ve been risky. Overall I had a good time while working and during leisure activities. I´d like to thank the organizers for this interesting and rich experience.

Team Robo

2013-04-04T07:41:32Z

Vevainu: /* Results */

File:Final RoboTeam documentation.pdf

2013-04-04T07:39:00Z

Vevainu:

Team Robo

2013-04-02T13:50:02Z

Vevainu: /* Tuesday- 02.04.13 */

Team Robo

2013-04-02T13:48:37Z

Vevainu: /* Monday - 01.04.13 */

Team Robo

2013-04-01T13:55:04Z

Vevainu: /* Monday - 01.04.13 */

Team Robo

2013-04-01T13:47:05Z

Vevainu: /* Monday - 01.04.13 */

Team Robo

2013-04-01T13:41:23Z

Vevainu: /* Monday - 01.04.13 */

Team Robo

2013-04-01T13:38:08Z

Vevainu: /* Activity */

Team Robo

2013-03-29T15:38:17Z

Vevainu: /* Goal */

Team Robo

2013-03-29T14:57:40Z

Vevainu: /* IP Feed-back */

Team Robo

2013-03-29T14:09:12Z

Vevainu: /* Friday - 29.03.13 */

Team Robo

2013-03-29T07:37:19Z

Vevainu: /* Thursday - 28.03.13 */

Team Robo

2013-03-29T07:34:22Z

Vevainu: /* Activity */

V

2013-03-27T18:43:38Z

Vevainu: /* Logi */

Deploying IT Infrastructure Solutions 2013

2013-03-27T18:26:13Z

Vevainu: /* Team Robo */

[[Category: Õppetöö]]
[[File:EL_Sotsiaalfond_horisontaal_small.jpg‎‎|right|text-top]]
 
----
__TOC__

----
This is the student results wiki page for the IP program [http://www.itcollege.ee/en/co-operation/dits2013/ "Deploying IT Infrastructure Solutions"] taking place from 24th of March until 6th of April 2013.

All the information regarding program will be presented in the program [http://www.itcollege.ee/en/co-operation/dits2013/ web page].

=Assignments=

==Security testing of web application==

===Description===
Learn about the security of web applications.
Find vulnerabilities from known vulnerable web applications.
Find not known vulnerabilities of development version of web application
Study Information Portal (Used by eleven universities of applied
science in Estonia)
File report that describes methods, tests and findings.

===Expected outcome===
Description of testing methods and findings (all vulnerabilities that
students found in development environment) as testing report.

===Expectations from students===
Understanding web applications (What is difference of GET and POST, how
sessions work, what is header etc).
Knowledge of at least one web programming language (php, java, ruby, C#, python is preferred)

===Lectures support===
Several security related topics will covered during lectures and
practical classes before starting actual testing.
Lecture covers several attack types and vulnerabilities like SQL
injection, cmd injection, XSS, CSRF etc. Practical classes based on DVWA
(Damn Vulnerable Web Application)
After lectures and practical classes students will get access to web
application development environment for practical work.

[http://elab.itcollege.ee:8000/DITS2013/ Lecture/Lab materials and virtual machines]

Lecturer: Margus Ernits (Estonian IT College)

==Driving lessons registration information system==

===Description===
It is a client-server solution which keeps records of student's driving lessons.
Each driving study car has a device / computer where client application runs.

===Expected outcome===
Client application registers the student’s driving lesson time and the GPS
coordinates and sends them to the server over the mobile Internet.
Client application must register driving lessons also without Internet connection
and synchronize with the server when connection is established.
Later a student can check ones driving lesson and travel route on the Internet.

===Limitations===
GPS accuracy at least one point per second.

==Improving toolset for race sailing performance analysis==

===Description===
Implementation of logger that could be used for performance analysis of race sailing teams,
based on data specification for communication between marine electronic devices NMEA
0183.
Learning about the performance analysis needs and specifics of race sailing teams, also
learning about the marine instruments specifics and communication standard NMEA 0183.
Based on core architecture of the NMEA 0183 data logger implementation including
software, hardware and testing.

===Expected outcome===
Fully functioning and tested race sailing performance analysis data logger.

===Expectations from students===
Aspiration to develop in rapid prototyping and testing environment together with professional
and Olympic Team race sailors and marine technology specialists fully functional
performance analysis logger. Both software and hardware development skills. If you can
understand and are interested in what is described
at http://www.boatdesign.net/forums/attachments/onboard-electronics-controls/19260d1204757550-laptop-interface-tacktick-nmea-architecture.png then you are
expected to join team.

===Lectures support===
Lectures and seminars will cover first the needs specification of the performance analysis
logger, NMEA0183 standard description, marine instruments Received Sentences description:
DBT, DPT, GLL, HDG, HDM, MTW, MWV, RMB, RMC, VHW, VLW, VWR. Team will
implement the logger and install the marine wireless range instrument for testing on actual
performance sailing boat. Life saving equipment and wetsuits not needed :)

Lecturer: Linnar Viik (Estonian IT College)

==Robotic competitions organization software system==

===Description===
The software system provides everything from participant registration to the live competition carry out
by the referees. It contains web based interfaces and real-time applications such as score and time
overlay on video broadcast. Different competition (tournament) formats are needed. As much as
possible smart solutions and freely available components shall be used in order to keep the
development time short.

===Expected outcome===
System design description including component, database and sequence diagrams. Suggestion on
database, programming language and reusable components is expected. Creating a project time plan
with at least two scenarios (full scope, minimum scope) is secondary objective. Prototype solution
covering some part of the system would be a bonus task.

===Expectations from students===
Knowledge of database- and web programming. Understanding of software architectures such as MV is
appreciated.

==E-teacher==

In the course of studying Database Fundamentals the students, as independent coursework, must draw ERD-
schemes. Although there is no use of drawing the diagrams if the lector doesn’t give feedback on the success
or failure of said work. The whole process of drawing ERD-diagrams looks like any other teaching process-
The teacher prepares the task, the student draws the ERD-diagram and hands it to the teacher, The teacher
then looks it over and corrects/improves/comments it then returning it to the student. The specificity in here
being that the solutions of the tasks are graphic and no task has one concrete solution – every student solution
is different. This makes every revision unique- the teacher must understand the undergrads intention, check
its compliance whit the task set and then if needed make changes in the model without changing its nature.

For now it has always been done on paper – Undergrad draws a ERD case system model, prints it and hands
it to the lecturer; the lecturer, if needed, corrects it with a pen , writes their comments and the non-grading
evaluation and returns it to the undergrad. The lector marks the results of the test in their ÕIS table.

This process doesn’t exist electronically because during the semester there are many undergrads (ca 140-150)
and there are no comfortable ways to grade them QUICKLY electronically. Herewith, when the lector gets
the work printed on paper he is capable of correcting them with haste. Hence it raises two main problems that
need solving. The Schemes sent on paper must be replaced by electronically forwardable materials and a way
to revise/correct electronically presented ERD quick must be created.

Past couple of years have brought with them the development of portable computer user interface – There are
touch screens and electronic pens, with which one can draw on a computer screen. From there springs the
thought, of making an application for correction of such works, where the lector writes the
corrections/notes/comments directly on the work presented by the undergrad. Using an electronic pen.

The process itself should look like this:
# The undergrad creates an ERD‐diagram and presents it in some from, that is editable by the pen (Would be best if the format permitted layers, for both the teacher and the student, so if needed the teachers additions could be „turned off
# The undergrad logs into the portal where their tests are to be presented and uploads their work. (the status becomes „presented“)
# The lector makes the corrections and adds the grade (the status of the work becomes „graded“; the evaluation can either be „accepted“, „needs personal discussion “ or „Must be reapplied“)
# The undergrad finds out their grade. If needed presents the work again.

Notes:
# The form of the presentation and the correction must be chosen
# The environment should allow the setting of the time for the discussion and medium if the lector wished for it (Time and place of direct contact; Skype etc.)
# The lector must be able to note the appointment
# The system must send an email to the lector if there is a wish for discussion

==A Professional too valuable to lose==

Andrew Bessett (45) is an experienced systems administrator with nearly
20 years of experience in both Microsoft and Unix-like systems. His successful career as a leading sysadmin of Shelley's, a high-profile London insurance company, got a serious setback in Februrary 2012 when the British Airways flight 6201 from Dubai to London with 146 passengers onboard crashed in the Austrian Alps due to bad weather and control system malfunction. Andrew, returning from his winter vacation, was one of the 12 survivors. However, he suffered serious injuries. His two upper vertebrae were smashed on impact, his hands suffered third-degree burns and had to be amputated - right at the shoulder, left at the elbow.

After spending a year in a rehabilitation programme at the Royal National Orthopaedic Hospital in Stanmore, London, he has decided to return to his work. His condition has stabilized but has left him practically paralyzed from neck down - he can move his head and (with very limited power and range) his remaining part of the left hand. He had to use respirator after the accident, but has recovered enough to breathe freely. His speech, hearing, vision and mental aptitude have survived fully intact and he has retained most of his professional skills (interrupted only by the year in therapy). He uses a joystick-controlled powered wheelchair as a means of transportation.

The company has decided to re-hire Andrew if he can prove his ability to handle most of his earlier duties. You are his technical advisory team and have to draft a suitable workstation and necessary software, plus all the necessary amendments in the company infrastructure (premises, workspace, hardware, networking, typical configuration of servers and workstations, intranet, mobile communication, website etc) to allow him return to work. Note: The IT infrastructure at Shelley's makes extensive use of both Microsoft Windows and Debian GNU/Linux platforms.

=Teams and their assignments=
[http://enos.itcollege.ee/~saus/Activity_Chart_Template.xlsx Activity chart]

==Sailing pirates==

Assignment: [[#Improving toolset for race sailing performance analysis|Improving toolset for race sailing performance analysis]]

Documentation: [[Sailing pirates]]

====Members====
* Kristjan Tõnismäe, IT College
* Konstantinos Verigos, Technological Educational Institute of Crete
* Stefanos Athanasiadis, Technological Educational Institute of Crete
* Tommi Potapoff, Vaasa University of Applied Sciences
* Jesse Koski, Vaasa University of Applied Sciences
* Mikko Heikkuri, Vaasa University of Applied Sciences

==Security==

Assignment: [[#Security testing of web application|Security testing of web application]]

Documentation: [[Security]]

====Members====
*Sten Aus, Estonian Information Technology College
*Matis Palm, Estonian Information Technology College
*Sandra Suviste, Estonian Information Technology College
*Markus Rintamäki, Vaasa University of Applied Sciences
*Tomas Lepistö, Vaasa University of Applied Sciences
*Mika Salmela, Vaasa University of Applied Sciences
*Kęstutis Tautvydas, Vilnius University of Applied Sciences
*Jurij Lukjančikov, Vilnius University of Applied Sciences

==Team Robo==

Assignment: [[#Robotic competitions organization software system | Robotic competitions organization software system]]

Documentation: [[Team Robo]]

====Members====
* Veiko Vainu, IT College
* Andreas Plado, IT College
* Giorgos Ioannidis, T.E.I. of Crete, Department Of Applied Informatics And Multimedia
* Konstantinos Michailidis, T.E.I. of Crete, Department Of Applied Informatics And Multimedia

==Team E-Teacher==

Assignment: [[#E-teacher|E-teacher]]

Documentation: [[E-teacher]]

===Members===
* Indrek Mitt, IT College
* Sander Saarm, IT College
* Panagiota Chatzi, T.E.I. of Crete, Department Of Applied Informatics And Multimedia
* Nikolaos Karadimitriou , T.E.I. of Crete, Department Of Applied Informatics And Multimedia

Team Robo

2013-03-27T18:25:59Z

Vevainu: /* Team Members */

Team Robo

2013-03-27T18:22:17Z

Vevainu: /* Team Members */

Team page for [[Deploying IT Infrastructure Solutions]].

==Team Members==
* Veiko Vainu, IT College
* Andreas Plado, IT College
* Giorgos Ioannidis, T.E.I. of Crete
* Konstantinos Michailidis, T.E.I. of Crete

==Goal==
*Goal 1 form assignment
*Goal 2 form assignment
*Goal 3 form assignment

==Activity==
===Monday - 25.03.13===
Things what we did that day
* Participate in lectures
* Learn
* We get to know each other through the exercises.

===Tuesday - 26.03.13===
Things what we did that day
* Composed a set of questions for the client.
* Started making a draft scenario for the client.
* Researched similar systems.

Problems what we faced:
* Lack of project details

Things what we plan to do:
* Client meeting

===Wednesday - 27.03.13===
Things what we did that day
* Met with the client
* Clarified project details
* We made the activity chart
* We divided roles

Problems what we faced:
* We didn't have problems today

Questions and answers from client:
* We asked the basic structure of the outcome
The outcome supposed to be the analysis part of the software.

Things what we plan to do:
* Continiue with undertaking the subtasks of the project
* [https://wiki.itcollege.ee/images/9/97/Tasks.pdf Tasks List.pdf]

==Results==
Summary of what we did and solution what we developed

===Final documentation===
====Analysis====

====Solution====

==IP Feed-back==

===Konstantinos Michailidis===
I liked this and that. Didn't like.
===Konstantinos Verigos===
I liked this and that.

===Andreas Plado===
I liked this and that. Didn't like.
===Veiko Vainu===
I liked this and that.

Deploying IT Infrastructure Solutions 2013

2013-03-27T18:22:10Z

Vevainu: /* Team Robo */

[[Category: Õppetöö]]
[[File:EL_Sotsiaalfond_horisontaal_small.jpg‎‎|right|text-top]]
 
----
__TOC__

----
This is the student results wiki page for the IP program [http://www.itcollege.ee/en/co-operation/dits2013/ "Deploying IT Infrastructure Solutions"] taking place from 24th of March until 6th of April 2013.

All the information regarding program will be presented in the program [http://www.itcollege.ee/en/co-operation/dits2013/ web page].

=Assignments=

==Security testing of web application==

===Description===
Learn about the security of web applications.
Find vulnerabilities from known vulnerable web applications.
Find not known vulnerabilities of development version of web application
Study Information Portal (Used by eleven universities of applied
science in Estonia)
File report that describes methods, tests and findings.

===Expected outcome===
Description of testing methods and findings (all vulnerabilities that
students found in development environment) as testing report.

===Expectations from students===
Understanding web applications (What is difference of GET and POST, how
sessions work, what is header etc).
Knowledge of at least one web programming language (php, java, ruby, C#, python is preferred)

===Lectures support===
Several security related topics will covered during lectures and
practical classes before starting actual testing.
Lecture covers several attack types and vulnerabilities like SQL
injection, cmd injection, XSS, CSRF etc. Practical classes based on DVWA
(Damn Vulnerable Web Application)
After lectures and practical classes students will get access to web
application development environment for practical work.

[http://elab.itcollege.ee:8000/DITS2013/ Lecture/Lab materials and virtual machines]

Lecturer: Margus Ernits (Estonian IT College)

==Driving lessons registration information system==

===Description===
It is a client-server solution which keeps records of student's driving lessons.
Each driving study car has a device / computer where client application runs.

===Expected outcome===
Client application registers the student’s driving lesson time and the GPS
coordinates and sends them to the server over the mobile Internet.
Client application must register driving lessons also without Internet connection
and synchronize with the server when connection is established.
Later a student can check ones driving lesson and travel route on the Internet.

===Limitations===
GPS accuracy at least one point per second.

==Improving toolset for race sailing performance analysis==

===Description===
Implementation of logger that could be used for performance analysis of race sailing teams,
based on data specification for communication between marine electronic devices NMEA
0183.
Learning about the performance analysis needs and specifics of race sailing teams, also
learning about the marine instruments specifics and communication standard NMEA 0183.
Based on core architecture of the NMEA 0183 data logger implementation including
software, hardware and testing.

===Expected outcome===
Fully functioning and tested race sailing performance analysis data logger.

===Expectations from students===
Aspiration to develop in rapid prototyping and testing environment together with professional
and Olympic Team race sailors and marine technology specialists fully functional
performance analysis logger. Both software and hardware development skills. If you can
understand and are interested in what is described
at http://www.boatdesign.net/forums/attachments/onboard-electronics-controls/19260d1204757550-laptop-interface-tacktick-nmea-architecture.png then you are
expected to join team.

===Lectures support===
Lectures and seminars will cover first the needs specification of the performance analysis
logger, NMEA0183 standard description, marine instruments Received Sentences description:
DBT, DPT, GLL, HDG, HDM, MTW, MWV, RMB, RMC, VHW, VLW, VWR. Team will
implement the logger and install the marine wireless range instrument for testing on actual
performance sailing boat. Life saving equipment and wetsuits not needed :)

Lecturer: Linnar Viik (Estonian IT College)

==Robotic competitions organization software system==

===Description===
The software system provides everything from participant registration to the live competition carry out
by the referees. It contains web based interfaces and real-time applications such as score and time
overlay on video broadcast. Different competition (tournament) formats are needed. As much as
possible smart solutions and freely available components shall be used in order to keep the
development time short.

===Expected outcome===
System design description including component, database and sequence diagrams. Suggestion on
database, programming language and reusable components is expected. Creating a project time plan
with at least two scenarios (full scope, minimum scope) is secondary objective. Prototype solution
covering some part of the system would be a bonus task.

===Expectations from students===
Knowledge of database- and web programming. Understanding of software architectures such as MV is
appreciated.

==E-teacher==

In the course of studying Database Fundamentals the students, as independent coursework, must draw ERD-
schemes. Although there is no use of drawing the diagrams if the lector doesn’t give feedback on the success
or failure of said work. The whole process of drawing ERD-diagrams looks like any other teaching process-
The teacher prepares the task, the student draws the ERD-diagram and hands it to the teacher, The teacher
then looks it over and corrects/improves/comments it then returning it to the student. The specificity in here
being that the solutions of the tasks are graphic and no task has one concrete solution – every student solution
is different. This makes every revision unique- the teacher must understand the undergrads intention, check
its compliance whit the task set and then if needed make changes in the model without changing its nature.

For now it has always been done on paper – Undergrad draws a ERD case system model, prints it and hands
it to the lecturer; the lecturer, if needed, corrects it with a pen , writes their comments and the non-grading
evaluation and returns it to the undergrad. The lector marks the results of the test in their ÕIS table.

This process doesn’t exist electronically because during the semester there are many undergrads (ca 140-150)
and there are no comfortable ways to grade them QUICKLY electronically. Herewith, when the lector gets
the work printed on paper he is capable of correcting them with haste. Hence it raises two main problems that
need solving. The Schemes sent on paper must be replaced by electronically forwardable materials and a way
to revise/correct electronically presented ERD quick must be created.

Past couple of years have brought with them the development of portable computer user interface – There are
touch screens and electronic pens, with which one can draw on a computer screen. From there springs the
thought, of making an application for correction of such works, where the lector writes the
corrections/notes/comments directly on the work presented by the undergrad. Using an electronic pen.

The process itself should look like this:
# The undergrad creates an ERD‐diagram and presents it in some from, that is editable by the pen (Would be best if the format permitted layers, for both the teacher and the student, so if needed the teachers additions could be „turned off
# The undergrad logs into the portal where their tests are to be presented and uploads their work. (the status becomes „presented“)
# The lector makes the corrections and adds the grade (the status of the work becomes „graded“; the evaluation can either be „accepted“, „needs personal discussion “ or „Must be reapplied“)
# The undergrad finds out their grade. If needed presents the work again.

Notes:
# The form of the presentation and the correction must be chosen
# The environment should allow the setting of the time for the discussion and medium if the lector wished for it (Time and place of direct contact; Skype etc.)
# The lector must be able to note the appointment
# The system must send an email to the lector if there is a wish for discussion

==A Professional too valuable to lose==

Andrew Bessett (45) is an experienced systems administrator with nearly
20 years of experience in both Microsoft and Unix-like systems. His successful career as a leading sysadmin of Shelley's, a high-profile London insurance company, got a serious setback in Februrary 2012 when the British Airways flight 6201 from Dubai to London with 146 passengers onboard crashed in the Austrian Alps due to bad weather and control system malfunction. Andrew, returning from his winter vacation, was one of the 12 survivors. However, he suffered serious injuries. His two upper vertebrae were smashed on impact, his hands suffered third-degree burns and had to be amputated - right at the shoulder, left at the elbow.

After spending a year in a rehabilitation programme at the Royal National Orthopaedic Hospital in Stanmore, London, he has decided to return to his work. His condition has stabilized but has left him practically paralyzed from neck down - he can move his head and (with very limited power and range) his remaining part of the left hand. He had to use respirator after the accident, but has recovered enough to breathe freely. His speech, hearing, vision and mental aptitude have survived fully intact and he has retained most of his professional skills (interrupted only by the year in therapy). He uses a joystick-controlled powered wheelchair as a means of transportation.

The company has decided to re-hire Andrew if he can prove his ability to handle most of his earlier duties. You are his technical advisory team and have to draft a suitable workstation and necessary software, plus all the necessary amendments in the company infrastructure (premises, workspace, hardware, networking, typical configuration of servers and workstations, intranet, mobile communication, website etc) to allow him return to work. Note: The IT infrastructure at Shelley's makes extensive use of both Microsoft Windows and Debian GNU/Linux platforms.

=Teams and their assignments=
[http://enos.itcollege.ee/~saus/Activity_Chart_Template.xlsx Activity chart]

==Sailing pirates==

Assignment: [[#Improving toolset for race sailing performance analysis|Improving toolset for race sailing performance analysis]]

Documentation: [[Sailing pirates]]

====Members====
* Kristjan Tõnismäe, IT College
* Konstantinos Verigos, Technological Educational Institute of Crete
* Stefanos Athanasiadis, Technological Educational Institute of Crete
* Tommi Potapoff, Vaasa University of Applied Sciences
* Jesse Koski, Vaasa University of Applied Sciences
* Mikko Heikkuri, Vaasa University of Applied Sciences

==Security==

Assignment: [[#Security testing of web application|Security testing of web application]]

Documentation: [[Security]]

====Members====
*Sten Aus, Estonian Information Technology College
*Matis Palm, Estonian Information Technology College
*Sandra Suviste, Estonian Information Technology College
*Markus Rintamäki, Vaasa University of Applied Sciences
*Tomas Lepistö, Vaasa University of Applied Sciences
*Mika Salmela, Vaasa University of Applied Sciences
*Kęstutis Tautvydas, Vilnius University of Applied Sciences
*Jurij Lukjančikov, Vilnius University of Applied Sciences

==Team Robo==

Assignment: [[#Robotic competitions organization software system | Robotic competitions organization software system]]

Documentation: [[Team Robo]]

====Members====
* Veiko Vainu, IT College
* Andreas Plado, IT College
* Giorgos Ioannidis, T.E.I. of Crete
* Konstantinos Michailidis, T.E.I. of Crete

==Team E-Teacher==

Assignment: [[#E-teacher|E-teacher]]

Documentation: [[E-teacher]]

===Members===
* Indrek Mitt, IT College
* Sander Saarm, IT College
* Panagiota Chatzi, T.E.I. of Crete, Department Of Applied Informatics And Multimedia
* Nikolaos Karadimitriou , T.E.I. of Crete, Department Of Applied Informatics And Multimedia

Team Robo

2013-03-27T04:33:34Z

Vevainu: /* Tuesday - 26.03.13 */

Team page for [[Deploying IT Infrastructure Solutions]].

==Team Members==
* Veiko Vainu, IT College
* Andreas Plado, IT College
* Konstantinos Verigos, T.E.I. of Crete
* Konstantinos Michailidis, T.E.I. of Crete

==Goal==
*Goal 1 form assignment
*Goal 2 form assignment
*Goal 3 form assignment

==Activity==
===Monday - 25.03.13===
Things what we did that day
* Listen to lectures
* Learn

===Tuesday - 26.03.13===
Things what we did that day
* Composed a set of questions for the client.
* Started making a basic ERD-diagram for the database.
* Researched similar systems.

Problems what we faced:
* First problem
* Second problem

Things what we plan to do:
* First thing
* Second thing

===Wednesday - 27.03.13===
Things what we did that day
* First thing
* Second thing

Problems what we faced:
* First problem
* Second problem

Questions and answers from client:
* First Question
Answer to question

* Second Question
Answer to question

Things what we plan to do:
* First thing
* Second thing

==Results==
Summary of what we did and solution what we developed

===Final documentation===
====Analysis====

====Solution====

==IP Feed-back==

===Konstantinos Michailidis===
I liked this and that. Didn't like.
===Konstantinos Verigos===
I liked this and that.

===Andreas Plado===
I liked this and that. Didn't like.
===Veiko Vainu===
I liked this and that.

Deploying IT Infrastructure Solutions 2013

2013-03-27T04:29:07Z

Vevainu: /* Team Robo */

[[Category: Õppetöö]]
[[File:EL_Sotsiaalfond_horisontaal_small.jpg‎‎|right|text-top]]
 
----
__TOC__

----
This is the student results wiki page for the IP program [http://www.itcollege.ee/en/co-operation/dits2013/ "Deploying IT Infrastructure Solutions"] taking place from 24th of March until 6th of April 2013.

All the information regarding program will be presented in the program [http://www.itcollege.ee/en/co-operation/dits2013/ web page].

=Assignments=

==Security testing of web application==

===Description===
Learn about the security of web applications.
Find vulnerabilities from known vulnerable web applications.
Find not known vulnerabilities of development version of web application
Study Information Portal (Used by eleven universities of applied
science in Estonia)
File report that describes methods, tests and findings.

===Expected outcome===
Description of testing methods and findings (all vulnerabilities that
students found in development environment) as testing report.

===Expectations from students===
Understanding web applications (What is difference of GET and POST, how
sessions work, what is header etc).
Knowledge of at least one web programming language (php, java, ruby, C#, python is preferred)

===Lectures support===
Several security related topics will covered during lectures and
practical classes before starting actual testing.
Lecture covers several attack types and vulnerabilities like SQL
injection, cmd injection, XSS, CSRF etc. Practical classes based on DVWA
(Damn Vulnerable Web Application)
After lectures and practical classes students will get access to web
application development environment for practical work.

[http://elab.itcollege.ee:8000/DITS2013/ Lecture/Lab materials and virtual machines]

Lecturer: Margus Ernits (Estonian IT College)

==Driving lessons registration information system==

===Description===
It is a client-server solution which keeps records of student's driving lessons.
Each driving study car has a device / computer where client application runs.

===Expected outcome===
Client application registers the student’s driving lesson time and the GPS
coordinates and sends them to the server over the mobile Internet.
Client application must register driving lessons also without Internet connection
and synchronize with the server when connection is established.
Later a student can check ones driving lesson and travel route on the Internet.

===Limitations===
GPS accuracy at least one point per second.

==Improving toolset for race sailing performance analysis==

===Description===
Implementation of logger that could be used for performance analysis of race sailing teams,
based on data specification for communication between marine electronic devices NMEA
0183.
Learning about the performance analysis needs and specifics of race sailing teams, also
learning about the marine instruments specifics and communication standard NMEA 0183.
Based on core architecture of the NMEA 0183 data logger implementation including
software, hardware and testing.

===Expected outcome===
Fully functioning and tested race sailing performance analysis data logger.

===Expectations from students===
Aspiration to develop in rapid prototyping and testing environment together with professional
and Olympic Team race sailors and marine technology specialists fully functional
performance analysis logger. Both software and hardware development skills. If you can
understand and are interested in what is described
at http://www.boatdesign.net/forums/attachments/onboard-electronics-controls/19260d1204757550-laptop-interface-tacktick-nmea-architecture.png then you are
expected to join team.

===Lectures support===
Lectures and seminars will cover first the needs specification of the performance analysis
logger, NMEA0183 standard description, marine instruments Received Sentences description:
DBT, DPT, GLL, HDG, HDM, MTW, MWV, RMB, RMC, VHW, VLW, VWR. Team will
implement the logger and install the marine wireless range instrument for testing on actual
performance sailing boat. Life saving equipment and wetsuits not needed :)

Lecturer: Linnar Viik (Estonian IT College)

==Robotic competitions organization software system==

===Description===
The software system provides everything from participant registration to the live competition carry out
by the referees. It contains web based interfaces and real-time applications such as score and time
overlay on video broadcast. Different competition (tournament) formats are needed. As much as
possible smart solutions and freely available components shall be used in order to keep the
development time short.

===Expected outcome===
System design description including component, database and sequence diagrams. Suggestion on
database, programming language and reusable components is expected. Creating a project time plan
with at least two scenarios (full scope, minimum scope) is secondary objective. Prototype solution
covering some part of the system would be a bonus task.

===Expectations from students===
Knowledge of database- and web programming. Understanding of software architectures such as MV is
appreciated.

==E-teacher==

In the course of studying Database Fundamentals the students, as independent coursework, must draw ERD-
schemes. Although there is no use of drawing the diagrams if the lector doesn’t give feedback on the success
or failure of said work. The whole process of drawing ERD-diagrams looks like any other teaching process-
The teacher prepares the task, the student draws the ERD-diagram and hands it to the teacher, The teacher
then looks it over and corrects/improves/comments it then returning it to the student. The specificity in here
being that the solutions of the tasks are graphic and no task has one concrete solution – every student solution
is different. This makes every revision unique- the teacher must understand the undergrads intention, check
its compliance whit the task set and then if needed make changes in the model without changing its nature.

For now it has always been done on paper – Undergrad draws a ERD case system model, prints it and hands
it to the lecturer; the lecturer, if needed, corrects it with a pen , writes their comments and the non-grading
evaluation and returns it to the undergrad. The lector marks the results of the test in their ÕIS table.

This process doesn’t exist electronically because during the semester there are many undergrads (ca 140-150)
and there are no comfortable ways to grade them QUICKLY electronically. Herewith, when the lector gets
the work printed on paper he is capable of correcting them with haste. Hence it raises two main problems that
need solving. The Schemes sent on paper must be replaced by electronically forwardable materials and a way
to revise/correct electronically presented ERD quick must be created.

Past couple of years have brought with them the development of portable computer user interface – There are
touch screens and electronic pens, with which one can draw on a computer screen. From there springs the
thought, of making an application for correction of such works, where the lector writes the
corrections/notes/comments directly on the work presented by the undergrad. Using an electronic pen.

The process itself should look like this:
# The undergrad creates an ERD‐diagram and presents it in some from, that is editable by the pen (Would be best if the format permitted layers, for both the teacher and the student, so if needed the teachers additions could be „turned off
# The undergrad logs into the portal where their tests are to be presented and uploads their work. (the status becomes „presented“)
# The lector makes the corrections and adds the grade (the status of the work becomes „graded“; the evaluation can either be „accepted“, „needs personal discussion “ or „Must be reapplied“)
# The undergrad finds out their grade. If needed presents the work again.

Notes:
# The form of the presentation and the correction must be chosen
# The environment should allow the setting of the time for the discussion and medium if the lector wished for it (Time and place of direct contact; Skype etc.)
# The lector must be able to note the appointment
# The system must send an email to the lector if there is a wish for discussion

==A Professional too valuable to lose==

Andrew Bessett (45) is an experienced systems administrator with nearly
20 years of experience in both Microsoft and Unix-like systems. His successful career as a leading sysadmin of Shelley's, a high-profile London insurance company, got a serious setback in Februrary 2012 when the British Airways flight 6201 from Dubai to London with 146 passengers onboard crashed in the Austrian Alps due to bad weather and control system malfunction. Andrew, returning from his winter vacation, was one of the 12 survivors. However, he suffered serious injuries. His two upper vertebrae were smashed on impact, his hands suffered third-degree burns and had to be amputated - right at the shoulder, left at the elbow.

After spending a year in a rehabilitation programme at the Royal National Orthopaedic Hospital in Stanmore, London, he has decided to return to his work. His condition has stabilized but has left him practically paralyzed from neck down - he can move his head and (with very limited power and range) his remaining part of the left hand. He had to use respirator after the accident, but has recovered enough to breathe freely. His speech, hearing, vision and mental aptitude have survived fully intact and he has retained most of his professional skills (interrupted only by the year in therapy). He uses a joystick-controlled powered wheelchair as a means of transportation.

The company has decided to re-hire Andrew if he can prove his ability to handle most of his earlier duties. You are his technical advisory team and have to draft a suitable workstation and necessary software, plus all the necessary amendments in the company infrastructure (premises, workspace, hardware, networking, typical configuration of servers and workstations, intranet, mobile communication, website etc) to allow him return to work. Note: The IT infrastructure at Shelley's makes extensive use of both Microsoft Windows and Debian GNU/Linux platforms.

=Teams and their assignments=
[http://enos.itcollege.ee/~saus/Activity_Chart_Template.xlsx Activity chart]

==Sailing pirates==

Assignment: [[#Improving toolset for race sailing performance analysis|Improving toolset for race sailing performance analysis]]

Documentation: [[Sailing pirates]]

====Members====
* Kristjan Tõnismäe, IT College
* Yorgos Ioannidis, school
* Stefanos Athanasiadis, school
* Tommi Potapoff, school
* Jesse Koski, school
* Mikko Heikkuri, school

==Demo team 1==

Assignment: [[#Security testing of web application|Security testing of web application]]

Documentation: [[Demo team]]

====Members====
* Member 1, school
* Member 2, school
* Member 3, school

==Demo team 2==

Assignment: [[#Robotic competitions organization software system]]

Documentation: [[Demo team 2]]

====Members====
* Member 1, school
* Member 2, school
* Member 3, school

==Security==

Assignment: [[#Security testing of web application|Security testing of web application]]

Documentation: [[Security]]

====Members====
*Sten Aus, Estonian Information Technology College
*Matis Palm, Estonian Information Technology College
*Sandra Suviste, Estonian Information Technology College
*Markus Rintamäki, Vaasa University of Applied Sciences
*Tomas Lepistö, Vaasa University of Applied Sciences
*Mika Salmela, Vaasa University of Applied Sciences
*Kęstutis Tautvydas, Vilnius University of Applied Sciences
*Jurij Lukjančikov, Vilnius University of Applied Sciences

==Team Robo==

Assignment: [[#Robotic competitions organization software system | Robotic competitions organization software system]]

Documentation: [[Team Robo]]

====Members====
* Veiko Vainu, IT College
* Andreas Plado, IT College
* Konstantinos Verigos, T.E.I. of Crete
* Konstantinos Michailidis, T.E.I. of Crete

==Team E-Teacher==

Assignment: [[#E-teacher|E-teacher]]

Documentation: [[E-teacher]]

===Members===
* Indrek Mitt, IT College
* Sander Saarm, IT College
* Panagiota Chatzi, T.E.I. of Crete, Department Of Applied Informatics And Multimedia
* Nikolaos Karadimitriou , T.E.I. of Crete, Department Of Applied Informatics And Multimedia

Deploying IT Infrastructure Solutions 2013

2013-03-27T04:28:19Z

Vevainu: /* Team Robo */

[[Category: Õppetöö]]
[[File:EL_Sotsiaalfond_horisontaal_small.jpg‎‎|right|text-top]]
 
----
__TOC__

----
This is the student results wiki page for the IP program [http://www.itcollege.ee/en/co-operation/dits2013/ "Deploying IT Infrastructure Solutions"] taking place from 24th of March until 6th of April 2013.

All the information regarding program will be presented in the program [http://www.itcollege.ee/en/co-operation/dits2013/ web page].

=Assignments=

==Security testing of web application==

===Description===
Learn about the security of web applications.
Find vulnerabilities from known vulnerable web applications.
Find not known vulnerabilities of development version of web application
Study Information Portal (Used by eleven universities of applied
science in Estonia)
File report that describes methods, tests and findings.

===Expected outcome===
Description of testing methods and findings (all vulnerabilities that
students found in development environment) as testing report.

===Expectations from students===
Understanding web applications (What is difference of GET and POST, how
sessions work, what is header etc).
Knowledge of at least one web programming language (php, java, ruby, C#, python is preferred)

===Lectures support===
Several security related topics will covered during lectures and
practical classes before starting actual testing.
Lecture covers several attack types and vulnerabilities like SQL
injection, cmd injection, XSS, CSRF etc. Practical classes based on DVWA
(Damn Vulnerable Web Application)
After lectures and practical classes students will get access to web
application development environment for practical work.

[http://elab.itcollege.ee:8000/DITS2013/ Lecture/Lab materials and virtual machines]

Lecturer: Margus Ernits (Estonian IT College)

==Driving lessons registration information system==

===Description===
It is a client-server solution which keeps records of student's driving lessons.
Each driving study car has a device / computer where client application runs.

===Expected outcome===
Client application registers the student’s driving lesson time and the GPS
coordinates and sends them to the server over the mobile Internet.
Client application must register driving lessons also without Internet connection
and synchronize with the server when connection is established.
Later a student can check ones driving lesson and travel route on the Internet.

===Limitations===
GPS accuracy at least one point per second.

==Improving toolset for race sailing performance analysis==

===Description===
Implementation of logger that could be used for performance analysis of race sailing teams,
based on data specification for communication between marine electronic devices NMEA
0183.
Learning about the performance analysis needs and specifics of race sailing teams, also
learning about the marine instruments specifics and communication standard NMEA 0183.
Based on core architecture of the NMEA 0183 data logger implementation including
software, hardware and testing.

===Expected outcome===
Fully functioning and tested race sailing performance analysis data logger.

===Expectations from students===
Aspiration to develop in rapid prototyping and testing environment together with professional
and Olympic Team race sailors and marine technology specialists fully functional
performance analysis logger. Both software and hardware development skills. If you can
understand and are interested in what is described
at http://www.boatdesign.net/forums/attachments/onboard-electronics-controls/19260d1204757550-laptop-interface-tacktick-nmea-architecture.png then you are
expected to join team.

===Lectures support===
Lectures and seminars will cover first the needs specification of the performance analysis
logger, NMEA0183 standard description, marine instruments Received Sentences description:
DBT, DPT, GLL, HDG, HDM, MTW, MWV, RMB, RMC, VHW, VLW, VWR. Team will
implement the logger and install the marine wireless range instrument for testing on actual
performance sailing boat. Life saving equipment and wetsuits not needed :)

Lecturer: Linnar Viik (Estonian IT College)

==Robotic competitions organization software system==

===Description===
The software system provides everything from participant registration to the live competition carry out
by the referees. It contains web based interfaces and real-time applications such as score and time
overlay on video broadcast. Different competition (tournament) formats are needed. As much as
possible smart solutions and freely available components shall be used in order to keep the
development time short.

===Expected outcome===
System design description including component, database and sequence diagrams. Suggestion on
database, programming language and reusable components is expected. Creating a project time plan
with at least two scenarios (full scope, minimum scope) is secondary objective. Prototype solution
covering some part of the system would be a bonus task.

===Expectations from students===
Knowledge of database- and web programming. Understanding of software architectures such as MV is
appreciated.

==E-teacher==

In the course of studying Database Fundamentals the students, as independent coursework, must draw ERD-
schemes. Although there is no use of drawing the diagrams if the lector doesn’t give feedback on the success
or failure of said work. The whole process of drawing ERD-diagrams looks like any other teaching process-
The teacher prepares the task, the student draws the ERD-diagram and hands it to the teacher, The teacher
then looks it over and corrects/improves/comments it then returning it to the student. The specificity in here
being that the solutions of the tasks are graphic and no task has one concrete solution – every student solution
is different. This makes every revision unique- the teacher must understand the undergrads intention, check
its compliance whit the task set and then if needed make changes in the model without changing its nature.

For now it has always been done on paper – Undergrad draws a ERD case system model, prints it and hands
it to the lecturer; the lecturer, if needed, corrects it with a pen , writes their comments and the non-grading
evaluation and returns it to the undergrad. The lector marks the results of the test in their ÕIS table.

This process doesn’t exist electronically because during the semester there are many undergrads (ca 140-150)
and there are no comfortable ways to grade them QUICKLY electronically. Herewith, when the lector gets
the work printed on paper he is capable of correcting them with haste. Hence it raises two main problems that
need solving. The Schemes sent on paper must be replaced by electronically forwardable materials and a way
to revise/correct electronically presented ERD quick must be created.

Past couple of years have brought with them the development of portable computer user interface – There are
touch screens and electronic pens, with which one can draw on a computer screen. From there springs the
thought, of making an application for correction of such works, where the lector writes the
corrections/notes/comments directly on the work presented by the undergrad. Using an electronic pen.

The process itself should look like this:
# The undergrad creates an ERD‐diagram and presents it in some from, that is editable by the pen (Would be best if the format permitted layers, for both the teacher and the student, so if needed the teachers additions could be „turned off
# The undergrad logs into the portal where their tests are to be presented and uploads their work. (the status becomes „presented“)
# The lector makes the corrections and adds the grade (the status of the work becomes „graded“; the evaluation can either be „accepted“, „needs personal discussion “ or „Must be reapplied“)
# The undergrad finds out their grade. If needed presents the work again.

Notes:
# The form of the presentation and the correction must be chosen
# The environment should allow the setting of the time for the discussion and medium if the lector wished for it (Time and place of direct contact; Skype etc.)
# The lector must be able to note the appointment
# The system must send an email to the lector if there is a wish for discussion

==A Professional too valuable to lose==

Andrew Bessett (45) is an experienced systems administrator with nearly
20 years of experience in both Microsoft and Unix-like systems. His successful career as a leading sysadmin of Shelley's, a high-profile London insurance company, got a serious setback in Februrary 2012 when the British Airways flight 6201 from Dubai to London with 146 passengers onboard crashed in the Austrian Alps due to bad weather and control system malfunction. Andrew, returning from his winter vacation, was one of the 12 survivors. However, he suffered serious injuries. His two upper vertebrae were smashed on impact, his hands suffered third-degree burns and had to be amputated - right at the shoulder, left at the elbow.

After spending a year in a rehabilitation programme at the Royal National Orthopaedic Hospital in Stanmore, London, he has decided to return to his work. His condition has stabilized but has left him practically paralyzed from neck down - he can move his head and (with very limited power and range) his remaining part of the left hand. He had to use respirator after the accident, but has recovered enough to breathe freely. His speech, hearing, vision and mental aptitude have survived fully intact and he has retained most of his professional skills (interrupted only by the year in therapy). He uses a joystick-controlled powered wheelchair as a means of transportation.

The company has decided to re-hire Andrew if he can prove his ability to handle most of his earlier duties. You are his technical advisory team and have to draft a suitable workstation and necessary software, plus all the necessary amendments in the company infrastructure (premises, workspace, hardware, networking, typical configuration of servers and workstations, intranet, mobile communication, website etc) to allow him return to work. Note: The IT infrastructure at Shelley's makes extensive use of both Microsoft Windows and Debian GNU/Linux platforms.

=Teams and their assignments=
[http://enos.itcollege.ee/~saus/Activity_Chart_Template.xlsx Activity chart]

==Sailing pirates==

Assignment: [[#Improving toolset for race sailing performance analysis|Improving toolset for race sailing performance analysis]]

Documentation: [[Sailing pirates]]

====Members====
* Kristjan Tõnismäe, IT College
* Yorgos Ioannidis, school
* Stefanos Athanasiadis, school
* Tommi Potapoff, school
* Jesse Koski, school
* Mikko Heikkuri, school

==Demo team 1==

Assignment: [[#Security testing of web application|Security testing of web application]]

Documentation: [[Demo team]]

====Members====
* Member 1, school
* Member 2, school
* Member 3, school

==Demo team 2==

Assignment: [[#Robotic competitions organization software system]]

Documentation: [[Demo team 2]]

====Members====
* Member 1, school
* Member 2, school
* Member 3, school

==Security==

Assignment: [[#Security testing of web application|Security testing of web application]]

Documentation: [[Security]]

====Members====
*Sten Aus, Estonian Information Technology College
*Matis Palm, Estonian Information Technology College
*Sandra Suviste, Estonian Information Technology College
*Markus Rintamäki, Vaasa University of Applied Sciences
*Tomas Lepistö, Vaasa University of Applied Sciences
*Mika Salmela, Vaasa University of Applied Sciences
*Kęstutis Tautvydas, Vilnius University of Applied Sciences
*Jurij Lukjančikov, Vilnius University of Applied Sciences

==Team Robo==

Assignment: [[#Robotic competitions organization software system]]

Documentation: [[Team Robo]]

====Members====
* Veiko Vainu, IT College
* Andreas Plado, IT College
* Konstantinos Verigos, T.E.I. of Crete
* Konstantinos Michailidis, T.E.I. of Crete

==Team E-Teacher==

Assignment: [[#E-teacher|E-teacher]]

Documentation: [[E-teacher]]

===Members===
* Indrek Mitt, IT College
* Sander Saarm, IT College
* Panagiota Chatzi, T.E.I. of Crete, Department Of Applied Informatics And Multimedia
* Nikolaos Karadimitriou , T.E.I. of Crete, Department Of Applied Informatics And Multimedia

Team Robo

2013-03-26T13:21:11Z

Vevainu: /* IP Feed-back */

Team page for [[Deploying IT Infrastructure Solutions]].

==Team Members==
* Veiko Vainu, IT College
* Andreas Plado, IT College
* Konstantinos Verigos, T.E.I. of Crete
* Konstantinos Michailidis, T.E.I. of Crete

==Goal==
*Goal 1 form assignment
*Goal 2 form assignment
*Goal 3 form assignment

==Activity==
===Monday - 25.03.13===
Things what we did that day
* Listen to lectures
* Learn

===Tuesday - 26.03.13===
Things what we did that day
* First thing
* Second thing

Problems what we faced:
* First problem
* Second problem

Things what we plan to do:
* First thing
* Second thing

===Wednesday - 27.03.13===
Things what we did that day
* First thing
* Second thing

Problems what we faced:
* First problem
* Second problem

Questions and answers from client:
* First Question
Answer to question

* Second Question
Answer to question

Things what we plan to do:
* First thing
* Second thing

==Results==
Summary of what we did and solution what we developed

===Final documentation===
====Analysis====

====Solution====

==IP Feed-back==

===Konstantinos Michailidis===
I liked this and that. Didn't like.
===Konstantinos Verigos===
I liked this and that.

===Andreas Plado===
I liked this and that. Didn't like.
===Veiko Vainu===
I liked this and that.

Team Robo

2013-03-26T13:18:00Z

Vevainu: /* Monday - 25.03.13 */

Team page for [[Deploying IT Infrastructure Solutions]].

==Team Members==
* Veiko Vainu, IT College
* Andreas Plado, IT College
* Konstantinos Verigos, T.E.I. of Crete
* Konstantinos Michailidis, T.E.I. of Crete

==Goal==
*Goal 1 form assignment
*Goal 2 form assignment
*Goal 3 form assignment

==Activity==
===Monday - 25.03.13===
Things what we did that day
* Listen to lectures
* Learn

===Tuesday - 26.03.13===
Things what we did that day
* First thing
* Second thing

Problems what we faced:
* First problem
* Second problem

Things what we plan to do:
* First thing
* Second thing

===Wednesday - 27.03.13===
Things what we did that day
* First thing
* Second thing

Problems what we faced:
* First problem
* Second problem

Questions and answers from client:
* First Question
Answer to question

* Second Question
Answer to question

Things what we plan to do:
* First thing
* Second thing

==Results==
Summary of what we did and solution what we developed

===Final documentation===
====Analysis====

====Solution====

==IP Feed-back==
===Member 1 feedback===
I liked this and that.

===Member 2 feedback===
I liked this and that. Didn't like.

Deploying IT Infrastructure Solutions 2013

2013-03-26T13:17:03Z

Vevainu: /* Security */

[[Category: Õppetöö]]
[[File:EL_Sotsiaalfond_horisontaal_small.jpg‎‎|right|text-top]]
 
----
__TOC__

----
This is the student results wiki page for the IP program [http://www.itcollege.ee/en/co-operation/dits2013/ "Deploying IT Infrastructure Solutions"] taking place from 24th of March until 6th of April 2013.

All the information regarding program will be presented in the program [http://www.itcollege.ee/en/co-operation/dits2013/ web page].

=Assignments=

==Security testing of web application==

===Description===
Learn about the security of web applications.
Find vulnerabilities from known vulnerable web applications.
Find not known vulnerabilities of development version of web application
Study Information Portal (Used by eleven universities of applied
science in Estonia)
File report that describes methods, tests and findings.

===Expected outcome===
Description of testing methods and findings (all vulnerabilities that
students found in development environment) as testing report.

===Expectations from students===
Understanding web applications (What is difference of GET and POST, how
sessions work, what is header etc).
Knowledge of at least one web programming language (php, java, ruby, C#, python is preferred)

===Lectures support===
Several security related topics will covered during lectures and
practical classes before starting actual testing.
Lecture covers several attack types and vulnerabilities like SQL
injection, cmd injection, XSS, CSRF etc. Practical classes based on DVWA
(Damn Vulnerable Web Application)
After lectures and practical classes students will get access to web
application development environment for practical work.

[http://elab.itcollege.ee:8000/DITS2013/ Lecture/Lab materials and virtual machines]

Lecturer: Margus Ernits (Estonian IT College)

==Driving lessons registration information system==

===Description===
It is a client-server solution which keeps records of student's driving lessons.
Each driving study car has a device / computer where client application runs.

===Expected outcome===
Client application registers the student’s driving lesson time and the GPS
coordinates and sends them to the server over the mobile Internet.
Client application must register driving lessons also without Internet connection
and synchronize with the server when connection is established.
Later a student can check ones driving lesson and travel route on the Internet.

===Limitations===
GPS accuracy at least one point per second.

==Improving toolset for race sailing performance analysis==

===Description===
Implementation of logger that could be used for performance analysis of race sailing teams,
based on data specification for communication between marine electronic devices NMEA
0183.
Learning about the performance analysis needs and specifics of race sailing teams, also
learning about the marine instruments specifics and communication standard NMEA 0183.
Based on core architecture of the NMEA 0183 data logger implementation including
software, hardware and testing.

===Expected outcome===
Fully functioning and tested race sailing performance analysis data logger.

===Expectations from students===
Aspiration to develop in rapid prototyping and testing environment together with professional
and Olympic Team race sailors and marine technology specialists fully functional
performance analysis logger. Both software and hardware development skills. If you can
understand and are interested in what is described
at http://www.boatdesign.net/forums/attachments/onboard-electronics-controls/19260d1204757550-laptop-interface-tacktick-nmea-architecture.png then you are
expected to join team.

===Lectures support===
Lectures and seminars will cover first the needs specification of the performance analysis
logger, NMEA0183 standard description, marine instruments Received Sentences description:
DBT, DPT, GLL, HDG, HDM, MTW, MWV, RMB, RMC, VHW, VLW, VWR. Team will
implement the logger and install the marine wireless range instrument for testing on actual
performance sailing boat. Life saving equipment and wetsuits not needed :)

Lecturer: Linnar Viik (Estonian IT College)

==Robotic competitions organization software system==

===Description===
The software system provides everything from participant registration to the live competition carry out
by the referees. It contains web based interfaces and real-time applications such as score and time
overlay on video broadcast. Different competition (tournament) formats are needed. As much as
possible smart solutions and freely available components shall be used in order to keep the
development time short.

===Expected outcome===
System design description including component, database and sequence diagrams. Suggestion on
database, programming language and reusable components is expected. Creating a project time plan
with at least two scenarios (full scope, minimum scope) is secondary objective. Prototype solution
covering some part of the system would be a bonus task.

===Expectations from students===
Knowledge of database- and web programming. Understanding of software architectures such as MV is
appreciated.

==E-teacher==

In the course of studying Database Fundamentals the students, as independent coursework, must draw ERD-
schemes. Although there is no use of drawing the diagrams if the lector doesn’t give feedback on the success
or failure of said work. The whole process of drawing ERD-diagrams looks like any other teaching process-
The teacher prepares the task, the student draws the ERD-diagram and hands it to the teacher, The teacher
then looks it over and corrects/improves/comments it then returning it to the student. The specificity in here
being that the solutions of the tasks are graphic and no task has one concrete solution – every student solution
is different. This makes every revision unique- the teacher must understand the undergrads intention, check
its compliance whit the task set and then if needed make changes in the model without changing its nature.

For now it has always been done on paper – Undergrad draws a ERD case system model, prints it and hands
it to the lecturer; the lecturer, if needed, corrects it with a pen , writes their comments and the non-grading
evaluation and returns it to the undergrad. The lector marks the results of the test in their ÕIS table.

This process doesn’t exist electronically because during the semester there are many undergrads (ca 140-150)
and there are no comfortable ways to grade them QUICKLY electronically. Herewith, when the lector gets
the work printed on paper he is capable of correcting them with haste. Hence it raises two main problems that
need solving. The Schemes sent on paper must be replaced by electronically forwardable materials and a way
to revise/correct electronically presented ERD quick must be created.

Past couple of years have brought with them the development of portable computer user interface – There are
touch screens and electronic pens, with which one can draw on a computer screen. From there springs the
thought, of making an application for correction of such works, where the lector writes the
corrections/notes/comments directly on the work presented by the undergrad. Using an electronic pen.

The process itself should look like this:
# The undergrad creates an ERD‐diagram and presents it in some from, that is editable by the pen (Would be best if the format permitted layers, for both the teacher and the student, so if needed the teachers additions could be „turned off
# The undergrad logs into the portal where their tests are to be presented and uploads their work. (the status becomes „presented“)
# The lector makes the corrections and adds the grade (the status of the work becomes „graded“; the evaluation can either be „accepted“, „needs personal discussion “ or „Must be reapplied“)
# The undergrad finds out their grade. If needed presents the work again.

Notes:
# The form of the presentation and the correction must be chosen
# The environment should allow the setting of the time for the discussion and medium if the lector wished for it (Time and place of direct contact; Skype etc.)
# The lector must be able to note the appointment
# The system must send an email to the lector if there is a wish for discussion

==A Professional too valuable to lose==

Andrew Bessett (45) is an experienced systems administrator with nearly
20 years of experience in both Microsoft and Unix-like systems. His successful career as a leading sysadmin of Shelley's, a high-profile London insurance company, got a serious setback in Februrary 2012 when the British Airways flight 6201 from Dubai to London with 146 passengers onboard crashed in the Austrian Alps due to bad weather and control system malfunction. Andrew, returning from his winter vacation, was one of the 12 survivors. However, he suffered serious injuries. His two upper vertebrae were smashed on impact, his hands suffered third-degree burns and had to be amputated - right at the shoulder, left at the elbow.

After spending a year in a rehabilitation programme at the Royal National Orthopaedic Hospital in Stanmore, London, he has decided to return to his work. His condition has stabilized but has left him practically paralyzed from neck down - he can move his head and (with very limited power and range) his remaining part of the left hand. He had to use respirator after the accident, but has recovered enough to breathe freely. His speech, hearing, vision and mental aptitude have survived fully intact and he has retained most of his professional skills (interrupted only by the year in therapy). He uses a joystick-controlled powered wheelchair as a means of transportation.

The company has decided to re-hire Andrew if he can prove his ability to handle most of his earlier duties. You are his technical advisory team and have to draft a suitable workstation and necessary software, plus all the necessary amendments in the company infrastructure (premises, workspace, hardware, networking, typical configuration of servers and workstations, intranet, mobile communication, website etc) to allow him return to work. Note: The IT infrastructure at Shelley's makes extensive use of both Microsoft Windows and Debian GNU/Linux platforms.

=Teams and their assignments=
[http://enos.itcollege.ee/~saus/Activity_Chart_Template.xlsx Activity chart]

==Demo team 1==

Assignment: [[#Security testing of web application|Security testing of web application]]

Documentation: [[Demo team]]

====Members====
* Member 1, school
* Member 2, school
* Member 3, school

==Demo team 2==

Assignment: [[#Robotic competitions organization software system]]

Documentation: [[Demo team 2]]

====Members====
* Member 1, school
* Member 2, school
* Member 3, school

==Security==

Assignment: [[#Security testing of web application|Security testing of web application]]

Documentation: [[Demo team 2]]

====Members====
* Sten Aus, Estonian Information Technology College
* Member 2, school
* Member 3, school

==Team Robo==

Assignment: [[#Robotic competitions organization software system]]

Documentation: [[Team_Robo]]

====Members====
* Veiko Vainu, IT College
* Andreas Plado, IT College
* Konstantinos Verigos, T.E.I. of Crete
* Konstantinos Michailidis, T.E.I. of Crete

Team Robo

2013-03-26T13:12:12Z

Vevainu: Created page with 'Team page for Deploying IT Infrastructure Solutions. ==Team Members== * Veiko Vainu, IT College * Andreas Plado, IT College * Konstantinos Verigos, T.E.I. of Crete * Konstan…'

Team page for [[Deploying IT Infrastructure Solutions]].

==Team Members==
* Veiko Vainu, IT College
* Andreas Plado, IT College
* Konstantinos Verigos, T.E.I. of Crete
* Konstantinos Michailidis, T.E.I. of Crete

==Goal==
*Goal 1 form assignment
*Goal 2 form assignment
*Goal 3 form assignment

==Activity==
===Monday - 25.03.13===
Things what we did that day
* First thing
* Second thing

===Tuesday - 26.03.13===
Things what we did that day
* First thing
* Second thing

Problems what we faced:
* First problem
* Second problem

Things what we plan to do:
* First thing
* Second thing

===Wednesday - 27.03.13===
Things what we did that day
* First thing
* Second thing

Problems what we faced:
* First problem
* Second problem

Questions and answers from client:
* First Question
Answer to question

* Second Question
Answer to question

Things what we plan to do:
* First thing
* Second thing

==Results==
Summary of what we did and solution what we developed

===Final documentation===
====Analysis====

====Solution====

==IP Feed-back==
===Member 1 feedback===
I liked this and that.

===Member 2 feedback===
I liked this and that. Didn't like.

V

2013-03-24T13:05:42Z

Vevainu: /* Retsensioonid */

Talk:SaanEndagaHästiLäbi

2013-03-24T13:03:54Z

Vevainu: Created page with '=Meeskond „V“ retsensioon meeskond „SaanEndagaHästiLäbi“ XML-i kohta – 24.03.2013= Esmalt XML struktuuri vaadates jääb silma, et see on väga lihtsa ülesehitus…'

=Meeskond „[[V]]“ retsensioon meeskond „SaanEndagaHästiLäbi“ XML-i kohta – 24.03.2013=
Esmalt XML struktuuri vaadates jääb silma, et see on väga lihtsa ülesehitusega. Selline lihtne ülesehitus ei vasta ülesandes püstitatud nõuetele. XML struktuur on küll kohati 4 dimensiooniga, kuid enamus nendel puuduvad atribuudid täielikult. Samas ülesandepüstituses oli nõutud 3-el dimensioonil atribuute, mis oleks enam kui lihtsalt „ID“. Nii mõnegi elemendi oleks võinud atribuudiks panna, näiteks nagu „id“, „sex“.

XSD skeemifaili puhul hakkab silma, et isikukood kirjutatakse sõnena mille pikkus on piiratud 11 tähemärgini. Võibolla on pikkuse piiramine see põhjus miks kasutati sõne, kuid nii ei välistata tähemärkide sisestamist. Alternatiivina oleks võinud kasutada numbritüüpi ning „totalDigits“ piirangut, mis samuti piiraks numbrite arvu. Kuupäevamuutujate puhul jääb arusaamatuks, miks ei kasutada sisseehitatud ajatüüpe. Muus osas tegu väga põhjaliku skeemifailiga, mis ei jäta XML koostamisel eksimusteks ruumi.

XSLT-d ise käivitada proovides ilmnes, et üheski brauseris see ei funktsioneeri, mõningase uurimise järel selgus, et probleemiks on täpitähed. Kui täpitähed olid eemaldatud, siis XSLT kuvas XML-is peituva isiku info ilusti vormistatult. Ainus silma häiriv tõik on sünniaeg, mis kuvatakse kujul „198911118“, siinkohal oleks võinud selle paremini loetavaks vormistada. Meeldib idee, et sugulaste ID-d on lingid, mille kaudu võiks vajadusel ka nende info kohe kättesaadav olla, kahjuks selle lõpuni teostus oleks nõudnud juba mingisuguse teenuse olemasolu. XSLT stiilifaile oli ülesandepüstituses nõutud 2 või 3, seega on üks ülesande täitmisest puudu.

Kokkuvõtteks on meeskonnal küll mõningaid puudujääke, kuid kohati on tehtud rohkemgi kui vaja, näiteks väga põhjalik XSD fail. Oleks oodanud ka XSLT näidet konkreetse XML-i peal, kuid ülesandepüstitusel seda otseselt nõutud ei olnud. Töö tulemusestest jääb siiski mulje, et XML teema on läbi töötatud ning aru saadud selle rakendamise võimalustest.

Meeskond "[[V]]"

V

2013-03-24T11:04:17Z

Vevainu:

[[Category:Võrgurakendused II: hajussüsteemide ehitamine]]
=Liige=
Veiko Vainu D21
=Retsensioonid=
[https://wiki.itcollege.ee/index.php/Talk:Meeskond_%22asdasdasd%22 Retsensioon meeskond „asdasdasd“ XML-i kohta – 24.03.2013]
=XML fail=
==XML andmefail==
*[http://enos.itcollege.ee/~vevainu/XML/armeeXML.xml XML andmefail]

==XML skeemifail==
*[http://enos.itcollege.ee/~vevainu/XML/armeeXML.xsd XML skeemifail]

==XML stiilifailid==
XML to HTML - Kuvab vasakul pool lehte kogu XML-i sisu nn. puuvaates. Paremal pool on otsing, mis otsib sõduri ees- ja perekonnanimest vastavat stringi.
* [http://enos.itcollege.ee/~vevainu/XML/xmlTOhtml.xslt XML to HTML]
* [http://enos.itcollege.ee/~vevainu/XML/xmlTOhtml.xml Näidis]

XML to XML - Trükib välja kõik sõdurid sorteerides perekonnanime ja seejärel eesnime järgi. Igale sõdurile on lisatud ka uus atribuut ID, mis koosneb sõduri ID-st ja tema rühma, allüksuse ja väeosa ID-st.
* [http://enos.itcollege.ee/~vevainu/XML/xmlTOxml.xslt XML to XML]
* [http://enos.itcollege.ee/~vevainu/XML/xmlTOxml.xml Näidis]

XML to Excel - Loob workbooki iga allüksuse jaoks oma worksheeti kuhu kuvatakse selle üksuse isikkooseis sorteeritult Auastme tähestikulises järjekorras.
* [http://enos.itcollege.ee/~vevainu/XML/xmlTOxlsx.xslt XML to Excel]
* [http://enos.itcollege.ee/~vevainu/XML/xmlTOxlsx.xml Näidis XML]
* [http://enos.itcollege.ee/~vevainu/XML/xmlTOxlsxNAIDE.xlsx Näidis EXCEL]
* Kuidas - tuleb xml faili lisada viide vastavale xslt stylesheetile, seejärel tuleb xml fail Excelis avada ja valida, et kasutatakse vastavat stiilifaili.

==XML kõik ühes (.rar)==
*[http://enos.itcollege.ee/~vevainu/XML/XML.rar Kõik failid ühes (.rar)]

=Veebiteenus=
*PLACEHOLDER

=Klientrakendused=
*PLACEHOLDER

=Logi=
*2013.03.13 – Sai paika pandud XML faili struktuur ja loodud seda genereeriv rakendus.
*2013.03.14 – XSLT faili loomine, lisatud „Puuvaade“ näitamaks kõiki sisendeid.
*2013.03.15 – XSLT failile inimeste otsing vastavalt kasutaja sisendile lisatud (ainult IE). Sai tehtud XSLT fail XML-i transformeerimiseks teistsuguseks XML-iks ja ka XSLT fail XML-i exceli vorminduse jaoks.
*2013.03.20 – XML to HTML otsing töötab nüüd IE, Chrome ja Firefoxiga
**wiki leht loodud,XML wiki lehele lisatud, tehtud stiilifailide näidised

Talk:Meeskond "asdasdasd"

2013-03-24T11:02:46Z

Vevainu: Created page with '=Meeskond „V“ retsensioon meeskond „asdasdasd“ XML-i kohta – 24.03.2013= Esmalt XML faili struktuuri uurimise järel jääb silma selle lihtsus. Lihtne iseenesest e…'

=Meeskond „[[V]]“ retsensioon meeskond „asdasdasd“ XML-i kohta – 24.03.2013=
Esmalt XML faili struktuuri uurimise järel jääb silma selle lihtsus. Lihtne iseenesest ei ole halb, kuid on täitmata ka mõni ülesande tingimus. Ülesandepüstituses oli öeldud, et 3-el XML´i dimensioonil tuleb kasutada atribuute, mis on enamat, kui lihtsalt ID. Konkreetne meeskond on 4jandal dimensioonil lisanud hulgaliselt atribuute, kuid esimesed kolm on neist hoopi ilma atribuutideta. Samas oleks võinud sinna lisada igasugust infot, näiteks „käsitulirelvadele“ mingid tingimused, mis eritstavad neid „revolvritest“.

Meeskond on teinud ka ülesandes mitte nõutud „DTD“ faili, milles lähemalt uurides on mõned arusaamatud asjaolud. Näiteks on „käsitulirelvad“ ja „külmrelvad“ elementide korduvuseks märgitud „null või mitu“, kuid kuna tegemist on grupeerivate elementidega, mida esineb vaid ühel korral oleks võinud olla seal märgitud „null või üks“ esinemiskord. Sama olukord tundub olevat ka nende alamelementidega, vähemalt minule jääb arusaam, et revolvreid, püstoleid, automaate on käsitulirevlvade elemendis tegelikult vaid üks kord.

Käsitsi loodud XSD fail (DTD põhjal) on samasuguste ebakõladega, kuid automaatgenereeritud XSD-l need puuduvad.
XSLT-s on kasutatud põhilisi funktsionaalsusi nagu „for-each“ ja „if“, ning on toodud paar näidet sisulise info välja toomiseks. Oodanud oleks ka näidet XML formaadi muutmise kohta, mida ka ülesandepüstituses on nõutud.

Kokkuvõttes on mõningad pisivead, kuid üldpilt on hea. Jääb mulje, et XML teema on autoritel läbi töötatud ning saadud ka praktiline tulem. Koodi on ka mõningates, võibolla keerulisemates, kohtades kommenteeritud. Logisse on samuti mõned ülestäheldused tehtud, kui seal oleks võinud välja tuua ka reaalse XML tööde kokkupanemise aja, mitte vaid wikisse kandmise kuupäeva.

Meeskond "[[V]]"

V

2013-03-23T16:33:06Z

Vevainu:

[[Category:Võrgurakendused II: hajussüsteemide ehitamine]]
=Liige=
Veiko Vainu D21
=XML fail=
==XML andmefail==
*[http://enos.itcollege.ee/~vevainu/XML/armeeXML.xml XML andmefail]

==XML skeemifail==
*[http://enos.itcollege.ee/~vevainu/XML/armeeXML.xsd XML skeemifail]

==XML stiilifailid==
XML to HTML - Kuvab vasakul pool lehte kogu XML-i sisu nn. puuvaates. Paremal pool on otsing, mis otsib sõduri ees- ja perekonnanimest vastavat stringi.
* [http://enos.itcollege.ee/~vevainu/XML/xmlTOhtml.xslt XML to HTML]
* [http://enos.itcollege.ee/~vevainu/XML/xmlTOhtml.xml Näidis]

XML to XML - Trükib välja kõik sõdurid sorteerides perekonnanime ja seejärel eesnime järgi. Igale sõdurile on lisatud ka uus atribuut ID, mis koosneb sõduri ID-st ja tema rühma, allüksuse ja väeosa ID-st.
* [http://enos.itcollege.ee/~vevainu/XML/xmlTOxml.xslt XML to XML]
* [http://enos.itcollege.ee/~vevainu/XML/xmlTOxml.xml Näidis]

XML to Excel - Loob workbooki iga allüksuse jaoks oma worksheeti kuhu kuvatakse selle üksuse isikkooseis sorteeritult Auastme tähestikulises järjekorras.
* [http://enos.itcollege.ee/~vevainu/XML/xmlTOxlsx.xslt XML to Excel]
* [http://enos.itcollege.ee/~vevainu/XML/xmlTOxlsx.xml Näidis XML]
* [http://enos.itcollege.ee/~vevainu/XML/xmlTOxlsxNAIDE.xlsx Näidis EXCEL]
* Kuidas - tuleb xml faili lisada viide vastavale xslt stylesheetile, seejärel tuleb xml fail Excelis avada ja valida, et kasutatakse vastavat stiilifaili.

==XML kõik ühes (.rar)==
*[http://enos.itcollege.ee/~vevainu/XML/XML.rar Kõik failid ühes (.rar)]

=Veebiteenus=
*PLACEHOLDER

=Klientrakendused=
*PLACEHOLDER

=Logi=
*2013.03.13 – Sai paika pandud XML faili struktuur ja loodud seda genereeriv rakendus.
*2013.03.14 – XSLT faili loomine, lisatud „Puuvaade“ näitamaks kõiki sisendeid.
*2013.03.15 – XSLT failile inimeste otsing vastavalt kasutaja sisendile lisatud (ainult IE). Sai tehtud XSLT fail XML-i transformeerimiseks teistsuguseks XML-iks ja ka XSLT fail XML-i exceli vorminduse jaoks.
*2013.03.20 – XML to HTML otsing töötab nüüd IE, Chrome ja Firefoxiga
**wiki leht loodud,XML wiki lehele lisatud, tehtud stiilifailide näidised