Stages Of Development Life Cycle Research Articles

Crafting a Network Plan for a Microfinancing Establishment and Its Branch Network through Virtual Private Network (VPN) Implementation

This study successfully designed a network plan incorporating a Virtual Private Network (VPN) for Kasipag Microfinancing Incorporated (KMI). Employing a developmental research design approach and following the network development life cycle stages of planning, analysis, design, and simulation, the researchers evaluated the feasibility of the network design for implementation in KMI. The findings strongly recommend KMI to proceed with the implementation of the designed network plan that includes a VPN, as it offers significant benefits and advantages. Implementing a VPN in KMI's network infrastructure will greatly enhance network security and enable secure remote access to valuable resources, which is particularly crucial in today's digital landscape emphasizing remote work and data privacy. The thorough simulation of the network plan confirms its feasibility and ensures KMI will have a reliable and efficient network infrastructure. Additionally, the implementation of the network plan will provide KMI with a competitive edge by enabling seamless communication and streamlined data transfer between branches. This will enhance collaboration, improve operational efficiency, and increase overall organizational effectiveness. The cost analysis conducted by the researchers guarantees that the project remains within budget, offering KMI a clear breakdown of expenses for informed decision-making. In conclusion, the recommended implementation of the network plan incorporating a VPN will empower KMI with improved network security, secure remote access, and a competitive advantage in the microfinancing industry. By embracing these advancements, KMI can foster growth, productivity, and success in the ever-evolving digital landscape.

Perancangan Film Animasi 3 Dimensi Berjudul “Jangan Menyerah” dengan Metode Pose to Pose

3D animation film is a development of 2D animation which is developed through computer technology which is growing rapidly. However, in using computer technology to design a 3D animated film that is still very rigid, it can affect the performance of the animation because the animation does not look real like humans and objects. The purpose of this study is to explain the design of animating an animated film using the method that has been made, namely pose to pose for each pose used based on the animation design that has been made for the film entitled "Jangan Menyerah". Method: This study uses the Multimedia Development Life Cycle (MDLC) method with six stages, namely concept, design, material collection, manufacture, testing, and finally distribution. The concept of the title of the film is not to give up on moral and short film formats. The characters used use the pose to pose method with keypose movements, extreme movements and in between movements. After that, testing and distribution is the final process in making works that are published through social networks. Conclusion Making an animated film designing a 3-dimensional animated film entitled "don't give up" using the pose to pose method, the journey of a child who wants to achieve his goals, can be achieved by following the multimedia development life cycle stage with the last process being distribution on SNS such as YouTube and Instagram

Transformation Education Process Model Development in the Organization

The education as a whole is an important human development aspect which is directed to the receipt of new knowledge, technics and skills. The transformation education as a rule is the object-oriented process but often difficult because in the education process of the group of people the same information can be accepted by each person differently. One of reasons is the experience difference. Each adult person has a personal life experience which firstly extends permanently and secondly influences on the making of different solutions in the whole life process of people as well as on the information perception during the education. Even people with the similar life experience perceive the information differently but most often the collected experience of people is different. This fact shall be taken into account by entities making the transformation training for the purpose of the effectiveness increase of this process most crucially. During the pass of development life cycle stages the entity analyzes its activity for the purpose of problem detection: after the detection of problems, development and realization of managerial solutions for their solving the whole entity activity model is changed in detail that leads to the complete change of the thinking form of all employees who shall carry out the corresponding training. The article describes approaches to the employee transformation training process model development of the entity: because of the high instability of the external environment the employee training process shall become regular; where the personnel knowledge is developed on the basis of the information studied earlier and professional competencies of employees of the level following to qualification characteristics with the certain periodicity are formed.

A Literature Review of Using Machine Learning in Software Development Life Cycle Stages

Context: The software development industry is rapidly adopting machine learning for transitioning modern day software systems towards highly intelligent and self-learning systems. However, the full potential of machine learning for improving the software engineering life cycle itself is yet to be discovered, i.e., up to what extent machine learning can help reducing the effort/complexity of software engineering and improving the quality of resulting software systems. To date, no comprehensive study exists that explores the current state-of-the-art on the adoption of machine learning across software engineering life cycle stages. Objective: This article addresses the aforementioned problem and aims to present a state-of-the-art on the growing number of uses of machine learning in software engineering. Method: We conduct a systematic mapping study on applications of machine learning to software engineering following the standard guidelines and principles of empirical software engineering. Results: This study introduces a machine learning for software engineering (MLSE) taxonomy classifying the state-of-the-art machine learning techniques according to their applicability to various software engineering life cycle stages. Overall, 227 articles were rigorously selected and analyzed as a result of this study. Conclusion: From the selected articles, we explore a variety of aspects that should be helpful to academics and practitioners alike in understanding the potential of adopting machine learning techniques during software engineering projects.

