oalib

Publish in OALib Journal

ISSN: 2333-9721

APC: Only $99

Submit

Any time

2020 ( 8 )

2019 ( 164 )

2018 ( 489 )

2017 ( 419 )

Custom range...

Search Results: 1 - 10 of 22695 matches for " software development "
All listed articles are free for downloading (OA Articles)
Page 1 /22695
Display every page Item
Software Reuse: Developers’ Experiences and Perceptions  [PDF]
William W. Agresti
Journal of Software Engineering and Applications (JSEA) , 2011, DOI: 10.4236/jsea.2011.41006
Abstract: Reusing programs and other artifacts has been shown to be an effective strategy for significant reduction of development costs. This article reports on a survey of 128 developers to explore their experiences and perceptions about using other people’s code: to what extent does the “not invented here” attitude exist? The survey was structured around a novel and simple “4A” model, which is introduced in this article: for an organization to obtain any benefits from reusing code, four conditions must obtain: availability, awareness, accessibility, and acceptability. The greatest impediments to reuse were shown to be awareness of reusable code and developers’ perceptions of its acceptability for use on their new projects. For 72% of developers, the complexity of the old code was cited as a reason that the code was not reused. The survey also included developers’ suggestions for ways to take greater advantage of existing code and related artifacts.
Improving Parallelism in Software Development Process  [PDF]
Thang N. Nguyen
Journal of Software Engineering and Applications (JSEA) , 2013, DOI: 10.4236/jsea.2013.69059
Abstract:

Software development process basically consists of phases, planned and executed in series: 1) feasibility study; 2) requirements; 3) design and 4) implementation, prior to production and maintenance. At the end of each phase, there may be an official management decision (go/not go) depending upon cost, time or other reasons. Within each phase or across-phases, parallelism or concurrency can be achieved if modularity and/or independence of functionality exist(s). We propose a different approach to software development process that allows an improved parallel planning and execution of development effort beyond modularity and functionality independence. The goal is to shorten development time while possibly cutting cost and maintaining the same intended quality of performance. An example development is sketched.

Towards Knowledge Management in RE Practices to Support Software Development  [PDF]
Mamoona Humayoun, Asad Masood Qazi
Journal of Software Engineering and Applications (JSEA) , 2015, DOI: 10.4236/jsea.2015.88040
Abstract: Requirement engineering in any software development is the most important phase to ensure the success or failure of software. Knowledge modeling and management are helping tools to learn the software organizations. The traditional Requirements engineering practices are based upon the interaction of stakeholders which causes iteratively changes in requirements and difficulties in communication and understanding problem domain etc. So, to resolve such issues we use knowledge based techniques to support the RE practices as well as software development process. Our technique is based on two prospective, theoretical and practical implementations. In this paper, we described the need of knowledge management in software engineering and then proposed a model based on knowledge management to support the software development process. To verify our results, we used controlled experiment approach. We have implemented our model, and verify results by using and without using proposed knowledge based RE process. Our resultant proposed model can save the overall cost and time of requirement engineering process as well as software development.
Software Architectural Design in Agile Environments  [PDF]
Mehdi Mekni, Gayathri Buddhavarapu, Sandeep Chinthapatla, Mounika Gangula
Journal of Computer and Communications (JCC) , 2018, DOI: 10.4236/jcc.2018.61018
Abstract:
In this paper, we propose a novel methodology to guide and assist practitioners supporting software architecture and design activities in agile environments. Software architecture and design is the skeleton of a system. It defines how the system has to behave in terms of different functional and non-functional requirements. Currently, a clear specification of software architectural design activities and processes in agile environments does not exist. Our methodology describes in detail the phases in the agile software design process and proposes techniques and tools to implement these phases.
Call for Implementation: A New Software Development Mode for Leveraging the Resources of Open Community  [PDF]
Weiping Li, Weijie Chu, Ying Liu
Journal of Software Engineering and Applications (JSEA) , 2009, DOI: 10.4236/jsea.2009.21005
Abstract: With the growth of the internet and open software, there are additional software developers available from the open community that can participate in the development of software application systems. Aiming to leverage these resources, a new development model, CFI (call for implementation), is proposed. The basic idea of CFI is to publish some part of a software project to the open community, whole or part, in certain phases of the software development lifecycle to call for implementation. This paper discusses the basic concept and method for a software development process in CFI mode. Two different modes of CFI with different granularities are analyzed. And one of the CFI modes, fine-granularity-CFI mode, is thoroughly discussed including the main methods and basic steps. To verify the ideas a pilot project, an online store system, is built up with the CFI development process. The online store system takes the traditional Model-View-Control architecture and some common technologies such as Struts, Hibernate, Spring are used. The result shows that this new kind of software development mode is feasible though there are many problems that are still requiring further study.
Component-Based Software Development Framework for 3rd Party Logistics Business  [PDF]
Yang-Ja Jang, Taehan Lee, Seungkil Lim
Intelligent Information Management (IIM) , 2010, DOI: 10.4236/iim.2010.23032
Abstract: This paper suggests a component-based software development framework for 3rd party logistics (3PL) business. This framework integrates two engineering methodologies in order to identify the most reusable software components that can be used in several types of 3PL business models. UML (Unified Modeling Language) is used to design lower-level software components and DEMO (Design and Engineering Methodology for Organization), one of the business engineering methodologies based on the communication theory, is used to identify core business processes for 3PL business models. By using the methodologies, we develop a 3PL management solution by applying the framework into a C2C type of 3PL business model, specifically the door-to-door (D2D) service.
Laboratory Driven, Lean-to-Adaptive Prototyping in Parallel for Web Software Project Identification and Application Development in Health Science Research  [PDF]
Zachary Dwight, Alexa Barnes
Journal of Software Engineering and Applications (JSEA) , 2012, DOI: 10.4236/jsea.2012.52010
Abstract: Clinical research laboratories, bioinformatics core facilities, and health science organizations often rely on heavy planning based software development models to propose, build, and distribute software as a consumable product. Projects in non-agile software life cycles tend to have rigid “plan-design-build” milestones, increasing the amount of time needed for software development completion. Though the classic software development approach is needed for large-scale and organizational projects, clinical research laboratories can expedite software development while maintaining quality by using lean prototyping as a condition of project advancement to a committed adaptive software development cycle. Software projects benefit from an agile methodology due to the active and changing requirements often guided by experimental data driven models. We describe a lean to adaptive method used in parallel with laboratory bench work to develop quality software quickly that meets the requirements of a fast-paced research environment and reducing time to production, providing immediate value to the end user, and limiting unnecessary development practices in favor of results.
Developing Mathematical Literacy,Based on Elemental Software and Academic Tools Development  [PDF]
Oscar H. Salinas, Angel Estrada Arteaga, Martha E. Luna, Marco A. Amado González
Creative Education (CE) , 2013, DOI: 10.4236/ce.2013.47A2023
Abstract:

