Pine Valley Furniture WebStore: Determining System Requirements

Rating - NAN/5

Pine Valley Furniture WebStore: Determining System Requirements

In the last chapter, you read how Pine Valley Furniture’s management began the WebStore project—to sell furniture products over the Internet. Here we examine the process followed by PVF to determine system requirements and highlight some of the issues and capabilities that you may want to consider when developing your own Internet-based application. To collect system requirements as quickly as possible, Jim Woo and Jackie Judson decided to hold a three-day JAD session. In order to get the most out of these sessions, they invited a broad range of people, including representatives from sales and marketing, operations, and information systems. Additionally, they asked an experienced JAD facilitator, Cheri Morris, to conduct the session. Together with Cheri, Jim and Jackie developed an ambitious and detailed agenda for the session. Their goal was to collect requirements on the following items:

  • System layout and navigation characteristics
  • WebStore and site management system capabilities
  • Customer and inventory information
  • System prototype evolution 

In the remainder of this section, we briefly highlight the outcomes of the JAD session.

System Layout and Navigation Characteristics

As part of the process of preparing for the JAD session, all participants were asked to visit several established retail Web sites, including,,, and At the JAD session, participants were asked to identify characteristics of these sites that they found

These Topics Are Also In Your Syllabus
1 Representing and Scheduling Project Plans link
2 Representing Project Plans-Representing and Scheduling Project Plans link
You May Find Something Very Interesting Here. link
3 Calculating Expected Time Durations Using PERT-Representing and Scheduling Project Plans link
4 Constructing a Gantt Chart and Network Diagram at Pine Valley Furniture-Representing and Scheduling Project Plans link
5 Using Project Management Software link

TABLE 5-6: Desired Layout and Navigation Feature of WebStore

appealing and those they found cumbersome; this allowed participants to identify and discuss those features that they wanted the WebStore to possess. The outcomes of this activity are summarized in Table 5-6.

WebStore and Site Management System Capabilities

After agreeing to the general layout and navigational characteristics of the WebStore, the session then turned its focus to the basic system capabilities. To assist in this process, systems analysts from the information systems department developed a draft skeleton of the WebStore based on the types of screens and capabilities of popular retail Web sites. For example, many retail Web sites have a “shopping cart” feature that allows customers to accumulate multiple items before checking out rather than buying a single item at a time. After some discussion, the participants agreed that the system structure shown in Table 5-7 would form the foundation for the WebStore system.

These Topics Are Also In Your Syllabus
1 Security link
2 Scalability link
You May Find Something Very Interesting Here. link
3 Failure handling link
4 Concurrency link
5 Transparency link

TABLE 5-7: System Structure of the WebStore and Site Management Systems

In addition to the WebStore capabilities, members of the sales and marketing department described several reports that would be necessary to manage customer accounts and sales transactions effectively. In addition, the department wants to be able to conduct detailed analyses of site visitors, sales tracking, and so on. Members of the operations department expressed a need to update the product catalog easily. These collective requests and activities were organized into a system design structure called the Site Management system, summarized in Table 5-7. The structures of both the WebStore and Site Management systems will be given to the information systems department as the baseline for further analysis and design activities.

Customer and Inventory Information

The WebStore will be designed to support the furniture purchases of three distinct types of customers:

These Topics Are Also In Your Syllabus
1 Pervasive networking and the modern Internet link
2 Mobile and ubiquitous computing link
You May Find Something Very Interesting Here. link
3 Distributed multimedia systems link
4 Distributed computing as a utility link
5 Focus on resource sharing link
  • Corporate customers
  • Home-office customers
  • Student customers

To track the sales to these different types of customers effectively, the system must capture and store distinct information. Table 5-8 summarizes this information for each customer type identified during the JAD session. Orders reflect the range of product information that must be specified to execute a sales transaction. Thus, in addition to capturing the customer information, product and sales data must also be captured and stored; Table 5-8 lists the results of this analysis.

System Prototype Evolution

As a final activity, the JAD participants discussed, along with extensive input from the information systems staff, how the system implementation should evolve. After completing analysis and design activities, they agreed that the system implementation should progress in three main stages so that requirement changes could be more easily identified and implemented. Table 5-9 summarizes these stages and the functionality incorporated at each one. At the conclusion of the JAD session, all the participants felt good about the progress that had been made and about the clear requirements that had been identified. With these requirements in hand, Jim and the information systems staff could begin to turn these lists of requirements into formal analysis and

TABLE 5-8: Customer and Inventory Information for WebStore

These Topics Are Also In Your Syllabus
1 Openness link
2 Security link
You May Find Something Very Interesting Here. link
3 Scalability link
4 Failure handling link
5 Concurrency link

TABLE 5-9 Stages of System Implementation of WebStore

design specifications. To show how information flows through the WebStore, Jim and his staff will produce data-flow diagrams (Chapter 6). To show a conceptual model of the data used within the WebStore, they will generate an entity-relationship diagram (Chapter 7). Both of these analysis documents will become the foundation for detailed system design and implementation. As we saw in Chapter 1, the systems analysis phase of the systems development life cycle includes determining requirements and structuring requirements. Chapter 5 focuses on requirements determination, the gathering of information about current systems, and the need for replacement systems. Chapters 6 and 7 address techniques for structuring the information discovered during requirements determination.



These Topics Are Also In Your Syllabus
1 The Process of Identifying and Selecting Information Systems Development Projects-Identifying and Selecting Projects link
2 Initiating and Planning Systems Development Projects link
You May Find Something Very Interesting Here. link
3 Assessing Project Feasibility link
4 Building the Baseline Project Plan link
5 Reviewing the Baseline Project Plan link


Rating - NAN/5

Rating - NAN/5