NEEDS REVISION DUE THURSDAY - 6-WBS

USA RDMV ENGINEERING PORTAL RISK MANAGEMENT PLAN TEMPLATE Revision (1) 10/09/2023 Candiss Horry

<Project Name> Version: <1.1> VERSION HISTORY The first stage of our work breakdown structure for USA RDMV Engineering Portal includes planning, defining the scope, scheduling, risk management, and working with possible plan changes. Version # Implemented By Revision Date Approved By Approval Date Reason 1.0 Candiss Horry 10/09/2023 Initial Create WBS Plan draft 2 Revision Date: 10/09/2023 USA RDMV Engineering Portal

Rev. 1 INTRODUCTION 1.1 PURPOSE OF THE PROJECT WBS The USA RDMV Engineering Portal is very important. The project will be divided into small components. Work breakdown structure subdivide project deliverables … is As one of the main outputs, making a layout that is easy for people to use is crucial for making sure that the site is easily navigable. This part includes making styles that are easy to use, adding adaptable features, and making sure the user experience is great on all devices. Database integration is another important output. This is where a lot of information about driver's licenses, car titles, and other important things is stored safely and quickly recovered. To handle large amounts of data quickly and correctly, this part needs strong server development that includes advanced information management systems. In addition, the job includes putting in place high-tech protection measures. As part of this segment's deliverables, encryption protocols, multi-factor login systems, and strict access controls will be added to protect private user data and keep the portal's integrity. Also, security tests and risk reviews are very important for making sure that the site is safe from possible online dangers. The main goal of the project is also to create a complete tool for reports and analytics. As part of this product, you will make personalized reporting tools that will help managers find insights in the data that is collected in the site. These reports help people make decisions by showing officials trends, letting them judge user behavior, and making the whole system work better. The RDMV Engineering Portal project also has an important part that has to do with following rules and regulations. As part of this group of deliverables, you must make sure that the site follows all federal and state rules, as well as data security laws and usability standards. This includes rigorous testing and validation to make sure the site follows all relevant legal standards and offers a safe and welcoming space for all users. Lastly, training and help for users are important outcomes for the project. To help both internal staff and external users understand how the site works, it's important to create detailed user guides, lessons, and support documents. Setting up a fast customer support system with helpdesk services and Frequently Asked Questions (FAQs) will also make sure that users can quickly solve any problems they have while using the site, which will increase user happiness overall. the one that defines the tasks that are dependent on each other and the task that are independent. We will be dividing the components of the project into phases. The WBS is crucial in the stage of resources and time allocation when assigning responsibilities to allow the measure and control of the project. The WBS is vital during the development stage, because it will eliminate confusion and issues down throughout the lifecycle of the project. The WBS will also allow our development team to check the deliverables with our stakeholders in order to ensure that no pieces of the deliverables are missing and that that stakeholders stakeholders are comfortable with each phase of the project. Revision Date: 10/09/2023 Page 4 Risk Management Plan Template

Rev. 2 CREATE WBS PROCEDURE 2.1 PROCESS A Work Breakdown Structure (WBS) is a method for breaking down a big job into smaller tasks and outputs that are easier to handle. Here are the steps you need to take to make a WBS for the USA RDMV Engineering Portal project: Explain the project's scope: Start by making it clear what the USA RDMV Engineering Portal project is all about. Know what the goals, aims, and limits are. Find the important people and find out what they want. This step is very important because it builds the base of your WBS. Find the main deliverables: Work closely with the project's partners to figure out what its main goals are. These are the real results or outcomes that people who have a stake in the matter expect. For the RDMV Engineering Portal, important tasks might include creating a user interface, integrating a database, putting in place security measures, a logging tool, compliance measures, and user training materials. Break down the main deliverables: Break down each big assignment into smaller jobs or sub-deliverables that are easier to handle. Take a tiered method, starting with the most important tasks at the top and breaking them down into smaller parts. As an example, jobs that fall under user interface development could include wireframing, design mockups, web development, and testing for usefulness. Include the right stakeholders: Work together with project managers, developers, artists, and subject experts to make sure that all parts of the project are covered. Get feedback from the people on the team who will be in charge of carrying out certain jobs. With their help, the goals and subtasks can be clearly defined. Use the tools and templates in WBS: To make a clear record of the breakdown structure, use project management tools or WBS files. These tools help set up jobs in a structured way, which makes it easier to handle the project and keep track of its progress. When it makes sense, include job details, relationships, tools, and estimates of how long things will take. Review and Validate: Once the WBS is made, it should be looked over by the team and key partners. Check the split structure to make sure it includes all the jobs and clears up any confusion. Changes can be made based on what people say during the review process. Set up work packages: Group jobs that are similar together to make work sets. Work packages are groups of jobs that can be given to certain people or teams. The size and complexity of these packages should be doable so that they can be easily assigned and progress can be tracked. Explain what WBS stands for: Revision Date: 10/09/2023 Page 5 Risk Management Plan Template

