>> [Comp Sci Dept]
>> [R J Botting]
>> [New Bibliographic Items]
|| [Site Search]
|| [Bibliography Search]
Fri Dec 9 09:46:14 PST 2005
- Richard Botting
- Small Errors in "Toward formalizing domain modeling semantics in language syntax"
- IEEE Trans Software Engineering V31n10(Oct 2005)pp911
- =Correction Statecharts fork vs decision
- Peter Schuh
- Integrating agile development in the real world
- Charles river media 2005 ISBN1-58450-364-5 QA76.76
- =HOWTO agile
- David Wile
- Lessons learned from real DSL experiments
- Science of Computer Programming V51n3(Jun 2004)pp265-290 CR 0511-1252
- =UNREAD 3 EXPERIENCES DOMAIN LANGUAGES
- None went into use for the usual nontechnical reasons that software fails.
- Bill C Hardgrave & Deborah J Armstrong
- Software Process Improvement: It's a Journey, not a Destination
- Commun ACM V48n11(Nov 2005)pp93-96
- =EXPERIENCE IMPROVEMENT vs CMM
- It took 4 years to move from CMM Level 1 to level 2.
- In the process installed a common methodology throughout the organization.
- Measurable improvements:customer satisfaction, schedule deviations, budget deviations.
- Need management guidance and support from start to finish.
- Engage the members.
- Use well-respected team members to lead the process.
- MEASURE from day 1
- SPI is a project and needs resources.
- Focus on continuous improvement rather than meeting the next level by a given deadline.
- Fit the improvement to the organization.
- Radha Mookerjee
- Maintaining Enterprise Software Applications
- Commun ACM V48n11(Nov 2005)pp75-79
- =THEORY evolution maintenance multiple applications SYSTEMS COSTS
- Argues that it pays to schedule joint maintenance when fixed costs are high, applications are coupled, and the rate of change is low.
- Recommends separating implementation from interface and the use of wrappers, hubs, and web services.
- Organization: recommends separating development from maintenance,
- Benjamin A Kuperman & Carla E Brodley & Hilmi Ozdoganoglu & T N Viyakuma & AnkitJalote
- Detection and prevention of stack buffer overflow attacks
- Commun ACM V48n11(Nov 2005)pp51-56
- =REPORT TECHNICAL RISK ERROR STACK CODE V&V TOOLS
- Concludes that training and review is one of the more effective techniques for getting rid of code that can be exploited. Bit code review is not perfect.
- There are tools to spot potential security violations: ITS4, RATS, LCLint.
- Dynamic protection (eg modify compiler to do bounds checking) can be costly but hardware may evolve to spot attacks fast.
- Peter Kugel
- It's time to think outside the computational box
- Commun ACM V48n11(Nov 2005)pp33-37
- =ESSAY PROGRAMMING BY EXAMPLE COMPUTE IN THE LIMIT
- Allowing programs to be wrong a finite number of times before being correct allows them to (in the limit) produce the program that fits all the given examples.
- (dick): most software development works like this anyway: testing, beta, alpha, ...
- Denis L Baggi
- An IEEE Standard for Symbolic Music
- IEEE Computer Magazine V38n11(Nov 2005)pp100-102
- =REPORT MUSIC STANDARD P1599 XML MEI RM0
- P1599::= See http://www.computer.org/portal/pages/ieeecs/communities/standards/1599/par.html
- MusicXML::= See http://www.recordare.com/xml.html
- Mike Cohn
- User Stories Applied: for agile software development
- Addison-Wesley 2004 ISBN 0-321-20568-5
- =UNREAD USER REQUIREMENTS AGILE XP
- Brian Donnellan & Brian Fitzgerald & Brian Lake & John Sturdy
- Implementing an Open Source Knowledge Base
- IEEE Software Magazine V22n5(Nov/Dec 2005)pp92-95
- =COMPARISON TOOLS KB OPEN SOURCE COSPA MetaData DSpace LAMP Data Centric KMS Lotus Notes
- KB::="Knowledge Base", part of an expert system, the body of knowledge available for the inference engine to use.
- Dublin_Core::standard= See http://dublincore.org.
(Open archives initiative Protocol for Metadata Harvesting): framework
[ http://www.openarchives.org ]
- Only works well when it evolves with the needs of the users.
- Lars Mathiassen & Ojelanki K Ngwenyama & Ivan Aaen
- Managing Change in process improvement
- IEEE Software Magazine V22n5(Nov/Dec 2005)pp84- 91
- =CASE STUDY 4 DANISH COMPANIES VARIED SPI IMPROVEMENT
- All had limited success: software process was improved,none achieved as much as they wanted initially.
- SPI is organizational change.
- (above) |- need to use change management techniques.
- Understand context: source, organization structure,existing processes and needs.
- Create (and communicate) vision
- Manage commitment
- Stay agile
- Monitor improvement
- One size does not fit all. For example,
- maintenance does not follow a development process.
- Small and simple projects do not need all the procedures and data recording of a complex or large project.
- In all 4 projects nobody expected that management would have to change!
- Hakan Erdogmus
- The Economic Impact of learning and flexibility on Process decisions
- IEEE Software Magazine V22n5(Nov/Dec 2005)pp76-83
- =ESSAY MATH ONE SIZE Economics PROCESS ITERATIVE vs SEQUENTIAL COST-BENEFIT
- Calculated values of projects.
- Iteration & learning can make a project profitable in an uncertain situation.
- Kathleen Coleman Dangle & Patricia Larsen & Michele Shaw & Marvin V Zelkowitz
- Software Process Improvement in Small Organizations: A Case Study
- IEEE Software Magazine V22n5(Nov/Dec 2005)pp68-75
- =CASE STUDY DSCS CMM
- (dick) |- when does software process improvement merge into business process reengineering?
- (dick) |- Rediscovers some trad systems analysis and design ideas.
- Processes and process improvement should address business goals not just CMM dogma,
- Choose the sequence of improvements to support needs not CMM KPAs.
- TANSTAAFL: Improvement needs resources.
- Test proposed improvements on selected projects and change them before expanding enterprise-wide.
- Ongoing activities should drive the plans for introducing new processes.
- Start formal reviews immediately to provide feedback to stakeholders.
- Divide improvements up and delegate.
- Assess experience with software processes and SP improvement.
- David P Darcy & Chris F Kemerer
- OO metrics in Practice
- IEEE Software Magazine V22n5(Nov/Dec 2005)pp17-19
- =ADVERT =SURVEY CK METRICS Object-Oriented
- Jeremy Dick
- Design traceability
- IEEE Software Magazine V22n5(Nov/Dec 2005)pp14-16
- =ESSAY traceability REQUIREMENTS DESIGN
- Value in knowing why something is needed or how a need is met.
- Defines implicit traceability and rich traceability.
- Review. Sufficient design? Necessary design?