Hi, I am currently working towards the development of a 'product' subcontracted to us by our client, who is a software product development company. The client is a firm believer of RUP and participates in some of the workflows too. However, in a scenario where a solution is being designed for a client who belongs to another domain, will some aspects of RUP make sense? E.g. Asking a client to validate requirements captured in the use case model. That would expect the client to get familiar with Use Case Modeling notations in the least. The client might in fact be more familiar/comfortable with specifying requirements in a different way. And might insist on that too. The objective of inception, probably doesn't apply in such a case as the client must have already thought of the business case before giving the work to us. So we probably start our work with more Elaboration related activities. Now, the elaboration phase activities, the use case detailing is probably rework in some form as the requirements already exist in some client-preferred form but we are forced to put it into the form of use cases. Or are we not? The client is probably not going to relavidate the use cases again anyway. The iterative development thru construction still sounds like a great idea. However, some of the workflows in Construction such as preparing the Analysis Model could again be deemed a luxury by the client. Perhaps the generic answer to this question is thet RUP is customizable. If any of you folks have had any such experiences where you have customized the extent of your usage of RUP, please share it. That will give my an idea. Thanks. Santosh
0
