共查询到20条相似文献,搜索用时 15 毫秒
1.
Requirements analysis is an important phase in a software project. The analysis is often performed in an informal way by specialists who review documents looking for ambiguities, technical inconsistencies and incomplete parts. Automation is still far from being applied in requirements analyses, above all since natural languages are informal and thus difficult to treat automatically. There are only a few tools that can analyse texts. One of them, called QuARS, was developed by the Istituto di Scienza e Tecnologie dell'Informazione and can analyse texts in terms of ambiguity. This paper describes how QuARS was used in a formal empirical experiment to assess the impact in terms of effectiveness and efficacy of the automation in the requirements review process of a software company. 相似文献
2.
Software Requirements Specifications (SRS) have been used to fill the communication gap between systems analysts and the end-users. SRSs should satisfy the needs of both systems analysts and end-users. Non-technical end-users require intelligible SRSs while systems analysts need more precise, clear and concise SRSs. Object-oriented methods cannot represent temporal relations between events precisely. However, object-oriented principles are widely used in systems analysis and designing. Hence, there is a need for a software requirements specification language which supports object-oriented analysis methods, represents temporal knowledge precisely and whose representation scheme resembles natural languages. The specification language presented in this paper, GSL, is designed to meet the above requirements. The language is based on First-order Temporal Logic (FTL), which has temporal operators in addition to classical logical connectives and quantifiers. Since FTL cannot represent relative temporal knowledge and it inherits problems with point-based time models, a new logical connective TAND and redefined AND connective are used to represent relative temporal knowledge and to solve the problems with FTL. The language employs object-oriented principles: events, conditions, rules and activities can be represented as objects as well as attributes of an object. However, systems analysts can decide whether to use object-oriented conceptual modeling or not. © 1998 John Wiley & Sons, Ltd. 相似文献
3.
软件需求规格说明自动生成工具 总被引:1,自引:0,他引:1
首先提出了一种面向业务流的需求分析方法,并给出了相应的条件有向图需求描述模型(CDGRD),然后详细地介绍了基于CDGRD的软件需求规格说明自动生成工具,最后以某大型企业信息系统项目为例,详细讨论了CD-GRD描述方法以及该自动生成工具的具体应用. 相似文献
4.
从需求波动风险的定义出发,总结了需求波动形成的原因和对软件项目的影响,列举了一些代表性的风险分析和评估方法。最后提出了基于面向对象方法的系统需求工程的分析设计思路。 相似文献
5.
Jane Hesketh David Robertson Norbert Fuchs Alan Bundy 《Automated Software Engineering》1998,5(2):183-210
Formal design supported by automated reasoning can help keep track of requirements—a particular problem for large, detailed systems. Designers of system specifications are often constrained by codes of practice and must show not only that these have been observed but also demonstrate how that has been achieved. This is especially important in safety-critical systems where sections of the requirements will be regulations or guidelines. Using a lightweight approach, where formal proofs are used to support rather than guarantee adherence to requirements, we have developed an interactive system for formalising and managing information in codes of practice from the offshore oil industry. As a design proceeds, relevant requirements are found automatically and checked before being notified to the designer with an accompanying explanation of whether or not they are currently satisfied. Progress in satisfying requirements is monitored automatically and contributing choices are recorded. Such evidence of adherence to guidelines may be useful in checking the validity of the design. It may also provide useful reference material during subsequent system modification by drawing attention to the implications that changes will have on key parts of the codes of practice. 相似文献
6.
N. A. M. Maiden 《Information and Software Technology》1991,33(10):780-790
Analogy is proposed as an alternative paradigm for the reuse of specifications during requirements analysis. First, critical determinants of analogies between software engineering problems are discussed in relation to a specification retrieval mechanism. Second, the process of specification reuse is examined. Specification reuse by analogy is knowledge-intensive, hence an important role is proposed for the analyst during specification reuse: analyst involvement would appear necessary to categorize a new problem, select between candidate reusable specifications, and customize the selected specification to the new domain. Finally, a specification reuse tool is proposed that recognises the collaborative nature of reuse by analogy. This tool assists and advises the analyst during reuse founded on cognitive models of analyst behaviour during analogous reasoning and reuse. The prototype version of this intelligent reuse advisor (Ira) is outlined. 相似文献
7.
原型化方法是需求检测中的重要方法之一。文章基于面向嵌入式实时系统的需求描述模型RTRSM,给出了一种嵌入式实时系统的原型化检测方法,同时将这种方法与组件库相结合,动态调用组件,从而提高原型化检测方法的可用性和效率。 相似文献
8.
Specifying and analyzing early requirements in Tropos 总被引:2,自引:1,他引:2
We present a framework that supports the formal verification of early requirements specifications. The framework is based on Formal Tropos, a specification language that adopts primitive concepts for modeling early requirements (such as actor, goal, and strategic dependency), along with a rich temporal specification language. We show how existing formal analysis techniques, and in particular model checking, can be adapted for the automatic verification of Formal Tropos specifications. These techniques have been implemented in a tool, called the T-Tool, that maps Formal Tropos specifications into a language that can be handled by the NuSMV model checker. Finally, we evaluate our methodology on a course-exam management case study. Our experiments show that formal analysis reveals gaps and inconsistencies in early requirements specifications that are by no means trivial to discover without the help of formal analysis tools.
相似文献
Marco RoveriEmail: |
9.
The purpose of a requirement expression is to transform the needs of various entities into a formal language such that the intent is clearly understood by all involved. Although many sources provide definitions of the terms associated with a requirement expression, few contain guidance as to the process of developing a requirement, there are only occasional agreements on common definitions, and the defined terms are too narrowly focused to be useful across the full requirements engineering domain. This paper develops a cohesive set of definitions of the terms associated with a requirement expression. First, a framework for the transformation of needs into requirements is discussed and existing definitions are presented from the major relevant sources. These definitions are then analyzed and an integrated set of definitions is developed for the key terms associated with a requirements expression: entity; need; requirement expression; requirement statement; characteristics of a well-formed requirement statement and a well-formed set of requirements; and requirement attributes that, along with the requirement statement itself, comprise a well-formed requirement expression. 相似文献
10.
软件需求描述和需求分析建模一直以来是需求工程的重要工作;且存在紧密的关联;自动化需求分析建模与验证需要以规范的需求描述为基础。提出基于领域需求的结构化描述的自动分析建模方法;通过对系统整体按照一定的组织结构进行描述;描述句式采用富含语义的句型和普通句型相结合的方式;运用自然语言处理相关技术;通过预定义的转换规则对结构化描述下的需求文本进行建模元素识别;实现自动化的建模;最终生成UML图形化分析结果。 相似文献
11.
问题驱动的需求捕获方法广泛应用于需求获取.然而,利益相关者通常难以找到真实的、一致的问题解决方案并清晰地表达出来.协同式的问题分析与解决方法可以帮助利益相关者找到并表达出真实、一致的解决方案.方法的基本思想是:首先各个利益相关者平等地、按照一定流程协同地分析问题表述的可理解性、问题的价值、问题存在原因;然后利益相关者协同地识别解决方案.通过关联原因和解决方案来保证解决方案的客观性.通过问题的分类,提出问题及协同元素的元模型,及时关注相关联的问题,评估利益相关者的参与程度,用以帮助利益相关者分析与解决问题.选取“高校学生选课系统”进行实例研究,结果显示协同式问题分析与解决是一种在实际应用中行之有效的方法. 相似文献
12.
Leonard Elizabeth I. Heitmeyer Constance L. 《Higher-Order and Symbolic Computation》2003,16(1-2):63-92
Formal specifications of software systems are extremely useful because they can be rigorously analyzed, verified, and validated, giving high confidence that the specification captures the desired behavior. To transfer this confidence to the actual source code implementation, a formal link is needed between the specification and the implementation. Generating the implementation directly from the specification provides one such link. A program transformation system such as Paige's APTS can be useful in developing a source code generator. This paper describes a case study in which APTS was used to produce code generators that construct C source code from a requirements specification in the SCR (Software Cost Reduction) tabular notation. In the study, two different code generation strategies were explored. The first strategy uses rewrite rules to transform the parse tree of an SCR specification into a parse tree for the corresponding C code. The second strategy associates a relation with each node of the specification parse tree. Each member of this relation acts as an attribute, holding the C code corresponding to the tree at the associated node; the root of the tree has the entire C program as its member of the relation. This paper describes the two code generators supported by APTS, how each was used to synthesize code for two example SCR requirements specifications, and what was learned about APTS from these implementations. 相似文献
13.
14.
需求的不确定性和易变性一直是影响软件生命周期,困扰软件开发效率和开发质量的重要因素。通过对动力系统和软件复杂性理论的研究,提出了一种混沌演化模型,该模型可以对软件需求的演化过程进行指导,同时也可以评价需求过程的质量。研究表明,只要需求演化过程的变化图和模型的轨迹图一致,那么需求的演化过程就可以看成是正常的。通过对具体实例的分析,进一步说明了该模型在评价需求演化过程上是有效可行的。 相似文献
15.
16.
郑跃斌 《计算机工程与应用》2003,39(26):215-217
企业流程是指为完成企业战略目标而进行的一系列逻辑相关的活动的有序集合,是企业经营活动的表现形式,也是现代信息系统建立的基础。然而传统的需求分析技术并没有体现出企业流程这一概念。论文在分析企业流程特点的基础上,建立了基于企业流程的需求分析方法的图形描述机制,重点叙述了企业流程建模的方法。 相似文献
17.
一种需求变更影响分析方法 总被引:1,自引:0,他引:1
需求变化的影响分析通过对其影响进行评估,为软件开发者和管理者提供有效的信息,这项工作在软件开发过程中有重要的意义.面向方面文档驱动需求工程从文本需求出发,提供了基于关注点及其关系的需求模块化、横切关注点判定及生成形式化需求文档等过程和方法.在面向方面文档驱动需求工程方法框架下,给出了一种需求影响分析方法,该方法基于矩阵确定关注点和变量之间的内部联系,应用可达矩阵计算界定关注点和变量的影响范围,定量计算关注点和变量相互之间影响程度,并通过实例分析验证了新方法的有效性. 相似文献
18.
需求分析与获取的方法学与技术 总被引:3,自引:0,他引:3
本文给出需求工程的一般框架,在对需求分类的基础上主要讨论非功能性(即非行为性)需求,提出对软件需求规范和分析技术的要求,并强调对现有相关工作评价的其中两个方面。 相似文献
19.
Systems being developed today make extensive and complex use of advanced technology. Many, if not most, of these systems are being produced but are not used or useful on delivery because the wrong problem was solved. A major cause for this shortfall in system development is due to changes in the operational environment of the intended system while the development process is ongoing. Significant sections of the literature discuss the need to get stakeholders involved earlier in the development process to correct this problem. However, no one has developed a detailed framework that accomplishes this intent. This paper defines a method involving a four‐step sequence that validates the entire system design process early and continuously to ensure that the right problem is being solved. The method is called Continuous Early Validation (CEaVa). It is a method that increases the likelihood of producing the correct system. The method develops visibility of potential disconnects among stakeholders' needs, original written requirements, organizational policy, and derived requirements. The CEaVa method validates the external and internal consistency of the problem statement. Additionally, CEaVa facilitates consensus on trade offs and priorities, resolving the potential disconnects with decision analytical reasoning for trade‐off analysis. The CEaVa method improves the development process and ultimately the system itself by increasing the likelihood of building the right system within budget and schedule. © 2002 Wiley Periodicals, Inc. Syst Eng 5: 223–241, 2002 相似文献
20.
GlobalSoftware Engineering implies a paradigm shift towards globally‐distributed development that can be advantageous, but at the cost of having to address the specific challenges that arise when the stakeholders are not colocated. Reusing assets during the initial processes of the software development life cycle could be beneficial, but automated support is essential if the expected benefits of requirements reuse are to be actually obtained. The main contribution of this paper is the specification of a collection of software features for a tool support for distributed, catalogue‐based natural‐language requirements reuse. Two additional contributions are also made: (1) an implementation of the requirements specifications previously mentioned using Drupal, a Content Management System; and (2) an empirical assessment of this tool support using distributed university students as subjects (n =57). According to our findings, the tool helps in making requirements reuse better than requirements specification from scratch and in managing traceability, is easy to use, useful, and easy to learn. In contrast, the tool is not particularly suitable for managing users and user roles. 相似文献