System and method linking use case documents to business process documents

A system for information technology (IT) process management. The system comprises a processor, one or more memory storage devices coupled to the processor, and a document composer tool comprising a plurality of enterprise use case documents to locate an enterprise use case document relevant to an IT project based on input keywords and to link an enterprise use case document to at least one relevant enterprise business process document when an enterprise use case document is updated, wherein an enterprise use case document comprises a link referring to at least one enterprise business process document. The system further comprises an enterprise business process repository stored in at least one of the memory storage devices comprising a plurality of enterprise business process documents, wherein an enterprise business process document comprises a set of steps to accomplish a specific organizational goal.

CROSS-REFERENCE TO RELATED APPLICATIONS

Not applicable.

REFERENCE TO A MICROFICHE APPENDIX

Not applicable.

BACKGROUND

A project may be a temporary endeavor undertaken to create a unique product or service. Assessing project impacts on functions and organizations within an enterprise may be a lengthy and difficult process. For example, employees and/or contractors may be subjectively selected from numerous organizations, or areas, in the enterprise to evaluate potential impacts on both organizations and functions supported by the organizations. An evaluation meeting may constitute a waste of time for some erroneously selected employees whose organizations are not impacted by the project. Subsequent to the evaluation meeting, discoveries of unanticipated project impacts may result in a project manager requiring most or all of the previously selected employees to meet in a second evaluation meeting, this time with additional employees from organizations where the project's impact was unanticipated. The second evaluation meeting may result in overturning or revising previous project decisions made in the first evaluation meeting because the first evaluation meeting failed to take all project impacts into account. Overturning or revising previous project decisions may result in wasting some of the resources expended in implementing the previous project decisions. Halting project development for the second evaluation meeting may result in unnecessary delays in the project development. Repeated evaluation meetings may constitute an inefficient use of time for the initially selected employees.

SUMMARY

In an embodiment, a system for information technology (IT) process management is disclosed. The system comprises a processor, one or more memory storage devices coupled to the processor, and a document composer tool comprising a plurality of enterprise use case documents to locate an enterprise use case document relevant to an IT project based on input keywords and to link an enterprise use case document to at least one relevant enterprise business process document when an enterprise use case document is updated, wherein an enterprise use case document comprises a link referring to at least one enterprise business process document. The system further comprises an enterprise business process repository stored in at least one of the memory storage devices comprising a plurality of enterprise business process documents, wherein an enterprise business process document comprises a set of steps to accomplish a specific organizational goal. The system further comprises a portfolio management component stored in at least one of the memory storage devices and configured to locate the at least one enterprise business process document through a link in the enterprise use case document, send data from the document composer tool and the enterprise business process repository to a partner pipeline management component, wherein the partner pipeline management component promotes IT project bandwidth constraint identification before execution of an IT project, wherein an IT project bandwidth is the total resource capacity supporting IT projects, wherein an IT project bandwidth constraint occurs when the same resource is insufficient for executing multiple projects at the same time, and automatically identify process change tasks with an assigned owner or group for each task, wherein the process change tasks are defined in the enterprise business process document. The portfolio management component is configured to further automatically send notification to stakeholders and groups impacted by the IT project about the project and about meetings for the project, wherein the impacted stakeholders and groups are defined in the enterprise business process document, track status of tasks undertaken by the impacted groups, and automatically send notification to relevant stakeholders for approval of completed tasks after completed tasks are uploaded by the impacted groups.

In an embodiment, a method of managing information technology (IT) processes is disclosed. The method comprises inputting keywords of an IT project into a document composer tool, wherein a document composer tool is a software application comprising enterprise use case documents to locate an enterprise use case document relevant to an IT project based on input keywords, wherein an enterprise use case document comprises a link referring to at least one enterprise business process document, wherein an enterprise business process document comprises a set of steps to accomplish a specific organizational goal. The method further comprises if no enterprise use case document is found based on the input keywords, creating an enterprise use case document based on the input keywords. The method further comprises if an enterprise use case document is found based on the input keywords: locating the at least one enterprise business process document through the link in the enterprise use case document, and sending, by a portfolio management component, data from the document composer tool and an enterprise business process repository to a partner pipeline management component, wherein the partner pipeline management component promotes IT project bandwidth constraint identification before execution of an IT project, wherein an IT project bandwidth is the total resource capacity supporting IT projects, wherein an IT project bandwidth constraint occurs when the same resource is insufficient for executing multiple projects at the same time. The method further comprises automatically sending, by the portfolio management component, notification to stakeholders and groups impacted by the IT project about the project and about meetings for the project, wherein the impacted stakeholders and groups are defined in the enterprise business process document. The method further comprises automatically identifying, by the portfolio management component, process change tasks with an assigned owner or group for each task, wherein the process change tasks are defined in the enterprise business process document, tracking status of tasks undertaken by the impacted groups, and automatically sending notification to relevant stakeholders for approval of completed tasks after tasks are uploaded by the impacted groups. The method further comprises linking, by the document composer tool, the enterprise use case document with at least one enterprise business process document after approvals are received, automatically generating reports every predefined time interval, and promoting tracking and supporting audits and governance of the enterprise use case documents and enterprise business process documents.

