7.CEN6016-Chapter2.2

7.CEN6016-Chapter2.2 - Chapter 2.2 Iterative, Evolutionary,...

Info iconThis preview shows pages 1–5. Sign up to view the full content.

View Full Document Right Arrow Icon
Chapter 2.2 Iterative, Evolutionary, and Agile A Continuation
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
2 2. 4 Example Iterative and Evolutionary Analysis and Design? Excellent example. Many details will be forthcoming to explain all this. Overview of a simple example on 20 iterations (over a year) project: Before the first iteration , hold an initial requirements workshop with client and senior developers. In the UP this is the Inception Phase (covered in detail in next lectures) o Define the project objectives ; o Do high-level requirements analysis by identifying use cases (say 30 are found) and features; (use cases covered in a later chapter) 30 is a large number!!!! (High level: naming; short description; not much more in high level (façade) use cases). Place holders…. o Study problem domain…. 1. Identify non-functional requirements (look and feel, efficiency etc.) 1. These are typically ‘quality factors’ such as reliability, efficiency, scalability, learnability, maintainability, security, correctness, etc.
Background image of page 2
2.4 Example Iterative and Evolutionary Analysis and Design? o Before the first iteration – continuing …… o Pick the 10% of the use cases with a blending of: o Architecturally Significant ; (require significant work!! Design, build, test…) o High marketing value ; high business value; core needs o High risk Address these first!! this leads to say parts of three use cases: say UC2, UC11 and UC14; Recognize that these are likely scenarios WITHIN each of these use cases and not the entire use case…. o Do a detailed analysis of the functional and non-functional requirements for these three use cases (or scenarios from the use cases); Note perhaps 10% of use cases are now significantly analyzed. 90% not. o Review everything with everybody; o This is done before we actually START iteration one. This is the iteration planning for iteration 1, which will take place in the Elaboration Phase. o This (and much more – vision docs, risks lists, business rules, etc.) is done during Inception. Sometimes, we say that there is one iteration in Inception. Arguable.
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
4 2. Then the developers alone hold an iteration planning meeting to define a subset of UC2, UC11 and UC14 for the first iteration to fit within a, say, 4 weeks time box (do not be too greedy!). Document the subset . Maybe tentatively schedule 2nd and more tentatively the 3rd iterations; Excellent. Realize these are scenarios . Scope the iteration. 3. Iteration 1 (in UP terms this is the start of the Elaboration Phase ) which mainly deals with critical architectural modelling and risk reduction… 2. Perform OOA using the Domain Model captured in UML; review by all developers (3 days?); What is domain modelling?? Also includes several additional diagrams such as sequence and
Background image of page 4
Image of page 5
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 28

7.CEN6016-Chapter2.2 - Chapter 2.2 Iterative, Evolutionary,...

This preview shows document pages 1 - 5. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online