Journal articles: 'Software Project Life Cycle'

1

Cha, Jonghyuk, and Eunice Maytorena-Sanchez. "Prioritising project management competences across the software project life cycle." International Journal of Managing Projects in Business 12, no. 4 (December 2, 2019): 961–78. http://dx.doi.org/10.1108/ijmpb-11-2017-0145.

Full text

Abstract:

Purpose The purpose of this paper is to investigate the relative importance of project management (PM) competences across the different stages of a software project life cycle to identify competence development gaps and opportunities. Design/methodology/approach A deductive and quantitative approach was adopted to address the research questions with a web-based survey for data collection. Findings After reviewing the context of competences and PM competences, the importance of the PM competences overall and for specific stages in the project life cycle was analysed. The result highlights that functional and meta-competences are perceived to be the most important competence dimensions for software project practitioners. Originality/value This study makes three contributions. First, it consolidates PM competences into a set of 20 within four competence dimensions. Second, it prioritises these competences across the software project life cycle. Third, it identifies the significance of the inter-relationship between PM competences and project life cycle to reveal PM competence development gaps and opportunities.

APA, Harvard, Vancouver, ISO, and other styles

2

Baskette, J. "Life Cycle Analysis of an Ada Project." IEEE Software 4, no. 1 (January 1987): 40–47. http://dx.doi.org/10.1109/ms.1987.229793.

Full text

APA, Harvard, Vancouver, ISO, and other styles

3

Tia, Tuti Karen. "SIMULATION MODEL FOR RATIONAL UNIFIED PROCESS (RUP) SOFTWARE DEVELOPMENT LIFE CYCLE." SISTEMASI 8, no. 1 (January 27, 2019): 176. http://dx.doi.org/10.32520/stmsi.v8i1.420.

Full text

Abstract:

In software development there are several types of methodologies that can be used, one of which is Rational Unified Process (RUP). RUP is of software development process used in various software companies. There are various types of projects in RUP software development, small scale project, large-scale projects and re-engineering projects. Each type of project has different needs, especially in the use of each role. In RUP there are several important roles that cannot be done by an individual because they have to work at the same time. Basically the purpose of the RUP is to be able to produce high quality software. This cannot be achieved if the inappropriate role is used. This study proposes the number of roles needed for software development using RUP by creating simulation models. The purpose of simulation model is to determine the appropriate role based on each type of project. The results of the simulation model are in the form of a percentage of each role needed, the project manager has the largest percentage compared to other roles, which is 70% in small-scale projects and 65% in large-scale projects.

APA, Harvard, Vancouver, ISO, and other styles

4

Kumar, Madhup, and Ekbal Rashid. "An Efficient Software Development Life cycle Model for Developing Software Project." International Journal of Education and Management Engineering 8, no. 6 (November 8, 2018): 59–68. http://dx.doi.org/10.5815/ijeme.2018.06.06.

Full text

APA, Harvard, Vancouver, ISO, and other styles

5

Altunel, Haluk. "Agile Project Management in Product Life Cycle." International Journal of Information Technology Project Management 8, no. 2 (April 2017): 50–63. http://dx.doi.org/10.4018/ijitpm.2017040104.

Full text

Abstract:

Agile project management methodologies are becoming more popular day by day. They provide flexibility and adaptability to customers and project teams in terms of planning and competition. Due to these benefits, the share of the agile managed projects has been increasing. Most of the agile projects are executed on products. On the other hand, every product has a life cycle. Just as living beings, it is born, it grows/changes, matures, loses ground and completes its life and dies. The stages that define the product life in this way were put forth in The Product Life Cycle Theory. One or generally more projects and various operational works accompany the product throughout the product life. In this study, the effects of applying agile project management principles on product's life cycle are analyzed. In order to receive effective results from the agile project that accompany the product, project is suggested to be divided into phases and these phases are proposed to be differentiated according to the stage of the product. Furthermore, Product Life-time Project concept is introduced with agile methodologies. It reserves a project and its team to a specific product during its whole life. Product Life-time Project is applied to software development and automotive industries and the results are presented and compared with the traditional approach.

APA, Harvard, Vancouver, ISO, and other styles

6

Barnard, E. M. "4.1.2 Project-driven adaptation of software life cycle model." INCOSE International Symposium 16, no. 1 (July 2006): 509–22. http://dx.doi.org/10.1002/j.2334-5837.2006.tb02761.x.

Full text

APA, Harvard, Vancouver, ISO, and other styles

7

Molu, Fatma. "Software Testing Strategy." International Journal of E-Services and Mobile Applications 6, no. 2 (April 2014): 23–36. http://dx.doi.org/10.4018/ijesma.2014040103.

Full text

Abstract:

Complex financial conversion projects with large budgets have many different challenges. For companies that want to survive in conditions of tough competition, legacy (old) systems must continue to provide the required service throughout the project life cycle and in some circumstances even after project completion partly. In this case, the term coexistence comes into prominence. During this period, testing phase takes more critical role while integration systems' complexity and risk amount increase. Determining testing approach to use is essential to make sure both transformed and legacy systems provide service synchronously. In this paper, testing practices applied in the long conversion processes are discussed. Primarily, the basic features of the critical financial systems are addressed and then the main adoption methods in the literature are summarized. Then a variety of testing methodologies are presented depending on those adoption methods. These samples based on real-life experiences of transformation project. The most extensive example of real-time online financial systems is core banking systems. This paper covers the testing life cycle process of the large scale project of core banking system transformation project of a bank in Turkey.

APA, Harvard, Vancouver, ISO, and other styles

8

Guntamukkala, Vamsidhar, H. Joseph Wen, and J. Michael Tarn. "An empirical study of selecting software development life cycle models." Human Systems Management 25, no. 4 (November 8, 2006): 265–78. http://dx.doi.org/10.3233/hsm-2006-25405.

Full text

Abstract:

This article discussed the problem that is commonly faced by project managers in selecting an appropriate software development model. A good number of models and the ongoing debate between the advocates of agile and traditional models make the selection of a right one uneasy and complicated. The purpose of this study is to propose a new alternative view in selecting development models from the perspective of degree of flexibility in different project situations. The results of a survey conducted to 74 project managers and software developers indicate that there are three naturally occurring development model groups, including heavyweight (Waterfall and V models), middleweight (Incremental and Spiral models), and lightweight (Extreme Programming and SCRUM). A canonical function is identified to help project managers select an appropriate software development model for each potential or planned project.

APA, Harvard, Vancouver, ISO, and other styles

9

Wilson, Michael, David Duce, and Dan Simpson. "Life cycles in software and knowledge engineering: a comparative review." Knowledge Engineering Review 4, no. 3 (September 1989): 189–204. http://dx.doi.org/10.1017/s0269888900005026.

Full text

Abstract:

