The automation of the processing and activities of Hospital Management System (HMS) can invariably contribute greatly to the success, profitability and customer-based approach of such an organization. The use of formal specification creates a formal approach for specifying the underlying functions and properties of the system. This paper has attempted to give a formal description of the activities of a HMS system Using Zed notation. The interaction within the system is visualized using Unified Modeling
Language (UML) sequence diagrams
MANAGING AND ANALYSING SOFTWARE PRODUCT LINE REQUIREMENTSijseajournal
Modelling software product line (SPL) features plays a crucial role to a successful development of SPL.
Feature diagram is one of the widely used notations to model SPL variants. However, there is a lack of
precisely defined formal notations for representing and verifying such models. This paper presents an
approach that we adopt to model SPL variants by using UML and subsequently verify them by using firstorder
logic. UML provides an overall modelling view of the system. First-order logic provides a precise
and rigorous interpretation of the feature diagrams. We model variants and their dependencies by using
propositional connectives and build logical expressions. These expressions are then validated by the Alloy
verification tool. The analysis and verification process is illustrated by using Computer Aided Dispatch
(CAD) system.
A novel methodology for test scenario generation based on control flow analys...eSAT Publishing House
This document presents a novel methodology for generating test scenarios from UML 2.x sequence diagrams. It proposes constructing an intermediate control flow graph called a Sequence Control Flow Graph (SCFG) by analyzing the control flow in UML sequence diagrams. It also proposes a test scenario generation algorithm called STSGA that systematically generates test scenarios from the SCFG to test software in the early design phase and help testers later in the development cycle. The approach aims to address the challenges of fragments like alt, loop, break, par, and opt in UML sequence diagrams.
This document proposes a model-driven architecture approach to transforming UML state diagrams into a platform-independent model (PIM) using extended automata. The approach defines a Parallel Hierarchical Statechart Automaton (PHSA) that can represent state diagrams in a way that separates platform-independent and platform-specific aspects. The PHSA model decomposes state diagrams into components including a Moore automaton to represent states and transitions, a memory to store variables, a calculator to evaluate guards and actions, and input/output. This representation facilitates further transformations from the PIM to specific platform models.
SE_Lec 05_System Modelling and Context ModelAmr E. Mohamed
System modeling is the process of developing abstract models of a system using graphical notations like the Unified Modeling Language (UML) to represent different views of a system. Models help analysts understand system functionality and communicate with customers. Models of existing and new systems are used during requirements engineering to clarify current systems, discuss strengths/weaknesses, and explain proposed requirements.
System Models in Software Engineering SE7koolkampus
The document discusses various types of system models used in requirements engineering including context models, behavioral models, data models, object models, and how CASE workbenches support system modeling. It describes behavioral models like data flow diagrams and state machine models, data models like entity-relationship diagrams, and object models using the Unified Modeling Language. CASE tools can support modeling through features like diagram editors, repositories, and code generation.
This document discusses the role of use cases in requirements and analysis modeling. It distinguishes between black box and white box views of a system in the requirements and analysis phases. Black box views include the use case model, system interaction diagrams, system context class models, statecharts for state-dependent use cases, and test models. White box views address the internal workings of a system. The document describes how each black box view relates to use cases and requirements modeling.
The document discusses various techniques for modeling software requirements including:
1) Entity-relationship diagrams (ERDs) which model data objects and their relationships to understand the data domain.
2) Use case modeling which describes scenarios of how external actors will use the system through use cases and diagrams.
3) Flow-oriented modeling using data flow diagrams (DFDs) which represent how data objects are transformed as they move through the system.
Object Oriented Design in Software Engineering SE12koolkampus
The document discusses object-oriented design (OOD) and describes its key characteristics and processes. Specifically, it covers:
1) Objects communicate by message passing and are self-contained entities that encapsulate state and behavior.
2) The OOD process involves identifying objects and classes, defining their interfaces, relationships, and developing models of the system.
3) The Unified Modeling Language (UML) is used to describe OOD models including classes, objects, associations, and other relationships.
MANAGING AND ANALYSING SOFTWARE PRODUCT LINE REQUIREMENTSijseajournal
Modelling software product line (SPL) features plays a crucial role to a successful development of SPL.
Feature diagram is one of the widely used notations to model SPL variants. However, there is a lack of
precisely defined formal notations for representing and verifying such models. This paper presents an
approach that we adopt to model SPL variants by using UML and subsequently verify them by using firstorder
logic. UML provides an overall modelling view of the system. First-order logic provides a precise
and rigorous interpretation of the feature diagrams. We model variants and their dependencies by using
propositional connectives and build logical expressions. These expressions are then validated by the Alloy
verification tool. The analysis and verification process is illustrated by using Computer Aided Dispatch
(CAD) system.
A novel methodology for test scenario generation based on control flow analys...eSAT Publishing House
This document presents a novel methodology for generating test scenarios from UML 2.x sequence diagrams. It proposes constructing an intermediate control flow graph called a Sequence Control Flow Graph (SCFG) by analyzing the control flow in UML sequence diagrams. It also proposes a test scenario generation algorithm called STSGA that systematically generates test scenarios from the SCFG to test software in the early design phase and help testers later in the development cycle. The approach aims to address the challenges of fragments like alt, loop, break, par, and opt in UML sequence diagrams.
This document proposes a model-driven architecture approach to transforming UML state diagrams into a platform-independent model (PIM) using extended automata. The approach defines a Parallel Hierarchical Statechart Automaton (PHSA) that can represent state diagrams in a way that separates platform-independent and platform-specific aspects. The PHSA model decomposes state diagrams into components including a Moore automaton to represent states and transitions, a memory to store variables, a calculator to evaluate guards and actions, and input/output. This representation facilitates further transformations from the PIM to specific platform models.
SE_Lec 05_System Modelling and Context ModelAmr E. Mohamed
System modeling is the process of developing abstract models of a system using graphical notations like the Unified Modeling Language (UML) to represent different views of a system. Models help analysts understand system functionality and communicate with customers. Models of existing and new systems are used during requirements engineering to clarify current systems, discuss strengths/weaknesses, and explain proposed requirements.
System Models in Software Engineering SE7koolkampus
The document discusses various types of system models used in requirements engineering including context models, behavioral models, data models, object models, and how CASE workbenches support system modeling. It describes behavioral models like data flow diagrams and state machine models, data models like entity-relationship diagrams, and object models using the Unified Modeling Language. CASE tools can support modeling through features like diagram editors, repositories, and code generation.
This document discusses the role of use cases in requirements and analysis modeling. It distinguishes between black box and white box views of a system in the requirements and analysis phases. Black box views include the use case model, system interaction diagrams, system context class models, statecharts for state-dependent use cases, and test models. White box views address the internal workings of a system. The document describes how each black box view relates to use cases and requirements modeling.
The document discusses various techniques for modeling software requirements including:
1) Entity-relationship diagrams (ERDs) which model data objects and their relationships to understand the data domain.
2) Use case modeling which describes scenarios of how external actors will use the system through use cases and diagrams.
3) Flow-oriented modeling using data flow diagrams (DFDs) which represent how data objects are transformed as they move through the system.
Object Oriented Design in Software Engineering SE12koolkampus
The document discusses object-oriented design (OOD) and describes its key characteristics and processes. Specifically, it covers:
1) Objects communicate by message passing and are self-contained entities that encapsulate state and behavior.
2) The OOD process involves identifying objects and classes, defining their interfaces, relationships, and developing models of the system.
3) The Unified Modeling Language (UML) is used to describe OOD models including classes, objects, associations, and other relationships.
This document provides an introduction to using the Unified Modeling Language (UML) for object-oriented design and modeling. It describes UML as a standard language for visualizing, specifying, and documenting software designs using concepts from data, business, object, and component modeling. The document outlines the history and creators of UML, the different types of UML diagrams for modeling various aspects of systems, and internet resources for further information on UML.
Generation and Optimization of Test cases for Object-Oriented Software Using ...cscpconf
This document proposes an optimization approach to automatically generate test cases for object-oriented software using state chart diagrams. It presents a methodology to:
1) Derive a state transition graph from a state chart diagram.
2) Extract information like states, transitions, and events from the state chart diagram.
3) Generate test cases that satisfy transition path coverage, path coverage, and action coverage criteria.
4) Minimize the set of test cases by calculating node coverage and removing redundant test cases.
The methodology is demonstrated through a case study on an Automatic Ticket Machine system.
Minimal Testcase Generation for Object-Oriented Software with State Chartsijseajournal
Today statecharts are a de facto standard in industry for modeling system behavior. Test data generation is
one of the key issues in software testing. This paper proposes an reduction approach to test data generation
for the state-based software testing. In this paper, first state transition graph is derived from state chart
diagram. Then, all the required information are extracted from the state chart diagram. Then, test cases
are generated. Lastly, a set of test cases are minimized by calculating the node coverage for each test case.
It is also determined that which test cases are covered by other test cases. The advantage of our test
generation technique is that it optimizes test coverage by minimizing time and cost. The present test data
generation scheme generates test cases which satisfy transition path coverage criteria, path coverage
criteria and action coverage criteria. A case study on Railway Ticket Vending Machine (RTVM) has been
presented to illustrate our approach.
This document discusses model versioning and model repositories in the context of living models. It proposes maintaining mapping information between different model types using a mapping function. It also discusses performing system analysis based on difference reports between model versions and cross-link mapping information. The modeling environment involves different model types and modeling tools. The document presents an overview of related work on model versioning and the architecture of a tool that can parse models, generate difference reports, and analyze systems based on mapping data.
The document discusses various Unified Modeling Language (UML) diagrams used to model different aspects of software systems. It describes structure diagrams like class diagrams that show system composition and deployment diagrams that map software to hardware. It also covers behavioral diagrams like use case diagrams, interaction diagrams (sequence and communication diagrams), state-chart diagrams, and activity diagrams that model dynamic system behavior through object interactions and state transitions. Specific examples are provided for how to construct and interpret sequence diagrams, state machine diagrams, and activity diagrams.
The document discusses using UML (Unified Modeling Language) diagrams to aid in database design specification. It provides an overview of UML, describes common UML diagrams like use case diagrams, class diagrams, sequence diagrams, and state diagrams. An example of modeling a hotel reservation system is also presented to demonstrate how to implement UML diagrams.
MC0083 – Object Oriented Analysis &. Design using UML - Master of Computer Sc...Aravind NC
The document discusses several object-oriented concepts and methodologies. It defines objects as instances of classes that can perform related activities. Encapsulation is achieved through classes that expose public methods while hiding internal details. Polymorphism allows the same operations to be performed on different types of objects. It also explains the Object Modeling Technique (OMT) methodology, including its object model, dynamic model, and functional model. The Booch methodology is also briefly described.
The document provides guidance on developing use case models for a system. It defines key concepts like actors, use cases, include and extend relationships. It explains that use cases describe interactions between actors and the system to achieve goals. The document also provides examples of use case diagrams and descriptions to illustrate how to identify actors and use cases, and describe typical and alternative flows and exceptions. It emphasizes that use cases specify expected behavior from the user's perspective without detailing implementation.
The document discusses functional modeling using activity diagrams and use cases. It provides guidelines for creating activity diagrams and use cases, including identifying activities, control flows, decisions, and parallel processes for activity diagrams. It also discusses writing use case descriptions in SVDPI form from an observer perspective and creating use case diagrams by connecting actors to use cases. The overall purpose is to understand and create functional models to document requirements and describe business processes.
This document discusses using hidden Markov models to automatically discover the structure of clinical forms and annotate them with medical terminology. It presents a two-layer hidden Markov model approach to first assign tags like category and field to form elements, and then group related elements to identify form segments. The method was tested on 52 clinical forms and achieved over 95% accuracy in extracting the underlying structure of the forms in the form of trees. The ability to automatically understand form structure and annotate forms could enable more flexible design of electronic health records.
1. UML is a standardized modeling language used to visualize, specify, construct, and document a system.
2. UML includes structural elements like classes, interfaces, components as well as behavioral elements like use cases, interactions, state machines.
3. UML diagrams like class, sequence, activity diagrams are used to represent different views of a system based on its design, implementation, processes, and deployment.
Interaction modeling describes how objects in a system interact and communicate through message passing. It uses several UML diagrams including use case diagrams, sequence diagrams, activity diagrams, and collaboration diagrams. A use case diagram shows relationships between actors and use cases, while a sequence diagram depicts the temporal order of messages exchanged between objects to complete a scenario. An activity diagram models system workflows and dependencies between activities. A collaboration diagram displays message flows between objects to achieve a particular task.
Application Of UML In Real-Time Embedded Systemsijseajournal
The UML was designed as a graphical notation for use with object-oriented systems and applications.
Because of its popularity, now it is emerging in the field of embedded systems design as a modeling
language. The UML notation is useful in capturing the requirements, documenting the structure,
decomposing into objects and defining relationships between objects. It is a notational language that is
very useful in modelling the real-time embedded systems. This paper presents the requirements and
analysis modelling of a real-time embedded system related to a control system application for platform
stabilization using COMET method of design with UML notation. These applications involve designing of
electromechanical systems that are controlled by multi-processors.
SE18_Lec 06_Object Oriented Analysis and DesignAmr E. Mohamed
The document discusses key concepts in object-oriented systems development including classes, objects, attributes, methods, encapsulation, inheritance, polymorphism, relationships between classes such as associations and aggregations, and object persistence. Object-oriented development models real-world entities as classes of objects that encapsulate both data and behavior and can be organized into inheritance hierarchies.
System model.Chapter One(GEOFFREY GORDON)Towfiq218
This document provides an overview of system modeling concepts. It defines what a system is and basic system components like entities, attributes, and activities. It discusses different types of systems like open vs closed systems, stochastic vs deterministic activities, and continuous vs discrete systems. It also covers various types of models like physical, mathematical, static, and dynamic models. Specific examples are provided to illustrate concepts like static and dynamic physical and mathematical models. Principles of modeling like block-building, relevance, accuracy, and aggregation are also covered.
The document discusses various behavioral diagrams in UML including use case diagrams, sequence diagrams, collaboration diagrams, state machine diagrams and activity diagrams. It provides details on how to model scenarios and interactions using these diagrams, including modeling conditional paths, asynchronous messages, procedural vs flat sequencing, and how interaction diagrams relate to use cases at different levels of abstraction.
Module 3 Object Oriented Data Models Object Oriented notationsTaher Barodawala
The document discusses several object-oriented modeling methodologies including Coad-Yourdon, Shlaer-Mellor, OMT notation, UML notation, and Booch notation. It describes the key concepts, diagrams, and analysis steps of each methodology. The main point is that the choice of methodology is not as important as ensuring the final outcome meets requirements.
This document is a record notebook for a computer science student documenting the experiments completed in a CASE tools laboratory course. It contains details of 15 software systems developed during the course like passport automation, book banking, stock maintenance, etc. It also includes studies of UML diagrams like use case diagrams, sequence diagrams, class diagrams, etc. and how to connect a Visual Basic form to a Microsoft Access database.
IRJET- Facial Gesture Recognition using Surface EMG and Multiclass Support Ve...IRJET Journal
This document presents a study on facial gesture recognition using surface electromyography (EMG) signals and a multiclass support vector machine (SVM) classifier. EMG signals were collected from facial muscles for four expressions: frowning, puckering, smiling, and chewing. Time-domain features like root mean square, variance, and standard deviation were extracted from the EMG signals. These features were classified using SVM and k-nearest neighbors algorithms. SVM achieved the highest accuracy of 92.76% for recognizing the four facial expressions based on the EMG signals. The results indicate this EMG-based approach can efficiently predict different facial expressions.
FORMALIZATION OF A HOSPITAL MANAGEMENT SYSTEMijcseit
The automation of the processing and activities of Hospital Management System (HMS) can invariably
contribute greatly to the success, profitability and customer-based approach of such an organization. The
use of formal specification creates a formal approach for specifying the underlying functions and
properties of the system. This paper has attempted to give a formal description of the activities of a HMS
system Using Zed notation. The interaction within the system is visualized using Unified Modeling
Language (UML) sequence diagrams.
FORMALIZATION & DATA ABSTRACTION DURING USE CASE MODELING IN OBJECT ORIENTED ...cscpconf
In object oriented analysis and design, use cases represent the things of value that the system performs for its actors in UML and unified process. Use cases are not functions or features.
They allow us to get behavioral abstraction of the system to be. The purpose of the behavioral abstraction is to get to the heart of what a system must do, we must first focus on who (or what)
will use it, or be used by it. After we do this, we look at what the system must do for those users in order to do something useful. That is what exactly we expect from the use cases as the
behavioral abstraction. Apart from this fact use cases are the poor candidates for the data abstraction. Rather the do not have data abstraction. The main reason is it shows or describes
the sequence of events or actions performed by the actor or use case, it does not take data in to account. As we know in earlier stages of the development we believe in ‘what’ rather than
‘how’. ‘What’ does not need to include data whereas ‘how’ depicts the data. As use case moves around ‘what’ only we are not able to extract the data. So in order to incorporate data in use cases one must feel the need of data at the initial stages of the development. We have developed the technique to integrate data in to the uses cases. This paper is regarding our investigations to take care of data during early stages of the software development. The collected abstraction of data helps in the analysis and then assist in forming the attributes of the candidate classes. This makes sure that we will not miss any attribute that is required in the abstracted behavior using use cases. Formalization adds to the accuracy of the data abstraction. We have investigated object constraint language to perform better data abstraction during analysis & design in unified paradigm. In this paper we have presented our research regarding early stage data abstraction and its formalization.
This document provides an introduction to using the Unified Modeling Language (UML) for object-oriented design and modeling. It describes UML as a standard language for visualizing, specifying, and documenting software designs using concepts from data, business, object, and component modeling. The document outlines the history and creators of UML, the different types of UML diagrams for modeling various aspects of systems, and internet resources for further information on UML.
Generation and Optimization of Test cases for Object-Oriented Software Using ...cscpconf
This document proposes an optimization approach to automatically generate test cases for object-oriented software using state chart diagrams. It presents a methodology to:
1) Derive a state transition graph from a state chart diagram.
2) Extract information like states, transitions, and events from the state chart diagram.
3) Generate test cases that satisfy transition path coverage, path coverage, and action coverage criteria.
4) Minimize the set of test cases by calculating node coverage and removing redundant test cases.
The methodology is demonstrated through a case study on an Automatic Ticket Machine system.
Minimal Testcase Generation for Object-Oriented Software with State Chartsijseajournal
Today statecharts are a de facto standard in industry for modeling system behavior. Test data generation is
one of the key issues in software testing. This paper proposes an reduction approach to test data generation
for the state-based software testing. In this paper, first state transition graph is derived from state chart
diagram. Then, all the required information are extracted from the state chart diagram. Then, test cases
are generated. Lastly, a set of test cases are minimized by calculating the node coverage for each test case.
It is also determined that which test cases are covered by other test cases. The advantage of our test
generation technique is that it optimizes test coverage by minimizing time and cost. The present test data
generation scheme generates test cases which satisfy transition path coverage criteria, path coverage
criteria and action coverage criteria. A case study on Railway Ticket Vending Machine (RTVM) has been
presented to illustrate our approach.
This document discusses model versioning and model repositories in the context of living models. It proposes maintaining mapping information between different model types using a mapping function. It also discusses performing system analysis based on difference reports between model versions and cross-link mapping information. The modeling environment involves different model types and modeling tools. The document presents an overview of related work on model versioning and the architecture of a tool that can parse models, generate difference reports, and analyze systems based on mapping data.
The document discusses various Unified Modeling Language (UML) diagrams used to model different aspects of software systems. It describes structure diagrams like class diagrams that show system composition and deployment diagrams that map software to hardware. It also covers behavioral diagrams like use case diagrams, interaction diagrams (sequence and communication diagrams), state-chart diagrams, and activity diagrams that model dynamic system behavior through object interactions and state transitions. Specific examples are provided for how to construct and interpret sequence diagrams, state machine diagrams, and activity diagrams.
The document discusses using UML (Unified Modeling Language) diagrams to aid in database design specification. It provides an overview of UML, describes common UML diagrams like use case diagrams, class diagrams, sequence diagrams, and state diagrams. An example of modeling a hotel reservation system is also presented to demonstrate how to implement UML diagrams.
MC0083 – Object Oriented Analysis &. Design using UML - Master of Computer Sc...Aravind NC
The document discusses several object-oriented concepts and methodologies. It defines objects as instances of classes that can perform related activities. Encapsulation is achieved through classes that expose public methods while hiding internal details. Polymorphism allows the same operations to be performed on different types of objects. It also explains the Object Modeling Technique (OMT) methodology, including its object model, dynamic model, and functional model. The Booch methodology is also briefly described.
The document provides guidance on developing use case models for a system. It defines key concepts like actors, use cases, include and extend relationships. It explains that use cases describe interactions between actors and the system to achieve goals. The document also provides examples of use case diagrams and descriptions to illustrate how to identify actors and use cases, and describe typical and alternative flows and exceptions. It emphasizes that use cases specify expected behavior from the user's perspective without detailing implementation.
The document discusses functional modeling using activity diagrams and use cases. It provides guidelines for creating activity diagrams and use cases, including identifying activities, control flows, decisions, and parallel processes for activity diagrams. It also discusses writing use case descriptions in SVDPI form from an observer perspective and creating use case diagrams by connecting actors to use cases. The overall purpose is to understand and create functional models to document requirements and describe business processes.
This document discusses using hidden Markov models to automatically discover the structure of clinical forms and annotate them with medical terminology. It presents a two-layer hidden Markov model approach to first assign tags like category and field to form elements, and then group related elements to identify form segments. The method was tested on 52 clinical forms and achieved over 95% accuracy in extracting the underlying structure of the forms in the form of trees. The ability to automatically understand form structure and annotate forms could enable more flexible design of electronic health records.
1. UML is a standardized modeling language used to visualize, specify, construct, and document a system.
2. UML includes structural elements like classes, interfaces, components as well as behavioral elements like use cases, interactions, state machines.
3. UML diagrams like class, sequence, activity diagrams are used to represent different views of a system based on its design, implementation, processes, and deployment.
Interaction modeling describes how objects in a system interact and communicate through message passing. It uses several UML diagrams including use case diagrams, sequence diagrams, activity diagrams, and collaboration diagrams. A use case diagram shows relationships between actors and use cases, while a sequence diagram depicts the temporal order of messages exchanged between objects to complete a scenario. An activity diagram models system workflows and dependencies between activities. A collaboration diagram displays message flows between objects to achieve a particular task.
Application Of UML In Real-Time Embedded Systemsijseajournal
The UML was designed as a graphical notation for use with object-oriented systems and applications.
Because of its popularity, now it is emerging in the field of embedded systems design as a modeling
language. The UML notation is useful in capturing the requirements, documenting the structure,
decomposing into objects and defining relationships between objects. It is a notational language that is
very useful in modelling the real-time embedded systems. This paper presents the requirements and
analysis modelling of a real-time embedded system related to a control system application for platform
stabilization using COMET method of design with UML notation. These applications involve designing of
electromechanical systems that are controlled by multi-processors.
SE18_Lec 06_Object Oriented Analysis and DesignAmr E. Mohamed
The document discusses key concepts in object-oriented systems development including classes, objects, attributes, methods, encapsulation, inheritance, polymorphism, relationships between classes such as associations and aggregations, and object persistence. Object-oriented development models real-world entities as classes of objects that encapsulate both data and behavior and can be organized into inheritance hierarchies.
System model.Chapter One(GEOFFREY GORDON)Towfiq218
This document provides an overview of system modeling concepts. It defines what a system is and basic system components like entities, attributes, and activities. It discusses different types of systems like open vs closed systems, stochastic vs deterministic activities, and continuous vs discrete systems. It also covers various types of models like physical, mathematical, static, and dynamic models. Specific examples are provided to illustrate concepts like static and dynamic physical and mathematical models. Principles of modeling like block-building, relevance, accuracy, and aggregation are also covered.
The document discusses various behavioral diagrams in UML including use case diagrams, sequence diagrams, collaboration diagrams, state machine diagrams and activity diagrams. It provides details on how to model scenarios and interactions using these diagrams, including modeling conditional paths, asynchronous messages, procedural vs flat sequencing, and how interaction diagrams relate to use cases at different levels of abstraction.
Module 3 Object Oriented Data Models Object Oriented notationsTaher Barodawala
The document discusses several object-oriented modeling methodologies including Coad-Yourdon, Shlaer-Mellor, OMT notation, UML notation, and Booch notation. It describes the key concepts, diagrams, and analysis steps of each methodology. The main point is that the choice of methodology is not as important as ensuring the final outcome meets requirements.
This document is a record notebook for a computer science student documenting the experiments completed in a CASE tools laboratory course. It contains details of 15 software systems developed during the course like passport automation, book banking, stock maintenance, etc. It also includes studies of UML diagrams like use case diagrams, sequence diagrams, class diagrams, etc. and how to connect a Visual Basic form to a Microsoft Access database.
IRJET- Facial Gesture Recognition using Surface EMG and Multiclass Support Ve...IRJET Journal
This document presents a study on facial gesture recognition using surface electromyography (EMG) signals and a multiclass support vector machine (SVM) classifier. EMG signals were collected from facial muscles for four expressions: frowning, puckering, smiling, and chewing. Time-domain features like root mean square, variance, and standard deviation were extracted from the EMG signals. These features were classified using SVM and k-nearest neighbors algorithms. SVM achieved the highest accuracy of 92.76% for recognizing the four facial expressions based on the EMG signals. The results indicate this EMG-based approach can efficiently predict different facial expressions.
FORMALIZATION OF A HOSPITAL MANAGEMENT SYSTEMijcseit
The automation of the processing and activities of Hospital Management System (HMS) can invariably
contribute greatly to the success, profitability and customer-based approach of such an organization. The
use of formal specification creates a formal approach for specifying the underlying functions and
properties of the system. This paper has attempted to give a formal description of the activities of a HMS
system Using Zed notation. The interaction within the system is visualized using Unified Modeling
Language (UML) sequence diagrams.
FORMALIZATION & DATA ABSTRACTION DURING USE CASE MODELING IN OBJECT ORIENTED ...cscpconf
In object oriented analysis and design, use cases represent the things of value that the system performs for its actors in UML and unified process. Use cases are not functions or features.
They allow us to get behavioral abstraction of the system to be. The purpose of the behavioral abstraction is to get to the heart of what a system must do, we must first focus on who (or what)
will use it, or be used by it. After we do this, we look at what the system must do for those users in order to do something useful. That is what exactly we expect from the use cases as the
behavioral abstraction. Apart from this fact use cases are the poor candidates for the data abstraction. Rather the do not have data abstraction. The main reason is it shows or describes
the sequence of events or actions performed by the actor or use case, it does not take data in to account. As we know in earlier stages of the development we believe in ‘what’ rather than
‘how’. ‘What’ does not need to include data whereas ‘how’ depicts the data. As use case moves around ‘what’ only we are not able to extract the data. So in order to incorporate data in use cases one must feel the need of data at the initial stages of the development. We have developed the technique to integrate data in to the uses cases. This paper is regarding our investigations to take care of data during early stages of the software development. The collected abstraction of data helps in the analysis and then assist in forming the attributes of the candidate classes. This makes sure that we will not miss any attribute that is required in the abstracted behavior using use cases. Formalization adds to the accuracy of the data abstraction. We have investigated object constraint language to perform better data abstraction during analysis & design in unified paradigm. In this paper we have presented our research regarding early stage data abstraction and its formalization.
Formalization & data abstraction during use case modeling in object oriented ...csandit
This document discusses formalization and data abstraction during use case modeling in object-oriented analysis and design. It provides background on use case modeling and describes how data can be abstracted from use case steps. The document then presents a case study on an e-retail system to demonstrate modeling use cases, actors, and their relationships. It also discusses using activity diagrams to represent use case flows and the Object Constraint Language to add formalism and accuracy to data abstraction during analysis and design.
A Model of Local Area Network Based Application for Inter-office Communicationtheijes
This document presents a model for a local area network (LAN) based application for inter-office communication. The authors designed a messenger software to be installed on an organization's LAN to allow staff to communicate and share information efficiently. The software was developed using Java and analyzed using various UML diagrams. It uses a client-server model with the control part installed on the server and messenger part on clients. The software allows users to send short messages, memos, letters and access an electronic bulletin board. It was tested on a campus LAN network and achieved the objectives of enabling free communication between staff during office hours through a centralized and secure system.
This document discusses system modeling and the Unified Modeling Language (UML). It provides an overview of different types of UML diagrams including class, sequence, use case, state, and activity diagrams. It also discusses modeling systems using these diagrams to represent interactions, structures, contexts and boundaries. Specific examples are provided of using a class diagram and sequence diagram to model elements of a mental healthcare system.
This document discusses system modeling and the Unified Modeling Language (UML). It provides an overview of different types of UML diagrams including class, sequence, use case, state, and activity diagrams. It also discusses modeling concepts such as system boundaries, interactions, and structural models. Specific examples are provided including a use case diagram for a patient data transfer process and a sequence diagram for viewing patient information in a mental healthcare system.
This document provides an overview of system modeling. It discusses that system modeling involves developing abstract models of a system from different perspectives, and is commonly done using the Unified Modeling Language (UML). It also describes various UML diagram types used in system modeling like use case diagrams, class diagrams, and state diagrams. Finally, it gives examples of modeling different views of a mental health case management system, including contextual models, interaction models, structural models, and behavioral models.
It is a well-known fact that precise definitions play significant role in the development of correct and robust
software. It has been recognized and emphasized that appropriately defined formal conceptual framework
of the context/problem domain proves quite useful in ensuring precise definitions, including those for
software metrics, which are consistent, unambiguous and language independent. In this paper, a formal
conceptual framework for defining metrics for component-based system is proposed, where the framework
formalises the behavioural aspects of the problem domain. The framework in respect of structural aspects
has been discussed in another paper.
The document discusses process design and system architecture. It covers:
1) Process design includes both logical and physical design. Logical design models system inputs, outputs, and data flows. Physical design specifies actual system inputs, outputs, storage, processing, and control requirements.
2) Common UML diagrams used in process design are discussed, including class, use case, sequence, state, activity, and component diagrams. These diagrams model different aspects of a system from various perspectives.
3) A wireless sensor network architecture is presented involving sensor nodes communicating data via radio to a base station, which then transmits the aggregated data to other networks.
GENETIC-FUZZY PROCESS METRIC MEASUREMENT SYSTEM FOR AN OPERATING SYSTEMijcseit
This document presents a genetic-fuzzy system for measuring the performance of an operating system's processes. It develops a model using 7 key operating system process parameters and fuzzy logic to handle imprecision. A genetic algorithm is used to optimize the generated membership functions. Rules are created relating parameter combinations to performance classifications. The system was tested on sample data and the genetic algorithm was able to optimize the membership functions over 4 generations to best classify performance. The system brings an optimal and precise approach to measuring operating system process performance by combining genetic algorithms and fuzzy logic.
Genetic fuzzy process metric measurement system for an operating systemijcseit
Operating system (Os) is the most essential software of the computer system,deprived ofit, the computer
system is totally useless. It is the frontier for assessing relevant computer resources. It performance greatly
enhances user overall objective across the system. Related literatures have try in different methods and
techniques to measure the process matric performance of the operating system but none has incorporated
the use of genetic algorithm and fuzzy logic in their varied techniques which indeed is a novel approach.
Extending the work of Michalis, this research focuses on measuring the process matrix performance of an
operating system utilizing set of operating system criteria’s while fusing fuzzy logic to handle
impreciseness and genetic for process optimization.
GENETIC-FUZZY PROCESS METRIC MEASUREMENT SYSTEM FOR AN OPERATING SYSTEMijcseit
Operating system (Os) is the most essential software of the computer system,deprived ofit, the computer system is totally useless. It is the frontier for assessing relevant computer resources. It performance greatly
enhances user overall objective across the system. Related literatures have try in different methods and techniques to measure the process matric performance of the operating system but none has incorporated the use of genetic algorithm and fuzzy logic in their varied techniques which indeed is a novel approach. Extending the work of Michalis, this research focuses on measuring the process matrix performance of an
operating system utilizing set of operating system criteria’s while fusing fuzzy logic to handle impreciseness and genetic for process optimization.
SOFTWARE DESIGN ANALYSIS WITH DYNAMIC SYSTEM RUN-TIME ARCHITECTURE DECOMPOSITIONijseajournal
Software re-engineering involves the studying of targeting system’s design and architecture. However,
enterprise legacy software systems tend to be large and complex, making the analysis of system design
architecture a difficult task. To solve this problem, the study proposes an approach that dynamically
decomposes software architecture using the run-time system information to reduce the complexity
associated with analyzing large scale architecture artifacts. The study demonstrates that dynamic
architecture decomposition is an efficient way to limit the complexity and risk associated with reengineering
activities of a large legacy system. This new approach divides the system into a collection of
meaningful modular parts with low coupling, high cohesion, and a minimal interface. This division
facilitates the design analysis and incremental software re-engineering process. This paper details two
major techniques to decompose legacy system architecture. The approach is also supported by automated
reverse engineering tools that were developed during the course of the study. The preliminary results
indicate that this novel approach is very promising.
an analysis and new methodology for reverse engineering of uml behavioralINFOGAIN PUBLICATION
The emergence of Unified Modeling Language (UML) as a standard for modeling systems has encouraged the use of automated software tools that facilitate the development process from analysis through coding. Reverse Engineering has become a viable method to measure an existing system and reconstruct the necessary model from its original. The Reverse Engineering of behavioral models consists in extracting high-level models that help understand the behavior of existing software systems. In this paper we present an ongoing work on extracting UML diagrams from object-oriented programming languages. we propose an approach for the reverse engineering of UML behavior from the analysis of execution traces produced dynamically by an object-oriented application using formal and semi-formal techniques for modeling the dynamic behavior of a system. Our methods show that this approach can produce UML behavioral diagrams in reasonable time and suggest that these diagrams are helpful in understanding the behavior of the underlying application.
Comparison of the Formal Specification Languages Based Upon Various ParametersIOSR Journals
This document compares various formal specification languages based on different parameters. It describes Z notation, OCL, VDM, SDL and Larch languages. Z notation uses set theory and logic to model state using schemas. OCL uses constraints to describe UML models. VDM uses basic types and functions to formally specify models. SDL specifies systems as communicating finite state machines. Larch uses an interface language and shared language to specify behaviors. The languages differ based on whether they are process-oriented, sequential-oriented, model-oriented or property-oriented and the underlying mathematics used like set theory, logic or algebra.
This document discusses analyzing the requirements of a restaurant system using UML diagrams. It describes drawing interaction diagrams to realize use cases, defines attributes and operations for each class, and discusses responsibilities and cohesion of classes. It also covers software architecture patterns, mapping a three-tier architecture to the restaurant system, and refining the domain model based on use case analysis.
Distributed Graphical User Interfaces to Class Diagram: Reverse Engineering A...ijseajournal
The graphical user interfaces of software programs are used by researchers in the soft-ware engineering
field to measure functionality, usability, durability, accessibility, and performance. This paper describes a
reverse engineering approach to transform the cap-tured images of the distributed GUIs into class
diagram. The processed distributed GUIs come from different and separate client computers. From the
distributed GUIs, the inter-faces are captured as images, attributes and functions are extracted and
processed through pattern recognitions mechanism to be stored into several temporary tables
corresponding to each client’s graphical user interface. These tables will be analyzed and processed into
one integrated normalized table eliminating any attribute redundancies. Further, the normalized the one
integrated table is to create a class diagram.
This document describes a methodology for simulating heterogeneous embedded systems that include hardware, software, and electromechanical parts. Interfaces were developed to allow a VHDL simulator to communicate with a physical systems simulator and application programs. The interfaces use the C language links of the simulators to establish communication channels and exchange commands/parameter values between the simulated parts in a chained master/slave synchronization scheme. This unified simulation environment allows designers to validate the behavior of the entire system early in the design process before implementing any of its parts.
Similar to Formalization of a Hospital Management System (20)
Digital Twins Computer Networking Paper Presentation.pptxaryanpankaj78
A Digital Twin in computer networking is a virtual representation of a physical network, used to simulate, analyze, and optimize network performance and reliability. It leverages real-time data to enhance network management, predict issues, and improve decision-making processes.
Design and optimization of ion propulsion dronebjmsejournal
Electric propulsion technology is widely used in many kinds of vehicles in recent years, and aircrafts are no exception. Technically, UAVs are electrically propelled but tend to produce a significant amount of noise and vibrations. Ion propulsion technology for drones is a potential solution to this problem. Ion propulsion technology is proven to be feasible in the earth’s atmosphere. The study presented in this article shows the design of EHD thrusters and power supply for ion propulsion drones along with performance optimization of high-voltage power supply for endurance in earth’s atmosphere.
Embedded machine learning-based road conditions and driving behavior monitoringIJECEIAES
Car accident rates have increased in recent years, resulting in losses in human lives, properties, and other financial costs. An embedded machine learning-based system is developed to address this critical issue. The system can monitor road conditions, detect driving patterns, and identify aggressive driving behaviors. The system is based on neural networks trained on a comprehensive dataset of driving events, driving styles, and road conditions. The system effectively detects potential risks and helps mitigate the frequency and impact of accidents. The primary goal is to ensure the safety of drivers and vehicles. Collecting data involved gathering information on three key road events: normal street and normal drive, speed bumps, circular yellow speed bumps, and three aggressive driving actions: sudden start, sudden stop, and sudden entry. The gathered data is processed and analyzed using a machine learning system designed for limited power and memory devices. The developed system resulted in 91.9% accuracy, 93.6% precision, and 92% recall. The achieved inference time on an Arduino Nano 33 BLE Sense with a 32-bit CPU running at 64 MHz is 34 ms and requires 2.6 kB peak RAM and 139.9 kB program flash memory, making it suitable for resource-constrained embedded systems.
Generative AI Use cases applications solutions and implementation.pdfmahaffeycheryld
Generative AI solutions encompass a range of capabilities from content creation to complex problem-solving across industries. Implementing generative AI involves identifying specific business needs, developing tailored AI models using techniques like GANs and VAEs, and integrating these models into existing workflows. Data quality and continuous model refinement are crucial for effective implementation. Businesses must also consider ethical implications and ensure transparency in AI decision-making. Generative AI's implementation aims to enhance efficiency, creativity, and innovation by leveraging autonomous generation and sophisticated learning algorithms to meet diverse business challenges.
https://www.leewayhertz.com/generative-ai-use-cases-and-applications/
Applications of artificial Intelligence in Mechanical Engineering.pdfAtif Razi
Historically, mechanical engineering has relied heavily on human expertise and empirical methods to solve complex problems. With the introduction of computer-aided design (CAD) and finite element analysis (FEA), the field took its first steps towards digitization. These tools allowed engineers to simulate and analyze mechanical systems with greater accuracy and efficiency. However, the sheer volume of data generated by modern engineering systems and the increasing complexity of these systems have necessitated more advanced analytical tools, paving the way for AI.
AI offers the capability to process vast amounts of data, identify patterns, and make predictions with a level of speed and accuracy unattainable by traditional methods. This has profound implications for mechanical engineering, enabling more efficient design processes, predictive maintenance strategies, and optimized manufacturing operations. AI-driven tools can learn from historical data, adapt to new information, and continuously improve their performance, making them invaluable in tackling the multifaceted challenges of modern mechanical engineering.
Discover the latest insights on Data Driven Maintenance with our comprehensive webinar presentation. Learn about traditional maintenance challenges, the right approach to utilizing data, and the benefits of adopting a Data Driven Maintenance strategy. Explore real-world examples, industry best practices, and innovative solutions like FMECA and the D3M model. This presentation, led by expert Jules Oudmans, is essential for asset owners looking to optimize their maintenance processes and leverage digital technologies for improved efficiency and performance. Download now to stay ahead in the evolving maintenance landscape.
Null Bangalore | Pentesters Approach to AWS IAMDivyanshu
#Abstract:
- Learn more about the real-world methods for auditing AWS IAM (Identity and Access Management) as a pentester. So let us proceed with a brief discussion of IAM as well as some typical misconfigurations and their potential exploits in order to reinforce the understanding of IAM security best practices.
- Gain actionable insights into AWS IAM policies and roles, using hands on approach.
#Prerequisites:
- Basic understanding of AWS services and architecture
- Familiarity with cloud security concepts
- Experience using the AWS Management Console or AWS CLI.
- For hands on lab create account on [killercoda.com](https://killercoda.com/cloudsecurity-scenario/)
# Scenario Covered:
- Basics of IAM in AWS
- Implementing IAM Policies with Least Privilege to Manage S3 Bucket
- Objective: Create an S3 bucket with least privilege IAM policy and validate access.
- Steps:
- Create S3 bucket.
- Attach least privilege policy to IAM user.
- Validate access.
- Exploiting IAM PassRole Misconfiguration
-Allows a user to pass a specific IAM role to an AWS service (ec2), typically used for service access delegation. Then exploit PassRole Misconfiguration granting unauthorized access to sensitive resources.
- Objective: Demonstrate how a PassRole misconfiguration can grant unauthorized access.
- Steps:
- Allow user to pass IAM role to EC2.
- Exploit misconfiguration for unauthorized access.
- Access sensitive resources.
- Exploiting IAM AssumeRole Misconfiguration with Overly Permissive Role
- An overly permissive IAM role configuration can lead to privilege escalation by creating a role with administrative privileges and allow a user to assume this role.
- Objective: Show how overly permissive IAM roles can lead to privilege escalation.
- Steps:
- Create role with administrative privileges.
- Allow user to assume the role.
- Perform administrative actions.
- Differentiation between PassRole vs AssumeRole
Try at [killercoda.com](https://killercoda.com/cloudsecurity-scenario/)
AI for Legal Research with applications, toolsmahaffeycheryld
AI applications in legal research include rapid document analysis, case law review, and statute interpretation. AI-powered tools can sift through vast legal databases to find relevant precedents and citations, enhancing research accuracy and speed. They assist in legal writing by drafting and proofreading documents. Predictive analytics help foresee case outcomes based on historical data, aiding in strategic decision-making. AI also automates routine tasks like contract review and due diligence, freeing up lawyers to focus on complex legal issues. These applications make legal research more efficient, cost-effective, and accessible.
VARIABLE FREQUENCY DRIVE. VFDs are widely used in industrial applications for...PIMR BHOPAL
Variable frequency drive .A Variable Frequency Drive (VFD) is an electronic device used to control the speed and torque of an electric motor by varying the frequency and voltage of its power supply. VFDs are widely used in industrial applications for motor control, providing significant energy savings and precise motor operation.
1. International Journal of Computer Science, Engineering and Information Technology (IJCSEIT), Vol.7, No.3, June 2017
DOI : 10.5121/ijcseit.2017.7302 11
FORMALIZATION OF A HOSPITAL MANAGEMENT
SYSTEM
Okpor Margaret Dumebi
Department of Computer Science, Delta State, Polytechnic, Ozoro
ABSTRACT
The automation of the processing and activities of Hospital Management System (HMS) can invariably
contribute greatly to the success, profitability and customer-based approach of such an organization. The
use of formal specification creates a formal approach for specifying the underlying functions and
properties of the system. This paper has attempted to give a formal description of the activities of a HMS
system Using Zed notation. The interaction within the system is visualized using Unified Modeling
Language (UML) sequence diagrams.
KEYWORDS
HMS, Z-Notation, UML.
1. INTRODUCTION
Hospital Management Software (HMS) or Hospital Information System (HIS) or Hospital
Management Information System (HMIS) is software developed to facilitate easy, prudent and
customer-eccentric hospital services. This includes the clinical back office and generic
management processes. It integrates the entire resources of the hospital for easy organizational
process [1], [7].
This software usually offers; Registration and enquiry, physician order entry, casualty and
emergency management, pharmacy management system, laboratory information system, nursing
and ward management, store and inventory management, duty roster management, blood bank
management, ambulance services, patient referral, biomedical waste management [1]; [7]
The HMS is an all encompassing system. These systems includes: SoftClinc, Insta HMS,
eHopsital Systems, Health Data Archiver, Hospital Management Software,uniwide HIMS,
Medstar HIS, ProMED, Availity, evbisit, HIMS, Health.Net, SisoHIS, eHat, GeroPro, Suvarna-
HIS, MD-staff, Axpert HMS [4]; [7]
Generally speaking, a specification is the expression in some formal terms and at some level of
abstraction, of a collection of properties, some system should satisfy. The historical perspectives
and the qualities of good specifications have been discussed in [2]; [3].
Z–Notation is a formal specification construct based on set algebra and predicate calculus for
specification of computing systems [2], [3]. It has the ability of decomposing specification into
small piece called schemas. By splitting the specification into schemas, we can present it piece by
piece.
2. International Journal of Computer Science, Engineering and Information Technology (IJCSEIT), Vol.7, No.3, June 2017
12
Over the years the ambiguities in software system have been addressed with appropriate
formalization [2], [3]. These formalizations possibly have been devoid from most medical
systems, initiating researches toward this area.
Therefore it is the intent of this research to address the aforementioned issue utilizing a formal
approach.
2. MATERIAL AND METHODOLOGY
In achieving the objective of determining formal methods in ascertaining the functionalities of
Hospital Management System (HMS), Z-notation and Unified Modelling Language (UML)
serves as the main tools for the methodology of this work.
Z-notation uses mathematical notation to describe in a precise way the properties a software
system must possess, without unduly constraining the way in which these properties are achieved
[9], [6], [8]. Formal specification (Mathematical notation or Z) uses mathematical data types to
model data in a system and achieve it underlining objectives. These data types are not oriented
towards computer representation, but they obey a rich collection of mathematical laws which
make it possible to reason effectively about the way a specified system will behave. The research
uses the notation of predicate logic to describe abstractly the effect of each operation of the
system, again in a way that enables one to reason about their behaviour.
The other main ingredient in Z is a way of decomposing a specification into small pieces called
Schemas. By splitting the specification into schemas, we can present it piece by piece. Each piece
can be linked with a commentary which explains informally the significance of the formal
mathematics. In Z, schemas are used to describe both static and dynamic aspects of a system [9]
The static aspects include:
a. the state it can occupy;
b. the invariant (quantity that is unchanged by a set of mathematical operation) relationships
that are maintained as the system moves from states to state.
The dynamic aspects include:
a. the operation aspect that are possible;
b. the relationship between their input and outputs;
c. the changes of state that happen.
The schema presented in this presented paper provided an avenue wherein our formal
specification could be presented in fragment enabling us to associate commentaries; explaining
informally the significance of the formal mathematical notation representation.
2.1 METHODOLOGY
The following are some of the basic types in Z:
{CHAR, STRING, CURRENCY, QUERY, OBJECT, COMPONENTS, BOOLEAN:: =
TRUE/FALSE, DATA and OBJECT}.
3. International Journal of Computer Science, Engineering and Information Technology (IJCSEIT), Vol.7, No.3, June 2017
13
The Hospital Management System (HMS) authenticates each user using his username/ID and
password on the system:
System User
System User_name/ID: seq CHAR
System User_password: seq CHAR
System User: ℙ System User
Access! : Boolean User
System ∈system.access! = accepted) ٧ (system ∉system.access ≠ accepted)
Schema 1:SystemUser Schema
There is no frontier to the number of registered system user the Hospital Management System can
ascertain and each system user can have only one authentication and authorization privilege.
Logging on, each system user must register his user ID.
System List
System: ℙSYSTEM: ℙHOSPITAL FUNCTIONALITIES
System List: SYSTEM →HOSPITAL FUNCTIONALITIES
Systems = dom list
Schema 2: System List
The Systemlist provides the hospital functionalities provided by the system.
Register Hospital functionalities
∆ System List
System? : SYSTEM
Hospital Functionalities: Hospital Functionalities
report! : REPORT
(system? ∉system٨System List′ = SystemList U {system? →Functionalities?}٨ report! =
ok) ٧(system? ∉system٨systemlist′ = systemlist٨ Report! = already_known)
Schema 3: Register Hospital Functionalities Schema
The list braces the facility in registering hospital functionalities given that the system process
does not exist previously. If the process exists previously, a report of ‘already known’ is returned
or vice versa as the case may be.
Locate HospitalProcess
Ξ SystemList
Processes? : HOSPITAL PROCESSESS
Systemlist?ℙ HOSPITAL PROCESSES
(systemlist! = {system: systems / list (system) = process?}٧ (system ∉ systems ٨ report! =
not_known)
Schema 4: Locate Hospital process Schema
4. International Journal of Computer Science, Engineering and Information Technology (IJCSEIT), Vol.7, No.3, June 2017
14
The Locate Hospital Process function obtains a process type as an argument and returns a result
responds.
AlreadyExisting Hotel Process
Ξ SystemList
system? : SYSTEM
result! : REPORT
process? ∈ Processes
result! = already_known
Schema 5: AlreadyExisting Hospital ProcessSchema
The AlreadyExisting Hospital ProcessSchema determines if a change to the systemlist in terms of
new input process already. If it the result, will reply already_knowm otherwise not known.
Hospital ProcessNotAvailable
Ξ Processlist
process: ℙHOSPITAL PROCESS
report! : REPORT
request? : HOSPITAL PROCESS
∀process ∈system.list (process) ≠ Reliability
report! = not_known
Shema6: Hospital ProcessNotAvailable Schema
The schema 6 shows the error which occurs when a system user requests for a process which has
not been registered in the systemlist. An error report of ‘not known’ is returned. The list is
initialized at the beginning with no process or hospital process in Schema 7.
Hospital Initialize_List
SystemList
PROCESS: ℙHOTEL PROCESSES
systemlist = ∅
hotelprocess = ∅
Schema 7: Initialize_List Schema
2.2 SYSTEM DESIGN AND UNIFIED MODELING LANGUAGE (UML)
Software design immediately follows the requirements engineering phase in a software process.
Software design is the translation of the requirement specification into useful patterns for
implementation. Unified Modelling Language (UML) is a standard modelling language used for
modelling software systems. UML was used for design of the hospital system process because
UML focuses on creating simple, well documented and easy to understand software models.
UML sequence diagram shows the interaction between classes (or object) in the system for each
use case. The interaction represents the order of messages that are exchanged between classes to
accomplish a purpose. For the system we specify the utilizing several sequence diagram specified
on Figure 1.
5. International Journal of Computer Science, Engineering and Information Technology (IJCSEIT), Vol.7, No.3, June 2017
Figure 1: Registration User Sequence Diagram for HMS
Figure 1 models the sequence of steps involved in the registration of a system user. The order of
appearance of the arrows indicates the
direction of flow of events / results.
3. IMPLEMENTATION
The implementation of the system was handled utilizing MATLAB, for several reasons:
a. It also manipulates across varied numerical data and
interfaces.
b. Since formal specification are specified utilizing mathematical notation, MATLAB was
at the frontier of all available implementation tools available due to
mathematical ingredients.
c. It is open source
d. Most importantly, it has a large active community base
Utilizing several MATLAB tools such:
a. Assignment Statements
overriding Predecessor variable
statement were used in the system to override previous entries which have be saved to the
system database
International Journal of Computer Science, Engineering and Information Technology (IJCSEIT), Vol.7, No.3, June 2017
Registration User Sequence Diagram for HMS
Figure 1 models the sequence of steps involved in the registration of a system user. The order of
appearance of the arrows indicates the order of the actions while the arrow direction indicates the
direction of flow of events / results.
The implementation of the system was handled utilizing MATLAB, for several reasons:
It also manipulates across varied numerical data and It integrates with numerous user
Since formal specification are specified utilizing mathematical notation, MATLAB was
at the frontier of all available implementation tools available due to
mathematical ingredients.
Most importantly, it has a large active community base
Utilizing several MATLAB tools such:
Assignment Statements: Assignment statement as a MATLAB tool was used in
overriding Predecessor variable while the successor variable took over. The assignment
statement were used in the system to override previous entries which have be saved to the
International Journal of Computer Science, Engineering and Information Technology (IJCSEIT), Vol.7, No.3, June 2017
15
Figure 1 models the sequence of steps involved in the registration of a system user. The order of
order of the actions while the arrow direction indicates the
The implementation of the system was handled utilizing MATLAB, for several reasons:
It integrates with numerous user
Since formal specification are specified utilizing mathematical notation, MATLAB was
its available
Assignment statement as a MATLAB tool was used in
while the successor variable took over. The assignment
statement were used in the system to override previous entries which have be saved to the
6. International Journal of Computer Science, Engineering and Information Technology (IJCSEIT), Vol.7, No.3, June 2017
16
b. Case Sensitivity: The variable name within are system were case sensitive acceding to
Matric laboratory rules. The case sensitive rules in MatLab helped us in distinctively
separating our variables name
c. Immediate and Deferred Execution: When MATLAB is invoked; the user is presented
with an interactive environment. Enter a statement, press the carriage return ("ENTER")
and the statement is immediately executed. Given the power that can be packed into one
MATLAB statement, this is no small accomplishment.
4. FINDINGS
Based on the ease at which the users get information through this new system, a lot are sure to be
benefitted from this system. The system will:
a. Provide hospital process thereby eliminating wastage of unusual time
b. Eliminate and ratify unknown errors
c. Support multiple system processes
d. Provide user-friendliness interface
5. CONCLUSION
Formal specification is the bedrock of safety critical system which uncovers ambiguities and
unwanted error from system requirement. In Nigeria and African as a whole this approach has not
be implemented for most safety critical system opening the avenue for system failure with huge
implication such as financial loss and untimely death. This research paper focuses on providing a
sample representation of formal specification utilizing hospital proc esses as a case base. The
system design was specified utilizing UML while implementation was handled exploring
MATLAB. The results of the finding were listed assiduously. Formal specification is an avenue
for safety critical system which must be explored in as much safety is involved.
REFERENCES
[1] Acgil (1993), Hospital Management Information System, retrieved online from
http://www.acgil.com/products/hospital_management_system.htm
[2] Bowen J. P., (1988), Formal Specification in Z as a design and documentation tool. In proc.
Second IEE/BCS Conference on Software Engineering, number 290 in conference publication,
pages 164-168.
[3] Bowen P., (1990), Z bibliography, Oxford University Computing Laboratory.
[4] Capterra (2017), Top Hospital Management Solutions, retrieved online from
http://www.capterra.com/hospital-management-software
[4] CISA: Certified Information System Auditor (2011), “Cisa review manual 2010”, Chapter 5, Pp.
305.
[5] Jiantao P. (1999), “Software Reliability”, retrieved online from
http://ece.cmu.edu/koopman/Des_a 99/sw-reliability
7. International Journal of Computer Science, Engineering and Information Technology (IJCSEIT), Vol.7, No.3, June 2017
17
[6] Sannella D., (1988), “A Survey of formal software development methods”, appeared in Software
Engineering: A European Perspective, A. McGettrick and R. Thayer (eds.), IEEE Computer
Society Press, pp 281-297, 1993.
[7] SoftSuggest (2017) Best HopsitalManagenetSofwtare Solution-2017, retrived online from
https://www.softwaresuggest.com/hospital-management-software
[8] Spivey J. M. (1992), “The Z Notation: A Reference Manual, 2nd Edition”, Prentice Hall
International (UK) limited, United Kingdom.
[9] Spivey J. M. (1998), “The Z Notation: A Reference Manual”, Oxford, United Kingdom.
[10]Stuart R., and Norvig P. (1995), “Artificial Intelligence: A Modern Approach”, Prentice Hall (UK)
International.
AUTHOR
Mrs. Margaret Dumebi Okpor has B.Sc and M.Sc degrees in Computer
Science from University of Benin, Edo State, Nigeria in the years 1996 and
2012, respectively. Currently she is running a Ph.D programme in Computer
Science. She has been involved in teaching Computer Science courses for over
10 years in the Delta State Polytechnic, Ozoro, Delta State, Nigeria. She was
Head of Department in the Department of Computer Science in the same
institution. She is a member of Computer Professionals of Nigeria (CPN). She
has published several papers in local and international journals. Her research
interests include machine learning, soft computing, computational intelligence
and evolutional computing.