The Case Study


We can meet another objective in this book by developing a case study we can track from requirements start to requirements finish. In this way, we will be able to not only apply the techniques that we are about to discuss to our example but also provide example work products or artifacts (to further illustrate key points and to serve as examples for your own projects). Appendix A of this book provides a sample set of artifacts from the case study.

Background for the Case Study

Lumenations, Ltd. has been a worldwide supplier of commercial lighting systems for use in professional theater and amateur stage productions for more than 40 years . In 2001, its annual revenues peaked at approximately $120 million, and sales are flattening. Lumenations is a public company and the lack of growth in sales ”no, worse , the lack of any reasonable prospect for improving growth in sales ”is taking its toll on the company and its shareholders. The last annual meeting was quite uncomfortable, as there was little new to report about the company's prospects for growth. The stock climbed briefly to $25 per share last spring on a spate of new orders but has since crept back down to around $15.

The theater equipment industry as a whole is flat with little new development. The industry is mature and already well consolidated. Since Lumenations' stock is in the tank and its capitalization is only modest, acquisition is not an option for the company.

What's needed is a new marketplace , one not too remote from what the company does best but in which there is substantial opportunity for growth in revenue and profits. After completing a thorough market research project and spending many dollars on marketing consultants , the company has decided to enter a new market: lighting automation for high-end residential systems . This market is apparently growing at 25 percent to 35 percent each year. Even better, the market is immature, and none of the established players has a dominant market position. Lumenations' strong worldwide distribution channel will be a real asset in the marketplace, and the distributors are hungry for new products. Looks like a great opportunity!

The HOLIS Software Development Team

The project we choose will be the development of HOLIS, our code name for an innovative new HOme LIghting automation System to be marketed by Lumenations. The HOLIS team is typical in its size and scope. For the purposes of our case study, we've made it a fairly small team, composed of only 15 team members , but it's large enough to have all the necessary skills fairly well represented by individuals with some degree of specialization in their roles. Also, it's the structure of the team that's most important, and by adding more developers and testers, the structure of the HOLIS team scales well to a size of 30 “50 people and commensurately larger software applications than HOLIS will require.

To address the new marketplace, Lumenations has set up a new division, the Home Lighting Automation Division. Since the division and technology are mostly new to Lumenations, the HOLIS team has been assembled mostly from new hires, although a few team members have been transferred from the Commercial Lighting Division.

Figure 4-1 is an organization chart of the development team and the relationships among those team members. We'll revisit this team periodically throughout the book and see how it applies its new skills to the requirements challenge for HOLIS.

Figure 4-1. The HOLIS software development team



Managing Software Requirements[c] A Use Case Approach
Managing Software Requirements[c] A Use Case Approach
ISBN: 032112247X
Year: 2003
Pages: 257 © 2008-2017.
If you may any questions please contact us: