Academia.eduAcademia.edu

Figure 6 – uploaded by IJCSMC Journal

See full PDFdownloadDownload figure
7 depicts the FEAP ERD. Figure 7: FEAP Entity Relationship Diagram (representing relationship), oval shape (representing attributes), association relationship, and cardinality. Figure

Figure 7 7 depicts the FEAP ERD. Figure 7: FEAP Entity Relationship Diagram (representing relationship), oval shape (representing attributes), association relationship, and cardinality. Figure

Related Figures (12)

(Fishbone) diagram to analyze and highlight the possible root causes for the problem as shown in Figure /. A requirement is simply a statement of what the system must do for the user or what characteristics it needs to system is expected to have five users as follows: Regular User, Area Manager, Top Manager, FEE, FED Admin.
(Fishbone) diagram to analyze and highlight the possible root causes for the problem as shown in Figure /. A requirement is simply a statement of what the system must do for the user or what characteristics it needs to system is expected to have five users as follows: Regular User, Area Manager, Top Manager, FEE, FED Admin.
Table 1: Functional Requirements This describes the functionality of the system that will enable users to accomplish their tasks.
Table 1: Functional Requirements This describes the functionality of the system that will enable users to accomplish their tasks.
Table 2: Nonfunctional Requirements
Table 2: Nonfunctional Requirements
Figure 2: FEAP Use case Diagram scenario or event for which the FEAP must provide a defined response [14]. Figure 2 shows the FEAP use case analysis modeling tools for identifying and expressing the functional requirements. Each use case is a business
Figure 2: FEAP Use case Diagram scenario or event for which the FEAP must provide a defined response [14]. Figure 2 shows the FEAP use case analysis modeling tools for identifying and expressing the functional requirements. Each use case is a business
messages, and object destructor that end the lifeline of inexistence object [10]. Figure 3 depicts the report fire Captures the dynamic view of FEAP [15]. It illustrates how several objects collaborate to get a task done. It als Depicts the sequence of events and interactions that occurs between an actor and objects over time in
messages, and object destructor that end the lifeline of inexistence object [10]. Figure 3 depicts the report fire Captures the dynamic view of FEAP [15]. It illustrates how several objects collaborate to get a task done. It als Depicts the sequence of events and interactions that occurs between an actor and objects over time in
Figure 4: Report Fire Collaboration Diagram
Figure 4: Report Fire Collaboration Diagram
to be kept. Figure 5 depicts the Class diagram of the FEAP. [16]. In class diagram, the classes are either actors (noun that interact with the FEAP) or information that need Illustrate FEAP behavior across several use cases in response to external stimulus. It models the change in state
to be kept. Figure 5 depicts the Class diagram of the FEAP. [16]. In class diagram, the classes are either actors (noun that interact with the FEAP) or information that need Illustrate FEAP behavior across several use cases in response to external stimulus. It models the change in state
prototypes designed using Figma [18], an online tool due to its usability, scalability and collaborative nature. The User Interface design defines how the FEAP will interact with users to get input, process it and display the
prototypes designed using Figma [18], an online tool due to its usability, scalability and collaborative nature. The User Interface design defines how the FEAP will interact with users to get input, process it and display the
Figure 9: FED Admin Mobile Prototype View
Figure 9: FED Admin Mobile Prototype View
Figure 10: FEE, Area, and Top Manager Prototype GUI
Figure 10: FEE, Area, and Top Manager Prototype GUI
Figure 11: FED Admin Dashboard for Desktop/Tablet Prototype GUI
Figure 11: FED Admin Dashboard for Desktop/Tablet Prototype GUI
Related topics:
Computer ScienceInformation TechnologyTechnologyFire and Emergency ServicesWireless Networks (Computer Science)Mobile application developmentMobile appsGraphical User InterfacesComputer Science and Information TechnologyComputer Science Engineering
580 California St., Suite 400
San Francisco, CA, 94104
© 2025 Academia. All rights reserved