Export to

• Google Calendar
• iCalendar file
• hCalendar markup
  <div class="vevent h-event"> <h1 class="summary p-name">Rose City SPIN: Developing Requirements for Legacy Systems</h1> <div class='date'><time class="dtstart dt-start" title="2009-12-10T18:00:00" datetime="2009-12-10T18:00:00">Thursday, December 10, 2009 from 6</time>–<time class="dtend dt-end" title="2009-12-10T20:00:00" datetime="2009-12-10T20:00:00">8pm</time></div> <div class="location vcard p-location h-card"> <a class="url" href='http://calagator.org/venues/202390556'><span class='fn org p-name'>Intel Jones Farm Conference Center (JFCC)</span></a> <div class="adr p-adr h-adr"> <div class="street-address p-street-address">2111 NE 25th Avenue</div> <span class="locality p-locality">Hillsboro</span> , <span class="region p-region">Oregon</span> <span class="postal-code p-postal-code">97124</span> <div class="country-name p-country-name">US</div> (<a href='https://maps.google.com/maps?q=2111%20NE%2025th%20Avenue,%20Hillsboro%20Oregon%2097124%20US'>map</a>) </div> </div> <div class="description p-description"> <p>This is a free talk open to the public and presented by the Rose City Software Process Improvement Network (SPIN).</p> <p><b>Logistics:</b> Networking from 6:00 PM to 7:00 PM Talk presented from 7:00 PM to 8:00 PM (doors close at 7:15)</p> <p><b>Talk:</b> Developing Requirements for Legacy Systems presented by Bill Baker</p> <p><b>Abstract:</b> Many legacy systems were created without documented requirements. Over the years, changes were made, often without adequate documentation. Software quality suffers as the system becomes more and more complex. This presentation will provide a case study of bringing requirements management and other related process improvements to a legacy software product — one which has been successful for over twenty years.</p> <p>A cross-functional team of management undertook a project to improve significantly the processes related to requirements. This presentation describes the lessons learned while undertaking this project. Among these are: • A good implementation start is essential. Outside consultants are useful. Fully involve all stakeholders. • Different audiences have different needs. Find effective ways to communicate to each audience. • Be pragmatic when choosing what requirements to write and how much effort to put into describing the current system. • Leverage tool adoption to make changes that are more general to the software development process.</p> <p><b>Author Bio:</b> Bill Baker is a software development manager at Sage in Beaverton Oregon. He has been involved in software development, project management, and process improvement for a number of years. While at Harland Financial Solutions, Bill led the improvements outlined in this paper. Bill has a Ph.D. in Electrical Engineering from Washington State University and an excessive collection of other degrees from Washington State University and Michigan State University.</p> <p><b>About the Rose City SPIN:</b> The Rose City Software Process Improvement Network (SPIN) is a monthly forum for networking, mutual support, and promotion of effective software practices. We exchange practical experiences, ideas, knowledge, wisdom, and war stories about the technical, business, and human facets of software process improvement. The Rose City SPIN serves the software development community of the Portland/Vancouver metro area. Whether you work for a large company or a small one, corporate or self-employed, industrial or academic setting, you are welcome at the Rose City SPIN.</p> </div> <h3>Links</h3> <ul> <li><a class="url u-url" href="http://upcoming.yahoo.com/event/4889899/ ">Website</a></li> </ul> </div>