Software Scope Research Articles

Low-cost Access to the Deep, High-cadence Sky: the Argus Optical Array

New mass-produced, wide-field, small-aperture telescopes have the potential to revolutionize ground-based astronomy by greatly reducing the cost of collecting area. In this paper, we introduce a new class of large telescope based on these advances: an all-sky, arcsecond-resolution, 1000 telescope array which builds a simultaneously high-cadence and deep survey by observing the entire sky all night. As a concrete example, we describe the Argus Array, a 5 m-class telescope with an all-sky field of view and the ability to reach extremely high cadences using low-noise CMOS detectors. Each 55 GPix Argus exposure covers 20% of the entire sky to m g = 19.6 each minute and m g = 21.9 each hour; a high-speed mode will allow sub-second survey cadences for short times. Deep coadds will reach m g = 23.6 every five nights over 47% of the sky; a larger-aperture array telescope, with an étendue close to the Rubin Observatory, could reach m g = 24.3 in five nights. These arrays can build two-color, million-epoch movies of the sky, enabling sensitive and rapid searches for high-speed transients, fast-radio-burst counterparts, gravitational-wave counterparts, exoplanet microlensing events, occultations by distant solar system bodies, and myriad other phenomena. An array of O(1000) telescopes, however, would be one of the most complex astronomical instruments yet built. Standard arrays with hundreds of tracking mounts entail thousands of moving parts and exposed optics, and maintenance costs would rapidly outpace the mass-produced-hardware cost savings compared to a monolithic large telescope. We discuss how to greatly reduce operations costs by placing all optics in thermally controlled, sealed domes with only a few moving parts. Coupled with careful software scope control and use of existing pipelines, we show that the Argus Array could become the deepest and fastest Northern sky survey, with total costs in the $20M range.

A Framework of Software Project Scope Definition Elements: An ISM-DEMATEL Approach

Software project scope definition is complicated due to the diversity and magnitude of the information needed. An inadequate scope definition often results in project failure as it continues to emerge as the major cause of delays, changes/rework, and cost and schedule overruns. Literature mentions different tools and methods to verify, quantify, and control software scope definition. However, none of these methods and tools help in defining a complete scope. Since a well-defined scope in the early stages is a core ingredient for project success, therefore, previously we developed a method that includes 45 elements of the software project scope definition. Although these elements are noteworthy for project scope, some may influence others; and should be concentrated on more when defining the scope of the software projects. The objective of this present study is that it builds on our previous research and uses Interpretive Structural Modeling (ISM) to extract the interrelationships among the elements and Decision Making Trial and Evaluation Laboratory (DEMATEL) to determine the intensity of these relationships. Experts from academia and the software development industry were consulted to identify the relationships among the elements. ISM-DEMATEL approach indicates that the project manager's competence is the main driver. Further, requirements, stakeholders' expectations, cost estimates, project schedule, resource estimation, project summary, communication, consultation, top management support are among the most influential elements that are critical to focus on. Moreover, the findings of the study provide project managers with a better understanding of the elements and their interconnections thus, helping in achieving a better scope definition.

Ensemble Regression Models for Software Development Effort Estimation: A Comparative Study

As demand for computer software continually increases, software scope and complexity become higher than ever. The software industry is in real need of accurate estimates of the project under development. Software development effort estimation is one of the main processes in software project management. However, overestimation and underestimation may cause the software industry loses. This study determines which technique has better effort prediction accuracy and propose combined techniques that could provide better estimates. Eight different ensemble models to estimate effort with Ensemble Models were compared with each other base on the predictive accuracy on the Mean Absolute Residual (MAR) criterion and statistical tests. The results have indicated that the proposed ensemble models, besides delivering high efficiency in contrast to its counterparts, and produces the best responses for software project effort estimation. Therefore, the proposed ensemble models in this study will help the project managers working with development quality software.

A new digital denture procedure: a first practitioners appraisal

