1. Nelly Oudshoorn &Trevor Pinch (eds)
2. What
3. How Users Matter: The Co-Construction of Users and Technology
4. The MIT Press Boston MA 2003, reviewed by Ben Schneiderman American Scientist V92n5(Sep-Oct 2004)pp482-483
5. =UNREAD =IDEA SOCIOLOGY TECHNOLOGY USER
6. SCOT::acronym="Social Construction Of Technology".
7. Technology changes its users and users change the technology -- before it becomes theirs.
8. user actions: {domesticate, appropriate, incorporate, convert, reject, resists, exclude, expel}.

BoehmTurner03

1. Barry Boehm & Richard Turner
2. Balancing agility and Discipline: A guide for the perplexed
3. Addison-Wesley Longman Boston MA 2003 ISBN 0321186125
4. =UNREAD =SYNTHESIS AGILE ONESIZE CR 0410-1130
5. Notes

VolzerEtal04

1. Hagen Volzer & Anthony MacDonald & Brenton Atchison & Andrew Hanlon & Pete Lindsay & Paul Stroper
2. SubCM: A Tool for Improved Visibility of Software Change in an Industrial Setting
3. IEEE Trans Software Engineering V30n10(Sep 2004)pp678-693
4. =Experience SCADA Hierarchical Configuration management graphic tool SubCM
5. individual configuration items are parts of larger items. Version trees. Changes at bottom reflected at higher levels.

BrylowPalsberg04

1. Dennis Brylow & Jens Palsberg
2. Deadline Analysis of Interrupt-Driven Software
3. IEEE Trans Software Engineering V30n10(Sep 2004)pp634-655
4. =DEMO Formal TIMING Z86 Interrupt Handling TEST

YuSchachChenOffutt04

1. Liguo Yu & Stephen R Schach & Kai Chen & Jeff Offutt
2. Categorization of Common Coupling and its Application to the maintainability of the Linux Kernel
3. IEEE Trans Software Engineering V30n10(Sep 2004)pp694-706
4. =ANALYSIS Linux kernel coupling metrics
5. Common_coupling::= "Two or more modules refer to a common global variable", thought to make maintenance harder and less reliable.
6. Claims previous work on kernel showed linear growth in size of code and exponential growth in the number of common couplings.
7. Defines the direction of common coupling from definition (assigned a value) to usage.
8. Distinguishes modules in kernel with non-kernel OS modules (eg I/O).
9. Finds thousands of couplings.
10. 5 categories. Example: Category 1 is a global variable defined in kernel modules but not used in them.
11. Worst case? Fig 19. The variable current is changed 1.4K and use in 6.7K times in 1K non-kernel modules. It is used in 18 kernel modules and changed in 12 of these.
12. Provides no evidence that theoretically bad effects on maintenance have actually happened (yet).

SchneiderK04

1. Klaus Schneider
2. Verification of Reactive Systems: Formal Methods and Algorithms
3. Springer-Verlag London UK 2004 ISBN 3540002960 CR 0409-1013
4. =THEORY FORMAL V&V ALGORITHMS MODEL CHECKING Borel FIXPOINT AUTOMATA MODAL LOGIC

MillerR03

1. Roy Miller
2. Managing Software for Growth: without fear, control, and the manufacturing mindset
3. Addison-Wesley Longman, Boston MA 2003 ISBN 0321117433 CR 0409-1014
4. =UNREAD EVOLUTION ITERATION PROCESS AGILE COMPLEXITY
5. Software is not a product to be manufactured (predictable and repeated process and end point)

ObrenovicStarcevic04

1. Zeljko Obrenovic & Dusan Starcevic
2. Modeling multi-modal human-computer interaction
3. IEEE Computer Magazine V37n9(Sep 2004)pp65-72
4. =IDEA MODEL HCI UML

LippertAnandarajan04

1. Susan K Lippert & Murugan Anandarajan
2. Academic vs. practitioner systems planning and analysis
3. Commun ACM V47n9(Sep 2004)pp91-94
4. =SURVEY INFORMATION SYSTEMS RESEARCH
5. Studied samples abstracts from 13 journals 1970..1990 & 1991..2002 read?written by practitioners or academics.
6. Practitioners tended to research about needed skills(32/264), methods(116/264), and tools(53/264). Academics tended research about planning(123/269).
7. Both shifted toward methods(30->145) and tools(21->60) in the later period. Academics increased research on needed skills(9->18) and requirements(2->12) but practitioners did the reverse(28->4 and 3->1).
8. Claims the gaps are causing problems.

TuretkenSchuffShardaOw04

1. Ozgur Turetken & David Schuff & Ramesh Sharda & Terence T Ow
2. Supporting systems analysis and design through fish-eye views
3. Commun ACM V47n9(Sep 2004)pp72-77
4. =EXPERIMENT GRAPHIC DIAGRAMS LAYOUT DFDs ERDs
5. DOI::= degree of interest, determines size.
6. normal degree of interest:=original importance / distance from focus.
7. Embed focal diagram in its context.

8. for DFD, DOI = 1 - const*dL, dL=number of levels between focal diagram and element. Shaded context subjects did better with fish-eye.

9. ERD. Size lower for longer path lengths. (not tested).

Dumay04

1. Mark Dumay
2. Business Processes: the theoretical impact of process thinking on information development
3. arXive.org e-print archive Sun, 19 Sep 2004 09:56:24 GMT [ 0409037 ]

4. =ESSAY POSTMODERN SYSTEMS PEOPLE SOCIOLOGY BPR
5. Argues that BPR tend to fail because they expect & require people to fit the process.