Finance-Software

This book contains nothing valuable. The case studies in it are superficial and tells the readers nothing about what's actually going on behind the scene. For example, in the first case, there's an explanation about mapping between X12 837 to some other formats. The example shows a screenshot of a nice GUI that allows the user to map elements of X12 to some other format presumably by using XML mapping. But where does the screen gets its information from? This example doesn't tell us anything about how to come up with a good XML representation of the X12 837 spec. Which is the first thing that any "solutions" would have to start from. I guess it's because of the closed-source nature of everything that Microsoft is doing, that they are afraid of showing the actual processes that they went through. Furthermore, they are actually proud of a solution that employs 6 different servers? the licensing costs alone are enough to put most clearinghouses out of business. If you're looking for an insight on how to actually help someone with HIPAA compiance, don't count on this book to be anything but a waste of money and time.

How can someone write book about a solution to a national problem where all they are doing is promoting the WPC product lines and some shallow Microsoft explanation of a server that can be found for FREE from the Microsoft Website. I could not find this book in the store to check it out before buying so I had to buy it. Don't repeat my mistake. Look for a more objective view and solution elsewhere.
Is this ethical to charge money for this book??

I picked this book up not because of the Microsoft-specific solution, but for the HIPAA overview. Sounds like the other reviewers already had that, but for me this is the first place I've seen it all laid out.

As for it being Microsoft-specific, I just feel obligated to point out that this book documents a very specific solution that Microsoft put together with one of its partners. So, while the "comprehensive strategies" part of the title may be a misnomer, taken in context it's not a bad document. In Microsoft's document model this would be a Planning and Architecture document, aimed at the Business Decision Maker to give them an overview and get them interested in a particular architecture. (Disclaimer, I write these kinds of documents for Microsoft.) I do think the book, which appears extracted from a P&A document fails to adequately define the audience and that could cause some confusion.

So for a high-level view of both the landscape and a particular architecture, this is not a bad book. For a "comprehensive" solution, this is probably just the first step in a long journey.

Even though I typically don't like to read books that are assigned to me and I am forced to read this book was just one I could not put down. I loved reading about this book. I was able to understand the whole story of how Microsoft was made. This book gives you an insight to who Bill Gates and Paul Allen really are. The author goes into great detail about how two teen entrepreneurs were able to successfully start up and manage a business. The only thing is that this book is a little outdated meaning there is no current updates. To continue on the sequel book Over Drive which I am in the possess of reading is excellent as well.

(By Edward Trimnell, author of "Why You Need a Foreign Language & How to Learn One," ISBN:1591133343)

This book is required reading for anyone who is interested in:

1) Computers and software
2) Microsoft
3) Entrepreneurship

Hard Drive is as readable as a novel. The book covers the history of Bill Gates' rise to power with expert thoroughness. There are numerous insights into the man and company--not all of which are flattering.

If you have ever wondered how the current PC software market reached its current state, then you will find the answers within these pages. The authors portray the struggles between Microsoft, Lotus, IBM, and Apple from the technical, commercial, and human perspectives.

The book is also balanced in its handling of one of the business world's most controversial personalities. Gates admirers and detractors alike will find ammunition in Hard Drive.

Should I Buy This Book?

The story is starting to get a bit dated but the book still has 95% of the Gates story warts and all. He is one of the most compelling and admired and maybe feared business leaders today.

Unlike Jack Welch, another great leader and manager, he started from zero or near zero in a new field and (largely) owned the company. I remember seeing the personal computers for sale in the 70's - just pre Microsoft - that did not come with anything other than a very rudimentary software. He was one of the first people to recognize the dollar value of the software and to charge for its use in the hobby market. Since then he has dominated the market. Now there is a computer in virtually every office and home using his (expensive high margin) software. Now he has the resources to buy anything he wants, or to support any charity or university, or buy a sizeable portion of the stock in almost any company that he wishes. And of course he has no debt. He used no risky leverage or tricks. He took the software and generated billions of dollars in cash and securities on hand. It is quite the story.

This is a relatively short book and an easy read. Frankly it is a must read for anyone running their own business and or in the Tech field. Gates is the statistical anomaly who sits at the very pinnacle. He is perched even above Warren Buffet the financial guru who is at least 20 years older than Gates. But Gates was astute enough to buy DOS for $50,000. and then had the business smarts and drive to market and sell the product. He was a hands on manager working long hours and a technical leader. He was (is) as smart or smarter than anyone else in the field. He did not invent any major new invention but he had the practical ability to take the product to market and make it work, make it better, and build a winning business. He hired great people and built a team that literally crushed the opposition including IBM and all foreign competitors in that area. It is only now two decades later that people are (seriously) starting to consider alternatives such as Linux, and these still have a lot of catch up to do.

