An Evaluation of the FASAM System throughout the Software Lifecycle - Literature review Example

? Software Engineering CW4: An Evaluation of the FASAM System throughout the Software Lifecycle, With Particular Regard to the Goals and Principles of Software Engineering. Name of Student Student Number Institution Course Code Name of Instructor Date Table of Contents Table of Contents 1 1.0.Introduction 1 2.0.Goals and Principles of Software Engineering in regard to FASAM 2 2.1.Goals 2 2.2.Basic Principles 3 2.3.Evaluation of FASAM Software Lifecycle stages (against the specific goals and principles). 5 3.0.Critical Review of the Project Successes and Failures 6 4.0.Achievements 7 5.0.Conclusion 9 6.0.Reference List 10 1.0. Introduction Dating back from the era of technology development, early responses to fires have always resulted to positive results in controlling extensive damages. In the engineering sector, fire safety has remained a highly critical undertaking regarding any project initiated in the contemporary world. According to Casey and Grant (2008), the risks posed by fires in the current times, continues to cause a serious challenge to engineers across the entire profession. The requirement of control measures to fire outbreaks becomes an imperative undertaking in the construction of buildings. Therefore, Fire and Security Alarm Monitoring (FASAM) has a greater role in the engineering projects. Fire safety, remains a key concern for many engineers and leads to the initiation of fire safety elements in the projects forming a core part in their implementation (Garis and Clare 2012). This is dictated by diverse challenges emanating from the fire concerns. The requirements for fire fighting equipments like fire extinguishers comes in handy and are highly critical in this context. Further, the installation of an automated fire safety remains essential in ensuring fire safety within expansive buildings. According to NICET (2010), the understanding of various types of fire alarms system forms a basic concept in the fire control. The construction and development of fire safety reporting software could be termed as the beginning of developing a Fire and Security Alarm Monitoring (FASAM) system. The development of automated system could essentially provide immense assistance to the security of fire within buildings or industrial premises. This paper aims at looking at the goals and principles underpinning the FASAM in software engineering as well as the achievements realised. 2.0. Goals and Principles of Software Engineering in regard to FASAM 2.1. Goals The automated Fire and Security Alarm Monitoring system ought to achieve several organisational goals in dealing with the threats posed by fire, and other security concerns within large buildings. The main operational goals of developing the automated system revolve around ensuring that the security threats become handled in a timely and efficient manner (Schwalbe 2005). Among the fundamental concerns that might ensure timely response, include ensuring the involved individuals remain prepared for unexpected occurrences. Preparedness of the involved individuals shall be ensured through the information gathered from the system on a daily basis. The main goals which the FASAM system should achieve include: Providing detailed information concerning the security of the building to the relevant authorities involved in security management. Activating security and fire alarms, in the event of a safety threat, occurring within the concerned building. Storing the information regarding daily occurrences within the building that might assist involved individuals in improving the security within the building. 2.2. Basic Principles According to Pressman (2005), the software development process follows the specified basic principles utilized in development of software within the software engineering profession. The utilized principles govern the profession where development of new programs involves coming up with systems aimed at performing duties previously performed manually. The development of this FASAM system shall inherently involve the conversion of the security duties from manual to automatic. The basic principles ought to ensure integration of all the manual functions of the individuals involved in controlling security threats posed by fires among other things. Some of the basic principles applied in developing this system include: 1. Developing and delivering a quality system at an affordable cost. This shall ensure that the system does not cause financial strains on the budgetary allocation of the organisation. The developers of the software need to work within the scope of the allocated budgetary allowance for the project, hence minimising chances of the budget busting beyond the allocation (Schwalbe 2005). 2. Breaking the entire project into small segments. These segments shall ensure that the project could be implemented in sections, and evaluated in the same segments. This segmentation could potentially minimise the chances of the entire project failing, as problems could be rectified before proceeding to the next project segment (Robinson 2009). 3. Fulfilling the business requirements for the organisation desiring the software installed within their premises (Elliott and Scacchi 2004). This principle becomes limited by the desire to achieve engineering and, or technological excellence. 4. Producing documentation, from the system, allowing for developing and maintaining the system in the future. This maintenance could include introducing advanced technological features into the system at future stages of the system life (Berczuk and Appleton 2002). This feature remains critical in ensuring the system remains updated with the current technology, and eliminating chances of system obsolesce. 5. Joint application design where the users become actively involved in the development of the software. This would ensure that, before completion of the project, the users remains updated with the operations of the system (Garis and Clare 2012). This shall allow for the organisation to utilise minimum amount of time in training the people operating the system. 6. Development of a graphical user interface (GUI) that facilitates for easy interaction between users and system. This principle could allow quick training of individuals working with the system, and ensuring the individuals have the capacity to operate all the functions performed by the system (Ilhan 2005; Hinum 2004). 2.3. Evaluation of FASAM Software Lifecycle stages (against the specific goals and principles). The software contains various operational features that seek to satisfy the goals and objectives of the organisation. The evaluation process aims at establishing the compatibility of the developed system with the requirements of the organisation utilising the system. With respect to NFPA 72 (2007) argument, the system shall seek to satisfy and fill the existing security shortfalls with the manual systems utilised in providing fire and security alerts. The purpose of conducting a system evaluation remains ensuring that the system can perform all the desired functions of the security department. The evaluation shall be carried out following the implementation and installation phase of the project lifecycle. The project testing phase shall include the relevant evaluation of all components of the software. As a complete project, numerous sections of the project shall be evaluated following completion of each segment (Moore 2008). Dividing the project into segments shall allow the involved individuals to conduct an evaluation at each stage before completing the entire project. This evaluation process shall ensure that the project does not contain malfunctioning units upon completion. The process of evaluation, therefore, remains a continuous process following completion of each segment. According to Drouin (1984) segmented evaluation becomes essential in ensuring the project engineers remain assured of the project functionality. This also becomes crucial in ensuring timely evaluation while minimising the time consumed in evaluating an entire, completed project (Berczuk and Appleton 2002). Such evaluation remains fundamental through assisting the involved individuals in establishing the areas, within the project; that might cause challenges, or require amendments before presenting the completed project. 3.0. Critical Review of the Project Successes and Failures This section critically evaluates and reviews the project initiation stage incorporating the explanation of the whole project followed by the project implementation which entails the software and hardware analysis and evaluation; in general the testing of the whole project effectiveness. Further, it reviews critically sustenance of the whole system and the importance for maintenance and finally is the evaluation to ascertain the whole software cycle and its objectives for achievements. The project discussed in this paper clearly outlines the measures to be undertaken in the fire control measures. The introduction of monitoring procedures for fire alarm systems is critical towards the reduction of response time in comparison to actual alarms not to mention the maintenance needs (Bukowski and Moore n.d.). The project’s first stage is very extensive to ascertain the acquisition of materials and the eventual totality of requirements therein. The project’s automated fire reporting system could play a significant role in controlling imminent danger posed by conflagrations that might occur. Owing to the fact that the fire incidences are not expected, there is a critical need for system installation that looks into the management of the dangers as regards to Robinson (2009) argument. This has been well discussed and outlined with the validation checks well illustrated. The stage is very clear in illustrating to the non technicians the working of the project. The second stage clearly outlined the financial requirements regarding the whole project. The project is affordable as per the set standards with regard to the peril controlled. The modelling technique outlined has been effective with regard to the requirements set and the overall achievement with respect to FASAM. The utilisation of automated system is highly crucial in the enhancing the response time and rescue operations to prevent losses by initiating prompt alerts to the relevant departments. The two stages well illustrates what is required and its affordability. This shows how well the fire control could eventually result to blocking the incidences thus, saving the company from unexpected losses. The tools and operations needed are crucial and achievable. The third and fourth stage swell validates the overall realisation of the whole project, as well as the objectivity and eventual evaluation of the whole system. The monitoring systems are crucial in the impacting positively towards the operations of many sections in the building set up. In this venture, the challenge regards the potential failure when the system has been designed and installed to meet set objectives. As stated by Cholin and Moore (2002) the failure may come as a result of a given operational failure or fault. Further, the failure may come due to variations in the environment or hazards that affect the system’s ability to meet its objectives. Another failure may arise owing to the failure mechanism. This may arise from when the objectives of the fire alarm system have not been properly matched and integrated with the entire fire safety mission. Failures may also arise from faulty or nuisance alarms. 4.0. Achievements This section outlines the teams approach with respect to both achieving visibility and trace-ability. Further, it concludes with looking at the achievements of the two software modules fundamental aims. This regards to a well managed, life critical, real time, as well as other software attributes that will make higher satisfaction to the target building owners. On evaluating the project at hand, it is clear to note that the efficiency in fire tragedies control will be enhanced. According to Wilson (2011), fire system brings about the realisation of overarching goals for fire safety and its encompassment. This project has looked into all fire protection systems; this calls for their designs to be based on specific objectives that clearly meet the overarching fire protection goals. The life safety goals are very obvious in life (Wilson 2011). With fire protection calling for alarm system standpoint, the project will achieve prompt detection of the hostility entrenched with the hazard and the provision of notification to the occupants to the resultant evacuation of the victims. The system is compliant with the set emergency plan measures hence, will enhance the fire control measures. With property protection goals, the owners have the vision of owning their properties for long without any loss occurrence. According to Ravichandran and Rai (2000), the respect to combustibility of building materials coupled with combustible loading and the continuity of combustibles in the building; this will eventually determine the nature and extent of fire protection system that is relevant for the context. From a fire alarm, system point of view, the fire alarm system devised focuses on enhancing the operational readiness of other fire protection systems in conjunction with prompt detection of a hostile fire and the provision of notification with respect to emergency responders (NICET 2010; Moore 2008; Cholin 1997). The key achievement in the project is with respect to environmental protection that presents itself with the most obscure fire protection measure. With regard to Wilson (2011) and Robinson (2009), the combined efforts of facility owner, stakeholders and fire alarm specialists, the outlining of the objective goals help in the realisation of the overall achievement. The measures and goals discussed here are critical aiding the realisation of the overall achievement. The unique knowledge regarding fire protection is primarily entrenched in the understanding of fire alarm systems, the public fire section operations and the experiences acquired with time. As Frank (2005) discusses, the overall achievement of the project comes in with the true fire safety for any given facility and the combined efforts of the relevant individuals involved. With regard to the organisation desiring the system achieving the organisational, business needs, it remains fundamental as opposed to installing a system with immense technological advancements (Elliott and Scacchi 2004). Following the stated design of this system, the client will be very satisfied with the system. This is in the way that it has been produced in a perfectly managed, real time system that has incorporated all the requirements of a standard software design. 5.0. Conclusion The paper has well illustrated the application of FASAM software with regard to fire tragedies protection. The goals and basic principles behind the introduction of this software development in the fire system control management are highly crucial. This has been evidenced with ten achievements discussed with regard to the overall utilisation of the project. System obsolesce could potentially render the entire system useless in the future, through making the system incompatible with other systems working together with the FASAM. Thus, the paper clearly outlines the underpinning principles that will make the project a success and make fire control effective with respect to the engineering profession. 6.0. Reference List Berczuk, S. and Appleton, B. 2002. Software Configuration Management Patterns: Effective Teamwork, Practical Integration. Addison Wesley, 1st ed. Bukowski, R. and Moore, W.D. (n.d.). Fine Alarm Signaling Systems. 3rd ed. Casey, C. and Grant, P.E., 2008. Intelligibility of Fire Alarm and Emergency Communication Systems. The Fire Protection Research Foundation: Research in Support of the NFPA Mission. Cholin, J. 1997. Fire Alarm Systems Inspection, Testing, and Maintenace, Five Protection Handbook. 18th ed. NFPA, Batterymarch Park, Quincy, MA. Cholin, J. and Moore, W., 2002. How reliable is Your Fire Alarm System? NFPA, VOL. 89(1), pp. 49-53. Commercial Fire Alarm Systems, 2010. Fire Alarm System Components. [Online] Accessed on May 14, 2012 from Drouin, J., 1984. Simplex Safe Survey, Presentation to the Automatic Fire Alarm Association. Annual Meeting, New Orleans, LA, Simplex, Gardner, MA. Elliott, M. and Scacchi, W., 2004. Free Software Development: Cooperation and Conflict in a Virtual Organisation Culture, in Koch, S. (ed.) Free Open Source Software Development. Idea Press. Franz, H., 2005. Development of a Fire Alarm Class Taken by Students from Two-Year Colleges. Annual Conference and Exposition. American Society for Engineering Education Garis, C.L. and Clare, J., 2012. Smoke Alarms Work, But Not Forever; Posing the Challenge of Adopting Multifaceted, Sustained, Interagency Responses to Ensuring the Presence of a Functioning Smoke Alarm. Centre for Public Safety and Criminal Justice Research. [Online] Accessed on May 14, 2012 from Hinum, K., 2004. “Human Centered Design for Graphical User Interfaces”, A Master Thesis in Institute of Software Technology and Interactive Systems, Vienna University of Tech. Faculty of Informatics, Vienna. Ilhan, O., 2005. “Analysis of Graphical User Interface Design in the Context Interaction” (With Case Study Overall on Oven Control Panel); A Master Thesis in Izmir Institute of Technology. Moore, W., 2008. Mass Notification Systems: Design Challenges for the FPE, Fire Protection Engineering, Society of Fire Protection Engineers. Summer 2008, pp. 18-24. NFPA 72, 2007. National Fire Alarm Code, National Fire Protection Association, Quincy MA, 2007 edition. NICET, 2010. Fire Protection Engineering Technology; Fire Alarm Systems. National Institute for Certification in Engineering Technologies (NICET). 8th ed. Pressman, R., 2005. Software Engineering: A Practitioner’s Approach. New York: McGraw- Hill. Ravichandran, T. and Rai, A., 2000. Quality Management in Systems Development: An Organisational System Perspective. MIS Quarterly. Vol. 24(3), pp. 381-415. Robinson, J., 2009. Solving the System: Integrated Fire Alarm Monitoring. Peter Li, Inc. [Online] Accessed on May 14, 2012 from Schwalbe, K., 2005. Information Technology Project Management, 4th ed. Course Technology. Wilson, D.K., 2011. Carefully Examining Fire Alarm Goals, Fire Alarm Notebook. Read More