THE HEAO EXPERIENCE — DESIGN THROUGH OPERATIONS

Performing rigorous analysis of parallel and distributed systems (PDS) specifications is one of the important tasks during the early stages of development. The ambiguities and errors left unchecked during the analysis phase can creep into design and development phases, resulting in cost and schedule overruns and a less reliable end product. Commercial off the shelf CASE (Computer Aided Software Engineering) tools can play an important role in the analysis and design phases. However techniques must be developed to address the shortcomings of CASE tools. A set of such techniques is presented in this paper. CASE tools can be used to gather PDS specifications in the form of analysis models. The techniques presented in this paper deal with the problem of performing rigorous analysis of PDS specifications originally developed using a CASE tool. The approach is based on integrating a CASE tool with a verification tool based on coloured Petri nets (CPNs). CPNs can be used to model and analyze concurrency in specifications and design phases. Dynamic simulations of CPN models can be used to conduct performance/performability analysis as well as risk assessment studies.

This research was aimed to design a booklet of local folktales to support junior high school ninth grade students English extensive reading activities as well as to help them to reach their reading objectives in classroom with the related reading topic. This research was a subject of an English teacher. The method used for this research was development research that used the first three phases of the ADDIE instructional model, namely the analysis, design, and development phases. We conducted the first interview, followed by documentation and observation to gather the data and used experts’ recommendations and descriptive analysis to analyze the data. In the analysis phase, as the preliminary process of the research, we collected the data through interviews, documentation, and observation. In the design phase, we began to design a draft of the product. In the development phase, we started to develop a draft of the local folktales booklet followed by an internal evaluation. According to the findings of the research, it was indicated that the local folktales booklet was appropriate and able to support the students’ English extensive reading activities as well as to be their supplementary reading material product to be used in the classroom.

Technological developments occurring at the beginning of this century and particularly from the 1950s onward led to the construction of large, complex systems which were both productive and dangerous. The word dangerous can have many meanings: unsafe (nuclear power plants), or sensitive but essential (computer systems of a company), etc. Observations have shown that minor causes can lead to major effects resulting in undesirable events. Studies have been undertaken over the last forty years to predict and avoid these events. These studies constitute an interdisciplinary concept known as reliability . The 1970s constitute the turning period for the hardware/software dichotomy in industrial systems, and the importance of software is increasing rapidly. The main feature of software, as compared to hardware, is that it is not subject to physical breakdown due to wear and tear. The idea followed by researchers and practitioners since then is to concentrate effort in the requirement, specification, design, coding, and testing phases of development in order to ensure high quality and zero defect software at delivery time. These efforts have resulted in the accumulation of an enormous set of development methodologies and techniques accompanied by appropriated languages and tools. These languages and tools are used to improve the adherence to software production requirements, e.g., costs, schedule, and technical characteristics such as performance and reliability. Quantitative methods used in the latter steps of development such as reliability estimation or testing techniques help to increase confidence in the software. During the design phase, qualitative methods can be used efficiently for certain types of studies (safety, availability, etc.) for it is widely accepted that fixing a bug in early phases of development minimizes cost and efforts. Failure modes and effects analysis (FMEA) is one of these methods: originally developed for use in a hardware context, the technique was applied during the 1970s to software development. First its utilization by the hardware community is recieved. After a survey of FMEA's application in software, its role in the software process and its place in the software life‐cycle development are described. Procedures for its implementation will constitute the last part of the article.

Providing English learning material with an Islamic basis for Madrasah Aliyah students is important as the students are Islamic learners. This research aims to develop an e-module of Islamic reading text materials for the second semester of tenth-grade students of MAN 1 Pontianak. The researchers adapted the Analyze, Design, and Develop phases of the ADDIE concept to develop this research product. The analysis phase was conducted by interviewing the English teacher to determine the suitable e-module to be designed. The design phase was done by designing the contents of the e-module based on the analysis results. The e-module consists of recount and narrative texts materials with Islamic-based stories and integrates the values of aqidah (strong belief), tawakkul (reliance upon Allah), tolerance, hard work, and husnuzon (positive thinking). In the development phase, the researchers developed the e-module then checked it with a self-designed standard evaluation checklist. The result showed that the e-module already fulfilled the criteria of appropriateness. The e-module could be supplementary reading materials to make the students’ autonomous learning easier. It was written in easy-to-understand language and provided self-instructional material with independent self-evaluation. Specifically, it is expected to improve their understanding of recount and narrative text materials and strengthen their Islamic character values.

