My favorites | Sign in
Project Home Downloads Wiki Issues Source
READ-ONLY: This project has been archived. For more information see this post.
Search
for
TeamSkill5  
Team Skill 5 IOSS Supplementary Specification
Updated Nov 2, 2010 by scottle...@gmail.com


Supplementary Specification

1. Introduction

1.1 Purpose of the Supplementary Specification

This document collects, analyzes, defines, and organizes all the requirements of the system that are not contained within the use-case model for IOSS (IT Optimized Support System). This document highlights functional requirements and focuses on non-functional requirements and design constraints.

1.2 Scope

This document focuses on the functional requirements of the IOSS system from the software request form to the time when the software has been successfully downloaded and installed on the software requester’s computer. This specification covers all requirements for each subsystem of the IOSS.

1.3 Definitions, Acronyms, and Abbreviations

IOSS-IT Optimized Support System---new system being designed Software Requester-main targeted user of IOSS. This person requests new software(s) to be installed on his/her computer. IT Personnel-Information Technology workers who handle software download requests and repair any unsuccessful software installation. Sourcing Personnel-Workers or buyers who purchase software licenses.

1.4 References

Vision Documentation

2. Functionality

The functional requirements for IOSS have been captured and organized by each user class. There are 3 main user classes for IOSS: software requesters, IT personnel, and sourcing personnel. Functional features for IOSS captured from each user class are presented in the following sections.

2.1 Common Functional Requirements From All User Classes:

  • Provide online web-based system
  • Create a standard software request form
  • Automate process steps
  • Store information automatically and electronically

2.2 Functional Requirements From Software Requesters:

  • Provide capability to check on request status without having to manually track down other people
  • Provide a list of ready to install applications
  • Provide list of alternative software if a specific request is rejected

2.3 Functional Requirements From IT Personnel:

  • Facilitate faster responses from the buyer
  • Enable automatic status updates
  • Link automatically the request progress to the time to handle the request, document process flow trail
  • Record automatically the process flow into a database
  • Allow requester access to the progress timeline
  • Check for duplicate requests that may not need additional approval to process the request
  • Filter automatically request for keywords that indicate there may be an important or specially licensed software that requires manual handling
  • All standard or non-restricted requests should be handled by a fully automated process

2.4 Functional Requirements From Sourcing Personnel:

  • Provide automatically purchase updates to requester
  • Manage requests for ease of handling and look up
  • Standardize format of requests so that only a PO needs to be cut
  • Request automatically approval from management when required

3. Usability

The requirements affecting usability of IOSS have been captured and presented into 4 main groups: (1) Training, (2) Measurable Tasks, (3) Help Tools, and (4) Conventions and Standards.

3.1 Training

  • Training for IT personnel shall be within 1 week.
  • Training for general software requesters shall be within 1 day.
  • Training for sourcing personnel shall be within 1 week.
  • Training materials shall be posted online for availability and accessibility

3.2 Measurable Tasks

  • After training, IT personnel shall be able to handle twice as many requests as the current system.
  • After training, sourcing personnel shall be able to issue a purchase order within 1 hour after the request has been submitted.

3.3 Help Tools

  • IOSS shall provide tips to use the system, user manuals, online and on the phone help system

3.4 Conventions and Standards

  • IOSS shall conform to the standard purchase order format specified by the customer

4. Reliability

Requirements that affect reliability and availability of IOSS are listed below.

  1. Availability: IOSS shall be available to operate 90% of the time, 20 hrs a day with 4 hr-window to be used for upgrade and maintenance.
  2. Mean Time Between Failures (MTBF): 3 months
  3. Mean Time to Repair (MTTR): 24 hrs

5. Performance

IOSS shall handle up to the number or requests/simultaneous users per the licensing agreement without any noticeable degradation in performance.

6. Supportability

IOSS shall be easily modified by the customer to reduce steps deemed unnecessary by the customer such as the sourcing personnel handoff and the manager’s approval. If a company does not require the software license to be purchased by its sourcing personnel, then the IT personnel can issue the purchase order directly to the software’s supplier. This means that the sourcing personnel handoff will be eliminated. Similarly, if the customer does not require each software license purchase to be approved by the requester’s manager, then the customer should be able to eliminate this step from IOSS.

7. Design Constraints

Few constraints were placed on IOSS to ensure that it will be compatible with major IT system.

  1. IOSS shall operate with Windows and Macintosh platforms
  2. IOSS shall operate with Internet Explorer, Firefox, and Safari
  3. IOSS shall be compatible with MS Office

8. User Documentation and Help System Requirements

Following are documentations to be provided:

  1. Getting started guides
  2. User guides
  3. Online help
  4. Administration guide
  5. User glossary
  6. Read Me file and release notes
  7. Labeling and packing requirements

9. Purchased Components

IOSS does not require any purchased components to be built in its design or applications.

10. Interfaces

IOSS shall be able to interface with the following systems:

  1. Windows and McIntosh platforms
  2. Internet Explorer and Fire fox browsers
  3. MS Office Applications
  4. Common data storage systems (TBD)
  5. Common authentication systems (TBD)

11. Licensing and Security Requirements

There are terms and conditions set forth the rights being licensed to the customer for use of this IOSS application. These rights are the only rights the customer has to the software. If in any event the customer does not agree to the terms and conditions or violate the rights, they cannot use the software. There is 1 year of limited warranty given under this terms and conditions. By installing the system, the customer agrees that this terms and conditions is a legally binding and valid contract, agrees to abide by all of the terms and conditions, and further agrees to take all necessary steps to ensure that the terms and conditions are not violated by any person or entity under customer’s employment. Licensor grants this license software to solely use by the customer’s company.

12. Legal, Copyright, and Other Notices

See above section.

13. Applicable Standards

There are no applicable standards to be imposed on IOSS.

14. Internationalization and Localization

IOSS is currently intended to be utilized in the North American market; therefore, no internationalization and localization are required or applicable.

15. Physical Deliverables

Below are physical deliverables to be provided by IOSS:

  1. CD containing IOSS setup instructions
  2. CD containing IOSS training materials
  3. CD containing IOSS recommended standardized forms such as software requests

16. Installation and Deployment

IOSS can be installed and set up by the customer’s IT personnel team; However, IOSS technical representatives are available to deliver and set up the system for each customer onsite.

Comment by gcis...@gmail.com, Nov 28, 2010

Please provide use case descriptions.

It is better to list supplementary specification with numbers.

7/10

Powered by Google Project Hosting