|
||||
T1. Architectures of Next Generation Wireless Networks T2. Secure Routing T3. A New Unified Model of Custom Software Costs Determination in Contracts
Detailed Descriptions T1. Architectures of Next Generation Wireless Networks Emerging Internet Quality of Service (QoS) mechanisms are expected to enable wide spread use of real time services such as VoIP and videoconferencing. The "best effort" Internet delivery cannot be used for the new multimedia applications. New technologies and new standards are necessary to offer Quality of Service (QoS) for these multimedia applications. Therefore, new communication architectures integrate mechanisms allowing guaranteed QoS services as well as high rate communications. The service level agreement with a mobile Internet user is hard to satisfy, since there may not be enough resources available in some parts of the network the mobile user is moving into. The emerging Internet QoS architectures, differentiated services and integrated services, do not consider user mobility. QoS mechanisms enforce a differentiated sharing of bandwidth among services and users. Thus, there must be mechanisms available to identify traffic flows with different QoS parameters, and to make it possible to charge the users based on requested quality. The integration of fixed and mobile wireless access into IP networks presents a cost effective and efficient way to provide seamless end-to-end connectivity and ubiquitous access in a market where the demand for mobile Internet services has grown rapidly and predicted to generate billions of dollars in revenue. This tutorial covers to the issues of QoS provisioning in heterogeneous networks and Internet access over future wireless networks. It discusses the characteristics of the Internet, mobility and QoS provisioning in wireless and mobile IP networks. This tutorial also covers routing, security, baseline architecture of the inter-networking protocols and end to end traffic management issues. T2. Secure Routing Much has been written about the need for security on the Internet. However, little attention has been paid to securing the interactions among the routers that connect the Internet together. The Internet consists of many "Autonomous Systems" (ASes) (collections of routers with a common routing policy); routing between ASes has different goals from routing within an AS. In this tutorial, we will start with the motivation for routing security, and discuss the reasons why it has not seen widespread deployment, especially for intra-AS routing. We will then provide details on the threats to be overcome, and the approaches used, along with examples from existing protocol specifications. The issue of configuring routers automatically will be discussed. Finally, we will present a model for the management of routing security, which is being used to develop the capability to overcome the reluctance of Internet network managers to secure their networks. T3. A New Unified Model of Custom Software Costs Determination in Contracts Functional Size Measurement Methods are becoming quite common in the software engineering academic and business community but their contractual usage is still quite primitive. Many software development or enhancement contracts are based exclusively on the functional size as a cost driver. No explicit consideration is given to requirements which are not proportional to functionality within individual (single project) or broad (multi-project) contracts. As the ISBSG data strongly suggest, effort is not completely explained by the relation with the functional size. Much of the variance is due to non functional and process requirement, which are only partially correlated to Function Points. Spreading those costs on the FP measurement is an error because it pollutes unitary prices. Having only one average unitary price in a broad contract (long period, many projects...) seems to be a good choice because of the statistical compensations: a global equity is achieved by the means of local iniquities that compensate one with each other. In reality, things are different. No project is accepted as a "looser" just because another project is a "winner". Global equity may only be achieved by the mean of local equity. Different projects may need different unitary prices and so we need a contractual setting capable to face this requirement. This presentation will show how to build a specific price for custom software production considering functional and non functional requirements, expected average productivity, adjustment factors, resources mix, unitary human resource prices, life cycle phases and distribution of effort and roles and expected gross profit. It will also highlight traps that could affect the contractual economical relationship. |
||||
Copyright (c) 2006-2014, IARIA