Use Case diagrams as a requirements gathering tool for new functionality - particularly in systems t
        Posted  
        
            by drelihan
        on Stack Overflow
        
        See other posts from Stack Overflow
        
            or by drelihan
        
        
        
        Published on 2010-05-14T13:18:27Z
        Indexed on 
            2010/05/14
            13:34 UTC
        
        
        Read the original article
        Hit count: 268
        
Hi Folks
I'm interested in persuing the idea of using Use Case Diagrams as a tool for collecting user requirements. However, it will be for new features as opposed to developing a system from scratch. Also, the system only has a small level of user interaction - most of the actors will be external systems.
I want to know what people's experiances have been with using this method of gathering requirements. How did your customers respond to the change and was it positive? Did it just not work for anybody?
Thanks,
© Stack Overflow or respective owner