Sciweavers

184 search results - page 6 / 37
» Software Requirements Negotiation: Some Lessons Learned
Sort
View
ICSE
2003
IEEE-ACM
14 years 7 months ago
Quantifying the Value of Architecture Design Decisions: Lessons from the Field
This paper outlines experiences with using economic criteria to make architecture design decisions. It briefly describes the CBAM (Cost Benefit Analysis Method) framework applied ...
Mike Moore, Rick Kazman, Mark Klein, Jai Asundi
AGILEDC
2007
IEEE
14 years 1 months ago
Agile Program Management: Lessons Learned from the VeriSign Managed Security Services Team
This report examines how the VeriSign Managed Security Services team (MSS) has successfully extended agile software development practices to deal with a complex, multi-product dev...
Peter Hodgkins, Luke Hohmann
ICRA
2005
IEEE
147views Robotics» more  ICRA 2005»
14 years 1 months ago
Mars Exploration Rover Operations with the Science Activity Planner
– The Science Activity Planner (SAP) is the primary science operations tool for the Mars Exploration Rover mission and NASA’s Software of the Year for 2004. SAP utilizes a vari...
Jeffrey S. Norris, Mark W. Powell, Marsette Vona, ...
ISCA
2007
IEEE
128views Hardware» more  ISCA 2007»
14 years 1 months ago
Performance and security lessons learned from virtualizing the alpha processor
Virtualization has become much more important throughout the computer industry both to improve security and to support multiple workloads on the same hardware with effective isola...
Paul A. Karger
CE
2007
102views more  CE 2007»
13 years 7 months ago
ICT and learning: Lessons from Australian classrooms
Research into Information and Communication Technologies (ICT) in schools is well into its third decade but there is still a pressing need to better understand how computer-based ...
Debra N. A. Hayes