The Board of Realtors Multiple Listing Service (MLS) system isn’t very large in terms of use cases and domain classes. In that respect, the functional requirements are simple and well understood. MLS needs a Web site with public access to the listings, and it also needs to allow agents and brokers to log in to the system to add and update listings. There is very little back-end administrative data maintenance required, except to add or update a real estate office or agent.

1. Compared to the Tradeshow application described in Chapter 1, how long might this project take, and which approach to the SDLC would be most appropriate?

2. If you use a predictive SDLC, how much time might each phase of the project take? How much overlap of phases might you plan for? Be specific about how you would overlap the phases.

3. If you use an adaptive SDLC, how many iterations might you plan to include? What use cases would you analyze, design, and implement in the first iteration? What use cases would you work on in the second iteration? In additional iterations? Think in terms of getting the core functionality implemented early and then building the supporting functionality.

4. Assume this project focused on Web access to the MLS. If you also plan to deploy a smartphone application for use by the public and by the agents and brokers, how might this affect your choice of the approach to the SDLC? What are the implications for including the smartphone application in the initial project versus having a separate project for wireless later?

5. Consider using incremental development to include the Web application and wireless support. Describe what would be included in the first and second deployments of the project. Take into consideration that you might want to work on some initial problem solving for requirements, design, and implementation of the wireless support at the same time you are working on the Web application.