In an embodiment, a method of managing information technology (IT) processes is disclosed. The method comprises inputting keywords of an IT project into a use case tool, wherein a use case tool is a software application comprising use case documents and links from a use case document to at least one business process, wherein a business process document comprises a set of steps to accomplish a specific organizational goal. The method further comprises if no use case document is found based on the input keywords, creating a use case document based on the input keywords. The method further comprises if a use case document is found based on the input keywords: locating the at least one business process document through the link in the use case document, and sending, by a portfolio management component, data from the use case tool and a business process repository to a partner pipeline management component, wherein the partner pipeline management component promotes IT project bandwidth constraint identification before execution of an IT project, wherein an IT project bandwidth is the total resource capacity supporting IT projects, wherein an IT project bandwidth constraint occurs when the same resource is insufficient for executing multiple projects at the same time. The method further comprises modifying pipelines of IT projects based on identified bandwidth constraints, wherein a pipeline of an IT project is the sequence of process change tasks of the IT project. The method further comprises automatically sending, by the portfolio management component, notification to stakeholders and groups impacted by the IT project about the project and about meetings for the project, wherein the impacted stakeholders and groups are defined in the business process document. The method further comprises automatically identifying, by the portfolio management component, process change tasks with an assigned owner or group for each task, wherein the process change tasks are defined in the business process document, tracking status of tasks undertaken by the impacted groups, automatically sending notification to relevant stakeholders for approval of completed tasks after completed tasks are uploaded by the impacted groups, and linking, by a document composer tool, the updated use case document with at least one business process document after approvals are received.

DETAILED DESCRIPTION

When an information technology (IT) project is approved by partners and assigned to a project manager, a functional requirement specification (FRS) document and/or a system definition specification (SDS) typically do not include project specific process requirements. If process owners are not engaged during early phases of an IT project, the introduction of the IT project into production may be delayed or create production roll-out problems that degrade customer satisfaction. The present disclosure teaches a system and method for linking an enterprise use case (EUC) document and an enterprise business process (EBP) document and automation in an IT project development that reduces unexpected process impacts due to production roll-out.

For example, when an IT project is approved by partners, keywords of the IT project may be input into a document composer tool to search for a relevant enterprise use case document. A document composer tool is a software application comprising enterprise use case documents to locate an enterprise use case document relevant to an IT project based on input keywords. If no relevant enterprise use case document is found, an enterprise use case document may be created based on the input keywords. When an enterprise use case document is found based on the input keywords, a relevant enterprise business process document may be located through a link embedded in the enterprise use case document. While the teachings of this disclosure are often presented in terms of the enterprise business process and/or enterprise use cases, it is understood that these teachings may also be applied to business processes and/or use cases. A business process may comprise a set of steps to accomplish a specific organizational goal. An enterprise business process may be a business process at a higher level and may be more general than a business process.

Data from the document composer tool and an enterprise business process repository may be sent by a portfolio management component to a partner pipeline management component. For example, the portfolio management component may extract information from an enterprise use case document and/or a relevant enterprise business process document to send to the partner pipeline management component. The enterprise use case document may be obtained by the portfolio management component from the document composer tool. The enterprise business process document may be obtained by the portfolio management component from the enterprise business process repository. The partner pipeline management component may promote identification of IT project bandwidth constraint before execution of an IT project. An IT project bandwidth is the total resource capacity supporting IT projects. Resources that support IT projects may comprise manpower, hardware, software, and/or another type of resource. An IT project bandwidth constraint occurs when the same resource is insufficient for executing multiple projects at the same time. Pipelines of IT projects may be modified by the pipeline management component based on identified bandwidth constraints, for example to prevent an IT project bandwidth constraint from occurring. A pipeline of an IT project is the sequence of process change tasks of the IT project. As a result of the pipeline change, the schedule and staffing of an IT project may be adapted according to the pipeline change.

