Modeling the external software interface for requirements specification

Requirements specification is an important part of the software, indeed the system, development process. It is critical that this effort be started early. This work suggests an early model for software developers to incorporate a systems viewpoint in their process. This model is an attempt to formalize an approach that will include a systematic representation of essentials of the external interface for software that is embedded within a larger system. The model is useful for early analysis of the software system and environment for such things as consistency, completeness, and safety

An Experiment in Model Driven Architecture for e-Enterprise Systems

OMG's Model Driven Architecture demonstrates how a system's specification model can be used within the process of creating supporting software implementations. This article documents the findings of an experiment aimed at determining the extent to which this method of software engineering can be used within the domain of e-Enterprise systems

Software process modelling as relationships between tasks

Systematic formulation of software process models is currently a challenging problem in software engineering. We present an approach to define models covering the phases of specification, design, implementation and testing of software systems in the component programming framework, taking into account non-functional aspects of software (efficiency, etc.), automatic reusability of implementations in systems and also prototyping techniques involving both specifications and implementations. Our proposal relies on the identification of a catalogue of tasks that appear during these phases which satisfy some relationships concerning their order of execution. A software process model can be defined as the addition of more relationships over these tasks using a simple, modular process language. We have developed also a formal definition of correctness of a software development with respect to a software process model, based on the formulation of models as graphs.Peer ReviewedPostprint (published version

A Methodological Approach: Formal Specification Of Quality Attributes Modeling Approcahes In The Waterfall Process Model

The fields like Software Engineering (SE) and Human Computer Interaction (HCI) are considered dissimilar.. SE based process model mostly discuss modeling of functional requirement while the HCI based approaches are mostly concerned with the modeling of quality attributes. The quality attributes are mostly discussed during late phases of software development. The non-functional requirements as quality attributes can be integrated in software products by considering quality or non-functional modeling approaches during all of the phases of software engineering process model. The separation of SE and HCI concerns restricts formal specification of quality attributes during all of the phases of SE process model. The software systems or products are generally less user centered because SE process models can’t address formal specification of quality attributes in SE process models. In this research a methodology for the formal specification of approaches that model functional requirements and quality attribute during SE process model is proposed. The proposed methodology is based on waterfall SE process model. It can be utilized in design and development of users centered software products. Our proposed methodology also bridges gap between SE and HCI fields

Modeling the dialogue aspects of an information system.

In this paper we investigate techniques offered by current object-oriented development methods for the specification of the user-system dialogue aspect of a software system. Current development methods do not give very extensive guidelines on how to model this aspect and the available techniques need some refinement and elaboration to fit this particular task in the software specification process. The paper first compares a number of approaches. The common elements of these approaches are summarized and further developed into one comprehensive set of techniques that addresses the needs of functional requirements analysis.

Weighted Modal Transition Systems

Specification theories as a tool in model-driven development processes of component-based software systems have recently attracted a considerable attention. Current specification theories are however qualitative in nature, and therefore fragile in the sense that the inevitable approximation of systems by models, combined with the fundamental unpredictability of hardware platforms, makes it difficult to transfer conclusions about the behavior, based on models, to the actual system. Hence this approach is arguably unsuited for modern software systems. We propose here the first specification theory which allows to capture quantitative aspects during the refinement and implementation process, thus leveraging the problems of the qualitative setting. Our proposed quantitative specification framework uses weighted modal transition systems as a formal model of specifications. These are labeled transition systems with the additional feature that they can model optional behavior which may or may not be implemented by the system. Satisfaction and refinement is lifted from the well-known qualitative to our quantitative setting, by introducing a notion of distances between weighted modal transition systems. We show that quantitative versions of parallel composition as well as quotient (the dual to parallel composition) inherit the properties from the Boolean setting.Comment: Submitted to Formal Methods in System Desig

Embedding Requirements within the Model Driven Architecture

The Model Driven Architecture (MDA) brings benefits to software development, among them the potential for connecting software models with the business domain. This paper focuses on the upstream or Computation Independent Model (CIM) phase of the MDA. Our contention is that, whilst there are many models and notations available within the CIM Phase, those that are currently popular and supported by the Object Management Group (OMG), may not be the most useful notations for business analysts nor sufficient to fully support software requirements and specification. Therefore, with specific emphasis on the value of the Business Process Modelling Notation (BPMN) for business analysts, this paper provides an example of a typical CIM approach before describing an approach which incorporates specific requirements techniques. A framework extension to the MDA is then introduced; which embeds requirements and specification within the CIM, thus further enhancing the utility of MDA by providing a more complete method for business analysis

Operational specification for FCA using Z

We present an outline of a process by which operational software requirements specifications can be written for Formal Concept Analysis (FCA). The Z notation is used to specify the FCA model and the formal operations on it. We posit a novel approach whereby key features of Z and FCA can be integrated and put to work in contemporary software development, thus promoting operational specification as a useful application of conceptual structures.</p