About Us

OUR VISION

A vision document defines the high-level scope and purpose of a program, product, or project. A clear statement of the problem, proposed solution, and the high-level features of a product helps establish expectations and reduce risks. This topic provides an outline of potential content for a vision document.

See Developing a vision for an explanation of how the product owner or business analyst works with stakeholders to develop a vision document. That topic, which is part of the IBM® Engineering Lifecycle Management (ELM) scenario guidance, describes the vision-development process. This topic outlines typical content for the document. You can copy this outline, paste it into a new document, and use it as the basis for your vision document. Use those portions of this outline that are relevant for your project.

When a team uses the Requirements Management (RM) capability in the ELM, the vision document can be expressed in one or more rich-text documents or modules. You can embed requirements and related artifacts in rich-text documents or use the numbered hierarchical structure of a module to organize content. Team members can set attributes, such as priority and status, on each artifact and create trace links between related documents, modules, and individual artifacts.

OUR MISSION

The Department’s Mission is to lead the software engineering community by exploring, creating and disseminating knowledge by projecting sustainable software development technologies and practices. The department strives to offer programs which are well aligned with the requirements of the stakeholders including the software industry for the integrated development of the society.