Introduction Fasam System

Requirements enter Purpose Introduction The primary coil death of this roll is to provide a fuck and accurate list of requirements for a eruption and Security Alarm Monitoring System. Upon completion, the written inventory bequeath act as a binding contract between developers and substance abusers and bequeath provide a common saddle of reference for schema Document Conventions Although this document is int oddmented as a dress of Requirements, non a design, some technical information has been included with the requirements description. Intended AudienceThe primary audience of this document includes, but is not limited to, render leaders, the designers and developers of the governance and the end user. (Reference 1) Background Team external is princip tout ensembley a software exploitation follow specialising in eject and security shock monitoring system (FASAM). Team world(prenominal) has been awarded the contract to supply and implement a FASAM for Everett & Co . The building in question is a new building, so on that point is no previous FASAM system puted. The building in question constitutes of 2 graces, each floor consisting of 12 ffices. The building leave behind be grouped in ZONES. Zones will consist of x-amount of offices. Below is an ensample of this. Keep in mind that this is not the actual g everywheren layout representation but just an example to illustrate how the regularizes will work. pic from each one zone shall be equipped with various sensors which will monitor for and detect certain scourges. Each zone shall have security / fire doors installed which the FASAM will have authorization over in regards to locking and unlocking depending on the threat.Team global 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 range of a function The using of this system will include the gathering of the requirements, enlist the architecture design using substance modelling, creating a prototype based upon the proposed user porthole and the requirements validation which will all help to turn over to the initial development of a FASAM for Everett & Co.Gathering of the requirements The input for this shall behave from interviews with the client. The experience gained from the input will help get to 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 consequent of this will be a running(a) prototype of the system. Requirements validation The input for this fraction comes from the three previously mentioned stages. The outcome will be a produced va lidation document highlighting the pros and cons of each stage. Limits and constraints of the project scope Obviously with Team International universe 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 var. 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.