Enlaces

domingo, 6 de junio de 2010

Software Engineering

  • Center for Software Engineering: COCOMO-based tools for estimating
    the time and effort that large projects will require.
  • Estimate Professional : is a software project estimation tool from
    Starbase.
  • Ed Yourdon’s Home Page: Ed made rather a splash as one of the
    people publicly worried about the Y2K bug, but before and after
    that he’s been a steady practitioner of good software engineering.
    There are lots of good pointers to other sources here, and a great
    sense of humor.
  • Guide to the SWEBOK: SoftWare Engineering Body Of Knowledge. This
    is an IEEE project to codify what software professionals ought
    to know.
  • High-Level Best Practices in Software Configuration Management: one of
    a number of white papers on the Perforce web site. Perforce are
    also the makers of an excellent source code management system.
  • Joel On Software: Joel Spolsky has done software management at
    Microsoft and Juno. His essays on the software management process
    are well worth reading even if you don’t agree entirely with his
    management style (I don’t, but I still learn from them).
  • Patterns Home
    Page:     software patterns have had a big impact on the field
    of software engineering in recent years. The basic notion is to
    learn by abstracting the pattern of workable solutions. This page
    provides links to hundreds of resources, from tutorials to mailing
    lists to book reviews to online pattern repositories.
  • Refactoring Home Page: from Martin Fowler, who wrote the book on refactoring.
    Lots of good stuff here, including extra material and errata for
    the book, links to other sites and commercial tools, and a news
    section. Well worth a visit.
  • Scrum: is another methodology for hyper-rapid software development. Looks
    similar to Extreme Programming. Reading (and implementing) this
    sort of thing can be inspirational to organizations that are so
    mired in process that they can no longer get anything shipped.
  • SGI Software Usability II: a leaked 1993 memo from an engineer
    at Silicon Graphics, analyzing what went wrong with a large release.
    There are some lessons to be learned here about both writing software
    and managing the software process.
  • Software Engineering: a page of stories from Tom Van Vleck. These range
    from simple parables to technical journal articles about Multics,
    with which he was deeply involved. Most are short, and you can
    read an ponder one while you’re waiting for your next compile
    to complete.
  • Software Engineering Institute: located at Carnegie-Mellon, this is
    a federally-funded outfit that does research into serious management
    of serious software projects.
  • Software
    Engineering Laboratory:     this is a NASA effort that makes available
    fat PDF publications of what’s worked at Goddard Space Flight
    Center. They’re proponents of an extremely structured approach.
    Software engineering management.
  • Software Engineering Professionalism Website: another effort from Steve
    McConnell, this one complements his book After the Gold Rush.
    Links to much useful information on licensing, codes of ethics,
    reading lists, and other professional development topics.
  • Trends in Software Engineering Process Management

Programming

  • Agile Modeling Home Page: an extensive collection of material related to lightweight
    software modeling techniques.
  • Alistair Cockburn, Humans and Technology: website full of papers on object-oriented design
    and cooperative programming.
  • Big Ball of Mud: an essay that takes a look at some real-world software patterns and
    considers why so many projects end up taking the messy form of a big ball
    of mud, despite our best efforts to learn and apply solid software engineering
    principles. Includes some advice about salvaging projects that have reached
    this state.
  • The Case Against Extreme Programming: athoroughgoing attack on XP, together
    with rebuttal and discussion.
  • Catalog of Non-Software Examples of Design Patterns: if you have trouble understanding
    the abstract language sometimes used in describing software design patterns,
    take a look at this site.
  • Extreme Programming
  • Extreme Programming: A Gentle Introduction: covers the basics of XP.
  • Extreme Programming FAQ: the basics about XP, with pointers to further information.
    Good comparisons with other programming practices.
  • How to Write Unmaintainable Code: when you think all is lost and no one will
    ever write good software again, it’s time to go browse this site.
  • In Defense of Coding Standards: is an essay subtitled “How to Create
    Coding Standards That Work.” It argues for a minimalist approach that
    looks likely to succeed in bringing some form of (often much-needed) standardization
    to nearly any development organization.
  • An Introduction to Extreme Programming: on the O’Reilly Network, this article
    introduces the concepts of XP and considers possible synergies between XP
    and open source.
  • Literate Programming – Propaganda and Tools: literate programming is defined as
    the combination of documentation and source together in a fashion suited for
    reading by human beings.
  • Manifesto for Agile
    Software Development:     astatement of position from practitioners of a bunch
    of “lightweight” development practices such as XP and Scrum that
    picks out the common themes of responding quickly to change and valuing results
    over process.
  • Mob Software: The Erotic Life of Code: is a wandering essay arguing that we
    can get more and more interesting code by turning vast mobs of programmers
    loose on it.
  • Pairprogramming.com: a site devoted to research about and cheerleading for the practice of pair
    programming, where two developers work at the same time on the same source
    code. Several interesting articles here.
  • Process Builder
  • Process Impact: is a consulting house focused on “practical software process improvement”.
    Check out the Publication page, which includes a number of excellent articles
    on software culture, risk management, project management and related topics.
  • Software Program Managers Network: this is a group of software manager for the Department
    of Defense, very concerned with how to keep track of large, out-of-control
    projects.
  • Strengthening the Case for Pair Programming: apaper reporting on productivity and quality
    gains from the practice of having pairs of programmers working together. Includes
    some qualitative data.
  • XProgramming.Com: a new site for devotees of Extreme Programming.

    Graphic design

Credits: Mike Gunderloy

Comentarios cerrados.