Software Development's Evolution towards Product Design

An anonymous reader writes: "The Lost Garden site has an excellent post on software development's evolution into product design. He starts with the first attempts at software design (for yourself or a colleague), and brings the conversation forward to modern design settings." From the article: "At the dawn of software history, programmers wrote software for other programmers. This was a golden era. Life was so simple. The programmers understood their own technical needs quite intimately and were able to produce software that served those needs. The act of software development was a closed circuit. A programmer could sit in a corner and write code that he wanted. By default it also happened to apply to other programmers."

Comments

Re:Software design

[Anonymous Coward]

You're so funny how you worked "intelligent design" into your post so many times! It's classic! LOL. I'm dying here - OF LAUGHTER. Seriously, have you considered comedy as a living? 'Cause your materiel is sheer gold baby. You can take that to the bank!

MDA

[Anonymous Coward]

Executable UML

Executable UML is a major innovation in the field of software development. It is designed to produce a comprehensive and understandable model of a solution independent of the organization of the software implementation. It is a highly abstract thinking tool that aids in the formalization of knowledge, and is also a way of describing the concepts that make up abstract solutions to software development problems.

This timely new book, Executable UML: A Foundation for Model-Driven Architecture, thoroughly introduces, documents, and explains this important new technology. The authors show how UML can formalize requirements and use cases into a rich set of verifiable diagrams, how it can be used to produce executable and testable models, and how these models can be translated directly into code. In addition, the book explains how individual system domains are woven together by an executable UML model compiler.

The book is full of tips and techniques to help you:

        * Partition a system into subject matters based on individual aspects
        * Pick the right level for use case modeling to speed subject matter comprehension
        * Model classes and focus on relationships to capture subject matter semantics precisely
        * Express behavior using the newly adopted UML action semantics and action languages
        * Specify constraints using tags specified in OCL (Object Constraint Language)

In addition, this book tackles topics of particular importance in execution, such as how to:

        * Synchronize objects by building lifecycles using statechart diagrams
        * Model relationships and contention safely
        * Distribute dynamics to avoid unmaintainable controller objects
        * Verify the models by executing test cases against the statechart diagrams and constraints

A large-scale, fully developed case study runs throughout the book to illustrate concepts and techniques.

What is an item about software development...

[Anonymous Coward]

doing on Slashdot?

I'm modding this whole darned topic off-topic.

Re:Software design

[Anonymous Coward]

Sometimes I put my hand down the back of my pants, and pass wind directly on my bare hand. So I can feel the wind. Then I raise my hand to my nose, and sniff it. I deeply inhale. And the bouquet of the fermented feces in my bowel awakens my creativity. I am being 100% serious. I am posting ac because i know that some people won't appreciate my methods.

Re:Software design

[Anonymous Coward]

Yeah, I smell my hand after I scratch my balls. I don't know if it affects my creativity though...

You Have No Rights or Constitution: +1, Helpful

[Anonymous Coward]

in the United Gulags of America.

Defend America: Detain The White House !!!

Patriotically,
Kilgore Trout, C.E.O.