Macroscope (methodology suite)

Last updated
Macroscope
Developer(s) Fujitsu
Initial release1990;33 years ago (1990)
Stable release
Macroscope 5.0 / March 26, 2012;11 years ago (2012-03-26)
Operating system Microsoft Windows
Available inEnglish and French
Type Business Process
License Proprietary software
Website macroscope.ca.fujitsu.com

Macroscope is an integrated set of methods aimed at enterprise IT activities. [1] Macroscope was developed and is maintained by Fujitsu in Canada. It is primarily used as their core body of knowledge to support the consulting services that they provide to their clients and is also licensed as a commercial product to a number of their clients [2]

Contents

History

1984-1985: "DMR" Information System Development Guides

The first publication of methods that are at the source of Macroscope were two "Information System Development Guides": Part 1 Managing the Project [3] and Part 2 Developing the System. [4] The same books were published in French in 1984. These two methods were known as the "DMR" methods and were later attributed version number 1.0.

The two methods were based on fundamentals or principles that established the general approach. The methods were described in terms of processes, techniques and deliverables. The main approach for system design was by integrating the French Merise [5] data and the American Gane and Sarson [6] process modelling methods.

1987-1990: Information System Delivery Series

Publication of a set of five books collectively called "Information System Delivery Series" by DMR Group Inc. This publication was also issued in French under the title: "Collection Mise en oeuvre de systèmes d'information". The collection contained the following books:

The 1987 edition was later attributed version number 2.0. The 1990 edition of this collection was re-labeled "DMR Productivity Plus", which was quickly nicknamed to "P+" by users. This edition is later attributed version number 2.1.

1990-1996: DMR Macroscope

Research and Development project labelled "Le Macroscope Informatique", leads to the product initially called "DMR Macroscope" and re-branded in 2002 to "Macroscope". This program was initiated by DMR Group Inc., along with the Province of Quebec (Canada), industrial partners, research centers partners, and user groups that contributed financially and logistically. The initial objective of this program was to "develop a set of integrated products, that is, methods, software tools, training program in order to improve the development and usage of information technology". In a 1996 Research Note, [7] Gartner writes:

Taken together, this is one of the most extensive sets of methods and tools produced by any vendor. DMR's purpose is focused on service delivery, but the methods are clearly designed for use by clients.

This R&D effort was divided into four knowledge domains, initially known as Productivity Plus (P+), Strategy Plus (S+) Benefits Plus (B+) and Architecture Plus (A+).

1994-1995: "P+OnLine" method

A first commercial product under the "DMR Macroscope" umbrella, called "P+ OnLine" is released in 1994 and is the first release to display a version number, that is 2.2. Then the project gradually releases the following product components under new commercial names:

1996-1998: DMR Macroscope 3.0 - 3.1

Released in 1996, DMR Macroscope 3.0 was the first publication of the methodology in the HTML format, with mitigated success. This version was replaced in 1998 with version 3.1.

2001: DMR Macroscope 3.5

Release of version 3.5. The domain names lose their "DMR" prefixes, and ManagementSuite is added to the DMR Macroscope product.

2002-2011: Macroscope 4.0 - 4.9

Release of 4.0 in 2002. Re branding of the company to Fujitsu Consulting and the product suite loses its "DMR" prefix and is simply branded as "Macroscope". Then successive versions 4.5 to 4.9, and interim updates are released at a pace of approximately one per year.

2012: Macroscope 5.0

Release of 5.0 in 2012. The domain names are changed to a simpler terminology. The product is also offered "as a service" or hosted version for specific clients.

2014: Macroscope 5.2

The enterprise architecture approach is substantively revised.

Knowledge organization

The Macroscope methodology suite is organised into five process domains, [8] The domains are: Architecture (previously known as ArchitectureLab) for enterprise architecture, Project (previously known as ManagementSuite) for project management, Solution (previously known as ProductivityCentre) for system development and maintenance, Benefits (previously known as ResultStation) for benefits realisation program management and portfolio management, and Vision (previously known as StrategyForum) for enterprise strategy.

All domains of Macroscope are structured in a similar fashion using concepts described in the Software Process Engineering Metamodel (SPEM) of the Object Management Group (OMG). Fujitsu was one of the many contributors to SPEM and sections of Macroscope are used to depict some elements of SPEM.

A domain of Macroscope typically presents the following sections. A process, usually presented as a workflow, describes the phases, steps and activities, under the responsibility of which role, and what deliverables are resulting from the process. A deliverable, presented with a description, a template and, generally, one or more examples, is a work product resulting from a process. A technique is a detailed method of accomplishing something, and is used to produce the content of one or more deliverables.

