Object-Oriented Analysis and Design in Software Project Teams

Herbsleb, James D.; Klein, Helen Altman; Olson, Gary M.; Brunner, Hans; Olson, Judith Reitman; Harding, Joe

doi:10.1207/s15327051hci1002&3_4

Cited by 47 publications

(39 citation statements)

References 23 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…A total of six software engineering students, inexperienced in any analysis method, received the same training in all three methods during a university course. This study seemingly contradicts the finding of (Boehm-Davis and Ross, 1992;Herbsleb et al, 1995) and OO is easier to apply. While the methods used by developers in the Vessey and Conger study were almost identical to those in the Boehm-Davis and Ross (1992) study, the former study used students instead of experienced developers and used a much smaller sample size (n = 6 Vs. n = 18).…”

Section: Empirical Studies In Ooadcontrasting

confidence: 93%

Study of Object Oriented Analysis and Design Approach

Pandey¹

2011

Journal of Computer Science

View full text Add to dashboard Cite

Problem statement: Object and component technologies, rapidly maturing branches of information technology, have been becoming pervasive elements of systems development, especially the recently popular Internet applications and thus leading to increased complexity and at the same time broader range of applications. Approach: This needs to be understood in order to maximize its benefits and applications with consistent results. However, mainstream Object Oriented Systems Development (OOSD), consisting of Object Oriented Analysis and Design (OOAD) and ObjectOriented Programming (OOP), has a history of difficulties and is still struggling to gain prevalent acceptance. Results: There have been number of studies and experiments conducted by experts and researchers in the past which provides a solid base to take up this study and look into various intricacies present. There have been several studies and focused efforts in this direction which laid down the basis for a segment of people to form the opinion as "technology adoption is mostly the result of marketing forces, not scientific evidence" whereas there have been another segment that believes that object technology is "still long on hype and short on results ...". The gurus of OOSD continue to tout its vast superiority over conventional systems development, even to the extent of developing a unified software development process. Conclusion: The advocates of OOSD claim many advantages including easier modeling, increased code reuse, higher system quality and easier maintenance. It is well understood that analysis and design are extremely critical aspects of successful systems development especially in the case of OOSD. As the development of any successful information system must begin with a well-conceived and implemented analysis and design, this study will focus on the most recent empirical evidence on the pros and cons of OOAD.

show abstract

Section: Empirical Studies In Ooadcontrasting

confidence: 93%

Study of Object Oriented Analysis and Design Approach

Pandey¹

2011

Journal of Computer Science

View full text Add to dashboard Cite

show abstract

“…A great amount of time is spent on these activities (D'Astous et al, 2004;Herbsleb et al, 1995;Karsenty, 1991;Olson, Olson, Carter, & Storrosten, 1992;Stempfle & Badke-Schaub, 2002).…”

Section: Construction Of Interdesigner Compatible Representationsmentioning

confidence: 99%

Designing as Construction of Representations: A Dynamic Viewpoint in Cognitive Design Research

Visser¹

2006

Human–Computer Interaction

View full text Add to dashboard Cite

This article presents a cognitively oriented viewpoint on design. It focuses on cognitive, dynamic aspects of real design, i.e., the actual cognitive activity implemented by designers during their work on professional design projects. Rather than conceiving designing as problem solving-Simon's symbolic information processing (SIP) ap-proach-or as a reflective practice or some other form of situated activity-the situativity (SIT) approach-we consider that, from a cognitive viewpoint, designing is most appropriately characterised as a construction of representations. After a critical discussion of the SIP and SIT approaches to design, we present our viewpoint. This presentation concerns the evolving nature of representations regarding levels of abstraction and degrees of precision, the function of external representations, and specific qualities of representation in collective design. Designing is described at three levels: the organisation of the activity, its strategies, and its design-representation construction activities (different ways to generate, transform, and evaluate representations). Even if we adopt a "generic design" stance, we claim that design can take different forms depending on the nature of the artefact, and we propose some candidates for dimensions that allow a distinction to be made between these forms of design. We discuss the potential specificity of HCI design, and the lack of cognitive design research occupied with the quality of design. We close our discussion of representational structures and activities by an outline of some directions regarding their functional linkages.

show abstract

“…These problems concern communication, coordination, and the capture and use of application (or problem) domain knowledge (Krasner, Curtis and Iscoe, 1987;Curtis and Walz, 1990;Herbsleb & Kuwana, 1993). Computers, 1997, 9, p 47-72 Harding, 1995). OO design should also help to propagate application domain knowledge through the design team, because the shared representation has its basis in the concepts and vocabulary of the application domain.…”

