首页 | 本学科首页   官方微博 | 高级检索  
相似文献
 共查询到10条相似文献,搜索用时 156 毫秒
1.
Requirement development activities such as requirements analysis and modelling are well defined in software engineering. A model-based requirement development may result in significant improvements in engineering design. In current product development activities in this domain, not all requirements are consciously identified and modelled. This paper presents the checklist-oriented requirements analysis modelling (CORAMOD) approach. CORAMOD is a methodology for the use of model-based systems engineering for requirements analysis of complex products utilizing checklists, the simplest kind of rational design method. The model-based focuses the requirements analysis process on requirement modelling, whereas the checklist encourages a conscious and systematic approach to identify requirements. We illustrate the utility of CORAMOD artefacts by a comprehensive case study example and modelling with system modelling language (SysML). We suggest that visual accessibility of the SysML views facilitates the full participation of all stakeholders and enables the necessary dialogue and negotiation. The approach promotes tracing derived requirements to the customer need statement and enhances validation by model execution and simulation.  相似文献   

2.
From conceptual modelling to requirements engineering   总被引:1,自引:0,他引:1  
Conceptual modelling is situated in the broader view of information systems requirements engineering. Requirements Engineering (RE) explores the objectives of different stakeholders and the activities carried out by them to meet these objectives in order to derive purposeful system requirements and therefore lead to better quality systems, i.e., systems that meet the requirements of their users. Thus RE product models use concepts for modelling these instead of concepts like data, process, events, etc., used in conceptual models. Since the former are more stable than the latter, requirements engineering manages change better. The paper gives the rationale for extending traditional conceptual models and introduces some RE product models. Furthermore, in contrast to conceptual modelling, requirements engineering lays great stress on the engineering process employed. The paper introduces some RE process models and considers their effect on tool support. This revised version was published online in June 2006 with corrections to the Cover Date.  相似文献   

3.
Business process modelling focuses on the modelling of functional behaviour. In this article, we propose an extension for the business process modelling notation to express non-functional authorisations requirements in a process model to enable the collaboration between security experts and business analysts. To capture multi-level, role-based and Separation of Duty authorisation requirements, new model element attributes and authorisation artefacts are introduced. To enhance the usability of this approach, simple visual decorators are specified to ease the communication of requirements between various stakeholders. To provide an early validation of these authorisation requirements during the definition of a process model, formal semantics are applied to the process model and model-checking techniques are used to provide feedback. As a pragmatic proof-of-concepts, a first prototype implementation is briefly discussed.  相似文献   

4.
Specifications in Context: Stakeholders, Systems and Modelling of Conflict   总被引:1,自引:1,他引:0  
This paper looks from an ethnographic viewpoint at the case of two information systems in a multinational engineering consultancy. It proposes using the rich findings from ethnographic analysis during requirements discovery. The paper shows how context – organisational and social – can be taken into account during an information system development process. Socio-technical approaches are holistic in nature and provide opportunities to produce information systems utilising social science insights, computer science technical competence and psychological approaches. These approaches provide fact-finding methods that are appropriate to system participants’ and organisational stakeholders’ needs.  The paper recommends a method of modelling that results in a computerised information system data model that reflects the conflicting and competing data and multiple perspectives of participants and stakeholders, and that improves interactivity and conflict management.  相似文献   

5.
Business process models have become an effective way of examining business practices to identify areas for improvement. While common information gathering approaches are generally efficacious, they can be quite time consuming and have the risk of developing inaccuracies when information is forgotten or incorrectly interpreted by analysts. In this study, the potential of a role-playing approach to process elicitation and specification has been examined. This method allows stakeholders to enter a virtual world and role-play actions similarly to how they would in reality. As actions are completed, a model is automatically developed, removing the need for stakeholders to learn and understand a modelling grammar. An empirical investigation comparing both the modelling outputs and participant behaviour of this virtual world role-play elicitor with an S-BPM process modelling tool found that while the modelling approaches of the two groups varied greatly, the virtual world elicitor may not only improve both the number of individual process task steps remembered and the correctness of task ordering, but also provide a reduction in the time required for stakeholders to model a process view.  相似文献   

