1 / 8

UML for The IT Business Analyst A practical guide to Object Oriented Requirement Gathering

University Of Palestine. UML for The IT Business Analyst A practical guide to Object Oriented Requirement Gathering Hoard Podeswa Instructor: Mrs. Eman ElAjrami 2008. Introduction. Who this course is for?? This course is intended for the IT Business Analyst

ardith
Download Presentation

UML for The IT Business Analyst A practical guide to Object Oriented Requirement Gathering

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. University Of Palestine UML for The IT Business Analyst A practical guide to Object Oriented Requirement Gathering Hoard Podeswa Instructor: Mrs. Eman ElAjrami 2008

  2. Introduction • Who this course is for?? • This course is intended for the IT Business Analyst • The IT Business Analyst is an integral part of a software development team responsible for documenting and verifying the business and user requirements for a software system.

  3. Introduction • How you and your organization can benefit from B.O.O.A? • Many organizations are good at developing a good software products, but they are often week in developing the right software product. • The mismatch is between what the user wants, and what the developer delivers.

  4. INTRODUCTON • In addition, many IT projects are experiencing time and cost over runs due to the difficulty in responding to a rapidly changing business environment. • Finally, Many projects failure due to faulty communication between those who know the business, and those who write and construct the software. • With B.O.O.M, the business analyst documents business rules and requirement using the same type of diagrams and concepts that used by the developer.

  5. Chapter Objectives At the end of this chapter, we will: • Understand the role of the IT business analyst throughout a project’s life cycle . • Understand what is meant by a business model , dynamic model and static model .

  6. The IT and Non-IT BA • There are two types of business analysis: • A Business Analyst is someone who works within the context of the business . This person is involved in process improvement , cost-cutting , and so on . • An Information Technology Business Analyst (IT BA) works within the context of IT projects – projects to buy , purchase , or modify some software . • This course is directed to the IT BA.

  7. Why modeling is a good thing? • A business model is an abstract representation of a clearly delimited area of a business . • It may take many forms , for example , pictures with supporting text or the underlying format used by a tool such as Rational Rose to produce diagrams and generate code . • In this course, you’ll be asked to draw a lot of diagrams . What's the point ? After all, most users can’t read them , and they are reluctant to sign off on anything but text !!

  8. Why modeling is a good thing? (cont.) • So, What are those diagrams and models for?? • Use the diagrams to drive the interviews : • There is a logical step – by – step process to drawing a diagram . At each step , you have to ask the user certain questions to discover what to draw next . The act of drawing the diagram tells you what questions to ask and when , and even when the interview is complete • Use diagrams whenever you need to reconcile differing viewpoints

More Related