Emerging Role

Advanced Business

Analysis Workshop

Ask the Experts

Requirements Management Tools

Book Review

Software Requirements:Styles and Techniques

Business Analyst

Certification

New Course

the CONNECTING BUSINESS REQUIREMENTS TO TECHNOLOGY

Summer 2004

Emerging Roleof the

Business Analyst

Emerging Roleof the

Business Analyst

letter from the editors

Welcome to our first issue of the bridge. We have decided that it is time for Business Analysts and those

doing requirements gathering to have a publication that focuses on analyzing, documenting and

recommending solutions for our organizations. Our goal for this publication is to enhance your job by providing

you with the latest information, tools, and techniques used by Business Analysts around the country. The

importance and visibility of Business Analysts has become heightened, while the scope of their work in the

software application development process is expanding. Whether your title is Project Manager, Operations

Manager, Systems Analyst, Quality Assurance Analyst, or Marketing Associate, you may be performing the role

of a Business Analyst.

In this issue, you will find an article describing how B2T Training and other industry experts have seen the

Business Analyst role change over the years and our predictions for the future of this role. We discuss the important

issue of Requirements Management in our Ask the Experts section. Managing requirements continues to be a

challenge as we try to streamline our processes and expand our businesses globally. We have highlighted two

Requirements Management tools, DOORS and iServer, that are helping many organizations maintain control of

this important corporate asset. Our column, called Did you Know?, provides tips for utilizing Visio to enhance your

Requirements Packages.

In late 2002, we began offering our Business Analyst Certification Program. This program is unique in the

industry in that it certifies Business Analysts in two areas: their knowledge of business analysis techniques and

their ability to perform the essential or critical skills to be a Certified Business Analyst. This has been a very

successful program and we are pleased that so many are enrolled and completing the program. As an

opportunity to continue the development of experienced Business Analysts, we have developed a new course:

Advanced Business Analysis Workshop. See our detailed outline on page 7.

We hope you find this publication informative and helpful with your analysis work. We encourage you to

write to us with your questions for our Ask the Experts column and offer suggestions for future articles that

would be of interest to you.

TINA JOSEPH BARBARA CARKENORD

A N N O U N C I N G

We are excited to announce a new professional association called the International

Institute of Business Analysis. The group held its first annual meeting in Toronto, in March 2004. The purpose of the association is “To be the leading world-wideprofessional association developing and maintaining standards for the practice of

Business Analysis and for the certification of practitioners.” Their first order of business is to develop a Business Analysis Body of Knowledge.

B2T Training has joined this association because our vision of the role of the Business Analyst is consistent with the proposed goals of the IIBA. We feel that it is critical for Business Analysts to have a professionalorganization to support their career efforts. One of the committees that we will be working with will be definingthe industry accreditation and we will work towards making the B2T Training Certification transferable to theIIBA Certification.

To learn more about IIBA, visit the website at www.iiba.com.We encourage you to join and participate through

active involvement in the committees and various groups.

�

t a b l e o f c o n t e n t sEmerging Role of the Business Analyst

Ask the ExpertsRequirements Management Tools

New Course: Advanced Business Analysis Workshop

Business Analyst Certification Program

Book ReviewSoftware Requirements: Styles and Techniquesby Soren Lauesen

Did You Know?MS Visio Professional

Core Courses

Essential Skills for the Business Analyst

Detailing Business Data Requirements

Detailing Process and Business Rule Requirements

Additional Course Offerings

Requirements Testing for the Business Analyst

Overview of Business Analysis

B2T Training • 11795 Northfall Lane, Suite 601 • Alpharetta, GA 30004 • 865-675-2125

B2T Training is a woman-owned small business based in Atlanta, GA. Our training focuses on proven skillsand techniques to define and scope the business problem, gather requirements, document the requirements,model the requirements, and follow through with the development of business requirements test plans toensure the project has met its defined objectives.

Our training is offered nationally and on a limited international basis. Most of our classes are taught onsiteand are tailored to the unique environments of each organization. Public classes are also available in variouscities around the US.

Vice President, Sales and MarketingTina Joseph

©2004 B2T Training. All rights reserved.

the

Summer 2004

3

5

6

7

7

8

9

10

the bridge l Summer 2004 2

Vice President, TrainingBarbara A. Carkenord

Director of Business DevelopmentAngie Perris