Rev. The need for data collection from every state in the United States is spelled out in Requirement Statement 004. It is important to note that this condition is a subtask of the main WBS part called "Data Collection and Analysis." Requirement Statement 005 describes how to analyze data and post it on the site. Because of this need, subtasks have been added to the WBS for data analysis, content creation, and site posting.  3. Participation of Stakeholders (Requirement Statements 002, Stakeholder Needs): Stakeholders want advance funds and to be able to attend important meetings, which is in line with the requirement for regular talks with Frontier (Requirement Statement 002). These parts are very important for describing WBS elements that have to do with involving stakeholders, planning finances, and making decisions.  4. Quality assurance (requirements for quality): It is very important to offer a high-quality site that is safe, secure, and works well, as shown by the quality standards. These standards for quality have a direct effect on the creation of WBS parts that are used for testing, quality assurance, and putting security measures in place.  5. Transition and Readiness (Requirements for Transition and Readiness): The transfer and preparation standards spell out how to easily switch from the old way of submitting applications to the new site. To make sure the rollout goes smoothly, this requirement leads the creation of WBS parts that deal with planning the shift, teaching users, and coming up with communication plans. The project team will be broken down into departments. Each department will have different responsibilities. Each department will be on track with the entries team regarding the various phases that the team completes as a whole. Each department will have different documentation that they are responsible for delivering throughout the project. The permitting department will be responsible for tracking and housing all permit applications, and approved permits . Phase 1:  Requirement Analysis : This will be the first phase in the portal software development. During this phase our team will create details and concise requirements. This will help the team to finalize the work within allotted timeline.  Phase 2: Feasibility Study: This phase of the portal development will include the portal requirements. During this stage we will ensure it has the following perimeters. Economic, legal, operations, technical, and scheduling.  Phase 3: Design: This stage will include the preparation of all documents so that what is expected of the project is shown. This phase will set the tone for the coding process. Phase 4: Coding: This phase is where the codes are written into units, and each coding task is assigned to a specific developer.  Phase 5: Testing: This is the stage in which our software developers will test out the functionality of the portal. The purpose of this phase is to ensure that the portal is functioning in the way in which it was created.  Phase 6: Revision Date: 10/09/2023 Page 7 Risk Management Plan Template

Rev.  Portal Installation: This is the phase in which the portal is embedded into the various US RDMV portals.  Phase 7: Maintenance: This state is where we allow the clients and customers the opportunity to use the portal. We have a feedback section where we use their feedback to make enhancements to the portal. 2.3 DECOMPOSITION The work breakdown sequence of the portal development starts with the name of the project which is the USA RDMV Engineering Portal. After the name I have broken down different components into levels. The task tasks at the lowest level are the least complex and are assigned to individuals on the team. As we go up the chart, the working system changes and the task are done as a group. This is where we work as a group and combine the components from the lower levels to come up with a more complex function. The illustration below shows a general breakdown sequence of a general software development brought to life. Missing all outputs. Scope Baseline The project scope statement, WBS, and WBS dictionary are all in the Scope Baseline, which is a complete document. It helps people make decisions about the project and acts as a guide throughout its entire lifecycle. Work Breakdown Structure (WBS) Tree Revision Date: 10/09/2023 Page 8 Risk Management Plan Template 1 . P r o j e c t M a n a g e m e n t 1 . 1 P r o j e c t P l a n n i n g 1 . 2 R i s k M a n a g e m e n t 1 . 3 Q u a l i t y M a n a g e m e n t 1 . 4 S t a k e h o l d e r M a n a g e m e n t 2 . U s e r I n t e r f a c e D e v e l o p m e n t 2 . 1 W i r e f r a m i n g 2 . 2 D e s i g n M o c k u p s 2 . 3 F r o n t e n d D e v e l o p m e n t 2 . 4 U s a b i l i t y T e s ti n g 3 . D a t a b a s e I n t e g r a ti o n 3 . 1 D a t a b a s e D e s i g n 3 . 2 D a t a M i g r a ti o n 3 . 3 D a t a b a s e T e s ti n g 4 . S e c u r i t y I m p l e m e n t a ti o n 4 . 1 E n c r y p ti o n P r o t o c o l s 4 . 2 A c c e s s C o n t r o l 4 . 3 S e c u r i t y T e s ti n g 5 . R e p o r ti n g a n d A n a l y ti c s M o d u l e 5 . 1 R e p o r t D e s i g n 5 . 2 D a t a A n a l y s i s 5 . 3 R e p o r t G e n e r a ti o n 6 . C o m p l i a n c e a n d R e g u l a t o r y M e a s u r e s 6 . 1 L e g a l C o m p l i a n c e 6 . 2 A c c e s s i b i l i t y S t a n d a r d s 6 . 3 C o m p l i a n c e T e s ti n g 7 . U s e r T r a i n i n g a n d S u p p o r t 7 . 1 U s e r G u i d e s C r e a ti o n 7 . 2 T r a i n i n g W o r k s h o p s 7 . 3 H e l p d e s k S e t u p

