BoxedApp SDK 1.0
Why do i need BoxedApp SDK?
BoxedApp SDK is used to create virtual file system and a system registry for any application. So you can create temporary fake registry keys, entries and values, virtual files and etc.
When BoxedApp SDk can be useful?
- When your application must run but you do not have rights to enter necessary registry keys or to write to the file system.
- When your application uses DLL wich are secure and you cann’t save them
- For your application wich requires ActiveX but you don’t have installer to run it now.
BoxedApp SDk 1.0 Features:
- Create virtual files
- Create virtual registry keys
- Embed DLL
- Embed ActiveX / OCX
There are a lot of examples written on C++, Delphi, C# etc.
You can DOWNLOAD a demo version of BoxedApp SDK 1.0 HERE
PRICE-S Model
The PRICE-S model was originally developed at RCA for use internally on software projects such as some that were part of the Apollo moon program. It was then released in 1977 as a proprietary model and used for estimating several US DoD, NASA and other government software projects. The model equations were not released in the public domain, although a few of the model’s central algorithms were published in. The tool continued to become popular and is now marketed by PRICE Systems, which is a privately held company formerly affiliated with Lockheed Martin. As published on PRICE Systems website (http://www.pricesystems.com), the PRICE-S Model consists of three submodels that enable estimating costs and schedules for the development and support of computer systems. These three submodels and their functionalities are outlined below:
The Acquisition Submodel: This submodel forecasts software costs and schedules. The model covers all types of software development, including business systems, communications, command and control, avionics, and space systems. PRICE-S addresses current software issues such as reengineering, code generation, spiral development, rapid development, rapid prototyping, object-oriented development, and software productivity measurement.
The Sizing Submodel: This submodel facilitates estimating the size of the software to be developed. Sizing can be in SLOC, Function Points and/or Predictive Object Points (POPs). POPs is a new way of sizing object oriented development projects and was introduced in based on previous work one in Object Oriented (OO) metrics done by Chidamber et al. and others.
The Life-cycle Cost Submodel: This submodel is used for rapid and early costing of the maintenance and support phase for the software. It is used in conjunction with the Acquisition Submodel, which provides the development costs and design parameters.
PRICE Systems continues to update their model to meet new challenges. Recently, they have added Foresight 2.0, the newest version of their software solution for forecasting time, effort and costs for commercial and non-military government software projects.
Software Development Cost Estimation
Software development cost models and estimation techniques are used for a number of purposes.
These include:
- Budgeting: the primary but not the only important use. Accuracy of the overall estimate is the most desired capability.
- Tradeoff and risk analysis: an important additional capability is to illuminate the cost and schedule sensitivities of software project decisions (scoping, staffing, tools, reuse, etc.).
- Project planning and control: an important additional capability is to provide cost and schedule breakdowns by component, stage and activity.
- Software improvement investment analysis: an important additional capability is to estimate the costs as well as the benefits of such strategies as tools, reuse, and process maturity.
Just like in any other field, the field of software engineering cost models has had its own pitfalls. The fast changing nature of software development has made it very difficult to develop parametric models that yield high accuracy for software development in all domains. Software development costs continue to increase and practitioners continually express their concerns over their inability to accurately predict the costs involved. One of the most important objectives of the software engineering community has been the development of useful models that constructively explain the development life-cycle and accurately predict the cost of developing a software product. To that end, many software estimation models have evolved in the last two decades based on the pioneering efforts of the above mentioned researchers. The most commonly used techniques for these models include classical multiple regression
approaches. However, these classical model-building techniques are not necessarily the best when used on software engineering data.