volume 1 l issue 1

��

��

�

Software application development has only been around since the late1970’s. Compared to other industries

and professions the software industry is stillvery young. Ever since organizations beganto use computers to support their businesstasks, the people who create and maintainthose “systems” havebecome more and moresophisticated and special-ized. This specializationis necessary because as computer systemsbecome more and morecomplex, no one personcan know how to doeverything.

One of the “special-ties” to arise is theBusiness Analyst. Although some organiza-tions have used this title in non-IT areas ofthe business, it is an appropriate descriptionfor the role that functions as the bridgebetween people in business and IT. Theuse of the word “Business” is a constantreminder that any application softwaredeveloped by an organization should furtherimprove its business operations, either byincreasing revenue, reducing costs, orincreasing service level to the customers.

History of the BusinessAnalyst Role In the 1980’s when the software develop-ment life cycle was well accepted as a neces-sary step, people doing this work typicallycame from a technical background and were

working in the IT organization. They under-stood the software development process andoften had programming experience. Theyused textual requirements along with ANSIflowcharts, dataflow diagrams, database dia-grams, and prototypes. The biggest com-plaint about software development was the

length of time required todevelop a system that didn’talways meet the businessneeds. Business people hadbecome accustomed tosophisticated software andwanted it better and faster.

In response to thedemand for speed, a classof development toolsreferred to as CASE(Computer Aided

Software Engineering) were invented.These tools were designed to capturerequirements and use them to manage asoftware development project from begin-ning to end. They required a strict adher-ence to a methodology, involved a longlearning curve, and often alienated thebusiness community from the developmentprocess due to the unfamiliar symbols usedin the diagrams.

As IT teams struggled to learn to useCASE tools, PCs (personal computers)began to appear in large numbers on desk-tops around the organization. Suddenlyanyone could be a computer programmer,designer and user. IT teams were still per-fecting their management of a centralmainframe computer and then suddenly

3 Summer 2004 l the bridge

What has happened over the last few years andwhat to look for in the future.

What is a Business

Analyst?

A business analyst is aperson who acts as aliaison between businesspeople who have abusiness problem andtechnology people whoknow how to createautomated solutions.

Emerging Roleof the

Business Analyst

had hundreds of independent computers to manage. Client-server technologiesemerged as an advanced alternative to thetraditional “green screen,” keyboard-basedsoftware.

The impact on the software develop-ment process was devastating. Method-ologies and classic approaches to develop-ment had to be revised to support the newdistributed systems technology and theincreased sophistication of the computeruser prompted the number of softwarerequests to skyrocket.

Many business areas got tired of waitingfor a large, slow moving IT department torollout yet another cumbersome applica-tion. They began learning to do things forthemselves, or hiring consultants, oftencalled Business Analysts, who would reportdirectly to them, to help with automationneeds. This caused even more problems forIT which was suddenly asked to supportsoftware that they had not written orapproved. Small independent databaseswere created everywhere with inconsistent,and often, unprotected data. During thistime, the internal Business Analyst role wasminimized and as a result many systemsdid not solve the right business problemcausing an increase in maintenance expens-es and rework.

New methodologies and approacheswere developed to respond to the changes,RAD (rapid application development),JAD (joint application development), andOO (object oriented) tools and methodswere developed.

As we began the new millennium, theInternet emerged as the new technologyand IT was again faced with a tremendouschange. Once again, more sophisticatedusers, anxious to take advantage of newtechnology, often looked outside of theirown organizations for the automation theycraved. The business side of the organiza-tion started driving the technology as neverbefore and in a large percentage of organi-zations began staffing the Business Analystrole from within the operational unitsinstead of from IT. We now haveMarketing Directors, Accountants,Attorneys, and Payroll Clerks performingthe role of the Business Analyst.

In addition, the quality movement thathad started in the 70’s with TQM, cameinto focus again as companies looked forways to lower theircost of missed require-ments as they expand-ed globally. The ISO(InternationalStandardsOrganization) setquality standards thatmust be adhered towhen doing interna-tional business.Carnegie Mellon created a softwaredevelopment qualitystandard CMM(Capability MaturityModel). Additionally,Six Sigma provided adisciplined, data-driv-en quality approach toprocess improvement aimed at the near-elimination of defects from every product,process, and transaction. Each of thesequality efforts required more facts and rigorduring requirements gathering and analysiswhich highlighted the need for more skilledBusiness Analysts familiar with the business,IT, and quality best practices.

