I'm not getting the output. it showings error I think there is some error in my computer. please run code at your side and send me the screenshots For connection, you have to use the same code as demo example code through that code we can access the university database. "I really would like to say thank you for all that you have done to assist me with keeping my stress levels low. Working with you guys is always soothing. thank you so much. good handled."

Single PDF that is generally readable but includes some mistakes that impede understanding; some instances of instructional text have not been removed from original template. All SW test cases have only one method, or inconsistent indication if methods are black box or white box; most methods are clear enough to be followed; may use an independent SWC as a criterion on a SW entry to which is does not apply. Some test outcomes are missing. Report is generally not comprehensible, many instances of instructional text left in, or multiple files submitted instead of single PDF. All SW test cases have only one method, or not all required test cases included; or steps are extremely difficult to follow; or no indication if methods are black box or white box. More outcomes missing than present. Report is largely incomplete or cannot be understood. Meets all NN criteria regarding test case quality (hence, test cases poor in every respect). No outcomes recorded.

Single PDF that is clear, free of errors & contains only required information. Each SW test case has more than one method; methods are sufficiently detailed (no missing steps); white box and black box tests used appropriately; any SWC content included in use SW test case's criteria is relevant to that use case and not an independent SWC. All test outcomes are recorded. Single PDF that is clear, mostly free of errors & contains only required information. Each SW test case has more than one method; methods are mostly sufficiently detailed (1 or 2 missing steps); white box and black box tests used appropriately. All test outcomes are recorded. Single PDF that is generally readable but includes some mistakes that impede understanding; all instructional text has been removed. Two SW test cases have more than one method but one does not; methods are mostly sufficiently detailed (1 or 2 missing steps); most methods are marked as white box and black box, although some of those may have been used inappropriately. All test outcomes are recorded.

Appropriate choice of GUI controls; suitable layout elements that allow application to be resized yet remain usable; implementation makes use of data binding and maybe a data template; at least one user control implemented Appropriate choice of GUI controls, but some layout elements do not allow application to be resized yet remain usable; implementation makes use of data binding Appropriate choice of GUI controls; but some layout elements may not allow application to be resized yet remain usable; makes some use of either data binding or a data template Appropriate choice of GUI controls; some layout element choices do not allow application to be resized while remaining usable; no use of either data binding or data templates Poor choice of GUI controls; application cannot be resized while remaining usable; no use of either data binding or data templates User interface is unusable or does not display any information

Clean separation between model, view and controller classes At most one view class directly controls model objects Some view classes directly control model objects, but not all; any event handler code in the main window is brief Complex event handler code residing in main window's code-behind Model (i.e., data) objects declared in view objects (including the main window) View classes communicate with database adaptor Database interaction and use of LINQ (15%) Database queries are tailored to suit particular tasks and do not load more data than they need; LINQ used to correctly to implement suitable collection processing tasks Most database queries load only enough data for that task being performed, but at least one loop used where a LINQ expression could be Loops used in some places where LINQ expressions could be; or LINQ expressions overused by loading too much of the database into memory first Basic staff and unit details successfully loaded from database; at least one LINQ expression used No use of LINQ, or the only information retrieved from database is that needed for the staff or unit lists

Each class responsible for one part of the system; namespaces reflect packages in OO design; private data cannot be written arbitrarily, except in 'data-only' classes; appropriate use of abstract classes and static methods; one class per source file; uses enums or constants appropriately At least one of the HD criteria is not met At least two HD criteria not met; or string variables (i.e., not constants) used to hold enumerated values Some classes have multiple, different functions (purposes); perhaps only a project-wide namespace; little attempt at explicitly controlling data access; at- times inappropriate use of static methods; or more than one distinct class defined in the same source file Little OO in evidence; few classes, and those that are present have many responsibilities; only a project-wide namespace Insufficient implemented to observe any OO

Staff List and Staff Detail with photo, availability ('free', 'consulting' or 'teaching'), consultation times; Unit List and Unit Timetable showing required details and able to be filtered by campus; Staff List can be filtered by category; either Staff List or Unit list can also be filtered by partial name/code/title match Staff List and Staff Detail with photo but no availability, but including consultation times; Unit List and Unit Timetable showing required detiails and able to be filtered by campus; Staff List can be filtered by category Staff List and Staff Detail without photo or availability & may be missing consultation times list or unit teaching list; Unit List and Unit Timetable, but timetable cannot be filtered by campus; or application includes additional functionality not requested that interferes with its usability Staff or Unit List implemented but no details views Application is unusable, does not display any data or crashes unexpectedly

Submitted assignment is present in team repository; repository indicates project activity beginning by Week 9 As for HD level, but repository indicates project activity beginning during Week 10 As for DN level, but repository indicates project activity beginning during Week 11 As for CR level, but repository indicates project activity beginning during Week 12 Most recent version not available in repository Repository does not contain assignmen-related content Functionality (20%) In addition to DN requirements: all base (non-NTH) requirements implemented, including the list of units the staff member is involved in teaching; both staff name and unit code/title filtering ; ability to go from Staff Detail to Unit Timetable view and back or Activity Grid implemented; in UC16, when availability is 'teaching' unit and room are also shown. HD+ (100%) level requires all of the above to be functioning to a reasonable standard

Submission:submit deliverables 1 and 2 to the Assignment 2 – C# Application & Test Report assignment folder on the unit’s MyLO site. Separately, your team must complete (and all members must sign) the Group Assignment cover sheet; this may be scanned and submitted to the MyLO dropbox if you wish. Deliverables There are three deliverables in this assignment: 1. a zipped VisualStudio project that contains the WPF-based application that must be submitted to the assignment folder, accompanied by 2. a completed test report in PDF, which must also be submitted to the assignment folder. 3. The Visual Studio project and any precursor console application projects must be available in your group’s SVN repository.