John,
personally, I have only one important issue that you should add to your risk list: "The most dificult requirement is that the new system has to do the same like the old system" In opposite to a new system (green field development:-) you have many set expectations in the existing user/actor community. We had this during a replacement project (where we replaced an inhouse solution with ClearQuest). Even by 'only' configuring the new system, it ran out of scope massively because the existing stakeholders where used to the old system, so they very soldomly had the root problem in mind, just features... My suggestion for this risk: - start with timeboxes as short as possible - you even need more manegement and user(!) attention than in a 'normal' project - introduce a rigorous requirement management team with the will to really understand the WHYs of the old system - use cases, use cases, use cases: I found it useful to document and talk using use cases with everyone Also they are very useful to document the 'old' system without talking to much about the old architecture Another tip (Thanx to Walker Royce for pointing this out): shape the project team around the NEW architecture, don't let the old structure define your system (as they would try to squeeze the new system in the old organization/architecture). Best regards, Volker -----Ursprungliche Nachricht----- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Gesendet: Freitag, 8. Marz 2002 14:54 An: [EMAIL PROTECTED]; [EMAIL PROTECTED] Betreff: (ROSE) guidelines for a re-doing an existing architecture From: John Scott Parsons Does anybody have an quick guidelines for a project to re-do an existing software architecture for a software product (really a set of libraries)? If so, please send them or some useful references to me. My team is in the early stages of a project to revise the current architecture for a set of libraries which get used in several other products. We have collected some high-level requirements (ideas, etc.) and are defining the scope of the effort. This is a first project where the team is truing to use some UML-based design techniques. We are also trying to use some concepts from the RUP. Any suggestions would be of great help. Thanks. John John Scott Parsons Eastman Kodak Company 8/69/RL Room 8624 - MC-01915 1700 Dewey Avenue Rochester, NY 14650-1915 voice: 716-588-9721 (KNET: 25-89721) fax: 716-477-8681 [EMAIL PROTECTED] ------------------------------------------------------------------- ************************************************************************ * Rose Forum is a public venue for ideas and discussions. * For technical support, visit http://www.rational.com/support * * Post or Reply to: [EMAIL PROTECTED] * Subscription Requests: [EMAIL PROTECTED] * Archive of messages: * http://www.rational.com/support/usergroups/rose/rose_forum.jsp * Other Requests: [EMAIL PROTECTED] * * To unsubscribe from the list, please send email * To: [EMAIL PROTECTED] * Subject: <BLANK> * Body: unsubscribe rose_forum ************************************************************************* ************************************************************************ * Rose Forum is a public venue for ideas and discussions. * For technical support, visit http://www.rational.com/support * * Post or Reply to: [EMAIL PROTECTED] * Subscription Requests: [EMAIL PROTECTED] * Archive of messages: * http://www.rational.com/support/usergroups/rose/rose_forum.jsp * Other Requests: [EMAIL PROTECTED] * * To unsubscribe from the list, please send email * To: [EMAIL PROTECTED] * Subject: <BLANK> * Body: unsubscribe rose_forum *************************************************************************