Rev.  WBS dictionary – is a document that provides detailed deliverable, activity, and scheduling information about each component of the WBS. Here you will insert your WBS dictionary using the following format. 2.3.1 Project Document Updates Project documents that may be updated as a result of carrying out this process include but are not limited to:  Assumptions log – updated with additional assumptions or constraints that were identified in the WBS process. Revision Date: 10/09/2023 Page 10 Risk Management Plan Template

Rev.  Requirements documentation – requirements documentation may be updated to include approved changes resulting from the create WBS process. Requirements Traceability Matrix (RTM) Update Requirement ID Requirement Description WBS Number REQ-001 User interface should be intuitive and responsive. 2 REQ-002 System should comply with data protection laws. 4.1 REQ-003 Monthly tests to be conducted to ensure portal functionality. 4.3 REQ-004 Transition plan should be communicated 90 days prior to roll-out. 6 REQ-005 Portal must be visible on all U.S. state portals. 7 REQUIREMENTS TRACEABILITY MATRIX Project Name: USA RDMV ENGINEERING PORTAL Project Manager Name: Candiss Horry Project Description: A U.S based portal that will be used to submit all state RDMV permitting applications, The portal will also house information, laws, and requirements for each state located in the United States of America. ID Assoc ID Requirement s Description Business Needs, Opportunities, Goals, Objectives Project Objecti ves WBS Delivera bles Produ ct Desig n Product Develop ment Te st C as es 001 1.1.1 Gather all jurisdiction permit requirements Goal: We will gather all the information needed in order to build the portal. X X X X 002 2.2.2 Create a software for each state portal. Goal: Create a portal that will house all U.S RDMV applications, and information. X X X X 003 3.3.3 Create the Project Team. Goal: Establish a team of top performing engineers. X X X X 004 4.4.4 Hire internally for the Project Team. Goal: We will be able to create a team of people that are familiar with not only the project details, but also our stakeholders as well. X X X Revision Date: 10/09/2023 Page 11 Risk Management Plan Template

Rev. CREATE WBS PLAN APPROVAL The undersigned acknowledge they have reviewed the Create WBS Plan for the USA RDMV Engineering Portal project. Changes to this Plan will be coordinated with and approved by the undersigned or their designated representatives. Signature: Candiss Hory Date: Print Name: Candiss Horry Title: A&R Engineering Firm Sr. Project Manager Role: Sr. Project Manager Signature: Date: Print Name: Joseph Hanger Title: Frontier Director of Operations Role: Sponsor Signature: Date: Print Name: Robert Dawson Title: Frontier Director of Engineering Operations Role: Sponsor Signature: Date: Print Name: Title: Role: Revision Date: 10/09/2023 Page 13 Risk Management Plan Template

Rev. APPENDIX A: REFERENCES The following table summarizes the documents referenced in this document. Document Name and Version Description Location 5.5 Create WBS Plan [USA RDMV Engineering Portal Collect Requirements USARDMVENGINEERINGP ORTAL.COM Revision Date: 10/09/2023 Page 14 Risk Management Plan Template