AbstractProgress in software engineering has led to system development following models of the system life cycle. These models incorporate the use of prototyping and formal methods of program verification. They are becoming supported by integrated project support environments and permit the planning and monitoring of software development projects.In contrast, knowledge based systems (KBS) are developed using informal views of the system life cycle. Tools have been developed to support some stages of the life cycle in an undisciplined manner. The commercial use of KBS needs development projects to be planned and monitored. This requires methods and tools based on systematic life cycle models to be established for KBS.This paper reviews the current state of life cycle approaches to software engineering and KBS development projects in order to provide a direction for the development of methodical KBS life cycle models.

APA, Harvard, Vancouver, ISO, and other styles

10

Favaro, J. "Guest Editor's Introduction: Renewing the Software Project Management Life Cycle." IEEE Software 27, no. 1 (January 2010): 17–19. http://dx.doi.org/10.1109/ms.2010.9.

Full text

APA, Harvard, Vancouver, ISO, and other styles

11

Merikoski, Helena, Paula Savolainen, and Jarmo J. Ahonen. "Suppliers’ software development project start-up practices." International Journal of Managing Projects in Business 10, no. 4 (September 5, 2017): 880–96. http://dx.doi.org/10.1108/ijmpb-10-2016-0083.

Full text

Abstract:

Purpose The purpose of this paper is to present a life cycle phase of a software development project which is substantial for the success of the project. This paper visualizes the project start-up phase from suppliers’ perspective. Design/methodology/approach The method is a theory building from case studies. The data were collected from three software supplier firms by conducting process modeling separately in each firm. Findings The study resulted in a model of a supplier’s software project start-up which includes start-up practices and involved roles. The results indicate that project start-up is an integral and structured phase of project life cycle, which influences the execution of a software development project, especially from the supplier’s perspective in the project business context. Research limitations/implications The study focuses on the start-up phase of software development projects delivered to external customers. Therefore, developed project start-up model is applicable as such in software supplier firms. Practical implications The project start-up model presented in this paper indicates that project start-up is a complex and multi-dimensional activity in a supplier firm. This study suggests that if the project start-up phase is clearly defined, planned and followed in a supplier firm, it reduces confusion and miscommunication among the people involved in the project and helps to achieve the business goals of a project. Originality/value This study emphasizes that it is necessary to make a distinction between the perspectives of the customer and the supplier when studying projects in the project business context. The findings contribute the new knowledge for managing outsourced software development projects.

APA, Harvard, Vancouver, ISO, and other styles

12

Misra, Subhas C., and Virender Singh. "Conceptualizing open agile software development life cycle (OASDLC) model." International Journal of Quality & Reliability Management 32, no. 3 (March 2, 2015): 214–35. http://dx.doi.org/10.1108/ijqrm-08-2013-0127.

Full text

Abstract:

Purpose – Software development life cycle (SDLC) has always been the core methodology for any software engineer that depicts the entire development process which an organization is bound to utilize to achieve successful software. The purpose of this paper is to bring forth a conceptual model after analysing the best practices in SDLC, and extracting the best out of agile methodologies and the open source software, thereby bringing forward an optimised structure. Design/methodology/approach – The OASDLC is hypothesized specifically for “Brihaspati” project and is formulated keeping in mind the gaps and limitations posed by existing SDLC models. OASDLC is further put to test for achieving lower costs and efforts involved. The tests are further substantiated by means of hypothesis validation through execution of a survey based research. Findings – It has been observed that the present conceptual model further optimizes the efforts involved while adopting such a practice. Originality/value – This paper proposes a novel SDLC model so as to achieve a best practice for a software project. On analysing the issues involved such as tight budget and timelines, it led the authors to formulate a newer concept “Open Agile Software Development Life Cycle model” (OASDLC).

APA, Harvard, Vancouver, ISO, and other styles

13

BUNN, JULIAN, PAOLO PALAZZI, BERTRAND ROUSSEAU, and MATTHIEW SMITH. "A STEP TOWARDS LIGHT—LIFE CYCLE GLOBAL HYPERTEXT." International Journal of Modern Physics C 05, no. 05 (October 1994): 765–66. http://dx.doi.org/10.1142/s0129183194000866.

Full text

Abstract:

Life Cycle Global HyperText offers easier information access to all members of a software development project, with all documents resulting from the software life cycle being available through WWW hypertext. These documents are connected, via hypertext links, to the documents produced in other stages of the life cycle. To experiment with this concept we have developed converters that transform several kind of documents into the WWW format. Up to now we have focused on source code, but we are now concentrating on documents produced in earlier stages of the software life cycle, such as requirements specification, analysis and design.

APA, Harvard, Vancouver, ISO, and other styles

14

Vavilenkova, Anastasiia. "ANALYSIS OF FLEXIBLE METHODOLOGIES OF SOFTWARE DEVELOPMENT FOR IMPLEMENTATION IN TEAM PROJECTS." Bulletin of the National Technical University «KhPI» Series: New solutions in modern technologies, no. 1(7) (April 23, 2021): 39–46. http://dx.doi.org/10.20998/2413-4295.2021.01.06.

Full text

Abstract:

