Formal specifications are now being used as a basis for communication, design, testing and verification of a software product. For a formal specification to be used effectively, it must be valid, which means that it must be well-formed and reflects the user requirements. The normal technique for validating a formal specification is by using formal reasoning. However, the use of formal reasoning...

The goal of this paper is to discuss possibilities of inter-mixing formal and informal specification in order to guide and support the conceptual modeling process in software development. We sketch a framework which rests on an agentoriented methodology that provides a modeling language which allows for the definition of both informal and formal specification. We show how formal techniques can ...

Requirements specification activity in a human-readable and formal representation is crucial task while developing complex system. If the meaning of requirements description their fragments can be handled, Stakeholders produce more effective requirement specifications higher quality. To that end, an ontology developed to control capturing way. The proposed built using Protege tool. This paper f...

The accurate capture and representation of user requirements plays a critical role in the construction of effective and flexible information systems. However, despite the introduction of development methods and CASE tools in the project life-cycle, the process of developing a requirements specification remains problematical. This paper proposes that future development in CASE environments shoul...

introduction: since users have a critical role in the success of a hospital information system, and also considering software companies as information system service providers-not only product sellers, this study was conducted to evaluate the hospital information system (his) software based on user requirements in iran. methods: through a descriptive study, 5 vendors, which had the best selling...

In this paper, we present an approach to the object-oriented software development which is based on: i) automatic generation of a throwaway prototype from the initial specification in a formal, declarative, object-oriented specification language, ii) validation of user requirements and refinement of the specification by using this prototype, and iii) automatic translation from the validated spe...

The paper argues that the conventional methods for object oriented analysis and conceptual modeling suffer from lacks in requirements elicitation and validation by the end-user. Therefore, an intermediate level called ‘conceptual predesign’ is introduced between natural language requirements specification and conceptual design. The paper introduces the basic notions of a conceptual predesign mo...

This paper examines the use of Bayesian Networks to tackle one of the tougher problems in requirements engineering, translating user requirements into system requirements. The approach taken is to model domain knowledge as Bayesian Network fragments that are glued together to form a complete view of the domain specific system requirements. User requirements are introduced as evidence and the pr...