1. Introduction
1.1. Purpose of the system
A fire and security alarm monitoring system provide real-time remote, hardware or zone status, alert and monitoring to administrator, which is this system will be conduct in one place. Normally, building furnished with this system will divided into zones with a number of hardware such as alarm, sprinkler, direction indicators, auto door (this door functioned with automatic lock) and sensor that detecting a problem. All this hardware is associated with each zone which is linked to administration monitor. This system can be access by administrator anywhere in Local area network computer. However, this system also are connect to the internet which is react to called emergency services when there is confirmed situation.
1.2. Design goals
The design goals represent the desired qualities of the system. The following design goals for e-Junk system are identified.
· Methods. This system use an object-oriented design methodology based on the hybrid waterfall. The system will be developed using PHP and SQL for primary purpose and database, Microsoft Visual C# for hardware programming besides Microsoft PowerPoint, Word and Excel is used for slides presentation.
- Physical Environment. The database and application server will run in a computer machine connected the 3rd party device which connected to a number of hardware component distributed to all over the selected building area with local area network.
- Usability. The product has to be made as user-friendly as possible. All interfaces of the software product should be simple enough to convey the required information to the user and allow the user to control remotely at any place in local area network with permission level.
- Response time. The system must meet the specified hardware requirements and response times. The system should be fast enough to produce the correct result on time to avoid mistaken detection or hardware failure. This risk will be addressed by monitoring hardware health from time to time.
- Customization. The database for the system will be using SQL and PHP. The database program expected to be change in future. The changes in the future probably because of additional hardware component or system features upgrading.
1.3. Definitions, acronyms and abbreviations
Application Programmer Interface
Set of fully specified operations provided by a subsystem.
Capability Maturity Model
Framework for assessing the maturity of organizations characterized by five levels of maturity.
Issue-based Information System
An issue model proposed by Kunz Rittel composed of three types of nodes: issues, position, and argument.
Joint Application Design
A requirement elicitation technique involving the collaboration of clients, user, and developers on constructing a requirements specification through a week-long working meeting.
Object Constraint Language
A formal language defined as part of the UML used for expressing constraints.
Object Design Document
A document describing the objective design model. The object design model is often generating from comments embedded in the source code.
Question, Options, and Criteria
An issues model, proposed by McLean et al., extending IBIS to represent criterion and assessment set of questions.
Requirement Analysis Document
The documents describing the analysis model.
Software Configuration Management Plan
A document defining the procedures and conventions associated with the configuration management of a project. These include identifying configuration items, accounting for their status, approving change requests, and auditing.
Software Project Management Plan
The controlling document of a software project. The SPMP defines the activities, work products, milestone, and resource allocated to the project. Also defines in the SPMP are the management procedures, and conventions applicable to the project such as status reporting, risk management, and contingency management.
System Design Document
A document describing the system model.
Test Manual
A document describing the test cases used to test system, along with their results.
Unified Modeling Language
A standard set of notations for representing models.
Work Breakdown Structure
A hierarchical decomposition of project work into task. Leaves represent tasks that are assigned to participants. Aggregates represent the work associated with a work product.
Extreme Programming
A methodology targeted for small term of developers who need to develop software quickly in a changing environment. Extreme Programming aims at making the design of the system as explicit as possible in the source code, hence reducing the need for documentation and the risk of inconsistencies among different documents.
API Application Programmer Interface
AS Application Server
CMM Capability Maturity Model
IBIS Issue-based Information System
JAD Joint Application Design
OCL Object Constraint Language
ODD Object Design Document
QOC Question, Options, and Criteria
PHP Hypertext Preprocessor, computer scripting language
SQL Structured Query Language, database computer language designed for the retrieval and management of data in relational database management systems (RDBMS).
1.4. References
- “Fire and Alarm Security System” Problem Statement
- “Fire and Alarm Security System” Requirements Analysis Document
· Staff, C. 4. (2003, Spring). Department of Computer Science and Electrical Engineering. Retrieved September 19, 2008, from University of Maryland, Baltimore County Web site: www.cs.umbc.edu/courses/undergraduate/421/spring03/design.pdf
1.5. OVERVIEW
The rest of the document contain current software architecture, the new proposed software architecture and subsystem services.
The current software architecture will describe the architecture of the system that going to be replaced. This will involve some study results. As for proposed system architecture, this section will document the system design model of the new system. Details of these subsections can be seen here. Subsystem services will give an overview of what are the services provided of each of the subsystem in term of operations.