Future of the BusinessAnalyst RoleToday we see Business Analysts comingfrom both the IT and business areas. In thebest situations, the Business Analyst todayhas a combination of IT and business skills.Each organization has unique titles forthese individuals and the structure ofBusiness Analyst groups are as varied as thecompanies themselves. However, there is acore set of tasks that most Business Analystsare doing regardless of their background ortheir industry.

The Business Analyst role becomes morecritical as project teams become moregeographically dispersed.Outsourcing and globalization of large cor-porations have been the driving factors formuch of this change recently. When the ITdevelopment role no longer resides inside

our organizations, it becomes necessary toaccurately and completely define therequirements in more detail than ever

before. A consistentstructured approach,while nice to have in thepast, is required to besuccessful in the newenvironment. Mostorganizations will main-tain the BusinessAnalyst role as an “in-house” function. As aresult, more IT staff are being trained asBusiness Analysts.

The Business Analystrole will continue toshift its focus from“Software” to“Business System.”Most Business Analysts

today are focused on software developmentand maintenance, but the skills of theBusiness Analyst can be utilized on a largerscale. An excellent Business Analyst canstudy a business area and make recommen-dations about procedural changes, person-nel changes, and policy changes in addition to recommending software. The BusinessAnalyst can help improve the business system not just the business software.

The Business Analyst role will continueto evolve as business dictates.Future productivity increases will beachieved through re-usability of require-ments. Requirements Management willbecome another key skill in the expandingrole of the Business Analyst as organiza-tions mature in their understanding of this critical expertise.

The Business Analyst is often describedas an “Agent of Change.” Having a detailedunderstanding of the organization’s key initiatives, a Business Analyst can lead theway to influence people to adapt to majorchanges that benefit the organization andits business goals. The role of a BusinessAnalyst is an exciting and secure careerchoice as U.S. companies continue to drive the global economy. �


Who Makes a Great

Business Analyst?

• Must be an outstandingcommunicator

• Must understand the SDLC

• Must enjoy very detailedresearch and recording

• Must be skilled atorganizing and managinglarge amounts ofinformation in variousforms

• Must be customer-focused

• Must be flexible

• Must come prepared witha toolkit of techniques toelicit excellent requirements

Requirements Management refers to thecreation, storing, and maintaining of

application software requirements.Requirements consist of all the informationin a Requirements Package includingcorresponding notes, diagrams, orprototypes. Software vendors offer toolsthat store and manage these requirements,called Requirements Management tools.

Why buy a tool? Documentingrequirements is a time consuming anddetailed process. Keeping requirements upto date is even more challenging. Anyonewho has ever created a RequirementsPackage has asked herself or himself “Whatwill happen to all this work that I havedone when the project is over?”Requirements Management is necessarybecause business needs often change. Theychange while the project is still in processand they change after the software has beeninstalled. In addition, when multipleanalysts are working on the same project, itis difficult for more than one person toupdate a traditional word processingdocument.

A Requirements Management tooladdresses these problems. The tool storesrequirements and allows them to berevised, changed, and tracked so thatanalysts can keep them up to date at all

times. These requirements are available andre-useable on future projects.

The organizations that can quicklyadapt their software to changing businessneeds accomplish this feat by maintainingand re-using requirements. A RequirementsManagement tool is essential in offeringthis flexibility. Below are two RequirementsManagement tools currently available.

Tool: DOORSThe Requirements Management tool calledDOORS is sold by Telelogic, Inc. Telelogichas been offering application development

tools for over 20years. They hold a

strongmarketposition,

especially in Europe. DOORS: DynamicObject Oriented Requirements, includes arepository for storing requirements and aset of tools to maintain the requirements.

DOORS was originally designed tosupport textual requirements. It looks andworks like a MS office product. This makesentering requirements very easy for anyonewho is familiar with MS Word. Eachrequirement is assigned a unique number.DOORS keeps track of this uniquenumber and uses it to link one requirement

to another or to a test case (created in theirtool called TAU). In addition, graphicrequirements from tools like VISIO can be linked into DOORS. www.telelogic.com

Tool: iServerOne of the newest RequirementsManagement tools to come into the

