| 3
| SOFTWARE FOR NETWORKED INFORMATION SYSTEMS
| 3-1
|
| | Introduction
| |
| | Background
| |
| | The Role of Software
| |
| | Development of an NIS
| |
| | System Planning, Requirements, and Top-Level Design
| |
| | Planning and Program Management
| |
| | Requirements at the System Level
| |
| | Background
| |
| | The System Requirements Document
| |
| | Notation and Style
| |
| | Where to Focus Effort in Requirements Analysis and Documentation
| |
| | Top-Level Design
| |
| | Critical Components
| |
| | The Integration Plan
| |
| | Project Structure, Standards, and Process
| |
| | Barriers to Acceptance of New Software Technologies
| |
| | Findings
| |
| | Building and Acquiring Components
| |
| | Component-Level Requirements
| |
| | Component Design and Implementation
| |
| | Programming Languages
| |
| | Systematic Reuse
| |
| | COTS Software
| |
| | The Changing Role of COTS Software
| |
| | General Problems with COTS Components
| |
| | Interfacing Legacy Software
| |
| | Findings
| |
| | System Integration
| |
| | System Assurance
| |
| | Review and Inspection
| |
| | Formal Methods
| |
| | Testing
| |
| | System Evolution
| |
| | Findings
| |
| | References
| |
| 4
| REINVENTING SECURITY
| 4-1
|
| | Introduction
| |
| | Evolution of Security Needs and Mechanisms
| |
| | Access Control Policies
| |
| | Shortcomings of Formal Policy Models
| |
| | A New Approach
| |
| | Findings
| |
| | Identification and Authentication Mechanisms
| |
| | Network-Based Authentication
| |
| | Cryptographic Authentication
| |
| | Token-Based Mechanisms
| |
| | Biometric Techniques
| |
| | Findings
| |
| | Cryptography and Public-Key Infrastructure
| |