A formalized object oriented user driven approach using business forms

Although object-orientation exhibits many promises, there exists many fundamental areas that need to be addressed. Two of these areas are the widespread acceptance of the object mindset, and interactive user involvement in the object oriented business system development process. First, the mindset must grow and be extended not only by the engineering industry but also by the ever expanding service industry. Second, effective, efficient, flexible user driven tools must be developed, in the form of development approaches to reduce the reliance on scarce human resources. In order to accomplish both areas, the technology user is the key element. This research in progress concentrates on the development of a formalized business form user-driven approach using an object oriented analysis view. The resulting analysis produces an initial conceptual object model that is used by the users and designers for further object analysis, object design, design evolution, and object oriented application domain identification

Reasoning of Competitive Non-Functional Requirements in Agent-Based Models

During the decision-making process in real-time competitive environments, there is a need to perform concurrent optimisation of multiple competitive objectives to select an optimal design decision for interdependent stakeholders. To handle such issues, this thesis successfully assimilates the goal-oriented requirements-engineering knowledge with analytical decision-making approaches to facilitate reasoning and analysis by encouraging stakeholders’ involvement. This leads to optimal decisions with domain knowledge improvement in the agent-based i*-goal model by balancing multiple conflicting non-functional requirements reciprocally

A model of electronic warfare systems acquisition and engineering for Saudi Arabia

A major activity within the systems engineering process is the requirements definition and analysis phase. In technical systems, planning this phase looks too technical for top management and too broad for the engineers specialized in narrow technical fields. This categorization (too technical/too broad) represents a gap between top management and specialized engineering. In Saudi Arabia, such a gap is believed to be very wide. The main objective of this research is to find a way to narrow this gap between management and engineering when planning government systems, especially in electronic warfare (EW) systems. A solution in this effort is to streamline the process of systems acquisition, with more focus on the requirements definition phase before signing the contract. An acquisition procedural model has been developed. This model is structured in five sequenced phases linked through decision points. The first phase focuses on a method to develop threat analysis reports and why such a deterrent capability is needed. Requirements engineering is the main activity within the second phase. In this phase, the concept of structuring systems and subsystems into objects is explored by applying object-oriented expert systems to probe requirements completeness, correctness, consistency, traceability, timeliness, and documentation. Skeletons of three object-oriented knowledge bases for a Planning Support for Communication System (PSCS) were developed using EW sub-fields as the domain objects. The other three model phases are invitation for presentation, request-for-proposal (RFP) package development, and source selection. Government and corporate engineers in Saudi Arabia have reviewed the model, and it has a strong potential of becoming a Saudi national standard. Data analysis attributes the model\u27s strength to its applicability in 1) structuring the task of systems acquisition and keeping a documentation profile; 2) increasing government agencies\u27 self-reliance when planning systems; and 3) facilitating the generation of sound requirements --Abstract, page iii

Development of a Systems Engineering Model of the Chemical Separations Process: Final Report

The whole chemical separation process is complex to the point that definitely requires certain level of systematic coordination. To perform smoothly and meet the target extraction rates among those processes, this research proposed a general-purpose systems engineering model. A general purposed systems engineering model, Transmutation Research Program System Engineering Model Project (TRPSEMPro), was developed based on the above design concept. The system model includes four main parts: System Manager, Model Integration, Study Plan, and Solution Viewer. TRPSEMPro can apply not only to chemical separation process, but also a general system model. Software engineering and Object Oriented Analysis and Design (OOA&D) play a critical role during our software development. Through the application of OOA&D, the user can define objects and concepts from our problem domain that is quantitatively described by Unified Modeling Language (UML). The logical software objects were created from the previous definition. Meanwhile, different design patterns were also applied during the detailed design phase. Finally, those designed components were implemented by using MicrosoftTM.Net, the most up-to-date object-oriented programming language framework from Microsoft. Currently, only the UREX process module is available and ready to be implemented. Since extraction modules can be developed from various agencies with different development concepts and programming conventions, an intermediate bridge or interpreter is generally required. The system connects the only available process, UREX and with the TRPSEMPro system model from the AMUSESimulator interface. The AMUSESimulator communicates with the calculation engine AMUSE macros designed for the UREX process. A user-friendly GUI in AMUSESimulator allows the user to efficiently define the UREX process – flowsheet, input streams, sections, and stages

Constraints: the Heart of Domain and Application Engineering in the Product Lines Engineering Strategy

International audienceDrawing from an analogy between features based Product Line (PL) models and Constraint Programming (CP), this paper explores the use of CP in the Domain Engineering and Application Engineering activities that are put in motion in a Product Line Engineering strategy. The start idea is simple: both CP and PL engineering deal with variables, and constraints that these variables must satisfy. Therefore, specifying a PL as a constraint program instead of a feature model, or another kind of PL formalism, carries out two important qualities of CP: expressiveness and direct automation. On the one hand, variables in CP can take values over boolean, integer, real or even complex domains (i.e., lists, arrays and trees) and not only boolean values as in most PL languages such as the Feature-Oriented Domain Analysis (FODA). Specifying boolean, arithmetic, symbolic and reified constraint, provides a power of expression that spans beyond that provided by the boolean dependencies in FODA models. On the other hand, PL models expressed as constraint programs can directly be executed and analyzed by off-the-shelf solvers. Starting with a working example, this paper explores the issues of (a) how to specify a PL model using CP, including in the presence of multi-model representation, (b) how to verify PL specifications, (c) how to specify configuration requirements and (d) how to support the product configuration activity. Tests performed on a benchmark of 50 PL models show that the approach is efficient and scales up easily to very large and complex PL specification

Reuse oriented approach for reliable software product / Maziah Abdul Hamid

Software reuse oriented approach is an approach where the reuse of component in software development phases such as coding, people, and architecture. In order to implement reuse in an organization, many challenges must be face by the developer. Then, managing support is also one of the important things in implementing reuse. It is because; they are the one who giving cost to develop reuse. The objectives of this paper is to identify benefit using reuse oriented approach in an organization and to proposed architecture of the reuse oriented approach. Then, the findings gathered from the research is, the benefits that the most organization experience is shorten software development project and reduce cost of software development project. Then, the architecture proposed in this paper is called Reuse Engineering Life Cycle. It is based on the waterfall model, but in order to incorporate reuse, reuse repository, domain analysis and domain model are added. Furthermore, for formal reuse oriented approach, management support is vital, as well as the management of the reuse repository and the research on the reuse component being made by expert in domain analysis

Microgrid system design based on model based systems engineering: the case study in the Amazon region / Projeto de sistemas de microrredes baseado em engenharia de sistemas baseado em modelos: um estudo de caso na região Amazônica

Microgrid is a technically and economically viable opportunity to meet the demands of populations that, for various reasons, do not have access to electricity. The complexity of Smart Grid (SG) systems requires considerable engineering effort in the design process.  Designing this type of complex system requires new approaches, methods, concepts and engineering tools. Where, requirements analysis plays a major role in better characterizing, understanding and specifying the domain of application that SG systems should solve. This work presents a systemic proposal based specifically on System Systems (SoS) which anticipates the formalization of requirements, aiming to understand, analyze and design SG within the scope of Model Based Systems Engineering (MBSE). The definition of a microgrid from the SoS perspective is presented in order to provide a complete view of its life cycle. Requirements would be represented in an Objective Oriented Requirements Engineering (GORE) approach, specifically using visual diagrams based on the Keep All Objectives Satisfied (KAOS) method, where network operation and control will be formally represented. A case study for small communities in the equatorial Amazon Forest is used as a case study for the proposed method