:
About
Join the RESG
Mailing List
Events
RQ Newsletter
RE Sources
Search & Map
Home
Contact Us
|
Past RESG Event
Tool Vendors' Challenge and AGM
Date Wednesday 20 July 2005
Venue Rooms A, B & C, Level 4, Drysdale Building, Northampton Square (location 2 on MAP) City University, London
Schedule
12:00 - Open Display
12:30 - Registration
13.00 - AGM (Pete Sawyer)
13:45 - Challenge Introduction (Ian Alexander)
14:00 - Presentation 1 MKS
14:30 - Presentation 2 Objectiver
15:00 - Presentation 3 Telelogic
15:30 - Presentation 4 IBM Rational
16:00 - Questions (mediated by David Bush)
16:30 - Open Display
17:30 - Close
The Challenge
After the (short) Annual General Meeting, each invited
Tool Vendor spoke on how their tool met the
following challenge:
You are acting as requirements management consultant to a client who wants to automate his existing multi-storey car park with time-stamped ticket-issuing machines, payment machines, closed-circuit television cameras to deter both theft and non-payment, and automatic barriers operated by validated (paid-up) tickets. The client's systems engineer has advised that the requirements should be organised into a list of stakeholders, a set of stakeholder requirements, a system specification, a project dictionary, and a list of references, with traces between these (the dictionary and references both receive traces from all the other documents; the specification traces to the requirements, which trace to the list of stakeholders). The requirements will certainly need to be prioritised, approved (or rejected), and then have their status tracked through to final acceptance of the automated car park.
Show (without spending time restating the problem) how your tool handles this challenge. Illustrate briefly the steps you would go through to structure the requirements, traces, priorities, and status in your tool.
You will have 30 minutes altogether, as a minimum we suggest that you address the following topics:
- setting up the information structure skeleton;
- importing the requirements from Word or text files;
- setting up the traceability;
- prioritising and approving the requirements;
- controlling and managing changes to the requirements;
- tracking the status of the requirements;
- checking the completeness of the traceability;
- producing and maintaining documentation;
At the end, and for no more than 5 minutes (of the 30!):
- present any features of your tools that relate these requirements activities to other systems engineering lifecycle activities.
The invited vendors were -
MKS
www.mks.com

MKS is the preeminent provider of enterprise technology management solutions for the global 1000. MKS’s solution spans the application lifecycle from requirements management, through application development, to server deployment providing customers with greater visibility over software development activities, enhanced development productivity and improved IT controls for regulatory compliance. MKS solutions are distinguished by their ease of implementation and low total cost of ownership. Founded in 1984, MKS serves more than 10,000 customers in countries across the world. Whether through deployment of MKS’s enterprise solutions strategically on an enterprise scale, or by leveraging individual components to solve project-level challenges, our customers can use MKS’s technology to better enable higher levels of process maturity, better manage global development activity and safeguard their most critical business applications and software assets.
Objectiver
www.objectiver.com

Objectiver is a Requirements Engineering methodology and tool. It helps users write complete, consistent and well structured requirements documents, starting from a "blank paper". The approach is model-based focusing on goals, requirements, obstacles and assigned responsibilities to achieve the requirements. Objectiver complies with the KAOS methodology, well-known in the scientific community.
Telelogic
www.telelogic.com
IBM Rational
www-306.ibm.com/software/awdtools/reqpro/

The IBM® Rational® RequisitePro® solution is a requirements and use case management tool for project teams who want to improve the communication of project goals, enhance collaborative development, reduce project risk and increase the quality of applications before deployment.
[Back]
|