BackgroundHistorically, the complete removable denture is the last prosthetic procedure to switch to digital techniques whose advantages are mainly observed in the laboratory stages; however, it is not possible to measure the depressibility of the oral mucosa using optical cameras, thus conventional impression techniques are still necessary. This article describes the clinical and laboratory procedure and practitioners appraisal of the first fifteen digitally designed complete removable dental prostheses.MethodsSeveral systems are now available including the Wieland® Digital Denture® which offers a complete procedure. This system is composed of a five axis-milling machine combined with a laboratory scanner and a design software application. Fifteen rehabilitations were carried out using the Wieland® system.ResultsThe practitioner’s role is simplified by intraoral recording with a central point and a reduced number of sessions. The prosthesis laboratory requires considerable investment in learning and equipment, making it possible to obtain ideal mounting assemblies in accordance with the occluso-prosthetic concept of bilateral balanced occlusion. The absence of polymerization and therefore of base deformation risks reduce the equilibration step. Finally, the creation of templates as an alternative to the assembly of teeth on wax makes it possible to functionally validate (masticatory and phonatory) the future dentures. However, this procedure still presented some limitations in terms of scanning and software scope of applications.ConclusionDigital denture design software is relatively efficient and helps to standardize clinical results. However, to this date, improvements of the software are still required for a routine use.

Calculating completeness of software project scope definition

ContextSoftware project plan is the basis of the project execution, and its quality depends on completeness of software scope definition. A method is required that should gauge the completeness of different aspects of scope definition, thus, providing guidance to practitioners to reconsider areas that have not been defined well. ObjectiveThis paper aims to evaluate completeness of software project scope definition. It identifies a detailed list of different aspects of software project scope definition, and builds a method where numerical score can be assigned to a scope definition. MethodA detailed list of different elements of software project scope definition is identified through literature. These elements are then empirically evaluated through an electronic survey, conducted with the industrial experts. Once finalized, these elements are ranked and assigned weights to systematically build a scorecard that is used to calculate scope definition score. Evaluation of the proposed method is done through a series of formal experiments. ResultsEvaluation results suggest that the proposed method is useful not only in calculating completeness of software projects scope definition, but it also serves as a guide for practitioners to determine specific aspects that require further consideration.

WORK BREAKDOWN STRUCTURE: A TOOL FOR SOFTWARE PROJECT SCOPE VERIFICATION

Software project scope verification is a very important process in project scope management and it needs to be performed properly and thoroughly so as to avoid project rework and scope creep. Moreover, software scope verification is crucial in the process of delivering exactly what the customer requested and minimizing project scope changes. Well defined software scope eases the process of scope verification and contributes to project success. Furthermore, a deliverable-oriented WBS provides a road map to a well defined software scope of work. It is on the basis of this that this paper extends the use of deliverable-oriented WBS to that of scope verification process. This paper argues that a deliverable-oriented WBS is a tool for software scope verification.

Work Breakdown Structure: A Tool for Software Project Scope Verification

Software project scope verification is a very important process in project scope management and it needs to be performed properly and thoroughly so as to avoid project rework and scope creep. Moreover, software scope verification is crucial in the process of delivering exactly what the customer requested and minimizing project scope changes. Well defined software scope eases the process of scope verification and contributes to project success. Furthermore, a deliverable-oriented WBS provides a road map to a well defined software scope of work. It is on the basis of this that this paper extends the use of deliverable-oriented WBS to that of scope verification process. This paper argues that a deliverable-oriented WBS is a tool for software scope verification

“Quality of prenatal and maternal care: bridging the know-do gap” (QUALMAT study): an electronic clinical decision support system for rural Sub-Saharan Africa

