Project Objective AGENDA Oracle Financial System


The Above Picture is Related Image of Another Journal


Project Objective AGENDA Oracle Financial System

Baker University, US has reference to this Academic Journal, Oracle Financial System Project Team: Aseem Gupta Jeng Toa Lee Jun Lu Kevin Patrick Zhu Thomas Verghese Weicheng Wong Xuegong Wang ( Jeff ) Date : 26th September, 2001 AGENDA Project Objective Project Scope in addition to Plan Team Charter Communication Plan System Understanding Project Objective Understand Survivability Risks in addition to Strategies so that improve survivability A university-wide accounting in addition to financial system Services Financial service modules Self-service applications Application desktop integrator (ADI) Budget spreadsheet Integrate feeder systems Billing, reporting, reconciliation

 Robinson, Jennifer Baker University


Related University That Contributed for this Journal are Acknowledged in the above Image


D 2.1 Developing Usage scenarios D2.2 Identifying Essential Services in addition to Assets D2.3 Identifying essential service/ assets usage scenarios D2.4 Identifying Essential Components Identify required architecture parts Tracing Scenarios D2.5 Customer Review D 4.1 Identify Strategies in consideration of Survivability Resistance Recognition Recovery D 4.2 Develop Criteria in consideration of choice of strategy so that the architecture D 4.3 Make Recommendations D4.4 Identify Next Steps D4.5 Customer Review System Understanding Define Essential Services Survivability Analysis D 1.1 Project Team Created, Team Charter D 1.2 Communication Plan D1.3 Understanding Existing System Network Topology Hardware in addition to Software Components User Functions in addition to Workflows Critical Services in addition to Assets Administrative Control Domains Vendor Dependencies Connectivity alongside other Systems Security Components in addition to Policies Attack in addition to Intrusion Experience D 1.4 Project Plan Created Define Intrusion Scenarios D 3.1 Create Attacker Profiles Identify resources, time, tools, risk,access in addition to objectives of the attackers D3.2 Develop Intrusion Scenarios Determine usage scenarios Identify compromisable components D3.3 Customer review Milestone 1 Milestone 2 Milestone 3 Milestone 4 Satyajeet Grover in consideration of any queries 1 2 3 4 Milestone Chart Project Plan Team Charter

Communication Plan System Understanding System Architecture

Basic Swing Agenda New Features Swing vs. AWT Programming Windows Look in addition to Feel Motif Look in addition to Feel Java Look in addition to Feel Setting Native Look in addition to Feel Whirlwind Tour of Basic Components Starting Point 1: JApplet JApplet: Example Code JApplet: Example Output Starting Point 2: JFrame JFrame: Example Code JFrame Helper: ExitListener JFrame: Example Output Swing Equivalents of AWT Components JLabel JLabel: Example Code JLabel: Example Output JButton JButton: Example Code JButton: Example Code (Continued) JButton: Example Output JPanel Standard Borders JPanel: Example Code JPanel: Example Output JSlider JSlider: Example Code JSlider: Example Output (Windows, Motif, Java LAF) JColorChooser JColorChooser: Example Code JColorChooser: Example Output Internal Frames Using JInternalFrame Internal Frames: Example Code Internal Frames: Example Code (Continued) Internal Frames: Example Output JOptionPane JOptionPane Message Dialogs (Windows LAF) JOptionPane Confirmation Dialogs (Java LAF) JToolBar JEditorPane Other Simple Swing Components Summary Questions?

System Topology Wind, ES450 2 CPUs, 1GB RAM Mistral, Sun E4500 8 CPUs, 8GB RAM Chinook, SUN E3500 8CPUs, 8GB RAM Ethernet Outside Firewall Firewall Testing Production Disaster Recovery System Transactions Transaction volume Database grows at 2GB/month Traffic Self-services users: around 4,000 people Every day users: around 100 people System developer 1 project leader 2.5 DBAs All Stakeholders Module users Super user who own a module in addition to is responsible in consideration of it Purchasing module Accounts payable module Accounts receivable module Grants module General ledger Labor distribution module Power users Business administrator, Government fund manager System developers Project manager, DBAs Individual users

System Requirements Support all major campus desktop platforms Achieve excellent performance on all platforms Implement a ?thin client? Minimize software installation, distribution in addition to maintenance Leverage existing infrastructure Mitigate any/all security risks Security/Survivability Strategies Signed Java Applet RSA RC4 40-bit standard from of encryption Secure Socket Layer Kerberos-based authentication IP filtering Firewall Disaster Recovery Disaster Recovery Backup – The production system shut down at 4am in consideration of 1-1.5 hours – Flush over so that the Recovery system every 10-15 minutes – The disaster recovery system also keeps 1 day in addition to 5 minute transactions Survivability risks If the production system is down, it takes 2 hours so that fill over Minor system upgrade takes 6 months Ever attacked? Nobody intruded or found intruded. The system was down twice due so that the hardware failure. The longest was half a day.

Security Policies Badge: so that access the system machines Andrew ID: so that log into the first system Application Password: so that launch the applications IP address filtering Module owners have different access right based on the properties of their modules DBAs have limited access right so that the production system Next Steps Identify Intruder Profiles Identify Intrusion Scenarios

Robinson, Jennifer General Manager

Robinson, Jennifer is from United States and they belong to General Manager and work for KESZ-FM in the AZ state United States got related to this Particular Article.

Journal Ratings by Baker University

This Particular Journal got reviewed and rated by and short form of this particular Institution is US and gave this Journal an Excellent Rating.