The materials of the article analyze the main models of the software life cycle, which underlie the flexible methodologies of software development to identify the features of its application during the implementation of team projects. It was found that the use of classical life cycle models, in particular, cascade, spiral, incremental, V-shaped and iterative, is not effective in implementing all modern aspects of software development based on the use of new information technologies. It was conducted the comparative analysis of the most popular flexible methodologies of software development Agile, Scrum, Kanban, RUP, DSDM, RAD on such indicators as life cycle model, number of iterations, purpose of project creation and types of projects for implementation, priorities, possibility of interaction with the customer, adaptation to change. The advantages and disadvantages of flexible software development methodologies made it possible to single out the MSF methodology, which is based on the harmonization of cascading, spiral and iterative models of the software development lifecycle and allows you to choose the Scrum template as the most successful for implementing and demonstrating work in team development projects. MSF uses an approach that involves the gradual creation of a working product with some functionality that reflects the requirements for the final product at this stage. It is proposed to use Microsoft solutions based on Visual Studio and Team Foundation Server for centralized management of team project elements, use of visual architecture modeling tools, code quality management capabilities and obtaining all project team members up-to-date information on project status. This is because the MSF model combines five following main models: team model; process model (sequence of actions required to build a team project); discipline of project management (provides comprehensive planning of all stages of the team project, budget management, resources, costs, scheduling); risk management disciplines and readiness management disciplines (assessment of team project members' knowledge for further distribution of team roles). The article demonstrates an example of creating a training team project based on the use of the Scrum flexible methodology template in Visual Studio based on Team Foundation Server.

APA, Harvard, Vancouver, ISO, and other styles

15

Et.al, Naveen N. Kulkarni. "Tailoring effective requirement's specification for ingenuity in Software Development Life Cycle." Turkish Journal of Computer and Mathematics Education (TURCOMAT) 12, no. 3 (April 11, 2021): 3338–44. http://dx.doi.org/10.17762/turcomat.v12i3.1590.

Full text

Abstract:

Software Requirements Engineering (SRE) process define software manuscripts with sustaining Software Requirement Specification (SRS) and its activities. SRE comprises many tasks requirement analysis, elicitation, documentation, conciliation and validation. Natural language is most popular and commonly used to form the SRS document. However, natural language has its own limitations wrt quality approach for SRS. The constraints include incomplete, incorrect, ambiguous, and inconsistency. In software engineering, most applications are object-oriented. So requirements are unlike problem domain need to be developed. So software documentation is completed in such a way that, all authorized users like clients, analysts, managers, and developers can understand it. These are the basis for success of any planned project. Most of the work is still dependent on intensive human (domain expert) work. consequences of the project success still depend on timeliness with tending errors. The fundamental quality intended for each activity is specified during the software development process. This paper concludes critically with best practices in writing SRS. This approach helps to mitigate SRS limitation up to some extent. An initial review highlights capable results for the proposed practices

APA, Harvard, Vancouver, ISO, and other styles

16

Penha, Renato, Wagner Solivan Ferreira, Luciano Ferreira da Da Silva, Flavio Santino Bizarrias, and Cláudia Terezinha Kniess. "The Contribution of a Model to Estimate Activities in Software Projects Based on Lessons Learned." Future Studies Research Journal: Trends and Strategies 13, no. 1 (January 1, 2021): 73–93. http://dx.doi.org/10.24023/futurejournal/2175-5825/2021.v13i1.541.

Full text

Abstract:

Purpose – The main objective of this article is to propose the use of a model developed by Matturo and Silva (2010) to capture knowledge in software projects based on the lessons learned.Design/methodology/approach – We carried out a qualitative research from a descriptive perspective through a single case study applied to an Enterprise Information Technology company. The company is a leader in market solutions to support customer experience management. For the data collection process, we used systematic literature review, document analysis and semi-structured interviews.Findings – The results supported project managers to better understand the storage and use of information from lessons learned in dimensioning the use of human resources and to support the estimation of new project activities. In addition, the results showed the organization's disregard for not giving due importance to the information and knowledge generated during the life cycle of a project.Research, Practical & Social implications – The model allows companies to obtain new knowledge or consult existing knowledge throughout the life cycle of projects and to support project managers in the process of estimating activities and preparing budgets with greater precision, using the information from lessons learned as a support. acquired in the completed projects.Originality/value – The lack of information in the initial scope of the project and in the definition of activities in the human resource allocation process hinder the duration of the project's development activities, directly resulting in inaccurate estimates. As a result, this scenario contributes to the increased risk of deviations in terms and / or costs of software projects.

APA, Harvard, Vancouver, ISO, and other styles

17

Selvaraj, Manjula Gandhi, Devi Shree Jayabal, Thenmozhi Srinivasan, and Palanisamy Balasubramanie. "Predicting Defects Using Information Intelligence Process Models in the Software Technology Project." Scientific World Journal 2015 (2015): 1–6. http://dx.doi.org/10.1155/2015/598645.

Full text

Abstract:

A key differentiator in a competitive market place is customer satisfaction. As per Gartner 2012 report, only 75%–80% of IT projects are successful. Customer satisfaction should be considered as a part of business strategy. The associated project parameters should be proactively managed and the project outcome needs to be predicted by a technical manager. There is lot of focus on the end state and on minimizing defect leakage as much as possible. Focus should be on proactively managing and shifting left in the software life cycle engineering model. Identify the problem upfront in the project cycle and do not wait for lessons to be learnt and take reactive steps. This paper gives the practical applicability of using predictive models and illustrates use of these models in a project to predict system testing defects thus helping to reduce residual defects.

APA, Harvard, Vancouver, ISO, and other styles

18

Clarke-Hagan, Daniel, Michael Curran, John Spillane, and Mary-Catherine Greene. "Whole Life/Life Cycle Costing During the Design Stage of a Construction Project." International Journal of Digital Innovation in the Built Environment 9, no. 2 (July 2020): 66–87. http://dx.doi.org/10.4018/ijdibe.2020070103.

Full text

Abstract:

The calculations of life cycle costs (LCC) and whole life costs (WLC) are important tools in the life cycle of a project. The aim of this research is to examine life cycle costing, whole life costing, and the possible advantages and disadvantages to their introduction and use. A qualitative methodology encompassing an in-depth literature review, interviews, and qualitative analysis using mind mapping software, this research is important as it can add to the industry's understanding of the design process. It highlights reasons for the success or failure of a construction project, in terms of sustainability at the design stage. Results indicate that the researched topics had many advantages but also had inherent disadvantages. It is found that the potential advantages outweighed disadvantages, but uptake within industry is still slow and that better promotion and their benefits to sustainability, the environment, society, and the industry are required.

APA, Harvard, Vancouver, ISO, and other styles

19

Vogel, David A. "Software Safety for Every Phase of Software Development." Biomedical Instrumentation & Technology 40, no. 4 (July 1, 2006): 309–14. http://dx.doi.org/10.2345/i0899-8205-40-4-309.1.

Full text

Abstract:

Abstract Where does risk management belong, at the beginning of a project or at the end? Many managers choose one or the other, or both. The correct answer is that risk management needs to be considered throughout the software development life cycle. When the risks include the safety of patients or the users of the software, the methods need to be more formal. This article will explain why, and then will provide the how and the how much.

APA, Harvard, Vancouver, ISO, and other styles

20

Rahman, Nayem. "A Simulation Model for Application Development in Data Warehouses." International Journal of Operations Research and Information Systems 9, no. 1 (January 2018): 66–80. http://dx.doi.org/10.4018/ijoris.2018010104.

Full text

Abstract:

Software development projects have been blamed for being behind schedule, cost overruns, and the delivery of poor quality product. This paper presents a simulation model of a data warehouse to evaluate the feasibility of different software development controls and measures to better manage a software development lifecycle, and improve the performance of the launched software. This paper attempts to address the practical issue of code defects in each stage of data warehouse application development. The author has compared the defect removal rate of their previous project to the newly proposed enhanced project development life cycle that uses code inspection and code scorecard along with other phases of software development life cycle. Simulation results show that the code inspection and code score-carding have achieved a significant code defect reduction. This has also significantly improved the software development process and allowed for a flawless production execution. The author proposes this simulation model to a data warehouse application development process to enable developers to improve their current process.

APA, Harvard, Vancouver, ISO, and other styles

21

Wautelet, Yves, Christophe Schinckus, and Manuel Kolp. "Towards Knowledge Evolution in Software Engineering." International Journal of Information Technologies and Systems Approach 3, no. 1 (January 2010): 21–40. http://dx.doi.org/10.4018/jitsa.2010100202.

Full text

Abstract:

This article presents an epistemological reading of knowledge evolution in software engineering (SE) both within a software project and into SE theoretical frameworks principally modeling languages and software development life cycles (SDLC). The article envisages SE as an artificial science and notably points to the use of iterative development as a more adequate framework for the enterprise applications. Iterative development has become popular in SE since it allows a more efficient knowledge acquisition process especially in user intensive applications by continuous organizational modeling and requirements acquisition, early implementation and testing, modularity,… SE is by nature a human activity: analysts, designers, developers and other project managers confront their visions of the software system they are building with users’ requirements. The study of software projects’ actors and stakeholders using Simon’s bounded rationality points to the use of an iterative development life cycle. The later, indeed, allows to better apprehend their rationality. Popper’s knowledge growth principle could at first seem suited for the analysis of the knowledge evolution in the SE field. However, this epistemology is better adapted to purely hard sciences as physics than to SE which also takes roots in human activities and by the way in social sciences. Consequently, we will nuance the vision using Lakatosian epistemology notably using his falsification principle criticism on SE as an evolving science. Finally the authors will point to adaptive rationality for a lecture of SE theorists and researchers’ rationality.

APA, Harvard, Vancouver, ISO, and other styles

22

Iatrellis, Omiros, and Panos Fitsilis. "A Review on Software Project Management Ontologies." International Journal of Information Technology Project Management 9, no. 4 (October 2018): 54–72. http://dx.doi.org/10.4018/ijitpm.2018100104.

Full text

Abstract:

This article aims to provide the reader with a comprehensive background for understanding current knowledge and research works on ontologies for software project management (SPM). It constitutes a systematic literature review behind key objectives of the potential adoption of ontologies in PM. Ontology development and engineering could facilitate substantially the software development process and improve knowledge management, software and artifacts reusability, internal consistency within project management processes of various phases of software life cycle. The authors examined the literature focusing on software project management ontologies and analyzed the findings of these published papers and categorized them accordingly. They used qualitative methods to evaluate and interpret findings of the collected studies. The literature review, among others, has highlighted lack of standardization in terminology and concepts, lack of systematic domain modeling and use of ontologies mainly in prototype ontology systems that address rather limited aspects of software project management processes.

APA, Harvard, Vancouver, ISO, and other styles

23

Vandehei, Bailey, Daniel Alencar Da Costa, and Davide Falessi. "Leveraging the Defects Life Cycle to Label Affected Versions and Defective Classes." ACM Transactions on Software Engineering and Methodology 30, no. 2 (March 2021): 1–35. http://dx.doi.org/10.1145/3433928.

Full text

Abstract:

Two recent studies explicitly recommend labeling defective classes in releases using the affected versions (AV) available in issue trackers (e.g., Jira). This practice is coined as the realistic approach . However, no study has investigated whether it is feasible to rely on AVs. For example, how available and consistent is the AV information on existing issue trackers? Additionally, no study has attempted to retrieve AVs when they are unavailable. The aim of our study is threefold: (1) to measure the proportion of defects for which the realistic method is usable, (2) to propose a method for retrieving the AVs of a defect, thus making the realistic approach usable when AVs are unavailable, (3) to compare the accuracy of the proposed method versus three SZZ implementations. The assumption of our proposed method is that defects have a stable life cycle in terms of the proportion of the number of versions affected by the defects before discovering and fixing these defects. Results related to 212 open-source projects from the Apache ecosystem, featuring a total of about 125,000 defects, reveal that the realistic method cannot be used in the majority (51%) of defects. Therefore, it is important to develop automated methods to retrieve AVs. Results related to 76 open-source projects from the Apache ecosystem, featuring a total of about 6,250,000 classes, affected by 60,000 defects, and spread over 4,000 versions and 760,000 commits, reveal that the proportion of the number of versions between defect discovery and fix is pretty stable (standard deviation <2)—across the defects of the same project. Moreover, the proposed method resulted significantly more accurate than all three SZZ implementations in (i) retrieving AVs, (ii) labeling classes as defective, and (iii) in developing defects repositories to perform feature selection. Thus, when the realistic method is unusable, the proposed method is a valid automated alternative to SZZ for retrieving the origin of a defect. Finally, given the low accuracy of SZZ, researchers should consider re-executing the studies that have used SZZ as an oracle and, in general, should prefer selecting projects with a high proportion of available and consistent AVs.

APA, Harvard, Vancouver, ISO, and other styles

24

SINGH, YOGESH, ARVINDER KAUR, PRADEEP KUMAR BHATIA, and OMPRAKASH SANGWAN. "PREDICTING SOFTWARE DEVELOPMENT EFFORT USING ARTIFICIAL NEURAL NETWORK." International Journal of Software Engineering and Knowledge Engineering 20, no. 03 (May 2010): 367–75. http://dx.doi.org/10.1142/s0218194010004761.

Full text

Abstract:

Software effort estimation is an important and integral part of software development life cycle of any project. However, cost, time and manpower estimation is required prior to implementation of the project. The objective of this work is to explore the possibilities of application of Artificial Neural Network (ANN) as a tool for predicting software development effort. We proposed an ANN model for predicting software development effort. A multilayer feed forward network is trained using back-propogation algorithm and demonstrated to be suitable. This study used the training and validation data, which is randomly selected from the data repository of 650 projects [8]. The experimental results indicate that the Mean Absolute Relative Error (MARE) is 0.261 of ANN model and shows that ANN model is a competitive model for predicting software development effort.

APA, Harvard, Vancouver, ISO, and other styles

25

de Vicente Mohino, Bermejo Higuera, Bermejo Higuera, and Sicilia Montalvo. "The Application of a New Secure Software Development Life Cycle (S-SDLC) with Agile Methodologies." Electronics 8, no. 11 (October 24, 2019): 1218. http://dx.doi.org/10.3390/electronics8111218.

Full text

Abstract:

The software development environment is focused on reaching functional products in the shortest period by making use of the least amount of resources possible. In this scenario, crucial elements such as software quality or software security are not considered at all, and in most cases, the high value offered to the projects is not taken into account. Nowadays, agile models are booming. They are defined by the way they achieve the interaction and integration of everyone involved in the software life cycle, the advantages of the quick reaction to change, and the implementation of artifacts or deliverables which display the level of progress reached at any time. In this context, it seems clearly necessary to define a new software development model, which prioritizes security aspects at any phase of the software life cycle and takes advantage of the benefits of the agile models. The proposed methodology shows that if security is considered from the beginning, vulnerabilities are easily detected and solved during the time planned for the project, with no extra time nor costs for the client and it increases the possibilities of reaching success in terms of not only functionality but also quality.

APA, Harvard, Vancouver, ISO, and other styles

26

Rierson, Leanna, and Barbara Lingberg. "Reverse Engineering of Software Life Cycle Data In Certification Projects." Journal of Aerospace Computing, Information, and Communication 3, no. 6 (June 2006): 320–26. http://dx.doi.org/10.2514/1.10280.

Full text

APA, Harvard, Vancouver, ISO, and other styles

27

Kulkarni, Prof Avadhut. "Life Cycle Cost Assessment of Autoclaved Aerated Concrete Blocks." International Journal for Research in Applied Science and Engineering Technology 9, no. VI (June 30, 2021): 3389–93. http://dx.doi.org/10.22214/ijraset.2021.35712.

Full text

Abstract:

In the Development of construction materials Sustainable use of natural resources has become a necessity in India. In this project work, an LCA study is carry out for an AAC block production for environmental assessment. In addition to the LCA, the Life Cycle Cost (LCC) analysis is also applied for economic assessment. The LCA is performed according to ISO 14040. Firstly, a cradle to gate LCA method performed for one meter cube of Autoclaved Aerated Concrete Block. The LCCA method include in the OpenLCA software which is choose to calculate impact categories i.e. abiotic depletion, global warming potential, acidification potential, eutrophication potential, Eco toxicity, ozone depletion potential and photochemical oxidation potential. The last few decades, several approaches have been developed by agencies and institutions for Bricks Life Cycle Cost Analysis (LCCA). The LCC analysis was performed by developing a price model for internal and external cost categories within the software.

APA, Harvard, Vancouver, ISO, and other styles

28

Yücalar, Fatih, Deniz Kilinc, Emin Borandag, and Akin Ozcift. "Regression Analysis Based Software Effort Estimation Method." International Journal of Software Engineering and Knowledge Engineering 26, no. 05 (June 2016): 807–26. http://dx.doi.org/10.1142/s0218194016500261.

Full text

Abstract:

Estimating the development effort of a software project in the early stages of the software life cycle is a significant task. Accurate estimates help project managers to overcome the problems regarding budget and time overruns. This paper proposes a new multiple linear regression analysis based effort estimation method, which has brought a different perspective to the software effort estimation methods and increased the success of software effort estimation processes. The proposed method is compared with standard Use Case Point (UCP) method, which is a well-known method in this area, and simple linear regression based effort estimation method developed by Nassif et al. In order to evaluate and compare the proposed method, the data of 10 software projects developed by four well-established software companies in Turkey were collected and datasets were created. When effort estimations obtained from datasets and actual efforts spent to complete the projects are compared with each other, it has been observed that the proposed method has higher effort estimation accuracy compared to the other methods.

APA, Harvard, Vancouver, ISO, and other styles

29

Liu, Ying. "Direction Based Project Developing for Building Web-Services." Applied Mechanics and Materials 268-270 (December 2012): 1684–87. http://dx.doi.org/10.4028/www.scientific.net/amm.268-270.1684.

Full text

Abstract:

Software direction have been with us in many forms within Project developing community such as logic, experiences, domain expertise, laws, project developing principles, rules, design innovative thinking, conception, experimental results, programming rules, experience, observations, skills, algorithms have played major role in software development. This paper presents a new rule known as Direction Based Project developing where the aim is to learn from well known experience and filing newly developed and successful experience as a logic based when building software systems across the life cycle.

APA, Harvard, Vancouver, ISO, and other styles

30

Kumar, Chodagam Suresh, Mikkili Dileep Kumar, Donavalli Venkata Vidya Deepthi, and Prathipati Ratna Kumar. "Fast Track Technique for Software Testing and Quality Assurance Practice in Project Development Life Cycle." International Journal Of Recent Advances in Engineering & Technology 08, no. 04 (April 30, 2020): 26–32. http://dx.doi.org/10.46564/ijraet.2020.v08i04.007.

Full text

APA, Harvard, Vancouver, ISO, and other styles

31

Melo, Glaucia, Toacy Oliveira, Paulo Alencar, and Donald Cowan. "Knowledge reuse in software projects: Retrieving software development Q&A posts based on project task similarity." PLOS ONE 15, no. 12 (December 17, 2020): e0243852. http://dx.doi.org/10.1371/journal.pone.0243852.

Full text

Abstract:

Software developers need to cope with a massive amount of knowledge throughout the typical life cycle of modern projects. This knowledge includes expertise related to the software development phases (e.g., programming, testing) using a wide variety of methods and tools, including development methodologies (e.g., waterfall, agile), software tools (e.g., Eclipse), programming languages (e.g., Java, SQL), and deployment strategies (e.g., Docker, Jenkins). However, there is no explicit integration of these various types of knowledge with software development projects so that developers can avoid having to search over and over for similar and recurrent solutions to tasks and reuse this knowledge. Specifically, Q&A sites such as Stack Overflow are used by developers to share software development knowledge through posts published in several categories, but there is no link between these posts and the tasks developers perform. In this paper, we present an approach that (i) allows developers to associate project tasks with Stack Overflow posts, and (ii) recommends which Stack Overflow posts might be reused based on task similarity. We analyze an industry dataset, which contains project tasks associated with Stack Overflow posts, looking for the similarity of project tasks that reuse a Stack Overflow post. The approach indicates that when a software developer is performing a task, and this task is similar to another task that has been associated with a post, the same post can be recommended to the developer and possibly reused. We believe that this approach can significantly advance the state of the art of software knowledge reuse by supporting novel knowledge-project associations.

APA, Harvard, Vancouver, ISO, and other styles

32

Al-Taharwa, Ismail. "Teamwork Distribution: Local vs. Global Software Engineering Project Development Teamwork." International Journal of Emerging Technologies in Learning (iJET) 15, no. 18 (September 25, 2020): 183. http://dx.doi.org/10.3991/ijet.v15i18.15489.

Full text

Abstract:

Deliverable and course project become the preferred mean to measure learner competency and attainment of intended learning outcomes in IT-fields. Proper setup and evaluation for teamwork projects remains a key challenge for e-learning systems. This study investigates the possibility to improve the early prediction of academic software engineering project failure by treating teamwork differently according to the distribution of teamwork participants. Two configurations of teamwork distribution are considered. In the first configuration, a teamwork may include international participants, but all team participants are affiliated to the same institution, namely local teamwork. In the second configuration, a teamwork may include participants from different institutions, namely global teamwork. Software engineering projects are approached from two distinct perspectives. First, obeying the best practices during the system development life cycle (SDLC), namely, process perspective. Second, characteristics of the final deliverable deployed at each milestone of the SDLC, namely product perspective. A publicly released dataset collected by a designated e-learning environment is leveraged to validate the proposed approach. Results indicate a noticeable variance among local and global distributions. These results puts evidence that the reasons behind software engineering teamwork project failures may vary depending on the distribution of the teamwork, local vs. global. Consequently, it advise to customize e-learning systems differently according to the teamwork distribution.

APA, Harvard, Vancouver, ISO, and other styles

33

AGOSTINHO, SÉRGIO, ANA MOREIRA, ANDRÉ MARQUES, JOÃO ARAÚJO, RICARDO FERREIRA, RICARDO RAMINHOS, RITA RIBEIRO, ISABEL BRITO, and PHILIPPE CHEVALLEY. "ASPECT-ORIENTED SPECIFICATION: A CASE STUDY IN SPACE DOMAIN." International Journal of Software Engineering and Knowledge Engineering 20, no. 06 (September 2010): 783–808. http://dx.doi.org/10.1142/s0218194010004943.

Full text

Abstract:

Aspect-oriented software development claims to improve several software engineering principles, such as modularization, abstraction and composition. The Aspect for the Space Domain project (ASSD) developed a metadata-driven approach for aspect-oriented requirements analysis. The main objectives of the ASSD project, funded by the European Space Agency , were to study the applicability and usefulness of aspect-orientation for the space domain (ground segment software projects in particular), focusing on the early stages of the software development life cycle. Therefore, this paper describes a rigorous representation for requirements analysis concepts, refines an approach for handling early aspects, and proposes a client/server architecture based on a metadata repository. The ASSD approach has been validated with two space domain case studies.

APA, Harvard, Vancouver, ISO, and other styles

34

Wang, Jian Jun, Yan Feng Liu, and Qian Liu. "Study on Life Cycle Environmental Impact Assessment of Ground Resource Heat Pump Project." Advanced Materials Research 838-841 (November 2013): 1967–71. http://dx.doi.org/10.4028/www.scientific.net/amr.838-841.1967.

Full text

Abstract:

With the popularization and application of Ground Source Heat Pump (GSHP) technology and the expanding scale of shallow geothermal exploitation, the environmental impact in the process of development and utilization is receiving more and more attention. According to the characteristics of ground source heat pump engineering, eBalance software is used to conduct research on life cycle environmental impact assessment. The result shows that more than 60% of resources consumption potential, acidification potential, and global warming potential derived from the process underground construction, and the eutrophication potential mainly derived from ground construction, underground construction, decommissioning with the contribution of 40.24%, 30.67% and 28.99%. According to the results, we put forward several reasonable control measures to ease the environmental impact in the process of geothermal exploitation and utilization for heat pump project.

APA, Harvard, Vancouver, ISO, and other styles

35

Collis, Betty A., and Italo De Diana. "The Impact of Different Portability Factors During the Life Cycle of an Educational Software Adaptation Project." Journal of Research on Computing in Education 23, no. 2 (December 1990): 306–17. http://dx.doi.org/10.1080/08886504.1990.10781964.

Full text

APA, Harvard, Vancouver, ISO, and other styles

36

Bychkov, Igor, Andrey Demichev, Julia Dubenskaya, Oleg Fedorov, Andreas Haungs, Andreas Heiss, Donghwa Kang, et al. "Russian–German Astroparticle Data Life Cycle Initiative." Data 3, no. 4 (November 28, 2018): 56. http://dx.doi.org/10.3390/data3040056.

Full text

Abstract:

Modern large-scale astroparticle setups measure high-energy particles, gamma rays, neutrinos, radio waves, and the recently discovered gravitational waves. Ongoing and future experiments are located worldwide. The data acquired have different formats, storage concepts, and publication policies. Such differences are a crucial point in the era of Big Data and of multi-messenger analysis in astroparticle physics. We propose an open science web platform called ASTROPARTICLE.ONLINE which enables us to publish, store, search, select, and analyze astroparticle data. In the first stage of the project, the following components of a full data life cycle concept are under development: describing, storing, and reusing astroparticle data; software to perform multi-messenger analysis using deep learning; and outreach for students, post-graduate students, and others who are interested in astroparticle physics. Here we describe the concepts of the web platform and the first obtained results, including the meta data structure for astroparticle data, data analysis by using convolution neural networks, description of the binary data, and the outreach platform for those interested in astroparticle physics. The KASCADE-Grande and TAIGA cosmic-ray experiments were chosen as pilot examples.

APA, Harvard, Vancouver, ISO, and other styles

37

Perera, Indika. "Impact of Poor Requirement Engineering in Software Outsourcing: A Study on Software Developers’ Experience." International Journal of Computers Communications & Control 6, no. 2 (June 1, 2011): 337. http://dx.doi.org/10.15837/ijccc.2011.2.2182.

Full text

Abstract:

The software Requirement Engineering (RE) is one of the most important and fundamental activities in the software life cycle. With the introduction of different software process paradigms, the Requirement Engineering appeared in different facets, yet remaining its significance without a doubt. The software development outsourcing is considered as a win-win situation for both developed and developing countries. High numbers of low paid, yet talented workforce in developing countries could be employed for software outsourcing projects with the demanding power of the outsourcer to decide the projects, their scope and priorities with the intention of profit maximization. This study was conducted to analyze the impact of poor Requirement Engineering in outsourced software projects from the developers’ context (sample size n = 57). It was identified that the present outsourcing scenario has created to have frequent requirement changes, shrunk design and stretched development phases, and frequent deliverables, which have to be accommodated by the software developer with extra effort and commitment beyond the project norms. The results reveal important issues and open policy level discussions while questioning our insights on the outsourcing benefits as a whole.

APA, Harvard, Vancouver, ISO, and other styles

38

Alsaber, Leanah, Ebtesam Al Elsheikh, Sarah Aljumah, and Nor Shahida Mohd Jamail. "Perspectives on the adherance to scrum rules in software project management." Indonesian Journal of Electrical Engineering and Computer Science 21, no. 1 (January 1, 2021): 360. http://dx.doi.org/10.11591/ijeecs.v21.i1.pp360-366.

Full text

Abstract:

Adapting users need to fulfill their requirements and delivering products to be on time within the planned cost, is critical matter that all software project managers (SPM) put the highest priority for it while considering the users satisfaction at the same time. Agile methodology is one of the solutions provided by software engineers (SE), to get the customers involved in the system development life cycle (SDLC) to avoid the risk nonconformance cost. Yet SPM’s still facing the nonconformance costs and the dynamic changes, and the root cause of the issue is not pointed on to find a solution for it. This undertaking research aimed at determining whether software developers understand scrum rules. In addition, how does this knowledge gab affect the software projects success from the project management perspective. Furthermore, the engagement studied the impact of lack of enough knowledge on the topic to project delivery. The collected data from the qualitative and quantitative methods, which was conducted with scrum teams who worked in the <span>health information system</span> (HIS), Educational solutions, and Governmental solutions has showed deviations in organizational practices and team conflicting, competition, and pressure as well as declined product quality.

APA, Harvard, Vancouver, ISO, and other styles

39

Flores, Federico, Roberto Rondanelli, Marcos Díaz, Richard Querel, Karel Mundnich, Luis Alberto Herrera, Daniel Pola, and Tomás Carricajo. "The Life Cycle of a Radiosonde." Bulletin of the American Meteorological Society 94, no. 2 (February 1, 2013): 187–98. http://dx.doi.org/10.1175/bams-d-11-00163.1.

Full text

Abstract:

The development of scientific instruments was, only a few years ago, confined to universities and electronics companies having highly specialized human and/or technical resources. With the advent of open hardware initiatives, engineers, scientists, hobbyists, and even people with limited electronic skills have been able to tinker with complex electronic systems. Taking advantage of these inexpensive and widely available tools and in the context of an engineering project class for undergraduates, the authors set about building a working radiosonde prototype from the ground up, based on an open hardware platform and easily accessible components. As a result, a fully functional radiosonde has been built that measures, records, and transmits pressure, temperature, humidity, and wind, plus a small camera that stores images on a flash card. A release system was also developed so that the radiosonde can be detached from a balloon upon reaching a certain height, pressure level, or flight time. Once it is released, one can attempt the recovery of the radiosonde with the help of a precalculated trajectory using a numerical mesoscale forecasting model and visualization software. The performance of the sonde was compared with two commercial radiosondes using climate chambers and two field launches. This paper also discusses some of the more interesting capabilities foreseeable for such a platform: 1) collaboration between meteorology and engineering departments in both education and research, and 2) development of a flexible hardware platform that allows for an effective way to compare different commercially available sensors and to easily integrate new prototype sensors.

