please follow all instructions on the file uploaded, don't leave anything half done i need it fully done and then all documented after
Extended Business Programming Repeat Assessment This project involves working with all aspects of C# covered so far using Visual Studio. You must use at least 1 of each of the following in your solution: • Multiple Data types • Multiple forms with multiple types of controls • 2-dimensional array • Selection (if-statement or switch-statement). • Iteration (any type of loops). • Naming conventions for controls, classes, forms, methods, variables, etc must all follow the standard convention. You will have to explain your code to your lecturer in a scheduled meeting via MS Teams. Outline Create a new C# Windows Forms App project called YourNameRepeat, for example if I were naming mine, I would call it ElaineTynanRepeat. Follow the instructions to create a project that allows you to store, view, edit, add and delete details in a phone directory. The project will emulate a database project, but instead of using a database you will use a 2-dimensional string array. Because we are not using a database the data will not persist, which means that each time you run the application you will have to load in new data. The data must persist from one screen to the next (this can be done by making the 2D array a public static variable in the Menu form and accessing it from all other forms). The data to be stored about a contact is their name and phone number. The project will have a menu screen and screens to view, add, edit and delete contacts. The screens for view, add, edit and delete can all be done in 1 form or 4 separate forms. There will be extra marks for doing it in 1 form. The below forms are suggested layouts and may be modified if you prefer to create your own designs. Extended Business Programming Notes: • To make the buttons appear like a link to click on you can set the FlatStyle of the button, in properties to Flat, set the BorderSize in the FlatAppearance to 0 and set the BackColor to Control, the same as the form BackColor. • The one screen can be used for view, edit, add & delete by hiding/showing the appropriate buttons when the form is loaded. • After changes are made to the contact details the form will have to be refreshed to see the changes. This consists of loading the data into the list again as well as clearing any text boxes, etc. It would be wise to create a refresh method to do this. • Be sure your output is formatted into columns as per the image above. Some fonts are monospaced, or fixed width. Others are not and therefore 20 spaces will be different depending on the width of the characters. For example, w takes up more space than i. If you want to get proper formatting use a font that is monospaced. Some examples of monospaced fonts are Courier and Consolas. • There should be validation on operations where suitable. For example, you should not be allowed to add a blank name or phone number. Steps: 1. When the application is run the Menu Screen should be shown. 2. Each link/button on the main menu should take you to the correct screen option. View 3. The view screen should display a list of all contacts. There should be no blank lines loaded into the list. When a contact is selected their details should be loaded into text boxes or something similar, to allow for closer inspection. Extended Business Programming Add 4. The view screen should display a list of all contacts. There should be no blank lines loaded into the list. When a contact is selected their details should be loaded into text boxes or something similar, to allow for closer inspection. 5. When the user types in the text boxes they should be able to add the contact to the Phone Directory. 6. When the user clicks the add button, the user should be presented with a message box asking them if they are sure they want to add the contact. If they click No/Cancel, the details should not be added, if they click Yes/OK the details should be added unless the directory (the 2D array) is full, in which case the user should be notified of this. Edit 7. The edit screen should display a list of all contacts. There should be no blank lines loaded into the list. When a contact is selected their details should be loaded into text boxes or something similar, to allow the user to make changes. 8. When the user types in the text boxes they should be able to edit the selected contact. The changes should be reflected in the Phone Directory (2D array). 9. When the user clicks the save button, the user should be presented with a message box asking them if they are sure they want to edit the contact. If they click No/Cancel, the details should not be changed, if they click Yes/OK the details should be edited. Delete 10. The delete screen should display a list of all contacts. There should be no blank lines loaded into the list. When a contact is selected their details should be loaded into text boxes or something similar, to allow the user to inspect the contact to be deleted. 11. When the user clicks the delete button, the user should be presented with a message box asking them if they are sure they want to delete the contact. If they click No/Cancel, the details should not be removed, if they click Yes/OK the details should be removed from the 2D array. No blank lines should be left in the middle of the array. Exit 12. When the Exit button is clicked close the form. Testing Create a word document called TestCasesRepeat.docx, complete it with the test cases for any one method in your code. This document should be filled out before you start to write the test code. Please spend some time thinking about and doing this as this will determine whether you write good test code or not. You must read the code and think of the possible types of input a user could pass into the method. Some sample input types are valid, boundary, invalid, positive, negative, null, 0, etc. Extended Business Programming Write a test for each of these types of tests in the same format as shown. This document should be saved in the project solution folder and uploaded with the assessment. Follow the instructions given in the notes on moodle titled 08 UnitTestingVisualStudio to add a test project to your project. Run the test. If any if the tests fail, go back to the code and fix it so that they all pass. The assignment submission should include the project, the test project and the Test Case document. Note: Try to do as much of this as possible. The more you do, the better your marks will be. Zip your project folder (should be named RepeatMyName, e.g. Repeat ElaineTynan) and upload it at the link called Repeat Autumn Assessment Upload on the Extended Business Programming moodle page. The assessment is due no later than Sunday August 15th 2021 at 23:59. You will be invited to meet with your lecturer on MS Teams to explain your code.