Reconstruction of Large Systems Based on Business Data Model
Total Page:16
File Type:pdf, Size:1020Kb
Reconstruction of Large Systems Based on Business Data Model V Shoichi Okugawa (Manuscript received March 28, 2006) Some of our customers have large mainframe systems that have become oversized and hard to maintain, and these customers now want to structurally reform these sys- tems. However, it has been difficult for them to learn how to make this reform. This situation prompted Fujitsu to develop the FUTURITY solution, which is based on the experience we gained in the structural reform of KDDI Corp.’s system and involves work processes, development methodologies, and tools. FUTURITY is composed of four solutions: FUTURITY-TB, which is used to abstract a customer’s business into a business data model and develop To-Be data models; FUTURITY-AI, which is used to abstract the data structure of a customer’s current system and develop As-Is data models; FUTURITY-MP, which is used to compare To-Be data models with As-Is data models and develop reconstruction plans; and FUTURITY-SI, which provides methods and tools for efficiently developing a system designed on the basis of business mod- els. This paper describes the basic system development philosophy and other details of FUTURITY. 1. Introduction a comprehensive range of services for fixed-line Today, many companies that maintain large- and mobile communications.) scale mainframe systems are worried about how This paper describes a conceptual approach they can reform the structure of their systems, to constructing flexible, highly maintainable which are growing larger and more obsolete year- systems and the challenges faced when develop- by-year. One solution is to reconstruct the old, ing such systems. It then describes the solution outdated systems; however, it is not easy to system of FUTURITY. reconstruct systems consisting of several million steps. Moreover, reconstruction does not always 2. Highly maintainable systems solve the problem of maintainability.1),2) This section explains the essence of highly In May 2004, Fujitsu helped KDDI Corpora- maintainable systems. tion3) (hereafter called KDDI) totally reconstruct its large-scale, mainframe fixed-network billing 2.1 What companies require from system. Then, we integrated the approach, ideas, information systems and development methods we used for this recon- Maintainability is always a significant fac- struction and the experience we gained to tor in constructing strategic information systems create the FUTURITY solution. The concept of that directly affect business. Because these FUTURITY was also applied to SDAS/Service systems are now indispensable for business oper- Modeling. (KDDI is the only Japanese informa- ations, the rate at which services are provided has tion and communications enterprise that provides become proportional to the rate of system FUJITSU Sci. Tech. J., 42,3,p.389-393(July 2006) 389 S. Okugawa: Reconstruction of Large Systems Based on Business Data Model development. enables the construction of a system that can flex- The cellular phone business is a clear exam- ibly adapt to changes in the real world. ple of this proportionality. When KDDI began Business data models are essential in busi- providing its family discount service, which ness software development. discounts basic monthly charges and call charges for calls between family members, other compa- 2.3 Challenges when developing flexible nies soon offered similar services. If KDDI had systems and their solutions taken six months or more to develop a system for It is difficult, however, for developers who the new service, their business would have suf- have been used to function-oriented development fered significant damage. Competition among (i.e., development to realize required functions) companies will become even keener when servic- to understand how to develop a system based on es such as number portability allow customers to a business data model. change cellular phone companies without chang- There are two obstacles to overcome before a ing their phone numbers. developer can master this approach to system The primary goal for companies in construct- development. One is the abstraction of real-world ing (or reconstructing) information systems is to business into a model. For developers who have survive business competition by using their own been engaged in materializing, which is the oppo- highly maintainable systems. System vendors site of abstracting, it is not easy to extract kaname know it is a big challenge to construct highly main- entities/events from the real world and create a tainable systems that will last for many years. model. The other obstacle is the exact implemen- tation of the model onto computers. It is good to 2.2 Constructing a highly maintainable have a model, but a developer might not know how system to implement it. How can we develop highly maintainable Fujitsu has overcome these two obstacles systems? First, we must visualize the whole through its experiences in developing small system. However, because it is difficult to grasp systems. From these experiences, we have grad- a system consisting of several million steps as a ually learned the advantages of a development whole, developers can only understand the parts approach based on business data models, and we they are assigned to work on. The old saying, “You have now mastered this approach. can’t see the forest for the trees,” also applies to First, we brainstorm on the business before system development. It is important to see “the we create the business data model. This gives us forest” of a large system. That is, we must a close understanding of the business’s essence create a conceptual representation of the whole when creating the business data model. Then, by system and make it a communication base for implementing abstract models that reflect the real stakeholders. world using object-oriented technologies, we can Therefore, in our business information sys- easily see which software modules will be affect- tems solutions, we have introduced business data ed by real-world changes. The important points models, which are conceptual structures defined in system development are to design a firm archi- as a model and an architecture, by abstracting tecture, understand the architecture fully, and business of the real world. For example, we have then develop the system based on the model. created a business data model for the KDDI project Although it can be difficult for developers to mentioned above. As F. P. Brooks, Jr. writes in learn this method at the beginning, they soon see “The Mythical Man-Month,”4) a business data that it provides better maintainability. In fact, model abstracted from business of the real world KDDI’s reconstructed system is rated as being 3.5 390 FUJITSU Sci. Tech. J., 42,3,(July 2006) S. Okugawa: Reconstruction of Large Systems Based on Business Data Model times more maintainable than its predecessor. 3) FUTURITY-MP (Migration Plan) Therefore, thanks to this method, an additional Create a migration plan by comparing the development of this system that would have tak- outputs from TB and AI and by considering en, for example, seven months, will now take only future business factors and development risks. two months. 4) FUTURITY-SI (System Integration) Construct a system based on the results from 3. Solution system of FUTURITY TB, AI, and MP. Make the system flexibly adapt- FUTURITY is based on a development able to changes by applying a system development approach oriented for the above-mentioned busi- standard that is oriented for business data mod- ness data models. Therefore, it can be also applied els and development efficiency improvement tools. to an ordinary development started from scratch. However, we are preparing it as a solution for 3.1 FUTURITY-TB our main challenge at this time; namely, the FUTURITY-TB corresponds exactly to what reconstruction of large-scale mainframe systems. Brooks described as “the essential work” in “The This section describes the solution system of Mythical Man-Month.” We create the conceptual FUTURITY (Figure 1). structure (business data model) in a top-down 1) FUTURITY-TB (To-Be) manner by finding the “kaname entities” of busi- Create a To-Be business data model by ab- ness in the real world and the “kaname events” stracting the business of the real world. The model that make these entities undergo state transitions. can incorporate business factors expected in the It is important here to simply abstract the near future, but not uncertain factors. business of the real world without being bound 2) FUTURITY-AI (As-Is) by the mechanisms of existing systems or imple- Create a business data model by collecting mentation methods. Therefore, we need to work information from the database, files, and screens with people who are familiar with the business of the existing system in a bottom-up manner. being modeled rather than people familiar with This model is used to clarify the problems of the the system used to conduct that business. We existing data structure by comparing it with the create three business data models: model created in the TB process. FUTURITY-TB (Consulting service) Abstract business of real world into business data model and define To-Be FUTURITY-MP model. (Migration plan FUTURITY-SI creation service) (System integration service) Compare As-Is and To-Be Realize To-Be model based FUTURITY-AI models to clarify problems, on migration plan. (IT resources create migration plan, and analysis service) analyze cost effectiveness. Create visual model (As-Is) TB, AI, and MP are provided as a set, but TB and AI are by extracting data that also available separately. forms framework of existing system from resources. Figure 1 Solution system of FUTURITY. FUJITSU Sci. Tech. J., 42,3,(July 2006) 391 S. Okugawa: Reconstruction of Large Systems Based on Business Data Model 1) Static model gas industries, which have been maintained for This model represents the relationships be- nearly 20 years.