[CSUSB]>> [CNS]>> [CSE]>> [R J Botting]>> biba.php
Bibliographic Item (1.0)
- Roy Gelbard & Dov Te'eni & Matti Sadeh
- Object-oriented Analysis -- is it just a theory
- IEEE Software Magazine V27n1(Jan/Feb 2010)p64-71
- =POLL 54 PROJECTS UML DFDs flowcharts OOA ANALYSIS DESIGN CODE
- Most classes are identified during design & code.
- diagram types: (most used) class(ERD), package, activity, flow, sequence, state, collaboration, DFD, use case(least used). Component& deployment not used.
- Text always used, mostly with diagram. Diagrams are not enough.
- 80% used one iteration.
- Clients do not get oo diagrams.
- CASE tools don't speed up understanding and explaining.
- Missing: user interface, business process, ... OO models.
- Suggest that less is more.
- Notes use of OOA depends on policy, costs, and benefits.
- Minimize Costs: focus on organisational relationships, interactions, data items, and user experiences.
- Maximize Benefits: use psychology and sociology to analyse needs.
Search for bibliographic items containing a matching string.
Search for a specific bibliographic item by name.
To see the complete bibliography (1Mb+) select:[Bibliography]