use C++ for implementation

In this program we are working with stacks. A stack is a great abstraction for providing your data in the opposite order than it was entered. So, we will use a stack to help The user creates their resume! The client application will obtain all of the job experiences from the user in the order that they took place. So, at age 17, I worked at McDonalds (surve, cook )-that was my first job so it would be entered first. At 20, I was an intern at intel. That was my second job; it would be entered next. And so on. Then, when it is time to send your resume, The prospective employer wants to know the most recent job first, and so on. We will build a Stack ADT. Building the ADT: It is important to provide a complete implementation of a Stack ADT and provide for all functionality: 1. The information kept about jobs, clubs or other responsibilities for your resume (this can be implemented using a struct or a class): a. The name of the employer or club b. The start and end dates c. The job title d. A list of responsibilities 2. The ADT functions to be supported should include: a. Constructor/Destructor b. Push a job experience. Pop a job experience c. Peek, to receive information about the most recent job experience d. Display the contents of the stack . Please keep in mind that because we are creating ADTS, the user of the program must not be aware that a stack is being used. However, the client program knows that they are using this ADT. Make sure to thoroughly test each of the stack functions from the client program! This will require a user interaction with a menu interface from your client program. Do not hard-code the test conditions. Programming - Data Structures: The stack should be implemented using a linear linked list of arrays, where each element in the array is a job experience. The array must be dynamically allocated and each array must be of the same size. I recommend that the arrays be relatively small (e.g., 5) so that you can properly test the code. The job experience may be implemented as a struct or a class. Your choice! The idea of your client program is to test out your ADT functionality so that a real application can be developed off site by another team of Software Engineers based on the ADT public functions. You want to make sure that your stack ADT performs well! Things you should know...as part of your program: 1) Do not use statically allocated arrays in your classes or structures used by the ADT. 2) All data members in a class must be private 3) Never perform input operations from your class 4) Global variables are not allowed in 5) Global constants are great! 6) Do not use the String class! (use arrays of characters instead!) You may use the cstring library. 7) Use modular design, separating the .h files from the .cpp files. Remember, .h files should contain the class header and any necessary prototypes. The.cpp files should contain function definitions. Never #include" .cpp files! In this program we are working with stacks. A stack is a great abstraction for providing your data in the opposite order than it was entered. So, we will use a stack to help The user creates their resume! The client application will obtain all of the job experiences from the user in the order that they took place. So, at age 17, I worked at McDonalds (surve, cook )-that was my first job so it would be entered first. At 20, I was an intern at intel. That was my second job; it would be entered next. And so on. Then, when it is time to send your resume, The prospective employer wants to know the most recent job first, and so on. We will build a Stack ADT. Building the ADT: It is important to provide a complete implementation of a Stack ADT and provide for all functionality: 1. The information kept about jobs, clubs or other responsibilities for your resume (this can be implemented using a struct or a class): a. The name of the employer or club b. The start and end dates c. The job title d. A list of responsibilities 2. The ADT functions to be supported should include: a. Constructor/Destructor b. Push a job experience. Pop a job experience c. Peek, to receive information about the most recent job experience d. Display the contents of the stack . Please keep in mind that because we are creating ADTS, the user of the program must not be aware that a stack is being used. However, the client program knows that they are using this ADT. Make sure to thoroughly test each of the stack functions from the client program! This will require a user interaction with a menu interface from your client program. Do not hard-code the test conditions. Programming - Data Structures: The stack should be implemented using a linear linked list of arrays, where each element in the array is a job experience. The array must be dynamically allocated and each array must be of the same size. I recommend that the arrays be relatively small (e.g., 5) so that you can properly test the code. The job experience may be implemented as a struct or a class. Your choice! The idea of your client program is to test out your ADT functionality so that a real application can be developed off site by another team of Software Engineers based on the ADT public functions. You want to make sure that your stack ADT performs well! Things you should know...as part of your program: 1) Do not use statically allocated arrays in your classes or structures used by the ADT. 2) All data members in a class must be private 3) Never perform input operations from your class 4) Global variables are not allowed in 5) Global constants are great! 6) Do not use the String class! (use arrays of characters instead!) You may use the cstring library. 7) Use modular design, separating the .h files from the .cpp files. Remember, .h files should contain the class header and any necessary prototypes. The.cpp files should contain function definitions. Never #include" .cpp files