[CSUSB]>> [CNS]>> [CSE]>> [R J Botting]>> biba.php
Bibliographic Item (1.0)
- Mathias Weber & Joachim Weisbrod
- Requirements Engineering in Automotive Development: Experiences and Challenges
- IEEE Software Magazine V20n1(Jan/Feb 2003)pp16-24
- =EXPERIENCE REQUIREMENTS TOOLS PROCESS DaimlerChrysler
- DOORS::="Dynamic Object Oriented Requirements System",
[ index.cfm ]
(was Telelogic, now IBM).
- RequisitePro::= See http://www.rational.com/products/reqpro.
- RTM::="Requirements Traceability and Management",
[ http://www.chipware.com/ ]
- Complex domains have complex requirements.
- Requirements are more than text. Text+data(state, ...) +graphics... +metadata.
- Engineers and customers live in a document-driven world that has to be reflected in tools.
- Need to distinguish what the customer wants(Laastenheft) from what the supplier is contracted to do(Pflichtenheft).
- Redundancy causes problems but is built in to the existing system.
- Good engineers are already content specialists in their special area and the content tends to evolve incrementally, so it pays to recycle old specifications.
- Takes time to migrate documents into a new requirements database.
- Details only appear at the leaves of the tree.
- Nonfunctional requirements, acceptance criteria and tests are not done well.
- Change is part of project life. Be ready to handle a lot of it.
- User-adaptable views help guide and manage a process.
- Specification reviews are important.
- Traceability is good: but what should be traced?
- Bad couplings between tools and text.
- We need better tools to manage requirements.
- Most of the problems are in areas that are not being researched. The real problem is managing the complexity not in expressing content and domain knowledge.
Search for bibliographic items containing a matching string.
Search for a specific bibliographic item by name.
To see the complete bibliography (1Mb+) select:[Bibliography]