Showing posts with label iphone. Show all posts
Showing posts with label iphone. Show all posts

Mobile Computing Principles: Designing and Developing Mobile Applications with UML and XML Review

Mobile Computing Principles: Designing and Developing Mobile Applications with UML and XML
Average Reviews:

(More customer reviews)
Are you looking to buy Mobile Computing Principles: Designing and Developing Mobile Applications with UML and XML? Here is the right place to find the great deals. we can offer discounts of up to 90% on Mobile Computing Principles: Designing and Developing Mobile Applications with UML and XML. Check out the link below:

>> Click Here to See Compare Prices and Get the Best Offers

Mobile Computing Principles: Designing and Developing Mobile Applications with UML and XML ReviewPlease excuse English. This is a very good book for learning mobile applications in US and Europe. Also, a lot of good new things on UML and XML. But, I would have liked to see more on the Japanese Mobile development. I think this is good as a text book in class room or reference. I would like to have more introductions to UML than 1 chapter. The UML is more advanced in this book. Also lot of good location and voice informations.Mobile Computing Principles: Designing and Developing Mobile Applications with UML and XML OverviewWritten to address the technical concerns faced by mobile developers, this book explores the differences between mobile and stationary applications and the architectural and software development concepts needed to build mobile applications. Reza B'Far guides the developer through the development process, using UML from design to implementation. He focuses on general concepts, while using platforms as examples or as possible tools. After introducing UML, XML, and the derivative tools necessary for developing mobile software applications, B'Far demonstrates how to build user interfaces for mobile applications.

Want to learn more information about Mobile Computing Principles: Designing and Developing Mobile Applications with UML and XML?

>> Click Here to See All Customer Reviews & Ratings Now
Read More...

Just Enough Software Architecture: A Risk-Driven Approach Review

Just Enough Software Architecture: A Risk-Driven Approach
Average Reviews:

(More customer reviews)
Are you looking to buy Just Enough Software Architecture: A Risk-Driven Approach? Here is the right place to find the great deals. we can offer discounts of up to 90% on Just Enough Software Architecture: A Risk-Driven Approach. Check out the link below:

>> Click Here to See Compare Prices and Get the Best Offers

Just Enough Software Architecture: A Risk-Driven Approach ReviewThis a broad and deep book on all things software architecture except the architecting process (for process, one recommended read is "Process Software Architecting" by Eeles/Cripps). Several readerships will benefit from "Just Enough Software Architecture":
- As an experienced IT architect, I do not necessarily agree with everything in the book (this does not come as a surprise, as architects have opinions). That said, I certainly learned a lot that I can apply immediately on my projects and some of the more provocative statements challenge me to leave my comfort zone (or at least consider doing so).
- Junior architects can use the book both as a tutorial and as a reference when/while growing in their profession.
- Developers with a "who needs architects" mindset (hopefully) will understand architects and modelers much better after having read this book, and appreciate the value of archtecture.
Things I liked in particular:
- Overall vision and message of pragmatism sent
- The risk-driven approach increases chances to get accepted both in agile development and in more traditional architecture communities
- There is a lot of practical advice e.g. in Chapters 10, 11 and 15
- The author is in command of a large body of relevant related work (both industra and academia) and puts them in perspective adequately
- Editorial quality: structure, figures, command of the English language (some words and expressions a bit be hard to comprehend for non-native speaker)
Some room for improvements (2nd edition?):
- Not all metaphors and analogies work internationally, e.g. not all IT people are sports fans that follow baseball or know what a rookie is
- The connection between parts 1 and 2 could be a bit stronger, even if loose coupling generally is a good thing; e.g., some more backward references
In summary, I'd say Just Enough Software Architecture is a highly recommended read for every architect in touch with development reality and every developer with a desire to build complex systems that will stand the test of time.Just Enough Software Architecture: A Risk-Driven Approach OverviewThis is a practical guide for software developers, and different than other software architecture books. Here's why:
It teaches risk-driven architecting. There is no need for meticulous designs when risks are small, nor any excuse for sloppy designs when risks threaten your success. This book describes a way to do just enough architecture. It avoids the one-size-fits-all process tar pit with advice on how to tune your design effort based on the risks you face.
It democratizes architecture. This book seeks to make architecture relevant to all software developers. Developers need to understand how to use constraints as guiderails that ensure desired outcomes, and how seemingly small changes can affect a system's properties.
It cultivates declarative knowledge. There is a difference between being able to hit a ball and knowing why you are able to hit it, what psychologists refer to as procedural knowledge versus declarative knowledge. This book will make you more aware of what you have been doing and provide names for the concepts.
It emphasizes the engineering. This book focuses on the technical parts of software development and what developers do to ensure the system works not job titles or processes. It shows you how to build models and analyze architectures so that you can make principled design tradeoffs. It describes the techniques software designers use to reason about medium to large sized problems and points out where you can learn specialized techniques in more detail.
It provides practical advice. Software design decisions influence the architecture and vice versa. The approach in this book embraces drill-down/pop-up behavior by describing models that have various levels of abstraction, from architecture to data structure design.

Want to learn more information about Just Enough Software Architecture: A Risk-Driven Approach?

>> Click Here to See All Customer Reviews & Ratings Now
Read More...