Rabu, 23 Oktober 2013

Class Diagram Blog

































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 .

Class Definition Diagram

Class is a collection of objects with and that have a common structure , common behavior , common relationships , and semantic / general word . Classes determined / discovered by examining objects in sequence diagrams and collaboration diagrams . A class is described as a square with three parts of the room . Class should be named using a noun according to domain / section / group ( Jeffery L. Whitten et al , 2004) .

Class Diagram is a diagram that shows the existing classes of a system and its relationship with logic. Class diagrams describe the static structure of a system . Because the class diagram is the backbone or basic strength of almost any object -oriented method including UML ( Henderi , 2008) . While according to ( Jeffery L. Whitten et al 2004:432 ) class diagram is a graphic image of the static object structure of a system , showing object classes that make up a system and also the relationship between the object class .
Elements - elements relevant in modeling UML class diagram consists of : classes , class structure , the nature of class ( class behavior) , association / union ( association ) , collection / unity ( aggregation ) , dependency (dependency ) , derivatives relations , diversity and navigation indicators , and role name ( role / task name ) .

Class diagram symbols

1 . Class : Class is a block - the building blocks of class -oriented programming obyek.Sebuah described as a box that is divided into 3 parts . The upper part is a part of the class name . Defines the center of the property / class attribute . The final section defines methodmethod of a clas .
2 . Association : An association is a relationship between the 2 most common class and is represented by a line connecting the two classes . This line could symbolize the types of relationship and also can display the multiplicity of laws in a relationship . ( Example : One -to -one , one- to-many , many-to -many )
3 . Composition : If a class can not stand alone and must be part of another class , then the class has a Composition relation to the class in which he relies . A composition relationship is described as a line with the tip of a parallelogram -shaped features / solid
4 . Dependency : Sometimes a class uses another class . This is called a dependency . Generally use the dependency is used to indicate operation in a class that uses another class . A dependency is represented as a dotted arrow .

5 . Aggregation : Aggregation indicates a whole part relationship and is usually referred to as relations .

Rabu, 16 Oktober 2013

UseCase Diagram Blog

usecase diagram blog
A use case diagram is a graphic depiction of the interactions among the elements of a system. A use case is a methodology used in system analysis to identify, clarify, and organize system requirements. In this context, the term "system" refers to something being developed or operated, such as a mail-order product sales and service Web site. Use case diagrams are employed in UML (Unified Modeling Language), a standard notation for the modeling of real-world objects and systems.
System objectives can include planning overall requirements, validating a hardware design, testing and debugging a software product under development, creating an online help reference, or performing a consumer-service-oriented task. For example, use cases in a product sales environment would include item ordering, catalog updating, payment processing, and customer relations. A use case diagram contains four components.
·         The boundary, which defines the system of interest in relation to the world around it.
·         The actors, usually individuals involved with the system defined according to their roles.
·         The use cases, which are the specific roles played by the actors within and around the system.
·         The relationships between and among the actors and the use cases.