Software engineering assignment

Below is a section taken from a Problem Domain Description for a Fire and Security Alarm Monitoring System (FASAM).A large building requires an automated alarm system, which monitors and controls all fire and security alarms in the building. Normally the building is divided into zones and a number of alarms are associated with each zone. Alarms alert a central manned control area that may pass these on to the emergency services or may respond personally. Factors, which have to be taken into account in building such a system, are: 1) If the control area is unmanned and an alarm is activated this alarm should not be ignored if it is potentially serious. Emergency services should be called automatically. 2) Some but not all parts of the building may be equipped with sprinkler systems or systems to shut down electrical equipment. These should be activated if a fire alarm is confirmed. They should not be activated if there are people in the same room. 3) The building may be equipped with direction indicators, which illuminate the route to the nearest exit. These should be activated when a fire alarm is confirmed. At the same time, an audible signal should sound alerting occupiers to leave the building. 4) A security alarm may cause some internal doors to be locked automatically. It should be possible to isolate complete zones by automatic door locking. 5) False alarms are common and it might be normal practice to have an alarm confirmed before alerting emergency services. There are different ways of confirming an alarm. In the case of a fire alarm, multiple sensors detecting a problem may confirm it. ELEMENT (1) - A Project Plan and Schedule, setting milestones, identifying resource usage, and estimated costs. The following areas should be included: - a) Produce a Project Plan addressing the areas of: o Introduction with Polar Graph supporting. o Establish Project Costs o Hardware and Software resources requirement o Work breakdown o Project schedule o Monitoring and Reporting mechanisms b) Critical Evaluation of the importance of creating a workable Project Plan. ELEMENT (2) - A Document Standard and User Manual (or appropriate document). The following areas should be included: - a) An overview regarding the relevance of quality Documentation and the part it plays within the complete Software Lifecycle. b) Produce an appropriate Product Standard for the purpose of creating uniformed Documents. c) Create an appropriate Document using your Product Standard as the yardstick (A possible candidate could be a User Manual to support the Prototype). d) Critical Evaluation regarding the importance of Standards in the Quality Assurance Process. ELEMENT (3) - A Quality Plan including a formal inspection of the User Manual (or appropriate document.) The following areas should be included: - a) Produce a Quality Plan that reflects the following sections: o Management and Organisation of the team. o Standards and Practices (including a Process Standard for the Inspection Process) o Quality Reviews and Audits including: o A description of the Formal Inspection performed against a specific Document. o Checklist o Review Form o An Inspection Report o A Defect Report. b) Critical Evaluation of your Static approach to the process of Validation and Verification. ELEMENT (4) - Create a Risk Management Strategy and selection (with justification) of appropriate Life-cycle model. The following areas should be included: - a) The following components are required to further enhance the Project Plan created in ELEMENT (1) above: o A Risk Management Strategy. o Give a brief overview of the various Life-cycle models and select with justification, the most appropriate approach for FASAM. o State the ACM/IEE Code of Ethics and explain how FASAM intends to adhere to its guidelines, including relevant examples. Need all four elements completed or can negotiate need it completed for 24/05/19