Modeling Requirements for Value Configuration Design

Breadth and depth complexity are key challenges in achieving business process fusion as the enabler for value configuration design. The PARM framework is proposed as the requirement to address breadth and depth complexity through the independent but integrated operation of the process, activity, resource and management viewpoints. The operational scenarios for each viewpoint result in varying process modeling extension requirements. Existing process modeling constructs have varying support for these requirements. The PARM framework solution is an extension and integration of existing modeling constructs rather than a solution in its own right. Using the MDA approach of abstracting a platform independent model from a platform specific implementation, it is the goal in future papers to define process modeling extensions to support the PARM framework and map these into existing implementation architectures

Requirement Model for Instructor Management System

The purpose of this project is to create a requirement model for Instructor Management System (IMS) based in Universiti Utara Malaysia (UUM), Kedah Darul Aman. Requirement model provide a more structured and integrated guide for the development of systems. Its serves as a good starting point or reference for system developers to understand the user's requirement which save cost, time and resources, thus helps to decrease effort in the system development process and increased quality of the developed system. The methodology for requirement mode of the IMS is derived from requirements, analyze requirements and validate requirement model. System modeling and prototyping approach were used for requirement validation, while HOORA Analysis Tool (HAT was used to validate the requirement model. Unified Modeling Language (UML) notation was adopted for the development of the requirement model. The requirement model consists of use case diagram, use case specification, class diagram, sequence diagram, collaboration diagram, activity diagram and supporting textual information. This requirement model provides a guideline in developing IMS by specifies a solution that is right for the user's needs. This project concludes by discussing problems and limitations that were encountered in completing this project, and offers a few recommendations for future development in this subject

Case history of FAA/SRI wind shear models

In order to understand the development of the FAA/SRI wind fields, it is important to understand the operating philosophy of the FAA's Wind Shear Program Office. The goal of the office was to ensure an integrated solution to the wind shear problem which addressed three area: ground based equipment and coordination; airborne systems and procedures; and weather prediction. This triply addressed goal was central to the development of the wind fields. The primary user of the wind shear modeling during the FAA's program was airborne simulation. The project requirement was to use wind shear models that resulted from accidents so that effective procedures and/or equipment could be found for hazardous wind shear encounters. The wind shear model development is discussed in detail

A Requirement Model for Computer Hardware Tracking System

The purpose of this project is to create a requirement model for Computer Hardware Tracking system for Royal Malaysia Navy. Requirement model provide a more structured and integrated guide for the development of systems. Its serves as a good starting point or reference for system developers to understand the user’s requirement which save cost, time and resources, thus, helps to decrease efforts in the system development process and increased quality of developed system. The methodology for requirement model of the CHTS derived from requirements analysis, analyze requirements and validate requirement model. System modeling and prototyping approach were used for requirement validation, while HOORA Analysis Tool (HAT) was used to validate the requirement model. Unified Modeling Language (UML) notation was adopted for the development of the requirement model. The requirement model consist of use case diagram, use case specification, class diagram, sequence diagram, collaboration diagram, activity diagram and supporting textual information. This requirement model provides a guideline in developing CHTS by specifies a solution that is right for the users need. As a conclusion, the requirement model created has solved the tracking problem as well as managing the computer hardware all over the units and ships in RMN. The requirement model can be improved that can be used in other organization. The requirement model also can be used by similar organization like army and air force

Requirements analysis for decision-support system design: evidence from the automotive industry

The purpose of this paper is to outline the requirements analysis that was carried out to support the development of a system that allows engineers to view real-time data integrated from multiple silos such as Product Lifecycle Management (PLM) and Warranty systems, in a single and visual environment. The outcome of this study provides a clear understanding of how engineers working in different phases of the product-lifecycle could utilise such information to improve the decision making process and as a result design better products. This study uses data collected via in-depth semi-structured interviews and workshops that includes people working in various roles within the automotive sector. In order to demonstrate the applicability this approach, SysML diagrams are also provided

Hierarchical approach to 'atomistic' 3-D MOSFET simulation

We present a hierarchical approach to the 'atomistic' simulation of aggressively scaled sub-0.1-μm MOSFETs. These devices are so small that their characteristics depend on the precise location of dopant atoms within them, not just on their average density. A full-scale three-dimensional drift-diffusion atomistic simulation approach is first described and used to verify more economical, but restricted, options. To reduce processor time and memory requirements at high drain voltage, we have developed a self-consistent option based on a solution of the current continuity equation restricted to a thin slab of the channel. This is coupled to the solution of the Poisson equation in the whole simulation domain in the Gummel iteration cycles. The accuracy of this approach is investigated in comparison to the full self-consistent solution. At low drain voltage, a single solution of the nonlinear Poisson equation is sufficient to extract the current with satisfactory accuracy. In this case, the current is calculated by solving the current continuity equation in a drift approximation only, also in a thin slab containing the MOSFET channel. The regions of applicability for the different components of this hierarchical approach are illustrated in example simulations covering the random dopant-induced threshold voltage fluctuations, threshold voltage lowering, threshold voltage asymmetry, and drain current fluctuations

Modeling of Traceability Information System for Material Flow Control Data.

This paper focuses on data modeling for traceability of material/work flow in information layer of manufacturing control system. The model is able to trace all associated data throughout the product manufacturing from order to final product. Dynamic data processing of Quality and Purchase activities are considered in data modeling as well as Order and Operation base on lots particulars. The modeling consisted of four steps and integrated as one final model. Entity-Relationships Modeling as data modeling methodology is proposed. The model is reengineered with Toad Data Modeler software in physical modeling step. The developed model promises to handle fundamental issues of a traceability system effectively. It supports for customization and real-time control of material in flow in all levels of manufacturing processes. Through enhanced visibility and dynamic store/retrieval of data, all traceability usages and applications is responded. Designed solution is initially applicable as reference data model in identical lot-base traceability system

Ship product modelling

This paper is a fundamental review of ship product modeling techniques with a focus on determining the state of the art, to identify any shortcomings and propose future directions. The review addresses ship product data representations, product modeling techniques and integration issues, and life phase issues. The most significant development has been the construction of the ship Standard for the Exchange of Product Data (STEP) application protocols. However, difficulty has been observed with respect to the general uptake of the standards, in particular with the application to legacy systems, often resulting in embellishments to the standards and limiting the ability to further exchange the product data. The EXPRESS modeling language is increasingly being superseded by the extensible mark-up language (XML) as a method to map the STEP data, due to its wider support throughout the information technology industry and its more obvious structure and hierarchy. The associated XML files are, however, larger than those produced using the EXPRESS language and make further demands on the already considerable storage required for the ship product model. Seamless integration between legacy applications appears to be difficult to achieve using the current technologies, which often rely on manual interaction for the translation of files. The paper concludes with a discussion of future directions that aim to either solve or alleviate these issues