Gungley Industrial Machines - Heavy Plant Sales System (HPPS)

3661J,K,L - Case study for Practice activities

Project plan HPPS-PP extract

Test plan HPPS-TP

Functional specification overview HPSS-F01

Functional specification HPPS-EX1-FS1

Functional specification HPPS_LX1_FS3

Test requirement HPSS-S4A-TR1, extract

Test requirement HPSS-U17A-TR1, extract

Test requirement HPSS-X5A-TR1, extract

Test requirement HPSS-X11A-TR1, extracts

Test script HPSS-S4A-TS1

Test script HPSS-S4A-TS2

Test script HPSS-U17A-TS1

Test script HPSS-X5A-TS1

Result Log HPSS-RL-1

Result Log HPSS-RL-2

Result sheet HPSS-S4A-RS1

Result sheet HPSS-U17A-RS1

Result sheet HPSS-UX5A-RS1

Result sheet HPSS-X10A-RS1

Test summary report HPSS-TS1, extract

Test summary report HPSS-TS2, extract

Project plan HPPS-PP extract

Project details

Name / Heavy Plant Sales System
ID: / HPSS
Document Ref: / HPPS-PP
Start / 2 September 2007
End
Estimated Costs / $179,000
Owner / Graham Gungley, CEO Gungley Industrial Machines
Description / The purpose of this project is to develop and implement software, using internet technology to conduct on-line ordering of heavy plant equipment. Customers will be able to use the internet to browse a product list, and then send an order to sales staff. Sales staff then process the order, and contact the customer.
Objectives / The developed software will:
(1) Allow customers to view a list of product specifications and create an order for an individual product.
(2) Allow sales staff to view a list of products and edit product details.
(3) Allow sales staff to view a list of customer orders and update order status
Deliverables / (1) Software - Centralised database for order and product details
(2) Software - Centralised web site connecting to the database
(3) Software - On-line (internet) product query and ordering facility
(4) Software - Networked product/order query and editing facility
(5) Documentation – Top level design
(6) Documentation – Test Plan, Results and Analysis
(7) Documentation – Functional Specifications
(8)Documentation – User Guide
(9) Documentation – Operators Guide

Project brief

Gungley Industrial Machines sell heavy plant equipment to mining operations and large agricultural companies. Sales staff receive calls from customers requesting information on plant items. Information is faxed, emailed or mailed to the customer who places an order for a plant item. Past experience has demonstrated that potential customers have been lost due to untimely access to information on product specifications.

The decision to develop the Heavy Plant Sales System (HPSS) is based on its ability to retain customers by providing a service for easy access to product information and ordering. The company’s client base includes remote industrial sites, all with internet access, who will readily accept this technology to perform business.

The HPSS will be resident on the corporate web server. Customers access the system through web pages, over the internet. Sales staff access the system using compiled software, over the corporate network. All application software access over the network will be restricted by the systems administration. The system will be able to handling 10 orders per day, with 2000 hits to the product web pages per month. All completed orders will be deleted at the end of the financial year. The system will reside on the database server computer connected to the corporate internet/intranet server. The database server will be a Leviathan PX4800, with twin Dual Core Xeon 3G processors, Raid 5 hard disk arrays of total 600G and 8G RAM.

HPSS will be developed in three separate sub-systems

Order creation

A set of web pages to list product details and create an order. The order created is submitted to the corporate web server, which updates the database.

Order processing

A compiled stand-alone program accessed by users logged on to the corporate network. Sales staff list all unfilled orders and can update orders status.

Product maintenance

A compiled stand-alone program accessed by users logged on to the corporate network. Sales staff list all plant items and modify product specifications.

Project scope

To be included

  • A home page to provide links to the product listing and the order form.
  • Corporate web page layout standards.

To be excluded

Any security features. Web pages will be accessible to all internet users. Corporate users access programs through access privileges granted by network administrator.

Project constraints

  1. Project must be completed and accepted prior to the financial year beginning 1 July 2008.
  2. Consultants will not be available beyond February 2008.
  3. All payments to be made during the 2007-2008 financial year.

Stakeholder/communications

Graham Grungley, CEO Gungley Industrial Machines

Cheryl Turner, Financial Controller, Gungley Industrial Machines

Sarah Gaskell, Network Administrator, Gungley Industrial Machines

Simon Symes, Project Manager - Software Development, Gungley Industrial Machines

Greg Cummings, Senior Sales Supervisor, Gungley Industrial Machines

Jane London, Team Leader, Consultant

Judy Wong, Analyst/Programmer, Consultant

Nick Curtis, Programmer, Consultant

Carol Graves, Web developer, Consultant

Assumptions

  • Representative development environment is available to project team at all stages of the project.
  • Selected software/hardware platform is adequate for system development

Work schedule

Sep / Oct / Nov / Dec / Jan
ACTIVITY / 02 / 09 / 16 / 23 / 30 / 07 / 14 / 21 / 28 / 04 / 11 / 18 / 25 / 02 / 09 / 16 / 23 / 30 / 06 / 13
Prepare & review project plan / x
Prepare top-level design / x
Prepare functional specifications / x / x
Prepare test plan / x / x
Review design & test plan / x
Prepare development environment / x / x
Program network software / x / x / x / x
Program web pages / x / x / x
Prepare project documentation / x / x / x
Perform unit test / x / x / x / x
Review unit test / x / x
Perform integrated testing / x / x
Review integrated testing / x
Perform system testing / X
Review system testing / x
Perform defect correction / x
Review defect correction / x / x
Perform version control / x / x
Prepare User Guide / x / x / x / x
Prepare Operator Guide / x / x / x
Perform acceptancy test / x / x / x / x
Review acceptancy test / x / x / x / x
Perform defect correction / x / x

Test plan HPPS-TP

Cover sheet

Name / Heavy Plant Sales System
ID: / HPSS
Document Ref: / HPPS-TP
Date
Status / Final
Author / Judy Wong - Analyst/Programmer, Consultant
Author Signature
Approval (PM) / Jane London, Team Leader, Consultant
Approval Signature
Approval (Owner) / Simon Symes, Project Manager - Software Development, Gungley Industrial Machines
Approval Signature

1. Introduction

Outline

This document provides the test plan for the completing of the events for unit, integrated and system testing of the Heavy Plant Sales System (HPSS).

Document structure

This document has the following structure:

Section 2 Test methodology, outlines the testing approach, the constraint on this process, and the dependencies of tasks.

Section 3 Scope – lists inclusions and exclusions

Section 4 Assumptions

Section 5 Test completion, defines criteria for exiting the testing process

Section 6 Risks

Section 7 Roles and responsibilities

Section 8 Summary of test events

Section 9 Work Schedule (Whole Project)

References

HPSS-PP Project Plan

HPSS-FO Functional Specification (Overview)

Functional Specification HPPS-FO1, version 1.0

2. Testing methodology

Overview

This section discusses the overall methodology taken to implement the testing phase of the project.

  1. Unit testing is performed on each software module. Events include logical and user interface tests.
  2. System tests cover functionality, usability, security, disaster recovery, performance testing. Testing to be performed in a simulated environment. Automated test software is used to perform performance and stress testing.
  3. Integrated testing is performed on the live system
  4. Stress tests performance examine degradation for order entry modules at 2000 transactions per hour.
  5. Integrated tests are performed incrementally for each module/database interface component. Components are then grouped for testing into the functionally groups: order processing and product maintenance. Functional groups are combined to test the integrated software.

Constraints

  1. Project must be completed and accepted prior to the financial year beginning 1 July 2008.
  2. Consultants will not be available beyond February 2008.
  3. All payments to be made during the 2007-2008 financial year.
  4. All unit, system and integrated testing, including any regression testing to be complete before the 16 December 2007.

Dependencies

  • All unit testing of modules included in systems test to be complete and defect free prior to system testing
  • All unit testing of modules test to be complete and defect free prior to integrated testing
  • System testing cannot commence until hardware and software are delivered, and installed

3. Test scope

To be included

Tests for potential security risk from the internet

To be excluded

  • User acceptancy testing
  • Network applications access security
  • Integrated tests not to include the testing of browser software.

Assumptions

  • Selected software/hardware environments are available to project team at relevant stages of the project.
  • Selected software/hardware environments is adequate for testing
  • Team Members will be available during the testing process, as required

5. Test Completion

  • All result sheets and logs, for every test collected
  • All test summaries complete
  • All defects identified and acceptable to user

6. Risks

  • Unit testing reveals large number of defects, system and integrated testing delayed
  • Critical defects identified requiring redesign of software specification
  • Defect modification requirements exceed the time and budget available

7. Roles and Responsibilities

Name / Position / Responsibility
Graham Grungley / CEO Gungley Industrial Machines / Owner
Cheryl Turner / Financial Controller, Gungley Industrial Machines / User representative
Sarah Gaskell / Network Administrator, Gungley Industrial Machines / User representative and testing
Simon Symes / Project Manager - Software Development, Gungley Industrial Machines / User representative
Greg Cummings / Senior Sales Supervisor, Gungley Industrial Machines / User representative and testing
Jane London / Team Leader, Consultant / Project Manager
Judy Wong / Analyst/Programmer, Consultant / Test analyst, testing and programming
Nick Curtis / Programmer, Consultant / Application programming and testing
Carol Graves / Programmer, Consultant / Web development and testing

8. Summary of test events

8.1 Unit tests

Module(s) tested / Test ID / Test Type / Comment
… / … / … / …
HPSS-LP1 / HPSS-U3A / White box / Check logic for retrieving product details from database
HPSS-MM1 / … / … / …
HPSS-EX1 / HPSS-U17A / Black Box / Test validation routines and error message displays
HPSS-EX1 / HPSS-U18A / … / …
HPSS-EX1 / HPSS-U19A / … / …
HPSS-LP2 / … / … / …
HPSS-EP1 / … / … / …
HPSS-LX1 / … / … / …
HPSS-UX1 / HPSS-U58A / … / …
HPSS-UX1 / HPSS-U59A / … / …
HPSS-UX1 / HPSS-U60A / User Interface / Check screens against style sheets and Functional Spec.
… / … / … / …

8.2 System tests

Module(s) tested / Test ID / Test Type / Comment
… / … / … / …
HPSS-EX1
HPSS-LX1 / HPSS-S4A / Functional / Order entered on-line and retrieve by network software.
HPSS-LX1- / HPSS-S5A / Performance / Perform queries on maximum orders
HPSS-UX1 / HPSS-S6A / Stress / Automated test software performs high volume order entry
… / … / … / …
… / … / … / …

8.3 Integrated tests

Module(s) tested / Test ID / Test Type / Comment
… / … / … / …
HPSS-LP1 / HPSS-X3A / Integrated / In
HPSS-LP1 / HPSS-X5A / Stress & Load / Module/database
HPSS-EX1 / HPSS-X6A / Stress & Load / Module/database
HPSS-LP2 / HPSS-X7A / Stress & Load / Module/database
HPSS-EP1 / HPSS-X8A / Stress & Load / Module/database
HPSS-LX1 / HPSS-X9A / Stress & Load / Module/database
HPSS-UX1 / HPSS-X10A / Stress & Load / Module/database
HPSS-LP1
HPPS-LP2
HPSS-EP1
HPSS-MM1 / HPSS-X11A / Integrated / Interoperability of product maintenance modules
HPSS-EX1
HPSS-LX1
HPSS-UX1
HPSS-MM1 / HPSS-X12A / Integrated / Interoperability of order processing modules
HPSS-LP1
HPSS-MM1
HPSS-EX1
HPSS-LP2
HPSS-EP1
HPSS-LX1
HPSS-UX1 / HPSS-X13A / Integrated / Load all components on operational platform

9. Work schedule

Sep / Oct / Nov / Dec / Jan
ACTIVITY
/ 02 / 09 / 16 / 23 / 30 / 07 / 14 / 21 / 28 / 04 / 11 / 18 / 25 / 02 / 09 / 16 / 23 / 30 / 06 / 13
Prepare & review project plan / x
Prepare top-level design / x
Prepare functional specifications / x / x
Prepare test plan / x / x
Review design & test plan / x
Prepare development environment / x / x
Program network software / x / x / x / x
Program web pages / x / x / x
Prepare project documentation / x / x / x
Perform unit test / x / x / x / x
Review unit test / x / x
Perform integrated testing / x / x
Review integrated testing / x
Perform system testing / x
Review system testing / x
Perform defect correction / x
Review defect correction / x / x
Perform version control / x / x
Prepare User Guide / x / x / x / x
Prepare Operator Guide / x / x / x
Perform acceptancy test / x / x / x / x
Review acceptancy test / x / x / x / x
Perform defect correction / x / x

Functional specification overview HPSS-F01

Cover sheet

Name / Heavy Plant Sales System
ID: / HPSS
Document Ref: / HPPS-FO1
Release No: / 1.0
Date
Status / Final
Author / Judy Wong - Analyst/Programmer, Consultant
Author Signature
Approval (PM) / Jane London, Team Leader, Consultant
Approval Signature
Approval (Owner) / Graham Grungley, CEO Gungley Industrial Machines
Approval Signature

1. Introduction

1. Objectives

The objectives of the Heavy Plant Sales System are to:

  • Allow customers to view products and create order over the internet
  • Allow suppliers to update customer orders using a network application
  • Allow suppliers to maintain a list of products using a network application

2. Module overview

The Heavy Plant Sales System (HPSS) has three sub-systems (figure 2.1 System Overview). The order entry sub-system allows an internet customer to list available products and create an order, submitted to a server. The order processing sub-system provides a facility for a network user (supplier) to retrieve a customers order and enter order status. Products list are maintained the product maintenance sub-system.

All data is stored on a server side database HPSS in two tables: products and orders

Image: Showing the relationship between Customer, Create Orders, Maintain orders, Supplier, Maintain Products

Figure 1: System overview

Order entry

The customer selects either to list products or enter orders from a menu: module HPSS-MM1, The list product module HPSS-LP1 displays a list of product items. The enter order module HPSS-EX1 displays a screen base form for customer data entry. When the customer submits the form the orders table is updated.

All modules include for client-side and server-side processes developed using HTML, Javascript and VBScript.

3661J_R-CaseStudy_fig02.jpg

Image: Showing arrow from Customer to (order details) HPSS-EX1 Enter Order, arrow to Orders. From Products arrows to (product details) HPSS-LP1 List Products to (product details_ Customer).

Figure 2: Order entry data flow

Order processing

The business user accesses customer order with a network based application. Unprocessed orders are displayed by module HPSS-LX1, and the user selects an item. The selected order is displayed in a form by the order edit module HPSS-UX1. The user can change details and then update the orders table.

3661J__CaseStudy_fig03.jpg

Image: Showing arrows from Supplier to (order details) HPSS-LX1 List Orders to (order details) Orders to (order details) HPSS_UX1 Update Orders to (order details) Supplier.

Figure 3: Order processing data flow

Product maintenance

The business user accesses product details with a network based application. Products are displayed by module HPSS-LP2, and the user selects an item. The selected product is displayed in a form by the product edit module HPSS-EP1. The user can change details and then update the product table.

3661J_R_CaseStudy_fig04.jpg

Image: Shows arrows from Supplier (product details) to HPSS-EP1 Edit Production to (product details) Products to (product details) HPSS-LP2 List Products to (product details) Supplier.

Figure 4: Product maintenance data flow

Appendix 3 – Data dictionary (extracts)

Table Name: Orders
Field Name / Type / Size / Default / Validation rules/Comments
ID / Long / 0 / Assigned by RDBS
Product ID / Long / 0 / Required
Name / Text / 50 / Null / Required
Email / Text / 100 / Null / Required
Date / Date / Null / Assigned by RDBS
Status / Text / 10 / “new” / Required

Functional specification HPPS-EX1-FS1

1. Details

Name / Heavy Plant Sales System
ID: / HPSS
Document Ref: / HPPS-EX1-FS1
Release No: / 0.3
Date
Author / Judy Wong - Analyst/Programmer, Consultant
Author Signature
Approval (PM) / Jane London, Team Leader, Consultant
Approval Signature

2. Module function

This module:

Displays a data entry form in a client browser.

Validates user input data

Updates server-side database with valid data

3. Module overview

This module is represented as script in two web files. HPPS-EX1-01-3 is a client side file that displays a data entry form, performs data validation and submits valid data to a server side file HPPS-EX1-02-3. The server-side file connects to the HPPS database and adds the form details to the orders table.

4. Data access

Input

None

Output

Order Table, HPSS database

5. External Components

None

6. Screen layouts

Order screen

3661J_R_CaseStudy_fig05.jpg

Image: Shows Heavy Plant Sales System, Product Order Entry listing Product ID, Name. Email

Figure 5: Order screen

7. Object description

All field objects conform to the Style sheet for web design (SS-17) and the corporate colours detailed in the Functional Specification – Overview (HPSS-FO1)

Product Id field

Default value is null.

Name field

Default value is null.

Email field

Default value null.

Submit button

On click perform

8. Processes

Validate input

Use data dictionary rules validation rules to Product ID, Name and Email fields data entry. Validate data in order of form data entry. For each invalid entry display a standard warning screen with the message Invalid <field name>. On exit from warning screen set focus to invalid field and highlight invalid data.

If all data is valid:

Display message “Data has been successfully submitted” using the standard message screen detailed in the Functional Specification – Overview (HPSS-FO1)

Submit data to server side process update table and display