Elaboration and domain model

1,963 views 10 slides Jan 06, 2022
Slide 1
Slide 1 of 10
Slide 1
1
Slide 2
2
Slide 3
3
Slide 4
4
Slide 5
5
Slide 6
6
Slide 7
7
Slide 8
8
Slide 9
9
Slide 10
10

About This Presentation

Elaboration phase in Unified process


Slide Content

Object Oriented Analysis and Design
V Semester CSE
© Vignesh Saravanan K, AP/CSE
Lecture-11
Elaboration, Domain Model
UNIT II –STATIC UML DIAGRAMS

© Vignesh Saravanan K,AP/CSEObject Oriented Analysis and Design
RAMCO INSTITUTE OF TECHNOLOGY
2
The Essentials of Class Diagram
Aclassdiagramdescribesthetypesofobjectsinthesystemandthe
variouskindsofstaticrelationshipthatexistamongthem.
Thereare2kindsofstaticrelationships.
Associations
Subtypes
Theclassdiagramsshowtheattributesandoperationsofaclassandthe
constraintsthatapplytothewayobjectsareconnected.
Perspectives
Therearethreedifferentperspectives;weuseindrawingclass
diagrams.Theyare
Conceptual
Specification
Implementation

© Vignesh Saravanan K,AP/CSEObject Oriented Analysis and Design
RAMCO INSTITUTE OF TECHNOLOGY
3
ELABORATION
Elaborationisanactivityinwhichtherequirementsisexpanded
andrefined.Elaborationconsistsofseveralmodelingand
refinementtasks.
DuringElaborationphase,eachuserscenarioisparsedandvarious
classesareidentified.Thenwecandefinethefollowing:
Attributesandservices(functions)
Relationshipsontheclasses.
ThenUMLdiagram(classdiagrams)canbeeasilydeveloped.

© Vignesh Saravanan K,AP/CSEObject Oriented Analysis and Design
RAMCO INSTITUTE OF TECHNOLOGY
4
ELABORATION (cont.)
Elaborationhasthefollowingseriesofiterations.
1.Thecore(risky)softwarearchitectureisprogrammedandbuilt.
2.Almostallrequirementsareidentifiedandrefined.
3.Highrisksareresolvedorremovedandroughestimationdone.
Elaborationisconductedwithintwoormoreiterations.
Duringtheseiterationstheteam
Doesseriousinvestigations
Implementsprogramsandtestsforcorearchitecture
Clarifiesrequirementstackleshighriskissues.

© Vignesh Saravanan K,AP/CSEObject Oriented Analysis and Design
RAMCO INSTITUTE OF TECHNOLOGY
5
ELABORATION (cont.)
Eachiterationgoesfor2or3weeks.Eachiterationistime-boxed..
i.e.itsenddateisfixed.Itlastsfortwotosixweeks
Duringelaborationthemodelsarefullydevelopedinpreparation
forimplementation.
Duringelaboration,thecodeanddesignareinproduction.Itis
called“Executablearchitecture”or“Architecturalbaseline”.
Elaborationisneitheradesignstepnoraphaseinwhichfully
developedmodelforimplementationisdeveloped.

© Vignesh Saravanan K,AP/CSEObject Oriented Analysis and Design
RAMCO INSTITUTE OF TECHNOLOGY
6
Key Ideas of Elaboration
Elaborationis
Buildingthecorearchitecture
Resolvingthehighriskelements
DefinemorerequirementsandEstimateoverallscheduleand
resources
KeyIdeasofElaboration
Elaborationisnotmorethanfewmonths
Coreandriskypartsdoneinstepbystep
Hasshorttimeboxediterations
Hasrealistictests.
Adaptaccordingtothefeedbackofusers
Mostoftheusecasesandotherrequirementsindetail

© Vignesh Saravanan K,AP/CSEObject Oriented Analysis and Design
RAMCO INSTITUTE OF TECHNOLOGY
7
Inception vs Elaboration

© Vignesh Saravanan K,AP/CSEObject Oriented Analysis and Design
RAMCO INSTITUTE OF TECHNOLOGY
8
DOMAIN MODELS
A domain model is a visual representation of conceptual classes or
real situation objects in a domain.
In object oriented analysis, domain model is the most important.
It illustrates the concepts in a domain.
It acts as a source of inspiration for designing some software
objects.
Example
A partial domain model for a visual dictionary is drawn with
UML class diagram. The conceptual classes of
–Payment and
–Sale are shown
The payment is related to sale. Sale has date and time
information.

© Vignesh Saravanan K,AP/CSEObject Oriented Analysis and Design
RAMCO INSTITUTE OF TECHNOLOGY
9
DOMAIN MODELS (cont.)
Domain models are also called as conceptual models. Domain models are
illustrated with a set of class diagrams
Domain objects or conceptual classes
Association between conceptual classes
Attributes of conceptual classes
A domain model shows real-situation conceptual classes and not software
classes. [such as Java or C++ classes]
So a domain model should probably avoid
Software artifacts like window or database
Methods and responsibilities.

Object Oriented Analysis and Design
V Semester CSE
© Vignesh Saravanan K, AP/CSE
End of Lecture
•The Essentials of Class Diagram
•ELABORATION
•Key Ideas of Elaboration
•Inception vs Elaboration
•Domain Model