scholarly journals Efficiently Building On-line Tools for Distributed Heterogeneous Environments

2002 ◽  
Vol 10 (1) ◽  
pp. 67-74
Author(s):  
Günther Rackl ◽  
Thomas Ludwig ◽  
Markus Lindermeier ◽  
Alexandros Stamatakis
Keyword(s):  
Image Reconstruction ◽  
Software Development ◽  
High Performance ◽  
Development Process ◽  
Test Case ◽  
Heterogeneous Environments ◽  
Major Drawback ◽  
Performance Improvements ◽  
Performance Requirements ◽  
On Line

Software development is getting more and more complex, especially within distributed middleware-based environments. A major drawback during the overall software development process is the lack of on-line tools, i.e. tools applied as soon as there is a running prototype of an application. The MIMO MIddleware MOnitor provides a solution to this problem by implementing a framework for an efficient development of on-line tools. This paper presents a methodology for developing on-line tools with MIMO. As an example scenario, we choose a distributed medical image reconstruction application, which represents a test case with high performance requirements. Our distributed, CORBA-based application is instrumented for being observed with MIMO and related tools. Additionally, load balancing mechanisms are integrated for further performance improvements. As a result, we obtain an integrated tool environment for observing and steering the image reconstruction application. By using our rapid tool development process, the integration of on-line tools shows to be very convenient and enables an efficient tool deployment.

Agile Software Development Quality Assurance

2009 ◽  
pp. 2680-2699
Author(s):  
James F. Kile ◽  
Maheshwar R. Inampudi
Keyword(s):  
Software Development ◽  
High Performance ◽  
General Rule ◽  
Adaptive Methods ◽  
Agile Software Development ◽  
Agile Development ◽  
Performance Requirements ◽  
Small Project ◽  
Software Development Methodologies ◽  
Agile Software

Of great interest to software development professionals is whether the adaptive methods found in agile methodologies can be successfully implemented in a highly disciplined environment and still provide the benefits accorded to fully agile projects. As a general rule, agile software development methodologies have typically been applied to non-critical projects using relatively small project teams where there are vague requirements, a high degree of anticipated change, and no significant availability or performance requirements (Boehm & Turner, 2004). Using agile methods in their pure form for projects requiring either high availability, high performance, or both is considered too risky by many practitioners (Boehm et al., 2004; Paulk, 2001). When one investigates the various agile practices, however, one gets the impression that each may still have value when separated from the whole. This chapter discusses how one team was able to successfully drive software development quality improvements and reduce overall cycle time through the introduction of several individual agile development techniques. Through the use of a common-sense approach to software development, it is shown that the incorporation of individual agile techniques does not have to entail additional risk for projects having higher availability, performance, and quality requirements.

Agile Software Development Quality Assurance

2011 ◽  
pp. 186-205
Author(s):  
J. Kile
Keyword(s):  
Software Development ◽  
High Performance ◽  
General Rule ◽  
Adaptive Methods ◽  
Agile Software Development ◽  
Agile Development ◽  
Performance Requirements ◽  
Small Project ◽  
Software Development Methodologies ◽  
Agile Software

Of great interest to software development professionals is whether the adaptive methods found in agile methodologies can be successfully implemented in a highly disciplined environment and still provide the benefits accorded to fully agile projects. As a general rule, agile software development methodologies have typically been applied to non-critical projects using relatively small project teams where there are vague requirements, a high degree of anticipated change, and no significant availability or performance requirements (Boehm & Turner, 2004). Using agile methods in their pure form for projects requiring either high availability, high performance, or both is considered too risky by many practitioners (Boehm et al., 2004; Paulk, 2001). When one investigates the various agile practices, however, one gets the impression that each may still have value when separated from the whole. This chapter discusses how one team was able to successfully drive software development quality improvements and reduce overall cycle time through the introduction of several individual agile development techniques. Through the use of a common-sense approach to software development, it is shown that the incorporation of individual agile techniques does not have to entail additional risk for projects having higher availability, performance, and quality requirements.

Trust Elements in Open Source

