Ackoff

However (1) people often lag behind at lower levels. (21st islamic terroists move from control&power to salvation and reject materialism) (2) males tend to move to the tribe or team levels - even to the point of suicide/self-sacrifice.

Max Abrahms

Terroism is essentially not goal oriented!

8 management types

Felder's Learning styles: Sensing/Intuiting, Visual/Verbal, Active/Reflective, Sequential/Global dimensions.

also see 5 stages of ...

5 Questions for doctors diagnosing

1. How did you come to this conclusion?
2. Is there anything that doesn't fit?
3. What else could it be?
4. Could two or more things be going on?
5. What are the possible bad outcomes from this treatment/procedure? How often?

   Source: How doctors think By Jerome E. Groopman - Houghton Mifflin (2007) - Hardback= ISBN 0618610030 [ catalog?q=%22How+doctors+think%22 ]

5 Questions when Disagreeing.

1. "If I understand you correctly, you are saying that <translation>"
2. "How did you arrive at that view?"
3. "Have you considered <alternative>?"
4. "When you say this, I worry that it means <negative impact>."
5. "I have a hard time seeing that because of <objection>.

   Source: Quoted by Bob Rosner in SB Sun Business Section D 04/9/13 apparently from "The Fifth Discipline" by Peter Singe (Curreency 1994).

5+ stages of

6 principles in making people like you - Carnegie

1. Become genuinely interested in other people.
2. SMILE
3. Remember that a person's name is to that person the sweetest and most important sound in any language.
4. Be a good listener. Encourage others to talk about themselves.
5. Talk in terms of the other person's interests.
6. Make the other person feel important -- and do it sincerely.

7 Deadly Sins

7 keys to seven rooms of thought

1. Accept the statement of authority without basis, without question.
2. Disagree with the statement without basis, out of general contrariness.
3. Perhaps the statement is true, but what if it isn't? How then to account for the phenomenon?
4. How much of the statement rationalizes to suit man's purpose that he and his shall be ascendent at the center of things?
5. What if the minor becomes major, the recessive dominant, the obscure prevalent?
6. What if the statement were reversible, that which is considered effect is really cause?
7. What if the natural law perceived in one field also operates unperceived in all other phases of science. What if there be only one natural law manifesting itself, as yet, to us in many facets because we cannot apperceive the whole, of which we have gained only the most elementary glimpses, with which we can cope only at the crudest level?

   And are those still other doors, yet undefined, on down the corridor?

   Mark Clifton, Eight Keys to Eden, 1960

802.11b and Wi-Fi not wifi

Wi-Fi is another name for 802.11b coined by the Wireless Ethernet Compatability Alliance, or WECA.

open standard for wireless communication unlicensed spectrum at 2.4 gigahertz, omnidirectional range 200 feet.

The 2.4-gigahertz part of the radio spectrum is shared by microwave ovens, cordless phones and baby monitors. An 802.11b base station, about the size of a hardcover book, can send signals 200 feet in any direction. up to 11 megabits per second.

802.11s mesh networking standard that could be ratified by early 2007, reported Motorola Mesh Networking Group executive Joe Hamilla. Hamilla said the IEEE task force has approved the 802.11s proposals, which are now open to comment. "With the standard will come ubiquity for the mesh networking concept, and we anticipate a major build up in demand next year," he said. "It will become mainstream in the near future." Approval for a mesh technology standard has been relatively free of difficulty, and a pair of competing proposals from the Wi-Mesh Alliance and the SEEMesh Alliance were integrated into a single specification. The meshing of Wi-Fi hot spots turns them into an interconnected network that can cover an area with wireless broadband connectivity, and mesh-enabled access points not only deliver Wi-Fi to users, but also function as routers/repeaters for other access points. This establishes a wireless broadband cloud that can organize and repair itself, lowering the cost of backhaul, implementation, and system engineering.

802.11b and Wi-Fi not wifi Security

Setting up a router at home

1. Beware! security is an option not a default.
2. Typically router stores the ISP account name and password, allowing any computer to use the ISP under that ID.
3. The admin account often has the password "admin". Not used to access ISP but to change accounts.
4. Encryption between computers and router is turned off... Plain text. Read logins.
5. default WEP Encryption is too weak. Enable WPA!

802.16a WiMAX metro lan 75Mbps 11GHz

9 principles in leading - Carnegie

1. Begin with praise and honest appreciation.
2. Call attention to people's mistakes indirectly.
3. Talk about your own mistakes before criticizing the other person.
4. Ask questions instead of giving direct orders.
5. Let the other person save face.
6. Praise the slightest improvement and praise every improvement. Hearty and lavish.
7. Give the other person a fine reputation to live up to.
8. Use encouragement. Make the fault seem easy to correct.
9. Make the other person happy about doing the thing you suggest.

Working Systems

Adjoint of matrix transposed conjugates

operator algebras. vonNeuman. quantum theory. noncommutive ops are complementary.

dynamical System system:=Net{X:topology, G:group, phi:action of G on X. G is Int or Real.}

make algebra by, convolu§, involu§, Cauchy comple§

Ideals!

An Old English Prayer

Aristotle

->Syllogisms

Big O notation bigO big_O big-O

f(n) in O( g(n) ) ::= for some c, n0, all n, if n > n0 then ( f(n) <= c * g(n) ).

Can you find c, and n0?

Look at the contrapositive!