Still a great book and a great yarn. A must buy 5 stars.

Jack in Toronto

This book is a comprehensive analysis of the points throughout development life cycles where team collaboration is appropriate for creating deliverables. Formats and methods for conducting team workshops are set out in great detail, based on the organizational environment, project type, end result desired, and particular phase of the life cycle.

Jones proposes a "framework" for development which he calls Team Design and which he contrasts with Joint Application Development (JAD) and other group methods. Jones defines five Formats (Business Process Design, Requirements Definition, Application Design, Team Planning, Decision Making) under which almost any development project or part thereof can be placed. He devotes separate chapters to each Format, defining for each Format the life-cycle steps within the Format, the workshop agenda activities that apply to each phase of the life-cycle, and recommended workshop methods (e.g., brainstorming, scoping diagrams, scenario analysis) that can develop the deliverables for the phase.

Team Design comprises a generic set of life-cycle Phases (Initiating, Scoping, Visualizing, Usage, Packaging, Validating) that can be mapped to each of the five Formats. For each Phase, Jones then recommends certain workshop methods that can be used regardless of the Format. This allows flexibility in analyzing all the factors facing a Project Manager and Facilitator (organization type, project type, end result, life-cycle phase) and adapting a workshop plan that will apply best. It also allows for bridging of experience with workshop methods across different Formats.

Jones also deals in depth with a wide variety of topics related to team-based development, including: (1) JAD and Participatory Design: A survey of the history of these two group-based methods, and an assessment of their strengths and weaknesses in various environments; (2) Facilitation: The scope of Facilitation; the technical competencies required of a Facilitator in a development environment; in-depth description of facilitation tools (e.g., conflict resolution, problem solving) and workshop methods (e.g., brainstorming, diagramming, Pareto charts), and their applicability; (3) Requirements: Analysis of the major problems faced by organizations in creating and managing requirements, and how Team Design can address those problems; (4) Team Dynamics: The phases of team development; team-building techniques; special issues involving workgroups comprising members with different functional backgrounds; and (5) Organizational Culture: The impact of organizational dynamics on a company's receptiveness to structured methods and team-based approaches to development.

A tremendous discussion and reference of the nuts and bolts for all kinds of teaming in the IT world. It's loaded with nuances related to teaming that you won't easily find in one place. It's also a good review, thinker, and is exceptionally well researched and written. I definitely reccomend this book to anyone who is serious about adding to their skills in this often overlooked but necessary specialty.

This book is a comprehensive analysis of the points throughout development life cycles where team collaboration is appropriate for creating deliverables. Formats and methods for conducting team workshops are set out in great detail, based on the organizational environment, project type, end result desired, and particular phase of the life cycle. Jones proposes a "framework" for development which he calls Team Design and which he contrasts with Joint Application Development (JAD) and other group methods. Jones defines five Formats (Business Process Design, Requirements Definition, Application Design, Team Planning, Decision Making) under which almost any development project or part thereof can be placed. He devotes separate chapters to each Format, defining for each Format the life-cycle steps within the Format, the workshop agenda activities that apply to each phase of the life-cycle, and recommended workshop methods (e.g., brainstorming, scoping diagrams, scenario analysis) that can develop the deliverables for the phase. Team Design comprises a generic set of life-cycle Phases (Initiating, Scoping, Visualizing, Usage, Packaging, Validating) that can be mapped to each of the five Formats. For each Phase, Jones then recommends certain workshop methods that can be used regardless of the Format. This allows flexibility in analyzing all the factors facing a Project Manager and Facilitator (organization type, project type, end result, life-cycle phase) and adapting a workshop plan that will apply best. It also allows for bridging of experience with workshop methods across different Formats. Jones also deals in depth with a wide variety of topics related to team-based development, including: · JAD and Participatory Design: A survey of the history of these two group-based methods, and an assessment of their strengths and weaknesses in various environments · Facilitation: The scope of Facilitation; the technical competencies required of a Facilitator in a development environment; in-depth description of facilitation tools (e.g., conflict resolution, problem solving) and workshop methods (e.g., brainstorming, diagramming, Pareto charts), and their applicability · Requirements: Analysis of the major problems faced by organizations in creating and managing requirements, and how Team Design can address those problems · Team Dynamics: The phases of team development; team-building techniques; special issues involving workgroups comprising members with different functional backgrounds · Organizational Culture: The impact of organizational dynamics on a company's receptiveness to structured methods and team-based approaches to development