1.2 What are the main phases of product design and development Before discuss the collaboration issues for product design and development, we need to briefly review the phases of product design and development. The major phases of product design and development are normally defined as conceptual design, preliminary design, and detail design and development (Blanchard, 2004). During the conceptual design phase, the concepts, which are also called scheme, are built in order to completely and efficiently design the transceiver. The concepts may include such as product operational requirements and maintenance, current product problem (or deficiency), functional analysis for the product, applicable technical performance measures (TPMs), and specific performance measures and design-to criteria. Preliminary design phase begins with a “functional baseline” product configuration described in the product specification prepared during conceptual design phase. The functional baseline is translated into detailed qualitative and quantitative design requirements for allocating applicable elements of the product. An “allocated baseline” configuration in the form of development, product, and process specifications is established during this phase. At the beginning of detail design and

The OpenOrbiter I mission has changed significantly since its conceptualization, as the small spacecraft industry has evolved – rapidly – around it. The spacecraft design has iterated through multiple concepts as changing policies and technical realities prevented various initial design decisions from being brought to fruition. Communications licensing issues, power consumption and the physical footprint of a licensable radio and structural changes are among the many challenges that the project faced. The initial goals of the mission are reviewed and an update is provided on its current status as it heads through the final steps in preparation for launch. The mission concept and revised concept of operations are reviewed. In particular, changes to the power and communications systems are discussed. The new power system and communications systems and the impact that these have on the spacecraft and overall mission are presented and discussed in detail. The paper reviews the student learning that has occurred throughout the mission development process and the impact of the required changes and associated processes on the student learning mission objectives. It revisits the question of build versus buy, in light of the pathway taken (build), the challenges that have been encountered and the results. The paper extracts, from the program’s activities and results, lessons and best practices that can be applied by others within the small spacecraft domain. It concludes with a discussion of what the mission has demonstrated to-date, what will be demonstrated by on-orbit operations and the team’s plans for future work in this area.

BackgroundThe development of integrated care is a complex and long term process. Previous research shows that this development process can be characterised by four phases: the initiative and design phase; the experimental and execution phase; the expansion and monitoring phase and the consolidation and transformation phase. In this article these four phases of the Development Model for Integrated Care (DMIC) are validated in practice for stroke services, acute myocardial infarct (AMI) services and dementia services in the Netherlands.MethodsBased on the pre-study about the DMIC, a survey was developed for integrated care coordinators. In total 32 stroke, 9 AMI and 43 dementia services in the Netherlands participated (response 83%). Data were collected on integrated care characteristics, planned and implemented integrated care elements, recognition of the DMIC phases and factors that influence development. Data analysis was done by descriptive statistics, Kappa tests and Pearson’s correlation tests.ResultsAll services positioned their practice in one of the four phases and confirmed the phase descriptions. Of them 93% confirmed to have completed the previous phase. The percentage of implemented elements increased for every further development phase; the percentage of planned elements decreased for every further development phase. Pearson’s correlation was .394 between implemented relevant elements and self-assessed phase, and up to .923 with the calculated phases (p < .001). Elements corresponding to the earlier phases of the model were on average older. Although the integrated care services differed on multiple characteristics, the DMIC phases were confirmed.ConclusionsIntegrated care development is characterised by a changing focus over time, often starting with a large amount of plans which decrease over time when progress on implementation has been made. More awareness of this phase-wise development of integrated care, could facilitate integrated care coordinators and others to evaluate their integrated care practices and guide further development. The four phases model has the potential to serve as a generic quality management tool for multiple integrated care practices.

Traditional multiphase flow simulations often include less rigorous boundary condition assumptions, because flowline models are commonly isolated from both upstream well inflow and downstream processing facilities. Such an approach can be even more unrealistic if the flowline model network is complicated for example, where connected with subsea processing equipment. Within this kind of system, changes in fluid behavior are even more sensitive to overall operability. A full field integrated simulation, which includes well inflow, subsea equipment (XTs and manifolds), subsea processing, flowlines, and/or arriving facilities, offers a more realistic solution. This paper describes the application and value of performing full field integrated simulations throughout the life-cycle phases of field development. The solver used for the simulation provides a powerful tool to screen design alternatives to identify the optimal field solution in a cost efficient way at an early design phase. In the detailed design phase the dynamic simulations using the same full field model can be performed to ensure system operability. Similarly, in the life-of-field operation phase, the same full field model can be used to perform real time metering and monitoring as well as "look-ahead" forecasting as part of an advisory system. This is usually instrumental for a challenging field production. As the simulation model evolves since early design phase until the life-of-field operation, it promotes a comprehensive continuity. "One model one solution" provides an effective design and operation tool. Such a tool is able to provide a wide range of information that is relevant across multidisciplinary teams.

