EventFeb2009

From Requirements Engineering Specialist Group

Jump to: navigation, search

Past Event

Jump to comments on this event

Requirements for Changes to Existing Systems

Contact Johnette Holworthy.

Date 5pm - 7.30pm, 12 February 2009

Venue Main Theatre, Misys, One Kingdom Street, Sheldon Square, Paddington, London W2 6BL



Capturing and Documenting Requirements for Modifications to Large, Existing Systems



This "birds of a feather" event will be an open but facilitated discussion with an introductory talk by Phil Cantor of Misys.

Large, existing systems are different and hard. Much of the literature on software engineering assumes a green field, but most people have to add to an existing environment. This session is an attempt to explore what is best practice for capturing and documenting requirements that are essentially modifications.

Misys plc is delighted to host the Requirements Engineering Specialist Group of the British Computer Society to explore these issues at our brand new, state of the art London office. We certainly don’t have all the answers but are willing to share our experiences in exchange for hearing those of other IT professionals.

All welcome – please register with johnette.holworthy@misys.com.

After: Continue discussions at the Union Bar, Sheldon Square



Some of the issues



To what extent should/can/must the existing system be documented in the requirement?

Can agile approaches be used sensibly for these systems?

What is the level of detail for intrusive but simple changes?

What level of granularity should be used for a single requirement identifier?

Can modern requirements diagram techniques be effective in these cases?

How does it differ if there are multiple customers (package) versus a single one (bespoke or in-house)?

Should requirements be captured per venture, per investment, per release or per release component?

How and to what extent should non-functional requirements be documented (eg platform, performance, reuse, architectural probity)?


Views