6.
Prognostic and health management (PHM) describes a set of capabilities that enable to detect anomalies, diagnose faults and predict remaining useful lifetime (RUL), leading to the effective and efficient maintenance and operation of assets such as aircraft. Prior research has considered the methodological factors of PHM system design, but typically, only one or a few aspects are addressed. For example, several studies address system engineering (SE) principles for application towards PHM design methodology, and a concept of requirements from a theoretical standpoint, while other papers present requirement specification and flow-down approaches for PHM systems. However, the state of the art lacks a systematic methodology that formulates all aspects of designing and comprehensively engineering a PHM system. Meanwhile, the process and specific implementation of capturing stakeholders’ expectations and requirements are usually lacking details. To overcome these drawbacks, this paper proposes a stakeholder-oriented design methodology for developing a PHM system from a systems engineering perspective, contributing to a consistent and reusable representation of the design. Further, it emphasizes the process and deployment of stakeholder expectations definition in detail, involving the steps of identifying stakeholders, capture their expectations/requirements, and stakeholder and requirement analysis. Two case studies illustrate the applicability of the proposed methodology. The proposed stakeholder-oriented design methodology enables the integration of the bespoke main tasks to design a PHM system, in which sufficient stakeholder involvement and consideration of their interests can lead to more precise and better design information. Moreover, the methodology comprehensively covers the aspects of traceability, consistency, and reusability to capture and define stakeholders and their expectations for a successful design.  相似文献   

7.
As software complexity grows and clients demand higher quality software, quality requirements can no longer be considered to be of secondary importance. Thus, eliciting, specifying, prioritizing and validating quality requirements is a prerequisite to the development of effective and efficient information systems. Despite the critical importance of quality requirements, there is a considerable gap in the breadth and depth of quality requirements engineering (RE) support in most RE approaches. In practice, it is often the case to have quality requirements considered as an afterthought in the systems development process. While there is a wealth of modelling techniques and tools for functional requirements, there is very limited support for quality requirements in RE. Support for quality requirements is usually ad‐hoc, without clear guidelines on how to capture, specify and manage quality requirements and also without proper usage of standardized terminologies based on established quality models such as the ISO/IEC 9126 quality model. In this paper, we discuss a quality‐driven RE framework and tool that applies knowledge management techniques and quality ontologies to support RE activities. The ontology implements the quality characteristics and metrics prescribed by the ISO/9126 quality model, providing a common vocabulary to address quality concerns/aspects across RE activities. We empirically validate how the framework and tool can be used to effectively support the requirements elicitation and prioritization activities through a case study addressing the development of an intranet portal project at the University of Manchester.  相似文献   

8.
Provoking creativity: imagine what your requirements could be like   总被引:1,自引:0,他引:1  
Requirements engineering isn't recognized as a creative process. However, as new systems and products emerge, stakeholders are increasingly creating and inventing ideas that they express as requirements. Requirements engineering, with its focus on elicitation, analysis, and management, has yet to fully grasp this trend. We applied techniques to encourage creative thinking during the requirements process for a software-based system in a naturally conservative domain - air traffic management (ATM). We applied unusual theories, such as analogical reasoning from cognitive science, to underpin the use of these techniques, and we report basic results and lessons learned. We focus on the creativity techniques we applied (see the sidebar) and demonstrate them with examples from the ATM domain.  相似文献   

9.
Scenario-based requirements analysis   总被引:1,自引:4,他引:1  
  相似文献   

10.
Workplace studies provide an important input to system development, yet there is no straightforward way of translating empirical results into requirements. This study contributes to the development of methods by reporting an activity theory based approach consisting of (i) field observations, (ii) modelling and (iii) a specific task analysis for system requirements. The research informed the further development of the Build-it system, a multi-user system designed to support co-located interaction between designers in engineering and architecture, and other stakeholders such as clients, operators, or inhabitants. The background research was conducted in four engineering companies and comprised of meeting observations, a questionnaire on design collaboration (n=94) and the analysis of 20 artefacts. The findings indicate that collaboration is of critical importance to the design process, and at least some of the tasks in engineering design could be supported by a system like Build-it. The task analysis for system requirements involved potential users from engineering but extended the scope to other domains, namely architecture and chemical process engineering (n=22). In all three domains a multi-user system like Build-it would be advantageous; however, the specific requirements varied more than expected. The study critically reflects on the use of generic concepts and the process of conducting research for the purpose of understanding work for design.  相似文献   

设为首页 | 免责声明 | 关于勤云 | 加入收藏

Copyright©北京勤云科技发展有限公司  京ICP备09084417号