Visser, W. (1990), "More or less following a plan during design: Opportunistic deviations in specifications", International Journal of Man-Machine Studies, vol. 33:pp. 247--278.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....the problem situation and the stakeholders needs within that situation was ill structured, adaptive and opportunistic. Similar observations have been recorded in other domains. Adaptive responses to a context or situation have been called serendipity and then opportunism in programming [10] [24], improvisation in change management [19] and reflectionin action in architectural design [21] these describe how an unexpected event or response triggers deviation from a plan in order to adapt to the event. These examples involve creative, ill structured processes in poorly defined areas, ....

Visser, W. (1990). `More or Less Following a Plan During Design: Opportunistic Deviations in Specification', International Journal of Man-Machine Studies, 33, 247-278.

....the development of partial and interim solutions which may ultimately play no role in the final design. Design intrinsically involves the discovery of new goals. 108, pg. 27] Design problem solving is an activity that occurs in a broad spectrum of activities, including engineering design [514, 661, 662], paper writing [575] software design [103, 283, 663] programming [267] or software construction [488] redocumentation [17] and reverse engineering [139, 331] A number of reasons have been suggested for its prevalence: the limited planning capacity of human designers [267,662] the fact that ....

....their way into computing science theorizing (see e.g. Robbins et al. 544] Guindon et al. 285] Sch on et al. 566] A more direct mixing occurs when authors who publish in design literature (Visser, Hoc, Guindon, Davies, etc. publish also in journals common to both communities (e.g. IJMMS [661]) or when they publish also in software psychology related conferences and books (e.g. the Empirical Studies of Programmers Workshops [745] In addition, design research may utilize the same science base as computing. For example, design may begin to use DC theories (e.g. Gedenryd [235] Perry ....

[Article contains additional citation context not shown here]

Visser, W. More or less following a plan during design: Opportunistic deviations in specification. International Journal of Man-Machine Studies, 33(3), 1990, pp. 247--278.

....human beings. Subsequent problem solving actions are chosen by incorporating new information from the developer s memory triggered by cues present in the workspace [39] That explains why software developers with differing knowledge often choose very different approaches to develop the same task [42]. For the same task, a software developer who recalls a certain component that can be reused in the task may take a bottom up approach to design the program that is centered on the component, whereas another developer who does not know or recall that component may take a top down approach to ....

Visser, W. More or Less Following a Plan during Design: Opportunistic Deviations in Specification. International Journal of Man-Machine Studies, 1990. 33(3): 247-278.

....of these implications are presented without any formal evaluation. A further work to be performed is the implementation of these requirements in a tool and the execution of usage tests. 4.1. Opportunistic Design Designers in practice have been observed to perform tasks in an opportunistic order[12, 32] instead of following a hierarchical plan. This theory explains that, although designers plan and describe their work in an ordered, hierarchical fashion, in actuality, they choose successive tasks based on the criteria of cognitive cost, i.e. they choose steps that are mentally least expensive ....

W. Visser. More or less following a plan during design: opportunistic deviations in specifications. Int. J. of ManMachine Studies, 33:247--278, 1990.

....declarqOz e as in thetr3j33jqOEFSF patter3j nor se uential as in the designpr duct knowledge.Her each step may be trjE6WqO based on acerWWS symptom. Some rmeq t empirSqO studies show that this knowledge may be applied in an oppor3LSEjqO way that deviatesfri the top down stepwiserseq3Fj t of design [23]. The need for a scheme that can integr60 the pur top down apprqj h with the data dra enstr3W6S hasalrSFz been mentioned [7, 4] In the contrq knowledge, we have distinguished between twostrFFqOFj for applyingtryingqS0E3jq patterqj i.e. intra process detailing and inter process detailing (see ....

W. Visser, "More or Less Following A Plan During Design: Opportunisti Deviations in Spe ifi ation," Int. J. of Man-Machine studies, vol. 33, no. 3, pp. 247-278, 1990. 336

.... Features The cognitive theory of opportunistic design explains that although designers plan and describe their work in an ordered, hierarchical fashion, in actuality, they choose successive tasks based on the criteria of cognitive cost (Hayes Roth, Hayes Roth, 1979; Guindon, Krasner, Curtis 1987; Visser, 1990). Simply stated, designers do not follow even their own plans in order, but choose steps that are cognitively the least cost among alternatives. The cognitive cost of a task depends on the background knowledge of designers, accessibility of pertinent information, and complexity of the task. Thus, ....

Visser, W. More or Less Following a Plan During Design: Opportunistic Deviations in Specification, International Journal of Man-Machine Studies, Vol. 33, No. 1990, pp. 247-278.

....of a The Reuse of Uses in Smalltalk Programming . 249 ACM Transactions on Computer Human Interaction, Vol. 3, No. 3, September 1996. library information system, and observed that relatively small parts of the design were developed locally until contentions forced reworking. Guindon [1990] and Visser [1990] have demonstrated pervasive opportunistic control in software design. In the domain of reuse, Lange and Moher [1989] observed that an experienced programmer extending a library of software components frequently used existing components with related functionality as templates or models for the new ....

VISSER, W. 1990. More or less following a plan during design: Opportunistic deviations in specification. Int. J. Man Mach. Stud. 33, 3, 247--278.

....Opportunism The software development method should not be too prescriptive. A developer should be able to do what seems best at any stage of development within well defined bounds, and the method should support this. The lack of opportunistic flexibility often constrains software development, see [119, 76, 62, 79]. Uncontrolled opportunism is not desirable, but there is no reason why software developers cannot be encouraged, by the method being employed, to both craft and engineer software. ffl Customer Awareness The analysis and requirements capture phases of software development should be customer ....

W. Visser. More or less following a plan during design: opportunistic deviations in specification. International Journal of Man-Machine Studies, 33(3):247--278, 1990.

....process [19] Classic waterfall development models assume that work progresses in a systematic fashion. In reality, software design is a creative process and designers often jump from idea to idea. Task switching by designers is not random, it can be explained by theories of opportunistic design [23]. For example, designers tend to switch tasks when they don t have the knowledge needed to continue on their current task or when knowledge for another task suddenly comes to mind. Many CASE tools provide multiple views on the design; in fact, UML itself defines seven diagram types. We have tried ....

Visser, W. More or Less Following a Plan During Design: Opportunistic Deviations in Specification. Int. J. ManMachine Studies. 1990. pp. 247-278.

....of the program in any order and then paste them together into a correct program without having to be constrained by the ordering of operations. This would make programming in Pursuit more amenable to the #top down with deviation programming process exhibited in other end user programming domains #Visser, 1990; Davies, 1991#. It is interesting to note that the demonstrational speci#cation technique can both decrease and increase the look ahead necessary to write a program. Demonstrating a program on existing data objects, without considering all possible problems the program may encounter, decreases ....

W. Visser #1990#. More or Less Following a Plan During Design: Opportunistic Deviations in Speci#cation. Int. J. Man-Machine Studies, 33#3#:247#278.

....of the program in any order and then paste them together into a correct program without having to be constrained by the ordering of operations. This would make programming in Pursuit more amenable to the top down with deviation programming process exhibited in other end user programming domains (Visser, 1990; Davies, 1991) It is interesting to note that the demonstrational specification technique can both decrease and increase the look ahead necessary to write a program. Demonstrating a program on existing data objects, without considering all possible problems the program may encounter, decreases ....

W. Visser (1990). More or Less Following a Plan During Design: Opportunistic Deviations in Specification. Int. J. Man-Machine Studies, 33(3):247--278.

....of that structure to a real situation getting it into some concrete familiar objects . checking that the abstract structure fits that, and changing it if it doesn t. To summarize, the design problem solving in Sessions 2 and 3 was characterized by the following (c.f. Booch, 1991; Visser, 1990): opportunistically driven generate evaluate cycles to refine the form of the message passing hierarchy; use of complex, concrete examples as test cases for the abstract structure; 10 . management of numerous constraints within the message passing hierarchy; application of much implicit ....

Visser, W. (1990). More or Less Following a Plan During Design: Opportunistic Deviations in Specification. International Journal of Man-Machine Studies, 33, 3, 247-278.

....declarative as in the design rules, nor sequential as in the design product knowledge. Here each step may be triggered based on a certain symptom. Some recent empirical studies show that this knowledge may be applied in an opportunistic way that deviates from the stepwise refinement of design [21]. The need for a scheme that can integrate the pure top down approach with the data driven strategy has already been mentioned [4] Opposite to the design rules, tacit knowledge does not depend on a particular design and can be implemented independently. In the CREATOR2, the CREATION expert unit ....

W. Visser, "More or Less Following A Plan During Design: Opportunistic Deviations in Specification," Int. J. of Man-Machine studies, vol. 33, no. 3, pp. 247-278, 1990.

....of the program in any order and then paste them together into a correct program without having to be constrained by the ordering of operations. This would make programming in Pursuit more amenable to the top down with deviation programming process exhibited in other end user programming domains (Visser, 1990; Davies, 1991) Constraints Imposed by PBD It is interesting to note that the demonstrational specification technique both decreases and in16 creases the look ahead necessary to write a program. Demonstrating a program on existing data objects without considering all possible problems the program ....

W. Visser (1990). More or Less Following a Plan During Design: Opportunistic Deviations in Specification. Int. J. Man-Machine Studies, 33(3):247--278.

....Programmers neither write down a program in text order from start to finish, nor work top down from the highest mental construct to the smallest. They sometimes jump from a high level to a low level or vice versa, and they frequently revise what they have written so far [4] 14] 16] 34] [86]. For the purposes of programming support, that is all we need to know. Although the causes and nature of deviations from top down development have inspired much research, the implication for a programming environment is quite straightforward; the order of working should be left to the programmer, ....

Visser, W. (1990) More or less following a plan during design: opportunistic deviations in specification. Int. J. Man-Machine Studies 33 (3) 247-278.

No context found.

Visser, W. (1990), "More or less following a plan during design: Opportunistic deviations in specifications", International Journal of Man-Machine Studies, vol. 33:pp. 247--278.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC