Introduction fasam system

Requirements Document Purpose Introduction The primary goal of this document is to provide a complete and accurate list of requirements for a Fire and Security Alarm Monitoring System. Upon completion, the document will act as a binding contract between developers and users and will provide a common point of reference for system Document Conventions Although this document is intended as a set of Requirements, not a design, some technical information has been included with the requirements description. Intended Audience

The primary audience of this document includes, but is not limited to, project leaders, the designers and developers of the system and the end user. (Reference 1) Background Team International is primarily a software developing company specialising in fire and security alarm monitoring system (‘ FASAM’). Team International has been awarded the contract to supply and implement a FASAM for Everett & Co. The building in question is a new building, so there is no previous FASAM system installed. The building in question consists of 2 floors, each floor consisting of 12 ffices. The building will be grouped in ZONES. Zones will consist of x-amount of offices. Below is an example of this. Keep in mind that this is not the actual zone layout representation but just an example to illustrate how the zones will work. [pic] Each zone shall be equipped with various sensors which will monitor for and detect certain threats. Each zone shall have security / fire doors installed which the FASAM will have control over in regards to locking and unlocking depending on the threat.

Team International has decided, after gathering the requirements, that an automated system with a manual over-ride option, which will be connected to a central control room, will best suit the needs of Everett & Co. Product Scope Processes involved in the project scope The development of this system will include the gathering of the requirements, outline the architecture design using CORE modelling, creating a prototype based upon the proposed user interface and the requirements validation which will all help to contribute to the initial development of a FASAM for Everett & Co.

Gathering of the requirements: The input for this shall come from interviews with the client. The knowledge gained from the input will help create the Requirements document. Outline the architecture: The input for this shall come from the requirements document. The knowledge gained from the document will contribute to help producing systems architecture and a systems model. Creating a prototype: The input for this shall come from the requirements document.

The outcome of this will be a working prototype of the system. Requirements validation: The input for this section comes from the three previously mentioned stages. The outcome will be a produced validation document highlighting the pros and cons of each stage. Limits and constraints of the project scope Obviously with Team International being primarily a software producing company, there is a lack of knowledge in regards to certain hardware elements.

That is why this project will not cover the configuration of sensors due to the fact that when Team International purchases the sensors from the supplier, the suppliers implement the required configuration settings for the sensors. In regards to the sensors, all Team International does is install the sensors and connect them to the main user interface system. This process shall only cover the developing of a fire and security threat system.