Business Analysis Tools, Lecture notes of Business

Download Business Analysis Tools and more Lecture notes Business in PDF only on Docsity!

Business Analysis Tools

Enterprise Architect User Guide Series Author: Sparx Systems & Stephen Maguire Date: 30/06/ Version: 1. CREATED WITH

Table of Contents

Business Analysis Tools

Enterprise Architect is a sophisticated and flexible Business Analysis modeling tool that can be used by the analyst from planning through to product support. The tool can be used with any Business Analysis process and there is a wide range of features that allow analysts to work using their preferred methods, such as Word Processor views, Spreadsheet views, Diagrams, Relationship Matrix or a number of other core and extended features. The analyst will be happy in the knowledge that whatever the task is, there will be a tool to assist them to carry out their work, and the results will be stored in a sophisticated repository that can be accessed by other team members who will ultimately benefit from their work. This Mind Map shows the landscape of the key Business Analysis tools that can be used to develop and manage the wide range of artefacts produced by the Business Analyst.

Activity Diagram

Getting to know the Activity Diagram

Introducing the Activity Diagram The Activity Diagram is one of the Unified Modeling Language (UML) Behavioral diagrams that can be used to model a process or algorithm as a sequence of steps. It is a more sophisticated version of its close cousin the Flowchart diagram. Activity diagrams can be used to model Business Processes as a UML alternative to the BPMN Business Process Diagram and have the same ability to create a hierarchy of Activities in the Project Browser. «Class» Transaction «Class» Order Order Placed Package Order Send Order Close Order Send Invoice Invoice Customer Payment Invoice Payment^ Process Valid Order? This diagram shows the use of Partitions (swim lanes) to organize the elements and these can be orientated horizontally or vertically They act as a container for the elements in the Project Browser. The diagram also shows the use of Output and Input pins connected by an Object flow. Activity Diagram showing the use of Partitions [Order Rejected] [Order Accepted] The elements can be given a name and detailed descriptions can be added to the notes. By connecting the Activities, Decisions and Forks with connectors (Control Flows) a sequence of elements can describe the business process. A process hierarchy can be constructed by nesting Activities in the Project Browser and using the Child Diagram functionality to enable drill down from the value chain level down to the lowest level processes. Where to find the Activity Diagram Ribbon: Design > Diagram > New > UML Behavioral > Activity Project Browser Caption Bar Menu: New Diagram | UML Behavioral | Activity Project Browser Context Menu: Add Diagram... |UML Behavioral | Activity Usage of the Activity Diagram The Activity Diagram can be used to model any business or technical activity or notion that has a series of steps. This includes business and technical processes and also computer algorithms. The steps are connected by Control Flow relationships that show the sequencing of the steps. Decisions and Merges can be used to model choice and to further control the flow through the Activity. Forks and Joins can be added to split and reunite the flow of control and objects added to show how data is supplied and consumed. Options for the Activity Diagram Activity Diagrams can be drawn at different levels of formality from a Basic Flow Chart style of diagram used to represent a simple Business Process to a sophisticated Action based diagram that can be used to model a complex system.

Artifact

Getting to know the Artifact

Introducing the Artifact An Artifact can be used to represent an external file that resides outside the repository. This is particularly useful for making reference to external file sources including files such as word processor files, spreadsheets and web pages or files reachable by a Universal Resource Indicator (URI). They are also used for other purposes in Enterprise Architect such as for programming source code files and database Tables. The external files can be opened by selecting the element in a diagram or the Project Browser and pressing Ctrl+E or the F12 key. Each file is opened either on a separate tab in the Diagram View workspace (if the file can be opened within Enterprise Architect) or in the default Windows viewer/editor for the file type (if the file cannot be opened within Enterprise Architect). Business Case - Online Bookstore notes The business Case has been prepared to articulate the solution options and what is involved with each solution. It recommends one option as being the most appropriate for the organization. It also list a number of solution features which are considered to be critical to a successful result. It was written to present to the board for the purpose of securing funding for this strategic project. A Commencement of the North America and European Academic Year notes The solution needs to be ready for the Commencement of the next North America and European Academic Year. The financial modeling has factored these sales of academic titles into the first year of revenue and the solution needs to be available for the product entry staff to ensure the titles are listed and ready for purchase. Reprint of rare and out-of-print titles notes This is a differentiating service and is expected to produce good return on investment. There are some titles that sell for tens of thousands of dollars and the customers are specialized and must be treated accordingly. They include gallery owners, national libraries, and academic institutions. Information and system vulnerability due to online presence notes The transition to an online presence has caused the security architect to raise issue about the vulnerability of systems and the information they contain. The sales force is now global and this requires new measures to protect sensitive information that must be accessed by the internet and from potentially un- trusted networks. This diagram shows a number of factors that are important about the Bushiness Case that are time sensitive, high value or are important because of risk or architectural significance. The document is modeled using a Document Artifact and the statements using an Issue element. Where to find the Artifact Toolbox Page: Common, Artifacts, Component, Documentation, Deployment | Artifact Usage of the Artifact The Artifact is a powerful tool for connecting elements in the repository with external files or web resources. It is particularly useful when a file such as a spreadsheet, word processor, presentation or other file that resides outside the repository has to be referenced or connected to elements inside the repository. For example, a Business Case might have been written before the Enterprise Architect repository was established, in a word processor file stored in a corporate document registry available through a URL. The file can simply be dragged onto any Enterprise Architect diagram, which will give the user the option to create an Artifact representing the external document. Leaving the default name will assign the name of the external file. A hyperlink will be created automatically. The Artifact in the repository acts as a surrogate, and any number of elements can be connected to it or Tagged Values added to it. The external file can be opened by simply selecting or or by using the 'Launch' option of the Artifact 'Properties' dialog.

