MULTI-PERSPECTIVE SPECIFICATION, DESIGN AND IMPLEMENTATION OF SOFTWARE COMPONENTS USING ASPECTS

2000 ◽  
Vol 10 (06) ◽  
pp. 713-734 ◽  
Author(s):  
JOHN GRUNDY
Keyword(s):  
Systems Engineering ◽  
Interface Design ◽  
Software Component ◽  
Tool Support ◽  
Software Systems ◽  
Software Components ◽  
Functional Requirements ◽  
Low Level ◽  
Design And Implementation ◽  
Component Engineering

Current approaches to component-based systems engineering tend to focus on low-level software component interface design and implementation. This often leads to the development of components whose services are hard to understand and combine, make too many assumptions about other components they can be composed with and component documentation that is too low-level. Aspect-oriented component engineering is a new methodology that uses a concept of different system capabilities ("aspects") to categorise and reason about inter-component provided and required services. It supports the identification, description and reasoning about high-level component functional and non-functional requirements grouped by different systemic aspects, and the refinement of these requirements into design-level software component service implementation aspects. Aspect information is used to help implement better component interfaces and to encode knowledge of a component's capabilities for other components, developers and end users to access. We describe and illustrate the use of aspect-oriented component engineering techniques and notations to specify, design and implement software components, report on some basic tool support, and our experiences using the approach to build some complex, component-based software systems.

Design and Implementation of Manufacturing Execution System (MES) for Automobile Main Gear Reducer Assembly Line

2012 ◽  
Vol 468-471 ◽  
pp. 111-114
Author(s):  
Dao Ye Huang ◽  
Ming Zhou Liu
Keyword(s):  
Assembly Line ◽  
Manufacturing Execution System ◽  
Functional Requirements ◽  
Low Level ◽  
Design And Implementation ◽  
Field Management ◽  
Mes System ◽  
Manufacturing Execution

Because of low level of informatization in automobile main gear reducer assembly line, it is proper to put forward Manufacturing Execution system to monitor, control and manager the production assembly line. First, functional requirements and coverage of MES system is investigated. Second, function of the MES for automobile main gear reducer assembly line is described. Third, the results of implementation on the line are discussed. It is proved that the efficiency of assembly line and the field management can be improved using MES system.

scholarly journals A Multi-Objective Dragongfly Optimization for Requirement Traceability Establishment

2021 ◽  
Vol 12 (2) ◽  
pp. 2523-2532
Author(s):  
Swathine.K , Et. al.
Keyword(s):  
Software Development ◽  
Development Process ◽  
Ad Hoc ◽  
Tool Support ◽  
Software Systems ◽  
Development Effort ◽  
Software Development Process ◽  
Functional Requirements ◽  
Faster Development ◽  
Requirement Traceability

Software traceability is a crucial component of various exact software development process and it is needed for various component certification and approval process in security system. With the tremendous growth of system, traceability is considered as a recent research topic. The traceability is a software development process that is indefinable. Various manufacturers struggle in predicting the appropriate traceability degree for their needs and produce the appropriate set of traceability links. The effort, cost, and discipline have to be maintained with tracking links with the faster development of software systems that are extremely higher. Also, it produces various advantages in practical realization; as it can be either ad-hoc or not properly defined traceability process, produces poor training or lack of effectual tool support. Moreover, the traceability process has to be determined as it can diminish the development effort and to enhance the development process. Generally, traceability research is based on empirical investigations for exploring newer investigational queries or to compute newer tracing methods. Here, this work concentrates on traceability, functional requirements, link establishment. It shows a better trade-off among the prevailing approaches.

scholarly journals Reliability Estimation Model for Software Components Using CEP

2013 ◽  
pp. 287-291
Author(s):  
R. Chinnaiyan ◽  
S. Somasundaram
Keyword(s):  
Graph Theory ◽  
Software Component ◽  
Reliability Estimation ◽  
Software Systems ◽  
Software Components ◽  
Estimation Model ◽  
Graph Theoretic ◽  
In Series ◽  
Decision Structure ◽  
Overall Reliability