Notification may be automatically sent by the portfolio management component to stakeholders and groups impacted by the IT project about the project and about meetings for the project. The impacted stakeholders and groups may be defined in the enterprise business process document. Process change tasks may be automatically identified by the portfolio management component with an assigned owner or group for each task. The process change tasks may also be defined in the enterprise business process document. Status of tasks undertaken by the impacted groups is tracked by the portfolio management component and may be displayed by a dashboard of the portfolio management component.

When a task is completed, the modified process of the IT project may be uploaded by the relevant group, for example to the portfolio management component or the enterprise business process repository. However, the enterprise business process process document may not be officially updated until approval has been received from applicable stakeholder(s). Notification may be automatically sent by the portfolio management component to relevant stakeholders for approval of completed tasks after tasks are uploaded by the impacted groups. The enterprise use case document may be linked by the document composer tool with at least one enterprise business process document after approvals are received. For example, at least a link may be composed in the enterprise use case document by the document composer tool with each link referring to a relevant enterprise business process document. The impacted groups may be notified of the approval of completed tasks from the stakeholders. Reports may be automatically generated every predefined time interval by the portfolio management component. Tracking and supporting audits and governance of the enterprise use case documents and enterprise business process documents may be promoted by the portfolio management component.

The system promotes using use case documents as a touch point to assure that impacted processes are identified and considered for constraints on the development plans and schedules. The system further promotes including stakeholders of the impacted processes for approvals and notifications related to the subject development project.

Turning now toFIG. 1, a communication system100is described. In an embodiment, the communication system100comprises a server computer102and a data store116. The server102may comprise a processor110, a document composer tool104, a portfolio management component108, a pipeline management component122, and an enterprise business process repository118. The document composer tool104may comprise a plurality of enterprise use case documents106. The enterprise business process repository118may comprise a plurality of enterprise business process documents120. The server102may have access to a network114. The data store116may also have access to the network114. The network114may comprise any combination of private and public networks.

It is understood that the system100may comprise any number of servers102and any number of data stores116. The server computer102may be any of a desktop computer, a server computer, or another network capable device. Computer systems are described further hereinafter. The server102and the data store116may communicate through a private internal network and/or public external network.

The document composer tool104, the portfolio management component108, the pipeline management component122, and the enterprise business process repository118may be stored in one computer—for example, a server computer, in four different computers—for example, a first server computer for the document composer tool104, a second server computer for the portfolio management component108, a third server computer for the pipeline management component122, and a fourth server computer for the enterprise business process repository118, in multiple different computers—for example, a first set of multiple server computers for the document composer tool104, a second set of multiple computers for the portfolio management component108, a third set of multiple server computers for the pipeline management component122, and a fourth set of multiple computers for the enterprise business process repository118, or in some other combination of computers. In an embodiment, the enterprise use cases106and/or the enterprise business process repository118may be stored in the data store116or another data store. Alternatively, some of the document composer tool104, the portfolio management component108, the pipeline management component122, and the enterprise business process repository118may be stored in computers, and the rest may be stored in the data store116or another data store.

In an embodiment, the enterprise business process repository118may comprise a plurality of enterprise business process documents120. While the teachings of this disclosure are often presented in terms of the enterprise business process and/or enterprise use cases, it is understood that these teachings may also be applied to business processes and/or use cases. A business process may comprise a set of steps to accomplish a specific organizational goal. For example, a business process may comprise a structured, measured set of activities designed to produce a specified output for a particular customer or market. An enterprise business process may be a business process at a higher level and may be more general than a business process. The enterprise business process repository118may be updated with the latest version of an enterprise business process document120when any change is made to the enterprise business process document120by the portfolio management component108.

The document composer tool104may be a software application that comprises a plurality of enterprise use case documents106. When executed by the processor110, the document composer tool104may be utilized to locate an enterprise use case document106relevant to an IT project based on input keywords. Additionally, the document composer tool104may compose a link referring to a relevant enterprise business process document120in an enterprise use case document106.

For example, when keywords “disconnect service” of an IT project are input into a user interface of the document composer tool104, enterprise use case document(s)106relevant to “disconnect service” may be located by the document composer tool104. If no relevant enterprise use case document106is found based on the input keywords, an enterprise use case document106may be created by the document composer tool104based on the input keywords. An enterprise use case document106may be updated by the document composer tool104when any change is made to the enterprise use case document106by an impacted group or a stakeholder and the change has been approved by relevant stakeholder(s). The change may be updated in a revision history of the enterprise use case document106.

