465,068 research outputs found

    Integrating automated support for a software management cycle into the TAME system

    Get PDF
    Software managers are interested in the quantitative management of software quality, cost and progress. An integrated software management methodology, which can be applied throughout the software life cycle for any number purposes, is required. The TAME (Tailoring A Measurement Environment) methodology is based on the improvement paradigm and the goal/question/metric (GQM) paradigm. This methodology helps generate a software engineering process and measurement environment based on the project characteristics. The SQMAR (software quality measurement and assurance technology) is a software quality metric system and methodology applied to the development processes. It is based on the feed forward control principle. Quality target setting is carried out before the plan-do-check-action activities are performed. These methodologies are integrated to realize goal oriented measurement, process control and visual management. A metric setting procedure based on the GQM paradigm, a management system called the software management cycle (SMC), and its application to a case study based on NASA/SEL data are discussed. The expected effects of SMC are quality improvement, managerial cost reduction, accumulation and reuse of experience, and a highly visual management reporting system

    Object oriented development of engineering software using CLIPS

    Get PDF
    Engineering applications involve numeric complexity and manipulations of a large amount of data. Traditionally, numeric computation has been the concern in developing an engineering software. As engineering application software became larger and more complex, management of resources such as data, rather than the numeric complexity, has become the major software design problem. Object oriented design and implementation methodologies can improve the reliability, flexibility, and maintainability of the resulting software; however, some tasks are better solved with the traditional procedural paradigm. The C Language Integrated Production System (CLIPS), with deffunction and defgeneric constructs, supports the procedural paradigm. The natural blending of object oriented and procedural paradigms has been cited as the reason for the popularity of the C++ language. The CLIPS Object Oriented Language's (COOL) object oriented features are more versatile than C++'s. A software design methodology based on object oriented and procedural approaches appropriate for engineering software, and to be implemented in CLIPS was outlined. A method for sensor placement for Space Station Freedom is being implemented in COOL as a sample problem

    Proposed Methodology for Crowdsourcing and Agile Development

    Get PDF
    In this research work, devised a methodology for ‘crowdsourcing’ focused on incorporating these methods to Agile Development in software engineering. The whole SDLC model for crowdsourcing is developed and tried to be integrated with Agile. This is done in order to speed up the process of Agile Development as Agile is a Rapid Application Development (RAD) based software engineering methodology. The ‘workers’ of the crowdsourcing process are individually assigned the Roles of the Agile methods that function upon the Agile tasks and produce the deliverables. Keywords: Crowdsourcing, Requirement Elicitation, Tasks Hierarchy Diagram, Concurrent Task Mode

    Integration issues of information ingineering based I-CASE tools

    Full text link
    Problems and requirements regarding integration of methods and tools across phases of the software-development life cycle are discussed. Information engineering (IE) methodology and I-CASE (integrated CASE) tools supporting IE claim to have an integrated view across major stages of enterprise-wide information-system development: information strategy planning, business area analysis, system design, and construction. In the main part of this paper, two comprehensive I-CASE tools, ADW (Application Development Workbench) and IEF (Information Engineering Facility), are analyzed and compared with regard to integration issues.<br/

    Sustainability in Software Engineering: A Design Science Research Approach

    Get PDF
    In the current global context, with so many challenges to be faced, it is important to see people’s increased interest in sustainability issues as an opportunity for change. Sustainable Software Engineering, as a recent research area, incorporates sustainability principles and dimensions in the software development process. On the other hand, the Design Science Research methodology has become a well-received research paradigm in Information Systems in general and in Software Engineering in particular. The paper presents a Sustainable Software Engineering approach integrated into the Design Science Research methodology. The concepts of sustainability in software development, namely the principles of the Karlskrona Manifesto, the principles of Green Software Engineering and the Sustainable Development Goals are integrated into the approach. Preliminary results from applying the approach indicate that the iterative process of the Design Science Research methodology allows for the integration of multidisciplinary sustainability artefacts during the software process

    The Environment for Application Software Integration and Execution (EASIE) version 1.0. Volume 1: Executive overview

    Get PDF
    The Environment for Application Software Integration and Execution (EASIE) provides a methodology and a set of software utility programs to ease the task of coordinating engineering design and analysis codes. EASIE was designed to meet the needs of conceptual design engineers that face the task of integrating many stand-alone engineering analysis programs. Using EASIE, programs are integrated through a relational database management system. Volume 1, Executive Overview, gives an overview of the functions provided by EASIE and describes their use. Three operational design systems based upon the EASIE software are briefly described

    THE BUSINESS CASE FOR AUTOMATING SOFTWARE METRICS IN OBJECT-ORIENTED COMPUTER AIDED SOFTWARE ENGINEERING ENVIRONMENTS

    Get PDF
    This paper makes the business case for automating the collection of software metrics for gauging development performance in integrated computer aided software engineering (CASE) environments that are characterized by an object-oriented development methodology and a centralized repository. The automation of function point analysis is discussed in the context of such an integrated CASE environment (ICE). We also discuss new metrics that describe three different dimensions of code reuse -- leverage, value and classification -- and examine the p,ossibility of utilizing objects as means to estimate software development labor and measure productivity. We argue that the automated collection of these software metrics opens up new avenues for refining the management of software development projects and controlling stra-egic costs.Information Systems Working Papers Serie
    • …
    corecore