APA, Harvard, Vancouver, ISO, and other styles

40

Knight, Richard, Mitsuru Obana, Christer von Wowern, Athanasios Mitakakis, Erhard Perz, Mohsen Assadi, Bjo¨rn F. Mo¨ller, et al. "GTPOM: Thermo-Economic Optimization of Whole Gas Turbine Plant." Journal of Engineering for Gas Turbines and Power 128, no. 3 (June 13, 2006): 535–42. http://dx.doi.org/10.1115/1.1850511.

Full text

Abstract:

Trends towards distributed power generation and the deregulation of energy markets are increasing the requirement for software tools that optimize power generation plant design and operation. In this context, this paper describes the GTPOM (thermo-economic optimization of whole gas turbine plant) European project, funded in part through the European Commission’s 5th Framework Programme, focusing on the development and demonstration of an original software tool for the thermo-economic analysis and optimization of conventional and advanced energy systems based on gas turbine plant. PSEconomy, the software tool developed during the GTPOM project, provides a thermo-economic optimization capability for advanced and more-conventional energy systems, enabling the complex trade-offs between system performance and installed costs to be determined for different operational duties and market scenarios. Furthermore, the code is capable of determining the potential benefits of innovative cycles or layout modifications to existing plants compared with current plant configurations. The economic assessment is performed through a complete through-life cycle cost analysis, which includes the total capital cost of the plant, the cost of fuel, O&M costs and the expected revenues from the sale of power and heat. The optimization process, carried out with a GA-based algorithm, is able to pursue different objective functions as specified by the User. These include system efficiency, through-life cost of electricity and through-life internal rate of return. Three case studies demonstrating the capabilities of the new tool are presented in this paper, covering a conventional combined cycle system, a biomass plant and a CO2 sequestration gas turbine cycle. The software code is now commercially available and is expected to provide significant advantages in the near and long-term development of energy cycles.