marketplace isiServer byOrbus. Orbuswas started by severalRequirementsManagement

experts who saw the need for an openrequirements repository that would be ableto manage and link requirements that werecreated in various tools. The iServerinterface uses MS VISIO to enterrequirements and manage them. Thedatabase stores requirements from MSWord, Excel, PowerPoint, and VISIO.Links between requirements can be built.VISIO users will be able to quickly learnthe iServer menu options.www.orbussoftware.com �

Send your questions to Ask the Experts [email protected].


ask the expertsWhat is a Requirements Management Tool? Why would I buy one?

A few of the major features of Requirements Management tools are outlined below:

Feature Benefit

Repository or database When a requirement is named and stored in a database, it becomes a business asset that can be tracked like any other asset. The repository keeps track of the date it was created, who created it, when it was revised, who it was revised by, etc. Multiple analysts can work on each requirement. In addition, centralized storage allows for easy backup and recovery.

Traceability Each requirement can be linked to related requirements and to other design components such as test cases. This traceability is referred to when a requirement is changed to make sure that all related components are also changed.

Revision tracking Each revision to a requirement is saved and documented. This allows the project team to look back at how the requirement evolved on its way to completion.

Change control When a business change requires a change to an automated procedure, existing requirements from previous projects are available for re-use.

Security A user id or logon id is assigned to each user so that the name of the user who made each change is recorded.

DOORS


new courseAdvanced Business Analysis Workshop Business Analysts are constantly striving to improve their skills and increase the quality oftheir project requirements. This course enhances the effectiveness of Business Analysts bygiving them additional techniques and strategies for gathering, documenting, and reviewingrequirements. Techniques such as advanced data definition, traceability, and gap analysis helpBAs to document more accurate and complete requirements.

The course also presents the concept of Requirements Management and requirement reuse.Implementing a requirements management process into your organization can significantlyreduce the time required to make software changes and develop software interfaces.

Course Outline

Introduction

• What are the challenges faced by Business Analysts? • Review requirements gathering and documentation

process • Define requirements management and re-usability

Conducting a Requirements Review Workshop

• Review rules for conducting a review and the rolesinvolved

• Group workshop - Maintenance project requirements •• Conduct a formal, structured review of the case

study requirements package •• Formulate follow up questions and a revision plan •• Present findings to the class

Advanced Project Initiation Requirements

• Learn to assess a project request and select theappropriate requirements components

• Review objectives for measurable and cleardescriptions

• Review context level dataflow diagram. How doexternal agents differ from user classes and actors?

• Learn a technique to help subject matter expertsscope a project with unclear boundaries

• Group workshop - Revise the requirements packageproject initiation section

Advanced Data Requirements

• Review of the core data components • Discuss data ownership issues • Discuss the use of data in process requirements • Learn about involuted and ternary relationships • Learn techniques for data generalization • Discuss the reusability of data components • Group workshop - Refine the data requirements

section

Advanced Process Requirements

• Discuss typical problems with process descriptions • Review event partitioning • Group workshop - Refine the process requirements

Advanced Business Rule Requirements

• Review of business rule types • Learn about language structures • Group workshop - Refine the business rules in the

requirements package

Advanced Functional Requirements

• Review the design area scope • Review documenting system functionality using

Use Case Descriptions • Learn about screen usability principals in designing

prototypes • Group workshop - Refine the functional

requirements in the requirements package

Assuring a Complete Requirements Package

• Learn about traceability matrices • Group workshop - Create traceability matrices

Project Cost Benefit Analysis

• Learn the purpose of cost benefit analysis • Use the requirements package to estimate project

costs and benefits• Group workshop - Write a simple cost benefit

analysis

Requirements Management

• What is requirements management? Why isrequirements management important?

• How are requirements managed? • Group workshop - Initiating a maintenance project

Requirements Gap Analysis

• Learn about gap analysis and where it can be useful• Show gaps in data, process, and business rule

requirements • Use gap analysis to document requirements for

COTS (Custom Over The counter Software) • Group workshop - Perform gap analysis on case

study project

Intended Audience

This course is intended forexperienced BusinessAnalysts who want toenhance their skills.

Prerequisites

BAs registering for this course must haveattended the three corecourses or have at least 2 years experience inrequirements gathering and documentation usingstructured techniques.

3 Days

