Dissecting business from software requirements
Jochen Krebs of IBM does a good job and explaining the importance of seperating business requirements from software requirements. http://www-128.ibm.com/developerworks/rational/library/aug05/krebs/
Jochen Krebs of IBM does a good job and explaining the importance of seperating business requirements from software requirements. http://www-128.ibm.com/developerworks/rational/library/aug05/krebs/
June 22, 2006
RUP is very big and at times is difficult to figure out which pieces of RUP you should use. Hans Admirall does a good job sharing his experience with RUP and what modeling activities make sense in the below White Papers. Part 1 – Business Modeling & Requirements Part 2 – [...]
December 29, 2005
Overcoming cultural challenges in adopting iterative development is the topic of an article I found on IBM’s site. Clay Nelson does a great job of talking about the advantages of iterative development as well as assessing and overcoming your organizational culture. Working in a high or low trust organization “……………………..A lack of [...]
December 21, 2005
It may not be the silver bullet but it sure gets close. Planning and executing a iterative software development cycle seems to go against the main grain of most people in business today. In the world of contracts and share holder deliverables the concept of beginning to build before the contract is signed is [...]
December 7, 2005
Vision is what guides us and keeps us between the lines. Chaos is almost always inevitable when developing software and a good vision document will assist us with staying on track and ensuring we deliver the right solution. This product vision model helps team members pass the elevator test — the ability to [...]
July 21, 2006