InfoSphere Blueprint Director tasks

You can use InfoSphere® Blueprint Director to synchronize the project vision with the actual solution by linking the blueprint to business and technical artifacts throughout the lifecycle of your data integration project. Understanding each phase in the project enables enterprise architects to incorporate change into the existing architecture.

Your organization can use InfoSphere Blueprint Director to complete the following tasks:

Define and manage the project architecture

By visualizing the project architecture in a blueprint, team members can understand which tasks are required at each phase of the project, how those tasks must be implemented, who is working on each task, and which assets are involved.

Enterprise architects create blueprints to form the reference architecture for your project. The main blueprint might depict the data sources, data integration points, data repositories, analytic processes, and consumers. Each of these domains represent the different phases of the project, and can be modified as the project changes.

Link the project design to existing metadata

By planning information integration projects and linking the designs to existing metadata, enterprise architects can incorporate existing architectures into new designs.

Users can develop their free-form designs into a layered, interactive blueprint that represents your project. Subdiagrams represent additional parts of each phase of the project and can be linked to the main blueprint. The overall solution connects the visions of each team member with real-world data and concepts, rather than developing a disconnected diagram.

Enterprise architects can develop blueprints based on proven methodologies. By linking a method to a blueprint, enterprise architects can create documentation that describes user roles, responsibilities, and tasks for each phase of the project to provide contextual guidance on the development of solution artifacts.

Modify the environment as the project changes

To highlight changes in each phase of the project, users can incorporate milestone planning into each blueprint.

Users can define the evolution of a blueprint over time, and view the assets that are active during each project milestone. To represent existing metadata and assets specific to your business, users can create custom elements to include in blueprints.

Users can then publish blueprints to a common repository so that the extended team can review blueprints across projects. This visibility helps team members to identify areas for improving reuse and consistency.