Win a copy of Testing JavaScript Applications this week in the HTML Pages with CSS and JavaScript forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Bear Bibeault
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
Sheriffs:
  • Tim Cooke
  • Liutauras Vilda
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • fred rosenberger
  • salvin francis
Bartenders:
  • Piet Souris
  • Frits Walraven
  • Carey Brown

OOA phase

 
Ranch Hand
Posts: 1491
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
When we do OOA phase (whether before deciding the Technology) ?
 
author
Posts: 11962
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Depends on the process you're using. Which leads us to the question of which process you are using?
 
author
Posts: 14112
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

Originally posted by kri shan:
When we do OOA phase (whether before deciding the Technology) ?



The best would be to not have an OOA *phase* at all. Analysis should be an ongoing activity throughout the project.

Would you probably *should* have is an Exploration Phase. Here you (as a team) gather the most important requirements, break them down in working units at the size of some days to a couple of weeks and roughly estimate them to get a feeling on the size of the project. To be able to do that, you probably already have to decide on the basic technology and architecture to use, possibly even to verify it with some small Spike Solutions (kinda mini-prototypes).

That phase could last from some days to weeks, depending on the project.
 
(instanceof Sidekick)
Posts: 8791
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
And what exactly is OO about A? Mostly kidding with that one, but good anlaysis ought to work with any implementation, even COBOL. Design is a different story altogether.
 
Ilja Preuss
author
Posts: 14112
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

Originally posted by Stan James:
And what exactly is OO about A?



Mostly it seems to be about using Class diagrams for depicting the problem domain. I'll probably never understand why people think this is a good idea...
 
Ranch Hand
Posts: 1759
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I think Business Analysts have to understand some level of the design
otherwise how are they going to ask for changes or decide where best to put the modifications to requirements ?
 
Ilja Preuss
author
Posts: 14112
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

Originally posted by Helen Thomas:
I think Business Analysts have to understand some level of the design otherwise how are they going to ask for changes



"We want this to work this way instead of that way. How much will this cost?"


decide where best to put the modifications to requirements?



I am not sure I understand what you mean by this. Could you please rephrase? Thanks!
 
Helen Thomas
Ranch Hand
Posts: 1759
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

Originally posted by Ilja Preuss:


I am not sure I understand what you mean by this. Could you please rephrase? Thanks!



I meant modifications to functional requirements. They know which types of users use which functions and therefore it's not unusual to find references to specific system elements : screens , reports, queues in functional change documents.

I haven't seen references to classes yet, though only to persisting data tables.
[ July 26, 2004: Message edited by: Helen Thomas ]
 
author
Posts: 608
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I think that I make a pretty good argument that an analysis phase is the wrong way to be looking at modeling in the essay posted at http://www.agilemodeling.com/essays/phasesExamined.htm . Modeling on object projects usually happens in an evolutionary manner, not a phased/serial one. Furthermore, most modeling techniques can be used for requirements, analysis, or design (use cases are a perfect example). Therefore when do we do analysis is likely the wrong question to be asking. Anyway, check out the essay.

- Scott
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
    Bookmark Topic Watch Topic
  • New Topic