The Martian Principles for Successful Enterprise Systems: 20 Lessons Learned from NASAs Mars Exploration Rover Mission

Overview

  • For the first time ever, the senior architect and lead developer for a key enterprise system on NASA's ongoing Mars Exploration Rover mission shares the secrets to one of the most difficult technology tasks of all-successful software development
  • Written in a conversational, brief, and to-the-point style, this book presents principles learned from the Mars Rover project that will help ensure the success of software developed for any enterprise ...
See more details below
Available through our Marketplace sellers.
Other sellers (Paperback)
  • All (11) from $1.99   
  • New (3) from $50.00   
  • Used (8) from $1.99   
Close
Sort by
Page 1 of 1
Showing All
Note: Marketplace items are not eligible for any BN.com coupons and promotions
$50.00
Seller since 2015

Feedback rating:

(228)

Condition:

New — never opened or used in original packaging.

Like New — packaging may have been opened. A "Like New" item is suitable to give as a gift.

Very Good — may have minor signs of wear on packaging but item works perfectly and has no damage.

Good — item is in good condition but packaging may have signs of shelf wear/aging or torn packaging. All specific defects should be noted in the Comments section associated with each item.

Acceptable — item is in working order but may show signs of wear such as scratches or torn packaging. All specific defects should be noted in the Comments section associated with each item.

Used — An item that has been opened and may show signs of wear. All specific defects should be noted in the Comments section associated with each item.

Refurbished — A used item that has been renewed or updated and verified to be in proper working condition. Not necessarily completed by the original manufacturer.

New
Brand new.

Ships from: acton, MA

Usually ships in 1-2 business days

  • Standard, 48 States
  • Standard (AK, HI)
$50.00
Seller since 2015

Feedback rating:

(228)

Condition: New
Brand new.

Ships from: acton, MA

Usually ships in 1-2 business days

  • Standard, 48 States
  • Standard (AK, HI)
$86.18
Seller since 2008

Feedback rating:

(210)

Condition: New

Ships from: Chicago, IL

Usually ships in 1-2 business days

  • Standard, 48 States
  • Standard (AK, HI)
Page 1 of 1
Showing All
Close
Sort by
Sending request ...

Overview

  • For the first time ever, the senior architect and lead developer for a key enterprise system on NASA's ongoing Mars Exploration Rover mission shares the secrets to one of the most difficult technology tasks of all-successful software development
  • Written in a conversational, brief, and to-the-point style, this book presents principles learned from the Mars Rover project that will help ensure the success of software developed for any enterprise system
  • Author Ronald Mak imparts anecdotes from his work on the Mars Rover and offers valuable lessons on software architecture, software engineering, design patterns, code development, and project management for any software, regardless of language or platform
Read More Show Less

Product Details

  • ISBN-13: 9780471789659
  • Publisher: Wiley
  • Publication date: 5/28/2006
  • Edition number: 1
  • Pages: 138
  • Product dimensions: 152.40 (w) x 228.60 (h) x 10.10 (d)

Meet the Author

Ronald Mak was a senior computer scientist and software architect at the NASA Ames Research Center. He was the architect and lead developer of the middleware for the Collaborative Information Portal, an important enterprise software system that is a part of NASA’s ongoing and highly successful Mars Exploration Rover mission. Mission managers, scientists, and engineers continue to use CIP—after over two years of continuous operation, it has an uptime record of better than 99.9 percent.
Working as a key member of the CIP development teamvalidated the principles that Ron describes in this book.Ron was also the architect and lead developer of an enterprise class information portal for NASA’s International Space Station and the future Crew Exploration Vehicle.
Prior to joining NASA, Ron had over 15 years of experience designing and developing enterprise systems using several programming languages and technologies on various platforms.
Most of these systems were highly successful, but therewere a few failures, too. The Martian principles are derivedfrom these experiences.
Ron held an academic appointment with the University of California at Santa Cruz, and he worked on contract to NASAAmes. He earned his B.S. degree with distinction in the Mathematical Sciences and his M.S. degree in Computer Science from Stanford University.
He has written three previous books on computer science, Java Number Cruncher, the Java Programmer’s Guide to Numerical Computing (Prentice Hall PTR, 2003), Writing Compilers and Interpreters, C++ Edition (Wiley, 1996), and Writing Compilers and Interpreters, a Practical Approach (Wiley, 1991). He recently wrote several papers about CIP for refereed journals. He continues to hone his exposition of the Martian principles by giving presentations to both industry and academic audiences.
Ron recently co-founded and is the CTO of Willard & Lowe Systems, Inc. (www.willardlowe.com) which develops enterprise systems for information management and collaboration.

Read More Show Less

Table of Contents

About the Author.

Preface.

Acknowledgments.

Introduction.

Part 1 The Martian Principles.

Principle 1 Don’t reinvent the wheel.

Someone Else Has Already Solved Your Problem.

Understand What Your Added Value Is.

Use Commercial Software Whenever Practicable.

Principle 2 You won’t do better than what’s already been done.

Adhere to Industry Standards and Best Practices.

Seek User Groups, Chat Forums, Online Documentation, Books, and the Like.

Do Not Gum Up the Plumbing.

Principle 3 Your customers don’t know what they want.

Do Not Push Too Hard on the Requirements.

Do Rapid Prototyping and Lots of User Testing.

Customers Are the Best Testers.

Principle 4 Get something working as soon as possible.

The First End-to-End Thread Is Critical.

Working Code Builds Confidence.

Always Build on Top of Working Code.

Principle 5 Use sound software engineering practices.

Use a Component-Based Architecture.

