Hello I am getting a java.util.NoSuchElementException when i declare third variable inside my while loop ? why is that and can you fix that issue ?? I will be using around 5 to 6 different variables but at the moment it only allows me to add 2 inside the while loop When i add more thant 2 variables i get an error at runtime . This java code is suppose to read certain text lines from a text file .

import java.io.*;

import java.util.Scanner;

public class SortingText {

public static void main(String[] args) throws IOException {

File file = new File("input.txt");

try {

Scanner sc = new Scanner(file);

int found=0;

String result=" ";

String results=" ";

String resultsB=" ";

String resultsA= " ";

while (sc.hasNext()) {

String i = sc.next();

String b = sc.next();

String a = sc.next();

if(i.equals("2.1.1")) found=1;

if(i.equals("2.1.2")) found=0;

if(found==1) result+=i+" ";

// calculating when to start and stop copying code.

if(b.equals("2.1.8")) found = 1;

if(b.equals("2.2.7")) found = 0;

if(found == 1)results+= b + " ";

}

sc.close();

FileWriter fw = new FileWriter("output5.txt");

BufferedWriter bw = new BufferedWriter(fw);

bw.write(result);

bw.write(results);

bw.write(resultsA);

System.out.println(results);

System.out.println(" ");

System.out.println(result);

System.out.println(resultsB);

bw.close();

}

catch (FileNotFoundException e) {

e.printStackTrace();

}

}

}

the text file is :

2. Lessons Learned

2.1 Key Learnings and Recommendations per Key Performance Indicators

In this section capture key learnings and recommendations from the project as they relate to the Key Performance Indicators. For each Key Performance Indicator capture what worked well and went well along with what could have been improved. Lastly capture any lessons learned that can be leveraged for future projects, focus on aspects which will help you and others in future projects. If there is no take away or learning worth mentioning in terms of knowledge transfer for a specific phase, move on to the next one.

2.1.1 Stakeholder Management & Engagement

Stakeholder Management & Engagement

What worked well?

What were the resulting benefits?

Communications with the vendor worked well in that we had various contact methods (phone, email, text) and the vendor always quickly responded, including evenings and weekends. The benefits were that there was no delay in getting responses when they were needed quickly.

What could have been improved?

What were the resulting impacts?

Stakeholders changed mid-way through the project. Craig was the original stakeholder, Kathy was the original team lead. Both changed job responsibilities in the course of the project. Handoff of responsibilities could have been handled better. The resulting impact was that the new sponsor was not fully up to speed when taking on sponsor role; it took longer than necessary to fully understand the expectations and project goals and deliverables.

Future Recommendations/ Lessons Learned

* Validate that the onboarding sponsor is fully up to speed regarding the project.

* If necessary, work with the Executive Sponsor to address perceived risks of resource changes

* If needed, conduct a sponsor interview with the onboarding sponsor to ensure expectations are being met and coordinate any knowledge transfer needed

2.1.2 Scope Management & Change Management

Scope Management & Change Management

What worked well?

What were the resulting benefits?

The project scope of purchasing and installing upgraded software, and providing end user training, did not change. The resulting benefit was not having to deal with scope creep.

What could have been improved?

What were the resulting impacts?

In the course if the Quick Start training, best practices to get the most of the new software discovered that file structures and data needed to be adjusted. This resulted in a Change Request filed for the project to be conducted outside of the project itself.

Future Recommendations/ Lessons Learned

The changes to the file structure and data could have been discovered in the early stages of the project, such as discovery when the vendor marketing team presented to Farmers. This could have uncovered the need for file format and data changes, allowing these changes to be included within the scope of the project. The vendor is making changes to their process, which is to include the software administrator to be part of the upfront Marketing team to better evaluate the needs of the client and assist with the ROM process if IT work is needed.

2.1.3 Communication

Communication

What worked well?

What were the resulting benefits?

