IFS工程项目管理.pptVIP

* * IFS系统中所有层面的应用都是可以被外部IFS系统或非IFS系统访问的。 支持多种接口技术。我们承认并非所有的软件开发都用F1使用的工具，技术和编程语言。为了使集成更加便易，F1为常用编程语言，协议提供了集成平台，使集成变得可能并可操作，哪怕这些程序并非F1实施系统中的一部分。 使用开放的标准，系统整合时不需要培训和特殊的能力。基于通用平台。 可扩展的开发框架，F1包含很多业务逻辑、用户界面和整合的开发框架，这些可以实现对开发框架进行扩展。 * * Purpose of slide To show how one Connect System can process multiple IFS Applications instances Things to say Only one additional process is needed for each IFS Applications system The Message Router handle what instance the message should be sent to. It’s possible to send the message to one or many instances at the same time. * * Overview of the integrated systems. The context sensitive navigation enable users to right-click on an asset object in any system which will bring up a menu where different aspects of the object can be selected in the other system. A video can be shown clicking on the camera symbol. Note that you have the correct path to the start-up file (run.bat) in the hyperlink. The rin.bat and the video (USI_demo_Haugesund.avi). The files need to be stored in the same folder as the presentation. The video can be viewed in Camplay.exe * * Purpose of this slide: Show that we have a modeling focused approach to application design. Much of the code is generated directly from the model. Define our three basic architecture tiers—user interface, business logic, and data storage. Things to say: Process models describes what the application does; the object model describe the components that make up the application and how they relate to each other. IFS use the industry standard UML (Unified Modeling Language) to design the object model. Because much of the investment is done in the model and a lot of code is generated, it is easier for IFS to change/update the implementation. We have three main architecture tiers (show in picture). These tiers are compleately encapsulated and isolated from each other. Each architecture tier contains a number of software components. Web pages, portlest, forms, activities, are all examples of sof