[CSUSB] >> [CNS] >> [Comp Sci] >> [R J Botting] >> newb1125
[Index] || [Blog] || [Research] Tue Nov 25 16:43:24 PST 2003

McLaughlin03

Laurianne McLaughlin
Buggy Software: Can New Liability Rules Help Quality?
IEEE Software Magazine V20n5(Sep/Oct 2003)pp104-108
=ESSAY LEGAL QUALITIES DHS NIST UCITA
UCITA::="Uniform Compute Information Transactions Act", recommended to states but passed(2003) by only two: VI & MD, protects vendors from being sued if the software fails. Vendors can specify which state law will apply in their acceptance contract.
Kaner::= See http://www.badsoftware.com.
Trustworthy computing and MS windows server 2003. Security Engineering Strategy.
Sustainable_computing_consortium::= See http://www.sustainablecomuting.org. Don't count defects.... predict failure intensity.
Licensing? no real SWEBOK.
California law: "Security Breach Information Act" July 2003. Businesses must promptly notify customers when reasonable suspicion f unencrypted personally identifiable data is accesses in bad faith----civil damage$$$

DeMarcoLister03

Tom DeMarco & Tim Lister
Risk Management during Requirements
IEEE Software Magazine V20n5(Sep/Oct 2003)pp99-101
=EXPERIENCE RISKS REQUIREMENTS PEOPLE POLITICS
Continuous public identification of risks to a project.
examples: arbitrary schedule, stakeholder conflict, scope creep, personnel loss, productivity variation.
Assign ranks to all requirements and express all outcomes in probabilities. Show growth of probability of delivering requirement as a graph.
Risks of using vague requirements to hide non-agreement (non-concurrence)
Diagnose non-agreement/politics by precisely documenting data flows in and out of system.

Andy Hunt & Dave Thomas
Preparing the Raw Material
IEEE Software Magazine V20n5(Sep/Oct 2003)pp97-98
=ESSAY GOOD PEOPLE
Software development is a mental activity. We are the raw materials.
good people: pragmatic, take multiple views, take responsibility, communicate well, and learn.
(Confucius) |- "Hearken to [...] words and watch their deeds"

Ivan Aaen
Software Process Improvement: Blueprints versus Recipes
IEEE Software Magazine V20n5(Sep/Oct 2003)pp86-93
=ADVOCATES AGILE IMPROVEMENT SPI PEOPLE vs PROCEDURE
Lists the risks of having a separate SPI team working out a blueprint/structure/standards.
Promotes the facilitation of improvisation plus reflection within existing teams