Part 1 The Martian Principles.
Principle 1 Don't reinvent the wheel.
Principle 2 You won't do better than what's already been done.
Principle 3 Your customers don't know what they want.
Principle 4 Get something working as soon as possible.
Principle 5 Use sound software engineering practices.
Principle 6 Don't trust the client applications.
Principle 7 Plan to make changes.
Principle 8 You can't predict the future.
Principle 9 Don't tie your services into knots.
Principle 10 Build early, build often!
Principle 11 "What middleware?" should be your greatest compliment.
Principle 12 Expose the invisible.
Principle 13 Log everything.
Principle 14 Know the data.
Principle 15 Know when it will break.
Principle 16 Don't fail due to unexpected success.
Part 2 Project Management and Software Engineering.
Principle 17 Strong leadership drives a project to success.
Principle 18 Don't ignore people issues.
Principle 19 Software engineering is all about the D's.
Principle 20 The formulas for success aren't complicated.
The Martian Principles for Successful Enterprise Systems: 20 Lessons Learned from NASA's Mars Exploration Rover Mission
20 Lessons Learned from NASA's Mars Exploration Rover Mission
Buch (Taschenbuch, Englisch)
Fr.43.90inkl. gesetzl. MwSt.
When you need to land and operate a robot on Mars, "halfway" software is not an option. While helping to develop the Collaborative Information Portal, or CIP, for NASA's Mars Exploration Rover mission, Ronald Mak identified and refined a set of principles that represent the fundamental goals necessary for any successful enterprise system. Following them, Mak's team developed a CIP that scientists, researchers, and engineers have been using continually for over two years to access data from two Martian rovers. Its uptime record-99.9%.
The principles are language and platform independent. They're not design patterns or code samples. They're not even rocket science. They just work.
Real-world examples from the Rover mission help you learn to:
* Take advantage of what others have learned from their mistakes
* Realize that clients may not know how to know what they want
* Acknowledge that you aren't clairvoyant
* Think like a user
* Test, anticipate, be flexible, and keep it simple
* Recognize that code integration is a greater challenge than code development
* Become the successful architect of a successful system
VerlagJohn Wiley & Sons
Verfassen Sie die erste Bewertung zu diesem Artikel
Helfen Sie anderen Kund*innen durch Ihre MeinungErste Bewertung verfassen