The document composer tool104may perform composition of a link referring to a relevant enterprise business process document120at a variety of times, for example when an enterprise use case document106is created for the first time, when an enterprise use case document106is updated, or at some other time. A use case may comprise a sequence of actions, including variants, that a software system performs that yields an observable result of value to a particular actor, for example a user of the software system. An ECU may be a use case at a higher level that corresponds to an enterprise business process. An enterprise use case document106may be updated after approvals from relevant stakeholders are received. An enterprise use case document106may refer to more than one relevant enterprise business process document120, for example with multiple links, each link referring to a relevant enterprise business process document120. In an embodiment, the document composer tool104may also compose a link referring back to a relevant enterprise use case document106in an enterprise business process document120. The composition may be performed by the document composer tool104at a variety of times, for example when an enterprise business process document120is created for the first time, when an enterprise business process document120is updated, or at some other time. An enterprise business process document120may be updated after approvals from relevant stakeholders are received. An enterprise business process document120may refer to more than one relevant enterprise use case document106, for example with multiple links, each link referring to a relevant enterprise use case document106.

The portfolio management component108may be a software application that performs a variety of functionality to manage information technology (IT) projects, enterprise business process documents120, and/or enterprise use case documents106. For example, when executed by the processor110, the portfolio management component108may communicate with the pipeline management component122, the document composer tool104, and/or the enterprise business process repository118to perform IT project related activities.

The portfolio management component108may locate the relevant enterprise business process document120of the enterprise use case document106through a link in the enterprise use case document106. For example, when the document composer tool104locates an enterprise use case document106based on input keywords, a link may be found in the enterprise use case document106referring to a relevant enterprise business process document120. The document composer tool104may send a message/notification to the portfolio management component108with information about the link from the enterprise use case document106or information about the enterprise use case document106. The portfolio management component108may locate the relevant enterprise business process document120in the enterprise business process repository118with the received information from the document composer tool104. For example, the portfolio management component108may request the enterprise business process repository118for the enterprise business process document120with the link information of the enterprise business process document120. The enterprise business process repository118may transmit information of the enterprise business process document120to the portfolio management component108if the enterprise business process document120is located by the enterprise business process repository118.

The portfolio management component108may send data from the document composer tool104and the enterprise business process repository118to the partner pipeline management component122. For example, the portfolio management component108may extract information from an enterprise use case document106and/or a relevant enterprise business process document120to send to the partner pipeline management component122. The enterprise use case document106may be obtained by the portfolio management component108from the document composer tool104. The enterprise business process document120may be obtained by the portfolio management component108from the enterprise business process repository118. Alternatively, the portfolio management component108may extract information from the enterprise use case document106and/or the relevant enterprise business process document120. Information extracted from the enterprise use case document106and/or the relevant enterprise business process document120may comprise process change tasks information, process step information, impacted group information, or some other information.

When executed by the processor110, the partner pipeline management component122may promote IT project bandwidth constraint identification before execution of an IT project. An IT project bandwidth may be the total resource capacity supporting IT projects. Resources that support IT projects may comprise manpower, hardware, software, and/or another type of resource. An IT project bandwidth constraint may occur when the same resource is insufficient for executing multiple projects at the same time, for example personnel with some specific expertise. The pipelines of IT projects may be modified based on identified bandwidth constraints. A pipeline of an IT project may be the sequence of process change tasks of the IT project. As a result of the pipeline change, the IT project schedule and staffing may be adapted according to the pipeline change.

The portfolio management component108may automatically identify process change tasks with an assigned owner or group for each task. The process change tasks may be defined in the enterprise business process document120. When information of the enterprise business process document120is obtained by the portfolio management component108, the portfolio management component108may identify process change tasks. A process change task may be a task that its process may change by the IT project. Each task may have been assigned with an owner and the owner of each task may be identified by the portfolio management component108. Notification about the project and about meetings for the project may be automatically sent by the portfolio management component108to stakeholders and groups impacted by the IT project. The impacted stakeholders and groups may be defined in the enterprise business process document120and may be obtained by the portfolio management component108. For example, the stakeholders and impacted groups may be notified by the portfolio management component108of the IT project and/or the enterprise use case document106. The enterprise use case document106may comprise a link referring to the relevant enterprise business process document120. Thus, the stakeholders and impacted groups may review the IT project, the enterprise use case document106, and/or the enterprise business process document120. Meeting schedules may automatically be sent in the notification from the portfolio management component108to the stakeholders and impacted groups.