1. if f(n)>c*g(n) then n<n0.

   not (f(n) in O( g(n) ))= for all c, n0, some n > n0( f(n) > c * g(n) ).

   f(n) asymptotically_equivalent_to g(n) ::= ( lim[n->oo](f(n)/g(n) ) = 1).

   ?? f <<< g ::= for all c, some n0, all n, if n>n0 then ( f(n)/g(n) <= c ). Some Notes on the bigO Asymptotic Formula used in Computer Science

   Follows and extends Brassard & Brately 1988 "Algorithmics" PHI.

   Motivation: the standard way to represent the efficiency of algorithms. The order of a function ignores small values (which don't matter very much in most practical situations) and the speed up effects of changing a platform.

   Definitions

2. P:=Positive & Real.
3. F:= Nat -> P.
4. For f:F, O(f)::={ t: F. for some c:P, n0:Nat, all n:n0..( t(n) <= c * f(n) )}.
5. For f:F, Ω(f)::={ t: F. for some c:P, n0:Nat, all n:n0..( t(n) >= c * f(n) )}.
6. For f:F, Θ(f)::=O(f) & Ω(f).

7. For f,g,h:F, c:P, n,n0:Nat.

8. 1::F= map [n](1).

   Abuse of notation: we traditionally write an expression containing n to indicate the function of n in F. So for example n is short for the identity function map [n](n).

   Expressions that have functions as arguments: (f+g for example) are interpreted pointwise.

9. (f+g)(i) = f(i)+f(i).

   Expressions of sets of functions (like 20+O(f)) mean taking all possible combinations:

   
   

10. (STANDARD)|-f =[O] g iff O(f)=O(g).

    Note on Proofs

    Proofs that some f in O(g) from the definitions can be challenging because we often have to guess the values of c and n0. There is a lot to be said for memorizing the 15 or so results below and use these to work out the orders of a function.

    Results

    
    
11. (above)|- (Oreflexive): For all f, f in O(f).
    
12. (above)|- (Otransitive): if f in O(g) and g in O(h) then f in O(h).
    
13. (above)|- (2): For all a:P, f, a*f in O(f).
    
14. (above)|- (3): for all f,g, if for all n(f(n) <=g(n)) then f in O(g).
    
15. (above)|- (4): for all f, g, if f in O(g) then f+g in O(g).
    
16. (3)|- (5): for all p:Nat0, q:Nat0, ( if p<=q then n^p in O(n^q) )and (if p<q then not n^q in O(n^p)).
17. For p:Nat0, Polynomial(p)::={ map[x](sum[i:0..p](a[i]*x^i). some a:0..p->Real }.
18. Exponential::={ map[x](a^x). some a:P}.
19. Logarithmic::={ map[x](log[a](x). some a:P}.
    
20. (2, 4)|- (6): for all f:Polynomial(p), f in O(n^p).
    
21. (above)|- (7): for log: Logarithmic, log in O(n) and not n in O(log).
    
22. (above)|- (8): for exp: Exponential, n^p in O(exp) and not exp in O(n^p).
    
23. (above)|- (9): log[a](n) =[O] log[b](n).
    
24. (above)|- (10): a^n =[O] b^n.
    
25. (above)|-for some f,g, not f in O(g) and not g in O(f).
    
26. (above)|-(11) log in O(sqrt) and not sqrt in O(log).
    
27. (above)|- (12): For k:0.., sum[i:1..n](i^k) in Θ(n^(k+1)).
    
28. (above)|- (13): sum[i:1..n](1/i) in Θ(log).
    
29. (above)|- (14): log(n!) in Θ(n* log(n)).
    
30. (above)|- (15): f =[O] g iff f =[Θ] g iff f in Θ(g).

31. ?? if f in O(h1) and g in O(h2) then f+g in O(h1+h2) and f*g in O(h1*h2).

Persuasion

Cialdini: Influence: The Psychology of Persuasion by Robert Cialdin, pub Quill; ISBN: 0688128165. Motivators:

Reciprocation

Like to give back what we get.

Scarcity

Authority

Spokes person

Comittment and consistency:

yes yes...
1. first agree with logically consistent with target.
2. ?? cognitive dissonance.

   Consensus

   go with the crowd

   Liking

   Can be used to fool a person: ONCE.

Clippings+scraps

The recyclic nature of software work.

"Beliefs are more powerful than facts," Duke Paulus Atreides, Dune: House Atreides.

Disturb not the scholar in his ivory tower for your empires are mere dreams to him?? Geordy Dickson, the tactics of mistake

Coase

Complexity NicolisPrigogine89

phase transitions.

fluid convec§: as Δ T increases -> 3 phases(small random varia§s; order\ cells; chaotic). transition to order requires a random choice - break/ symmetry.

Chemical systems - clos\ & asymptotically stable vs open & unstable( bistable, hysterisis, cyclic., turbulent) Autocatalysis. conservative systems - reversible - time space symmetry - don't forget disturbances disipative systems - not reversible - tend to forget some disturbances

algorithmic complexity.

biology.

climate.

Conferences -- 1 day trip

Pockets: tickets, palmtop, pens, photo-id, Tissues, Tchecks, cards, digestion, 3 hankies, cash

Bag: Teeth (gum, brush, paste), pointer, hankies, (batteries | charger), paper&AVs, box ( tie, clean underparts, socks, shirt ), shaver, 3 bars food, sleep: socks&mask&plugs.

Conferences -- Why and how to attend.

Go to panels, discus§s, lunches, BOFs, wash ups, workshops, small sessions.

Clothes:

compare with Pareto and Nash equilibria.

Cooper99 User Interfaces

Problems

1. Cognitive friction.
2. programming is difficult! programming + interaction design is impossible! Triangle := business + enginering + design.
3. dick: with no designers the users get shafted.
4. Homo Logicus: prefer to pilot the plane than be a passenger - choosing to fight complexity to gain control. They want to understand how things work more than use them - prefer a dismantled a clock that they understand to one that works. They are interlectual jocks - superior by making others feel stupid.
5. False goals - technical with 0 user value.

   solution

6. first catch your user. Personas; Goals; Scenarios.
7. persona := a precise named picture of an imaginary user and his/her goals/motivation. Not broad but precise - even if wrong! Not sets or averages but individuals. Not edge cases. Not a buyer who won't use it.
8. Design for one user only. "We are designing for Rosemary not somebody".
9. cast := 3..12 personae. May include some negative personas that we are not designing for.
10. How happy do we need each to be? -> select a few Prime personas.
11. personas have goals ( purposes / ends) that are personal and practical. There are also corporate goals.

12. Tasks are not goals, they lead to goals. Tasks depend on technology but goals stay the same. Tasks often seem to oppose their goals ( war vs peace ). Tasks are transient and goals permanent. Goals may involve many tasks but the tasks must not disguise or block their goal.
13. Let user achieve practical goals without violating personal goals. cf. London: make system run down hill. See motivation theory. Politeness!
14. Scenarios := concise description of how a persona achieves a goal. Act them out to test a design. Play the part of the specific user, not the computer. daily use + necessary use + edge cases. Product success depends on handling the first two, The code must also handle the last.
15. Interaction design focusses on daily and necessary scenarios - both must need to be learned quickly but only daily uses need shortcuts and customization.
16. inflect the interace: daily uses are prominent, the options are out of normal sight.
17. Most people will be somewhere between beginner and experts. But programmers write for experts and marketers sell to beginners. Therefore design for perpetual intermediates.
18. Techniques: pretend its magic, make a vocabulary, break open cliches, lateral thinking
19. Good design is like service in a good restaurent - invisibly smoothing the experience. It is also frustrating because afterwards the good solution is obvious: "of course the wheel is round".

    non-solutions

20. Programming is poring the concrete, so do the design first.
21. Usability testing detects problems but won't give you better ideas.
22. Style guides may not fit your particular user's goals.
23. Focus groups of users tell you what is bad but don't come up with good design ideas.
24. Graphic design can paint the corpse but not make it live.
25. Industrial design makes it fit the hands not the user's sequential needs.
26. New technology/media is likely to be as frustrating as the old.
27. Iteration is slow, expensive, abusive, and needs a rock solid brand name.

    management

    Riding the tiger. Chasing autos ( marketting, coders, sales, ... ).
28. Dragged to follow customers: feature accretion into a dog's breakfast; give up leadership. brains or gray hair.
29. Need long view, responsibility, time, ... like the movies: pre-production, production, post-production. The pre phase plans to save time and money in production. During production managers fetch the pizza.
30. Design documents are equivalent to code: complete, specific, detailed, blueprints. Spiral structure. What vs how.
31. Programmers are not responsible for the user's experience - they solve the technical problems.

32. Where do interaction designers come from?

CORT

CORT FI-FO Review

FI: Find information in your thinking.

FO: Find information outside your thinking.

CORT PISCO 1 Purpose

1. - what do I want out of this thinking.
2. Types::={ find, organise, decide, create , number, map}.
3. type::Types.
4. area - general
5. specific - who, what, when, where, . . .
6. Do a TEC.
7. to fit general area
8. If several purposes, do a PISCO on each.

   CORT PISCO 2 Input

   - survey what is known and unknown.
9. urgency: time, importance, pressures.
10. situation: who is responsible+what factors: people objects things. interactions.
11. knowledge - experience, info, data, unknowns, questions; sources; answers.
12. put on cards & collide by shuffle.
13. futures - Have/given + Need/goal, forces, short scenarios: null + worst + best
14. Do a TEC! Do a FI-FO (Info in and out) [ original input = background, foreground, futureground, surround ]

    CORT PISCO 3 SolutionS

    - Find many before you choose!
15. include bad and improved.

16. First set a quota of alternatives. Quota should be >= 3. Alphabet!
17. look for do-nothing, obvious, algebraic, changed purpose - PISCO, do a TEC, ...
18. add improvements of what you've got. Eg. Reduce uncertainty, improve worst case, combine advantages
19. look for common factors & invariants then try to find ways to vary them.
20. random stimulation.
    Table

    Solutions	a	b	c	d	e	f

    
    (Close Table)
    

    CORT PISCO 4 Choice

    - my choice to fit my Purpose because ....
21. for each solution rank by:
    Table

    Solutions	a	b	c	d	e	f
    PMI	0	0	0	0	0	0
    feel	0	0	0	0	0	0
    ease	0	0	0	0	0	0
    cost	0	0	0	0	0	0
    fit	0	0	0	0	0	0
    consequences
    best	0	0	0	0	0	0
    likely	0	0	0	0	0	0
    worst	0	0	0	0	0	0
    plan B	0	0	0	0	0	0
    risk	0	0	0	0	0	0

    
    (Close Table)
    Priorities

22. Review the solutions><rankings matrix.
23. Make your choice and explain why.

    CORT PISCO 5 Operations

24. - a simple practical plan of action that ensures implementation of chosen solution.
25. Planning
    • What resources & data? Tackle uncertainties early!
    • Visualize actions
    • Map obvious contingencies+quit points
    Three phases:
    
    1. immediately -- do something!
    2. development -- make it work
    3. follow up
       • Operations
       • Periodic maintenance?
       • Stopping rule
       • What have you learned?
    
    Define who does what + when + how.

26. Do a TEC!

    CORT PMI

    Plus

    Minus

    Interesting

    CORT TEC

    Target - select specific clearly in area

    1. type of target
    2. target area, subtargets, be specific, extract one.

       Expand - think everything possible around target

       context, association, breadth, depth/refine:{sequence, detail, parallel, conjunction}, alternatives
    3. Avoid conclusions and wandering. Review & vary constants.

       Contract - reduce and harvest for target.

       one of summary, simplify, choice, conclude, combine, sort/organise, contained in, and/or

CSP notation translated

CTL Modal Logic

Cultures and organizations

Mimetic processes for communicating systems. Geographic input. [DiamondJ03]

Larry Miller's stages := prophets; barbarians; builders & explorers; administrators; bureaucrats; aristocrats.

See 4 types of people

Curvature

Domestic Data

De Bono Biodics

De Bono on Thinking

Rightness

1. R::= ( Emotional, logicAl, Unique, recOgnition ) vs. proto-truth (scIentific, not disproved yet).

   Mistakes

2. M::= ( monorail, magnitude,misfit, must be, missout ).

   Understanding

3. L::= (describe event, porridge words, give a name, give a structure, blueprint (names+structure)).

   CORT Frameworks

   PMI, OPV, EBS, ADI, CAF, APC, C&S, AGO, FIP, TEC-PISCO (>=> Palm/memo/CORT* )

   Happiness Purpose

   Life space <== Self space. EPA

   Steps

   Normal: copy, modify, improve, implement, abstract, make practical, build on, negative-positive

   Lateral: set quota/list; explode, force fit, reverse, extreme, forbid, Po, random, jump off, change medium/mode, change personel, rotate focus, map/tabulate/draw, contrast/promin

   Review: assumptions, evidence, FI-FO, boundaries, invariants, fixed components, defects.

   bubble logic & logic bubbles.

   Put on different colored thinking hats

   Hat Colors
4. White - facts, figures and objective information.
5. Red - emotions, feelings, hunches and intuition.
6. Black - logical negative, judgment, caution, worst case scenario.
7. Yellow - logical positive, feasibility, benefits, best possible scenario.
8. Green - new ideas and creative thinking.
9. Blue - control of the thinking process, broader overview. (The Six Hat Method, Holst Group, reported in The Observer 12/Sep/2004 London UK)

Design Patterns

GoF Design Pattern Catalog

Creational Patterns

Abstract Factory, Builder, Factory Method, Prototype, Singleton

Structural Pattern

Adapter, Bridge, Composite, Decorator, Facade, Flyweight, Proxy

Behavioral Patterns

Chain of Responsibility, Command, Interpreter, Iterator, Mediator, Memento, Observer, State, Strategy, Template Method, Visitor

. . . . . . . . . ( end of section GoF Design Patterns) <<Contents | End>>

Digits have phonetic Mnemonics

passcodes? 90710 92404 pen raisor log[10]π .4971 ropey.cat 000021527 Senate Link.

EMACS

Ergonomics

back extn§ b4 lift/

.Features Features Funhouse: SD Mag

Describe proposals like an optician describes spectacles... a feature at a time

Remember the Future

Ask your customer what you need to know. Goal: Understand your customer’s definition of success. Activity: Hand each of your customers a few pieces of paper. Ask them to imagine that they’ve been using your product continuously for one week. Ask your customers to write down, in as much detail as possible, exactly what the system will have done to make them happy (or successful or rich or safe or secure or smart—choose the adjective that works best for your system). Note that the question’s phrasing is extremely important, as you’ll get different results if you ask “What should the system do?” instead of “What will the system have done?” If you’re skeptical, just try it.

Fighting Jetlag the Forbes way

Lots of water, no cafeine, no alchohol.

Exercise inflight.

Arrive at night? Sleep inflight! Arrive in day? Keep awake.

Flower Meanings

Forcefield Analysis

Getting Things Done -- GTD -- David Allen

life-hacking top-down
1. Collect all the stuff. Anything that can be done in 2 minutes: do it.
2. Process each piece of stuff in a precise way: classify, label, retrieve. EG: email:={to be read, to be answered}. To do lists (next-action lists).

3. Describe items on to do lists as concretely as possible -- ready to be executed without thought.

   "small scale cleverness"

   Sort by: how long will it take, where are you, what devices, what people to hand?

   Free of worrrying about things to do.

   aggreements with yourself that are undischarged. Open loops: Make projects of intentions, file, list

   History: UCBerkeley, Bookbinder, drugs, breakdown, karate, hospital, Roger Hinkins MSIA est

Goal analysis

1. explode -> subgoals; classify subgoals as fuzzy | duplicate | unwanted | performance.
2. Delete unwanted & duplicate.
3. For f:fuzzy, Goal analysis(f),delete f.
4. Quantify; qualify; specify
5. check that list guarantees g.

6. Results thin air | ok | surprise;(mea culpa | change subject | new problem)

7. control chart ).

   Good writing

   can't make a bad idea work, bad writing can stop a project starting.

   Grants

   TSSA Teaching Skills Study award SOTL Scholarship of Teaching and Learning PSP Professional Study program FPDCC for content/research ion a discipline

   Grants D Berleant Comm ACM V43n8(Aug 2000)pp24-25

   Good

   early.

   typography: san-serif headings, body <12pt

   narative has abstract & conclusions

   refer to self as "we".

   Bad

   Duplicated summary in narative. Numbered sections in narative as subsubsections.

   Grants M Brasch 10/2/99 EECR1189

   Note

   CSUSB Distance learn/ hispanic outreach. .2 Introduc§ paperwork! big -> www latency!

   Success factors

   2:1 = prep:write. Latest info Partners, interfaces, & collabora§ is want\. Contact business & congressmen. real & positive Available -> handout. .2 Define organisa§ Boilerplate: org+environment stats Plan 1..5yrs: Prioritize needs/ideas Competencies/strengths:we have... Support systems: who does admin communifation etc.- its a contract... staff devt.

   Proposal structure

   see handout for generic.

   Follow rules

   Use given format or its trashed! eg. SB county reqs 2sided recycled paper! Watermark

   Intro

   sum&overvu

   Statement o need

   knowledge<-ressarch . p desc timeline who, do what, when diagram?color?layout ask!

   Budget

   Organisation

   History names contacts constituency qualifica§s

   Conclusion

   . . . . . . . . . ( end of section Proposal structure) <<Contents | End>>

   Source devt

   www.infoed.org -> info.office smarts -> specialized

   Budget

   not too little or too much. Must fit
   1. -> needs. Costs...., matching genuine consultants! Be ready for a Phone call nego§ session. Never say no, repropose.

      Writing

      ask not beg: invite investment in a partnership. not hesitant: "may be able", "we hope". "we strongly believe" Don't men§ mistakes/failures/political smart not cute, nothing extra sell idea,process, product rules: margins, type size,length readable-check check data,check data,check data,.. Promise what you can do, then deliver what you promised

      Include how it will continue

      Letter of intent

      2 or 3 Pages, Hook up front Show you know about agency & share its goals. top person must sign !(forgo brag points)

      Critique

      Evaluate

      continuous thruout whole progect.

      Thank, invite,

      Success

      Say thank you! Invite themto elebrations! Send results.

   GRASP

   Assign responsibilities to object/class:
   
   1. to the Expert.
   2. to the Creator.
   3. to a Controler.
   4. to give Low coupling.
   5. to give High cohesion.
   6. to use Polymorphism.
   7. to a Purely fabricated class
   8. Indirectly. Don't talk to strangers/Demeter

      see cs375

      Guildford generates solutions

      factorize, vary the factors, recombine.

      Historical Dynamics

      Peter Turchin

      1. Historical Dynamics: Why States rise and fall ISBN 0-691-11669-5 $35 Princeton UP (complexity) 2003? D16.25 T87 3rd

         Asabaya? Ability of people to work for society rather than selves.

         Agrarian societies are unstable. Every 100 years the peasants revolt.

      2. dN/dt=r *N*(1-N/k(S)),
      3. dS/dt=N*(1-N/k(S))-β*N,
      4. k(S)=1+c *S/(s0 + S).
      5. Societies tend to appear where there used to be active borders.
      eg. Anastasi

      Toynbee. Challenge&response. mimetics.

      Spengler. pre_culture; Culture & (Feudal &(formation; breakdown); Aristocratic; absolutism); Civilization & (Revolution; transition; Caesarism; Final); aftermath.

      McCulloch. landed aristocrats vs plutocrats. =~=Whig vs Tory

      Asimov. Successful Emperors put down successful generals.

      Diamond. Geography rules!

      history of methods and processses

      40 Monolythic after math 50 math subprograms 60 modules 70 SP info data ddd 80 " " " dad 90 objects processes 00 XP/agile

      how to get key Questions from many

      qns -> cards, 3 times {shuffle, rate pair cards out of 7} , sum, ask for card with max total down.

   9. I will not fear. Fear is the mind killer.

      Fear

      is the little-death that brings total obliteration. I will face my fear. I will permit it to pass over me and through me. And when it has gone past I will turn the inner eye to see its path. Where the fear has gone there will be nothing. Only I will remain.

      Frank Herbert

      IEEESw authors

      mission=build community, topics..., style = readable, length <5400.words, 1.fig=200.words, normally refs <= 12. only republish best, process= ( submit 1 printable+ 1 source; peer reveiw -> significant revision; edit for errors, style, content -> concise +well-worded+useful ).

      Odd Theorem

      if for all x(f(x) or g(x)) then (all f or some g)

      Proof of Odd Theorem

      
      Let
      
      
      1. (let)|- (1): for all x(f(x) or g(x))
         
      2. (let)|- (2): not(all f or some g)
         
      3. (2)|- (3): not(all f)
         
      4. (2)|- (4): not(some g)
         
      5. (3, x:=v)|- (5): not f(v).
         
      6. (1, x:=v)|- (6): f(v) or g(v),
         Case
         1. f(v),
            
         2. (5)|-RAA.
         
         (End of Case)
         Case
         1. g(v),
            
         2. (4, x:=v)|-not g(v),
            
         3. (5)|-RAA.
         
         (Close Case )
         
      
      (Close Let )
      

      Introduce person template

   10. PERSON::= following
       Net
       1. name::...
       2. ugrad degree::...
       3. highest degree::...
       4. area::...
       5. kicker::...
       6. now::...

       
       (End of Net)
       
       

       Jackson's 2001 problem frames.

       Also see [ Problem_Frames_Approach ] on the wikipedia for a more uptodate summary of the Problem Oriented Approach to requirements and software development.

       Jackson01

       1. Michael A Jackson
       2. Problem Frames: Analyzing and structuring software development problems
       3. Addison wesley 2001 ISBN 0-201-59627-X QA76.76 D47 J32 2001
       1. domains: machine, designed, given.
       2. domains: symbolic/lexical, causal, biddable.
       3. Domains are shared between subproblems. Each subproblem has its own machine. Do NOT put two or more subproblems into a single diagram.

          Diagrams: context, problem, problem frame, statediagram, tree diagrams(JSP).

          Description domains: symbolic and describes a requirement refering to phenomena in other domains.

          Requirements refer to domains and constrain domains.

          Connections/interfaces are phenomena shared between two or more domins.

          Shared events normally have one controlling domain.

          Interfaces can be causal, symbolic, or a set of shared events,

          A connection domain describes indirect and complex connection between domains.

          
          Net

          1. Phenomena: individuals or relations.
          2. Individuals: entities, events, values.
          3. Relations: roles, states, truths.
          4. Roles: @(events, values).
          5. states: @(entities, values).
          6. truths: @ # values,
          7. relationships: @ # entities.

          
          (End of Net)
          
          Continuous vs discrete phenomena.

          Distinguish definition, designation, assertion.

          Frames. Basic Frames: required behavior, commanded behavior, Information, display, simple workpieces, transformation.

          Variants. Add descriptions, operators, and/connections. Control variant: change the controler of a shared event(inversion).

          Problems: audit, behaviour,

          Decompositions. Introduce a model, separate perfect from imperfect,

          Concerns. Frame. Givens & machine_specification implies Requirement.

          Note one problems given is another problems requirement.

       4. overrun, initialization, reliability, identities, completeness.

          Breakage, commensurability, conceptual.

          STD/FSM/modified UML statechart. Shows events that are rejected, and those that are rejected. Also can show a special unknown state,

       . . . . . . . . . ( end of section Jackson's 2001 problem frames.) <<Contents | End>>

       Jackson's domain characteristics.

   11. domains have dimensions,
   12. |dimensions| in 1..,
   13. domains >== { tangible, intangible }.
   14. domains >== {formal, informal }.
   15. domains >=={bounded,unbounded }.
   16. tangible ==> informal ==> unbounded.
   17. domains >== { static, dynamic }.
   18. dynamic >== { inert, reactive, active }.
   19. active >== {autonomous, biddable, programmable }.

       2001

   20. active >== {causal, biddable, lexical }

       Jackson's problem frames.

       1. FRAME::=following,
          Net
          1. principle_parts::Sets,
          2. domains::@principle_parts, relationships::@principle_parts, -- natural and required
             
          3. |-no relationships & domains.
             
          4. |-principle_parts = relationships | domains.
          5. machine::domains, -- that which is to be built, shown with 2 stripes
          6. other_domains::=domains~{machine},
             
          7. |-other_domains>=={designed, given}. designed shown with one stripe.

          8. connections::@(domains, domains), -- shared phenomena,
          9. 2001 connections::@@domains, -- shared phenomena,
          10. whole_part::@(domains, domains),
          11. constrains::@(relationships, domains).

          
          (End of Net)
          
          

          simple IS frame

       2. simpleIS::=FRAME with following
          Net
          
          
          1. |-machine=system.
             
          2. |-other_domains= { real_world, information_outputs, information_requests}.
             
          3. |-relationships={ information_function},
             
          4. |-constraint= information_function +>other_domains.
             
          5. |-connections= system +>other_domains ,
             
          6. |-whole_part={},
             
          7. |-required=constraint.
             
          8. |-real_world is static | dynamic & active.
             
          9. |-system does not control real_world.
             
          10. |-information_requests is active & dynamic. Methods: model simulated in system, JSD.

          
          (End of Net)
          
          
       3. may need a connection frame between system and real_world.

          simple control frame

       4. control::=FRAME with following
          Net
          
          
          1. |-machine=controler,
             
          2. |-other_domains = {controlled_domain},
             
          3. |-connections= controller+>controlled_domain,
             
          4. |-whole_part={},
             
          5. |-relationships={ desired_behavior},
             
          6. |-constrains = desired_behavior+>controlled_domain,
             
          7. |-controlled_domain is dynamic & active & reactive.
          8. controler does control controlled_domain directly or there is a need to solve problem with connection_domain.
          9. controlled_domain may have parts, -- washing_machine + user.
          10. controlled_domain must have 2 descriptions -- indicative and optative.

          
          (End of Net)
          
          

          connection frame

       5. connection::=FRAME with following
          Net
          used when a connection is needed between parts but there are no shared phenoma connecting them.
          
          1. |-machine=connecting_machine,
             
          2. |-other_domains={a, b, ac, cb},
          3. connections={},
             
          4. |-whole_part= a+>ac | c+>ac | b+>bc | c+>bc,
             
          5. |-relationships = {achievable_correspondence},
             
          6. |-constrains = achievable_correspondence+>a | achievable_correspondence+>b.

          7. once connect/ is done may need to treat a and/or b as a machine

          
          (End of Net)
          
          

          JSP frame

       6. JSP::=FRAME with following
          Net
          tight constraints gives a strong method.
          
          1. |-machine= program,
             
          2. |-other_domains = {input_streams, output_streams }, -- given & goal data. Both sequential structures of elements describable by regular expression..
             
          3. |-connections = { program +> input_streams, program +> output_streams },
             
          4. |-whole_part = {},
             
          5. |-relationships = { input_output_condition }, -- relates regular expressions that describe input_streams and output_streams simply. Simply means that there is a single regular expression that is reducible to i/o expressions. This expression describes a program structure -- a non-deterministic FSA.
             
          6. |-constraints = { input_output_condition +>input_streams, input_output_condition +>output_streams },

             example: collate and merge 2 sorted directory list.

             Advanced_JSP for handling problems where structures do not fit and for removing non-determinism.

          
          (End of Net)
          
          

          workpieces frame

       7. workpieces::=FRAME with following
          Net
          
          
          1. |-other_domains = { operation_requests, workpieces },
             
          2. |-connections = { operation_requests +> machine },
             
          3. |-whole_part = { machine +> workpieces },
             
          4. |-relationships = { operation_properties },
             
          5. |-constrains = { operation_properties +> operation_requests , operation_properties +> workpieces },
          6. operation_requests in one_dimensional active dynamic. workpieces in inert dynamic.
          7. Different workpieces are independent, -- operations change only one piece.

          
          (End of Net)
          
          

       Jackson Satisfaction Argument

       
       
   21. (Domain, Specification)|- (Satisfaction Argument): Requirement.

       JacksonTwaddle97

       1. Michael Jackson & Graham Twaddle
       2. Business Process Implementation: Building Workflow Systems,
       3. Addison Wesley ACM Press 199? ISBN 0-201-17768-4 3rd hd58.87.j32 1997
       4. =EXPERIENCE SPECIFICATION MODEL OFFICE WORKFLOW PEOPLE DATA PROCESS FLEXIBLE vs BUSINESS RULES TABULAR GRAPHIC METADATA
       5. workflow_problem_frame::= following,
          Net
          
          
          1. |- (minimal_workflow_frame): The machine supports an office that interacts with an outside world.
             
          2. |-The prime business need is to keep track of long term commitments, contracts, and obligations.
             
          3. |-There are rigid business rules and flexible activities.
             
          4. |-activities are multitasked, error correcting, and proceed at a human pace.
             
          5. |-not safety critical.

          
          (End of Net)
          
          
       6. theoretical_method:= data; process; tasks; workflow.
       7. In practice incremental and iterative delivery is feasible.
       8. data:=simple ERD, like SSADM.
       9. task_types:=initiated performed content task_details.
       10. initiated:=X | T | P | I. X=eXternal, T=Time, P=follows Preceeding, I=Internally.
       11. performed= A | M, A=Automatically, M=not A, Manually,
       12. content:= E | K| U | D | O, E=dataEntry, K=checK, U=Update, D=Decision, O=Output.
       13. Tasks involve entities.
       14. LC:=" life cycle".
       15. An entity life cycle is a defined sequence of stages but an entity may not progress thru the stages in such a simple way. Office work may backtrack, hangup, fail, or multitask parts of stages at one time. Stages may not be omitted. Backtracking (a setback) means handling side-effects: beneficent, neutral, and intolerable. cf JSP.
       16. If a stage contains a task that fails then the current life cycle fails and initiates a different one instead.
       17. Stages determine states: State = ("In" | "Failed" | "Awaiting" | "Halted" ) stage.
       18. Within a Stage many tasks can execute in parallel. some can spawn (one|many (inclusive | exclusive)) subtasks (sometimes). One subtask can be spawned by many tasks, and a subtasks can restart their parent tasks (in a loop).
       19. Task states = null; start; (n/a | run | failed | passed). passed states do not spawn subtasks, run states must start their subtasks. Task states determine lifecycle states.
       20. There are rules for assigning tasks to stages.
       21. One life cycle can depend on another one. Changing stage depends on one(or all) other linked entities of a given type is|are past a certain stage. Tasks can start and halt other life cycles.
       22. Entities are placed in classes. Classes form a heterarchy -- multiple inheritance. Also classification entities -- classes of objects each defining a class of object!
       23. Entities play roles in entity life cycles. roles require only a subset of the attributes, Also several types of entity can play the part in a single role.
       24. Datasets are structured navigation paths between entity types. from A access one B and many Cs. They are chosen to fit tasks.
       25. Programs support tasks - within task context and using task content. actions include SET_RESULT, START_LC, SUSPEND_LC, RESUME_LC, CANCEL_LC, SETBACK_LC, WAIT..., SIMPLE_CHECK, COMPLEX_CHECK, SIMPLE_SET, APPLICABLE_WHEN. Some tasks must not be repeated, others may be repeated when backtracking.
       26. Decision Tables!
       27. Tasks and life cycle mainly define wrong sequences. Work flows help get good things done. Work flows are about scheduling, options, menus, and efficiency. Work flows are based on a relational data base:
       28. task_details:=
           Net{

           1. Each task is in a stage of a life cycle of an entity.
           2. Each task has a task_type that has a program, data set, and a set of skills.
           3. Tasks are related to users who can/should do them by Skills and by stages and depts for example.
              }.
       29. Detailed reporting and so tuning of the workflows.
       30. Life cycle definitions and the office workflow are also held in the data base. "Process representations become data". Process data is PLANs and FEATUREs.
       31. The only purpose of documentation is understanding.... but if documentation is in a data base is also useful to the software.
       32. dick:the office workflow frame fits agile software development process.

       Lao Tzu on problems

   22. Deal with the difficult while it is still easy.
   23. Solve large problems when they are still small.
   24. Preventing large problems by taking small steps is easier than solving them.
   25. By small actions great things are accomplished.

       Man's Mortallity by Michael Arlan 1933 p316

       "What we have apparently got -- a mechanized Messiah. We never really took to the meek and gentle poet who called us to repentance, did we? So now we've apparently got a Messiah who speaks in a language we can understande -- mathematics instead of parables, the miracle of atomic energy instead of loaves and fishes."

       Markets

       Everett Roger's innovation
   26. curve::=following (
       innovators; early adopters; the_chasm early majority; late majority; laggards
       ).

       Buying hierarchy

       by Windermere assocs o SG

       function; reliability; convenience; price.

       Metcalfes law

       The value of a network grows exponentionally with the number of nodes. N log(N)?

       markup languages

   27. RTL
   28. SGML
   29. ?? HDML -- handheld Device ML
   30. -> HTML
   31. -> CHTML -- compact HTML
   32. -> TinyHTML -- for PalmOS
   33. -> XML
   34. +> XSL -- stylesheet
   35. +> XSLT -- stylesheet transform
   36. -> XHTML
   37. -> RML -- relational ML
   38. -> xCBL -- common business lang XML+HTML -> WML -- wireless Markup Language

       SOAP

   39. http://www.w3.org/TR/SOAP

       Maypole extends LAMP

       Linux Journal 2005 131(mar 2005)p3 and 18 line web database application.

       Medieval curiculum

   40. quadrivium::= arithmetic; geometry; astronomy; music.
   41. trivium::= rhetoric; grammar; logic.

       Early vs late medieval think/ in Europe. 1. record ancient. 2. learn the auctores. 3. Sic et Non vs faith. 4. Disputations. 5. Summa

       Meeting plus and minus

       +ve
   42. ask, start build solve note listen

       -ve,

   43. shutout mumble criticize makeproblem disagree instant

       Meeting Agendas should include

       Who, What, Where, When
       
       OVERALL GOAL:

       MEETING GOAL:

       PROCESS:

       BEFORE THE MEETING:

       
       

       Meeting -- conversation Cafe

       Well thought ot technique for meetings that identify and solve problems [ Process%20and%20Agreements.htm ]

       Mistakes tricks Twisted thinking

       Mistake

       1. monorail, magnitude, misfit, must be, missout

          tricks

       2. emotional loadings, prestige, fashion, tradition
       3. jargon, catchphrases/cliches/slogans/labels, ambiguity, overly abstract
       4. decoration
       5. blatant assertion, repetition

          Twisted thinking

          black and white only. one is some is all negative/positive ego - binoculars. instantly discount. mind-reading and fortune telling. feelings are the only reality. shouldism & mustaba§. once implies permanent property.

       . . . . . . . . . ( end of section Mistakes tricks Twisted thinking) <<Contents | End>>

       Moral thinking by Wilson

       phil - degree to which one can identify with others as equals

       emp - insight into our own and others feelings.

       gig - knowledge (Gignosis)

   44. gig1 - knowledge of facts
   45. gig2 - know-how: knowing how to act
   46. dik - rational organisation of rules from the above
   47. phron - organising personal rules effecting ourselves

       krat - resolution, translating the above into action

       Natural Semantic Metalanguage Primitives

       [Goddard97]
       1. I you someone people/person something
       2. think know want feel see hear
       3. say word
       4. do happen move
       5. there_is
       6. live die
       7. this the_same other
       8. one two some many/much all
       9. good bad
       10. big small
       11. when/time now before after a_long_time a_short_time for_some_time
       12. where/place here above below far near side inside
       13. because if
       14. not maybe
       15. can
       16. very more
       17. kind_of part_of
       18. like

       Object Orientation

   48. OOP::=
       Net{

       1. abstraction.
       2. encapsulation.
       3. polymorphism.
       4. inheritance.

       
       }=::OOP.

       Ozymandias Tleilaxu

       Here lies a toppled god --- His fall was not a small one. We did but build his pedestal, A narrow and a tall one.
   49. Frank Herbert, Dune Messiah

       Pareto Equilibrium

       State where no one stakeholder can improve their own situation.

       Von Neuman: zero sum games have equilibra.

       Nash: nonzero sum games have equilibra.

       Patterns of proof -- Proof Patterns

       Template

       Situation

       Therefore

       But

       Construction

       Show for all x some y such that Pxy

       Given x find y such that Pxy

       But

       Deduction

       Show for all x, if Px then Qx

       Let x, Px. Show Qx.

       But

       Reduction

       Show P is false

       Let P....

       But

       Induction

       Show for all integers n>=n0, P(n)

       Two steps

       Basis. Prove P(n0)

       Induction. Prove for k>=n0, if Pk then P(k+1)

       But

       Analysis

       Show P or Q

       Cases

       Let R. Show P.

       Let not R. Show Q.

       But

       Analysis - dilemma

       Know P or Q Show R

       Cases

       Let P. Show R.

       Let Q. Show R

       But

       People as Non-Linear, First-Order Components

       Cockburn00
       • Alistair Cockburn [ arc@acm.org ]
       • Characterizing People as Non-Linear, First-Order Components in Software Development
       • Proc SCI/ISAS2000 VI pp728-736 [SCI00]
       • =EXPERIENCE 20 projects PEOPLE
       • A commonly observed pattern by methodologists and tool smiths

         ---

         1. The people on the projects were not interested in learning our system.
         2. They were successfully able to ignore us, and were still delivering software, anyway.
         3. Almost any methodology can be made to work on some project.
         4. Any methodology can manage to fail on some project.
         5. Heavy processes can be successful.
         6. Light processes are more often successful, and more importantly, the people on those projects credit the success to the lightness of the methodology.
         7. People:
            
            1. are communicating beings, doing best face-to-face, in person, with real-time question and answer.
            2. have trouble acting consistently over time.
            3. are highly variable, varying from day to day and place to place.
            4. generally want to be good citizens, are good at looking around, taking initiative, and doing "whatever is needed"
            5. need both think time and communicating opportunities.
            6. work well from examples.
            7. prefer to fail conservatively than to risk succeeding differently
            8. prefer to invent than to research
            9. can only keep a small amount in their heads, and make mistakes
            10. find it hard to change their habits.
            
            

         8. Individual personalities easily dominate a project.
         9. A person's personality profile strongly affects their ability to perform specific assignments.
         10. Paper documentation is the least effective communication medium available.

         ---

       People like 90% solutions! Machines need 100% perfection!

       Polya - how to solve it

       princeton 1988 2nd edn isbn0-691-02356-5 qa11p6 1988
       1. Understand, 2. Plan, 3. Carry_out_the_plan, 4. Looking_Back.

          Understand

       2. what is the unknown? -- goal/output/conclusion?
       3. What are the data? -- given/input/parameters/hypothesis
       4. What are the conditions? -- operations/relations/premises connect/ given to goal
       5. check: possible & sufficient ~ redundant~ contradictory ~ separate
       6. Draw a diagram.
       7. Introduce a suitable notation.
       8. Separate the various parts of the condition. Can you write them down?

          Plan

       9. Use plausible, reversed, and lateral thinking to invent a way to solve the problem. Avoid rigor and details.
       10. look at the goal/end point first!
       11. Have you seen a similar problem before?
           • Look for similar goal/given/...
           • Look for more general/specific.
           • Look at any previously solved problem/theorem... can you make use of it?
       12. Can you restate/reverse ths problem?
       13. Review
           
           1. Did you use all the data/givens?
           2. did you use the whole condition?
           3. Have you allowed all the notions in the problem... if not revise your plan.
           
           

           Carry_out_the_plan

       14. Carry out your plan step by rigorous step.
       15. Use formal techniques that fill in the details in your plan.+
       16. At each step look for signs of progress,
       17. Check each step for correctness.
           • Can you see that it is correct(intuitive)?
           • Can you prove that it is correct?
       18. Fill in the details in steps top-down by refinement.+

           Looking_Back

       19. Can you check the result?
       20. Can you check the steps?
       21. Did you use all the givens?
       22. Can you improve the steps?
       23. Can you see the whole at a glance?
       24. Can you use the result or the method in some other probleme?
       25. How can you share/present/publish the result? +

       Presentations and PowerPoint

       Advice from Desrochers & Cheal of CSUN

       Design: Choose the right layout, line, scale, color, movement, and timing.

       Good Layouts: Heading and picture, bar graph, 4 or 5 bullets... Empty space. NO PARAGRAPHS.

       Mix layouts. Avoid the "machine gun" bullets.

       Scale: Big is seen as most important. Minimum font 16pt, San Serif. Big text is better than small. Big hall->big text.

       Color: moods and style rather than content. Careful that foreground contrasts background.

       Avoid laser: program a red circle cursor.

       Movement: Don't animate it -- unless it is special, meaningful, or to get attention.

       DO NOT do the slides first.

   50. (1) Plan, (2) write, (3) illustrate, (4) edit without mercy.

       Share metaphors, stories, & analogies verbally.

       Find ways to find out audience experiences/needs and link to them.

       Find ways to allow/encourage thinking about the data, making plans, doing things.

       Technology. Check it out before hand: systems and visibility. Turn off sleep mode.

       If you handout notes.... do it last!

       Principia Mathematica Definition of 2

       For sets A, B, 1 A, 1 B(0(A & B) iff 2 (A | B)).

       Reasons for Software Failure

       Technical: Bugs, Mis-communication, Lack of Testing, ...?

       Human error: Lazy Cheap Stupid Ignorant Malicious!

       RISKS Forum

       a MODERATED digest. Its Usenet equivalent is comp.risks.
   51. => SUBMISSIONS: to risks@CSL.sri.com with meaningful SUBJECT: line.
   52. => SUBSCRIPTIONS: PLEASE read RISKS as a newsgroup (comp.risks or equivalent) .
   53. => The INFO file (submissions, default disclaimers, archive sites,
   54. copyright policy, PRIVACY digests, etc.) is also obtainable from [ risksinfo.html ]

   55. => ARCHIVES are available: ftp://ftp.sri.com/risks or
   56. ftp ftp.sri.com<CR>login anonymous<CR>[YourNetAddress]<CR>cd risks
   57. [volume-summary issues are in risks-*.00]
   58. [back volumes have their own subdirectories, e.g., "cd 19" for volume 19]
   59. http://catless.ncl.ac.uk/Risks/VL.IS.html [i.e., VoLume, ISsue]. [ http://the.wiretapped.net/security/textfiles/risks-digest/ ]
   60. ==> PostScript copy of PGN's comprehensive historical summary of one liners:
   61. illustrative.PS at ftp.sri.com/risks .

       RMA Rate Monotonic Analysis

   62. RMA::= following
       Net
       1. TASK::= Net{period, worst, block:Duratlon,...}.
       2. SIMPLE_RMA::= following
          Net
          1. n::Nat= given, number of tasks.
          2. tasks::#TASK = given.
          3. Schedulable::@= +(worst/period) + max(block/period) <= n*( 2^(1/n) -1).
          4. note. Some quote: max(1..n-1); (block/period).

          
          (End of Net)
          
          

       
       (End of Net)
       
       

       Scientific evidence

       USA federal rule of evidence 702.

       Daubert

   63. Testable, falsifiable, refutable.
   64. Peer reviewed & published.
   65. Error rate of technique.
   66. Acceptedness by scientific community.

       Kumho - expert(skill, experience)

   67. same criteria.
   68. applied to particular evidence.

       Baer92

       WilsonF00

       Seminar TODO

       Who? what? when?

       Post to Dept office, web site, personal data base.

       Where=JBH391/389

       Schedule room & equipment

       get intro info!

       ??parking

       announce: csci, twalde

       Invite: bb or campus

       remind: bb or campus

       snacks

       setup

       ?? Lunch

       ---

       int life comm??

       -

       Shirky03 GROUP Psychology

   69. Clay Shirky
   70. A Group Is Its Own Worst Enemy
   71. ETech (Apr 2003 ) + Published July 1, 2003 on the "Networks, Economics, and Culture" mailing list. [ group_enemy.html ]
   72. =TALK =HISTORY WWW/NET SOCIAL GROUP PEOPLE CULTURE WEB2.0 TEAM
   73. Refers to W.R. Bion: "Experiences in Groups": Groups of people become both collections of individuals and a self-coordinating entitiy. Therapeutic groups tend to: talk sex, identify external enemies, and religiously venerate something. Need for structure for groups to work. In particular rules for creating rules...
   74. Examples of BBSs, Usenet, .... where open free group is invaded.
   75. Therefore need structure in social systems.
   76. Technology (TCP/IP, WiFi, IM, Mobile phones, ...) now lets all people be online together.
   77. Example. Ito's Conference call moderated on chat with wiki for references.
   78. For a given technology -- most groups fail!
   79. Accept:
       
       1. Social and technical issues are intertwingled: they can not be separated niether does the technical drive the social. The system will have antics -- emergent properties. There will be a formal rules and informal rules.
       2. Members are not just users. There will be an onion structure. Example: reader -> anonimous coward -> named person -> moderator. The Core subgroup love and weed the garden that others wander through (and vandalize?). = Volunteer fire department.
       3. One user = one vote does not work when anybody can be a user.
       
       
   80. Things to design for
       
       1. Give members a handle -- stable local name. So they get a reputation.
       2. Make a simple way for behavior to be visible -- who is in good standing?
       3. Make it difficult to enter the core subgroups. The group is the real user!
       4. Make the communications scale. Encourage a small world structure. Many linked small groups.
       
       

       Shirky08 Sociology of Net

   81. Clay Shirky
   82. Here comes everybody
   83. Penguin NY NY 2008 HM851 S5465 ISBN 978-1-59420-153-0
   84. =EXAMPLES SOCIOLOGY WEB/NET ECONOMICS SOCIAL CAPITAL SMALL WORLDS POWER LAWS
   85. Net lowers cost of communication, publication, copying, collaboration to ZERO. So a lot more of all of these.
   86. More is Different. Faster is Different.
   87. New paradigm: Publish; Filter.
   88. Many attempts, failure is free, on the way to one big success.
   89. A shared resource needs motivated people and people need Face-to-face meetings.
   90. Developing_a_resource::= Promise; Tool; Bargain.
   91. Examples: Usenet FlashMobs F/OSS Linux SourceForge Flickr MySpace FaceBook MeetMe EBay Wikipedia Wikitorial Encarta

       Shorthand

       § .ion / .ing \ .ed ß .ble ƒ .ful µ ? ¿ Think a a A A b be B but c can C could d do D Dick e is|am E exists f for F from g go G get h had H how j ? J ? k know l let m me n on N Net o of O Open p put q queue r are s she S some t the T Tricia 2 to u you U ? v have w with x ex... y why z has

       Sincerity is the important thing -- Once you can fake that you've got it made.

       Burnsten07

       1. Sidney L Burnsten
       2. To map a process, first find its swimlane
       3. Commun ACM V50n10(Oct 2007)p14
       4. =LETTER IBM SLB GRAPHIC ANALYSIS DESIGN METHOD DesignFlow
       5. SLB::="Swim Lane Based".
       6. Draw both "as is" and "to be" diagrams.
       7. Involve users and stakeholders.
       8. Each actor has a swimlane. Shows activities, information, & decisions.
       9. Claims many years of successful use.
       10. Claims better than DFDs or Usecases.

       Soundex encoding

       Keep first letter after that - remove vowels, h, w and map (
       1. bfpv +> 1 |
       2. cgjkqsxz +> 2 |
       3. dt +> 3 |
       4. l+>4 |
       5. mn +> 5 |
       6. r+>6 |
       ) remove duplicate digits

       zero-pad | trim to : letter digit^3

       SRS from LeffinghamWidrig00

       Modern SRS

       Overview

       Revision History

       Table of Contents

       1.0 Introduction

       1.1 Purpose

       1.2 Scope

       1.3 Reference

       1.4 Assumptions and dependencies

       . . . . . . . . . ( end of section 1.0 Introduction) <<Contents | End>>

       2.0 Use-Case Model Survey

       3.0 Actor survey

       4.0 Requirements

       4.1 Functional Requirements

       4.2 Nonfunctional Requirements

       4.2.1 Usabilty

       4.3.2 Reliability

       4.2.3 Performance

       4.2.4 Supportability

       . . . . . . . . . ( end of section 4.2 Nonfunctional Requirements) <<Contents | End>>

       . . . . . . . . . ( end of section 4.0 Requirements) <<Contents | End>>

       5.0 Online Use Docs and Help

       6.0 Design Constraints

       7.0 Purchased Components

       8.0 Interfaces

       8.1 User interfaces

       8.2 Hardware Interfaces

       8.3 Software Interfaces

       8.4 Communication Interfaces

       . . . . . . . . . ( end of section 8.0 Interfaces) <<Contents | End>>

       9.0 Licensing Requirements

       .10.0 Legal, copyright, and other notices

       11.0 Applicable Standards

       Index

       Glossary

       Appendix: Use-Case Specifications

       Revision History

       Usecase Name

       Flow of Events

       Basic

       Alternative

       . . . . . . . . . ( end of section Flow of Events) <<Contents | End>>

       Special Requirements

       Preconditions

       Postconditions

       Extension Points

       Other

       . . . . . . . . . ( end of section Usecase Name) <<Contents | End>>

       . . . . . . . . . ( end of section Appendix: Use-Case Specifications) <<Contents | End>>

       . . . . . . . . . ( end of section SRS from LeffinghamWidrig00) <<Contents | End>>

       Isidore -- Protector of Computers

       St. Isidore, Bishop of Seville, protector of computers. 556 AD.

       Structure of IEEE Experimental Paper

       1. Title + Abstract
       2. Introduction
       3. Things tested
       4. Emprical study
          
          1. Research Questions
          2. Experimental Design
          3. Subjects
          4. Effectiveness measures
          5. Tools
          6. Experiments and discussion
          7. Threats to validity
          
          Related Work
       5. Conclusions and Future Work
       6. Appendix
       7. Acknowledgments
       8. References
       9. Authors

       How to study

       1. Prep
       2. select time><gestalt
       3. map your knowledge
       4. note your questions

       5. Apply
       6. overview: contents, conclusions, summaries, figures. . .
       7. preview: start+end of each part
       8. inview: note memorable+difficult
       9. review: fill in, notes

       10. Follow up
       11. act on information
       12. review after: 1 day; 1 week; 1 month; yearly

       . . . . . . . . . ( end of section How to study) <<Contents | End>>

       SWEBOK areas & related disciplines

       1. - Software Requirements
       2. - Software Design
       3. - Software Construction
       4. - Software Testing
       5. - Software Maintenance
       6. - Software Configuration Management
       7. - Software Engineering Management
       8. - Software Engineering Methods and Tools
       9. - Software Engineering Process
       10. - Software Quality --------- (cognitive science and human factors, computer engineering, computer science, management and management science, mathematics, project management, systems engineering).

       . . . . . . . . . ( end of section SWEBOK areas & related disciplines) <<Contents | End>>

       sysML SML for system engineering

       Talks

       1. problem: what,why,how
       2. if complex then particular, general, particular
       3. analyse pieces
       4. provide practice
       5. give some paper to all
       6. show up early and finish early

       . . . . . . . . . ( end of section Talks) <<Contents | End>>

       Thats funny

       Date: Sat, 17 Jul 1999 15:17:15 GMT From: Jim Thompson <jim.thompson@pobox.com> Subject: Re: Cancelling errors, serendipity in avoiding risks, and Kepler

       In reading Henry Baker's thoughtful article, I am strongly reminded of something the late Isaac Asimov once said:

   92. The most exciting phrase to hear in science, the one that heralds new discoveries, is not "Eureka!" (I found it!) but "That's funny..."

       Asimov's point is similar to Baker's: that discovery is more driven by the desire to understand mistakes, discrepancies, and other "funnies" than by pure intellectual will.

       Jim Thompson <jim.thompson@pobox.com>

       Christiansen Inventors dilema

       The Innovators Dilemma: when new technologies cause great firms to fail.
   93. Doing the right things(research, listening to customers, finding improvements and profits ) helps an organisation FAIL to develop NEW markets/values that ultimately eclipse the old ones.
   94. Disruptive technology re-creates the market with new values and metrics but initially shows lower profits, performance, and a smaller market.
   95. Disruptive tech discovers new customers that fit the new tech.
   96. Disruptive is downmarket: less performance at a lower price, higher convenience, and/or higher reliabillity.
   97. Survival: create small separated suborganisation with room to fail and learn. Don't ask the customer; watch them. K.I.S.S. !

       Clayton M Christensen

   98. Harvard Business School Press 1997 ISBN 0-87584-585-1 HD53.C49

       also in Jared Diamond I

       Theology church history heresy

       1. -37 herod the great
       2. Judaic
       3. Saducees. Sanhedrin. aristocratic collaborators
       4. Essenes. Ultra pure. Temple of people not place
       5. Pharisees. Lawyers.
       6. Diaspora
       7. The poor
       8. 0-30 Christ
       9. Christian churches - no calm period. 34 first tradi§s. Conver§ o Paul?
       10. 50s Paul vs Jerusalemites -> zealots -> Ebionites
       11. first epistles
       12. Many gnostics(dualistic +secret knowledge) emerge. - ophite, samaratines, basilides, docetists deny incarna§
       13. - many reject old testament
       14. - nicolaitans(rev ch2)
       15. 66-70 Gospel of mark redacted
       16. -68 st linus 2nd bishop of rome
       17. 70 Gospels of luke & mathew + acts redacted
       18. 88-97 Clement I bishop of rome
       19. 95~ Revelations+gospel+letters of john
       20. 100..140 Marcion rationalises away most of old & new testament. Sex is bad! old testament demiurge. Dualist (Pel)
       21. opposed by Tertullian (Gus)
       22. organised Priesthood vs inspired prophets.
       23. 100 Basic eucharist in use.
       24. 160 monuments of martydom of st peter and paul in Rome.
       25. 170 Montanists, accused of behav/ like a church. "broke marriages to make women priests". opposed by Tertullian, who then joins them.
       26. 200s Earliest gnostic gospels.
       27. 200s bishop of rome := pope.
       28. Ireneus vs Valentinus Gnostic (sophia->demiurge). Dualism.
       29. Origen exegesis -> philosophy -> church as sacred society, clergy better than laity even if bad men.
       30. Cyprian adds episcopal power. Hierarchy necessary for people's salvation.
       31. neo-platonists.
       32. Rise of Rome as prime bishopric.
       33. 270-340 Eusebius
       34. Penance develops & is debated
       35. 313 Constantine & Licinius - edict of Milan..toleration.
       36. 311-347 Caecilian vs Donatus. Donatists: Zealots. Orders subvert\ by unworthiness. Carthage vs rest. Poor vs rich.
       37. 320s Arians: Christology.
       38. 325 Nicean creed
       39. 300-373 Athanasius
       40. 360? Mani. Montanism+eastern. Dualism and pessimism. Manicheaism. Secretive.
       41. 350 church becoming rich. Schola Cantorum
       42. 350-430 Augustine. Pessimist.
       43. Pelagius. Optimist.
       44. 367 canonical books fixed.
       45. 386 Hymns Ambrose
       46. 390 orthodox=imperial. With 156 distinct heresies + oo enthusiasts in opposition.
       47. 405 Vulgate of Jerome
       48. 400s Mass translat\ & becomes more ceremonial & formalized
       49. 411 Carthage. donatists.
       50. 428... Nestorius vs "theotokos" 450 alternate sing§
       51. 451 council of Chalcedon vs arian(from 320)
       52. several monophysite churches: Coptic, Armenian, ....
       53. Mob theology & Monks

       54. Catholic West vs Orthodox East. "Filioque".
       55. 500 incense

       Timezones time zones

   99. 0. Pacific CA NV OR WA. CA summer longer.
   100. AR with no DST. Mountain in Winter and Pacific in Summer +1 Mountain NM UT DenverCO
   101. Navajo matches NM, Hopi AZ +2. Central TX OK MO AL? MN +3. Eastern FL MA NY +4. Atlantic +8. London GB UK

        UP

   102. unified_process::= inception; elaboration; construction; transition.

   103. inception::= do(iteration(0)).
   104. elaboration::= do(iteration(1)).
   105. construction::= do(iteration(2)).
   106. transition::= do(iteration(3)).

   107. iteration(w)::= usecase -> requirements(w)-> analysis(w) -> design(w) -> implementation(w) -> test(w).
        Table

        w	r	a	d	i	t
        0	l;h	l	l	l	0
        1	h	h	h	l;h	l
        2	l	l	h	h	l
        3	0	l	l	l	h;l

        
        (Close Table)
        

        Wedding anniversaries

        silver 25 pearl 30 coral ?5 ruby 40 saphire 45 gold 50 emerald 75 diamond 100+

        Writing is learning iterative multithreaded

        1. writing::process= develop; #(review;undo & redo).
        2. develop::=( refine_outline | chaos...theme ).
        3. refine_outline::= #questions; add_answers; structure.

        4. review::= Someone who doesn't know | wait.... | Use software

   . . . . . . . . . ( end of section My Random Reference Memoranda) <<Contents | End>>