In your final project, you will revise and compile each part of the final projec
ID: 3824721 • Letter: I
Question
In your final project, you will revise and compile each part of the final project that you have been working on. Submit your final Portfolio Project with the following components:
Project preparation and project charter (Remember you’re your project charter will not be graded again.)
Project scope management plan and WBS
Communication management plan
Project risk and change management plans
Quality management plan
Project closure plan.
In addition, also include the following elements:
An executive summary that offers a high-level description of the project you have developed.
A conclusion that includes a self-assessment as a project manager assigned to this IT project. Address key elements you identified in throughout the project, and identify additional areas that you think have benefitted you and contributed to the success of your project.
Explanation / Answer
Introduction
Purpose
Purpose of the project
Emergency Response System is to be the only system that in event of emergency or crisis, the airlines to efficiently manage execution of the entire crisis management activity. This application enables the airlines to initiate crisis, notify concerned staff, follow-up availability with the support team at the operation area, provide ready reference of data to support inquiries from NOK (Next of Kin) of PDA (Persons Directly Affected), regular updates PDA’s (passenger or crew or others) status and aligns PDAs with NOKs, update cargo status, generate reports and facilitates stand-down of the crisis.
Purpose of the document
The purpose of the document is to capture the business requirements of Emergency Response System. This document ensures the envisaged requirements are comprehended well by Indigo project team, TCG Digital solution architects, developers and quality assurance team and other related stakeholders to accurately transform the business requirements into system requirements, design and code.
Document Conventions
The document categorizes the high level scope in functional modules and each module is elaborated individually. The overall business flow diagram provides a link across all the functional modules. The legends for BPM notification are explained in section 7 of the document.
Intended Audience
The intended audience for this document are:
Business users
Solution Architects
Developers
Operation Support Group
Testing team
Project Scope
Following are the list of functional modules and their corresponding availability over different devices:
Functional Modules Web Mobile and Tablet
(iOS & Android only)
Emergency Initiation Management
Emergency Notification Management
Data feed Management
Call Center Management
Demand Management (with offline data sync)
Checklist Management (with offline data sync)
Emergency Stand-down
Peace time management
User Management
Login Authentication and Authorization
Message broadcasting (with offline data sync)
Scope Exclusions
Success Criteria
Project Success Criteria
As part of the formal process to transition from development into production stakeholders must be satisfied that the business requirements are appropriately addressed.
UAT Success Criteria
Based on the UAT Test cases (to be provided by IndiGo), following severity matrix and priority matrix are to be maintained for Go-live.
UAT Bug Severity Defect Count Severity Description
Severity 1 0 System aborts without a business workaround. This is normally associated with system crashes that make the system unusable. The system or an entire business function is down or inoperable and it prevents further execution
Severity 2 0 System does not adhere to the requirements; serious errors in results or the performance is substantially degraded. But business workaround exists
Severity 3 0 – 10 These types of defects are generally tolerable or deferrable, such as errors in format of displays or printouts
Severity 4 0 – 15 An improvement suggestion, which is not a defect and does not prevent the system from functioning
UAT Bug Priority Defect Count Priority Description
Priority 1 0 Blocker, critical or showstopper defects. Entire functionality is blocked or a feature is unusable with no workaround, no testing can proceed as a result of this.
Priority 2 0 Main feature or functionality is incorrect and does not adhere to the requirements, but workaround is available, performance issues, regression issues, environmental issues and important UI errors related to branding.
Priority 3 0 – 5 Minor functionality is incorrect but workaround is available, cosmetic errors not related to branding.
Priority 4 0 – 10 Minor cosmetic errors, improvement suggestions which does not impact the functionality in any way.
Abbreviation Description
ERS Emergency Response System
PDA Passenger Directly Affected
PNL Passenger Name List
NOK Next Of Kin
IP Interested Party
ERM Emergency Response Management
SMS Short Messaging Services
SPOC Single Point Of Contact
AMOS Aircraft Maintenance Operations Simulation
AIMS Airplane Information Management System
OCC Operation Control Center
HRMS Human Resource Management System
ESB Enterprise Service Bus
AOCS Airport Operation and Customer Service
Other Notes
Role Hierarchy
The ERS system will be having a role hierarchy of 2 levels as follows:
Level Role Name Role description
Level 1 Super Admin This role will be having all the controlling privileges of the ERS system. The two departments that will be specifically mapped to this role are ERM and ERC.
Level 2 ERS Users All other departments, who will be accessing the ERS system, for example: In-flight Services, Call Center, Flight Safety etc., will be categorized under this role.
Department Hierarchy
The ERS system will be having a department hierarchy of 2 levels as follows:
Level Hierarchy Name Description
Level 1 Department The parent department, for example OCC. When demands from one department are assigned to other departments, only the department name will be visible.
Level 2 Sub-department Parent departments may or may not have sub-departments. For example, for OCC as parent department, sub-departments can be Dispatchers, Logistics etc.,
Functionality Access mapping
Following are the different functional activities which will be made configurable for access rights modification for different departments created.
Module Functionality
Emergency Initiation Management Emergency Initiation
Emergency Notification Management Select departments & initiate notify
Data feed Management Excel upload for persons directly affected
Excel upload for cargo directly affected
Excel upload for crew directly affected
Excel upload for flight schedule
Excel upload for on-board IndiGo passengers
Excel upload for flight maintenance records
Excel upload for flight weight and balance records
Excel upload for support member training records
Verify passenger manifest
Verify cargo manifest
Call Center Management Search for affected persons and cargo items
Update caller details
View activity details against a ticket number
Update activity details against a ticket number
Fine tune messages that can be communicated to NOKs
Media Management View media queries
Publish press release
Publish President’s message
Demand Management View department specific demands
Raise department specific demands
Approve demands that require approval
Checklist Management View and update own-department specific checklists
View sub-department (of own department) checklists
Emergency Stand-down Submit own-department specific closure reports
Close or terminate emergency
Peace time management Update own-department specific checklist
Update all department’s checklist
Update master data for departments
Update master data for functionality access mapping
Update master data for emergency types
Update master data for demand types
Update master data for event specific notification template
Open archived incidents for attachment uploads
Upload own-department specific lessons learnt
Upload all department’s lesson learnt
Upload incident specific reports for archived incidents
Close archived incidents for attachment uploads
User Management Activate support members and assign roles
Login Authentication and Authorization Unlock user account
Appendix A: Assumptions and Dependencies
Assumptions
Appendix B: Business Risks
None identified at this stage of the project. Introduction
Purpose
Purpose of the project
Emergency Response System is to be the only system that in event of emergency or crisis, the airlines to efficiently manage execution of the entire crisis management activity. This application enables the airlines to initiate crisis, notify concerned staff, follow-up availability with the support team at the operation area, provide ready reference of data to support inquiries from NOK (Next of Kin) of PDA (Persons Directly Affected), regular updates PDA’s (passenger or crew or others) status and aligns PDAs with NOKs, update cargo status, generate reports and facilitates stand-down of the crisis.
Purpose of the document
The purpose of the document is to capture the business requirements of Emergency Response System. This document ensures the envisaged requirements are comprehended well by Indigo project team, TCG Digital solution architects, developers and quality assurance team and other related stakeholders to accurately transform the business requirements into system requirements, design and code.
Document Conventions
The document categorizes the high level scope in functional modules and each module is elaborated individually. The overall business flow diagram provides a link across all the functional modules. The legends for BPM notification are explained in section 7 of the document.
Intended Audience
The intended audience for this document are:
Business users
Solution Architects
Developers
Operation Support Group
Testing team
Project Scope
Following are the list of functional modules and their corresponding availability over different devices:
Functional Modules Web Mobile and Tablet
(iOS & Android only)
Emergency Initiation Management
Emergency Notification Management
Data feed Management
Call Center Management
Demand Management (with offline data sync)
Checklist Management (with offline data sync)
Emergency Stand-down
Peace time management
User Management
Login Authentication and Authorization
Message broadcasting (with offline data sync)
UAT Success Criteria
Based on the UAT Test cases (to be provided by IndiGo), following severity matrix and priority matrix are to be maintained for Go-live.
UAT Bug Severity Defect Count Severity Description
Severity 1 0 System aborts without a business workaround. This is normally associated with system crashes that make the system unusable. The system or an entire business function is down or inoperable and it prevents further execution
Severity 2 0 System does not adhere to the requirements; serious errors in results or the performance is substantially degraded. But business workaround exists
Severity 3 0 – 10 These types of defects are generally tolerable or deferrable, such as errors in format of displays or printouts
Severity 4 0 – 15 An improvement suggestion, which is not a defect and does not prevent the system from functioning
UAT Bug Priority Defect Count Priority Description
Priority 1 0 Blocker, critical or showstopper defects. Entire functionality is blocked or a feature is unusable with no workaround, no testing can proceed as a result of this.
Priority 2 0 Main feature or functionality is incorrect and does not adhere to the requirements, but workaround is available, performance issues, regression issues, environmental issues and important UI errors related to branding.
Priority 3 0 – 5 Minor functionality is incorrect but workaround is available, cosmetic errors not related to branding.
Priority 4 0 – 10 Minor cosmetic errors, improvement suggestions which does not impact the functionality in any way.
Overall Business Flow Diagram
Nonfunctional Requirements
ERS Emergency Response System
PDA Passenger Directly Affected
PNL Passenger Name List
NOK Next Of Kin
IP Interested Party
ERM Emergency Response Management
SMS Short Messaging Services
SPOC Single Point Of Contact
AMOS Aircraft Maintenance Operations Simulation
AIMS Airplane Information Management System
OCC Operation Control center
HRMS Human Resource Management System
ESB Enterprise Service Bus
AOCS Airport Operation and Customer Service
Symbols used in business flow diagrams
Symbol Meaning Symbol Meaning
The control will wait at this point till the time all other activities are complete. From this point, only one activity will get activated based on respective conditions.
From this point, all of the subsequent activities will simultaneously start. Intermediate task within a process flow, which may or may not impact the main business flow.
The control will not wait for all the activities to complete. Common task is initiated for any of the activities. Sub task. The detailed of that task or functional module is explained in other section of the document.
From this point, any one of the activity or all of the activities can start simultaneously. Conditional activity. If the condition is not met, then the subsequently associated task will be skipped.
Appendix B: Business Risks
None identified at this stage of the project.