The Project Administrator team (Tony and Nick) were excellent communicators during the three day Quick Start process. The resulting benefits allowed the IT and End User team to understand and take action of what is needed to get the most out of the Lexis Nexis software.

The Status updates for the Sponsor/Executive sponsor and team were well balanced. The information was not too much or too little and provided good information regarding project status.

What could have been improved?

What were the resulting impacts?

The Vendor Marketing team did not effectively communicate that additional costs would be in scope for the ROM and Business Expenses, such as vendor travel for the Quick Start process and possible IT costs for file and data adjustments. The resulting impact was that the CAP funding was already approved and in progress when the new cost discoveries came to light during the training and implementation phase of the project.

Future Recommendations/ Lessons Learned

Provided that the PM is on board during the ROM process, a future recommendation is to verify with the vendor if additional costs should be included in the ROM and CAP process. Possibly create a checklist to review with the vendor to check for hidden costs that may be discovered during the training, testing and implementation process.

2.1.4 Risk and Issues Management

Risk and Issues Management

What worked well?

What were the resulting benefits?

Risks and Issues were identified throughout the course of the project. They were updated in the Risk and Issue log and addressed on a regular basis. Mitigation plans for identified and applied for issues that became realities.

What could have been improved?

What were the resulting impacts?

N/A

Future Recommendations/ Lessons Learned

N/A

2.1.5 Capture and Management of Approvals

Capture and Management of Approvals

What worked well?

What were the resulting benefits?

Approvals for the CAP were completed on time. Admin Assistants within Compliance were very helpful in getting signatures on short notice. The results benefits were that we met the deliverable dates for CAP approvals.

What could have been improved?

What were the resulting impacts?

N/A

Future Recommendations/ Lessons Learned

N/A

2.1.6 Deployment Planning

Deployment Planning

What worked well?

What were the resulting benefits?

The IT SME and Lead created a good basic Project Plan that identified the tasks needed leading up to and including deployment. The benefits were that we had a basic plan that was easily adjusted when needed due to deliverable delays.

What could have been improved?

What were the resulting impacts?

Deployment in general was delayed due to a delay in obtaining and configuring the server. The SOW was delayed due to losing a resource during the project and the time delay in getting the replacement resource up to speed and finalizing the SOW. The resulting impacts were delays in project implementation. The original plan was to have the software up and running for the Q1 OFAC processing. Due to delays, we had to run Q1 processing using the legacy software, as well as Q2.

Future Recommendations/ Lessons Learned

No net new recommendations. Continue to develop a mitigation plan for delays and issues and apply the plan if needed.

2.1.7 Remaining on Project Budget

Remaining on Project Budget

What worked well?

What were the resulting benefits?

On a whole, the project budget was successful. The costs identified for business and IT against the ROM was accurate. The resulting benefits were that we did not come up short for in scope project costs.

What could have been improved?

What were the resulting impacts?

The accounting treatment applied to the CAP did not allow for costs to be pushed over to 2017 for IT. Also, since the software licensing costs were split between 2017 and 2018 (April to April) the costs needed to be amortized. While this did not directly impact the success of the project, it did result in a need to extend the I/O to March 31, 2018.

Future Recommendations/ Lessons Learned

* Ensure the CAP Accounting has the correct accounting treatment applied

2.1.8 On-Time Delivery

On-Time Delivery

What worked well?

What were the resulting benefits?

While the project was successfully delivered, it missed the original planned delivery date.

What could have been improved?

What were the resulting impacts?

The project plan was to complete the software installation in time to run Q1 OFAC processing in parallel with the existing and new software. (Feb, 2017). Due to delays described in other sections of this document, the delivery was delayed to April, 2017.

Future Recommendations/ Lessons Learned

None identified

2.2 Key Learnings and Recommendations per Project Life Cycle Phase

In this section capture key learnings and recommendations from the project as they relate to the various project phases. During the various phases of the project consider what went well, what didnt go well, what would you do differently the next time? What are key take aways and learnings from the specific project phases? Focus on aspects which will help you and others in future projects. If there is no take away or learning worth mentioning in terms of knowledge transfer for a specific phase, move on to the next one.