The portfolio management component108may track status of tasks undertaken by the impacted groups. An impacted group may be a department, an organization, or a group of an enterprise that is impacted by the IT project. This may be a group which does not actively implement the IT development but which experience a change in operations or work load when the IT development or project is rolled out. For example, roll out of an IT project of an enterprise may impact a call center of the enterprise, and the call center may be considered an impacted group. When a new feature is rolled out, users may be unfamiliar with the new feature and may generate a significant increase of calls to the customer care call center.

For example, when the tasks are undertaken by the impacted groups, task status may be tracked and/or monitored by the portfolio management component108. Status of a task may comprise “in review”, “completed”, “past due”, or some other type of status. The portfolio management component108may keep track of task status and indicate the status in a dashboard of the portfolio management component108. Stakeholders and impacted groups may review task status through accessing the portfolio management component108. The portfolio management component108may send a notification to a relevant group when the corresponding task is past due. The portfolio management component108may automatically send notification to relevant stakeholders for approval of completed tasks after completed tasks are uploaded by the impacted groups, for example to remind stakeholders to confirm that gate or milestone completion criteria have been satisfied.

When tasks are completed by the impacted groups and uploaded, for example uploaded to the portfolio management component108, notification may be sent by the portfolio management component108to applicable stakeholders for approval. For example, the call center in a previous example may be assigned a task to boost its staffing. For example, the call center may undertake the task of conducting call center training to prepare for anticipated increased call volume resulting from roll-out of new functionality from the IT project. When the task is completed by the call center, details of the completed task may be uploaded to the portfolio management component108, for example the number of new employees in the call center, the number of employees in the call center that have completed the call center training, or another type of information.

When all completed and uploaded tasks are approved by the stakeholders, the portfolio management component108may send a notification to the document composer tool104indicating all tasks have been uploaded and approved. The portfolio management component108may transmit the latest enterprise business process document120to the enterprise business process repository118or send a notification to the enterprise business process repository118to update the enterprise business process document120. The portfolio management component108may transmit the latest enterprise use case document106to the document composer tool104or send a notification to the document composer tool104to update the enterprise use case document106. The document composer tool104may compose a link in the enterprise use case document106referring to at least one relevant enterprise business process document120. In an embodiment, the document composer tool104may also compose a link in the enterprise business process document120referring to at least one relevant enterprise use case document106.

Reports may be automatically generated by the portfolio management component108periodically, for example every week, every month, every year, or at some other periodic interval. A report may comprise information on status of the IT project, the enterprise use case document106, and/or the enterprise business process document120. The portfolio management component108may comprise an option for relevant stakeholders to select to receive notification of the reports. Tracking of the enterprise use case documents106and enterprise business process documents120may be promoted by the portfolio management component108. For example, the portfolio management component108may keep a record of relations of enterprise use case documents106, enterprise business process documents120, revision history of enterprise use case documents106, revision history of enterprise business process documents120, or other information on the enterprise use case documents106and/or enterprise business process documents120. Audits and governance of the enterprise use case documents106and/or enterprise business process documents120may be supported by the portfolio management component108. For example, the portfolio management component108may send notification to relevant personnel for audits and governance periodically, for example every month, every quarter, every year, or at some other periodic interval. The portfolio management component108may record the audit and governance status of the enterprise use case documents106and/or enterprise business process documents120. The enterprise use case documents106and the enterprise business process documents120may be kept evergreen with the assist from the portfolio management component108in tracking and supporting audits and governance.

Turning now toFIG. 2AandFIG. 2B, a method200is described. At block202, keywords of an IT project are input into an enterprise use case tool, wherein a document composer tool is a software application comprising enterprise use case documents to locate an enterprise use case document relevant to an IT project based on input keywords. An enterprise use case document comprises a link referring to at least one enterprise business process document. An enterprise business process document comprises a set of steps to accomplish a specific organizational goal. For example, when an IT project is built, keywords of the IT project may be input into the document composer tool104. The document composer tool104may search for an enterprise use case document106relevant to the IT project based on the input keywords. Each enterprise use case document106may comprise a link referring to at least one relevant enterprise business process document120. An enterprise business process document120may comprise a set of steps to accomplish a specific organizational goal.

