New-age Transactional Systems - Not Your Grandpa's OLTP
John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Abel Avram on Jan 06, 2009
Jesse Johnston and Denis Morozov created code2plan, an Agile software project management tool, as a beta Visual Studio add-in and released it for free. The tool also runs as a stand-alone application that can be used to track projects, iterations, user stories, features, tests, defects and builds.
Agile software project management is becoming increasingly popular, so another Agile tool is not a surprise. The attractive part of this tool is its integration with Visual Studio 2008, but it can also run as a stand-alone application. .NET Framework 3.5 SP1 is required and it is automatically installed during setup if missing.
code2plan currently tracks the following features: projects, iterations, user stories, features, tests, defects and builds. The tool also manages traditional projects by tracking phases instead of iterations and requirements instead of stories. code2plan creates burndown charts for both types of projects.
code2plan can use its own database or can connect to a team database, SQL 2005 and 2008 being supported. Using a team database allows for projects to be shared across team members which can edit the projects. Every team member can update the current view to include the changes done by other team members. Project changes can be edited offline and they will be automatically synchronized with the team upon connection. There is no limit on how many members a team could have.
code2plan is free and no registration or license is required. The two developers team plan to release a richer application in the future which will most probably be not free, but they promise to keep the basic edition free. The project is not open sourced and there are no plans to make it so. An SDK is to be released soon allowing other developers to enhance the tool by using its API.
18 agile and lean practices for effective software development governance
Five Key Practices to Agile ALM
Using Drools? See what you're missing! Get the Power of Drools with the Assurance of Red Hat
In today’s hyper-competitive world, later may be too late to adopt Agile development and this Roadmap for Success will help you get started. Download "Agile Development: A Manager's Roadmap for Success" now!
There are more and more of these tools out there and I struggle to figure out why I would want to use them more than a nice big visible white board.
We have a geographically dispersed team so it would have to be a REALLY big white board to be visible by all ;-)
I don't seem to be able to login. It always crashes...
Please report any bugs to the development team. Thank you!
You were logged in because you could post this comment.
This app crashes consistently and it won't connect to my team database. We cannot use this!!!!
Oops, I meant the software not the InfoQ website. I seem to have the same problem that Cleavon has.
John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.
Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.
Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.
Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).
Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.
Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.
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.
6 comments
Watch Thread Reply