Desouza03b

Kevin C Desouza
Facilitating Tacit Knowledge exchange
Commun ACM V46n6(Jun 2003)pp85-88
=EXPERIENCE TEAM KNOWLEDGE
People needed encouraging to use a game room on company time.
Managers expected job-related knowledge to be shared in the room.
Lotus notes was used fro sharing knowledge later and both game room and project oriented knowledge started to be posted.

Spinellis03c

Diomidis Spinellis
reflections on Trusting Trust Revisited
Commun ACM V46n6(Jun 2003)p112
=HISTORY SECURITY XBox
See Thompson84. showed that you can not trust applications unless you trust the compiler and run time system as well.
XBox hole (how to run Linux!) shows that you have to trust games to not load unwanted software.
Total security seems a long way off.

Christopher Ferris & Joel Farrell
What are Web Service
Commun ACM V46n6(Jun 2003)p31
=SIDEBAR WEB/NET SERVICES W3C URI XML WSDL SOAP
An application identified by a URI with interface and bindings defined described and discovered via XML.
See
Web_Services_Architecture_Draft::= See http://www.w3.org/TR/WD-wsa-xxx.
Finding, publishing and working with services provided over the web.
WSDL::="Web services description Language"

Harry H Goode & Robert E Machol
System Engineering: An Introduction to the design of Large-scale systems
McGraw-Hill NY NY (1957) LC Card# 56-11714 TA168
=TEXT ANALYSIS DESIGN ENGINEERING MATHEMATICS CYBERNETICS PEOPLE MODELS EXPERIMENTS ECONOMICS PERFORMANCE PROCESS TEAM GRAPH THEORY
Proposes a multi-phase process: initiation; Organization; Preliminary design; Principal Design; Prototype construction; Test Training and Evaluation
Each phase has a complex block diagram.
non-standard flow diagrams (digital and analog) implement mathematical models of computations on 2 0r 3 pages.
Block diagrams are discussed in detail (pages305-314): functional, component, geographical, physical-layout, ...
Distinguished information flow from material flow and hypothesizes that designs based on information flow are easily adjusted to include material flow.
Ref to Luce53 and Leavitt51 on the effects of team structure (graph theory) on problem solving ability and attitudes. A wheel like structure with a central communicational hub tends to develop a leader and solve easier problems faster. A circular structure is better for some hard problems and people felt they had more fun but were not organized. (pages 390-393)
Implies that structure of a system design team must not reflect the structure of the system they are designing because system design is typically a harder problem than running the solution system (page 392)