It is often exceedingly difficult to map requirements directly onto design.
Here, Anja Wever shares her thoughts on why this is the case, and explores various techniques that can be used to facilitate this critical transition. The traditional set up of teams, the “nothing is absolute” conundrum, and the various business analyst viewpoints are discussed, with a view of determining just why it is so difficult to bridge the gap between requirements and design.
We also discuss the necessary collaboration needed between business analysts, architects and testers which helps to make the whole process more dynamic and creative – and allows us to deliver more state-of-the-art solutions as opposed to ‘merely practical’ ones.
Learning Objectives
-
Participants will receive an overview of the limitations that a traditional team structure has on requirements work.
-
Participants will learn about a number of techniques that help support the transition from requirements to design.
-
Participants will be able to include the discussed techniques in their BA frameworks.
Skill Level: Advanced |
Anja Wever, B.Sc.(Hons)
Knowledge Engineer
Software Education
Australia Pty Ltd
Anja Wever has international experience in formal Business and Systems Analysis. In addition to developing courses and delivering training, Anja provides senior consultancy services related to Business Analysis and Effective Business Requirements for Software Education’s customers.
Anja has Medical, Pharmaceutical and Transport industry experience working on safety-critical systems in England, France and her native Germany. While at DWS in Sydney, Anja gained extensive experience with the Australian Electronic Taxpack system e-tax, which allows taxpayers to electronically file a tax return.
|
