Monday, 28 October 2013

Class Diagram



Blog is short for web log is a web application that resembles the form of writings ( published as a post ) on a public web page . These writings are often published in reverse order ( most recent content first and then followed the older content ) , although not necessarily so . Web sites like these can usually be accessed by all Internet users according to the topics and goals of the user's blog .
Class diagrams are used to show classes and packages in the system . Class diagram gives an overview of the system and the static relationships between them . Typically , dibua some class diagrams for a single system . Some diagrams will show a subset of the classes and their relationships . Can be made ​​a few diagrams as desired to get a complete picture of the system is built .
Class diagram is the best tool for the design of the development team . The diagram helps developers get the system structure before the code is written , and help to ensure that the system is the best design .
Class diagrams are used to display diagam several classes and packages that exist in the system / software we're using.
Class diagram gives us a picture (static diagram) of the system / software and relas-relationships that exist therein.
The class diagram is the main building block of object oriented modelling. It is used both for general conceptual modelling of the systematics of the application, and for detailed modelling translating the models into programming code. Class diagrams can also be used for data modeling.The classes in a class diagram represent both the main objects, interactions in the application and the classes to be programmed.
In the diagram, classes are represented with boxes which contain three parts:
  • The top part contains the name of the class
  • The middle part contains the attributes of the class
  • The bottom part gives the methods or operations the class can take or undertake
There are five key relationships between classes in a UML class diagram : dependency, aggregation, composition, inheritance and realization. These five relationships are depicted in the following diagram:

The above relationships are read as follows:
  • Dependency : class A uses class B
  • Aggregation : class A has a class B
  • Composition : class A owns a class B
  • Inheritance : class B is a Class A  (or class A is extended by class B)
  • Realization : class B realizes Class A (or class A is realized by class B)
What I hope to show here is how these relationships would manifest themselves in Java so we can better understand what these relationships mean and how/when to use each one.

Dependency

Dependency is a weaker form of relationship which indicates that one class depends on another because it uses it at some point in time. One class depends on another if the independent class is a parameter variable or local variable of a method of the dependent class. This is different from an association, where an attribute of the dependent class is an instance of the independent class.

Dependency is represented when a reference to one class is passed in as a method parameter to another class. For example, an instance of class B is passed in to a method of class A:  
?


Aggregation

Aggregation is a variant of the “has a” association relationship; aggregation is more specific than association. It is an association that represents a part-whole or part-of relationship. As a type of association, an aggregation can be named and have the same adornments that an association can. However, an aggregation may not involve more than two classes.
Aggregation can occur when a class is a collection or container of other classes, but where the contained classes do not have a stronglife cycle dependency on the container—essentially, if the container is destroyed, its contents are not.
In UML, it is graphically represented as a hollow diamond shape on the containing class end of the tree with a single line that connects the contained class to the containing class. The aggregate is semantically an extended object that is treated as a unit in many operations, although physically it is made of several lesser objects.

Now, if class A stored the reference to class B for later use we would have a different relationship called Aggregation. A more common and more obvious example of Aggregation would be via setter injection: 
?


Composition

Composition is a stronger variant of the “owns a” association relationship; composition is more specific than aggregation.
Composition usually has a strong life cycle dependency between instances of the container class and instances of the contained class(es): If the container is destroyed, normally every instance that it contains is destroyed as well. (Note that, where allowed, a part can be removed from a composite before the composite is deleted, and thus not be deleted as part of the composite.)
The UML graphical representation of a composition relationship is a filled diamond shape on the containing class end of the tree of lines that connect contained class(es) to the containing class.Aggregation is the weaker form of object containment (one object contains other objects). The stronger form is called Composition. In Composition the containing object is responsible for the creation and life cycle of the contained object. Following are a few examples of Composition. First, via member initialization: 
?



?


Realization

In UML modelling, a realization relationship is a relationship between two model elements, in which one model element (the client) realizes (implements or executes) the behavior that the other model element (the supplier) specifies.
The UML graphical representation of a Realization is a hollow triangle shape on the interface end of the dashed line (or tree of lines) that connects it to one or more implementers. A plain arrow head is used on the interface end of the dashed line that connects it to its users. In component diagrams, the ball-and-socket graphic convention is used (implementors expose a ball or lollipop, while users show a socket).
Realizations can only be shown on class or component diagrams.
A realization is a relationship between classes, interfaces, components, and packages that connects a client element with a supplier element. A realization relationship between classes and interfaces and between components and interfaces shows that the class realizes the operations offered by the interface.



?




Monday, 7 October 2013

Usecase diagram blog