APA, Harvard, Vancouver, ISO, and other styles

41

Singh, Vikram. "A Simulation Based Approach for Software Release and Support Management." Asia Pacific Business Review 4, no. 4 (October 2008): 124–28. http://dx.doi.org/10.1177/097324700800400411.

Full text

Abstract:

Deciding when to stop testing and deliver or release a software product in the competitive market place, is an important decision in software project management. Software tools are available in the market for backing the decisions of project managers with regards to software release. Also, software development houses may need to know “for how long should they support and maintain their software product after release?” A few tools are available that take into account the software product support activities that go beyond software release while computing and optimizing software life cycle cost. A simulation based approach has been devised for helping Software Project Managers in deciding: 1) How long to test software? 2) How long to provide free support to the product? 3) When to withdraw the product support?

APA, Harvard, Vancouver, ISO, and other styles

42

Kyeremeh, Kwadwo. "Overview Of System Development Life Cycle Models." Journal of Management and Science 11, no. 1 (March 31, 2021): 12–22. http://dx.doi.org/10.26524/jms.11.3.

Full text

Abstract:

During the time half of the twentieth century, the utilization of Programmed computers has become huge. As an outcome, software programming has turned out to be increasingly differing and complex. Also, there are expanding requests on software programming – it must be less expensive, have more usefulness, be conveyed speedier, and be of higher quality than already. In the constantly changing environment and society of programming advancement, the procedures and strategies utilized when growing little projects are not adequate while developing extensive frameworks. As one response to this, distinctive improvement lifecycle models have been characterized. This paper portrays the three fundamental sorts of systems Development lifecycle models, from the successive models using incremental models to transformative models. The iterative advancement technique is additionally examined, and we additionally intricate the association of advancement lifecycle models to two rising fields in programming designing: programming design and part-based programming advancement.