At block204, it is determined whether any relevant enterprise use case document is found based on the input keywords. For example, if the result of block204is false, which means no relevant enterprise use case document106is found based on the input keywords, the process/method may proceed to block206. On the other hand, if the result of block204is true, which means a relevant enterprise use case document106is found based on the input keywords, the method may proceed to block208. At block206, an enterprise use case document is created based on the input keywords. For example, an enterprise use case document106may be created based on the input keywords. At block208, the at least one enterprise business process document is located through the link in the enterprise use case document. For example, the portfolio management component108may locate the at least one relevant enterprise business process document120through the link in the enterprise use case document106. The information of the enterprise use case document106comprising the link to the at least one relevant enterprise business process document120may be obtained by the portfolio management component108from the document composer tool104.

At block210, data from the document composer tool and an enterprise business process repository is sent by a portfolio management component to a partner pipeline management component, wherein the partner pipeline management component promotes IT project bandwidth constraint identification before execution of an IT project. An IT project bandwidth is the total resource capacity supporting IT projects. An IT project bandwidth constraint occurs when the same resource is insufficient for executing multiple projects at the same time. For example, data from the document composer tool104and the enterprise business process repository118may be sent by the portfolio management component108to the partner pipeline management component108. The partner pipeline management component108may promote IT project bandwidth constraint identification before execution of an IT project. An IT project bandwidth may be the total resource capacity supporting IT projects. The resources that support IT projects may comprise manpower, hardware, software, and/or another type of resource.

An IT project bandwidth constraint may occur when the same resource is insufficient for executing multiple projects at the same time. For example, personnel with some specific expertise may be desirable by multiple IT projects at the same time when the IT projects progress to a certain point. It may be desirable to avoid this type of bandwidth constraint. When visibility of progress of multiple IT projects is presented by the pipeline management component122, the bandwidth constraint may be avoided by modifying pipelines of IT projects. A pipeline of an IT project may be the sequence of process change tasks of the IT project. The partner pipeline management component122may promote IT project bandwidth constraint identification before execution of an IT project.

At block212, notification is automatically sent by the portfolio management component to stakeholders and groups impacted by the IT project about the project and about meetings for the project, wherein the impacted stakeholders and groups are defined in the enterprise business process document. For example, the portfolio management component108may send notification to stakeholders and groups impacted by the IT project about the project and about meetings for the project. In an embodiment, the impacted stakeholders and groups may be defined in the enterprise business process document120.

At block214, process change tasks are automatically identified by the portfolio management component with an assigned owner or group for each task, wherein the process change tasks are defined in the enterprise business process document. For example, process change tasks may be automatically identified by the portfolio management component108and each task may have been assigned an owner or a group. An owner of a process change task may be a relevant stakeholder. When the process change task is completed by impacted group(s), the owner may approve the completed task before the enterprise business process document120and/or the enterprise use case document106is updated with the modified task.

At block216, status of tasks undertaken by the impacted groups is tracked. For example, status of tasks undertaken by the impacted groups is tracked by the portfolio management component108. Status of a task may comprise “in review”, “completed”, “past due”, or another type of status.

At block218, notification is automatically sent to relevant stakeholders for approval of completed tasks after tasks are uploaded by the impacted groups. For example, notification may be automatically sent by the portfolio management component108to relevant stakeholders for approval of completed tasks after tasks are uploaded by the impacted groups. When all approvals have been received for all process change tasks of the IT project, the portfolio management component108may send a notification to the document composer tool104and/or the enterprise business process repository118indicating all tasks have been uploaded and approved. The portfolio management component108may transmit the latest enterprise business process document120to the enterprise business process repository118or send a notification to the enterprise business process document120to update the enterprise business process document120. The portfolio management component108may transmit the latest enterprise use case document106to the document composer tool104or send a notification to document composer tool104to update the enterprise use case document106.

At block220, the enterprise use case document is linked by the document composer tool with at least one enterprise business process document after approvals are received. For example, the enterprise use case document106may be linked by the document composer tool104with at least one relevant enterprise business process document120after the approvals of the tasks are received. For example, the document composer tool104may compose at least one link in the enterprise use case document106with each link referring to one relevant enterprise business process document120.

At block222, reports are automatically generated every predefined time interval. For example, reports may be automatically generated by the portfolio management component108periodically, for example every week, every month, every year, or at some other periodic interval. At block224, tracking and supporting audits and governance of the enterprise use case documents and enterprise business process documents are promoted. For example, tracking and supporting audits and governance of the enterprise use case documents106and/or the enterprise business process documents120may be promoted by the portfolio management component108.