WangenheimAnacletoSalviano06

1. Christiane Gresse von Wangenheim & Alessandra Anacleto & Clenio F Salviano
2. Helping Small Companies Assess Software Processes
3. IEEE Software Magazine V23n1(Jan/Feb 2006)pp91-98
4. =EXPERIENCE MARES ISO/IEC 15504 CMM/CMMI ISO 9001 BRASIL
5. MARES::=a prize winning process assessment process for small companies.
6. Sidebars describe ISO/IEC 15504.

Gotel06

1. Olly Gotel
2. In Search of the System Concept
3. IEEE Software Magazine V23n1(Jan/Feb 2006)pp102-103
4. =ADVERT REQUIREMENTS CONCEPT
5. The systems concept is a short vision statement.
6. It can be as short as a tag line or motto.
7. They have many uses and many advantages.

PelzAnrews66

1. Donald C Pelz & Frank M Andrews
2. Scientists in Organizations: productive climates for research and development
3. John Wiley and Sons (1966) LC card#66-26756
4. =POLL PEOPLE P MANAGEMENT PAPERS PATENTS SCIENTISTS ENGINEERS
5. An overwhelming study of what makes scientists and engineers more productive.
6. Some coordination and some freedom is best.
7. Contact with colleagues helps.
8. Involvement and self-reliance is good.
9. Creativity doesn't help in tightly managed situations.
10. Groups tend to decline.
11. Autonomy and loose coordination is not good.

Cervanto00

1. Iliano Cervanto
2. Logical Framework: Why not just classical logic?
3. CSLI Lecture notes V91, Stanford U(2000)pp87-104 in "Formalizing the dynamics of information" ed. Martina Faller & Stefan C Kaufmann & Marc Pauly ISBN 1-57586-239-5 Q360
4. =ESSAY LOGIC LAMBDA cf Z SCHEMA
   
5. (dick) |- Parallels my thinking in creating MATHS.

BaniassadEtal06

1. Elisa Baniassad & Paul C Clements & Joao Araujo & Ana Moreira & Awais Rashid & Bedir Tekinerdogan
2. Discovering Early Aspect
3. IEEE Software Magazine V23n1(Jan/Feb 2006)pp61-70
4. =IDEA ASPECTS REQUIREMENTS ARCHITECTURE
5. See [ http://www.early-aspects.net ]
6. An aspect is a property that cuts across the dominant decomposition.
7. In requirements, aspects constrain many scenarios.
8. In architecture, aspects cut across many views.

GriswoldEtal06

1. William G Griswold & Macneil Shonle & Kevin Sullivan & Yuanyuan Song & Nishit Tewari & Yuanfang Cai & Hridesh Rajan
2. Modular Software Design with Crosscutting Interfaces
3. IEEE Software Magazine V23n1(Jan/Feb 2006)pp51- 60
4. =CASESTUDY ASPECTS INTERFACES CONTRACTS AspectJ
5. Claims that defining interfaces for aspects: what the provide and what they require, makes the design clearer and simpler.

Lesiecki06

1. Nicholas Lesiecki
2. Applying AspectJ to J2EE Application Development
3. IEEE Software Magazine V23n1(Jan/Feb 2006)pp24-32
4. =EXPERIENCE ASPECTS GOOGLE AOP AspectJ
5. In [MurphySchwanninger06]

MurphySchwanninger06

1. Gail Murphy & Christa Schwanninger
2. Aspect-oriented programming
3. IEEE Software Magazine V23n1(Jan/Feb 2006)pp20-23
4. =EXAMPLE ASPECTS AOP weaving
5. Introduces section with good examples, adverts, & discussion of AOP pp24-75

Wirfs-Brock06

1. Rebecca J Wirfs-Brock
2. Looking for Powerful abstractions
3. IEEE Software Magazine V23n1(Jan/Feb 2006)pp13-15
4. =ESSAY Object-Oriented TECHNICAL DESIGN > REALITIES
5. You need more than domain objects in a design.
6. The classes in a design should often ignore(abstract from) domain classification when the (internal) behavior is the same.

Harrison06

1. Warren Harrison
2. Content Mismanagement systems
3. IEEE Software Magazine V23n1(Jan/Feb 2006)pp5-8
4. =ESSAY REQUIREMENTS QUALITIES vs TECHNICAL CMSs URLs
5. Example of a technical constraint leading to a reduction in a quality.
6. CMS systems place database paths and keys into URLs making them long and incomprehensible -- unmailable.
7. Solutions? tinyurl.com, www.digbig.com, shorl.com, snipurl.com.