APA, Harvard, Vancouver, ISO, and other styles

43

Ren, Yong Chang, De Yi Jiang, Tao Xing, and Ping Zhu. "Research on Quality Control Flows and Techniques of Software Project Management." Advanced Materials Research 328-330 (September 2011): 820–23. http://dx.doi.org/10.4028/www.scientific.net/amr.328-330.820.

Full text

Abstract:

Software project quality management is the important work throughout the entire software life cycle, the effective implementation of software product quality control is an important means of improving software quality and reducing the cost. For the difficulty of quality control, research the control flows and techniques. First, describe the quality control process including prior quality control, matter quality control and afterwards quality control. Then, research the quality control flows through graphs. Finally, by combining graphs and textual descriptions to research quality control techniques, including four commonly used techniques such as cause-effect diagram, Pareto diagram, control chart and run chart. The results show that, through the study of quality control flows and techniques provide techniques and methods to support quality control and improve the science of quality management.

APA, Harvard, Vancouver, ISO, and other styles

44

Abd Wahab, Alawiyah, and Teh Piak San. "A Systematic Literature Review on Risk Factors in Software Development Outsourcing." International Journal of Engineering & Technology 7, no. 3.20 (September 1, 2018): 76. http://dx.doi.org/10.14419/ijet.v7i3.20.18984.

