The project specification can be defined in word processor format as you would normally. By adding some special items, such as titled bulleted lists and highlighted text items, both a test suite and glossary can be written right into the spec. The Arbiter server will parse these documents and run the tests, reporting the results into the documents themselves. This allows the client to see project process.
Two powerful tools for communicating requirements from your customers, and testing those requirements, are Fitnesse and Selenium. Fitnesse, a wiki encapsulating the Framework for Integration Tests (aka FIT), enables customers to write sentence-like tests which can be mapped to the underlying system. Selenium drives a browser without all of the fragile mouse coordinate testing you get from a lot of testing tools (ala WinRunner).
XRules is an XML business rules language that expresses constraints, calculations, interdependencies, and properties that describe and exist among elements and attributes of an XML document. XRules can be used to validate business rules in an XML transaction, attach metadata to the XML Infoset, or add dynamism to XML by using the Dynamic DOM.
Beginning January 23, 2007, ALL persons, including U.S. citizens, traveling by air between the United States and Canada, Mexico, Central and South America, the Caribbean, and Bermuda will be required to present a valid passport, Air NEXUS card, or U.S. Co
The PLANdora project was born with the intent of to be a tool to help the software development process, since the customer requirement until the task conclusion, and consequently gather the "history" of project. The PLANdora system can be useful for teams that have problems with resource bottle-necks, parallel projects, critical dead lines, necessity for scope documentation of tasks and requirements, etc.
A cogent analysis of the underlying complexity of software engineering. Each problem is new; software is the most complex thing humans have ever built; it is impossible to measure complexity of something given that product. Software is fractal in complexity (really?)
I. Alexander. RE '02: Proceedings of the 10th Anniversary IEEE Joint International Conference on Requirements Engineering, Seite 61--70. Washington, DC, USA, IEEE Computer Society, (2002)
T. Alspaugh, D. Richardson, und T. Standish. 4th International Workshop on Scenarios and State Machines: Models, Algorithms and Tools (SCESM'05), Seite 1--5. St. Louis, MI, (Mai 2005)