Life Cycles of Firm Disclosures

We examine the link between product life cycles and disclosure using a novel 4-stage text-based life cycle model and report two main results. First, the standard link between competition and less disclosure holds primarily in the early product development life cycle stage, when product strategies are not fully public. Second, firms with mature-stage products disclose more, consistent with lowering search costs for an outward-focused investment strategy seeking synergistic partners. These results obtain across a wide array of disclosure policies and in a quasi natural experiment. Our interpretations are further supported by tests examining not only the sender of disclosure, but also the intended receiver.

The initial process of creating a guide to evaluate the usability in Virtual Learning Environments

The usability evaluation includes a method set to analyze the system use quality in different development life cycle stages, for which there are a wide variety of evaluation methods (EM), each method uses certain ways and techniques to measure different aspects. Its choice does not only depend on which answer you are looking for but on multiple factors, the problem arises when looking for which of the existing EM are appropriate to assess the Virtual Learning Environments (VLE) usability, considering that there aren´t a combination methods or specific evaluation methods for this type of software to obtained a complete, consistent evaluation and considering factors such as effectiveness, efficiency, satisfaction, reasonable times, among others, this is why the following question arises: Which existing usability EMs are appropriate to apply on VLEs? This paper focuses on showing the initial process before the construction of the guide obtained from the EM combination that allows the usability evaluation in VLE. Process that was carried out, initially, with a bibliographic analysis about the usability EM of interactive systems existing and a comparison among them, where the first combination version was obtained, with this version, a metrics set was defined that will be applied to the VLE object of study and will allow selecting the useful methods to assess usability in this context. The result of the application of these metrics will be the combination of usability EM to form the VLE evaluation guide in upcoming research.

Architecture Evaluation of Mobile Application: Whatsapp

Software become an unavoidable in every once life. Quality of the software is an import aspect in the software development life cycle. Quality for a software is represented in terms of functional and non-functional requirement. Software architecture is used to represent the using set of components and is connectivity as a relationship between these components. To assure the development process meet the requirement given by the user, the Software Evaluation is used. Early detection of error protect the software development producing the defect software. ATAM is the one of the method used to detect the risk, non-risk, scenarios and tradeoff in the earlier stage of development life cycle. Here in this paper security scenarios for mobile application has been elicited and compared with the scenarios extracted from the whatsapp application. Comparison shows few scenarios need to added with existing scenarios in order to improve / ensure full security for the metadata.

Design of Secure and Traceable Requirement Engineering Process for Security-Sensitive Projects

With continuous evolution in software industry, security is becoming very important in software projects. However, in many development methodologies, security is thought to be added in the project at later stages of the development lifecycle. There are also many proposed methodologies where the security measures are considered at requirement engineering stage of the development lifecycle, but many of them still do not seem adequate for applicability due to the reason that these approaches do not provide sufficient support for mapping the security requirements to the later stages of development. So, we are in need of a software requirement engineering approach, which is not only helpful in security requirement specification at requirement engineering stage but also provides support for using the specified security requirements at later stages of development. To meet this requirement, we introduce a new method Secure and Traceable Requirement Engineering Process (STREP). This method also helps the non-security-expert requirement engineers to specify requirements in such a way that the specified requirements can be used to derive security related test cases. STREP method not only deals with security issues of the system at requirement engineering stage, but also makes the security requirements more traceable to be used at later stages of development lifecycle, and as a result, secure systems are produced that are also usable as the customer wishes.

Impact and Challenges of Requirement Engineering in Agile Methodologies: A Systematic Review

