views:

99

answers:

1

I have chosen to use the development method RUP (Rational Unified Process) in my project. This is a method I've never used before. I've also included some elements from Scrum in the development process. The question is what the requirement specifications should contain in a RUP-model? Is it functional and non-functional requirements? And what should be included in a technical analysis and security requirements for RUP? Can’t find any information. Notes about this would be helpful. Hope people with RUP experience can share some useful experiences

A: 

Try the Rational Unified Process page at Wikipedia for an overview.

The core requirements should be documented in the project description. RUP tends to place a lot of emphasis on "use cases", however it is very important not to lose sight of the original requirements at all levels of detail, because these will answer the "Why?" questions. If the developers only see the uses cases, they will know What they are supposed to build (effectively the functional requirements) but not Why it is required. Unless the developers have easy access to the original analysts, this can cause very serious problems.

richj
ok. Are theire any report where someone have used RUP before? Would be nice to see the structure
tony
There's a "Modern Software Requirements Specification" template here: https://www.burlesontech.com/wiki/display/btg/Template+-+Software+Requirements+Specification+(SRS)"
richj
For obvious reasons, http://www.ibm.com/ has a lot of material about the Rational Unified Process.
richj