Functionality Requirements for Fleet Management System

The project aims to identify the functional requirements of fleet management system with Unified Modelling Language (UML). Three main phases were involved in this project, which are defining requirements, analyze requirements and validate functionalities. The functionalities of requirement are presented by using UML diagrams that consists of use case diagram, use case specification, sequence diagram, collaboration diagram and class diagram. The prototype was built to provide a guideline in developing the running system of Fleet Management System on user’s needs

Functionality Requirements for Fleet Management System

The project aims to identify the functional requirements of fleet management system with Unified Modelling Language (UML). Three main phases were involved in this project, which are defining requirements, analyze requirements and validate functionalities. The functionalities of requirement are presented by using UML diagrams that consists of use case diagram, use case specification, sequence diagram, collaboration diagram and class diagram. The prototype was built to provide a guideline in developing the running system of Fleet Management System on user’s needs

Object-oriented modelling with unified modelling language 2.0 for simple software application based on agile methodology

Unified modelling language (UML) 2.0 introduced in 2002 has been developing and influencing object-oriented software engineering and has become a standard and reference for information system analysis and design modelling. There are many concepts and theories to model the information system or software application with UML 2.0, which can make ambiguities and inconsistencies for a novice to learn to how to model the system with UML especially with UML 2.0. This article will discuss how to model the simple software application by using some of the diagrams of UML 2.0 and not by using the whole diagrams as suggested by agile methodology. Agile methodology is considered as convenient for novices because it can deliver the information technology environment to the end-user quickly and adaptively with minimal documentation. It also has the ability to deliver best performance software application according to the customer's needs. Agile methodology will make simple model with simple documentation, simple team and simple tools.Comment: 15 pages, 30 figure

Extension to UML-B Notation and Toolset

The UML-B notation has been created as an attempt to combine the success and ease of use of UML, with the verification and rigorous development capabilities of formal methods. However, the notation currently only supports a basic diagram set. To address this we have, in this project, designed and implemented a set of extensions to the UML-B notation that provide a much fuller software engineering experience, critically making UML-B more appealing to industry partners. These extensions comprise five new diagram types, which are aimed at supplying a broader range of design capabilities, such as conceptual Use-Case design and future integration with the ProB animator tool

ConfBits: A Web Based Conference Management System

ConfBits is a Web-based Conference Management System (CMS) developed to aid effective organization and management of professional, academic and technical conferences. The web based application is an object-oriented and multi-conferences platform that is made up of four major actors which are authors, reviewers, administrators (otherwise known as Program Committee (PC) chair) and participants. Conference organizers in any Anglophone country can subscribe to the platform via the Internet to access and utilize the different features which include; abstract and full paper submissions, assignment of papers to reviewers, sending email notifications to authors and reviewers, participants management and conference program scheduling. The prototype of the platform is already deployed on the Internet and the trial Universal Resource Locator (URL) is www.cucms.com.ng. From our review of existing online CMSs, ConfBits (although still at a prototype stage) is the first of such system from a developing clime. We hope the platform will serve to bridge the hitherto wide digital divide between the developed and developing nations especially with respect to scholarly online content

STAIRS - Understanding and Developing Specifications Expressed as UML Interaction Diagrams

STAIRS is a method for the step-wise, compositional development of interactions in the setting of UML 2.x. UML 2.x interactions, such as sequence diagrams and interaction overview diagrams, are seen as intuitive ways of describing communication between different parts of a system, and between a system and its users. STAIRS addresses the challenges of harmonizing intuition and formal reasoning by providing a precise understanding of the partial nature of interactions, and of how this kind of incomplete specifications may be consistently refined into more complete specifications. For understanding individual interaction diagrams, STAIRS defines a denotational trace semantics for the main constructs of UML 2.x interactions. The semantic model takes into account the partiality of interactions, and the formal semantics of STAIRS is faithful to the informal semantics given in the UML 2.x standard. For developing UML 2.x interactions, STAIRS defines a number of refinement relations corresponding to basic system development steps. STAIRS also defines matching compliance relations, for relating interactions to real computer systems. An important feature of STAIRS is the distinction between underspecification and inherent nondeterminism. Underspecification means that there are several possible behaviours serving the same overall purpose, and that it is sufficient for a computer system to perform only one of these. On the other hand, inherent nondeterminism is used to capture alternative behaviours that must all be possible for an implementation. A typical example is the tossing of a coin, where both heads and tails should be possible outcomes. In some cases, using inherent nondeterminism may also be essential for ensuring the necessary security properties of a system

Transformation of UML Behavioral Diagrams to Support Software Model Checking

Unified Modeling Language (UML) is currently accepted as the standard for modeling (object-oriented) software, and its use is increasing in the aerospace industry. Verification and Validation of complex software developed according to UML is not trivial due to complexity of the software itself, and the several different UML models/diagrams that can be used to model behavior and structure of the software. This paper presents an approach to transform up to three different UML behavioral diagrams (sequence, behavioral state machines, and activity) into a single Transition System to support Model Checking of software developed in accordance with UML. In our approach, properties are formalized based on use case descriptions. The transformation is done for the NuSMV model checker, but we see the possibility in using other model checkers, such as SPIN. The main contribution of our work is the transformation of a non-formal language (UML) to a formal language (language of the NuSMV model checker) towards a greater adoption in practice of formal methods in software development.Comment: In Proceedings FESCA 2014, arXiv:1404.043

Development of a Secured Information System to Manage Malaria Related Cases in South Western region of Nigeria

Effective community based management of malaria incidences in most community health care centers are hampered by failure in the prompt diagnosis and treatment of malaria. This challenge is exacerbated by the emergence of multidrug resistant plasmodium parasites which makes ineffective most of the effective therapeutic drugs used in the treatment of malaria. Furthermore, even at abrupt changes in the therapeutic recommendations does not always translate to an immediate change in the effective management and control of malaria. Thus, the quest for effective diagnosis and appropriate treatment becomes a daunting and necessary task. . In this article, a secured Information system to manage malaria related cases was developed by 2-tier architecture by using the VB.NET programming language within the Microsoft Visual studio 2008 edition. The database employed for storing relevant data was the SQL server 2005 edition and fingerprint device integrated into the information system was the Microsoft fingerprint reader. From the results in this study, we modeled a feasible medical history system for prompt diagnosis, effective drug recommendations and promulgation of policies that would serve as palliatives for community health care centers that suffers shortages in material and human resources handling malaria and its related diseases