Full text

Abstract:

Software development outsourcing has become a prevalent practice in the software industry. Organizations in both public and private sectors are adopting software development outsourcing in order to achieve lower cost and to access to skilled labour. However, it is widely recognized that outsourced software development projects involve risks and sometimes leads to undesirable consequences. Existing research in the software engineering and related areas have identified several risks in the software development outsourcing projects such as lack of communication and technical skills. The aim of this paper is to examine the literature on outsourced software development in order to identify some risks that could occur during the pre-contract, contract and post-contract phases of the outsourcing life cycle. It is anticipated that by understanding these risks, project managers could better manage them and subsequently increase the possibility of the success of outsourcing project. A systematic literature review of studies on software development outsourcing published in year 2005 to year 2015 was conducted. Of 41 studies consulted, 18 were concerned with outsourcing software development risk factors. The top three risk factors identified are lack of required technical skills and competencies (61%), lack of communication (44%) and poorly articulated requirements (44%).

APA, Harvard, Vancouver, ISO, and other styles

45

Halfawy, Mahmoud R. "Cloud-Based Scalable Software for Optimal Long-Range, Network-Level Bridge Improvement Programming." Transportation Research Record: Journal of the Transportation Research Board 2612, no. 1 (January 2017): 132–40. http://dx.doi.org/10.3141/2612-15.

