it service management software PDF: 1 to 10 of 415 results fetched - page 1 [ao]

Zoolz is the only cloud solution that keeps your data even when you disconnect your drives

DTIC ADA433126: Improving Software Quality and Management Through Use of Service Level Agreements

www.archive.org/details/DTIC_ADA433126...
In this dissertation we explore the use of service level agreements (SLAs) to improve the quality and management of software intensive systems. SLAs are typically used in outsourcing contracts for post-production support. We propose that SLAs be used in software acquisition to support quality and process control throughout the lifecycle (requirements engineering through post-production support) of a software-intensive system. The hypothesis was tested using two methodologies. The first method explained how SLAs could be used throughout a system's lifecycle to improve software quality. This concept was validated by a survey of IT professionals. The results of the survey indicated that practitioners in the IT field felt that SLAs could be used to improve overall quality in the development effort and in the end product. The second approach was to develop actual SLAs for a specific lifecycle phase (post-production) to illustrate the concepts of SLAs and to demonstrate their value as a quality control and management tool.
Published on 05/25/2018
Document details: 434 pages. 5 downloads.

Improving software quality and management through use of service level agreements

www.archive.org/details/improvingsoftwar1094510040...
In this dissertation we explore the use of service level agreements (SLAs) to improve the quality and management of software intensive systems. SLAs are typically used in outsourcing contracts for post-production support. We propose that SLAs be used in software acquisition to support quality and process control throughout the lifecycle (requirements engineering through post-production support) of a software-intensive system. The hypothesis was tested using two methodologies. The first method explained how SLAs could be used throughout a system's lifecycle to improve software quality. This concept was validated by a survey of IT professionals. The results of the survey indicated that practitioners in the IT field felt that SLAs could be used to improve overall quality in the development effort and in the end product. The second approach was to develop actual SLAs for a specific lifecycle phase (post-production) to illustrate the concepts of SLAs and to demonstrate their value as a quality control and management tool.
Published on 05/04/2019
Document details: 435 pages. 1 download.

DTIC ADA486856: Beyond Reactive Planning: Self Adaptive Software and Self Modeling Software in Predictive Deliberation Management

www.archive.org/details/DTIC_ADA486856...
The purpose of this paper is to examine an approach to planning which extends beyond the traditional reactive planning state space. We present the following hypothesis: predictive deliberation management using self-adapting and self-modeling software will be required to provide mission planning adjustments after the start of a mission. Self-adaptive software evaluates its own behavior and changes behavior when the evaluation indicates that it is not accomplishing what the software is intended to do, or when better functionality or performance is possible. Self-modeling systems construct their own abstractions as a basis of computational intelligence. In order to provide a proper process context for the evolution of software toward this level of autonomy, and in alignment with the proposed planning maturity models, we put forth a concept of a NCW C2 Software Maturity Model. This new C2 software maturity model will take software beyond the service-oriented paradigm into a new era of software designing its own replacements or modifications in order to satisfy new command and control requirements.
Published on 06/25/2018
Document details: 27 pages. 4 downloads.

Enterprise Software Service Emulation: Constructing Large-Scale Testbeds

www.archive.org/details/arxiv-1605.06729...
Constructing testbeds for systems which are interconnected with large networks of other software services is a challenging task. It is particularly difficult to create testbeds facilitating evaluation of the non-functional qualities of a system, such as scalability, that can be expected in production deployments. Software service emulation is an approach for creating such testbeds where service behaviour is defined by emulate-able models executed in an emulation runtime environment. We present (i) a meta-modelling framework supporting emulate-able service modelling (including messages, protocol, behaviour and states), and (ii) Kaluta, an emulation environment able to concurrently execute large numbers (thousands) of service models, providing a testbed which mimics the behaviour and characteristics of large networks of interconnected software services. Experiments show that Kaluta can emulate 10,000 servers using a single physical machine, and is a practical testbed for scalability testing of a real, enterprise-grade identity management suite. The insights gained into the tested enterprise system were used to enhance its design.
Published on 06/29/2018
Document details: 27 pages. 2 downloads.

ERIC ED243460: Guide to Software Conversion Management. [Final Report.]

www.archive.org/details/ERIC_ED243460...
Based mainly on interviews conducted at 14 federal agencies that had completed or were involved in software conversion projects, this publication provides guidelines for the entire process of software conversion. This is defined as the transformation, without functional change, of computer programs or data elements to permit their use on a replacement or changed data processing or teleprocessing system or service. It is noted that a conversion involving non-code compatible machines is assumed since this situation produces the most problems. Following introductory information, six phases of the conversion life cycle are described: project initiation; the conversion requirements phase where studies and analyses are conducted to identify agency requirements and cost considerations; the conversion planning phase; the conversion preparation phase; the actual conversion phase; and the post-conversion phase. The objectives, activities, and management considerations involved in each phase are outlined. Appendices include a 51-item bibliography; a list of 23 conversion directives, standards, and other references produced by the federal government; an extensive methodology for software conversion costing; 11 case studies of software conversion projects at federal agencies; and a 27-item glossary. (ESR)
Published on 01/08/2015
Document details: 227 pages. 69 downloads.

DTIC ADA487810: Irreducible Truths of Software-Intensive Program Management