This report describes the procedure to develop mathematical literacy through learning basic mathematical concepts, and applying the acquired knowledge for the development of elemental software to be used as academic tool. Basic operations with matrix were performed using open and commercial sources software. A simple and basic matrix calculator were developed integrating mathematical concepts and software development skills, and the deliverable was a calculator developed on Java platform. The procedure started from a traditional classroom explanation; worked on calculus worksheet, solving some academic problems about addition, subtracted product of two matrix, following by the use of some commercial software, and finally the development of the own academic tool. These works were developed into the frame of competency based education system.

Re-Evaluating Media Richness Theory in Software Development Settings  [PDF]
Mohammed A. Bindrees, Robert J. Pooley, Idris S. Ibrahim, Nick K. Taylor
Journal of Computer and Communications (JCC) , 2014, DOI: 10.4236/jcc.2014.214004
Abstract: Software development teams communicate differently by using a variety of communication tools. Successful communication leads to competitive software based on clear and quickly delivered re-quirements, as well as smoothness in bug reporting and explanation. Agile and Waterfall software development approaches have both addressed the importance of communication for their process. However, neither Agile nor Waterfall has guaranteed communication effectiveness during their development lifecycle. In this study we highlight the main differences between Agile and Waterfall approaches in the light of Media Richness Theory (MRT). We also identify the preferred commu-nication tools during a project’s lifecycle using both Agile and Waterfall models separately. A mixed-method approach was employed in this study incorporating quantitative and qualitative data from interviews and a multilingual web-based survey. The results are presented descriptively and statistically and a rank ordering of communication tools based on our participants’ preferences leads to a better understanding of how to select the best tool in a given situation. Thus a new updated MRT ranking model tailored for software development environment was developed, as well as, we conclude that communication tools are employed differently based on project stages and team member’s role. These differences in using communication tools could be also attributed to the type of transferable information or personal preferences.
Hermeneutical Engineering of Requirements  [PDF]
Wagner Varalda, ítalo S. Vega
Journal of Computer and Communications (JCC) , 2017, DOI: 10.4236/jcc.2017.52002
Abstract: The Software Engineering aims to develop, within the deadlines and costs established, quality software and that meets the needs of its users. To be made the definition of what the software should do (to establish its purpose), it included the execution of activity the Requirements Engineering, where the context of software to be developed is identified, examined and specified. All other activities of software development depend primarily on this activity. However, there is a problem increasingly in evidence: understand the context of software to be developed. This article aims to present a proposal to face this problem through the use of specific hermeneutical methods for the Requirements Engineering, which will help the software development team understand the original needs of the business to be attended. The basic idea is to produce a hermeneutic specification acceptable, which will be used for the extraction and the specification of the software requirements to be developed. In essence, the hermeneutics focuses on the true interpretation and understanding in contextualized of what is intended to know. The Hermeneutical Engineering of Requirements comes to be the result of the adequacy of methods hermeneutical to assist, specifically the activity of Engineering of Requirements.
Page 1 /22695
Display every page Item


Home
Copyright © 2008-2017 Open Access Library. All rights reserved.