The Artifact can be used to create references to project management documents or resources that are located in a Project Management Office registry. It is also useful to create a virtual reference library inside Enterprise Architect, connecting to resources that reside outside the repository. Options for the Artifact The Artifact can be created as an External or an Internal file. When a file or resource is dragged onto a diagram, a menu will prompt the user to select the type of Artifact to create:

· 'Hyperlink' creates a Hyperlink element on the diagram; you can select a

sub-option to define what happens when double-clicking on the Hyperlink: 'Open' displays the file content and 'Edit' opens it within the assigned file editor

· 'External' creates an Artifact element on the diagram that stores a hyperlink to

the external file; press F12 or Ctrl+E to open the external file

· 'Internal' creates an Artifact element on the diagram and makes a copy of the

file inside the repository; double-clicking the Artifact launches the internal document

· 'Insert' (graphics files only) inserts the file into the diagram as a filled

Boundary element Learn more about the Artifact Artifact

Learn more about Auditing

· Auditing

Auto Names and Counters

Getting to know Auto Names and Counters

Introducing Auto Names and Counters To aid, regulate and enforce a naming standard, Enterprise Architect includes some capabilities to configure the default names assigned to new elements of a specific type. This is a useful feature when dealing with complex and large sets of requirements, but is also relevant when dealing with smaller data sets. Auto Names and Counters can be used to assign a sequential number to any element type including Requirements. It includes a prefix definition, a counter and a suffix definition allowing numbers such as: 'REQ007 - Manage Inventory' to be created. Where to find Auto Names and Counters Ribbon: Configure > Reference Data > Settings > Auto Names and Counters Usage of Auto Names and Counters Analysts and others can use the sequential number for communicating unambiguously about the requirements without having to use the often long requirement name. The 'Apply on Creation' option must be checked to start using the auto numbering feature, this can also be used to temporarily suspend auto naming for example if other types of requirements are being entered that don't need to have sequential numbers assigned. Options for Auto Names and Counters There are options to define the prefix, counter and suffix for a requirement. Learn more about Auto Names and Counters Apply Auto Naming to Existing Elements

Balanced Scorecard

Getting to know the Balanced Scorecard

Introducing the Balanced Scorecard Balanced Scorecard is a strategic diagram that allows a balanced approach to performance measures to be modeled. The diagram can be created from a Pattern that adds and connects the four perspectives: Financial, Customer, Internal Business Process, Learning and Growth. Most organizations of any appreciable size will be using some type of Balanced Scorecard approach to align business activities to the vision and strategy of the organization, to monitor performance against strategic goals and to improve communication. The Balanced Scorecard diagram is part of a set of strategic diagrams that allow many aspects of an organization's business to be modeled. B usiness Process Perspective What Business Processes must we excel at?

