System Architect
Tutorial
Popkin Software Part Number 2001-3 Printed in the U.S.A.
Popkin Software makes no representations or warranties with respect to the contents hereof and specifically disclaims any implied warranties of merchantability or fitness for any particular purpose. Further, Popkin Software reserves the right to revise this publication and to make changes from time to time in the content hereof without obligation of Popkin Software to notify any person or organization of such revision or changes. The software described in this document is furnished under a license agreement. The software may be used or copied only in accordance with the terms of the agreement. No part of this manual may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, for any purpose other than the purchaser’s personal use without the written permission of Popkin Software. You may use the .PDF files supplied with the software to print a maximum of four copies of this manual. If you need more than four copies, please contact Popkin.
The System Architect logo is a trademark of Popkin Software.
Publication No. 8.1244 Copyright 2001 Popkin Software & Systems, Inc. All rights reserved.
Table of Contents
Table of Contents
Table of Contents...... I Introduction ...... 1-1 The Project: An International Hotel Business...... 1-2 The Zachman Framework...... 1-3 The Popkin Enterprise Framework...... 1-5 Process Chart for Tutorial ...... 1-6 Getting Started ...... 2-1 Starting System Architect ...... 2-2 Creating/Opening an Encyclopedia...... 2-3 Set Preferences...... 2-6 An Explanation of Some Preferences ...... 2-7 Creating a Business Profile...... 3-1 Defining a Business Profile ...... 3-2 Review the Business Profile Definition...... 3-4 The Business Segment Profile...... 3-6 Adding a New Business Segment...... 3-8 Reviewing the Products and Customers ...... 3-9 Customers Profile...... 3-11 Reviewing Suppliers and Competitors ...... 3-13 Business Forces Summary ...... 3-15 Establish the Business Enterprise Direction...... 4-1 Business Enterprise Direction Model ...... 4-2 Review the Business Enterprise Direction Model...... 4-4 Mission Statement...... 4-5 Establish the Business Vision ...... 4-9 Establish Business Objectives ...... 4-11 Requirements ...... 5-1 Requirements...... 5-2 Business Objectives...... 5-4 Business Requirements ...... 5-5 Functional Requirements ...... 5-6 System Requirements...... 5-7 Technology Requirements ...... 5-8
I Table of Contents
Process Threads and Process Charts...... 6-1 Identifying Process Threads in the Organization...... 6-2 Reviewing the Process Charts Already Built ...... 6-4 Create a New Process Chart Diagram...... 6-8 Specify the Process Thread Represented by the Process Chart...... 6-9 Modeling the Process Flow of a Reservation Inquiry ...... 6-11 Drawing Sequence Lines ...... 6-14 Adding Swimlanes to the Process Chart Diagram ...... 6-17 Create More Swimlanes for Other Organizational Units ...... 6-19 Relating Roles to Processes ...... 7-1 Introduction to Matrices ...... 7-2 The Event to Result Matrix ...... 7-3 View the Results of Event-to-Result Matrix Correlations...... 7-6 Roles vs Elementary Business Processes...... 7-7 Relating Roles to EBPs via a Matrix...... 7-8 Process Decomposition ...... 8-1 To Create a New Process Decomposition ...... 8-2 Add a Primary Process Group...... 8-3 Add Process Threads...... 8-4 Update a Process Thread with EBPs...... 8-6 Building a Functional Hierarchy ...... 9-1 Examine the Functions of the Business ...... 9-2 Relate Business Processes to Functions...... 9-3 Create a Functional Hierarchy...... 9-5 Introduction to UML ...... 10-1 Object-Oriented Modeling ...... 10-2 This Tutorial -- A Use Case-Driven Approach...... 10-3 Opening the Tutorial Encyclopedia...... 10-6 Setting Preferences...... 10-9 Explanation of Some Preferences...... 10-10 Modeling With UML Use Cases...... 11-1 How to Model with Use Cases -- Discussion...... 11-2 Organize the Project with Packages ...... 11-4 Modeling Use Case Scenarios ...... 11-7 Create a Child UML Use Case Diagram ...... 11-12 Drawing the Child Use Case Diagram...... 11-13 Defining the Actors ...... 11-15 Define a Use Case with Steps...... 11-16 Create an Includes Relationship Between Use Cases...... 11-20 Extend a Use Case ...... 11-21
II Table of Contents
Tracking Requirements Against Use Cases ...... 11-23 UML Sequence and Collaboration Diagrams ...... 12-1 Sequence and Collaboration Diagrams...... 12-2 Create Sequence/ Collaboration Diagrams...... 12-4 Finding Objects By Examining Use Case Scenarios ...... 12-5 Create a Sequence Diagram...... 12-6 Adding Additional Objects to the Sequence Diagram ...... 12-9 Draw Message/Stimulus Lines Between Objects...... 12-12 Show Object Creation ...... 12-15 Complete the Sequence Diagram ...... 12-16 Adding a Method to a Message Line...... 12-19 Adding a New Method to a Class ...... 12-21 Create Collaboration Diagram...... 12-23 Add a Message to a Link...... 12-24 Modify a Message ...... 12-26 Synchronize Sequence Diagram ...... 12-27 UML Class Diagram...... 13-1 Create UML Class Diagram ...... 13-2 Begin a New UML Class Diagram...... 13-4 Building Relationships Between Classes ...... 13-6 Defining an Association...... 13-8 Adding Associations Between Other Classes ...... 13-11 Building Inheritance...... 13-12 Cross Referencing Class and Sequence Diagrams...... 13-15 Create a UML State Diagram ...... 13-18 Determine the States and Transitions for a Class...... 13-19 Drawing the State Diagram ...... 13-21 Defining a State...... 13-24 Mapping the Class Diagram to an ER Model ...... 13-26 Implementing the Design with Code (Java)...... 13-28 Generating Java ...... 13-29 Logical Data Modeling ...... 14-1 Logical Data Modeling...... 14-2 Creating a Subject Area of the Data Model...... 14-4 Creating a New ER Diagram ...... 14-5 Drawing Entity Symbols...... 14-7 Defining Entities ...... 14-10 Specifying Primary Keys...... 14-13 Creating New Data Elements in an Entity ...... 14-15 Drawing Relationship Lines...... 14-17 Updating Foreign Keys...... 14-19
III Table of Contents
Creating a Second Subject Area Diagram ...... 14-21 Creating a Model Diagram ...... 14-25 The Physical Data Model ...... 15-1 The Physical Data Model...... 15-2 Creating the Physical Diagram...... 15-4 The Physical Table...... 15-8 Display Options for a Table ...... 15-11 Modeling Constraints Between Tables...... 15-12 Generating Schema ...... 15-13 Reversing Database Designs...... 15-15 Reporting System...... 16-1 Opening System Architect Encyclopedia...... 16-2 Run a Pre-Written Report...... 16-3 Create a New Report...... 16-4 Select the Diagram Type...... 16-7 Select Diagram Properties to Print...... 16-9 Make Report Contain Symbols on Diagram...... 16-11 Select Entities As the Symbol Type...... 16-12 Select Entity Definition Properties To Print ...... 16-13 Select Entity Definition Properties ...... 16-15 Use "Is A" Relationship ...... 16-18 Final Report...... 16-20 HTML Publishing Tutorial...... 16-22 Opening The SA/HTML Generator...... 16-23 Select a Template Home Page ...... 16-25 Select the Publish Home Page...... 16-26 Selecting Diagrams ...... 16-27 Generate HTML...... 16-29 View the Results...... 16-30
IV 1 Introduction
Welcome to System Architect, the world's leading Enterprise Modeling Tool. In the this tutorial, we will tour through some of System Architect's extensive capabilities within Business Enterprise Modeling, UML, and relational data modeling techniques. We will examine the business operations of a fictional Hotel Chain, and undertake to build an e-Commerce Hotel Reservation System. We will use a scenario of the Popkin Process as a road map to model this business, and as we model, we will create artifacts against cells of the Zachman framework. Topics in this chapter Page The Project: An International Hotel Business 1-2
The Zachman Framework 1-3
The Popkin Enterprise Framework 1-5
Process Chart for Tutorial 1-6
1-1 Introduction
The Project: An International Hotel Business
In this tutorial, we will examine a fictitious International Hotel Chain. For argument's sake, we'll call this company Chelsea Hotels and Resorts. We will take a look at the business as it currently stands, determine problems that exist, and state Business Objectives that we would like to realize. Then we'll map these Business Objectives into lower-level requirements, and build models to show how the business should run to satisfy these requirements. We will then undertake the project to build a new e-Business reservation system for the hotel, using business process modeling, application modeling with UML, and relational data modeling. Chelsea is a chain of inns that has been around a number of years. The company has competed in the low-cost accommodations business segment by primarily providing rooms for cost-conscience families on vacation. The Restaurants business segment provides an on-site restaurant featuring home cooked food catering to families. The company has recently begun to expand its business, entering the resort business segment (and thus adding the word Resorts to its name), and the business travel segment. The management at Chelsea has realized that an effective Internet presence is crucial to compete in these business segments. Company management has determined that this does not simply mean designing a pretty site to introduce the company. The companies main focus is to examine business functions and processes, while making sure that the company is operating efficiently and without redundancy. They want to integrate a website into the business processes. As part of this effort, the company has determined that they want to build an effective on-line reservation system. Chelsea's high-level business objectives can be summarized as stated: • Create a market presence as a leader in resort travel • Create a market presence as an ideal solution for business travel • Achieve Sales Growth of 20 % per year for next 5 years • Create efficient on-line Reservation System • Integrate website with improved business processes.
1-2
The Zachman Framework
The Zachman Framework
The Zachman Framework for Enterprise Architecture, developed by John Zachman, provides a common vocabulary and set of perspectives-a framework-for defining and describing complex enterprise systems. It is a logical structure for classifying and organizing the elements of an enterprise that are important to both the management of the enterprise and the development of its information systems. The Zachman Framework was initially published in 1987, and has evolved to become the model around which major organizations worldwide view and communicate their enterprise information infrastructure. Not a Method, But a Tool for Thinking The Zachman Framework is not a method, nor is it a specification for the diagram notations that should be used to capture information at various stages. It is simply a very important tool for thinking about the information that needs to be gathered about a business and its systems, for classifying that information, and for seeing how different parts of the enterprise need to share information. The columns of the Zachman Framework specify the type of information to be captured - the who, what, why, when, where, and how of modeling a business and its systems. the rows of the Zachman Framework specify the stages of development - starting at Contextual, then Conceptual, then Logical, then Physical, then Implementation, and finally, Finished system.
1-3
Introduction
Figure 1-1 Zachman Framework.
1-4
The Popkin Enterprise Framework
The Popkin Enterprise Framework
The Popkin Enterprise Framework maps each cell of the Zachman Framework to a System Architect diagram or definition. During this tutorial, we will use a subset of the diagrams and definitions in the Popkin Enterprise Framework to model the Chelsea Hotels and Resorts business. We will ' walk' a path through the framework, selecting various diagram and definition types to capture information about our business. The path that we walk, will be labeled a scenario. It is only one of a number of equally correct paths to walk. Figure 1-2 Definitions and diagrams that map System Architect to the Zachman Framework.
1-5
Introduction
Process Chart for Tutorial
The Popkin Process is a guide for building Enterprise systems with System Architect. A copy of it is installed with System Architect, and is located in the System Architect/Manuals directory. For this tutorial, we will use a scenario of the Popkin Process to model the Chelsea Hotels and Resorts business. We depict this scenario as a workflow diagram called a Process Chart. We will walk this scenario during this tutorial, using it as a road map, and taking a closer look at it. Figure 1-3 Process Chart describing road map for this tutorial.
1-6
2 Getting Started
In this chapter… In this chapter we will create a new project, select the methods and notations we will use in this tutorial, and set the drawing preferences.
Topics in this chapter Page Starting System Architect 2-2
Creating/Opening an Encyclopedia 2-3
Set Preferences 2-6
An Explanation of Some Preferences 2-7
2-1 Getting Started
Starting System Architect
To start System Architect: 1. Run System Architect from the Start, Programs menu or double-click on the System Architect program icon. The product screen and the Audit Id dialog will appear. 2. In the Audit Id dialog box, type a personal identifier of up to 7 characters. This identifier will automatically be added to all diagrams and dictionary definitions you create or modify in your encyclopedia. Click OK. Note: If you are using the network version of System Architect, you will not see the same Audit Id dialog box. Instead you will be asked to enter your network password which will be used in the place of your Audit Id.
2-2 Creating/Opening an Encyclopedia
Creating/Opening an Encyclopedia
The System Architect encyclopedia is a relational database in a single sub-directory on your computer. Whether you're working on a stand-alone PC, or as part of a network in a client/server system, the relationship between the encyclopedia and a sub-directory is 1-to-1. That is, the encyclopedia is in a sub-directory; one sub-directory contains just one encyclopedia. All the diagrams and all the definitions, both those associated with diagrams and those that aren't, are in the encyclopedia. If you have several projects, you may have several encyclopedias, but that's entirely an individual decision. For example, you can build an enterprise encyclopedia in which you keep all the information relating to your company's standards as well as information that has been used in old projects. When the company decides to start a new project, such as an Accounts Payable (AP) system, those parts of the enterprise encyclopedia that should be used as a "leaping off point" for the AP system are exported to a new encyclopedia. And after the AP system is completed, some of the information discovered in the process of designing that system might be merged into the enterprise encyclopedia. Creating/Opening an Encyclopedia We will open an encyclopedia that has already been populated with some of the systems we will build. The project encyclopedia we will open for is called Tutorial. Important Note: In this tutorial, we will model in the encyclopedia provided called Tutorial, using information already provided in it as a starting point. If other team members have already taken this tutorial and modified the Tutorial encyclopedia, you may want to start with a fresh version of this encyclopedia as a starting point. A zip file, Tutorial.zip, is provided in the Tutorial directory. It provides a fresh version of the Tutorial encyclopedia. You should unzip this file to a new path before beginning these exercises.
2-3 Getting Started
To open the Tutorial encyclopedia with System Architect: 1. From the File menu, select Open Encyclopedia. The Encyclopedia Open dialog appears. The Samples encyclopedia within the Existing tab is selected by default. 2. Choose a project by selecting the Browse button on the Existing tab to reveal all of the project encyclopedias in this folder. Select the Tutorial encyclopedia and choose OK. Figure 2-1 Select and open Tutorial encyclopedia.
3. If not already selected, toggle on Load this project at startup, located at the bottom left of the encyclopedia open dialog. This will make this encyclopedia the default encyclopedia that will automatically open each time you start the product. 4. Click OK to load the project.
2-4 Creating/Opening an Encyclopedia
Property Configuration: Next, let's take a look at the Property Configuration dialog box to see what methods, diagram types, and target languages are selected for this project encyclopedia. These can be changed at any time during the project. 1. Select Tools, Customize Method Support, Encyclopedia Configuration to open the System Architect Property Configuration dialog. You will notice that the encyclopedia has been configured for Entity Relation Data Modeling, Enterprise Business Modeling, and UML, among other things. We have chosen Oracle as the Target Database and Java as the Target Language as shown below. Figure 2-2 Specify methods and properties to model with.
Note: You can change the Property Configuration at any time using the Customize Method Support, Encyclopedia Configuration command from the Tools menu. After making changes you must reopen the encyclopedia for the changes to take effect.
2-5 Getting Started
Set Preferences
Now you are almost ready to begin the tutorial project. However, first you need to set your preferences for how System Architect will react to your drawing commands. System Architect offers many optional drawing and tool behavior features. They can be turned on or off at any time with the Preferences dialog. To set Preferences: 1. From the Tools menu, select Preferences. The Preferences dialog box appears. 2. In the preference Auto dialog, click number as displayed below. 3. Click OK to close out the preferences dialog. Figure 2-3 Set preferences for drawing and behavior.
2-6 An Explanation of Some Preferences
An Explanation of Some Preferences
Here are explanations for some of the major settings chosen in the picture on the previous page:
Note: For a fuller explanation of the Preferences dialog, go to the Help menu and select Help for the On-line Help System. You can also find this information in your System Architect User Guide or System Architect Tutorial manual, as well.
2-7 3 Creating a Business Profile
What is a Our first step in modeling Chelsea Hotels and Resorts is to establish Business what the business is currently about. We will capture some of this Profile? information in a Business Profile definition. Within this definition, we'll get a handle on the company's products, services, customers, suppliers, competitors, the business segments it operates in, and other forces impacting the business.
In this chapter… In this chapter we will establish a Business Profile for the hotel. This process will clarify areas on which the business needs to focus. In essence, we will lay the foundation on which to develop our business vision. Topics in this chapter Page Defining a Business Profile. 3-2
Review the Business Profile Definition 3-4
The Business Segment Profile 3-6
Reviewing the Products and Customers 3-9
Customers Profile 3-11
Reviewing Suppliers and Competitors 3-13
Business Forces Summary 3-15
3-1
Creating a Business Profile
Defining a Business Profile
The picture below shows where we are in the business modeling scenario that we are following for the tutorial.
In summary, the Business Profile will contain the following information: Business Segments Profile summarizing key information about the different lines of business or market segments. Products and Services Profile summarizing key information about the different product and service categories within each business segment to be considered further. Customers Profile summarizing key information about the different customer types within each business segment that will be considered further.
3-2 Defining a Business Profile
Suppliers Profile summarizing key information about the different supplier types used by the company. Competitors Profile summarizing key information about the competitors within each business segment. Business Forces Summary highlighting the financial, regulatory, and other forces that impact the company. This identifies any pressures or constraints imposed on the company that restrict freedom or suggest a focus for business change in redesigning business processes or organizational structure.
3-3 Creating a Business Profile
Review the Business Profile Definition
Let's examine the Business Profile for Chelsea already created in the Tutorial encyclopedia. 1. Select the All Methods tab in the browser, and click on the + mark next to Definitions, to reveal a list of all definition types. (Note: if your browser has been narrowed in width, the All Methods tab will be truncated to All). 2. Click on the + mark next to Business Profile, to reveal the Chelsea Hotels and Resorts definition. Figure 3-1 Open the Business Profile definition for Chelsea Hotels and Resorts.
3-4 Review the Business Profile Definition
3. Double click on the definition Chelsea Hotels and Resorts or right-mouse click on it and select Open. The definition dialog for Chelsea Hotels and Resorts opens, as shown below. Figure 3-2 View the Business Profile definition.
Notice that there are four tabs of information for the business profile. The first tab provides a text box for Description. You will see a Description text field in just about every definition type that you run across in System Architect. It provides you with a place to put a general text description of the item. In the upcoming sections we will examine and add to the information in the Business Profile definition.
3-5 Creating a Business Profile
The Business Segment Profile
The first tab of the Business Profile definition provides a list of Business Segments. Every business operates within one or more business segments. Within each business segment conditions will vary, including the competition, types of customers, profit margins, and marketing approach. For example, Chelsea Hotels and Resorts operates in the Accommodations segment and the Leisure segment. As we mentioned in the previous chapter, they are looking to get into the Resort segment and the Business Travel segment. Within the Business Travel segment, hotel services, customers, competitors, and marketing approach will be different than the Accommodations segment.
Note: In the Business Segments list box, notice that Accommodations and Restaurants are already listed. To review information about these segments, select the segment and click on the Define button at the bottom of the list box.
Let's add the two business segments that Chelsea is now trying to compete in - Business Travel and Resorts. One of these segments, Resorts, is already defined in our project encyclopedia -- we will reuse it. The other segment, Business Travel, we will add anew. 1. Under Business Segment Profile, click on the Choices button in the lower right corner of the dialog. The Select and Drag dialog gives you a list of all definitions of this type already in the project encyclopedia. 2. Right-mouse click anywhere on the white area in the Select and Drag dialog and click on Details to open a window that provides a summary of each item as you select it. 3. Select and hold (with your left mouse button) the Resorts business segment and drag it into the top of the list, then release it so that it is added to the list. Once added, you may highlight Resorts and click on the Define button to see its full definition.
3-6 The Business Segment Profile
Figure 3-3 Reuse a business segment definition from the underlying repository.
3-7 Creating a Business Profile
Adding a New Business Segment
You can (optionally) add a new business segment to the project. 1. Place your cursor in the top line of the Business Segment Profile list box and type in Business Travel, then click Add. 2. To define the Business Travel business segment, highlight it and click the Define button. 3. Complete the appropriate sections of the dialog with the information provided below: Description Certain hotels will be targeted toward the business traveler. Characteristics All accommodations are geared toward business traveler - all rooms include phone data link, iron and ironing board, free copy of local daily newspaper, and continental breakfast. Critical Issues In the U.S., the price should conform to government per-diem allowances. 4. Click OK. You will return to the Business Profile definition dialog.
3-8 Reviewing the Products and Customers
Reviewing the Products and Customers
To understand the business, you must fully understand what your Products are and who your Customers are. Let's take a look at those already entered in the business profile definition for Chelsea Hotels and Resorts. 1. Click on the Products and Customers tab, and look at the Products/Services list box. You can look at the definitions behind the products listed (Restaurants, Leisure Facilities, and Conferences) at your leisure, but for this tutorial, we will examine Rooms. Figure 3-4 Review the products and customers of the hotel chain.
2. Select Rooms and click Define, to open the definition dialog for Rooms. Note that a product/service type, in this case Rooms, includes a brief description (as does every definition type in System Architect), key characteristics, and critical issues. A product/service may also be categorized.
3-9 Creating a Business Profile
Categories: You may categorize a product, service, or customer. In this example Rooms are categorized into standard rooms, suites, and business traveler rooms. We might also categorize rooms into smoking rooms, non-smoking rooms, rooms with king-sized beds, rooms with two double beds, etc.
For the Room product, you can see that rooms in the hotel have been categorized into three different types - Suites, Standard Room, and a new category invented to cater to the business traveler - a Business Traveler Room. 3. Select Business Traveler Room, and click on Define. 4. View the pages of this definition - you will notice a brief description of what this room should provide, and a description of the needs and values of the customer to this product. On page 2 of this definition, the relative size and growth of this type of product are described in very general terms. 5. Click OK to close the Business Traveler Room dialog. 6. Click OK again to close the Products/Service Profile – Rooms.
3-10 Customers Profile
Customers Profile
A hotel has many types of customers - you should distinguish them by major types, and then categorize within those types. For example, there are business travelers and vacationers. For vacationers, you might categorize by budget-minded vacationers, Resort vacationers, and honeymooners. You might also list major customers independently, especially if they exert a certain influence on the hotel by themselves. Let's take a look at Vacationers: 1. Within the Customers Profile dialog, select Vacationers and press Define as shown below. The Customer Profile - - Vacationers definition dialog appears. Figure 3-5 Open the definition of a customer profile.
Defining the Customers Notice that Vacationers have been categorized by Honeymooners, Budget-minded Vacationers, and Resort Vacationers. Each of these different types of customers will have very different needs and values. For example: 2. Select Resort Vacationers and click Define. Notice that this type of customer has very special values and needs that you need to accommodate if you hope to succeed in this business segment.
3-11 Creating a Business Profile
Figure 3-6 View the definition of the Resort Vacationers category.
3. Click OK to close the Resort Vacationers dialog, and the Vacationers dialog, to get back to the Chelsea Hotels and Resorts Business Profile dialog.
3-12 Reviewing Suppliers and Competitors
Reviewing Suppliers and Competitors
An important part of understanding the business is understanding who your suppliers are and how dependant you are upon them, and who your competitors are, and how and in what markets you compete against them. Oftentimes, a competitor can also be a supplier and also a customer, or even a partner. Suppliers Profile Let's take a look at a supplier: 1. Click on the Suppliers and Competitors tab. 2. Tribeca Textiles is listed in the Suppliers Profile list box. Select it and press the Define button at the bottom of the list box. Definition of the Supplier 3. Review the tabs of information that have been gathered about this supplier: • Critical Issues are listed in the Characteristics tab. • This supplier has established business with Chelsea Hotels and Resorts by competitive procurement, which is modeled in the Relationship tab. • This supplier only delivers on Tuesday and Friday mornings -- this is modeled in the Relative Power tab, as Suppliers Can Impose Processes. 4. Click OK to close the Suppliers Profile dialog. Competitors Profile Within the Competitors Profiles list box you may list individual competitors, or competitor types. There are already two listed for Chelsea Hotels and Resorts - Bed and Breakfasts and Major Hotels. Let's take a look at a competitor: 5. Under Competitors Profile, select Bed and Breakfasts and press Define as shown below.
3-13 Creating a Business Profile
Figure 3-7 Open the definition of a competitor profile.
Definition of the Competitor 6. Review the tabs of information that have been gathered about this competitor and then click OK to close the Bed and Breakfasts competitors profile.
3-14 Business Forces Summary
Business Forces Summary
Within the Business Forces section of the business profile, you try to get a handle on the financial, regulatory, and other business forces affecting the company. You create one Business Forces profile for the company. Defining the Business Forces Summary Let's take a look at the business forces affecting Chelsea Hotels and Resorts: 1. Click on the Business Forces Summary tab. 2. Select Chelsea Business Forces and click on the Define button. Tour the various tabs of the definition and view the textual information summarizing some of the business forces at work. Figure 3-8 View the business forces summary.
3. Close all dialogs by clicking OK to each one.
3-15 4 Establish the Business Enterprise Direction
What is the A Business Enterprise Direction Model analyzes the strategy of Business the business, including the mission, business objectives and goals, critical success factors, critical business issues, and specific Enterprise strategies. Direction? In this chapter… In this section of the tutorial we will establish the Business Enterprise Direction of Chelsea Hotels and Resorts. In the last section we established its Business Profile -- what it currently does; now we will establish where we want to take the business. Topics in this chapter Page
Business Enterprise Direction Model 4- 2 Review the Business Enterprise Direction Model 4-4 Mission Statement 4-5 Establish the Business Vision 4-9 Establish Business Objectives 4-11
4-1
Establish the Business Enterprise Direction
Business Enterprise Direction Model
The next step in Contextual modeling that we will perform is to examine the Business Enterprise Direction for the hotel chain. We want to establish the high-level goals of the business, the business objectives, mission statement, etc. Information entered here will set the context of the modeling we will do. This information can later be disseminated through automatic reports. The picture below shows where we are in the business modeling scenario that we are following.
General The Business Enterprise Direction Model analyzes the strategy of the business. It covers the future business vision and the accompanying case for action. With the framework of the model you will identify the key business policies and rules that govern the choices for business change. The Business Enterprise Direction Model consists of the following components: Mission Statement -- a brief, succinct declaration of what the enterprise exists to do. It should identify the enterprises purpose, general product lines, target customer segments, and intended level of performance. Business Objectives -- specific results or long-term objectives that the enterprise wants to achieve in a three- to five-year time period, usually via a series of shorter-term goals. The objectives, generally between five and ten, should be measurable and state specific measurements of success.
4-2 Business Enterprise Direction Model
Specific Strategies -- represent the direction the enterprise will take to achieve its Business Objectives. The strategies state how the objectives will be achieved and are therefore subordinate to the objectives themselves. Critical Success Factors (CSFs) -- a few key circumstances, generally ten or fewer, that must occur in order for the enterprise to fulfill its mission. Critical Business Issues (CBIs) -- opportunities, problems, trends, competitive threats, or regulatory situations causing the enterprise to take action at the current time. Balanced Scorecard -- a one-page summary of the most critical measures of the company, grouped into four perspectives: 1) Customer, 2) Internal business, 3) Innovation and learning, and 4) Financial. Case for Action -- may apply on an enterprise level or on a business area level. This is a clear and succinct summary of the primary business issues that have led to the current initiative and are raising the sense of urgency for change. Business Vision -- may apply to the entire enterprise or to a specific business area. This describes what it will be like when the transformations within this area are complete. Key Business Policies -- statements that identify the major policies necessary for the new system concepts to work. Business Rules Comparison -- identifies old unwritten rules and assumptions under which the business area has operated in the past and possible new rules under which it will operate in the future.
4-3 Establish the Business Enterprise Direction
Review the Business Enterprise Direction Model
Let's examine the Business Enterprise Direction for Chelsea already created in the Tutorial encyclopedia: 1. Select the All Methods tab in the browser, and click on the + mark next to Definitions, to reveal a list of all definition types. 2. Click on the + mark next to Business Enterprise Direction, to reveal the Chelsea Hotels and Resorts definition. Double-click on this definition or right-mouse click on it and choose Open. The definition dialog for the hotel's Business Enterprise Direction appears. We will fill in some of the information. Figure 4-1 Open the Business Enterprise Direction definition.
4-4 Mission Statement
Mission Statement
What is the mission of the company? Why does the company exist -- what good does it hope to achieve. If the leaders of the company have a mission in mind, do the employees have a clear understanding of what it is? Do the customers know? Before undertaking any more modeling of the business, we will define the mission statement of Chelsea Hotels and Resorts.
Description The first page of the Mission Statement tab of the Business Enterprise Direction dialog contains the generic Description property as well as the Mission Statement and Specific Strategies. By default, every definition dialog in System Architect contains a description property - you generally enter general information concerning this definition in itself; in this case we might enter some text concerning this Business Enterprise Direction definition - for example, is this the Business Enterprise Direction for the whole company or just a division; is it a suggested direction or is it clad in stone, are there time limits to it, etc. The Description property just happens to fall within the Mission Statement tab, which is for the overall Business Enterprise Direction definition.
1. Examine the Description field of the Business Direction of Chelsea Hotels and Resorts. It contains the following text:
This sets forth the Business Enterprise Direction for the next 5 years. Mission 2. From examining the Business Profile, we now have a Statement good feel for what the company currently does. Examine the Mission Statement for Chelsea Hotels and Resorts. You can change it if you like, but what we've filled in is:
We will provide the business traveler with a consistently excellent experience at a moderate cost. We will also provide premier resorts for vacation travel. 3. Examine the high-level Specific Strategies listed for how Chelsea will attempt to achieve this mission:
Marketing, pricing, and accommodations will be targeted to business travelers. We will increase participation in conferences in hotels located in major conference cities.
4-5 Establish the Business Enterprise Direction
Figure 4-2 Business Enterprise Direction definition.
Critical Success Now let's examine Critical Success Factors (CSF) and Critical Factors/Critical Business Issues (CBI) of Chelsea Hotels and Resorts. Business Issues Critical Success Factors Critical Success Factors (CSFs) are key circumstances that must occur in order for the enterprise to fulfill its mission. There are generally no more than 10 CSF's for a business, each described by five to ten statements describing what the enterprise wishes to achieve. 1. Within the Business Enterprise Direction definition, click on the CSF/CBI tab. Take a look at the first page of this tab, in which the Critical Success Factors are listed. 2. Click on the small rectangle in the bottom right-hand corner of this dialog to expand the list.
4-6 Mission Statement
3. View the critical success factors listed: Business Traveler Repeats Beach-front properties for Resorts Strong partnerships with Travel Agents Be recognized as leading resort hotel Critical Business Issues Critical Business Issues are opportunities, problems, trends, competitive threats, or regulatory situations requiring action or resolution. Let's examine some of the Critical Business Issues for Chelsea: 4. Within the CSF/CBI tab, click on the page arrow in the top of the dialog to move to page 2, revealing a list of Critical Business Issues: Figure 4-3 Examine Critical Business Issues.
4-7 Establish the Business Enterprise Direction
5. View the critical business issues listed: On-line reservation system is mandatory Interest rates are rising globally Exchange rate in South America
A Case for Action A Case for Action is a clear summary of the primary business issues leading to this initiative and raises the sense of urgency for change. 6. Examine the Case for Action: The company has experienced no real growth over last eight years. Market surveys show company is known for moderate accommodations in dated facilities that appeal most to cost-conscience family vacationers. Hotel rankings are very low in two fastest growing travel market segments - business travel and premier resort accommodations.
4-8 Establish the Business Vision
Establish the Business Vision
In the next section of the Business Enterprise Direction dialog we'll take a look at the Business Vision, Key Business Policies, and the Business Rules Comparison. The Business Vision describes the future vision of the business enterprise. 1. Within the Business Enterprise Direction definition, click on the Business Vision tab, and view the information. Business Vision: The hotel will become a major force in the areas of business travel and exotic resort vacations. The hotel name will become synonymous with an elegant, professional atmosphere for the business traveler at moderate rates. Business travelers will take their families back to the hotel and to its resorts for vacations. Key Business Policies: Web site will be the most advanced in the field for reservations. Its content will reflect the business vision. It will become a site that the casual web surfer will go to for travel.
4-9 Establish the Business Enterprise Direction
Figure 4-4 Examine the Business Vision.
Business Rules Comparison In Business Rules Comparison, we record the present state and future state of business rules as we identify, challenge, and redefine them based on the new enterprise direction. Take a look at the Business Rules Comparison: 2. Examine the Old Rules. Rely on established base of family vacationers. 3. Examine the New Rules. Recruit business travelers to return for vacations.
4-10 Establish Business Objectives
Establish Business Objectives
From the Introduction to the Hotel Example, we started with five business objectives: • Create a market presence as a leader in resort travel • Create a market presence as an ideal solution for business travel • Achieve Sales Growth of 20 % per year for next 5 years • Create efficient on-line Reservation System • Integrate website with improved business processes These business objectives should be part of Chelsea's Business Enterprise Direction. Let's add them: 1. Return to the Mission Statement tab of the Business Enterprise Direction definition, and click on the Page arrow in the top of the dialog to move to page 2, revealing an empty list box for Business Objectives. 2. Enter the business objectives listed above by typing each one in and pressing Add (do not include any periods as you type). 3. Click OK to close the Business Enterprise Direction dialog.
4-11 Establish the Business Enterprise Direction
Figure 4-5 Open the Business Enterprise Direction.
4-12 5 Requirements
Business The purpose of our modeling effort is to capture requirements for the Objectives and business, and make sure that those requirements are met by the Multi-Level processes we have in place and the systems we build. Generally, there are many levels of requirements, starting with high-level Requirements business objectives, which fan out into business requirements, which fan out into system requirements, which fan out into technology requirements, etc. System Architect enables you to capture these and other requirement types, and attach them to your models. Later, you can run reports or view matrices to see what the requirements are, how they have been met, and if one changes, what parts of the system are affected.
In this Chapter… We will establish the business objectives for our hotel business example, and look at how we will capture lower-level requirements. Topics in this chapter Page Requirements 5-2 Business Objectives 5-4 Business Requirements 5-5 Functional Requirements 5-6 System Requirements 5-7 Technology Requirements 5-8
5-1 Requirements
Requirements
As we model Chelsea Hotels and Resorts, we must be aware of our high-level business objectives. Business objectives will result in a more refined set of business requirements. The business requirements must be fulfilled by the business processes and data that the processes deal with. Business requirements will later yield functional requirements for the systems that we build. As we move to design, the functional requirements will yield systems requirements, and as we move to implementation of the systems, we will deal with technology and architectural requirements. Out of the box, System Architect provides Business Objective and Requirement as definition types. Since Popkin Software cannot possibly know what each customer wants to capture as properties of a requirement, both of these definitions present a suggested property set (ie, for a Requirement, you may enter Source Document, Author, etc). Each user will generally have their own particular properties that they need to capture. In addition, each user generally has different terminologies for lower-level requirements - for example, in this tutorial we will talk about Functional, System, and Technology requirements - but this will not be what every user calls lower-level requirements in their organization. To facilitate this, we will use System Architect's ability to create new definition types, and modify the properties of existing definition types, with its customizable metamodel and USRPROPS.TXT. A full explanation of USRPROPS.TXT is provided in the help system and the User Guide. For now, we want to establish a few basic rules on how you would handle requirements in your organization with USRPROPS.TXT and System Architect. Basic Rules for Requirement Capture with USRPROPS.TXT The basic rules for requirement capture with USRPROPS.TXT are: Decide upon what requirement types you will be gathering - for example, Business Objectives, Business Requirements, Functional Requirements, System Requirements, etc. For each new Requirement type definition, establish the properties for that requirement type that you will be capturing. Decide what model elements you will be associating requirements against.
5-2 Requirements