[CSUSB]>> [CNS]>> [CSE]>> [R J Botting]>> biba.php

Bibliographic Item (1.0)

GelbardTeeniSadeh09

  1. Roy Gelbard & Dov Te'eni & Matti Sadeh
  2. Object-oriented Analysis -- is it just a theory
  3. IEEE Software Magazine V27n1(Jan/Feb 2010)p64-71
  4. =POLL 54 PROJECTS UML DFDs flowcharts OOA ANALYSIS DESIGN CODE
  5. Most classes are identified during design & code.
  6. diagram types: (most used) class(ERD), package, activity, flow, sequence, state, collaboration, DFD, use case(least used). Component& deployment not used.
  7. Text always used, mostly with diagram. Diagrams are not enough.
  8. 80% used one iteration.
  9. Clients do not get oo diagrams.
  10. CASE tools don't speed up understanding and explaining.
  11. Missing: user interface, business process, ... OO models.
  12. Suggest that less is more.
  13. Notes use of OOA depends on policy, costs, and benefits.
  14. Minimize Costs: focus on organisational relationships, interactions, data items, and user experiences.
  15. Maximize Benefits: use psychology and sociology to analyse needs.

Search for bibliographic items containing a matching string.


(Search uses POSIX regular expressions and ignores case)

Search for a specific bibliographic item by name.



To see the complete bibliography (1Mb+) select:[Bibliography]