Some domains of Macroscope contain many processes. For example, the domain called Project, contains only one process, called Project Management, while the Benefits domain contains a Program Management process and a Portfolio Management process.

Each Macroscope domain is also based on a set of fundamental principles, which help understanding, adapting and using the process.

Methodology domains

Vision

Before version 5.0, this was known as StrategyForum, formed of two words: Strategy, the main subject of interest, and Forum, referring to a group of stakeholders discussing about the evolution or the future of something.

The intent of Vision is to provide a methodology to capture, structure, document and confirm an organisation's business strategy, and understand the organisation's strategy process.

Architecture

Before version 5.0, this was known as ArchitectureLab, formed of two words: Architecture, the main subject of interest referring to Enterprise Architecture, and Lab, referring to the word Laboratory, where one can simulate the reality through a model representing such reality. In this context, ArchitectureLab initially came with a modeling and simulation tool that allowed one to create a model of business processes and simulate the behaviour of such process.

The intent of Architecture is to provide a method for delivering the capabilities required to support the organization's strategy.

Solution

Before version 5.0, this was known as ProductivityCentre. This domain name was not following exactly the same naming pattern as the other domains. This is largely due to the longer history of this methodology used to be called Productivity Plus, often referred to as P+ by users. To preserve a strong connection the word Productivity was kept and the word "Centre" was added to refer to "where things get delivered".

The intent of Solution is to provide organizations with the appropriate information system solutions and help them maintain and operate these systems to continuously support their evolving business needs.

Benefits

Before version 5.0, this was known as ResultStation, formed of two words: Results (the final "s" combined with the starting "s" of the second word), which refers to the outcomes resulting from a series of change initiatives into an organization. The second word, Station, refers to a control station where one could plan, observe, pull levers and steer where the change initiatives are going.

The intent of Benefits is to help organizations formulate and manage programs in order to obtain maximum business value from their investments in new technologies and IT-enabled business improvement initiatives.

Project

Before version 5.0, this was known as ManagementSuite, formed of two words: Management, as in project management and Suite, following the same metaphor about name of places.

The intent of Project is to provide project managers with the tools, methods and processes to help them deliver projects on time, within budget and with the expected level of quality. The processes and procedures are coherent with the principles and framework proposed in the Guide to the Project Management Body of Knowledge (PMBOK®) published by the Project Management Institute (PMI).

Trademarks

Macroscope is a registered trademark of Fujitsu Consulting (Canada) Inc. a Fujitsu company.

See also

Related Research Articles

Project management is the process of leading the work of a team to achieve all project goals within the given constraints. This information is usually described in project documentation, created at the beginning of the development process. The primary constraints are scope, time, and budget. The secondary challenge is to optimize the allocation of necessary inputs and apply them to meet pre-defined objectives.

<span class="mw-page-title-main">Risk management</span> Identification, evaluation and control of risks

Risk management is the identification, evaluation, and prioritization of risks followed by coordinated and economical application of resources to minimize, monitor, and control the probability or impact of unfortunate events or to maximize the realization of opportunities.

<span class="mw-page-title-main">Fujitsu</span> Japanese multinational technology company

Fujitsu Limited is a Japanese multinational information and communications technology equipment and services corporation, established in 1935 and headquartered in Tokyo. It is the world's sixth-largest IT services provider by annual revenue, and the largest in Japan, in 2021. The hardware offerings from Fujitsu are mainly of personal and enterprise computing products, including x86, SPARC and mainframe compatible server products, although the corporation and its subsidiaries also offer a diversity of products and services in the areas of data storage, telecommunications, advanced microelectronics, and air conditioning. It has approximately 126,400 employees and its products and services are available in approximately 180 countries.

The rational unified process (RUP) is an iterative software development process framework created by the Rational Software Corporation, a division of IBM since 2003. RUP is not a single concrete prescriptive process, but rather an adaptable process framework, intended to be tailored by the development organizations and software project teams that will select the elements of the process that are appropriate for their needs. RUP is a specific implementation of the Unified Process.

The following outline is provided as an overview of and topical guide to software engineering:

In software development, agile practices include requirements discovery and solutions improvement through the collaborative effort of self-organizing and cross-functional teams with their customer(s)/end user(s), Popularized in the 2001 Manifesto for Agile Software Development, these values and principles were derived from and underpin a broad range of software development frameworks, including Scrum and Kanban.

Enterprise architecture (EA) is a business function concerned with the structures and behaviours of a business, especially business roles and processes that create and use business data. The international definition according to the Federation of Enterprise Architecture Professional Organizations is "a well-defined practice for conducting enterprise analysis, design, planning, and implementation, using a comprehensive approach at all times, for the successful development and execution of strategy. Enterprise architecture applies architecture principles and practices to guide organizations through the business, information, process, and technology changes necessary to execute their strategies. These practices utilize the various aspects of an enterprise to identify, motivate, and achieve these changes."

