-
7/25/2019 examQA
1/4
Discuss topic show exercise solution and discuss to more
practircal
exam question: topic 1 and topic 2what is model an show some
concreate model
explain syntax semantic
1. why system development:follow recipe follow certain
steps(when cook a turkey for example).Expereinced team: still
follow the methology feel and do what you want. Employer want to
ha!edeadline need to findout "ring more p.p in pro#ect to "e a"le
to catch up. Emplyer know what goal
and what time. $line something work together.
2. iterative method:sprial model. %epeat increament product from
scratch. &ook at requirementanytime. Do no. 'f step "uilding a
"it of final software at a time. (when get tested "uild it as final
of
product(exe "ase line) you still ha!e product e!en though 1
interation not appro!ed still ha!e somefunctionality( to ad#ust it
according to customer get early feed"ack and you can ad#ust. an
addapt
to changea"le to change to course of pro#ect)
pro" w water fall(requirements)*(design) implement(2yrs)* what
if you arwrong so no adapt pr
3.agile: ad#ust flesi"le iterati!e hard to adpat w
waterfall(strict in time"ox)functionality a" notmaking model light
weight dont make these models on fornt(misunderstood): make
+,&: do itwhene!er you need it more adapt unclear how to
implement that(sketch on white "oard) until
group find a design will not type them in and refactingnot
making models. ,any fla!or: agile +-
strict. (scrum is scrum "ut agile): model : model when u need
todesign : foward as design at end of documentation(re!erse)5. dif
btw diagram and model: si/e: diagram larger(dynamics class
diagram): presentation ofinfo #ust another way of
presenting(description of to "e)model has purpose consist of 1 or
more
diagram(ER model model of conceptual data) diagram(class
diagram) to mae model usecasemodel consist diagram usecase model
consist 5 dif artifact. !odel larger than diagram bcsmodel consist
more diagram( loo at dynamics and static) business modelwhy use
this digram: when show some diagram.
".#raceability: trace the code from models no need to read
complicated code. 0racea"ility "tw allthe models.
. 0ypes of models: tatics: class diagram domain modelDynamics:
+se case diagram use case text description( sale) D D
33:
$or %&0he requirements are unknown or hard to elicit from
the user
4 0he requirements change frequentlyEm"racing hange
4 Each iteration in!ol!es choosing a small su"set of the
requirements and quickly design implement
-
7/25/2019 examQA
2/4
and testing them
4 0his leads to rapid feed"ack and an opportunity to modify or
adapt understanding of therequirements or design
25
A requirement describes
a condition or capability
to which a system mustconform; either derived
directly from user needs,
or stated in a contract,
standard, specification,
or other formally
imposed document.
For UML:
3. Use case: Use cases capture the functional requirements of a
system.
Use cases describe the interactions between actors and the
system from the users
perspective
Use cases must have business value
Use cases divide the system into meaningful parts meaningful
parts not just a list offunctions
Use cases describe how goals are achieved through use of the
system .e. the wor!
process when the system is build
Use case scenario:
-
7/25/2019 examQA
3/4
"oncepts related to use cases
Actor# something with behaviour, and having a goal using the
system, such as a person,
computer system, or organi$ation, e.g. a cashier.
%oal# &hat the actor wants to achieve by interacting with
the system.
'cenario# specific sequence of actions and interactions between
actors and the systemunder discussion, e.g. the scenario of
successfully purchasing items with cash. An instance
Use case# a collection of related success and failure scenarios
that describe actors using a
system to support a goal.
4. Conceptual models:
(omain )odel *conceptual model + class diagram
-
7/25/2019 examQA
4/4
III: Design.
GRAS atterns
! " goals #$%at $e $ant& ! 'ig%
Co%esion ! Lo$ Coupling
! 3 means #%o$ $e get it& !
In(ormation )*pert ! Controller !
Creator