Requirement Engineering is one of important stage in development life cycle. All requirements required for development of product is collected in this phase. A high standard product can be developed by agile methodology in less budget and time. Importance of agile practices have been enhanced since it offers assist cooperation too software engineering. Being basic phase of software engineering, requirement engineering has different processes. The elements of direct correspondence is one of spry way which not at all like to other conventional and traditional approaches .Although a lot of research has been done on agile practices and role of requirement in agile methodologies but still there is need of studies on change manage management ,requirement prioritization, prototyping and nonfunctional requirement in agile methodologies. Aim of this review paper is to present the limitations in presentation of requirement engineering phases in agile practices and what are the issues and challenges that agile person faces in implementation of agile practices. Many research studies from different sources have been reviewed on basis of inclusion and exclusion criteria. Most RE activities has been discussed in review. Evidence helps to prove that how RE process was performed in scrums. Mostly research has been conducted on general agile methodologies, few authors specified RE practices in other methodologies of agile. Finding of this research is the work of researchers that will be beneficial for those who are interested in finding interesting area of research in this field because many techniques of agile (extreme programming, crystal methodology, lean ) requires further study and practical results as clarified by studies.

IJARCCE - Computer and Communication Engineering

The quality of any object oriented design is critical because it has a great influence on overall quality of finally delivered software product. Testability quantification early in the software development process is a criterion of crucial important to software development team. Testability has always been an indefinable concept its correct measurement, quantification or evaluation is a difficult task because of its potential factors. Testability analysis of object oriented software at an initial stage of software development process has been identified as a key factor for high quality product. A best suited object oriented design (OOD) properties and its associated metrics are helpful if applied in the early stage of development process .This paper describes an improved testability quantification framework using the identified set of potential factors, OOD properties and OOD metrics for software products at early phase, exclusively at design time. The proposed framework relates OOD properties to high level quality attributes/constructs using appropriate information to develop quality product and it may used to benchmark software products according to their key attribute. The objective of this research work to encourage researchers and developers to provide a framework to access and quantify software testability at early stage of development life cycle.

Survey on Different Machine Learning Techniques for Software Effort Estimation

Software development effort estimation is the process of predicting the effort required to develop or maintain software based on vague, incomplete or uncertain inputs. Accurate estimate of software development effort is required in the early stages of development life cycle for planning the development activities. Determination of software cost, allocation of resources, scheduling and monitoring of development activities are all dependent on the effort. Hence effort estimation is crucial for the control, quality and success of all software development projects. This paper provides an overview of the three general categories of estimation models namely; Expert Judgment based models, Algorithmic models and Non Algorithmic models. Moreover a comparison of different machine learning techniques, namely Fuzzy Logic, Artificial Neural Network, Case Based Reasoning and Fuzzy Neural Network is done in order to study which machine learning method is more suitable in which situation. Advantages and Disadvantages of these four machine learning techniques are identified as well as it was found that when applying these techniques to the COCOMO dataset the fuzzy logic and Fuzzy Neural Network showed better performance compared to other techniques. General Terms Software Effort Estimation, Project Planning.

A Review of User-Centered Design for Diabetes-Related Consumer Health Informatics Technologies

User-centered design (UCD) is well recognized as an effective human factor engineering strategy for designing ease of use in the total customer experience with products and information technology that has been applied specifically to health care information technology systems. We conducted a literature review to analyze the current research regarding the use of UCD methods and principles to support the development or evaluation of diabetes-related consumer health informatics technology (CHIT) initiatives. Findings indicate that (1) UCD activities have been applied across the technology development life cycle stages, (2) there are benefits to incorporating UCD to better inform CHIT development in this area, and (3) the degree of adoption of the UCD process is quite uneven across diabetes CHIT studies. In addition, few to no studies report on methods used across all phases of the life cycle with process detail. To address that void, the Appendix provides an illustrative case study example of UCD techniques across development stages.

Managing System of Systems Requirements with a Requirements Screening Group

AbstractFiguring out an effective and efficient way to manage not only your Requirement's Baseline, but also the development of individual requirements during a System of Systems Program's Conceptual and Developmental Life Cycle Stages can be both daunting and difficult. This is especially so when you are dealing with a complex and large System of Systems (SoS) Program with many thousands of SoS Level Requirements as well as an even larger number of System, Subsystem and Configuration Item requirements that need to be managed. This task is made even more difficult when you add in integration of the efforts of multiple requirements development teams (e.g., Integrated Product Teams (IPTs)) and numerous System/Subsystem Design Teams.One solution for tackling this difficult activity on a recent large System of Systems Program was to establish an empowered Requirements Screening Group (RSG). This group is a Team made up of co‐chairs from the Contractor, Customer, and User Stakeholders that are empowered by and accountable to the Program Manager for Requirements Development on the Program. The RSG co‐chairs, with the support of the System of System Requirements Team monitor, make decisions on, and provide guidance on all Requirements Development activities during the Conceptual and Development Life Cycle Stages of the Program. In addition, the RSG establishes and maintains the Requirements Baseline, monitors and enforces requirements traceability across the entire Program, and works with other elements of the Program to ensure integration and coordination.

