A model allows you to define your own architecture and present the same information using any number of 2-dimensional diagrams. The book structure is enforced through chapters and subsections within chapters. The BABOK is in a book format and as such it presents analysis information linearly. Components colored white are external inputs to the business analysis. The component in question is colored green. For example, Figure 2: shows the Business Analysis Approach artifact and its relationships to other artifacts.įigure 2:Business Analysis Approach Artifact Relationships One viewpoint allows you to focus on a particular component (or set of components) and see the relationships between those components and other components in the model. This allows the information to be displayed from many different viewpoints. Once the relationships between these components are identified, the modeling tool automatically generates diagrams showing logical connections (traceability) between components. Types of component are inputs, outputs, tasks, techniques, guidelines and tools. The model captures components of the BABOK and the relationships between them. The information in the model is not simply repeated using a graphical representation, but it is consolidated into an unambiguous set of guidelines. I wanted a more logical method for finding this information which uses clues in the question to find logical links to an appropriate answer. I realized that finding the information in the BABOK required a lot of searching. This model came about when I was trying to understand the BABOK in order to address practice questions for CBAP certification. What is the benefit of repeating BABOK information in a modeling tool (such as Visual Paradigm)? (See Trace Requirements, BABOK section 5.1.) Why Model? Relationships between the model components capture traceability. (See Define Requirements Architecture, BABOK section 7.4.) The model architecture organizes these classes and supporting components, into packages. (See Specify and Model Requirements, BABOK section 7.1.) A class details the object’s data and its functions.
The analysis breaks down the BABOK into object classes and their supporting components.
Links to Visual Paradigm and to the model, are referenced at the end of this article. display the new ticket details 8.Visual Paradigm is my personal preference, but there are several modeling tools that are equally capable of hosting this model. infroms RSystem with the new ticket and ask to cancel lost ticket 6. Create Ticket see 4.a for alternative floyw 5. RSystem sends its feedback System Response ticket number to 4. Old ticket has been canceled New ticket has been issued to passen ger Main Success Scenario Actor Action 1. The old ticket number exists with the passenger Post-conditions 1. display the new ticket details 8.confirms that ticket has been saved 7 passenger selects to save the ticket Alternative flows 4a: if the ticket has been used or not found, system displays error message Show transcribed image text Issue new Ticket for a lost one Use case Id: UC05 Brief Description A passenger had his ticket lost, so he enters his ticket number and asks the system to create a new ticket and remove the old one actors Trig Preconditions Passenger enters the ticket numbers and click on (lost ticket 1. It is better using visual paradigm 15.2Issue new Ticket for a lost one Use case Id: UC05 Brief Description A passenger had his ticket lost, so he enters his ticket number and asks the system to create a new ticket and remove the old one actors Trig Preconditions Passenger enters the ticket numbers and click on (lost ticket 1. Draw a sequence diagram forthis use-case ?
0 kommentar(er)
