Payment. amount. Payment. amount: Money. getbalance(): Money

Transcription

1 Dpto. de Computación y T.I. Taller de Ingeniería de Software Clase 5

2 Agenda 1.Exposición por equipos: Diagrama de Clases de Análisis 2. Diagrama de Clases 3.Traducción clases a Esquema Relacional 3. 4.Asignación próxima semana

3 Diagramas de Clases Del modelo del dominio al modelo de diseño

4 Clases e Instancias

5 Modelo de diseño UP Domain Model Stakeholder's view of the noteworthy concepts in the domain. A Payment in the Domain Model is a concept, but a Payment in the Design Model is a software class. They are not the same thing, but the former inspired the naming and definition of the latter. This reduces the representational gap. This is one of the big ideas in object technology. Payment amount Payment amount: Money 1 Pays-for 1 inspires objects and names in 1 1 Pays-for date time Sale Sale date: Date starttime: Time getbalance(): Money gettotal(): Money... Domain layer of the architecture in the UP Design Model The object-oriented developer has taken inspiration from the real world domain in creating software classes. Therefore, the representational gap between how stakeholders conceive the domain, and its representation in software, has been lowered.

6 Notación Diagrama de clases 3 common compartments 1. classifier name 2. attributes 3. operations an interface shown with a keyword «interface» Runnable run() SuperclassFoo or SuperClassFoo { abstract } - classorstaticattribute : Int + publicattribute : String - privateattribute assumedprivateattribute isinitializedattribute : Bool = true acollection : VeggieBurger [ * ] attributemaylegallybenull : String [0..1] finalconstantattribute : Int = 5 { readonly } /derivedattribute + classorstaticmethod() + publicmethod() assumedpublicmethod() - privatemethod() # protectedmethod() ~ packagevisiblemethod() «constructor» SuperclassFoo( Long ) methodwithparms(parm1 : String, parm2 : Float) methodreturnssomething() : VeggieBurger methodthrowsexception() {exception IOException} abstractmethod() abstractmethod2() { abstract } // alternate finalmethod() { leaf } // no override in subclass synchronizedmethod() { guarded } officially in UML, the top format is used to distinguish the package name from the class name unofficially, the second alternative is common dependency java.awt::font or java.awt.font plain : Int = 0 { readonly } bold : Int = 1 { readonly } name : String style : Int = 0 getfont(name : String) : Font getname() : String Fruit interface implementation and subclassing run() SubclassFoo - ellipsis means there may be elements, but not shown - a blank compartment officially means unknown but as a convention will be used to mean no members association with multiplicities 1 order PurchaseOrder

7 Diagrama de clases Domain Model conceptual perspective Register 1 Captures 1 Sale time iscomplete : Boolean /total Register Sale Design Model DCD; software perspective endsale() enteritem() makepayment() 1 currentsale time iscomplete : Boolean /total makelineitem()

8 Diagrama de clases applying the guideline to show attributes as attribute text versus as association lines id: Int Register 1 currentsale Sale time: DateTime Register has THREE attributes: 1. id 1 2. currentsale 3. location location Store address: Address phone: PhoneNumber

9 Diagrama de clases Sale SalesLineItem time: DateTime lineitems : SalesLineItem [1..*] or lineitems : SalesLineItem [1..*] {ordered} Two ways to show a collection attribute Sale time: DateTime 1..* lineitems {ordered, List} SalesLineItem notice that an association end can optionally also have a property string such as {ordered, List}

10 Diagrama de clases three ways to show UML constraints Stack size : Integer { size >= 0 } push( element ) pop() : Object { post condition: new size = old size + 1 } { post condition: new size = old size 1 }

11 Diagrama de clases Company * Employs * Person a person may have employment with several companies salary startdate Employment

12 Diagrama de clases UML notation: in a class box, an underlined attribute or method indicates a static (class level) member, rather than an instance member ServicesFactory instance : ServicesFactory accountingadapter : IAccountingAdapter inventoryadapter : IInventoryAdapter taxcalculatoradapter : ITaxCalculatorAdapter getinstance() : ServicesFactory 1 UML notation: this '1' can optionally be used to indicate that only one instance will be created (a singleton) getaccountingadapter() : IAccountingAdapter getinventoryadapter() : IInventoryAdapter gettaxcalculatoradapter() : ITaxCalculatorAdapter

13 Diagrama de clases Revisar clase 6 teoría Traducción clases a Relacional Revisar clase 7 teoría

14 Traducción clases a Relacional Manufacturer name city : Manufacturer name = Now&Zen city = Mumbai MANUFACTURER TABLE name Now&Zen Celestial Shortening city Mumbai San Ramon

15 Traducción clases a Relacional aggregate signifies a referential constraint: a ProductDescription row can't exist without a related Manufacturer row «Table» Manufacturer «PK» OID : char(16) Name : varchar(100) City : varchar(50) 1 PK - primary key FK - foreign key * «Table» ProductDescription «PK» OID : char(16) Description : varchar(100) «FK» Manu_OID : char(16)

16 Plan de Implementación Planificación de las actividades de implementación, prueba e integración de los casos de uso asignados para cumplir con la meta de un prototipo semana 10 y producto final semana 11

17 Plan de Implementación

18 Próxima Entrega Exposición: Traducción de Clases a Esquema Relacional Informe: Diagrama de Clases Plan de Implementación

19 Recursos Bernd Bruegge, and Allen H. Dutoit. Object- Oriented Software Engineering: Using UML, Patterns and Java. Prentice Hall. 3rd Edition, 2009 Craig Larman: Applying UML and Patterns: An Introduction to Object-Oriented Oriented Analysis and Design and Iterative Development