1.3.2 Tailoring Systems Engineering Processes in a Conceptual Design Environment: a case study at NASA Marshall Spaceflight Center's ACO

AbstractThis paper provides an overview of Systems Engineering as it is applied in a conceptual design space systems department at the National Aeronautics and Space Administration (NASA) Marshall Spaceflight Center (MSFC) Advanced Concepts Office (ACO). Engineering work performed in the NASA MFSC's ACO is targeted toward the Exploratory Research and Concepts Development life cycle stages, as defined in the International Council on Systems Engineering (INCOSE) System Engineering Handbook.This paper addresses three ACO Systems Engineering tools that correspond to three INCOSE Technical Processes: Stakeholder Requirements Definition, Requirements Analysis, and Integration, as well as one Project Process – Risk Management. These processes are used to facilitate, streamline, and manage systems engineering processes tailored for the earliest two life cycle stages, which is the environment in which ACO engineers work.The role of systems engineers and systems engineering as performed in ACO is explored in this paper. The need for tailoring Systems Engineering processes, tools, and products in the ever‐changing engineering services ACO provides to its customers is addressed.

Educational Software Development Life Cycle Stages

Educational Software Development Life Cycle Stages

Object Oriented Design Complexity Quantification Model

This paper does meticulous research review of complexity quantification of object oriented software design and put forth some relevant information about complexity factors identification and its impact with object oriented design parameters. Complexity is a key factor to software quantification at early stage of development life cycle. A Complexity Quantification Model (CQM) is proposed and relationship from design parameters to complexity factors is defined in accordance with its anticipated influence and importance.

A Framework to Quantify Security: Complexity Perspective

 Abstract—This paper discus the detailed research review on security quantification of object oriented software and put forth an effort to characterize design time software security. An effort through complexity perspective is to identify the involved factors of complexity and its probable impact with object oriented design parameters to quantify security. Complexity is taken as a key factor to software security quantification at early stage of development life cycle. A Security Assessment through Complexity (SAC) framework is proposed and relationship from design parameters to complexity and security is defined in accordance with its anticipated influence and importance. Index Terms—Security, complexity attributes, OO design constructs, security quantification. I. INTRODUCTION A series of tragedies and chaos caused by the insecure software proves that the software security may be simply a matter of death and life at time. Security is now becoming foremost concern for software industries. Controlling and improving software design security have been an important issue in software security engineering. Security estimation of software may heavily affect security of the final product. The analysis of security parameters and their impact on security will ease up to uncover the strengths and weakness of the software and provide the basis for carrying out cost and benefit analysis (1). Generally, security problem arises because of the lack of inherent security measures. Effort in respect of early and accurate security estimation needs to be undertaken for worthwhile software development. It is apparent that fixing bugs, mitigating vulnerabilities, removing irregularities and nonconformance to standards and eliminating unwanted complexity early in the development life cycle leads to the development of secure software.

An eye on design: Effective embedded system software

Good software design is as important in the development of a product as a strong foundation in the construction of an edifice. This is particularly important in the development of an embedded system where resources like memory, power, and processing capabilities are limited. Continuous innovation, fast-changing consumer needs, and the drive to remain ahead of competitors in terms of market share and product profile has drastically reduced the time to market a product and its development life cycle. The cost of defect correction increases with the development lifecycle stage. Post-release defect fixing is the most costly. Thus, it is important to have good software design and a process in place so that stringent deadlines can be met and rework activities minimized.

An Empirical Validation of Object Oriented Design Quality Metrics

This paper describes an integrated single class based metric called Weighted Class Complexity (WCC) for object oriented design. The metric is discussed from measurement theory viewpoint, taking into account the recognized object oriented features which the metrics was intended to measure encapsulation, inheritance, coupling and polymorphism, and the quality factors efficiency, complexity, understandability, reusability and maintainability/testability. Empirical data, collected from eight different application domains, is then analyzed using WCC metric to support this theoretical validation. The result shows that the proposed metric could be used to provide an overall quality assessment of object oriented software system in early stage of development life cycle, which may be helpful to the developer to fix problems, remove irregularities and non-conformance to standards and eliminate unwanted complexities in the early development cycle. Early use of this metric may help to ensure that the analysis and design have favorable internal properties that will lead to the development of quality end product. WCC may significantly help in reducing rework during and after implementation to design effective test plans. However, further studies are needed before these results can be generalized.