This paper presents a graphical complexity measure based approach with an illustration for estimating the reliability of software component. This paper also elucidates how the graph-theory concepts are applied in the field of software programming. The control graphs of several actual software components are described and the correlation between intuitive complexity and the graph-theoretic complexity are illustrated. Several properties of the graph theoretic complexity are presented which shows that the software component complexity depends only on the decision structure. A symbolic reliability model for component based software systems from the execution path of software components connected in series, parallel or mixed configuration network structure is presented with a crisp narration of the factors which influence computation of the overall reliability of component based software systems. In this paper, reliability estimation model for software components using Component Execution Paths (CEP) based on graph theory is elucidated.

scholarly journals Software Component Selection Based on Quality Criteria Using the Analytic Network Process

2014 ◽  
Vol 2014 ◽  
pp. 1-12 ◽  
Author(s):  
Shah Nazir ◽  
Sajid Anwar ◽  
Sher Afzal Khan ◽  
Sara Shahzad ◽  
Muhammad Ali ◽  
...  
Keyword(s):  
Software Development ◽  
Real Life ◽  
Quality Criteria ◽  
Analytic Network Process ◽  
Software Component ◽  
Software Systems ◽  
Software Components ◽  
Schedule Delay ◽  
Component Selection ◽  
Network Process

Component based software development (CBSD) endeavors to deliver cost-effective and quality software systems through the selection and integration of commercially available software components. CBSD emphasizes the design and development of software systems using preexisting components. Software component reusability is an indispensable part of component based software development life cycle (CBSDLC), which consumes a significant amount of organization’s resources, that is, time and effort. It is convenient in component based software system (CBSS) to select the most suitable and appropriate software components that provide all the required functionalities. Selecting the most appropriate components is crucial for the success of the entire system. However, decisions regarding software component reusability are often made in an ad hoc manner, which ultimately results in schedule delay and lowers the entire quality system. In this paper, we have discussed the analytic network process (ANP) method for software component selection. The methodology is explained and assessed using a real life case study.

Framework for Semantic Search Enabled Software Component Repository (SSESCR)

2018 ◽  
Author(s):  
Vishnu Sharma ◽  
Vijay Singh Rathore ◽  
Chandikaditya Kumawat
Keyword(s):  
Software Quality ◽  
Software Reuse ◽  
Development Time ◽  
Software Component ◽  
Semantic Search ◽  
Easy Access ◽  
Software Components ◽  
Efficient Search ◽  
Systematic Reuse ◽  
New System

Software reuse can improve software quality with the reducing cost and development time. Systematic reuse plan enhances cohesion and reduces coupling for better testability and maintainability. Software reuse approach can be adopted at the highest extent if relevant software components can be easily searched, adapted and integrated into new system. Large software industries hold their own well managed component libraries containing well tested software component with the project category based classification .Access to these repositories are very limited. Software reuse is facing so many problems and still not so popular. This is due to issues of general access, efficient search and adoption of software component. This paper propose a framework which resolves all of the above issues with providing easy access to components, efficient incremental semantics based search, repository management, versioning of components.

Research on Mechanical Product Development Based on CAD Software

2014 ◽  
Vol 484-485 ◽  
pp. 933-937
Author(s):  
Fu Na Li ◽  
Lin Wei Yang ◽  
Ying Zeng
Keyword(s):  
Programming Language ◽  
Interface Design ◽  
Development Process ◽  
Visual Basic ◽  
Common Language ◽  
Test Results ◽  
Technology Application ◽  
Development System ◽  
Design And Implementation ◽  
Software Interface

This paper introduces analysis the development process of CAD technology, application of the AutoCAD software in engineering field and teaching as well as the significance of the development of two times the. This paper analyzes in detail the development of common language, and the use of Visual BASIC development and application of software based on AutoCAD. The author elaborates the software interface design and method calls AutoCAD in VB. Finally, the design and implementation of a programming language re-development system based on AutoCAD is concerned. The test results show that the developed AutoCAD two development system has good practical value.