• Move to Internet Channel
• Reduce Processing Time
• Broaden Product Offering
• Understand Customer Segments Financial Perspective How should we appear to our shareholders?
• Broaden Revenue Base
• Improve Operating Efficiency
• Reduce Reliance of Domestic Customers Customer Perspective How should we appear to our Customers?
• Product Range
• Service Excellence
• Innovative and Reliable
• Trusted Business Partner Learning & Growth Perspective How can we maintain our ability to change and improve?
• Increase Employee Job Satisfaction
• Increase Employee Productivity
• Hire Internet Aware Technical Staff
• Hire multi-Channel Sales Executives VISION & STRATEGY The Balanced Scorecard diagram is part of the Strategic Diagrams used by managers and others to manage activities performed by the staff under their control. Where to find the Balanced Scorecard Ribbon: Design > Diagram > New > Strategic Modeling > Balanced Scorecard Project Browser Caption Bar Menu: New Diagram | Strategic Modeling | Balanced Scorecard Project Browser context menu: Add Diagram... | Strategic Modeling | Balanced Scorecard Usage of the Balanced Scorecard A Balanced Scorecard can be used to ensure business activities are aligned to the vision and strategy of the organization, to monitor performance against strategic goals and to improve communication.

Options for the Balanced Scorecard The Classes representing the four perspectives can be traced to other elements in the models such as Goals and Business Capabilities and also to linked documents that allow the perspectives to be documented. Learn more about the Balanced Scorecard Balanced Scorecard

Learn more about the Baseline Tool Package Baselines

Boundary

Getting to know the Boundary

Introducing the Boundary The Boundary element is derived from the Use Case system boundary but can be used extensively in other contexts as a way of describing a separation between a system or part of a system and its external environment. Any number of Boundaries can be added to a diagram and other elements such as Use Cases, Features, Requirements, Components and more can be placed inside the boundary. The properties of the Boundary can be altered to show a number of compartments organized into vertical and horizontal swimlanes. The border style and opacity of the Boundary can also be set. Affected External Stakeholders Organization or Enterprise Affected Organizational Unit Solution Delivery Katherine Celta: Training Partner Felicity Newton- Jones: Human Resources Manager Yukiko Miakawati: Chief Financial Officer Karl Zimmerton: Development and Implementation Manager Paul Magnolia: Test Manager Andre Douglas: Chief Technical Officer Toni Rothland: Stock Control Manager Alessandro Taglia: Customer Experience Manager Hamyln Piper: Chief Financial Officer

Stakeholder Onion Diagram

This diagram indicates the level of involvement the stakeholders have with the solution, which stakeholders will interact directly with the solution or participate in a business process, which are part of the whole organization, and which are outside the organization. Where to find the Boundary UML Elements Toolbar | Boundary Common Toolbox Page | Boundary Usage of the Boundary The Boundary element is particularly useful for defining what is inside a system (or part of a system) and what is outside. It can be used to show the Use Cases of a

Business Process Diagram

Getting to know the Business Process Diagram

Introducing the Business Process Diagram The Business Process Diagram is part of the Business Process Model and Notation (BPMN) and is the main diagram type for defining business processes. The diagram can include Start, Intermediate, End Events, Business Processes, Activities, Gateways and Pools and Lanes and more. The elements can be given a name and detailed descriptions can be added to the notes. By connecting the flow objects with connectors a sequence of activities and gateways and events can describe the business process. Order received C heck availability (^) Ship article undeliverable late delivery Procurement undeliverable late delivery Financial settlement Payment received Inform customer C ustomer informed Inform customer Remove article from catalogue Article removed Article available This BPMN Business Process Diagram shows the use of Intermediate Events to model particular temporal events that can be used to describe what happens during the execution of a Business Process. no yes A process hierarchy can be constructed by nesting Business Processes and Activities in the Project Browser and using the Child Diagram functionality to

enable drill down from the value chain level down to the lowest level processes.

Where to find the Business Process Diagram Ribbon: Design > Diagram > New > BPMN x.y > Business Process Project Browser Caption Bar Menu: New Diagram | BPMN x.y | Business Process Project Browser context menu: Add Diagram... | BPMN x.y | Business Process Usage of the Business Process Diagram Business Process Diagrams can be used to model the Business Processes in an entire organization or part of an organization. Business Processes can be created to represent the current or future state of the organization at any level of detail from the value chain down to a process performer level. A process hierarchy would typically be defined that would set the standards for the number of levels, naming, organisation of the processes and more. Options for the Business Process Diagram Business Process Diagrams can be drawn at different levels of formality from a Basic Flow Chart style of diagram used to represent a simple Business Process to a sophisticated diagram making use of many of the markers for Events and Activities to describe complex business processes. There is a toolbox which contains a range of elements, relationships and Patterns for creating the models.

The Business Process Diagram can also be used to generate Business Process Execution Language (BPEL) which is an XML language that can be ingested by a number of tools. The Business Process Diagram (like any diagram) can be viewed as an element list which makes working with the element's properties easier. Diagram Filters can also be used when presenting the diagrams to draw attention to parts of the diagrams. Learn more about the Business Process Diagram Business Process Diagram