Enterprise content management (ECM) extends the concept of content management by adding a timeline for each content item and, possibly, enforcing processes for its creation, approval, and distribution. Systems using ECM generally provide a secure repository for managed items, analog or digital. They also include one methods for importing content to bring manage new items, and several presentation methods to make items available for use. Although ECM content may be protected by digital rights management (DRM), it is not required. ECM is distinguished from general content management by its cognizance of the processes and procedures of the enterprise for which it is created.

A federal enterprise architecture framework (FEAF) is the U.S. reference enterprise architecture of a federal government. It provides a common approach for the integration of strategic, business and technology management as part of organization design and performance improvement.

Technology strategy is the overall plan which consists of objectives, principles and tactics relating to use of technologies within a particular organization. Such strategies primarily focus on the technologies themselves and in some cases the people who directly manage those technologies. The strategy can be implied from the organization's behaviors towards technology decisions, and may be written down in a document. The strategy includes the formal vision that guide the acquisition, allocation, and management of IT resources so it can help fulfill the organizational objectives.

A software factory is a structured collection of related software assets that aids in producing computer software applications or software components according to specific, externally defined end-user requirements through an assembly process. A software factory applies manufacturing techniques and principles to software development to mimic the benefits of traditional manufacturing. Software factories are generally involved with outsourced software creation.

The British Ministry of Defence Architecture Framework (MODAF) was an architecture framework which defined a standardised way of conducting enterprise architecture, originally developed by the UK Ministry of Defence. It has since been replaced with the NATO Architecture Framework.

<span class="mw-page-title-main">Enterprise architecture framework</span> Frame in which the architecture of a company is defined

An enterprise architecture framework defines how to create and use an enterprise architecture. An architecture framework provides principles and practices for creating and using the architecture description of a system. It structures architects' thinking by dividing the architecture description into domains, layers, or views, and offers models - typically matrices and diagrams - for documenting each view. This allows for making systemic design decisions on all the components of the system and making long-term decisions around new design requirements, sustainability, and support.

The following outline is provided as an overview of and topical guide to business management:

<span class="mw-page-title-main">Business architecture</span>

In the business sector, business architecture is a discipline that "represents holistic, multidimensional business views of: capabilities, end‐to‐end value delivery, information, and organizational structure; and the relationships among these business views and strategies, products, policies, initiatives, and stakeholders."

Logical Domains is the server virtualization and partitioning technology for SPARC V9 processors. It was first released by Sun Microsystems in April 2007. After the Oracle acquisition of Sun in January 2010, the product has been re-branded as Oracle VM Server for SPARC from version 2.0 onwards.

A glossary of terms relating to project management and consulting.

Lean IT is the extension of lean manufacturing and lean services principles to the development and management of information technology (IT) products and services. Its central concern, applied in the context of IT, is the elimination of waste, where waste is work that adds no value to a product or service.

Business process management (BPM) is the discipline in which people use various methods to discover, model, analyze, measure, improve, optimize, and automate business processes. Any combination of methods used to manage a company's business processes is BPM. Processes can be structured and repeatable or unstructured and variable. Though not required, enabling technologies are often used with BPM.

Capability management is the approach to the management of an organization, typically a business organization or firm, based on the "theory of the firm" as a collection of capabilities that may be exercised to earn revenues in the marketplace and compete with other firms in the industry. Capability management seeks to manage the stock of capabilities within the firm to ensure its position in the industry and its ongoing profitability and survival.

References

  1. ↑ Macroscope Overview [ permanent dead link ], Fujitsu.
  2. ↑ Macroscope presentation, Fujitsu.
  3. ↑ Information System Development Guide Part 1 Managing the Project, DMR AND ASSOCIATES LTD, 1986, ISBN   2-9800387-3-3
  4. ↑ Information System Development Guide Part 2 Developing the System, DUCROS, MEILLEUR, ROY AND ASSOCIATES LTD, 1984, ISBN   2-9800387-0-9
  5. ↑ Tardieu H., Nanci D. & Pascot D., Conception d'un système d'information - construction de la base de données, Editions d'organisation, Paris, 1979
  6. ↑ Chris Gane & Trish Sarson, Structured System Analysis: tools and techniques, Improved System Technologies, New York, 1979
  7. ↑ DMR's Macroscope: A powerful Mix, Gartner Research Note P-400-156, August 29, 1996
  8. ↑ Macroscope description on Macroscope User Group site

Bibliography

Portals

Portal:Business and economics

This page is based on this Wikipedia article
Text is available under the CC BY-SA 4.0 license; additional terms may apply.
Images, videos and audio are available under their respective licenses.