[DL-Learner SVN] SF.net SVN: dl-learner:[4083] trunk/test/isle/swore

[<jen...@us...>]

Revision: 4083
          http://sourceforge.net/p/dl-learner/code/4083
Author:   jenslehmann
Date:     2013-09-05 08:20:31 +0000 (Thu, 05 Sep 2013)
Log Message:
-----------
updated SWORE test case

Modified Paths:
--------------
    trunk/test/isle/swore/corpus/requirements_management.txt

Added Paths:
-----------
    trunk/test/isle/swore/corpus/customer_requirement.txt
    trunk/test/isle/swore/corpus/requirement.txt
    trunk/test/isle/swore/corpus/requirements_analysis.txt

Property Changed:
----------------
    trunk/test/isle/swore/

Index: trunk/test/isle/swore
===================================================================
--- trunk/test/isle/swore	2013-09-05 08:03:11 UTC (rev 4082)
+++ trunk/test/isle/swore	2013-09-05 08:20:31 UTC (rev 4083)

Property changes on: trunk/test/isle/swore
___________________________________________________________________
Added: svn:ignore
## -0,0 +1 ##
+searchTree*.txt
Added: trunk/test/isle/swore/corpus/customer_requirement.txt
===================================================================
--- trunk/test/isle/swore/corpus/customer_requirement.txt	                        (rev 0)
+++ trunk/test/isle/swore/corpus/customer_requirement.txt	2013-09-05 08:20:31 UTC (rev 4083)
@@ -0,0 +1 @@
+A customer requirement is usually desired by at least one customer and usually specificed or captured via requirements engineering systems for later inspection by software developers and maintainers. The goal of involving customer in the requirements elicitation process is to improve the quality of the software (see also: requirements elicitation, open source software, E-Government).

Added: trunk/test/isle/swore/corpus/requirement.txt
===================================================================
--- trunk/test/isle/swore/corpus/requirement.txt	                        (rev 0)
+++ trunk/test/isle/swore/corpus/requirement.txt	2013-09-05 08:20:31 UTC (rev 4083)
@@ -0,0 +1 @@
+In product development and process optimization, a requirement is a singular documented physical and functional need that a particular design, product or process must be able to perform. It is most commonly used in a formal sense in systems engineering, software engineering, or enterprise engineering. It is a statement that identifies a necessary attribute, capability, characteristic, or quality of a system for it to have value and utility to a customer, organisation, internal user, or other stakeholder. A specification (often abbreviated as spec) may refer to an explicit set of requirements to be satisfied by a material, design, product, or service. In the classical engineering approach, sets of requirements are used as inputs into the design stages of product development. Requirements are also an important input into the verification process, since tests should trace back to specific requirements. Requirements show what elements and functions are necessary for the particular project. This is reflected in the waterfall model of the software life-cycle. However, when iterative methods of software development or agile methods are used, the system requirements are incrementally developed in parallel with design and implementation.

Added: trunk/test/isle/swore/corpus/requirements_analysis.txt
===================================================================
--- trunk/test/isle/swore/corpus/requirements_analysis.txt	                        (rev 0)
+++ trunk/test/isle/swore/corpus/requirements_analysis.txt	2013-09-05 08:20:31 UTC (rev 4083)
@@ -0,0 +1 @@
+Requirements analysis in systems engineering and software engineering, encompasses those tasks that go into determining the needs or conditions to meet for a new or altered product, taking account of the possibly conflicting requirements of the various stakeholders, analysing, documenting, validating and managing software or system requirements. Requirements analysis is critical to the success of a systems or software project. The requirements should be documented, actionable, measurable, testable, traceable, related to identified business needs or opportunities, and defined to a level of detail sufficient for system design.

Modified: trunk/test/isle/swore/corpus/requirements_management.txt
===================================================================
--- trunk/test/isle/swore/corpus/requirements_management.txt	2013-09-05 08:03:11 UTC (rev 4082)
+++ trunk/test/isle/swore/corpus/requirements_management.txt	2013-09-05 08:20:31 UTC (rev 4083)
@@ -0,0 +1 @@
+Requirements management is the process of documenting, analyzing, tracing, prioritizing and agreeing on requirements and then controlling change and communicating to relevant stakeholders. It is a continuous process throughout a project. A requirement is a capability to which a project outcome (product or service) should conform.

This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.