Pine Valley Furniture WebStore: Determining System Requirements




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

Topics You May Be Interested In
Difference Between Manual And Automated System - Manual System Vs Automated System Heterogeneity
Systems Models Types Of Models - Systems Environment And Boundaries Security
Qualifications And Responsibilities Of System Analyst Architectural Patterns
Types Of Feasibility Studies And Feasibility Reports Establishing A Project Starting Date-using Project Management Software
Trends In Distributed Systems Using Project Management Software

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

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

Pine Valley Furniture WebStore: Determining System Requirements

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.

Topics You May Be Interested In
Role And Need Of Systems Analyst Trends In Distributed Systems
System Development Life Cycle (sdlc) Transparency
Data And Fact Gathering Techniques- Interviews, Group Communication, Presentations, Site Visits Physical Models
Feasibility Study And Its Importance Architectural Models
Examples Of Distributed Systems Radical Methods For Determining System Requirements

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.

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

Pine Valley Furniture WebStore: Determining System Requirements

Topics You May Be Interested In
Role And Need Of Systems Analyst System Models
Qualifications And Responsibilities Of System Analyst Physical Models
Feasibility Study And Its Importance Reuse-systems Acquisition
Mobile And Ubiquitous Computing Executing The Project-managing The Information Systems Project
Failure Handling Performing Requirements Determination

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:

  • 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.

Topics You May Be Interested In
System Analyst As Change Of Agent , Investigator And Monitoring Guy , Architect , Psychologist , Motivator , Intermediary Pervasive Networking And The Modern Internet
Types Of Feasibility Studies And Feasibility Reports Transparency
Selected Application Domains And Associated Networked Applications Planning The Project-managing The Information Systems Project
Massively Multiplayer Online Games (mmogs) Building The Baseline Project Plan
Trends In Distributed Systems Modern Methods For Determining System Requirements

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

Pine Valley Furniture WebStore: Determining System Requirements

Topics You May Be Interested In
Systems Models Types Of Models - Systems Environment And Boundaries Architectural Elements
Software Measuring Process And Product Attributes Reuse-systems Acquisition
What Is Information Systems Analysis And Design? Planning The Project-managing The Information Systems Project
Examples Of Distributed Systems Establishing A Project Starting Date-using Project Management Software
Scalability Using Project Management Software

TABLE 5-9 Stages of System Implementation of WebStore

Pine Valley Furniture WebStore: Determining System Requirements

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.

 

Topics You May Be Interested In
System Development Life Cycle (sdlc) Physical Models
Cost-benefit And Analysis -tools And Techniques Reuse-systems Acquisition
Distributed Multimedia Systems Representing And Scheduling Project Plans
Quality Of Service Assessing Project Feasibility
Introduction Modern Methods For Determining System Requirements

 

 



Frequently Asked Questions

+
Ans: Whether traditional or modern, the methods for determining system requirements that you have read about in this chapter apply to any requirements determination effort, regardless of its motivation. view more..
+
Ans: Even though we called interviews, questionnaires, observation, and document analysis traditional methods for determining a system’s requirements, all of these methods are still used by analysts to collect important information. view more..
+
Ans: As stated earlier and shown in Figure 5-1, the two parts to systems analysis are determining requirements and structuring requirements. view more..
+
Ans: In the last chapter, you read how Pine Valley Furniture’s management began the WebStore project—to sell furniture products over the Internet. view more..
+
Ans: Collection of information is at the core of systems analysis. view more..
+
Ans: Even though we called interviews, questionnaires, observation, and document analysis traditional methods for determining a system’s requirements, all of these methods are still used by analysts to collect important information. view more..
+
Ans: Whether traditional or modern, the methods for determining system requirements that you have read about in this chapter apply to any requirements determination effort, regardless of its motivation. view more..
+
Ans: Process modeling involves graphically representing the processes, or actions, that capture, manipulate, store, and distribute data between a system and its environment and among components within a system. view more..
+
Ans: Data-flow diagrams are versatile diagramming tools. view more..
+
Ans: Sofware engineering syllabus The course of the program is designed in an exceedingly manner that it covers all the aspects of software system engineering needed for higher understanding of the scholars. The delivery methodology of the program is usually schoolroom lectures Associate in Nursing sensible laboratory sessions beside seminars and internships being an integral a part of the course. BE/B.Tech software system Engineering give students data of evaluating the correct codes and software system for specific tasks. view more..
+
Ans: The first published model of software development process was derived from more general system engineering processes. Because of the cascade from one phase to another, this model is known as the waterfall model or software life cycle. The principal stages of the model map onto fundamental development activities: view more..
+
Ans: System prototyping performs the analysis, design, and implementation phases concurrently in order to quickly develop a simplified version of the proposed system and give it to the users for evaluation and feedback. view more..
+
Ans: Software is defined as collection of data, programs, procedures, associated documentaion and rules. which does not have any mass, volume and colour. software does not wear out,get tired or degrade over a long period of time view more..



Recommended Posts:


Rating - NAN/5
524 views

Advertisements