For more information on this course visit www.b2ttraining.com, call 865-675-2125 or email [email protected]�

B2T Training offers a program forBusiness Analysts certifying that the

individual has the skills necessary to performanalysis and complete a BusinessRequirements Document for applicationdevelopment. The program consists ofcompleting three proficiency area tests and acomprehensive case study final exam. Inaddition, the candidate must have completed

two years work experience and receive tworecommendations from peers or co-workersvalidating their experience and knowledge.

All of our exams and verificationinformation are reviewed by a CertifiedInstructor/Business Analyst. CertifiedBusiness Analyst may use the B2T Trainingcertification as proof of their provencapabilities. �

certification Business Analyst Certification Program


Essential Skills for the

Business Analyst

4 day class

Pass class exam

Detailing Business

Data Requirements*

3 day class

Pass class exam

Detailing Process and

Business Rule

Requirements

4 day class

Pass class exam

Pass FinalCertification

ExamReceive BA Certification

Submit applicationfor certication

• 2 written recommendations

• Verify work exp. (2 years min.)

*You may substitute Logical Data Modeling

New Certified Business

Analysts

We are pleased to highlight thoseindividuals who have earned the titleof Certified Business Analyst. Theprogram began in late 2002, and weare excited that so many BusinessAnalysts are enrolled and workingtoward certification. To date, we havemore than 700 people in the programand over 100 of these are expected tocomplete all the requirements by theend of 2004.

Iwas initially attracted to Lauesen’s bookbecause he covers numerous requirements

documentation techniques. Many authorsonly focus on one particular approach ormethodology but in reality a BusinessAnalyst needs to be familiar with varioustechniques and able to select theappropriate technique for eachrequirement’s need.

Lauesen has an excellent understandingof the difficulty of documentingrequirements so that they are detailedenough for the IT team to use and yetunderstandable for the SME team toreview and approve. This balance isaddressed in every chapter of the book,with every technique covered. He discusses

well established techniques such asdataflow diagrams and data modeling alongwith newer, less proven techniques such asUML class diagrams and collaborationdiagrams. Lauesen’s examples are clear,

understandable,and yet complexenough to showthe challenges indocumentingaccuraterequirements. Tohelp withgatheringrequirements,Lauesen coversmany elicitation

options along with suggestions forvalidating your requirements.

If you are looking for a step by stepapproach to documenting requirements,this is not it. But if you are looking for arealistic description of the advantages anddisadvantages of various approaches, Iwould highly recommend this book as areference. �

Barbara A. Carkenord is the Vice President,Training at B2T Training. She has workedin the requirements gathering anddocumentation field for over 20 years and hasconducted hundreds of seminars for BusinessAnalysts. Comments are welcome [email protected].

book reviewSoftware Requirements: Styles and Techniquesby Soren LauesenREVIEWED FOR B2T TRAINING BY BARBARA A. CARKENORD

Sue AndrewsTerrie BrosmithAlphonso BrownChristina ChewLynn DonnellyKaren DurneyCheryl EnslinScott GarnerStephanie GriffithsNoreen KellyDavid Kinser

Christine MialiThomas NevludPaul OlesakAnjali RavuriBarb RyanBeth ShaferBecky StichAngie StridRoy SwinehartMarsha WolfbergRachelle Zani

This book is availableat b2ttraining.com.

Outlined below are the steps within Visio necessary to get startedcreating Use Case Diagrams.

1. In Visio when you create a New file, choose Software and thenchoose UML Model Diagram.

2. The new file will be created with one initial page. New pages canbe added for different diagrams within the same project.

3. All of the stencils and shapes associated with UML diagrammingare available on the left hand side of the tool. Below these stencilsis the Model Explorer window. This will show all of the diagramsand shapes (objects) that have been created in your model.

4. The stencil: UML Use Case contains theshapes that are available for Use CaseDiagrams. Simply click on a shape anddrag in onto your page.

5. Once a shape is on your page, doubleclick on it to open its Properties windowwhere you can name it and supplyadditional information about the object.

6. Visio diagrams can be copied into MS Word documents allowinggraphical requirements along with your text.

did you know? MS Visio Professional SupportsUML Modeling and Diagramming


�

�

�

Visit our websitewww.b2ttraining.com

Business Analyst ConferenceBoston, MA in Fall 2004

Announcements and Updates

