Ryoei Yoshioka, Y. Watanobe, Nikolay Mirenkov · Frontiers in artificial intelligence and applications · 2008
A general scheme of software development process is considered and some aspects related to integrating security into this scheme are analyzed. In particular, semantic-based, defense-in-depth techniques embedded into system/component defense shields and data acquiring/monitoring kernels are considered. The defense shields are to semantically check data of every input before a software component may process them and also to check every output before sending it to other components. The kernels are to regularly perform semantic analysis of the internal status and local data of a component/system. Based on these two ideas, real-time discovery of vulnerabilities and threats is possible even when various protective measures, such as, passwords, firewalls, intrusion detection systems, access control lists, etc. have been breached. Existing programming systems and possible new methods to realize the shields and kernels are also considered.
Cited by 0
Matvei Braginski · 2009
Up to these days, development control still is not well-explored as to operational guidelines and applications. In this report, the author brings forward his observations regarding software development management organisation, gives options of management configuration, as well as discussion and analysis thereof. The author suggests a scheme of development documentary support which improves quality, portability and makes easier further support of developed software.
Cited by 0
Robert H Yacobellis · 1984
This paper describes a framework for gathering and reporting software and development process quality metrics, as well as data engineering issues related to data collection and report generation. The framework is described in project-independent terms, including a methodology for applying metrics to a given software project. A key aspect of this application is the use of project milestones predicted by a failure rate model. For the purposes of this paper, a software project is one which delivers a software or system product, and involves between thirty and several hundred developers, testers, and project managers.
Cited by 3
Caldeira, Joao · Mendeley Data · 2020
Dataset for article IDE-based Software Development Process Analytics
Cited by 0Open access
Fred C. Briggs · AIAA Infotech@Aerospace Conference · 2009
This is a survey paper of various systems engineering methods used in the software requirements definition and development process. The ratio of software to hardware in aerospace systems has increased dramatically in favor of software over the last twenty years. Currently, most of the systems in aerospace vehicles are controlled by, and cannot function without, software. Studies have found that 12-13 percent of all projects are late or did not meet expectations because of incomplete or changing software requirements and specifications. This paper investigates aerospace software engineering practices, tools, literature, and research with respect to approaches to software requirements definition and analysis. It also discusses a systems engineering process that includes software development. Observations show early and thorough requirements analysis is the most cost effective and efficient means of implementing a software program. I. Introduction Aerospace systems engineering programs start with the Concept Refinement Phase, followed by Technology Development, System Development and Demonstration, Production and Deployment, and lastly the Operations and Support Phase. Within these phases the software development life cycle is embedded. This makes the design and development of software a critical part of any new or upgraded development program. The cost of repairing a software defect has been shown to increase dramatically the later it is found in the life-cycle. Technical performance parameters such as size constraints, impact on throughput performance, power required, and memory utilization are related to the systems engineering process discussed later in this paper. Observations are presented for technical directors, lead systems engineers, and software project managers to make intelligent and cost-effective decisions with respect to software requirements during software development life-cycles.
Cited by 0
Orsolya Dobán, András Pataricza · 2002
The need for more and more dependable systems has been increased in the last decades. Strategic decisions during the design of these dependable systems require the joint control of the estimated cost and the product quality. Cost efficiency and development time became the most important factors of the software development process according to the international trends. The estimation of the cost remains a difficult problem till yet, despite of the use of standard, easy to understand modelling languages. On the other hand no working environment is known supporting the gradually refined cost estimation derived automatically from the formal product models. In this paper the experiments of a pseudo cost estimation are detailed with a special emphasis on the cost estimation driven system design.
Cited by 8
R. James Rockwell · Lecture notes in computer science · 2005
Cited by 0
Shaun Phillips, K. J. King · NASA STI Repository (National Aeronautics and Space Administration) · 2015
Cited by 0Open access
Škultinas, Tomas, · KTUePubl (Repository of Kaunas University of Technology) · 2005
Cited by 0Open access
Veronika Thurner · 1997
This paper is structured into two parts, dealing with notational and methodological aspects, respectively. The first part introduces a description technique for business processes which provides both an intuitive, graphical notation and a textual syntax. The definition of semantics of this description technique is related to a mathematical system model. Using this mathematical system model as a common formal basis, the relation between business process model and other models employed in software development can be precisely defined. In the second part, a business process driven method of software development is outlined, as well as a systematic approach to business process reengineering. As software development and business process reengineering are closely related and often occur together in practice, these two approaches will be integrated into a method which systematically combines both techniques. 1 Motivation and State of the Art In many software engineering methods, approaches t...
Cited by 0
Michał R. Wróbel · 2013
This paper presents the results of a survey on the experience of emotions in the work of software developers. Quantitative analysis revealed information about emotions affecting programmers, their frequency and impact on their performance. The concept of emotional risk to productivity was also presented. It allows to choose the emotional states, which should be avoided. Furthermore, all collected data were analyzed with information about the experience of developers. In addition to most hazardous emotions, those with the most positive impact on productivity were selected.
Cited by 111
Maria Laura Sebu, Horia Ciocârlie · 2014
Current study uses the event process logs of a custom software development process used internally in the IT department of a large automotive company. The target is to extract hidden information about the process, difficult to identify due to the wideness and complexity of the input data. The log file contains all incident records tracked during one release of a software product. This analysis was performed using process mining techniques and tools included in ProM Framework, an academic project of the Eindhoven Technical University. The paper describes the steps followed to extract the working process model, organizational network and statistical information. Based on the obtained results, an action plan is put in practice with the scope of improving the development process and the release result.
Cited by 19
Jan Lemmens · Document Server@UHasselt (UHasselt) · 2009
Mede door de steeds uitbreidende mogelijkheden van de computer, is deze alomtegenwoordig geworden in ons dagelijkse leven. We kunnen bijvoorbeeld met behulp van onze mobiele telefoon een voetbalwedstrijd volgen, terwijl we de wasmachine programmeren met behulp van een touch screen. Deze mogelijkheden worden geïmplementeerd in software. Het ontwikkelen van deze software gebeurt tijdens een proces dat Software Engineering wordt genoemd. Software Engineering is een tak van de informatica die zich bezighoudt met het ontwikkelen en onderhouden van software. In deze thesis worden bepaalde onderdelen van Software Engineering behandeld die de focus leggen op het creëren van gebruiksvriendelijke en bruikbare software en dit op een 'exibele en snelle manier. Er wordt gestart met een onderzoek naar Agile Software Engineering, gevolgd door een uiteenzetting over User-Centered Design. Een combinatie van deze twee methoden blijkt namelijk een goed uitgangspunt te zijn voor het bouwen van software di
Cited by 0Open access
El Soudani, Magdi M. Said · Qatar University QSpace (Qatar University) · 1995
This paper aims to standardize the software development process by making use of the well-established hardware development process. The procedure can be applied to any engineering software development process, but we consider the case of communication systems. We propose a model for software development process that has a hierarchical structure. We examine this hierarchical structure together with the development process at each level. Each process has several stages, and we use the same definitions at all levels. The development process consists of the following stages: requirements and specification, flow detailed structure, source coding, and testing stages. Integration of the whole system is performed in steps through different testing levels. During the development process we measure the performance or the quality of each stage. We consider the factors that have great impact on software quality and that may be the cause of defects. These includes complexity, supporting tools and methods, and system ability, and from these factors we define some quality attributes to measure the system quality.
Cited by 0Open access
Jakub Maléř · Digital Repository (National Repository of Grey Literature) · 2006
Cílem této diplomové práce je popis problematiky vývoje internetových aplikací na platformě Java. Dalším cílem je vytvořit aplikaci podle požadavků zákazníka. V úvodu práce se zabývám problematikou aplikačních frameworků, zaměřuji se na Spring Framework. V další kapitole rozebírám vhodné technologie pro vytváření vzhledu internetových stránek a možnosti jejich využití se Springem. Dále se věnuji problematice ukládání dat s důrazem na využití ORM a Hibernate. Popisuji také možnost využití aspektově orientovaného programování a jeho podporu ve Springu. V závěru práce obsahuje praktickou ukázku využití teoretických znalostí při vývoji internetové aplikace. Je popsán postup vývoje aplikace s využitím vývojového prostředí Eclipse a metodiky extrémního programování.
Cited by 0
Ahsan Nawaz, Kashif Masood Malik, Ahsan Nawaz et al. · 2008
Cited by 0
American Institute of Aeronautics and Astronautics eBooks · 1991
Cited by 0
Dennis de Champeaux · ACM SIGPLAN OOPS Messenger · 1992
A 92 Vancouver, British Columbia, Canada 5 - 10 October 1992 Addendum to the Proceedings Panel Report- The 00 Software Development Process Report by: Dennis de Champeaux HP-Labs Members of the panel Dermis de Champeaux, HP-Lab, moderator Bob Balzer, Information Sciences Institute Dave Bulman, Pragmatics Kathleen Culver-Lozo, AT&T Bell Laboratories Ivar Jacobson, Objectory Stephen J. Mellor, Project Technology Pankaj Garg, HP-Lab, co-organizer of the panel Aim of the panel Improving development processes is a key issue for the software community in general. The literature gives us some guidance with respect to major activities of the development process. The waterfall, spiral and fountain model all agree upon distinctions such as: requirements capture, analysis, design, implementation, testing, maintenance. They also agree in that they do not provide a finer granularity of the inside activities of analysis and design. We postulate that this omission is a key inhibitor to a more widespread acceptance of the 00 paradigm by project managers. They do not know how to plan a non-trivial 00 software development project. The purpose of this panel was to take the first steps towards developing such process models. More 5-10 October 1992 -61- specifically the panelists have been asked to address the following questions (among others): . Can you envision a generic OOA/ OOD development process? If so what are the major steps and deliverables of these steps. If not, why not? l If a software development organization had to choose between either doing a paradigm shift to 00, or improving its rating on the SE1 maturity scale what would you recommend? What are the relationships between the two? Qualify, if necessary, the answer with respect to an extant maturity level. It turned out that these, and the other questions, were quite hard for the panellists. Hence, we envision a follow on panel in the future where these topics will be raised again. In addition to this panel, I organized in 1992, workshops on 00 process: one at ECOOP and one also at OOPSLA. All the events had in common that the presenterslpanelists had hardly anything to say about process. The most tangible contributions were modest extensions of the standard macro process: requirements capture, analysis, design, implementation, test, maintenance, enhanced, of course, by the recommendation to iterate. Addendum to the Proceedings Hence, although the panel had lively exchanges, I refrain from giving the details because I do not feel that the state of the art was advanced. Instead I would like to point the reader to a report that proposes some details on the 00 analysis and design process: Dennis de Champeaux, Towards an 00 SW Development Process, HP-Labs Tech Report HPL-92-149, November 1992. [The contributors Doug Lea, Penelope Faure, and Mohammed Fayad could not be listed as authors for legal reasons.] For a copy contact: HP-Labs/ Technical Publications Dept./ 1501 Page Mill Rd Palo Alto, CA 94304 (415) 857 4573 OOPSLA92 -62 - Vancouver, British Columbia
Cited by 0
Richard F. Schmidt · Elsevier eBooks · 2013
Cited by 0
DISTEFANO, SALVATORE, M. Scarpa, A. Puliafito · Virtual Community of Pathological Anatomy (University of Castilla La Mancha)
Cited by 0