|
TeamSkill5
Team Skill 5 IOSS 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.
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.
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.
Vision Documentation
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.
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.
Requirements that affect reliability and availability of IOSS are listed below.
IOSS shall handle up to the number or requests/simultaneous users per the licensing agreement without any noticeable degradation in performance.
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.
Few constraints were placed on IOSS to ensure that it will be compatible with major IT system.
Following are documentations to be provided:
IOSS does not require any purchased components to be built in its design or applications.
IOSS shall be able to interface with the following systems:
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.
See above section.
There are no applicable standards to be imposed on IOSS.
IOSS is currently intended to be utilized in the North American market; therefore, no internationalization and localization are required or applicable.
Below are physical deliverables to be provided by IOSS:
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. | |
Please provide use case descriptions.
It is better to list supplementary specification with numbers.
7/10