rup analysis class 5B5A476F






Work Product (Artifact): Analysis Class








var defaultQueryStr = '?proc={002674F9-6511-4D15-8623-B761D8C48986}&path={002674F9-6511-4D15-8623-B761D8C48986},{F2160C54-F666-4736-9982-FC7F58F15FAD},_kU-isL9dEdqBwpaAk4N49g';
var backPath = './../../';
var imgPath = './../../images/';
var nodeInfo=null;
contentPage.preload(imgPath, backPath, nodeInfo, defaultQueryStr, false, true, false);










Work Product (Artifact): Analysis Class















This work product specifies elements of an early conceptual model for 'things in the system which have responsibilities and behavior'.






Purpose



Analysis classes are used to capture the major "clumps of responsibility" in the system.



Relationships



Container Artifact


Analysis Model





RolesResponsible:



Designer


Modified By:




Main Description



Analysis Classes specify elements of an early conceptual model for 'things in the system which have responsibilities and behavior'. They represent the prototypical classes of the system, and are a 'first-pass' at the major abstractions that the system must handle. Analysis classes may be maintained in their own right, if a "high-level", conceptual overview of the system is desired. Analysis classes also give rise to the major abstractions of the system design: the design classes and subsystems of the system.



Properties



Optional


Planned



Tailoring



Representation Options UML Representation: Class, stereotyped as <<boundary>>, <<entity>> or <<control>>.  An analysis class may have the following properties: name: the name of the class  description: brief description of the role of the class in the system responsibilities: a listing of the responsibilities of the class attributes: the attributes of the class   The analysis classes, taken together, represent an early conceptual model of the system. This conceptual model evolves quickly and remains fluid for some time as different representations and their implications are explored. Formal documentation can impede this process, so be careful how much energy you expend on maintaining this 'model' in a formal sense; you can waste a lot of time polishing a model which is largely expendable. Analysis classes rarely survive into the design unchanged. Many of them represent whole collaborations of objects, often encapsulated by subsystems. Usually, simple note-cards, such as the example below, are sufficient (this is based on the well-known CRC Card technique - see [WIR90] for details of this technique). On the front side of the card, capture the name and description of the class. An example for a Course in a course registration system is listed below: Class Name Course Description The Course is responsible for maintaining information about a set of course sections having a common subject, requirements and syllabus.  Responsibilities To maintain information about the course.  Attributes Name Description Type Course Title The name of the course string Description A short description of the course string On the back of the card, draw a diagram of the class: Class diagram for Course There is one analysis class card for each class discovered during the use-case-analysis workshop.



More Information



Checklists


Analysis Class





Guidelines


Analysis Class








©  Copyright IBM Corp. 1987, 2006.  All Rights Reserved.







contentPage.onload();
contentPage.processPage.fixDescriptorLinks();




Wyszukiwarka

Podobne podstrony:
rup analysis class?F7CE03
analysis class~97273E
rup analysis?sign discipline)760231

więcej podobnych podstron