10 tips on how to prevent business value risk
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Jonathan Allen on May 12, 2009
In a effort to remain relevant in the increasingly difficult news industry, the New York Times has built a REST-based API through the Times Developer Network. Though still in public beta, there is already a rather extensive list of available APIs. Most APIs return both XML and JSON and are very well documented. Other REST providers would do well to emulate their standards.
Currently the APIs are free, but there are numerous restrictions on the APIs. For example, only the Campaign Finance, Congress, and NY State Legislature APIs are licensed for commercial use. All other APIs are strictly limited to non-commercial, non-competing use. And of course there is no guarantee that fees won’t be charged in the future, presumably once they figure out how to make money off the thing.
In order to make it easier for developers to use these APIs, Microsoft and the New York Times are jointly offering the New York Times Silverlight Kit. As the name implies, this toolkit is heavily focused on promoting Silverlight and other Microsoft technologies. This are reflected in the project goals.
- Make it easy for designers and developers to use the APIs with little to no coding: all XAML
- Include Design-Time sample data to facilitate crafting experiences in Expression Blend and Visual Studio
- Use the MVVM Design Pattern to separate components for test-ability and data binding.
Despite being tagged with the Microsoft Permissive License, the source code isn’t actually available at this time. Only the DLL and related debug symbols are in the 1.0.1 release.
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.
Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.
John Davies examines Visa’s architecture and shows how enterprises have architected complex integrations incorporating Hadoop, memcached, Ruby on Rails, and others to deliver innovative solutions.
Sean Comerford unveils ESPN.com’s architecture, what components are used and why, and the current changes the website goes through.
Are there repeated patterns of failure on Enterprise Agile Enablement efforts? Sanjiv and Arlen discuss Seven Deadly Sins to avoid when adopting Agile in an enterprise.
Erik Dörnenburg answers: What is Enterprise and Evolutionary Architecture?, discussing 4 issues: Turning strategy into execution, Ensuring conformance, Where do the architects sit? Buying or building?
Sean Cribbs explains what Map-Reduce and Riak are, why and how to use Map-Reduce with Riak, and how to convert SQL queries into their Map-Reduce equivalents.
2 comments
Watch Thread Reply