Caso Navit

CASE STUDY REQM Directions When reading this case study, focus on the activities related to eliciting, verifying, and validating the requirements for a software project. Note how the software project managers handle requests to change the requirements. Identify issues associated with identifying and selecting the appropriate functional requirements and software quality attributes. Case SummaryDescription NavIT specializes in navigational systems for the DoD. NavIT wants to leverage its global positioning system (GPS) technology and software assets in the commercial marketplace. Management has proposed a joint venture with Signals & Systems (S&S), a company that develops radio frequency identification (RFID) tracking systems for the shipping industry. The joint venture involves thedevelopment of a GPS-RFID system to enable the secure and reliable location and tracking of packages, containers, or other goods being transported. S&S has identified target customers who are excited about the product idea and are interested in field-testing the first version of the product. The predicted time to market for this product is 18 months. Software will be a primary component of the newproduct. Case Study Objectives After reading the case study, you will be able to do the following: Understand the importance of the following decisions in eliciting the requirements:         Which software quality attributes are important to the business needs and goals of the client or customer? How can requirements regarding software quality attributes be verified and validated? When and whyshould the evolution of the software be thought about and planned when establishing the requirements? What risks are associated with the decisions made about the requirements, and how should they be handled?

Identify the activities by which the organization elicited, verified, and validated the requirements. Identify the approach that the software project managers used to handle requests tochange the requirements. •Explain the problems that occurred in the case scenario, the causes of the problems, and ways to reduce the likelihood that similar problems will occur in other software projects. Relate these to the decisions faced by project stakeholders.

Terminology DoD: Department of Defense. Geographical Information System (GIS): Computer-based systems that are used to store andmanipulate geographic information. Geographical Navigational Satellite System (GNSS): A satellite system that is used to pinpoint the geographic location of a user’s receiver anywhere in the world. Two GNSS systems are currently operational: the United States’ Global Positioning System (GPS) and the Russian Federation’s Global Orbiting Navigation Satellite System (GLONASS). A third, Europe’s Galileo,is due to be fully operational in 2013. Each of the GNSS systems employs a constellation of orbiting satellites working in conjunction with a network of ground stations Global Positioning System (GPS): A “constellation” of at least 24 well-spaced satellites that orbit Earth and make it possible for GPS receivers to determine their geographic location, direction, and time. The location accuracy isanywhere from 100 to 15 meters for most equipment. Accuracy can be pinpointed to within one meter with special military-approved equipment Radio Frequency Identification (RFID): A method of identifying unique items using radio waves. Typically, a reading device communicates with a tag, which holds digital information in a microchip Selective availability (SA): A DoD program that controls theaccuracy of pseudorange measurements, degrading the signal available to nonqualified receivers by dithering the time and ephemeris data provided in the navigation message. The United States removed SA on May 1, 2000, and currently has the capability to reintroduce the feature Software quality: The degree to which the software exhibits a desired combination of attributes (IEEE Std. 1061-1998; ISO/IEC...