BackgroundDespite strong efforts to improve maternal care, its quality remains deficient in many countries of Sub-Saharan Africa as persistently high maternal mortality rates testify. The QUALMAT study seeks to improve the performance and motivation of rural health workers and ultimately quality of primary maternal health care services in three African countries Burkina Faso, Ghana, and Tanzania. One major intervention is the introduction of a computerized Clinical Decision Support System (CDSS) for rural primary health care centers to be used by health care workers of different educational levels.MethodsA stand-alone, java-based software, able to run on any standard hardware, was developed based on assessment of the health care situation in the involved countries. The software scope was defined and the final software was programmed under consideration of test experiences. Knowledge for the decision support derived from the World Health Organization (WHO) guideline “Pregnancy, Childbirth, Postpartum and Newborn Care; A Guide for Essential Practice”.ResultsThe QUALMAT CDSS provides computerized guidance and clinical decision support for antenatal care, and care during delivery and up to 24 hours post delivery. The decision support is based on WHO guidelines and designed using three principles: (1) Guidance through routine actions in maternal and perinatal care, (2) integration of clinical data to detect situations of concern by algorithms, and (3) electronic tracking of peri- and postnatal activities. In addition, the tool facilitates patient management and is a source of training material. The implementation of the software, which is embedded in a set of interventions comprising the QUALMAT study, is subject to various research projects assessing and quantifying the impact of the CDSS on quality of care, the motivation of health care staff (users) and its health economic aspects. The software will also be assessed for its usability and acceptance, as well as for its influence on workflows in the rural setting of primary health care in the three countries involved.ConclusionThe development and implementation of a CDSS in rural primary health care centres presents challenges, which may be overcome with careful planning and involvement of future users at an early stage. A tailored software with stable functionality should offer perspectives to improve maternal care in resource-poor settings.Trial registrationhttp://www.clinicaltrials.gov/NCT01409824.

Service-oriented Controllable Multicast Model for Next Generation Internet

With the development of the IPv6 networks, more and more applications put forward to use multicast. Multicast security and management is one of the key issues for IP multicast services deployment in IPv6 network as in IPv4 network. We introduce the idea of Service-Oriented Architecture (SOA) in software scope to multicast service, and design a Service-oriented Controllable Multicast Model (SOCMM) for IPv6 multicast services. And the reference implementation of this model is proposed in this paper. DOI: http://dx.doi.org/10.11591/telkomnika.v11i3.2207

OS6-5 Development of Risk-Based Maintenance Software for Gas Turbines

"RISKWISE^<TM> for Gas Turbines" has been developed to perform risk-based maintenance and inspection planning on gas turbine hot gas path components. The software allows the user to easily prepare a risk matrix, plotting every active damage mechanism for each hot gas path component. Based on the result of the risk assessments the components can be ranked, allowing inspection plans to be focused and prioritised and aiding the user to identify the most appropriate and effective risk mitigating activity within the software. Risk assessments are performed on a component by component basis, with the software's scope including all combustor and turbine hot gas path components. The software also contains comprehensive help documents to aid the user in identifying and assessing peculiar damage mechanisms and prescribing the most effective inspection methods for gas turbines.

Real work, necessary friction, optional chaos

Challenges in estimating software scope by effort.

The case for reverse engineering

It may seem hard to choose between two software products, but studying their databases can reveal a clear winner and save you years of grief. The most productive way to reverse engineer a database is to build a model that conveys the software's scope and intent. For a clean database, you'll most likely want to prepare a model; for a flawed and poorly documented database, it may be best to stop after studying the style and quality of the database structure. At OMT Associates, we generally construct models-usually expressed as Unified Modeling Language (UML) object models. We typically organize reverse engineering into three phases-implementation recovery, design recovery, and analysis recovery. Reverse engineering is more than just a process for studying databases; it has profound implications for software development in general. You might view the reverse engineering of vendor databases as a creative response to the so-called software crisis. The current approach of preaching methodology and discipline isn't working, Software quality and development productivity still badly lag behind our desires. Database reverse engineering gives us both a carrot and a stick. The flaws and excellence of various products become more obvious and more heavily influence product success and failure. For a large corporation, the cost of the evaluation (as little as a few person-weeks) is trivial compared to the millions spent buying and deploying new software.