Full text

Abstract:

The current state of the practice in bridge management highlights a growing need to develop scalable optimization software tools to support the development of truly optimal bridge improvement programs and ensure that limited financial resources are optimally allocated. The heuristic project selection approaches employed in today’s bridge management systems are not capable of generating optimal programs. Agencies that rely on suboptimal programs may inadvertently direct a significant portion of their budget to the wrong projects, leading to an increase in maintenance backlogs and overall system risk levels. The subjective project selection criteria may also hinder the ability to quantify project benefits or justify projects to funding agencies and stakeholders. This paper presents a novel dynamic programming–based multiobjective optimization approach that is capable of generating global optimal network-level, long-range bridge improvement programs. The algorithm considers three objectives: the minimization of system-level risk, the maximization of system-level condition, and the minimization of life-cycle costs, subject to agency-defined constraints and planning scenarios. The algorithm efficiently explores the enormous search space to find optimal project lists for each year in the planning horizon under any given scenario. Alternative planning scenarios are defined to quantify the impact of different investment levels on system-level performance metrics and to determine the investment required to achieve the desired performance and risk targets.

APA, Harvard, Vancouver, ISO, and other styles

46

Olson, Andrew M. "Transforming an HCI Model to a Software Design Model." International Journal of Software Engineering and Knowledge Engineering 07, no. 01 (March 1997): 145–67. http://dx.doi.org/10.1142/s0218194097000072.

Full text

Abstract:

The software engineering and human factors communities are seeking ways to integrate their methodologies. This paper outlines an amplified, software engineering methodology that extends beyond requirements gathering to encompass human factors analyses. The methodology employs an object model that is uniform throughout the software project. It involves a procedure that seamlessly transforms a task action grammar model, from HCI theory, directly into a specification model based on user/machine dialog and, thence, into a software design model. The model's object-oriented structure makes it feasible to trace the effects of the user's needs throughout the amplified project life cycle to the final code. A case study documents evidence concerning how effectively the procedure supports the software engineering process. An examination of the extent of metamorphosis the model undergoes in the case study indicates that the transition through the amplified life history is well controlled; in particular, the transition from the software specification to the design model is more controlled than that under traditional methodologies.

APA, Harvard, Vancouver, ISO, and other styles

47

Halling, H. "Realtime Software System Projects for Technical Applications — Management During the Life Cycle." IFAC Proceedings Volumes 21, no. 2 (April 1988): 1–8. http://dx.doi.org/10.1016/s1474-6670(17)53949-x.

Full text

APA, Harvard, Vancouver, ISO, and other styles

48

Bouaziz, Rahma, Fatma Krichen, and Bernard Coulette. "C-SCRIP." International Journal of Information Technology and Web Engineering 10, no. 1 (January 2015): 31–46. http://dx.doi.org/10.4018/ijitwe.2015010102.

Full text

Abstract:

Collaboration is the act of working together, towards a common goal. Collaboration is essential to the success of construction project. In software engineering projects, understanding and supporting collaboration gives the broad impact on product quality. There appears that it is difficult to effectively interact and achieve a common project goals within the bounds of cost, quality and time. The purpose of the paper is to propose a collaborative engineering process, called Collaborative SeCurity patteRn Integration Process (C-SCRIP), and a tool that supports the full life-cycle of the development of a secure system from modeling to code.

APA, Harvard, Vancouver, ISO, and other styles

49

Kumar, Dr Prakash. "Comparative Study of Different Project Size Estimation Technique for the Development of Software." International Journal of Computer Science and Mobile Computing 6, no. 12 (December 30, 2017): 157–63. http://dx.doi.org/10.47760/ijcsmc.2021.v06i12.001.

Full text

Abstract:

In SDLC (Software development life cycle model) there are various phase we use to develop the software in that the one is planning phase in this phase we use some estimation technique for estimate the Size, Cost, Effort etc for the software. The main objective of software engineering discipline is to develop the software in systematic and discipline manner as per user requirement. And also the software should deliver in time and in budget. To acquiring this feature is called planning of the software i.e. how much it take time and cost to complete and effort required form development is depend on nature of the software. The objective of this paper is to find out advantages and shortcoming of different Size estimation technique. In this paper we compared all traditional approach for size estimation technique.

APA, Harvard, Vancouver, ISO, and other styles

50

Rhmann, Wasiur, and Gufran Ahmad Ansari. "Ensemble Techniques-Based Software Fault Prediction in an Open-Source Project." International Journal of Open Source Software and Processes 11, no. 2 (April 2020): 33–48. http://dx.doi.org/10.4018/ijossp.2020040103.

Full text

Abstract:

Software engineering repositories have been attracted by researchers to mine useful information about the different quality attributes of the software. These repositories have been helpful to software professionals to efficiently allocate various resources in the life cycle of software development. Software fault prediction is a quality assurance activity. In fault prediction, software faults are predicted before actual software testing. As exhaustive software testing is impossible, the use of software fault prediction models can help the proper allocation of testing resources. Various machine learning techniques have been applied to create software fault prediction models. In this study, ensemble models are used for software fault prediction. Change metrics-based data are collected for an open-source android project from GIT repository and code-based metrics data are obtained from PROMISE data repository and datasets kc1, kc2, cm1, and pc1 are used for experimental purpose. Results showed that ensemble models performed better compared to machine learning and hybrid search-based algorithms. Bagging ensemble was found to be more effective in the prediction of faults in comparison to soft and hard voting.

APA, Harvard, Vancouver, ISO, and other styles

Journal articles on the topic 'Software Project Life Cycle'

Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles