2007
DOI: 10.1504/ijmr.2007.014730
|View full text |Cite
|
Sign up to set email alerts
|

Formalisation of product requirements: from natural language descriptions to formal specifications

Abstract: In engineering design, customers usually provide product requirements in the form of a natural language while computer-aided design systems may prefer more formal and structured specifications. In this paper, a formalisation process is proposed to transform product requirements from its natural language descriptions to a formal specification. The formal specification is based on the product environment and the formulation of design problem, which identifies the components included in a design problem in terms … Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
13
0

Year Published

2011
2011
2024
2024

Publication Types

Select...
7
1

Relationship

1
7

Authors

Journals

citations
Cited by 24 publications
(13 citation statements)
references
References 25 publications
(25 reference statements)
0
13
0
Order By: Relevance
“…Requirements define what stakeholders such as users, customers, suppliers, developers, and manufacturers need and how each is satisfied (Hull et al 2005). Thus, one of the initial steps in the design process is to correctly identify and specify the system's requirements because their use and proper maintenance is crucial to the success and efficiency to any design project (Chen et al 2007).…”
Section: Need For Managing Requirement Changementioning
confidence: 99%
See 1 more Smart Citation
“…Requirements define what stakeholders such as users, customers, suppliers, developers, and manufacturers need and how each is satisfied (Hull et al 2005). Thus, one of the initial steps in the design process is to correctly identify and specify the system's requirements because their use and proper maintenance is crucial to the success and efficiency to any design project (Chen et al 2007).…”
Section: Need For Managing Requirement Changementioning
confidence: 99%
“…Requirement changes introduce negative consequences such as increased complexity (Chen andZeng 2006, Palmer et al 2010), potential data loss , and cost and time wasted . A designer could save time and money if it were possible to make a quick, yet accurate, assessment about the overall effects of a design or requirement change before committing to implementing a change (Stahovich and Ollinger 2001).…”
Section: Requirements Changementioning
confidence: 99%
“…These requirements may range from the initial functional requirements to the detailed specifications [15]. Several classification schemes for requirements were proposed in literature (compare Bühne and Herrmann [16]).…”
Section: Research Activities Concerning Requirements Managementmentioning
confidence: 99%
“…Zeng and Chen [8][9][10][11][12] propose some concepts, which we have adapted for our model, such as defining a product in terms of the elements of its environment, the use of requirement categories based on the product's life stages, and mapping natural language to a standardized representation. However, they do not provide an implementation strategy for actually authoring a PDS.…”
Section: Literature Reviewmentioning
confidence: 99%