Menu ▾ ▴

Product Requirements

product requirements (1)
Jack Liu

Project Management

Brief introduction

A project is just like what assignment that the end user works on. It also looks like a container for one or more environments. For example, for a test team which is working on IBM Connections 4.0 testing, they may name the project as "IBM Connections 4.0". This project may have 6 environments, including 4 RVT ( Reliability Verification Test ) environments and 2 IVT( Integration Verification Test ) environments.

Key line items

  1. User can create project to encapsulate one or more environments.
  2. User can view each project details, like project name, description etc.
  3. User can update project related information, such as project name, description.
  4. User can add/associate one or more environment into a project.
  5. User can remove environment from a project.
  6. user can delete project without deleting any environment that is associated with the project.

Environment Management

Brief introduction

A environment is a group of physical hosts or virtual machines. It has been setup for a testing/production purpose. For example, a simplified IBM Connections 4.0 environment may consist of 3 hosts, including a directory server, a DB2 server, and a application server which hosts WAS DM/Node Agent/Application Server.

Key line items

  1. User can create project environment and add it into a project.
  2. User can list all hosts in a environment.
  3. User can remove a environment without deleting any hosts which are in that environment.
  4. User can add hosts into a environment. The input could be a host name or IP address.
  5. User can remove hosts from a environment.

Host Management

Brief introduction

a host could a physical host or virtual machine.

Key line items

  1. User can add a host one by one into a environment.
  2. User can upload a text file which includes a bunch of host names each at a line.
  3. User can view the detail information of a host that can be populated dynamically and automatically. The detail information may include CPU type and quantity, memory, disk size, IP address, hostname, serial number, MAC address, part number, etc.
  4. The details of a host can be cached in the database.
  5. The details of a host can be refreshed manually.

IBM Product Detection

Brief introduction

A IBM product/product component can be installed a host. DSV can automatically detect all installed IBM products on a host when adding or refreshing a host details.

Key line items

  1. Product detection program can be run on any supported operating system.
  2. Supported production list can be extended. In other word, it should support new production detection in the future.

Supported IBM Product List

Brief introduction

This is a list that is only for the first version of DSV. But it can be extended in the future without altering the framework.

Key line items

  1. IBM Connections 3.x, 4.x
  2. IBM Portal 7.x 8.x
  3. IBM Sametime 8.5.2
  4. IBM HTTP Server 7.x 8.x
  5. IBM Directory Server 6
  6. IBM DB2 9.x
  7. IBM Rational Performance Tester 8.x

IBM Middleware Detection

Brief introduction

Detect if a IBM middleware (WAS, Domino) installed on a host.

Key line items

  1. Ability to detect if WAS installed. What version or fix pack?
  2. Ability to detect if Domino installed. What version or fix pack?

Network Detection

Brief introduction

DSV can detect the current network settings, and run some diagnosis tests.

Key line items

  1. DNS setting check, including name (reverse/)resolving.
  2. Duplex and Speed setting
  3. IPv4 and IPv6 detection
  4. NetBIOS over TCP/IP setting on Windows 2003
  5. Windows 2003 network tuning
  6. Linux network tuning

Operating System Detection

Brief introduction

DSV can detect what OS type on each host and run some OS related tests.

Key line items

  1. System time check, including time server setting.
  2. OS version and patch level check
  3. Product version and OS cross check.
  4. Cross check on CPU, memory, disk requirements for each product.
  5. OS tuning check, such as the max number of Linux open files

Hardware Detection

Brief introduction

Hardware information can be automatically collected.

Key line items

  1. How many CPU?
  2. Total size of memory
  3. How many hard disk attached and total size of each disk.
  4. SMART status

Validation Management

Brief introduction

A validation is a testing that can be run against with a IBM product, middleware, network, or operating system. After its running, it can tell whether the current configuration is correct or not.

Key line items

  1. User can add a validation and bind it with a IBM product, middleware, network, operating system.
  2. User can view all basic information about a validation, which may include validation name, description etc, and for what IBM production, middleware, network, or operating system.
  3. User can store their validation program on a central repository. All validation program will download from this repository before running a target host.
  4. User can delete a validation.
  5. Validation accounting, like how many times it runs, how long it may take.
  6. User can rate or add a tag to a validation. This is a social requirement.
  7. User can mark a validation as open or private to choose whether it can be searched by other user.
  8. All open validation can be searched by any other user.
  9. User can run a validation or a bunch of validations at the same time.
  10. After getting executed on a target host, each validation can report the status and checking result to DSV Center.

Validation Profile

Brief introduction

A validation profile is a group of settings. A validation may have one or more validation profiles. For example, the developer of a validation may create a default profile that includes a WAS thread pool size is 50. When the end user runs a validation with this default profile, the result will be displayed as failed if the current target has a thread pool size 20. The end use could also create a new profile based on the default. The result will be displayed as successful if the new profile contains a setting which has been adjusted to 15.

Key line items

  1. A default profile should be provided with the validation
  2. End user can create a profile based on the default profile.
  3. A validation can have one or more validation profile.

Validation List Generation

Brief introduction

The full validation list is generated automatically based on all kinds of auto-detected information. For example, we can generate a list for IBM Connections 4.0 on a designate environment.

Key line items

  1. Generate a validation list at runtime.
  2. All validations in the list can be executed simultaneously.

Validation Result Management

Brief introduction

DSV will display and cache every validation result into the database after each run.

Key line items

  1. DSV will display all validations on one page
  2. DSV has the ability to cache every validation result into the database after each run.
  3. User can select and delete cached result.

Legacy Scripts Support

Brief introduction

There are already lots of legacy scripts. These scripts could be programmed in Windows Batch scripts or Linux Shell scripts. The DSV framework could invent a adapter for each kind of legacy scripts to support reading the execution result from the standard output.

Key line items

  1. Windows Batch scripts support
  2. Linux Shell Script support
  3. Python script support