requirements

Requirements On The Verge Of A Nervous Breakdown

Session Type: 
Standard [35 minutes]
Speakers

Agile puts enormous strains on the people responsible for software requirements:

  • How do they get just enough requirements in time for the next sprint?
  • How do you pack enough information into the requirements to provide meaningful guidance?
  • Will you ever provide meaningful guidance for outsourcing partners?
  • How do you spin off additional artifacts for governance and compliance?
  • How do you re-purpose the information in the requirements for other audiences?
  • Do you ever get a chance to do retrospectives on requirements?

Schedule info

Time slot: 
26 March 11:15 - 11:50
Room: 
Back Bay
Status: 
Accepted

Audience

Track: 
ALM Connect
Experience level: 
Intermediate

Your system engineering workbench cookbook

Session Type: 
Standard [35 minutes]
Speakers

Ingredients

  • Requirements
  • Software
  • Quality
  • Mechanics
  • Safety
  • Electronics

The first step for this recipe is to get a new Eclipse IDE, and thaw it on your computer. While this is happening you can prep the Requirements editor and the UML/SysML libraries standards. Use high quality editors for best results. If dried existing tools are not available for your specific domain, add 2 teaspoons of freshly developed tools by forking the existing one from github.

Spread a little navigation features over the different components of the workbench. Bake at 42°F for 35 minutes, then take the workbench out of the oven when done and deliver to serve. Once baked, the workbench will last many weeks in the fridge and taste wonderfully whenever needed.

Schedule info

Status: 
Declined

Audience

Track: 
DSL
Experience level: 
Beginner

Agile Development using Visual Requirement Definition and Management Methods

Session Type: 
Standard [35 minutes]
Speakers

The advantages of applying lean and agile techniques to software design and development activities of are now well established and understood in IT focused organisations.

Often many IT organisations who have implemented agile techniques continue to struggle because they either do business analysis activities through a waterfall process or skip upfront requirements analysis completely as proposed by agile purists. How do we use requirements definition and management in an agile process?

Schedule info

Status: 
Declined

Audience

Track: 
ALM Connect
Experience level: 
Intermediate

Copyright © 2013 The Eclipse Foundation. All Rights Reserved.