scholarly journals Are Multi-Language Design Smells Fault-Prone? An Empirical Study

2021 ◽  
Vol 30 (3) ◽  
pp. 1-56
Author(s):  
Mouna Abidi ◽  
Md Saidur Rahman ◽  
Moses Openja ◽  
Foutse Khomh
Keyword(s):  
Programming Languages ◽  
Language Design ◽  
Functional Requirements ◽  
Code Smells ◽  
Design And Implementation ◽  
Design Smells ◽  
The Cost ◽  
The Impact ◽  
Fault Proneness

Nowadays, modern applications are developed using components written in different programming languages and technologies. The cost benefits of reuse and the advantages of each programming language are two main incentives behind the proliferation of such systems. However, as the number of languages increases, so do the challenges related to the development and maintenance of these systems. In such situations, developers may introduce design smells (i.e., anti-patterns and code smells) which are symptoms of poor design and implementation choices. Design smells are defined as poor design and coding choices that can negatively impact the quality of a software program despite satisfying functional requirements. Studies on mono-language systems suggest that the presence of design smells may indicate a higher risk of future bugs and affects code comprehension, thus making systems harder to maintain. However, the impact of multi-language design smells on software quality such as fault-proneness is yet to be investigated. In this article, we present an approach to detect multi-language design smells in the context of JNI systems. We then investigate the prevalence of those design smells and their impacts on fault-proneness. Specifically, we detect 15 design smells in 98 releases of 9 open-source JNI projects. Our results show that the design smells are prevalent in the selected projects and persist throughout the releases of the systems. We observe that, in the analyzed systems, 33.95% of the files involving communications between Java and C/C++ contain occurrences of multi-language design smells. Some kinds of smells are more prevalent than others, e.g., Unused Parameters , Too Much Scattering , and Unused Method Declaration . Our results suggest that files with multi-language design smells can often be more associated with bugs than files without these smells, and that specific smells are more correlated to fault-proneness than others. From analyzing fault-inducing commit messages, we also extracted activities that are more likely to introduce bugs in smelly files. We believe that our findings are important for practitioners as it can help them prioritize design smells during the maintenance of multi-language systems.

Tightening the Linkage of CSE and Software Systems Engineering

2004 ◽  
Vol 48 (3) ◽  
pp. 698-702 ◽  
Author(s):  
Robert G. Eggleston ◽  
Catherine Burns ◽  
James Gualtieri ◽  
Gavan Lintern ◽  
Sterling Wiggins ◽  
...  
Keyword(s):  
Systems Engineering ◽  
Software Systems ◽  
Software Systems Engineering

CASE AND ITS CHALLENGE FOR CHANGE

1991 ◽  
Vol 01 (02) ◽  
pp. 151-163 ◽  
Author(s):  
GREG BOONE
Keyword(s):  
Systems Engineering ◽  
Software Industry ◽  
Software Systems ◽  
Work Practices ◽  
Software Developers ◽  
Productivity Improvement ◽  
Computer Aided ◽  
Difficult Challenge ◽  
Ideological Change ◽  
Productivity Gains

Although the majority of professional trade press and academic attention regarding CASE (Computer Aided Software/Systems Engineering) has focused on technology, software developers have not been deluded by overinflated productivity gains attributed to those technologies. Truly profound technologies require a concomitant change in methods, practices, and techniques. Unfortunately, the majority of the software industry has had the expectation that CASE will automate their current work without rethinking work practices. Changing work practices, particularly among highly independent-minded software developers, who prize independent creativity more than team engineering, is the most difficult challenge facing the advance of the software development profession. Equally difficult is the ideological change from a productivity improvement expectation to a quality improvement expectation. This paper examines the current rate of CASE adoption and the changes necessary to accelerate its successful adoption.

Sign in / Sign up

Export Citation Format

Share Document