www.archive.org/details/DTIC_ADA487810...
This article argues that the odds are against a software-intensive program achieving the goals and objectives established in the initial acquisition program baseline. By most objective measures of success -- cost, schedule, and performance baselines -- almost every software-intensive program proves unsuccessful. Reasons for these failures are examined and solutions for improvement are discussed. The technical, social, and engineering skills required to be a better program manager or software engineer are necessary but not sufficient for success with a software-intensive program. The organizational environment must support the program objectives or the program will most likely fail. The proposed solution presupposes someone in power to observe behavior and reward or punish stakeholders as appropriate. A Program Manager must identify the senior leaders who have the greatest potential to impact the ongoing viability of the program (Pinto, 1996) and obtain their support. This more than any other factor will determine success or failure for most programs. A Project Manager's ability to find such support is more critical than any technique, skill, or tool taught in the classroom. Just about any process can work if it has real management support. Process cannot make up for lack of leadership support, but leadership support can mitigate process deficiencies. Do not forget that the success of the program ultimately depends on the ability to get stakeholders to do the things they often do not want to do. The behavior of individuals acting for or against the mission objectives controls the chance for success more than any other professional tool or skill employed on an acquisition program.
Published on 06/27/2018
Document details: 13 pages. 2 downloads.

Understand Your Chains: Towards Performance Profile-based Network Service Management

www.archive.org/details/arxiv-1703.08206...
Allocating resources to virtualized network functions and services to meet service level agreements is a challenging task for NFV management and orchestration systems. This becomes even more challenging when agile development methodologies, like DevOps, are applied. In such scenarios, management and orchestration systems are continuously facing new versions of functions and services which makes it hard to decide how much resources have to be allocated to them to provide the expected service performance. One solution for this problem is to support resource allocation decisions with performance behavior information obtained by profiling techniques applied to such network functions and services. In this position paper, we analyze and discuss the components needed to generate such performance behavior information within the NFV DevOps workflow. We also outline research questions that identify open issues and missing pieces for a fully integrated NFV profiling solution. Further, we introduce a novel profiling mechanism that is able to profile virtualized network functions and entire network service chains under different resource constraints before they are deployed on production infrastructure.
Published on 06/30/2018
Document details: 13 pages. 1 download.

Raising the degree of service-orientation of a SOA-based software system a case study

www.archive.org/details/raisingdegreeofs109454497...
The term \"service-oriented architecture (SOA)\" has been gaining popularity in the Department of Defense's (DoD) software engineering and IT community in recent years. It has become the next \"big thing\" and is the buzz word used at technical conferences and high level management meetings. But the term \"service-orientation\" has caused much confusion among program sponsors, government IT managers, and software professionals. Its apparent ambiguity has let them to claim their own interpretations of SOA. Many have been led to the notion that a technical architecture deemed service-oriented is simply one comprised of Web services. This is a common but dangerous assumption that leads to the number one mistake made by projects intending to adopt SOA-the perception that the benefits promised by current mainstream SOA are attainable solely through an implementation using the Web services platform. This paper will present a case study to illustrate that building an SOA-based application is not just about applying a particular set of technologies and standards but by following a set of sound design principles based on service-orientation. The biggest contribution of this paper is to show, by conducting a case study, that the use of Web services alone does not make a system service-oriented. The results of this paper can be used by IT professionals in the DoD to better evaluate the degree of service-orientation for a software system's architecture.
Published on 05/04/2019
Document details: 96 pages. 3 downloads.

DTIC ADA328660: Comparison of Tri-Service Spatial Data Standards (TSSDS), Release 1.6, and Intergraph Corporation Environmental Resource Management Application (ERMA) Software.

www.archive.org/details/DTIC_ADA328660...
This report compares the environmental portion of the Tri-Service Spatial Data Standards (TSSDS) to the default data structure provided with Intergraph Corporation's Environmental Resource Management Application (ERMA) software. The purpose of this comparison was to evaluate the ability of the ERMA product to support the data structures, attributes, and domains required by the TSSDS. This report was prepared to provide guidance to Department of Defense personnel and their contractors who may be implementing the TSSDS and may be using the ERMA suite of products. The information in this report will be used by the Tri-Service Computer Aided Drafting and Design (CADD)/Geographic Information System (GIS) Technology Center to help determine areas for further development of the TSSDS, and it will be provided to Intergraph Corporation for use in developing a TSSDS-compliant ERMA package.
Published on 04/07/2018
Document details: 254 pages. 3 downloads.

ERIC ED394407: Academic Scheduling and Management Software Program. Final Report and Recommendations.

www.archive.org/details/ERIC_ED394407...
This final report describes activities and findings of a project which examined computer-automated scheduling in institutions for higher education and secondary schools and selected two sources for scheduling systems products which it recommends to institutions in the member states of the Midwestern Higher Education Commission and members of the North Central Association of Colleges and Secondary Schools. It notes that automated systems can achieve significant administrative and cost efficiencies, but most are financially unattainable. The project selected two companies--Universal Algorithms and Applied Business Technologies--after a comprehensive review of available products and services over an 18-month period of research and inquiry. Submitted software was assessed for functional requirements, service expectations, and financial parameters for academic scheduling and management software in higher and secondary education. Negotiation of special pricing was accomplished to bring computer aided course scheduling on a variety of platforms within the financial reach of virtually all member institutions. Appendixes include detailed product information, survey results, and a copy of the original Request For Proposal. (Author/NAV)
Published on 12/12/2015
Document details: 44 pages. 82 downloads.
[1] 2345Next