By Topic

Keynote talk 4: Automated understanding of video object events in a distributed smart camera network

Sign In

Cookies must be enabled to login.After enabling cookies , please use refresh or reload or ctrl+f5 on the browser for the login options.

Formats Non-Member Member
$33 $13
Learn how you can qualify for the best price for this item!
Become an IEEE Member or Subscribe to
IEEE Xplore for exclusive pricing!
close button

puzzle piece

IEEE membership options for an individual and IEEE Xplore subscriptions for an organization offer the most affordable access to essential journal articles, conference papers, standards, eBooks, and eLearning courses.

Learn more about:

IEEE membership

IEEE Xplore subscriptions

1 Author(s)
Jenq-Neng Hwang ; University of Washington, Seattle, United States

Summary form only given. You may think that your requirements engineering process is fairly limited and currently not too complex to manage. Or you may be right in the middle of a storm of requirements where it is impossible to manage even the most important ones comprehensively. If you are in the former situation, it may be dangerous to relax as many successful software-intensive products have a tendency to grow very rapidly in size and complexity, and sooner than you might think you may be hit by a massive flood of feature requests and too few resources to prevent the flood from drowning your development organization, which in turn put your future innovation capability and competitiveness at risk.

Published in:

Advanced Technologies for Communications (ATC), 2011 International Conference on

Date of Conference:

2-4 Aug. 2011