A use case diagram at its simplest is a representation of a user's interaction with the system and depicting the specifications of a use case. A use case diagram can portray the different types of users of a system and the various ways that they interact with the system. This type of diagram is typically used in conjunction with the textual use case and will often be accompanied by other types of diagrams as well.
the use case that is used in case there are 3 actors blog .
ie user , admin and visitors . the blog admin person or machine can check every transaction that occurs in the blog .
while the user and the visitor is a person who uses blogs .
differences between the visitor and the user is the user has the right ases over the visitors and he , too, who provide information on the blog for the visitor .
while the visitor is a user that the user can only see the contents of the blog and comment .
user has full rights to the use of blogs like viewing messages, manage massage , manage profile and manage post . but to manage posts and manage user profiles must log in first.
while posting and saw no need to manage the massage . if you want to post then the user must do is to manage the post where the user can create new posts , edit existing posts , or delete existing posts . whereas in the manage user profiles can add their profile , change their profile or
delete their profil

sumber id.wikipedia.org

Monday, 23 September 2013

Ikimono Gakari

kimono-gakari (いきものがかり also "Ikimonogakari") is a Japanese pop rock band from Kanagawa. The group started in February 1999 with Hotaka Yamashita and Yoshiki Mizuno, and was joined by vocalist Kiyoe Yoshioka in December. The group's name is a reference to ikimono-gakari (生き物係), a group of children who are responsible for looking after plants and animals in Japanese elementary schools. In 2006, the group released its first single on Sony Music Entertainment Japan's Epic Records label. Several of its albums have reached number one on the Oricon Weekly, and its songs have been featured on various media from anime shows such as Naruto to the Olympic broadcast theme song for NHK and the set piece for a national junior high music competition.

MEMBERS:
 

Hotaka Yamashita (山下穂尊, Yamashita Hotaka?, born August 27, 1982) is from Ebina-shi, Kanagawa Prefecture. He is a graduate of Atsugi High School and the Faculty of Social Sciences, Hosei University. He plays the guitar and harmonica, and has written lyrics and melodies to some of the band's songs. His nicknames are Hocchi and Yama-chan.
Yoshiki Mizuno (水野良樹, Mizuno Yoshiki?, born December 17, 1982) is from Ebina-shi, Kanagawa Prefecture. He is a graduate of Atsugi High School and the Faculty of Social Sciences, Hitotsubashi University. He is the leader of the band, and plays the guitar and vocals. He has also written lyrics and melodies to some of the band's songs. His nickname is Yocchan.

Kiyoe Yoshioka (吉岡聖恵, Yoshioka Kiyoe?, born February 29, 1984) is from Atsugi-shi, Kanagawa Prefecture. Her parents are farmers. She is a graduate of Ebina High School and the Showa Academia Musicae Junior College. She is the band's lead vocalist, and has written lyrics to some of the band's songs. Her older brother was a classmate of both Hotaka and Yoshiki at high school. Her nicknames are Yosshie, Kiyoe-chan and Kiyorasu (by Shouko Nakagawa). She joined the band in high school when she suddenly saw Yamashita and Mizuno singing in front of the train station. She used to belong to a children theatrical company.


Musical style
 

Ikimono-gakari's musical style stems from their original lounge rock style found on their first three mini albums under Cubit Club. Their primary instruments were the acoustic guitar, the electric guitar, and the harmonica. Their initial music was considerably slower; "Natsu Koi" on Sakura Saku Machi Monogatari is considerably faster in tempo compared to the same song on Makoto ni Senetsu Nagara First Album wo Koshirae Mashita.... Guitarist and band leader Yoshiki Mizuno also sang considerably more on their indie albums.
With the release of their first major-label album, Sakura Saku Machi Monogatari, their style changed to a more conventional rock style, but still keeping with their traditional guitar-harmonica combination. They also began to add other elements to their songs, such as strings and tambourines, as evidenced by "Sakura" and "Kira Kira Train". Additionally, they recorded songs with faster tempos, such as "Ryūsei Miracle" and "Hinageshi".
Ikimono-gakari began to shift to a more mainstream pop sound with their second and third albums, Life Album and My Song Your Song. Songs like "Kimagure Romantic" differed greatly from their songs during the Sakura Saku era. Life Album saw the revival of a couple of songs from their indie albums; "Hana wa Sakura Kimi wa Utsukushi" from Makoto ni Senetsu... and "Chikoku Shichau yo" from Jinsei Sugoroku Dabe. "Kuchidzuke", also from Jinsei Sugoroku Dabe. was revived on My Song Your
source:
http://www.jpopasia.com/group/ikimonogakari/
http://en.wikipedia.org/wiki/Ikimono-gakari


back-on

 BACK-ON