New Training Classes and Schedules

White Papers on Business Analysis

certified core courses

Essential Skills for the Business AnalystThis course covers the critical skills for the Business Analyst. Students will learnto define what is, and what is not included in the project, how to ask the rightquestions, when and how to hold interviews and facilitated sessions, how towrite excellent requirements, how to verify that requirements are testable, howto conduct a requirements review, and have an overview of various applicationdevelopment methodologies. Additionally, students will be introduced to variousdocumentation techniques and plan an approach for documentation.

Detailing Business Data RequirementsThe Data portion of the business requirements is a critical component to definingcomplete requirements. Every process uses data and almost all business rulesare enforced by data. Missing a critical piece of data or incorrectly defining adata element contributes to the majority of maintenance problems and results insystems that do not reflect the business needs. This course teaches students anin-depth approach to identify and define all necessary data components usingboth textual templates and an entity relationship diagram.

Detailing Process and Business Rule RequirementsThis course continues the development of the requirements package by definingthe processes and business rules for the project. Students will learn to identifyand define the processes from a business and functional perspective. Varioustechniques are taught including decomposition diagrams, templates, workflowmodels, and Use Case diagrams and descriptions. Additionally, this courseteaches techniques to ensure that requirements have not been missed.

More detailed outlines are available on our website, www.b2ttraining.com


4 Days

3 Days

4 Days

�

additional course offerings

Requirements Testing for the Business AnalystThis course provides an excellent foundation for Business Analysts who areinvolved in software quality assurance (SQA). The course will improve theBusiness Analyst's development of requirements so that they can be used tobuild quality test cases. It will also enable the Business Analyst to create specifictest cases from the requirements. The course includes a workshop case studythat provides a cohesive learning experience.

This course provides Business Analysts the knowledge to:• Understand the basic SQA terms and definitions as defined by international

standards • Understand the link between requirements and testing • Understand the testing life cycle • Correct/update requirements for use in development of tests • Define and create test documentation using IEEE/ISO formats • Understand common testing techniques • Review and assist with the development of project test plans • Design and create usability tests • Understand the difference between manual and automated testing

Overview of Business AnalysisThis seminar presents the Business Analyst role to managers and others wholead and work with Business Analysts. In order for the Business Analysts to besuccessful, both the IT and business community must embrace the businessanalysis process. The seminar can be used as a working session to discuss howyour organization will implement the business analysis process and approachesfor documenting the requirements.

Both large and small organizations are realizing the benefits of using BusinessAnalysts on all of their application development projects. A Business Analyst actsas a liaison between business people who have a business problem andtechnology people who know how to create automated solutions. Improving thecommunication between your business areas and your IT team significantlyincreases the quality of the systems developed.

A Business Analyst's main responsibility is to gather, detail, and documentrequirements in a format that is useful to their business area experts and thetechnical developers. Analysis is a very important and time-consuming phase ofevery project. This seminar provides strategies for how management can supportthe business analysis process.

For more information on these courses visit www.b2ttraining.com


4 Hour Seminar

3 Days

�

public class schedule

Essential Skills for the Business Analyst - $1,980/per student

• Jun 14 – Jun 17, 2004 New York, NY

• Jul 26 – Jul 29, 2004 Atlanta, GA

• Sep 13 – Sep 16, 2004 Louisville, KY

• Dec 6 – Dec 9, 2004 Atlanta, GA

Detailing Business Data Requirements - $1,485/per student

• Aug 23 – Aug 25, 2004 Atlanta, GA

• Sep 13 – Sep 15, 2004 New York, NY

• Oct 13 – Oct 15, 2004 Louisville, KY

Detailing Process and Business Rule Requirements - $1,980/per student

• Aug 9 – Aug 12, 2004 San Francisco, CA

• Oct 4 – Oct 7, 2004 Atlanta, GA

• Nov 15 – Nov 18, 2004 Louisville, KY

• Dec 6 – Dec 9, 2004 New York, NY

Register – www.b2ttraining.com/Training-Courses

On-site classes are also available.

Call 865-675-2125 or email us at [email protected]

B2T Training

11795 Northfall Lane, Suite 601Alpharetta, GA 30004

Prsrt StdU.S. Postage

PAID

Permit #309Knoxville, TN

Emerging Role

Documents

Transcript of Emerging Role