Section: Claims About Ood At the Software Design Team Levelmentioning

confidence: 99%

“…Another problem dimension relevant to OO design is discussed by Herbsleb et al (Herbsleb, Klein, Olson, Brunner, Olson & Harding;. It characterises whether or not well understood abstractions have already been constructed in the task domain.…”

Section: Published In Interacting Withmentioning

confidence: 99%

Assessing the cognitive consequences of the object-oriented approach: A survey of empirical research on object-oriented design by individuals and teams

Détienne¹

1997

Interacting with Computers

View full text Add to dashboard Cite

This paper presents a state-of-art review of empirical research on object-oriented (OO) design. Many claims about the cognitive benefits of the OO paradigm have been made by its advocates. These claims concern the ease of designing and reusing software at the individual level as well as the benefits of this paradigm at the team level. Since these claims are cognitive in nature, its seems important to assess them empirically. After a brief presentation of the main concepts of the OO paradigm, the claims about the superiority of OO design are outlined. Computers, 1997, 9, p 47-72 http://www.elsevier.com/wps/find/journaldescription.cws_home/525445/description#description 2 The core of this paper consists of a review of empirical studies of OOD. We first discuss results concerning OOD by individuals. On the basis of empirical work, we (1) analyse the design activity of novice OO designers, (2) compare OO design with procedural design and, (3) discuss a typology of problems relevant for the OO approach. Then we assess the claims about naturalness and ease of OO design. Published in Interacting withThe next part discusses results on OO software reuse. On the basis of empirical work, we (1) compare reuse in the OO versus procedural paradigm, (2) discuss the potential for OO software reuse and (3) analyse reuse activity in the OO paradigm. Then we assess claims on reusability.The final part reviews empirical work on OO design by teams. We present results on communication, coordination, knowledge dissemination and interactions with clients. Then we assess claims about OOD at the software design team level.In a general conclusion, we discuss the limitations of these studies and give some directions for future research. Computers, 1997, 9, p 47-72 Interactions with clients 6.4 Published in Interacting withAssessing claims about OOD in design teams Limitations and directions for future work ReferencesPublished in Interacting with Computers, 1997, 9, p 47-72 IntroductionThis paper presents a state-of-art review of empirical research on object-oriented (OO) design. OO technology has been accepted by both academia and industry in a very short time. Ten years ago, the few OO languages available were seen as interesting ideas. Since then, new languages have been designed and existing languages have been extended to become object-oriented. Many claims about the cognitive benefits of the OO paradigm have been made by its advocates. These claims concern the ease of designing and reusing software at the individual level as well as the benefits of this paradigm at the team level. Given the rapid acceptance of this new technology, it is imperative to understand the process and to evaluate the benefits of OO design. Since these claims are cognitive in nature, its seems important to assess them empirically (Détienne & Rist, 1995).Since 1990, much empirical work has been conducted on OO design both at the individual level and at the software design team level. These studies are field studies and laboratory studies. Th...

show abstract

Object-Oriented Analysis and Design in Software Project Teams

Cited by 47 publications

References 23 publications

Study of Object Oriented Analysis and Design Approach

Study of Object Oriented Analysis and Design Approach

Designing as Construction of Representations: A Dynamic Viewpoint in Cognitive Design Research

Assessing the cognitive consequences of the object-oriented approach: A survey of empirical research on object-oriented design by individuals and teams

Contact Info

Product

Resources

About