Skip to main content

Home/ SoftwareEngineering/ Group items matching "aggregation" in title, tags, annotations or url

Group items matching
in title, tags, annotations or url

Sort By: Relevance | Date Filter: All | Bookmarks | Topics Simple Middle
kuni katsuya

UML Association - relationship between classifiers to show that instances of classifiers could be either linked to each other or combined into some aggregation. - 0 views

www.uml-diagrams.org/association.html

UML association

shared by kuni katsuya on 05 Sep 12 - No Cached
  • UML Association
  • Aggregation
  • aggregation
  • ...28 more annotations...
  • composition
  • shared aggregation
  • composite aggregation
  • (shared) part could be included in several composites
  • if composite is deleted, shared parts may still exist.
  • hollow diamond
  • Composition
  • "strong" form of aggregation.
  • "weak" form of aggregation
  • whole/part relationship,
  • composite (whole) is deleted, all of its composite parts are "normally" deleted with it.
  • aggregation
  • Aggregation
  • "weak" form of aggregation
  • composite aggregation
  • composition
  • shared aggregation (
  • same (shared) part could be included in several composites
  • composite is deleted, shared parts may still exist.
  • hollow diamond a
  • Composition
  • "strong" form of aggregation
  • part could be included in at most one composite
  • whole/part relationship,
  • composite (whole) is deleted, all of its composite parts are "normally" deleted with it.
  • filled black diamond
  • N-ary Association
  • more than two ends can only be drawn this way.
kuni katsuya

UML 2 Class Diagram Guidelines - 0 views

www.agilemodeling.com/...classDiagram.htm

uml class diagram best practices

shared by kuni katsuya on 19 Dec 12 - Cached
  • UML 2 Class Diagram Guidelines
  • 1.        General Guidelines
  • 2.        Class Style Guidelines
  • ...49 more annotations...
  • Use Common Terminology for Names
  • Prefer Complete Singular Nouns for Class Names
  • Name Operations with a Strong Verb
  • Name Attributes With a Domain-Based Noun
    • kuni katsuya
      kuni katsuya on 19 Dec 12
       
      don't just use the attribute's type with first character lower cased!!! argghhh!  (eg. instead of Node node, Node parent)
  • Do Not Model Scaffolding Code
  • Include an Ellipsis ( … ) At The End of Incomplete Lists
  • Develop Consistent Method Signatures
  • Avoid Stereotypes Implied By Language Naming Conventions
  • 3.        Interfaces
  • Name Interfaces According To Language Naming Conventions
    • kuni katsuya
      kuni katsuya on 19 Dec 12
       
      I+ is NOT an acceptable naming convention!  this is a very dumb, thoughtless, pointless convention originated by microsoft
    • kuni katsuya
      kuni katsuya on 19 Dec 12
  • Do Not Model the Operations and Attributes of an Interface in Your Classes
  • Consider an Interface to Be a Contract
  • 4.        Relationship Guidelines
  • Model Relationships Horizontally
  • Depict Similar Relationships Involving A Common Class As A Tree
  • Always Indicate the Multiplicity
  • reduce clutter in the diagram
  • Avoid a Multiplicity of “*”
  • Replace Relationships By Indicating Attribute Types
    • kuni katsuya
      kuni katsuya on 19 Dec 12
       
      if dependency relationships were drawn between every class and the types of it's attributes, the class diagram becomes cluttered very quickly this dependency is obvious if the type is indicated for each attribute
  • Do Not Model Every Single Dependency
    • kuni katsuya
      kuni katsuya on 19 Dec 12
       
      generalization of #7 what you show/don't show depends on the main concepts  you're trying to convey in any specific diagram
  • Write Concise Association Names In Active Voice
  • Indicate Directionality To Clarify An Association Name
  • Name Unidirectional Associations In The Same Direction
  • Indicate Role Names When Multiple Associations Between Two Classes Exist
  • Indicate Role Names on Recursive Associations
    • kuni katsuya
      kuni katsuya on 19 Dec 12
       
      eg. parent, child
  • Make Associations Bi-Directional Only When Collaboration Occurs In Both Directions
  • Question Multiplicities Involving Minimums And Maximums
    • kuni katsuya
      kuni katsuya on 19 Dec 12
       
      this just leads to stupid programming practices like hard-coding array sizes, making code more brittle
  • 6.        Inheritance Guidelines
  • “is a”
  • “is like” relationships
  • Apply the Sentence Rule For Inheritance
  • Place Subclasses Below Superclasses
  • A Subclass Should Inherit Everything
    • kuni katsuya
      kuni katsuya on 19 Dec 12
       
      if a subclass sets an attribute to null, implements a method returning null or throwing a NotImplementedException, it really isn't a subclass, or the superclass needs to be decomposed
  • 7.        Aggregation and Composition Guidelines
  • object is made up of other objects
  • aggregation
  • “is part of” relationships
  • whole-part relationship between two objects
  • Composition
  • stronger form of aggregation where the whole and parts have
  • coincident lifetimes, and it is very common for the whole to manage the lifecycle of its parts
  • Apply the Sentence Rule for Aggregation
  • Depict the Whole to the Left of the Part
  • Don’t Worry About Getting the Diamonds Right
  • associations, aggregation, composition, dependencies, inheritance, and realizations
  • line on a UML class diagram
  • defines a cohesive set of behaviors
  • Indicate Visibility Only On Design Models
  • Design Class Diagrams Should Reflect Language Naming Conventions
kuni katsuya

Seam Framework - What is the purpose of the @Model annotation? - 0 views

sfwk.org/...ThePurposeOfTheModelAnnotation

cdi stereotype annotation

shared by kuni katsuya on 12 Jul 12 - No Cached
  • A stereotype is an annotation that aggregates other annotations
  • @Named @RequestScoped @Stereotype
  • @interface Model
  • ...3 more annotations...
  • @Model stereotype; it lets you give a bean a name, and set its scope to @RequestScoped in one stroke
  • What is the purpose of the @Model annotation?
  • The @Model annotation does to things: it makes the bean request-scoped (instead of dependent, the default) it gives the bean an EL name
  • kuni katsuya on 12 Jul 12
     
    A stereotype is an annotation that aggregates other annotations
kuni katsuya

Seam Framework - Where can I find the JavaDoc for all of Java EE 6? - 0 views

sfwk.org/...IFindTheJavaDocForAllOfJavaEE6

javaee6 javadoc

shared by kuni katsuya on 12 Jul 12 - No Cached
  • Where can I find the JavaDoc for all of Java EE 6? You can find the aggregated JavaDoc for the whole Java EE 6 platform here.
kuni katsuya

UML Class Diagrams - structure diagrams which show architecture of the designed system using class, interface, association, composition, aggregation, dependency, etc. - 0 views

www.uml-diagrams.org/class-diagrams.html

UML ClassDiagram

shared by kuni katsuya on 03 Sep 12 - No Cached
  • «Boundary»
  • Boundary is a stereotyped class or object that represents some system boundary
  • «Control»
  • ...31 more annotations...
  • Control is a stereotyped class or object that is used to model flow of control or some coordination in behavior
  • usually describe some "business logic"
  • «Entity»
  • Entity is a stereotyped class or object that represents some information or data, usually but not necessarily persistent.
  • Features of a class are
  • attributes
  • operations
  • Static features are underlined
  • «Boundary»
  • «Boundary»
  • «Control»
  • «Entity»
  • «Control»
  • Interface
  • An interface is a classifier that declares of a set of coherent public features and obligations
  • specifies a contract.
  • Data Type
  • A data type is a classifier - similar to a class - whose instances are
  • identified only by their value
  • typical use of data types would be to represent value types
  • «dataType»
  • Enumeration
  • An enumeration is a data type whose values are enumerated in the model as user-defined enumeration literals.
  • «enumeration».
  • Multiplicity
  • Multiplicity allows to specify cardinality (allowed number of instances) of described element
  • Visibility
  • UML has the following types of visibility: public package protected private
  • Package visibility is represented by '~' literal.
  • Protected visibility is represented by '#' literal.
  • Private visibility is represented by '-' literal.
kuni katsuya

AuthorizationInfo (Apache Shiro 1.2.1 API) - 0 views

shiro.apache.org/...AuthorizationInfo.html

security ApacheShiro authorization AuthorizationInfo

shared by kuni katsuya on 09 Sep 12 - No Cached
  • AuthorizationInfo
  • represents a single Subject's stored authorization data (roles, permissions, etc)
  • Roles are represented as a Collection of Strings
  • ...4 more annotations...
  • Permissions are provided in two ways:
  • Collection of Strings
  • Collection of Permission objects
  • represent the total aggregate collection of permissions
1 - 11 of 11
Showing 20▼ items per page