This link has been bookmarked by 33 people . It was first bookmarked on 08 Jul 2006, by WittyGuy.
-
28 May 11
-
22 Oct 08
Lakshminarayanan VenugopalUML Reference
-
06 Mar 08
-
23 Nov 07
-
07 Sep 07
-
27 Jun 07
-
26 Jun 07
-
-
25 Jun 07
-
contain the business functionality
-
transfer control
-
don't contain any business functionality
-
provides only a definition of business functionality of a system
-
Only one stereotype can be created for any UML element in the same system
-
constraints are the business rules that the class must follow
-
Notes contain additional information for reference while developing the system
-
attributes.
-
a class also has properties that reflect unique features of a class
-
group together classes and/or interfaces that are either similar in nature or related.
-
Different classes belonging to different and discrete hierarchies can maintain their distinct hierarchies and still realize the functionality defined in the methods of the interface.
-
Analysis classes are also called stereotypes
-
Analysis classes
-
represents an entity of a given system that provides an encapsulated implementation of certain functionality
-
use cases talk about "what are the requirements" of a system
-
classes in a class diagram are interconnected in a hierarchical fashion
-
A class diagram consists of a group of classes and interfaces reflecting important entities of the business domain of the system being modeled, and the relationships between these classes and interfaces.
-
-
03 May 07
-
30 Mar 07
-
26 Jul 06
-
16 Mar 06
-
01 Feb 06
-
24 Jan 06
-
22 Dec 05
-
14 Dec 05
-
17 Sep 04
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.