scholarly journals ANALISIS DAN RANCANGAN PROTOTIPE MANAJEMEN DOKUMENTASI REKAYASA PERANGKAT LUNAK

Compiler ◽  
2014 ◽  
Vol 3 (1) ◽  
Author(s):  
Hanson Prihantoro Putro

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.

Author(s):  
Maulik V. Dhamecha

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.


2021 ◽  
Vol 4 (4) ◽  
pp. 338-353
Author(s):  
Oleksii B. Kungurtsev ◽  
Nataliia O. Novikova ◽  
Svitlana L. Zinovatna ◽  
Nataliia O. Komleva

It is shown that most technologies for creating information systems are based on an object-oriented approach and provide for the presentation of functional requirements in the form of use cases. However, there is no general agreement on the format of the use cases and the rules for describing script items. The work has improved the classification of items of use cases basing on the analysis of a great number of existing descriptions from different subject areas. New rules have been introduced and the existing rules have been clarified for describing use cases, which made it possible to further formalize and automate the process of describing use cases. It is also proposed to automate the process of forming a model of program classes by introducing additional information linking the class with use cases. Thus, the programming class model contains significantly more information for coding than the existing models in UML diagrams. A method for constructing a model of program classes has been developed. Methods for the automated description of use cases and the construction of a model of program classes are linked into a single process. The level of information richness of the class model also makes it possible to automate the debugging process associated with changing requirements. Since the decisions made cover most of the steps in the software module creation process, they collectively represent a new technology. The proposed model, methods and technology were implemented in the ModelEditor and UseCaseEditor software products. Approbation of the method for automating the description of use cases demonstrated a decrease in the number of errors compared to the traditional method of describing more than two times, and shortening the time  more than one and a half times. Testing the method for constructing a model of program classes showed its advantage over the existing technology: errors and time reduction  almost one and a half times. The proposed technology can be used in the development of any information systems.


1993 ◽  
Vol 22 (2) ◽  
pp. 155-172 ◽  
Author(s):  
Simon C-H Wong

Educational software developers have been criticized for the lack of software engineering methodologies and principles in their analysis and design and therefore have led to low quality products. This article introduces and demonstrates the “quick” or “rapid” prototyping software engineering paradigm which can be easily employed by causal software designers such as classroom teachers using object-oriented software production tools. Development of an educational software called “The Match-Maker,” a game for learning new words, is used as an example using HyperCard™ and its scripting language, HyperTalk™, for quick prototyping. The flexibility and suitability of the object-oriented hypermedia for quick prototyping are identified. Software engineering principles involved in various development stages are presented. Good programming styles and design principles which can be implemented at ease in the object-oriented environment are also discussed.


1996 ◽  
Vol 35 (01) ◽  
pp. 52-58 ◽  
Author(s):  
A. Mavromatis ◽  
N. Maglaveras ◽  
A. Tsikotis ◽  
G. Pangalos ◽  
V. Ambrosiadou ◽  
...  

AbstractAn object-oriented medical database management system is presented for a typical cardiologic center, facilitating epidemiological trials. Object-oriented analysis and design were used for the system design, offering advantages for the integrity and extendibility of medical information systems. The system was developed using object-oriented design and programming methodology, the C++ language and the Borland Paradox Relational Data Base Management System on an MS-Windows NT environment. Particular attention was paid to system compatibility, portability, the ease of use, and the suitable design of the patient record so as to support the decisions of medical personnel in cardiovascular centers. The system was designed to accept complex, heterogeneous, distributed data in various formats and from different kinds of examinations such as Holter, Doppler and electrocardiography.


Author(s):  
Dr. Abu Turab Alam

A useful Information System is difficult to conceive and develop. Research on technology has revealed that end-user likes or dislikes may matter towards the success or failure of information system (IS). A highly complicated system in which developers have put lots of development efforts may fail if the end-user dislikes it after its initial installation. In software engineering literature it is claimed that system rejection is mostly caused by not meeting the non-functional requirements. In this paper, a study is being done on ‘turnitin®’ as technology and its acceptance to a group of students in order to find out confirmation of result as claimed by TAM while it is a post implementation research activity for technology acceptance.


2017 ◽  
Vol 2 (11) ◽  
pp. 1-7
Author(s):  
Izay A. ◽  
Onyejegbu L. N.

Agriculture is the backbone of human sustenance in this world. With growing population, there is need for increased productivity in agriculture to be able to meet the demands. Diseases can occur on any part of a plant, but in this paper only the symptoms in the fruits of a plant is considered using segmentation algorithm and edge/ sizing detectors. We also looked at image processing using fuzzy logic controller. The system was designed using object oriented analysis and design methodology. It was implemented using MySQL for the database, and PHP programming language. This system will be of great benefit to farmers and will encourage them in investing their resources since crop diseases can be detected and eliminated early.


Sign in / Sign up

Export Citation Format

Share Document