Web Application for Generating a Standard Coordinated Documentation for CS Students’ Graduation Project in Gaza Universities

The computer science (CS) graduated students suffered from documenting their projects and specially from coordinating it. In addition, students’ supervisors faced difficulties with guiding their students to an efficient process of documenting. In this paper, we will offer a suggestion as a solution to the mentioned problems; that is an application to make the process of documenting computer science (CS) student graduation project easy and time-cost efficient. This solution will decrease the possibility of human mistakes and reduce the effort of documenting process

An Investigation into the Continued Use of Unified Modeling Language (UML) in Information Systems Development

As the de facto standard for object-oriented modeling language, UML is expected to play an increasingly important role in information systems development. The long-term viability and eventual success of UML depend, to a great extent, on the continued use by UML users such as developers and analysts. Systematic investigations on UML’s continued use have been missing from contemporary discussions. Our study attempts to fill this gap in the literature. We developed a research model, which is primarily based on the Expectation Disconfirmation Theory (EDT). According to this model, UML users’ perceived discrepancy between pre-adoption expectation and post-adoption perceived performance, which is conceptualized as performance disconfirmation and effort disconfirmation, is the determinant of satisfaction. UML users’ post-adoption expectation, in terms of perceived usefulness and perceived ease of use, is the determinant of attitude. Both satisfaction and attitude are posited as determinants of users’intention to continue using UML

Integrating Lightweight Systems Analysis into the United Process by Using Service Responsibility Tables

This paper is a step toward establishing direct, but non-automatic links between lightweight (semi-formal) analysis methods for business professionals and heavyweight analysis methods for IT professionals. After noting the importance of user involvement in obtaining accurate and meaningful user requirements, the paper summarizes the Unified Process, a software development methodology that employs Unified Modeling Language (UML). Another section in the paper summarizes previous extensions of the work system method that produced a lightweight analysis tool called Service Responsibility Tables (SRTs). This paper uses a straightforward example to demonstrate a set of heuristics for translating between service responsibility tables produced by business professionals and UML diagrams that IT professionals can use as a partial basis for programming. This type of guideline-based link between lightweight and heavyweight methods could lead to more effective user involvement in requirements determination and reduce failure rate in IT projects

Uso del lenguaje unificado en la modelización de sistemas operativos

El abordaje de la enseñanza de sistemas operativos orientados a objetos choca contra un elemento de singular peso: el escaso material de estudios que apunte en forma directa al centro del problema. Es por ello que en la actualidad las diferentes cátedras abordan la enseñanza de sistemas operativos tradicionales y muy pocas complementan con sistemas operativos orientados a objetos. En los trabajos existentes la arquitectura de integración del sistema está basada en una máquina abstracta que ofrece una funcionalidad mínima, y un sistema operativo que debe extender la funcionalidad de la máquina, chocando con la funcionalidad de arranque del sistema y en la utilización de herramientas de aplicación parcial, pues las estructuras existentes se basan en conceptos tradicionales de proceso, posición de memoria y archivo. El objetivo es constatar que el modelado de un sistema operativo mediante técnicas de Lenguaje Unificado presenta inconvenientes para definir los procedimientos, que requiere un sistema operativo, en especial todo lo relacionado con la interacción de bajo nivel, siendo necesaria la creación o redefinición de herramientas que permitan la modelización de un sistema operativo general y que tenga la visión de un sistema integral orientado a objetos como parte fundante de un sistema operativo distribuido.Eje: Tecnología Informática Aplicada en EducaciónRed de Universidades con Carreras en Informática (RedUNCI

Uso del lenguaje unificado en la modelización de sistemas operativos

El abordaje de la enseñanza de sistemas operativos orientados a objetos choca contra un elemento de singular peso: el escaso material de estudios que apunte en forma directa al centro del problema. Es por ello que en la actualidad las diferentes cátedras abordan la enseñanza de sistemas operativos tradicionales y muy pocas complementan con sistemas operativos orientados a objetos. En los trabajos existentes la arquitectura de integración del sistema está basada en una máquina abstracta que ofrece una funcionalidad mínima, y un sistema operativo que debe extender la funcionalidad de la máquina, chocando con la funcionalidad de arranque del sistema y en la utilización de herramientas de aplicación parcial, pues las estructuras existentes se basan en conceptos tradicionales de proceso, posición de memoria y archivo. El objetivo es constatar que el modelado de un sistema operativo mediante técnicas de Lenguaje Unificado presenta inconvenientes para definir los procedimientos, que requiere un sistema operativo, en especial todo lo relacionado con la interacción de bajo nivel, siendo necesaria la creación o redefinición de herramientas que permitan la modelización de un sistema operativo general y que tenga la visión de un sistema integral orientado a objetos como parte fundante de un sistema operativo distribuido.Eje: Tecnología Informática Aplicada en EducaciónRed de Universidades con Carreras en Informática (RedUNCI

A Work System Front End for Object-Oriented Analysis and Design

This paper proposes that basic ideas from the work system theory (WST) and the work system method (WSM) might serve as a front end to object-oriented analysis and design (OOAD), thereby providing a path from business-oriented descriptions to formal, technical specifications. After describing the background motivation and summarizing work system concepts, the paper uses a hiring system example to show how two tools from WSM can be used as a front end for OOAD, in effect, a step before creating use case diagrams and other types of Unified Modeling Language (UML) artifacts. Potential benefits of this approach stem from a business-oriented question, how can we improve this work system\u27s performance, rather than an IT-oriented question, how can we create a technical artifact that will be used

UML in practice

UML has been described by some as “the lingua franca of software engineering”. Evidence from industry does not necessarily support such endorsements. How exactly is UML being used in industry – if it is? This paper presents a corpus of interviews with 50 professional software engineers in 50 companies and identifies 5 patterns of UML use

UNDERSTANDING THE ADOPTION OF USE CASE NARRATIVES IN THE UNIFIED MODELING LANGUAGE

This research examines the adoption of Use Case Narratives within the Unified Modeling Language (UML).Using the Technology Acceptance Model (TAM) as a framework, practitioners with UML experience were asked questions to measure their Perceived Ease of Use and Perceived Usefulness of Use Case Narratives and their Intentions to Adopt them. We extend Perceived Usefulness in the context of UML adoption to address the question “usefulness for what purpose(s)?” Generally, we find that TAM explains Use Case Narrative acceptance. More importantly, we find that Perceived Usefulness is explained by usefulness for specific software development tasks. This research provides three main contributions, beginning with an improved understanding of the role of Use Case Narratives in UML projects. Second, the study extends TAM by explaining how a technology is used rather than simply whether it is used. Third, this study provides a framework for future studies into other UML diagrams