4. Business
IT
Business
IT Business
IT
Cost Center Key Infrastructure Morphing IT
確立したビジネスモデル
全体計画→全体リリース
技術的な意思決定は IT 部門
ビジネスモデルに IT が関与
ニーズに応じたリリース
技術的な方向性は、経営者層
ビジネスを IT がけん引
ジャスト イン タイム
IT 計画と投資は、顧客中心に
Software delivery is a cross-functional team effort that requires diverse functions to integrate in delivering the value envisioned for software investments. Effective Application lifecycle management practices enable organizations to integrate cross-functional teams in delivering a continuous flow of business value through software investments.
Software and technology are key enablers of business modernization in the current and evolving age. The business of IT is enabling business modernization. IT investments need to extend beyond traditional back-office systems to delivering modern and connected edge facing solutions that enable new consumer engagement, new revenue streams, and cost reduction value opportunities. Investments to realize such value opportunities need to be executed in rapid and incremental iterations to deliver timely value and make the needed directional pivots based on learning from production usage. Striking the balance between agility and quality while maximizing the economies of scale in taking their businesses forward by delivering continuous value, are the top challenges faced by IT organizations across the world and in every industry.
First, this slide really is the summary slide for the multi hour arch review that we are scheduling, so we’re really only going to scratch the surface here.There are three key pieces to our architecture: The runtimes that participate in this model driven world and their associated content, a place to store content called the repository and a tool to manipulate that content called Quadrant.Executable content is the center of valueI mean two things by this: firstis that we see many runtimes storing and leveraging their content inside the repository and using it directly, not via codespit. We’re trying to create a very dynamic environment that is not modal in the way many systems are today, no design time vs. run time. Updating the database is enough to change the application. You’re going to see an example of this in our demo.Second is that we are recognize that the system gets more value as we get more content and as we get the associated runtimes that leverage the content. We have a staged approach for targeting content and in the Oslo timeframe we’ll be focused on the middle tier (SOA) and systems management. We’re working with other groups like SharePoint and TFS to get them in our next product iteration.We store this content in a “Natural” SQL database repositoryThis means that our repository is designed to be a classic database application that deeply bets on the features of the database and doesn’t try to encapsulate it or build multiple layers on top of it. This approach allows us to not only leverage the features that the SQL team is building, but it also allows us to leverage the whole database ecosystem that exists, things like reporting, BI, integration with Office and other tools for example. When a customer looks at the repository through an existing tool, our goal is to ensure that they can make sense of what is there and leverage that tool.We are focused on modeling for the masses, not the ivory tower. We want a very broad base of developers to be able to use our system, and we want customers like business analysts, architects and systems management folks to also be comfortable editing these models. Thus we need a broadly approachable, general-purpose modeling tool. We call this tool Quadrant. It is designed to be able to edit any model in the repository using a set of generic viewers such as table, tree and diagram, much like Excel or Access can edit any tabular data. These views can also be customized to provide a more specific experience when editing certain models. You’ll see lots of examples of this in the demo. Finally it is important to note that Quadrant is really the first customer of this platform in that it, itself is model-driven. I’ve got a couple of slides that drill into Quadrant next and we’ll go into that in a little more detail.Because the file based world is not going away anytime soon, we are also creating a human-friendly textual representation of the content which is a modeling language called “D” D is a new declarative language designed for cases where you need a text based representation of your repository content and has a compiler and tool chain that allows you to build your .D files into SQL Scripts you can store in the repository or visa versa. Visual studio can then operate on these files directly in the file system.We also recognize that there is much content already in the world that will we will want to get in and out of the repository. Depending on the content, we expect customers to either load it directly into the repository (“Loaders”) or transform it to .D or .SQL files which can then be loaded via D.
First, this slide really is the summary slide for the multi hour arch review that we are scheduling, so we’re really only going to scratch the surface here.There are three key pieces to our architecture: The runtimes that participate in this model driven world and their associated content, a place to store content called the repository and a tool to manipulate that content called Quadrant.Executable content is the center of valueI mean two things by this: firstis that we see many runtimes storing and leveraging their content inside the repository and using it directly, not via codespit. We’re trying to create a very dynamic environment that is not modal in the way many systems are today, no design time vs. run time. Updating the database is enough to change the application. You’re going to see an example of this in our demo.Second is that we are recognize that the system gets more value as we get more content and as we get the associated runtimes that leverage the content. We have a staged approach for targeting content and in the Oslo timeframe we’ll be focused on the middle tier (SOA) and systems management. We’re working with other groups like SharePoint and TFS to get them in our next product iteration.We store this content in a “Natural” SQL database repositoryThis means that our repository is designed to be a classic database application that deeply bets on the features of the database and doesn’t try to encapsulate it or build multiple layers on top of it. This approach allows us to not only leverage the features that the SQL team is building, but it also allows us to leverage the whole database ecosystem that exists, things like reporting, BI, integration with Office and other tools for example. When a customer looks at the repository through an existing tool, our goal is to ensure that they can make sense of what is there and leverage that tool.We are focused on modeling for the masses, not the ivory tower. We want a very broad base of developers to be able to use our system, and we want customers like business analysts, architects and systems management folks to also be comfortable editing these models. Thus we need a broadly approachable, general-purpose modeling tool. We call this tool Quadrant. It is designed to be able to edit any model in the repository using a set of generic viewers such as table, tree and diagram, much like Excel or Access can edit any tabular data. These views can also be customized to provide a more specific experience when editing certain models. You’ll see lots of examples of this in the demo. Finally it is important to note that Quadrant is really the first customer of this platform in that it, itself is model-driven. I’ve got a couple of slides that drill into Quadrant next and we’ll go into that in a little more detail.Because the file based world is not going away anytime soon, we are also creating a human-friendly textual representation of the content which is a modeling language called “D” D is a new declarative language designed for cases where you need a text based representation of your repository content and has a compiler and tool chain that allows you to build your .D files into SQL Scripts you can store in the repository or visa versa. Visual studio can then operate on these files directly in the file system.We also recognize that there is much content already in the world that will we will want to get in and out of the repository. Depending on the content, we expect customers to either load it directly into the repository (“Loaders”) or transform it to .D or .SQL files which can then be loaded via D.