i have some confusion in these areas

[ayesha iqbal]

1)which statement about iterative and incremental
is correct.
a)it is the technique of divide and conquer
b)both are same.
2)to understand the domain which artifact we should see.
a)usecases
b)intercation daiagram
c)conceptual model
if use cases than what sort of
3)what terms are used in uml interchangeable
a)interface,type
b)abstract class,sub class
c)subtype,subclass
d)specialization,subtyping

is there any stereotype <<controller>>
in uml?

Q4) you have large team how will you distribute the project among the team to manage the project
1)usecase , packages and you can also do with your own wish
2)usecases ,packages

[ayesha iqbal]

i mean is there any stereotype in uml like this
<<controller>>
another confusion is this
what is the dependency of packages in uml
1)transitive
2)intransitive

[ayesha iqbal]

i mean <<controller>> stereotype
i also have one confusion that what is the dependency of packages
1)transitive
2)intransitve
give me the aanswers with refrence of reiable resource

[ayesha iqbal]

i mean stereotype of controller
actually controller is not being written
b/w <<>>stereotype notation

[ayesha iqbal]

i mean stereotype of controller
actually controller is not being written
b/w <<>>stereotype notation

[Atif Shah]

Originally posted by ayesha iqbal:
1)which statement about iterative and incremental
is correct.
a)it is the technique of divide and conquer
b)both are same.
in my view Iterative means to keep following a same flow. where as incremental is like stages in which you may no be following a same routine rahter u increasing a stage/step.
may be i m wrong but that what i think.

2)to understand the domain which artifact we should see.
a)usecases
b)intercation daiagram
c)conceptual model
if use cases than what sort of

if you are talking about busniess domain for that you may have to analyiz the buniess where usecases help you to understand application domain from user point of you. it is to represents group/collection of Scenario in we try to show user intraction with application.

3)what terms are used in uml interchangeable
a)interface,type
b)abstract class,sub class
c)subtype,subclass
d)specialization,subtyping

interface,type,abstract,class,generalization,specilization..
is there any stereotype <<controller>>
in uml?
well as far as i can recall define stereotypes are
" abstract,Actor,boundry,Control,entity,interface,busniess actor,busniess worker,busniess entity"
or you can have your or stereotypes BY using << abcd >>
Q4) you have large team how will you distribute the project among the team to manage the project
1)usecase , packages and you can also do with your own wish
2)usecases ,packages

well inorder to distribute the work first you have to see which level you talking about if you are talking about development of overall system then packages and component wise is better as far i can say. becuase uscases is high level and after have concret model you may have many common classes or interface which might be fullfilling the purpose of more then One or 2 or more usecases.
i try to divid or distribut work on gross level for development. but in case of domain analsyis and design i try to divid the overall system in to subsystem and then distribute subsustem but ofcourse it also requires that team is always intracting to each other and keep undating and sharing the distributed model.
we try to creat or define a frame work by considering the some tough examples and then for each specific subsystem which suppose to fit into the Frame work we distribute among the ppl.
this allows you to define the guidlines and boundries of your system..
may be my view point and explaination is different ...
but i hope this helps you in understanding some of it.

regards
Atif

[ayesha iqbal]

thanks Atif
i also have one confusion that
1-)in model view saperation view knows about model(domain) but model(domain) doesn't know about view
and to update the view model must talk to some one like observer who update the view...am i right?

2-)what is the difference b/w coordinator and controller?

3-)what is meant by callback term used iin larman on page no 286?

[Atif Shah]

well.
Model View Controller (MVC) based arch: is always preferable becuase its divides the three different level of complexity in three different layer. that is MVC where.
Model represents the logical entities in your system or your busniess Objects . where View is contains the presentation layer logic which handles the Presentation complexity.
Yes your are in order to populate the View, View needs to read data from Model well here Controllers job starts. When even a request or action is initiated from/by view it is first handled its controller which knows from which Model it has to fetch the data.
well if you see MVC having three object View and Model and Controller then you can see that in order to keep your Model and View sperate you need to work in your controller that makes controller job bit complex in this case it would not only hanlde the request and dispatching it also populating the view accorddingly.
In view it is always good to min the complexty so what is an other practice u can find that ppl tries to divid Controller job and it looks like somthing like this.
View --------------------- Controller -- Model
---------------------- | ---
|
View -ViewFormatter/Coordinator - |

based on MVC in order to minimize the complexcity many ppl have adopted different approch in above representation you can see that Controller identifies the Model and then creates the appropriate ViewFormatter which knows how to format view by given Model (passed by Controller) .
for me this Arch works in order to generate View form model. I have implemented in one of the Web based Application in which application was Quit complex becuase of the nature of Requirment and limitation of Web interface.
My View was divided into other layer as well JSP/HTMLs and etc.
I hope this could give you to understand something. i dont know if i am a good explainer or not but i tries to.
This not the end of the world there are some other approches as well implementing MVC. MVC givies you very Abstract idea but quit level to understand the each layer it is up to individual how he or she extends it.
Call back.
well callback can be event/functions that may rasied after or before certain actions.
function which you wished to be raised on
certain events. you can say them notifications you want to recive.
hope you get all this.
Take care.
At

[Atif Shah]

sorry for agitated english/sentences but i hope you understand.
kind of in very hurry