Back-On (stylized as BACK-ON) is a Japanese rock band from Tokyo, Japan. They are recognized for creating anime and game opening themes such as the Tales of the World: Radiant Mythology 2 opening theme, "fly away"; Air Gear opening theme, "Chain"; Murder Princess opening theme "Hikari Sasuhou (fk Metal ver.)" and Eyeshield 21s "Blaze Line". etc., although they have also written ending themes for both anime and TV shows. These include "flower" and "a day dreaming..." for Eyeshield 21, and "Butterfly" for the late-night TV drama Shinjuku Swan, and most recently "Sands of Time" for the mobile robot TV drama Keitai Sousakan 7.

Band members
Current
Kenji03 - Vocals, Emcee, Guitar
Birth date: 25.09.1984
Zodiac: Libra
Blood type: O


Teeda - Emcee
Birth date: 28.12.1984
Zodiac: Capricorn
Blood type: A


Gori - Bass Guitar
Birth date: 13.06.1984
Zodiac: Gemini
Blood type: B


Shu - Lead Guitar
Birth date: 24.10.1984
Zodiac: Scorpio
Blood type: B


Icchan - Drums
Birth date: 02.10.1985
Zodiac: Libra
Blood type: B


Former
Macchin - Drums


source:
http://www.jpopasia.com/group/backon/
http://en.wikipedia.org/wiki/Back-On

 

 


Kana nishino

Kana Nishino


Kana Nishino (西野 カナ Nishino Kana, born March 18, 1989 in Matsusaka, Mie, Japan)also known as kanayan is a J-Pop singer and lyricist signed with SME Records' Newcome Inc. She debuted on February 20, 2008, with the single "I". CNN said that she was the favorite singer of teenage girls in Shibuya, Tokyo, signalling Sony's jump on the bandwagon effect started by Avex.

From young, Nishino learned English from Eikaiwa schools and went to America twice. She was already interested in various genres of music, including hip-hop, R&B and reggae. In addition, she also enjoys traditional Japanese literature, and started singing Japanese folk songs.When she was 16, her mother secretly sent a demo tape of hers to the Miss Phoenix Audition  and she was rated the top singer entrant out of approximately 40,000 applicants. In 2006, she signed a contract with SME Records.

source :
 http://en.wikipedia.org/wiki/Kana_Nishino
http://www.jpopasia.com/celebrity/kananishino/

Sunday, 9 September 2012

Tugas Pemograman Web


1.       Carilah tag HTML yang dapat digunakan pada bagian HEAD diluar dari yang disampaikan diperkuliahan beserta contoh penggunaannya.
a.       base
Format : <BASE [TARGET] [HREF=url]>
b.       link
<a name="nama_link_tujuan">deskripsi tujuan</a>
c.       script
<script type="text/javascript">
document.write("Hello World!")
</script>
d.       noscript
<noscript>Your browser does not support JavaScript!</noscript>
 

2.       Carilah tag HTML yang dapat digunakan pada bagian BODY diluar dari yang disampaikan diperkuliahan beserta contoh penggunaannya.
a.       Tag <DIV>…..</DIV>
</div>
<div style="color:blue">
<h1>heading warna blue</h1>
<p>teks dalam paragraf berwarna blue</p>
</div>
b.       Tag ADDRESS
<address>
<h5>Author:</h5>
Endang<a href="mailto:endang2001@hotmail"><br>
endang2001@hotmail.com</a><br>
</address>

c.       FLOATING OBJEK

                         <html>
<head>
<title>Floating Objek</title>
</head>
<body bgcolor=lightgrey>
<h3>Floating Objek</h3>
d.       Order list
<OL>
<LH><EM>Dibawah ini aalah warna Pelangi : </EM><BR><BR>
<LI>Merah
<LI>Jingga
<LI>Kuning
<LI>Hijau
<LI>Biru
<LI>Nila
<LI>Ungu
</OL>
e.       Unordered List
<UL>
      <LH><EM>Planet dalam sistem tata surya : </EM><BR><BR>
      <LI>Merkurius
      <UL>
                                <LI>57,9 juta kilometer dari matahari
                                <LI>Tidak punya satelit
      </UL>
      <LI>Venus
      <UL>
                                <LI>108 juta kilometer dari matahari
                                <LI>Tidak punya satelit
      </UL>
      <LI>Bumi
      <UL>
                                <LI>149,6 juta kilometer dari matahari
                                <LI>Satu satelit = Bulan
      </UL>
      <LI>Mars
      <UL>
                                <LI>227,9 kilometer dari matahri
                                <LI>Dua satelit =
                                <UL START = 1>
                        <LI>Phobos
                        <LI>Deimos
                                </UL>
      </UL>
</UL>