Use Design Patterns.

Get All the Development Team Members to Agree.

Principle 6 Don’t trust the client applications.

Be Very Paranoid—They Are Out to Get You.

If You Do Not Break It, They Will.

Principle 7 Plan to make changes.

Do Not Hard-Code Values.

Use External Editable Parameter Files.

Implement a “Read Parameters” Method.

Maintain Client Parameter Files Centrally on the Server.

Identify the Parameter Values.

Principle 8 You can’t predict the future.

Make Each Service Dynamically Reconfigurable.

Create Field-Replaceable, Plug-and-Play Services.

Hot Redeployment Allows Reconfiguring without Rebooting.

Make Each Service Loosely Coupled.

Take a Peek into the Future.

Principle 9 Don’t tie your services into knots.

Keep Your Services Independent of Each Other.

Services Should Treat Other Services As Equals.

Principle 10 Build early, build often!

The Major Challenge Is Not Code Development but Code Integration.

Use a Source Code Repository.

Maintain a Separate Environment in Which to Build and Deploy.

Principle 11 “What middleware?” should be your greatest compliment.

The Middleware Should Be Invisible to Users.

Good Middleware Creates Ideal Virtual Worlds for the End Users.

Principle 12 Expose the invisible.

Put Hooks in the Middleware.

Do Runtime, Real-Time Monitoring.

Principle 13 Log everything.

Do Not Turn Off Logging in Your Production Code.

“Log Mining” Reveals Usage Patterns.

Principle 14 Know the data.

Learn the Data Usage Patterns.

Create Appropriate Application and Middleware Data Models.

Map to Practical Physical Data Models.

Adapt to Third-Party and Legacy Data.

Principle 15 Know when it will break.

Do Lots of Stress Testing.

If You Do Not Find Out What the Limits Are, Your Users Surely Will.

Principle 16 Don’t fail due to unexpected success.

Missions May Last Longer Than Expected.

Data Repositories May Grow Larger Than Planned.

Part 2 Project Management and Software Engineering.

Principle 17 Strong leadership drives a project to success.

A Good Architect Must Also Be a Good Leader.

Any Architecture Is Only As Good As Its Implementation.

Strong Project Management Is Necessary for Success.

Project Milestones Are Opportunities for Demos and Rebalancing.

The Project Milestones Near the End Allow You to Get Your Project Done on Schedule.

Principle 18 Don’t ignore people issues.

Software Projects Are Not Democracies.

Agree to Disagree, but Then Move On.

Scale the Project According to the Team Members’ Abilities and Experience.

Do Not Be a Slave to the Latest Project Management Methodology.

Foster Good Communication Plus Teamwork, Teamwork, Teamwork.

Remove Team Members Who Cannot or Will Not Perform.

Principle 19 Software engineering is all about the D’s.

Discovery.

Diplomacy.

Definition.

Design.

Development.

Debugging.

Documentation.

Deployment.

Dmaintenance.

Principle 20 The formulas for success aren’t complicated.

Successful Architect = Good Designer + Good Developer + Good Leader.

Successful System = Good Architecture + Good Software Engineering.

Keep It Simple!

Index.

Read More Show Less

Customer Reviews

Be the first to write a review
( 0 )
Rating Distribution

5 Star

(0)

4 Star

(0)

3 Star

(0)

2 Star

(0)

1 Star

(0)

Your Rating:

Your Name: Create a Pen Name or

Barnes & Noble.com Review Rules

Our reader reviews allow you to share your comments on titles you liked, or didn't, with others. By submitting an online review, you are representing to Barnes & Noble.com that all information contained in your review is original and accurate in all respects, and that the submission of such content by you and the posting of such content by Barnes & Noble.com does not and will not violate the rights of any third party. Please follow the rules below to help ensure that your review can be posted.

Reviews by Our Customers Under the Age of 13

We highly value and respect everyone's opinion concerning the titles we offer. However, we cannot allow persons under the age of 13 to have accounts at BN.com or to post customer reviews. Please see our Terms of Use for more details.

What to exclude from your review:

Please do not write about reviews, commentary, or information posted on the product page. If you see any errors in the information on the product page, please send us an email.

Reviews should not contain any of the following:

  • - HTML tags, profanity, obscenities, vulgarities, or comments that defame anyone
  • - Time-sensitive information such as tour dates, signings, lectures, etc.
  • - Single-word reviews. Other people will read your review to discover why you liked or didn't like the title. Be descriptive.
  • - Comments focusing on the author or that may ruin the ending for others
  • - Phone numbers, addresses, URLs
  • - Pricing and availability information or alternative ordering information
  • - Advertisements or commercial solicitation

Reminder:

  • - By submitting a review, you grant to Barnes & Noble.com and its sublicensees the royalty-free, perpetual, irrevocable right and license to use the review in accordance with the Barnes & Noble.com Terms of Use.
  • - Barnes & Noble.com reserves the right not to post any review -- particularly those that do not follow the terms and conditions of these Rules. Barnes & Noble.com also reserves the right to remove any review at any time without notice.
  • - See Terms of Use for other conditions and disclaimers.
Search for Products You'd Like to Recommend

Recommend other products that relate to your review. Just search for them below and share!

Create a Pen Name

Your Pen Name is your unique identity on BN.com. It will appear on the reviews you write and other website activities. Your Pen Name cannot be edited, changed or deleted once submitted.

 
Your Pen Name can be any combination of alphanumeric characters (plus - and _), and must be at least two characters long.

Continue Anonymously

    If you find inappropriate content, please report it to Barnes & Noble
    Why is this product inappropriate?
    Comments (optional)