Oversight Activities Agency oversight activities including the IRM office

Oversight activities agency oversight activities

This preview shows page 104 - 107 out of 247 pages.

• Oversight Activities: Agency oversight activities, including the IRM office, provide advice and counsel to the project manager on the conduct and requirements of the Design Phase. Additionally, oversight activities provide information, judgments, and recommendations to the agency decision makers during project reviews, and in support of project decision milestones. 3.4 Deliverables The content of these deliverables may be expanded or abbreviated depending on the size, scope, and complexity of the corresponding system’s development effort. Security Risk Assessment
Image of page 104
MBA 815 MANAGEMENT INFORMATION SYSTEM The purpose of the risk assessment is to analyze threats to and vulnerabilities of a system to determine the risks (potential for losses), and using the analysis as a basis for identifying appropriate and costeffective measures. Conversion Plan The Conversion Plan describes the strategies involved in converting data from an existing system to another hardware or software environment. It is appropriate to re-examine the original system’s functional requirements for the condition of the system before conversion, to determine if the original requirements are still valid. System Design Document This describes the system requirements, operating environment, system and subsystem architecture, files and database design, input formats, output layouts, human-machine interface, detailed design, processing logic, and external interfaces. It is used in conjunction with the Functional Requirements Document (FRD), which is finalized in this phase, to provide a complete system specification of all user requirements for the system and reflects the user’s perspective of the system design. Includes all information required for the review and approval of the project development. The sections and subsections of the design document may be organized, rearranged, or repeated as necessary to reflect the best organization for a particular project. In most cases there are both user and technical documentation. Without good documentation the new system may never be used, and it may be virtually impossible to modify the system in future. Poorly documented
Image of page 105
systems have resulted in mistakes that can lead to great loss. Implementation Plan The Implementation Plan describes how the information system will be deployed and installed into an operational system. The plan contains an overview of the system, a brief description of the major tasks involved in the implementation, the overall resources needed to support the implementation effort (such as hardware, software, facilities, materials, and personnel), and any site-specific implementation requirements. This plan is updated during the Development Phase; the final version is provided in the Integration and Test Phase and used for guidance during the Implementation Phase.
Image of page 106
Image of page 107

You've reached the end of your free preview.

Want to read all 247 pages?

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

Stuck? We have tutors online 24/7 who can help you get unstuck.
A+ icon
Ask Expert Tutors You can ask You can ask You can ask (will expire )
Answers in as fast as 15 minutes