1 / 33

Myth and Reality of OOA: the lack of domain knowledge in the representation

Myth and Reality of OOA: the lack of domain knowledge in the representation. Matti Sadeh Roi Gelbard Dov Te’eni. informatics. Computer Science IS ACM – IEEE MIS Quarterly ISR

kimberley-curry
Download Presentation

Myth and Reality of OOA: the lack of domain knowledge in the representation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Myth and Reality of OOA:the lack of domain knowledge in the representation Matti Sadeh Roi Gelbard Dov Te’eni

  2. informatics Computer Science IS ACM – IEEE MIS Quarterly ISR Management Science ) HCI (International Journal of Human computer studies Myth and Reality of OOA

  3. 1. Facts about practice of OOA • Object-Orientation is the most widely discussed Systems Development approach. • Books, Researches, Papers, Interest groups… • What happens in practice? 2. Speculation In practice, no inclusion of relevant theories Myth and Reality of OOA

  4. The OO Promise Many see the OO approach as a panacea to software problems: “It is a major premise of this book that the object-oriented approach to systems development helps to avoid many of the problems and pitfalls described in earlier chapters" [of the structured or functional analysis] (Bennett, McRobb and Farmer, 2002) However, little empirical evidence exist to support such premise, and most of them are lab results. Myth and Reality of OOA

  5. The Current Research • The current research tests empirically the application of the OO approach, with special emphasis on analysis. Myth and Reality of OOA

  6. The promise of OOA The OO approach holds the promise to cope with the traditional waterfall life cycle pitfalls: • Real world projects don’t follow a simple sequential life-cycle. • Inadequacies in the requirements analysis will arise in the late stages of the project • A long time may elapse between the initial system requirements stage and final installation. • The traditional life-cycle tends to be unresponsive to changes in client requirements or technology. • The transition between stages is not smooth - in OO smooth. • OO designs are more suited to real world problems • The OO software will be easier to understand • Better support for software reuse Myth and Reality of OOA

  7. OOA Principles Since the late ’80 many OO methodologies where suggested, but one can treat the work of the OMG (2001) as a conclusive work. The essentials of OO are: • Seeing the system as a collection of object that interact. • Classification of the objects into classes • Generalizations of classes to super-classes • Inheritance • Encapsulation • Polymorphism • Use of visual language (diagrams) • Continuance evolving approach to system life-cycle Myth and Reality of OOA

  8. Sample characteristics Myth and Reality of OOA

  9. Research method - Interviews • Diversity between projects suggested interviews best. • Project differ by: LC models, language, deliverables and more. • To manage risks (researcher bias, social desire) of such research few steps where adopted: • Structured interviews – skeletons, questions phrased up-front • Assuring the interviewees confidentiality • Gradual questions from ‘what’ through ‘How’ to ‘Why’ – postponing judgment questions to the end • Clear translation map from interview to quantitative measures Myth and Reality of OOA

  10. The generic life-cycle Although much is discussed about the iterative LC and its benefits the practice follows a more structured LC Customer Requirements RFP, SOW, MRD, or other. Might be divided into Sys. Req and SRS Software Requirements Software Analysis Software Design May be divided HLD & LLD Myth and Reality of OOA

  11. Findings – Activities in stages Analysis and design activities are pushed down the LC Myth and Reality of OOA

  12. Findings – Requirements specification • Requirements state the functionality needed from the system (not the objects that it will handle) • Requirements are broken-down by their functionality. Myth and Reality of OOA

  13. Findings – Analysis • In small projects and in some cases of information system development - might be neglected, jumping straight to implementation (overhead?) • In most cases – functions allocated to components. • Most times – not yet dealing with objects • When classes identified, almost never use the OO power of inheritance. • Declair interfaces within the system (between components) and with external systems. • Most times – UI design (specifically) Myth and Reality of OOA

  14. Findings – Design • Hardly ever full specification of system – the gap between the specification and the S/W system relate to • the complexity of the system, • knowledge and experience of the programmer, • usage of CASE tools • customer demands • Not all the classes are designed or even identified • Complex methods tend to be more specified Might suggest cost-effectiveness of design not fully proven. Myth and Reality of OOA

  15. Findings – Design • In most cases the design model is not kept updated. • implies about the usefulness of the model for maintenance Myth and Reality of OOA

  16. Findings - Graphical Language Myth and Reality of OOA

  17. Findings - Graphical Language • The graphical language is not fully adopted • Usually, text complements diagrams • Nevertheless, diagrams deliver quickly the overall picture • Two exceptions: • one very large project – design is completely graphical. Text is not feasible in such huge system. • Another, medium-scale project – completely textual descriptions of process (diagrams are overhead) Myth and Reality of OOA

  18. Story II (a little speculative):we do not in practice, include theory Myth and Reality of OOA

  19. (Systems modeling, 2000) Myth and Reality of OOA

  20. Type of information – theory implications? Myth and Reality of OOA

  21. Myth and Reality of OOA

  22. Myth and Reality of OOA

  23. An example of theory A cognitive-affective model of organizational communication:theory informs design MIS Quarterly, 2001 Myth and Reality of OOA

  24. Myth and Reality of OOA

  25. Myth and Reality of OOA

  26. Design Principles of Communication support systems(forthcoming Communications ACM) • Principle 1: Design must simultaneously consider enhancing mutual understanding and promoting relationships between communicators • Principle 2: Design should support adaptive behavior, including the contingent use of alternative communication strategies, alternative message forms and alternative media. • Principle 3: Design should control complexity. Myth and Reality of OOA

  27. Design Principles of Communication support systems (Cont.) • Principle 4: Design should support multiple levels of communication and easy travel between levels. • Principle 5: Memory should consist of speech act components, situations, norms and values. • Principle 6: Memory should consist of associative information, accessible through multiple media, and represented in multiple forms, allowing for indeterminate and emergent views too Myth and Reality of OOA

  28. Original message IEEE Trans. Intelligent systems 2000 w Schwartz Myth and Reality of OOA

  29. Contextualized message Myth and Reality of OOA

  30. Myth and Reality of OOA

  31. Myth and Reality of OOA

  32. Myth and Reality of OOA

More Related