2.2.1 Conceptualization Phase

Conceptualization Phase

What worked well?

What were the resulting benefits?

All deliverables needed for Conceptualization were completed on time. The results benefits were that the project moved forward on schedule.

What could have been improved?

What were the resulting impacts?

Nothing identified

Future Recommendations/ Lessons Learned

Nothing identified

2.2.2 Initiation Phase

Initiation Phase

What worked well?

What were the resulting benefits?

All deliverables required for Initiation were completed on time, resulting in CAP funding approval.

What could have been improved?

What were the resulting impacts?

The CAP process is long and can be confusing. The many steps and approvals required to CAP, as well as the long time periods for deliverables to be completed, is complicated. The resulting impact is that the CAP experience can result in confusion and frustration to stakeholders.

Future Recommendations/ Lessons Learned

* Create a simple document explaining the CAP process for stakeholders and include this when working with Sponsors and Stakeholders (for CAP projects).

2.2.3 Analysis and Design Phase

Analysis and Design Phase

What worked well?

What were the resulting benefits?

The project SME is an expert in OFAC processing and was able to work with the vendor and stakeholders in the Analysis and Design for the upgraded software. The resulting benefits were that that this phase of the process went smoothly.

What could have been improved?

What were the resulting impacts?

None identified

Future Recommendations/ Lessons Learned

None identified

2.2.4 Development Phase

Development Phase

What worked well?

What were the resulting benefits?

N/A due this being a software upgrade for an existing product, no net new development was required.

What could have been improved?

What were the resulting impacts?

N/A

Future Recommendations/ Lessons Learned

N/A

2.2.5 Testing Phase

Testing Phase

What worked well?

What were the resulting benefits?

The initial testing was done during the quick start process. The resulting benefits were that the testing was done in a controlled environment within both the test and production environments. This allowed for efficient testing with many experts available to validate or identify needed changes based on testing results.

What could have been improved?

What were the resulting impacts?

Testing will continue to occur after the project officially closed due to a change request for file formatting. The resulting impact is that more time is required of the Compliance team.

Future Recommendations/ Lessons Learned

None identified

2.2.6 Implementation Phase

Implementation Phase

What worked well?

What were the resulting benefits?

The software was able to be installed prior to the Quick Start process. This allowed the Quick Start process to being as planned without any delays. The Quick Start process allowed us to validate the application and identified any changes for best results from the OFAC processing.

What could have been improved?

What were the resulting impacts?

None identified

Future Recommendations/ Lessons Learned

None identified

2.2.7 Post Implementation Phase

Post Implementation Phase

What worked well?

What were the resulting benefits?

None identified

What could have been improved?

What were the resulting impacts?

None identified

Future Recommendations/ Lessons Learned

None identified

2.3 Recommendations in general and opportunities for future value creation

In this section describe key learnings and recommendations resulting from the project implementation in general that have not been captured above. Focus on the background of the project, the organizational setting and the change or improvement achieved through the project.

Include key findings on personnel resource management (e.g. how was work load managed with available skill set, was there a shift in amount of work outsourced).

Highlight which actions supported you in driving project implementation and how these recommendations foster knowledge transfer and can potentially create value for other projects.

1

2

3

4

No additional recommendations outside of the content within this document.

POST IMPLEMENTATION REVIEW FORM

INTERNAL USE ONLY 2

package readingtext; Sorting Text [Java Application] /Library/Java/JavaVirtualMachines/idk 1.8.0_121.jdk/Contents/Home/bin/ja Exception in thread "mann java util.NoSuchElementException import java.io.*; at java.util.Scanner.throwFor Scanner.java:862) at java.util.Scanner.next at readingtext.SortingText.main SortingText.java:27) S import java.util.Scanner 7 public class SortingText [ public static void main(string .2 .3 .5 .9 20 25