- Home Page
- Education
- Music
- SW Engineering
- PGP Public Key
- Self-Revealing Software
System self-explanation is critical for the construction, utility, acceptance, and maintenance
of complex, knowledge-based software. This paper presents a new methodology and implementation
techniques that enable software systems to explain their knowledge and reasoning, i.e., to
become "self-revealing." The theory addresses the spectrum of explanation goals and is
applicable to complex and unstructured domains and to general control structures.
The method, called REVEAL, represents the culmination of research and experimentation with new
explanation techniques conducted as part of the development of a legal expert system,
SAL (System for Asbestos Litigation). SAL adheres to the design philosophy of REVEAL and utilizes
many of the associated techniques. Throughout the paper, the theoretical concepts are demonstrated
by examples of their implementation in SAL.
Software Engineering
The Profession, Ethics, Risks, Perceptions
- Software Engineering Code of Ethics and Professional Conduct
- IEEE Code of Ethics
- ACM Code of Ethics and Professional Conduct
- Pledge of the Computing Professional
- Ten Commandments of Computer Ethics
- Computer Ethics Institute
- Electronic Frontier Foundation
- Ethics in Computing
- Electronic Privacy Information Center
- Privacy Rights Clearinghouse
- Computer Professionals for Social Resposibility
- The Markkula Center for Applied Ethics
- Risks Digest
- Ethical Implications of Privacy in Electronic Mail
- Rights and Responsibilities of Participants in Networked Communities
- Code Making: How Software Engineering Became a Profession [Davis] (PDF Book)
- Using the Software Engineering Code of Ethics [Gotterbarn]
- Using the ACM Code of Ethics [Anderson]
- ACM Self-Assessment XXII [CACM]
- Case 109: Why Software Quality Matters [Gage]
- Facts and Fallacies of Software Engineering [Glass]
- The Mythical Man Month [Brooks]
Software Development Lifecycle Models
Primary functions of a software process model
- Determine the order of activities involved in software
development and evolution
What shall we do next? - Establish the transition criteria for progressing from
one stage to the next
When shall we move on to the next activity?
Why are software process models useful?
- They provide guidance on what a software development project should do at any given time.
Spiral (Model Generator)
- Spiral Model
- WinWin Spiral Model
Using the WinWin Spiral Model: A Case Study [Boehm]
Spiral Development: Experience, Principles, and Refinements [Boehm] - Incremental Commitment Spiral Model (ICSM)
Presentation Slides & Video [Boehm 2013]
Agile
- Agile Software Development: A gentle introduction
- Agile Manifesto
- Agile Software Development [Fowler]
- A Road Map to Agile Documentation [Gonçalves]
- Articles (2006)
- eXtreme Programming
Scrum
- The Scrum Guide [Schwaber & Sutherland] (mirror)
- Scrum.org
- ScrumAlliance.org
Rational Unified Process (RUP)
- Rational Unified Process Overview [Rational]
- Rational Unified Process (Products) [IBM]
- Vision Document
- RUP Vision Document Template (Apple Pages)
- RUP Vision Document Template (Microsoft Word)
Waterfall
Software Quality
Validation
- Establishing the fitness or worth of a product for its intended mission
- valere = to be worth
- “Are we building the correct product?”
Verification
- Establishing the truth of correspondence between a product and its specification
- veritas = truth
- “Are we building the product correctly?”
Quality Engineering Practices
- Structured Walkthroughs
- Test Review Guidelines [Osherove]
- Testing & Debugging Guidelines
- Unit Testing
- Design Quality Attributes [Microsoft]
Requirements Engineering
- Mastering the Requirements Process [Robertson]
- Requirements Engineering Terminology [Glinz] (mirror)
- Setting Context [systemsguild.com]
- Agile Requirements Modeling [Ambler]
- Scrum: Product Backlog [Mansour]
- User Story Tips: [Pool] [Pichler]
- Requirements Trawling [Robertson]
Software Architecture & Design
- Software Architecture and Design [Microsoft]
Design Guidance
- Hiding Assumptions / Parnas Partitioning
This technique represents an attempt to buy the maximum insurance against program change
with the minimum cost. - Cohesion
- Coupling
- Design Fundamentals [Microsoft]
Refactoring
People, Projects, and Management
- Peopleware: Productive Projects and Teams [DeMarco & Lister]
- Exploring Requirements: Quality Before Design [Gause & Weinberg]
- Waltzing With Bears: Waltzing With Bears: Managing Risk on Software Projects [DeMarco & Lister]
Meetings
- How to Make Meetings Work! [Doyle]
- Making Meetings Work
- How to Run a Meeting [Lopp]
- Patterns for Daily Stand-Up Meetings [Yip]
Teams
Projects
- Naming: Implications and Heuristic
- Risk Management
- Risk Management Review [SEI]
- Continuous Risk Management Guidebook [Dorofee]
- Review of Risk Management Techniques [Misra]
- Risk Management [SEI]
- Risk Management Guide [DoD]
- Function Point Analysis
- Function Point Users Group
- Fundamentals of FPA [Longstreet] (PDF mirror)
Software Development Tools
Software Configuration Management / Revision Control
- RCS (Revision Control System)
- CVS (Concurrent Versions System)
- Subversion (version control system)
subversion: an open source version control system.
- Git (version control system) git: an open source version control system
- Mercurial (source code management) Mercurial: a free, distributed source control management tool
- Fossil (distributed SCM) Fossil: an open-source, simple, highly-reliable, self-contained, distributed software configuration management system with built-in bug tracking, wiki and web interface
- darcs (source code management) darcs: an open source, cross-platform version control system with a focus on changes rather than snapshots
Build Management
Continuous Integration
Overview of Continuous Integration [Fowler]- CruiseControl CruiseControl: a continuous integration tool and an extensible framework for creating a custom continuous build process
- Jenkins Jenkins: monitors executions of repeated tasks, such as building a software project or jobs run by cron (previously: Hudson)