Formal Interface-Component Based Software Analysis and Design

2010 ◽  
Author(s):  
Cui-Ye Song ◽  
Cheng-Lie Du ◽  
Gang Li
Keyword(s):  
Analysis And Design ◽  
Software Analysis ◽  
Formal Interface

scholarly journals An Efficient Comparison between Structured Analysis and Object-Oriented Analysis

2021 ◽  
pp. 290-295
Author(s):  
Maulik V. Dhamecha
Keyword(s):  
Object Oriented ◽  
Information Systems Development ◽  
Analysis And Design ◽  
Know How ◽  
Software Analysis ◽  
Develop Software ◽  
Structured Analysis ◽  
Analysis Design ◽  
Object Oriented Approach ◽  
Structured Approach

if you want to find out that which is the best suitable analysis then you have to find outs all the merits and demerits of that both analysis methods. The aspect of this paper is to describe combine both the traditional (structured) and the object-oriented approach, certain methodology for information systems development. Despite the fact that objects-oriented paradigm is actually widely adopted for software analysis, design, and implementation, there are still a large number of companies that continue to utilize the structured approach to develop software analysis and design. The empirical study that we present considers both an Uncontrolled and a controlled experiment with Master students. with the existing structured approach of developing a system there is significant way to know how appropriate the OO topics. So, in recent time, Objects-orientation analysis is largely acceptable subject. This paper discourses some basics about these two design paradigms.

scholarly journals Challenges in Developing Sequence Diagrams (UML)

2020 ◽  
Vol 5 (2) ◽  
pp. 221
Author(s):  
Tri Astoto Kurniawan ◽  
Lam-Son Lê ◽  
Bayu Priyambadha
Keyword(s):  
Software Design ◽  
Software Modeling ◽  
Sequence Diagrams ◽  
Postgraduate Students ◽  
Interaction Diagram ◽  
Analysis And Design ◽  
Software Analysis ◽  
Correct Sequence ◽  
Uml 2.0 ◽  
Novice Designers

During the object-oriented software design phase, the designers have to describe the dynamic aspect of the system under development through the most common interaction diagram variant in UML 2.0, i.e. sequence diagrams. Some novice designers, including undergraduate and postgraduate students, suffer from making inappropriate models due to insufficiently detailed guidance required to develop such sequence diagrams. This paper classifies some potential mistakes which are likely performed by such novice designers, and discusses the corresponding corrections. We summarized such mistakes based on our long experiences in teaching software modeling classes as well as software analysis and design classes. There were classified twenty-one potential mistakes with respect to the syntactical and semantical correctness of the developed models. It is concluded that novice designers have to be aware and take into account the identified mistakes in such a way they can produce correct sequence diagrams.

scholarly journals ANALISIS DAN RANCANGAN PROTOTIPE MANAJEMEN DOKUMENTASI REKAYASA PERANGKAT LUNAK

Compiler ◽  
2014 ◽  
Vol 3 (1) ◽  
Author(s):  
Hanson Prihantoro Putro
Keyword(s):  
Software Engineering ◽  
Object Oriented ◽  
Use Cases ◽  
Problem Analysis ◽  
Functional Requirements ◽  
Printing Process ◽  
Analysis And Design ◽  
Software Analysis ◽  
Software Documentation ◽  
Prototype Development

In our department, lectures found that students are difficult to create documentation, especially software documentation. Besides, software documentation is an important handbook in a software engineering. We need tools to help students or people that learn software engineering to create software documentation. This paper explains how to analyze and design a prototype for software documentation management. We propose three steps to do: problem analysis, prototype development and evaluation. First, we do the problem analysis by defining the component inputs, documentation management models and printing process. Then, the prototype is developed with object oriented software analysis and design. Finally, we create a traceability table and conduct a design testing in the evaluation step. At the result, we build analysis and design for a prototype to manage software engineering documentation with six use cases. The evaluation is conducted which well modeling the functional requirements. 26 errors are found and already refined in the documentation report. We ensure that this design is ready to implement.

PCI-PSO: Preference-Based Component Identification Using Particle Swarm Optimization

2017 ◽  
Vol 28 (5) ◽  
pp. 733-748 ◽  
Author(s):  
Seyed Mohammad Hossein Hasheminejad ◽  
Shabnam Gholamshahi
Keyword(s):  
Particle Swarm Optimization ◽  
Particle Swarm ◽  
Swarm Optimization ◽  
Analysis And Design ◽  
Independent Components ◽  
Software Analysis ◽  
Human In The Loop ◽  
Proper Number ◽  
Component Identification ◽  
Novel Method

Abstract Nowadays, component identification is one of the main challenges of software analysis and design. The component identification process aims at clustering classes into components and subcomponents. There are a number of methods to identify components in the literature; however, most of them cannot be customized to software architect’s preferences. To address this limitation, in this paper, we propose a preference-based method by the name of preference-based component identification using particle swarm optimization (PCI-PSO) to identify logical components. PCI-PSO provides a novel method to handle the software architect’s preferences using an interactive (i.e. human in the loop) search. PCI-PSO employs a customized PSO to automatically classify classes into suitable logical components and avoid the problem of identifying the proper number of components. We evaluated the effectiveness of PCI-PSO with four real-world cases. Results revealed that PCI-PSO has an ability to identify more cohesive and independent components with respect to the software architect’s preferences in comparison to the existing component identification methods.

Sign in / Sign up

Export Citation Format

Share Document