VISIBLE ANALYST TUTORIAL- BCIS 4610 [ref: www.cob.unt.edu/] Part 1: Connecting to Visible Analyst In order to use Visible Analyst Tools, you need to physically be in a COB computer lab or connect to a lab pool via VMware. For more instructions on how to connecting to the lab pool, please see: 1. Once connected to a lab computer, go to Start>COBA Menu>Applications>ITDS>4610>Visual Analyst 2. You will be prompted to log in, please enter your login that starts with BCIS4610_xx and your password. 3. Once authenticated, you will be prompted to open an existing project or to create a new project. In order to open an existing project, you should select a project on the list and press OK. You will only be able to open projects for which you have access rights. 4. If you press Cancel, you will see the main screen of the VA interface featuring Zackman s Architecture Model. 1
Part 2: Viewing TEST Project TEST project is a sample project, which deals with developing a system for a Drivers Licensing department. It already has a planning statement, a DFD, and ERD and several other diagrams. I strongly recommend that you study the diagrams for this project before starting your work on Project Interim Report. 1. In order to open TEST project, go to File>Select Project. Then select the TEST project and press OK. 2. Once the project opens, you will be able to browse existing objects using the navigation pane. 3. In order to view existing diagrams, click on one of the cells in the Zachman s diagram. Diagrams corresponding to that cell will appear in a dialog box. For example, if you click on the cell that lies at the intersection of the Function (How) column and the Business Model row, you will see the list of diagrams, which include 2 DFDs. 2
4. Double click on the DMV System. It shows a context DFD diagram, where the entire system is represented as one function or process. (Please note, that it is not conventional to show data stores on a context diagram) 5. Right-click on the Driver s Licensing System box, and select Explode. The level 0 DFD opens, which shows the key functionality of the system. 6. Explore diagrams that correspond to different cells of the Zachman s Framework, such as an ERD under business data models. 3
Part 3: Creating a Project and Adding Users 1. To create a new project, go to File>New Project. Make sure you save the project on your removable jump drive. 2. You will be prompted to create a new diagram. Press Cancel. 3. In order to add users to your project (in case of a group project only), go to File>Modify User List> Add. In a dialog box that pops up, select users that you would like to add and press OK. 4
Part 4: Creating a Context Data Flow Diagram For the rest of this tutorial, you will be working on Minicase 2 from Ch.5 in Dennis et al textbook. You will first need to create a context level diagram for the entire system. 1. In order to create a new diagram, to File>New Diagram. In the dialog box that opens, select a Data Flow Diagram as a Diagram Type. Make sure that Context Diagram is checked. 2. A new window will open with a blank process and a dialog box. Type PSST System in the box as the name for your system. 3. By selecting from the Toolbar above, add an external entity, (you will need to click on the rectangular shape, and then inside your diagram). 5
4. Name your external entity Client. 5. Add one more external entity, and call it PT Staff. 6. Add a data flow Contract Info from Client to PSST System by clicking on an arrow icon in the toolbar and drawing the arrow from Client external entity to PSST System process. 7. Add additional external entities and data flows as per your DW assignment. Your context diagram should look like this. Save your diagram as PSST-Context DFD 6
Part 5: Creating a Level 0 DFD 1. In your Context diagram, right click on the PSST System process and select Explode. Select Create New Diagram in the dialog box. 2. A new diagram will open, which already contains all the data flows from the Context level DFD. 3. Using the process icons in the tool bar, add a Store Contracts process. 7
4. Drag the arrow end of the Contract Info data flow and connect it to the Store Contract process. 5. Using a Data store icon, add a new data store. Call it Contracts DB. 6. Add a data flow between the Store contracts process and the Contracts DB data store. 8
7. Add other processes, data stores and data flows as per your assignment. Make sure to connect the existing data flows (the ones from the context diagram) to your processes. Save your diagram. 8. Your final diagram should look similar to the one below. 9
Part 6: Creating a Business Process Model 1. Create a new Business Process Model diagram. Make sure to select Landscape orientation. 2. Using the Pool/Swim lane icon add a new pool. In the pop-up dialog box specify the pool name and three lanes, contracts manager, placement and arrangements. A new pool will be added. 10
3. Click on the start event icon and drop it inside the pool. A dialog box will appear and the swim lanes will become visible. 4. Name your Start even as start, select none as trigger. 5. Expand your swim lanes by dragging and dropping the edges of the pool, so that they occupy the entire page. You can adjust the width of the swim lanes by dragging the edges of the lanes. 6. Using the Activity icon, add a new activity to the Contract manager lane. Call it Store Contracts. Add a sequence flow SF1 between the start event and the Store Contracts Activity. 11
7. Add additional activities and place them in corresponding swim lanes. 8. Add a decision point (a diamond) after the verify SR activity. Call in Valid SR. Add a data flow from Verify SR to the Decision point. 9. Add an end even after the close contract event. Select Terminate as a result. 12
10. Create conditional sequence flow between the decision point and the Find Staff activity and the End event. Call them Valid SR and Invalid SR respectively. Specify valid or invalid SR as conditions. 11. Your final diagram should look like this. You will need to do your HW individually and submit a printout of all your diagrams (1 diagram per page) with a cover page and 2 use case descriptions. 13