1. Getting to know IRMA ( Integration of Resource Management Applications) - Overview By: Margaret Beer, Brent Frakes, Alison Loar, Simon Kingston National Park Service U.S. Department of the Interior Natural Resource Program Center Inventory and Monitoring Program http://nrinfo.nps.gov/ NATURAL RESOURCE PROGRAM CENTER Science, Stewardship, Solutions From Silos to Service-Oriented Architecture Transition staff away from an application-based organization to a function- based organization. Step One – Transition Organization Philosophy System Development Life Cycle Engage Users Silo Application-based Goals and Benefits Service Development Goals SOA Function-based Step Two – Transition Infrastructure Configuration Transition infrastructure away from an application-based configuration to a task-based organization. Silo Application-based SOA Task-based Step Three – Build System Development Life Cycle Build a system development life cycle (SDLC) that is supported by role- based teams. Project Management Functional Analysis Architecture - SOA - Application - Database User Interface Design Development Quality Assurance Configuration Management & Support Silo One or two people do it all SOA Teams whose expertise is shared among applications Functional Analysis Architecture - Application - Database User Interface Quality Assurance Configuration Mgmt Technical Support Documentation Reconstruction: What are the user workflows among these discrete functions? How should work be channeled between users? How should data be consumed by various services? How can the services be made flexible for future needs? What infrastructure needs to be in place to optimize performance? What are the priorities and dependencies for development? Deconstruction: What are the discrete functions of current systems? How do users want to perform their work? Does an existing application get replaced by multiple services? Do we need to create new services? Do we outsource or delete existing functions? What do users need? How can discrete functions be improved? How can these functions be shared among wider audiences? Engage stakeholders and the many types of users by gathering user requirements before the system is built. Understand and fully document those requirements, including future needs and wants. Deconstruct the application into its core functions. These functions can be formalized as services which can be shared among many applications. Define Application Scope Build once, use many times. Each service is simple and modular, and can become one of the basic building blocks of many different advanced applications. When new user needs arise, applications can be built far more quickly and easily by tapping into existing services. Lasting Benefits of SOA and IRMA Background Over the past decade, NRPC has built and maintained information systems that have captured valuable information and provided essential tools for its management. However, each system has had a unique login, look, definitions, and logic for use. In 2006, the NRPC Center Director issued a policy that established the basis for revamping information systems and gave IRMA its start. The goal of the IRMA is to create a central web portal, a single sign-on system, and a common user interface for all natural resource applications. The underlying framework of this portal is based on service-oriented architecture (SOA), which allows efficient use and sharing (both within NPS and with partners) of data. Best practices for service development follow these goals: Attack risks earlyAttack risks early Develop iterativelyDevelop iteratively Get regular feedbackGet regular feedback Risks are addressed by maintaining regular contact with the users and informing them of the long-term service roadmap before the development begins. Previous system development followed a waterfall development approach, which was to build the entire system before release. IRMA follows an iterative development cycle which incrementally releases versions, each with a little more functionality than the previous. Users can provide regular feedback on each version and refine the long- term vision of the service (i.e., scope). Users can also help steer the development timeline to make sure their priorities are addressed first. Reconstruct the core functions into distinct services.