Presentation is loading. Please wait.

Presentation is loading. Please wait.

Designer at the Strategy Level. Overview Establishing the why, who, when, and what of the business direction model Defining business objectives, critical.

Similar presentations


Presentation on theme: "Designer at the Strategy Level. Overview Establishing the why, who, when, and what of the business direction model Defining business objectives, critical."— Presentation transcript:

1 Designer at the Strategy Level

2 Overview Establishing the why, who, when, and what of the business direction model Defining business objectives, critical success factors, key performance indicators, and problems in the Repository Storing project documents Reporting on the business direction Establishing the why, who, when, and what of the business direction model Defining business objectives, critical success factors, key performance indicators, and problems in the Repository Storing project documents Reporting on the business direction

3 Establish a common understanding: –What the business wants to achieve –The priorities for information systems development Forms part of high level requirements definition Establish a common understanding: –What the business wants to achieve –The priorities for information systems development Forms part of high level requirements definition Why Document the Business Direction? Objectives Critical Success Factors Key Performance Indicators Problems Requirements Specification Business Direction Statement

4 Who Defines the Business Direction? Senior management Analysts and business users on business side Developers need the definition, but do not provide it! Senior management Analysts and business users on business side Developers need the definition, but do not provide it!

5 When Is the Business Direction Defined? As part of an Information Systems Strategy –Reviewed before the start of detailed analysis Before detailed analysis for every project As part of an Information Systems Strategy –Reviewed before the start of detailed analysis Before detailed analysis for every project

6 Facilities for Strategy Documentation Repository Navigator –Built-in categories for documentation –Organizational Features –Document Storage Diagrams –ERD and Process Models Reports User defined additions

7 The Business Direction Business Objectives Assumptions Critical Success Factors Key Performance Indicators Problems Business Objectives Assumptions Critical Success Factors Key Performance Indicators Problems

8 Business Objective A statement of business intent that can be measured quantitatively Examples: –To increase membership fee revenue by 30% by offering corporate memberships to local companies. –To reduce membership non-renewals from 20% to 10%

9 Critical Success Factor A Danger or Sine Qua Non Something which must be achieved if a business objective is to happen. Examples: –Membership creation must not be so complex that people are deterred from becoming members –Staff must not be rude to customers

10 Key Performance Indicator Something that can be measured that shows amount of progress toward a business objective Examples: –Rate of membership upgrade should be > 15% –Number of bonus months for members bringing in new members should be >20 per month

11 Problems Something that may inhibit progress toward an objective Examples: –Clerks do not know when memberships are near renewal –Clerks are not aware of the advantages of upgrading membership

12 Organization through association Association type: connect any two objects Build associations through matrix diagrammer and RON Documents can be stored and associated as well

13 Associating Business Direction Objects Business Process Objective Critical Success Factor Key Performance Indicator Problem Business Unit

14 Documents Store project documents in the Repository Use the Document element type Associate documents with other types of element Store project documents in the Repository Use the Document element type Associate documents with other types of element

15 Diagrams High level documentation of business processes High level documentation of information requirements

16 Reports Built-ins: Strategic Considerations Report User defined (using Developer Reports)

17 The Strategic Considerations Report Built-in Designer Report Assumptions Critical success factors Key performance indicators Objectives Problems Built-in Designer Report Assumptions Critical success factors Key performance indicators Objectives Problems

18 Summary The business direction statement: –A basis for the project –Defined by senior management –May be defined as part of the business plan Objectives, critical success factors, key performance indicators, and problems are specified Documented in Oracle Designer The business direction statement: –A basis for the project –Defined by senior management –May be defined as part of the business plan Objectives, critical success factors, key performance indicators, and problems are specified Documented in Oracle Designer

19 Hidden Slide This should be inserted at the end of a lesson.


Download ppt "Designer at the Strategy Level. Overview Establishing the why, who, when, and what of the business direction model Defining business objectives, critical."

Similar presentations


Ads by Google