Multi-Agent Based Intelligent Tutoring System Source Code Generation Using MASITS ToolSeveral agent development tools have been proposed. At the same time, specific tools for agent based Intelligent Tutoring System (ITS) development do not exist. However, ITSs have some specific characteristics that must be taken into consideration during the development. General purpose Agent Oriented Software Engineering (AOSE) methodologies and therefore development tools do not sufficiently correspond to the characteristics of ITSs. Additionally, the general purpose AOSE methodologies and tools do not allow plugging in domain specific rules and diagrams. Thus, usage of knowledge gained in ITS research during the development process is limited. In the absence of general tools that allow plugging in knowledge from ITS research, a specific tool named MASITS has been developed. The tool supports a specific agent based ITS development methodology named MASITS which takes into consideration specific characteristics of ITSs and integrates knowledge from ITS research. The tool supports all phases of ITS development, starting from requirements analysis and ending with deployment. Requirements analysis and design phases are supported by appropriate diagram creation tools. Implementation is supported by source code generation from diagrams created during the design phase. JADE platform is used for agent implementation. Thus, Java classes for ontology, agents and behaviours are generated from the design diagrams. The paper includes a brief overview of diagrams used in the source code generation and detailed algorithms for source code generation from the diagrams.

Consistency between various phases of the software development process is an important aspect in software engineering. Without this aspect, software products may not satisfy users' needs. The cause of the inconsistency is that users' requirements may not be sufficiently reflected in software products. We consider this situation as a gap between the requirements and the products. We focus on the early phases of the software development, because we need to deal with the problem before the inconsistency in the early phases affects the later phases. KAOS has been attracting attentions and UML has been widely adopted, in the early phases, for requirements analysis and design respectively. However, the requirements analysis phase and the design phase are often practiced separately which may cause a gap between them. In this paper, we propose a systematic approach, to reduce the gap between the requirement analysis phase and the design phase, by generating UML class diagram and OCL constraints from the KAOS model. We propose transformation rules between operation models and class diagrams and rules for producing OCL constraints from the KAOS model. In addition, we carried out a case study to confirm the validity of this approach.

In the system architecture design phase, there may be flaws introduced by the access control design. The flaws make the system design vulnerable. Vulnerabilities that are not detected during the design phase will be taken to the subsequent phases of the system development. This reduces system security and leads to more repair cost. In order to detect the access control flaws in the design phase as early as possible, we propose the security analysis method using Architecture Analysis and Design Language (AADL). This method analyzes the access control policies between components. It can analyze and detect the access control flaws in the AADL architecture model. For describing the access control policies, vulnerability model annex is created. We use a case study, based on a module from an aircraft intelligent information system, to introduce the application of modeling and analysis methods.

Abstract: The purpose of this research is to develop teaching factory-based for Entrepreneurship Learning Model in Vocational High Schools. Furthermore, the model is named “TEFA-Entrepreneurship Model”. The type of research is research and development (R & D). The development process followed Plomp model development stage (1997: 5) which consists of five phases of development, namely: (1) preliminary investigation phase; (2) design phase; (3) realization/construction phase; (4) test, evaluation, revision phase; and (5) implementation phase. This research setting was in the Vocational High School in Makassar especially for Multimedia Program. The Subjects of the research were (1) principal, (b) Entrepreneurship Teachers, and (c) The 11th Grade Students of Multimedia Program. The early development of TEFA-Entrepreneurship Model has been validated by entrepreneurship experts and field practitioners, so this model is valid. The validity of the existing assessment has 5 indicators: (1) The principle of learning, (2) The Supporting Theory, (3) The Guidelines for the use of models, (4) Syntax Learning, and (5) Learning Outcomes Assessment Guidelines. The results of expert assessment and field practitioners (Vocational High School Teachers) against Entrepreneurship Model developed was valid and effective to be used in the Vocational High School.

Providing security to complex information system development is challenging because of complex network and ubiquitous system. Traditional mechanisms address security concerns during development or design phases that may lead to various loopholes or over-constrained system. The field of security engineering has emerged whereby security requirements are gathered along with other requirements during the initial phase of software development. However, dealing with security concerns during the initial phases of development is challenging because of design and code unavailability. The paper first represents the proposals for security requirements engineering based on different approaches such as use case approach, goal-oriented approach, and process-oriented approach. These methodologies are evaluated along various parameters such as security engineering activities covered, application domain and others. The in-depth analysis ends with a recent proposal for security engineering and list of unresolved issues that needs consideration. The outcome of the paper can be exploited to drive further research.

User engagement is often associated with successful information systems implementation, with this being particularly true in developing countries in the Global South. However, the term remains poorly understood with many seemingly conflicting definitions and the term “user engagement” has come to mean a variety of things in the literature. Also, it is unclear at what stage(s) of the design, development, implementation and use phase(s) that user engagement should apply to. This research examines the meaning of user engagement with the objective of bringing some level of clarity to suit the information communication technology for development (ICT4D) context. To this end, we propose an expanded definition of the term user engagement. The research also suggests what stages of the design, development, implementation and use phase of the technology this expanded definition of user engagement most usefully applies to by drawing lessons on user engagement in a variety of mobile health projects from the Global South. Qualitative methods of data analysis were used in collecting data which show that user engagement as applied to a specific phase of each of the projects was essential for the ongoing success of each project.

ITER Remote Maintenance System (IRMS) lifecycle management