aim700_2005
VPP
UID 100188
精华
11
积分 11
帖子 426
书签 11 个
书币 7458 枚
阅读权限 30
注册 05-6-18
|
[小喇叭]: 知识库:编程开发
网站开发
数据库开发
操作系统
路由技术
网络通信
CrossTalk - The Journal of Defense Software Engineering July 2006
CrossTalk - The Journal of Defense Software Engineering
July 2006
Format: pdf
Features: Net-Centricity
- From the DoD CIO:The Net-Centric Information Enterprise: This article explains why information is one of our greatest sources of power and emphasizes the need to deliver it in a timely and concise manner.
- Information Sharing Is a Strategic Imperative: The author describes the necessity of building a net-centric, collaborative approach to face any threat America may face.
- Secure From the Start: Designing and Implementing an Assured National Security Enterprise: The author defines Information Assurance as a key enabler of the Global Information Grid and outlines the Department of Defense’s strategic objectives for secure, enterprise-wide information sharing.
- Service-Oriented Architectures in Net-Centric Operations: This article describes how service-oriented architectures will make information available faster, at reduced costs, and to more users.
- The Team: Creating the Enabling Capability to Conduct Net-Centric Operations: This article looks at the Command, Control, Communications, and Computer accomplishments of 2005 and looks to continue the positive efforts in 2006.
- Overview of the Department of Defense Net-Centric Data Strategy: The author discusses the Department of Defense’s approach to net-centricity, emphasizing how data will be posted and accessed.
- Transformational Communications Systems for DoD Net-Centric Operations: This article details the foundation of U.S. and coalition net-centric operations, describing the three major communications systems.
- Development of a Ground Vehicle Maneuver Ontology to Support the Common Operational Picture: These authors discuss the process used to develop the Mobility Common Operational Picture for warfighters to maneuver effectively under multiple environmental and tactical conditions.
- and more ....
Plus
Online Only Feature :
- The New Java Security Architecture: Java’s original security architecture was designed to facilitate executing software from remote systems while simultaneously preventing downloaded code from performing unauthorized operations on host machines. The sandbox model of the Java Development Kit 1.0’s security architecture was found to be too restrictive; therefore, the model was modified so that remote code could be allowed as trusted code. In the Java 2 platform, the notion of trusted code was removed and security control mechanisms were implemented that could be applied to both application and applet code so the code could be run with configurable trust. Java developers need to understand and incorporate the new Java security architecture into their development process to make certain their applications are secure. This article looks at the implementation of the new architecture and the new mechanisms provided for ensuring security for Java code. It details the motivation for the security changes in a security architecture, gives a general overview of the architecture added, and looks at some of the details of the mechanisms either changed or provided by the new architecture. (http://www.stsc.hill.af.mil/crosstalk/2006/07/0607RuffinHamiltonCarlisle.html)
- Software Cost Estimating: A Cyclical Conundrum: is article describes the dilemma of some organizations in establishing credible software estimates, proposes some guiding principles and practices for improving the process, and addresses how current software best practices may play a role in the journey to achieving accurate software estimations. It seems that in spite of acquisition reform, in spite of our decade-long focus on achieving software process maturity, in spite of our adoption of modern structured development approaches, we (the software acquisition/ development community) still have problems achieving success (defined as delivering a quality product on time and within budget). Perhaps the incentives are not strong enough to compel us to deliver quality. Perhaps our focus is skewed in favor of cost or delivery time over quality. Perhaps our cost estimating practices (or lack thereof ) are impacting our success with software development. The hundreds of articles on software estimation and software metrics, and hundreds of hours spent in research and development of estimation techniques have not focused on the people and cultural issues surrounding estimating and data collection. Consequently, the reality of cost estimating and perceptions of practioners toward it, are, for the most part, vastly different from what the literature describes. (http://www.stsc.hill.af.mil/crosstalk/2006/07/0607Walker.html)
[ 本帖最后由 aim700_2005 于 06-6-24 22:41 编辑 ]
附件 ： 您的权限暂时无法下载本版内的附件,请参考论坛FAQ提升权限
|
|
