1. Fatima Al-Abdulla Managing Analysis

2. Outline:  Introduction  Why managing Analysis? 1-Documenting Analysis 2-Assigning Responsibilities 3-Communicating about analysis 4-Iterating on the analysis model 5-Client sign-Off  Conclusion

3. 1-Documenting Analysis Why “documenting Analysis”? To be able to revise our work any time through the whole process What should we document? Object& dynamic Model. textually and graphically. Where should we document them? In a RAD (Requirement Analysis Document).

4. 2-Assigning Responsibilities  Why “Assigning Responsibilities”?  The Responsibilities (Roles) are: Generation Of Information Integration Review

5. Assigning Responsibilities The User Generation Of Information Generation Of Information The Client Integration Why? The Reviewer Review Review  The Responsibilities (Roles) are: Generation Of Information Integration Review

6. 3-Communicating About Analysis How can we make the “communication” between A client/User and a developer “Useful”? How can we make the “communication” between A client/User and a developer “Useful”? 1-Define Clear territories 2-Brainstorming2-Brainstorming By stating 2 guidelines,

7. 4-Iterating over the analysis Model How to converge to a “stable” model? Add each change Considering Consequences Entropy

8. Company LOGO Client sign-off Some Points OF agreement:  List of priorities  A revision Process  A schedule and a budget

9. Why “Managing analysis”? References: The text-Book Object-Oriented software Engineering using UML,Patterns and Java