Java Source

Tuesday, October 10, 2006

SVN

Jak správně nainstalovat a nakonfigurovat SVN?

Stáhnete si z následující adresy (http://subversion.tigris.org/) potřebný spustitelný soubor a nainstalujete si SVN na své PC.
Dále je pro instalaci je potřeba service soubor . Až si ho nakopirujete do složky /bin, spustíte ji přes příkazový řádek s následujícími parametry:
SVNService.exe -install -d -r c:\svn , tak můžete pokračovat v dál.

Po instalaci SVN vytvoříme repository:
svnadmin create --fs-type bdb c:\svn\muhehe
- vytvoříme reposit \muhehe

Získání informací o konkrétním depositoru:
svn info c:\SVN\muhehe
svn info file:///c:\SVN\muhehe
svn info svn://localhost/muhehe

Pak se pokusíme vypsat checked files:
svn co file:///SVN

Vytvoření adresáře v SVN:
mkdir -m "Komentar..." svn://localhost/muhehe/novyadresar

Jak smazat servis:
sc delete SVNService

Na konec jsem našel link na konfigurační spustitelný soubor. Jmenuje se svn1clicksetup. Stačí se po něm podívat na výše zmíněném odkazu.

Monday, October 02, 2006

UML - just my kidding... no more.

UML is unified modeling language, witch serves for modeling and desing of applications. I studied UML on university for one semester. I gues that UML can be learn in two months. I was working on some project where we used some practice from UML. For instance we used use case and class diagrams. I think that this both diagrams is general for application development. Another diagram can be use for closer application specification.
Individuale aspects of UML is mainly "Requirements", "Analyse", "Design" and "Implementation".

So now I describe individual aspects of UML:
A. Requirements:
1. We must know wath we want do. And for this we must do requierement and specification analysis. Than if we have this analys we can continue with another aspects.
2. Second, and wery useful aspect is "Use Diagram". Use diagram is using for modeling witch roles has actors in our applications and with activities he can do.
B. Analyse:
3. In this part we want find classes and objects. These classes and objects we can find in use case diagrams and we can do some textual analyse, where we find names of classes. After when we have names of classes we can start with finding asociations betwen these classes. For making asociations we can use inheritance, polymorphism, agregations and composits. Then we can make activity diagrams. In activities diagrams we want describe proces like as "Object oriented diagram of flows". Thanks to them we can make model contains of activyties collection and state transitions.
C. Desing:
In desing part we want make and specify classes from analyse part. Actualy in this part we implement use cases. Indivisible part of desing is "State diagrams". In state diagrams we want catch witch states objects we can have.
D. Implementation:
In this part we want sort classes to the specify components. Implementation is about transalation model to code.