2010 ◽  
pp. 334-342
Author(s):  
Barbara Russo ◽  
Marco Scotto ◽  
Alberto Sillitti ◽  
Giancarlo Succi
Keyword(s):  
Software Development ◽  
Development Process ◽  
Automatic Measurement ◽  
Automatic Process ◽  
Software Development Process ◽  
Software Products ◽  
Development Tools ◽  
On Line ◽  
Measurement Approach

The quality of a software development process is based on a large spectrum of various elements that must be identified and assessed. The majority of elements can be measured quantitatively and possibly using an automatic process. Some elements, however, are rather subjective and depend strongly on different opinions of people using or evaluating the software development process. An automatic measurement approach is difficult to achieve (for example by on-line questionnaires or surveys inserted inside software products or software development tools). The foundation for all assessments is a set of elements that will be at a certain point of development or use measured and evaluated.

Efficient Framework for Fully Automatic Test Case Generation and Prioritization Using Genetic Algorithm in Software Testing

2020 ◽  
Vol 17 (11) ◽  
pp. 5198-5204
Author(s):  
Seema Rani ◽  
Amandeep Kaur
Keyword(s):  
Genetic Algorithm ◽  
Software Development ◽  
Software Testing ◽  
Development Process ◽  
Regression Testing ◽  
Process Time ◽  
Test Case ◽  
Test Cases ◽  
Software Development Process ◽  
Automatic Test

Automation in software testing is significantly growing in recent situation. Most part of the system is automated with help of the software. Today every modern software developers are trying to automate the software development process as much as possible. Therefore to develop any software more skills and expertise are needed. For the software development process, testing of software is the exceedingly significant and considerable phase. Automatic test data generation had an essential function in specific area regarding software testing. Test case creation is technique of gathering the data which completes the testing standards, all criteria’s and conditions. During testing process, the software goes through frequent modifications. As a result, due to all of these modifications and repetitive retesting the cost of testing process increases. This is called regression testing. Regression testing requires more expertise, more effort, more time and more cost. Here to reduce the time and expenditure, many type of techniques are proposed. The changes in one test case will affect all the others test cases. To triumph over this problem, when the changes occurred in the software every the test case have to be retested repeatedly. And this problem leads to make the testing process time consuming with unnecessary increased cost. Here In this research paper, the work’s focal point on automatic test cases generation and prioritization with improved evolutionary genetic algorithm.

The Concept of Model-View-Controler (MVC) as Solution Software Development

CCIT Journal ◽  
2010 ◽  
Vol 3 (3) ◽  
pp. 377-402
Author(s):  
Ermatita Ermatita ◽  
Huda Ubaya ◽  
Dwirosa Indah
Keyword(s):  
Software Development ◽  
Model View Controller ◽  
On Line ◽  
Line Test ◽  
Model View

Pengembangan perangkat lunak adalah tugas kompleks dan membutuhkan adaptasi untuk mengakomodasi kebutuhan pengguna. Untuk membuat konsep dan perubahan perangkat lunak, dalam pemeliharaan, sekarang telah dikembangkan lebih mudah dalam pengembangan perangkat lunak, pola model-view-controller, yang merupakan arsitektur yang dapat membantu memfasilitasi dalam pengembangan dan pemeliharaan perangkat luna. Hal ini, karena dalam arsitektur model tiga-lapis, yaitu: tampilan dan pengontrolan dalam pembangunan dilakukan secara independen, sehingga dapat memberikan dahan dalam pengembangan dan pemeliharaan. Selain itu, arsitektur ini juga dapat melihat hal-hal yang sederhana dan menarik bagi pengguna. Software sistem on-line test adalah perangkat lunak yang memerlukan interaksi dengan pengguna, dan pemeliharaan perangkat adaptif. Karena sistem ujian on-line memerlukan pengembangan perangkat lunak untuk mengakomodasi kebutuhan ini berkembang dengan cepat. Makalah ini untuk menganalisis Model-View-Controller dan mencoba pembangunan, untuk menerapkannya dalam pengembangan perangkat lunak sistem pengujian on-line. 

Sign in / Sign up

Export Citation Format

Share Document