Watch, Follow, &
Connect with Us

Please visit our new home

You are not logged in

More information and actions might be available on this page for logged in users. Click here to log in.

Edit Author

Author Information
ID: 661
First name: Randy
Last name: Miller
User name: rmiller


Search articles
Enter an article ID or an ID range (e.g. "100-200").You can also enter a wildcard (e.g. "1000-*").

LanguageSiteIDTitleCreated onTypeVisibilityStatus   
ENEDN31900The Invisible Software Process: Preface12/31/2003ArticlePublicLive
ENEDN31881What's New in UML™ 2.0?, Part 112/18/2003ArticlePublicLive
ENEDN30386Agile Process Framework, Activity Note #39/24/2003ArticlePublicLive
ENEDN30385Service-Oriented Architecture Part 1: Identification9/24/2003ArticlePublicLive
ENEDN30169What's New in UML™ 2? Model Exceptions6/30/2003ArticlePublicLive
ENEDN30168What's New in UML 2? A Question of Profiles6/30/2003ArticlePublicLive
ENEDN30167Agile Process Framework, Activity Note #26/30/2003ArticlePublicLive
ENEDN30166What's New in UML 2? The Use Case Diagram6/30/2003ArticlePublicLive
ENEDN30165The Dynamics of Agile Software Processes, Part III: The Philosophy of Agile Teams6/30/2003ArticlePublicLive
ENEDN30158Business Rules6/30/2003ArticlePublicLive
ENEDN30036Welcome to The Agile Developer General5/14/2003ArticlePublicLive
ENEDN30033Welcome to The Agile Software Developer Activities5/14/2003ArticlePublicLive
ENEDN29961Config Files Explained4/21/2003ArticlePublicLive
ENEDN29960Together Modules Manifest HOWTO4/21/2003ArticlePublicLive
ENEDN29878The Dynamics of Agile Software Processes, Part II: Creating the Right-Weight Process3/28/2003ArticlePublicLive
ENEDN29874Agile Process Framework, Activity Note #13/28/2003ArticlePublicLive
ENEDN29765Coad Letter Subscribe2/10/2003ArticlePublicLive
ENEDN29726The Dynamics of Agile Software Processes, Part I: Characteristics2/5/2003ArticlePublicLive
ENEDN29712Becoming Agile2/4/2003ArticlePublicLive
ENEDN29711Welcome to the Agile Software Developer2/4/2003ArticlePublicLive

Publish Article Version

Publisher Tasks
Warning: Warranty agreement has not been received

The author of this article has not yet submitted a signed warranty agreement. A signed agreement must be received before publishing article of this type.

If you have received a signed warranty (via fax or mail), you can submit it on behalf of the author. You can also set the article type to one that does not require a warranty.

Setting the article type affects all versions and translations of the article.

Article Visibility

Staging Sites

Server Response from: ETNASC03