C968 Mega Guide

Table of contents 📋

1. WGU's PA guide + resources & videos (Directory)

   • Performance Assessment guide
   • UML Class diagram
   • Lauren Provost's webinars
   • Data Grid webinars
   • Tom Weidner's webinars
   • Visual Studio & Other info

2. PA requirements checklist (Does it have what it needs?)

   • Introduction
   • Checklist Part 1: User Interface
   • Checklist Part 2: Application

3. Project checklist (Step by step basics to walk your project through)

   • Start your project here! 👈

🌐 Performance Assessment guide 🌐

In this guide, you'll find resources and links related to the performance assessment for this course, complete with captions.

All the links and content are courtesy of WGU through their Resources/Course Tips pages.

However, the content is often scattered, making it challenging to follow in a logical sequence when working on your performance assessment project.

This guide aims to compile a comprehensive list of resources for the C968 PA in a clear format, offering you improved guidance and progress tracking.

Feel free to copy and use the checklists in your preferred markdown reader.

Note: All requirements and information are from WGU as of Fall 2023.

---

Project requirements

Software I checklist

The A, B, C's for C968 (Requirements) - ( 08-29-2021)

---

UML Class Diagram

---

Lauren Provost's Webinars

Part 1: GUI Mock up in action Lauren Provost's Personal Room: 2224-1 (August 21, 2023)

Part 2: The ABC's for C Lauren Provost's Personal Room: 2251-1 (August 21, 2023)

---

Data Grid

The DataGrid series (2021)

The Data Grid: Swords (7-11-2021)

The Data Grid: Shields Part 2 (7-24-2021)

The DataGrid: A little more, Part 3 (08-08-2021)

---

Tom Weidner’s Webinars

Apr 18, 2021

• Access your database & switch times from UTC to local
• Link to associated materials
• DB access
• UTC to Local times
• Report

Sep 25, 2020

• Lambdas
• Link to associated materials

Aug 28, 2020

• Validation of info in text forms
• Link to associated materials
• validating text boxes

Jun 26, 2020

• Objects, lists of objects, displaying objects
• Link to associated materials
• Lists of things with lists of things

May 8, 2020

• Auto adjusting time zones

• UTC to Local time handling

• Tracking user logins to a text file

• Link to associated materials

• Text file IO

Apr 24, 2020

• How to generate a report (Student request)
• Link to associated materials
• generating reports

Mar 27, 2020

• How to pre-populate a DataGridView list (Student request)
• Link to associated materials
• pre-populating a datagridview from a list

Mar 13, 2020

• Using lists to populate DataGridView & Binary I/O using files
• Link to associated materials
• change list to change DGV
• binary file IO (serialization/deserialization)

Feb 28, 2020

• Handling time differences
• Link to associated materials
• handling time differences
• debugging using breakpoints

Feb 14, 2020

• Using static classes
• Link to associated materials
• creating inventory as a "static" class
• bindinglist vs list

Jan 24, 2020

• How the requirement can be met for handling a calendar / asking for a week and month view on that calendar
• Link to associated materials
• demonstrate calendar handling
• get ID from drop-down list without ID in it
• get ID from latest INSERT (access DB)

Dec 20, 2019

• Remembering what you’ve selected in DataGridView
• Link to associated materials
• remember what was selected in a DGV
• binding a list to a DGV
• null list vs empty list

Feb 15, 2019

• Localization
• link to associated materials

Jan 18, 2019

• Constructors & Debugging
• link to associated materials

Jan 4, 2019

• Searching & Screen-Hide_Show
• link to "Search" associated materials
• link to "Moving screen to screen" associated materials

Dec 21, 2018

• A "Modify" screen
• link to associated materials

Dec 7, 2018

• The DataGridView
• link to associated materials

---

Visual Studio & Other

Visual Studio configuration

Visual Studio 2019 Debugging Tools Part 1
Visual Studio 2019 Debugging Tools Part 2
Visual Studio 2019 Debugging Tools Part 3
Visual Studio 2019 Debugging Tools Part 4
Visual Studio 2019 Debugging (powerpoint file)

✅ PA Requirements Checklist ✅

Introduction

Throughout your career in software design and development, you will be asked to create applications with various features and functionality based on business requirements.

When a new system is developed, typically the process begins with a business analyst gathering and writing these business requirements, with the assistance of subject matter experts from the business.

Then a system analyst works with several application team members and others to formulate a solution based on the requirements.

As a developer, you would then create a design document from the solution and finally develop the system based on your design document.

For this assessment, you will create a C# application using the solution statements provided in the requirements section.

The skills you showcase in your completed application will be useful in responding to technical interview questions for future employment. This application may also be added to your portfolio to show to future employers.

Your submission should include a zip file with all the necessary code files to compile, support, and run your application.

Note: The preferred integrated development environment (IDE) for this assignment is Visual Studio.
If you choose to use another IDE, you must export your project into Visual Studio format for submission.

Your submission should include a zip file with all the necessary code files to compile, support, and run your application.
The zip file submission must also keep the project file and folder structure intact for the Visual Studio IDE.

---

Scenario

You are working for a small manufacturing organization that has outgrown its current inventory system.
They have been using a spreadsheet program to manually enter inventory additions, deletions, and other data from a paper-based system but would now like you to develop a more sophisticated inventory program.

They have provided you with a mock-up of the user interface to use in the design and development of the system (see the attached “GUI Mock-Up”) and a class diagram to assist you in your work (see the attached “UML Class Diagram”).
The organization also has specific business requirements that must be included as part of the application.
A system analyst from your company created the solution statements outlined in the requirements section based on the manufacturing organization’s business requirements. You will use these solution statements to develop your application.

---

Requirements

Your submission must be your original work.
No more than a combined total of 30% of the submission and no more than a 10% match to any one individual source can be directly quoted or closely paraphrased from sources, even if cited correctly. An originality report is provided when you submit your task that can be used as a guide.

You must use the rubric to direct the creation of your submission because it provides detailed criteria that will be used to evaluate your work. Each requirement below may be evaluated by more than one rubric aspect. The rubric aspect titles may contain hyperlinks to relevant portions of the course.

---

I. User Interface

Create a C# application with a graphical user interface (GUI) based on the attached “GUI Mock-Up.”
Write code to display each of the following forms in the GUI:

A. A main form, showing the following controls:

• buttons for “Add,” “Modify,” “Delete,” “Search” for parts and products, and “Exit”
• lists for parts and products
• text boxes for searching for parts and products
• title labels for parts, products, and the application title

B. An add part form, showing the following controls:

• radio buttons for “In-House” and “Outsourced” parts
• buttons for “Save” and “Cancel”
• text boxes for ID, name, inventory level, price, max and min values, and company name or machine ID
• labels for ID, name, inventory level, price/cost, max and min values, the application title, and company name or machine ID

**C. A modify part form, with fields that populate with data from an existing Part, showing the following

controls:**

• radio buttons for “In-House” and “Outsourced” parts
• buttons for “Save” and “Cancel”
• text boxes for ID, name, inventory level, price, max and min values, and company name or machine ID
• labels for ID, name, inventory level, price, max and min values, the application title, and company name or machine ID

D. An add product form, showing the following controls:

• buttons for “Save,” “Cancel,” “Add” part, and “Delete” part
• text boxes for ID, name, inventory level, price, and max and min values
• labels for ID, name, inventory level, price, max and min values, and the application
• a grid view for all parts
• a grid view for parts associated with the product
• a “Search” button and a text field with an associated list for displaying the results of the search

**E. A modify product form, with fields that populate with data from an existing product, showing the following

controls:**

• buttons for “Save,” “Cancel,” “Add” part, and “Delete” part
• text boxes for ID, name, inventory level, price, and max and min values
• labels for ID, name, inventory level, price, max and min values, and the application “all candidate parts”
• a grid view for parts associated with the product
• a “Search” button and a text box with associated list for displaying the results of the search

---

II. Application

Now that you’ve created the GUI, write code to create the class structure provided in the attached “UML (unified modeling language) Class Diagram.”
Enable each of the following capabilities in the application:

**F. Using the attached “UML Class Diagram,” create appropriate classes and instance variables with the following

criteria:**

• five classes with the all associated properties
• variables are accessible/modifiable through properties

**G. Add the following functionalities to the main form, using the methods provided in the attached “UML Class

Diagram”:**

• redirect the user to the “Add Part,” “Modify Part,” “Add Product,” or “Modify Product” forms
• delete a selected part or product from the grid view
• search for a part or product and display matching results
• exit the main form

**H. Add the following functionalities to the part forms, using the methods provided in the attached “UML Class

Diagram”:**

• [ ]

  1. “Add Part” form
  • select “In-House” or “Outsourced”
  • enter name, inventory level, price, max and min values, and company name or machine ID
  • save the data and then redirect to the main form
  • cancel or exit out of this form and go back to the main form

• 2. “Modify Part” form

  • select “In-House” or “Outsourced”
  • modify or change data values
  • save modifications to the data and then redirect to the main form
  • cancel or exit out of this form and go back to the main form

**I. Add the following functionalities to the product forms, using the methods provided in the attached “UML Class

Diagram”:**

• 1. “Add Product” form

  • enter name, inventory level, price, and max and min values
  • save the data and then redirect to the main form
  • associate one or more parts with a product
  • remove or disassociate a part from a product
  • cancel or exit out of this form and go back to the main form

• 2. “Modify Product” form

  • modify or change data values
  • save modifications to the data and then redirect to the main form
  • associate one or more parts with a product
  • remove or disassociate a part from a product
  • cancel or exit out of this form and go back to the main form

J. Write code to address the following conditions with exception handling code:

• Detect non-numeric values in textboxes that expect numeric values
• Min should be less than Max; and Inv should be between those two values
• Prevent the user from deleting a product that has a Part associated with it
• Confirm “Delete” actions

---

✅ Project Checklist ✅

Part 1

• Read the PA directions in EMA
• Watch Example GUI in Action
• Read the FAQ
• Download Visual Studio
• Study and comprehend the course Learning Resources seen above

Part 2

• Create a Windows C# App in Visual Studio (Please put your name in the project name, otherwise there will be several hundred zipped projects all named InventorySystem)
• Examine DataGridView tutorial
• Use C# Windows Forms to
  • Build the main screen
  • Build the Add/Modify Part screens
  • Build the Add/Modify Product screens

Part 3

• Create the following classes, following the [[UML diagram]] and using Properties
  • Inventory (consider making this class static)
  • Product
  • Part (this is an abstract class)
  • In-house
  • Outsourced
• Create all the button event handlers

Part 4

• Examine Populating a DataGridView
• View webinar on switching screens, in the Course Tips area, dated Jan 4, 2019, Screen-Hide/Show
• Create an Add and a Modify Part screen. You can choose to implement as two distinct files (Add and Modify) or one file implementing both views.
• Enable the user to Add a Part
• Enable the user to Modify a Part (pre-fill textboxes).
• Enable the user to Delete a Part using the Delete button on the main screen.
• Enable the user to pick whether to create an In-house or an Outsourced Part using a radio button
• Enable the user to cancel out of the Add & Modify Part screens
• View webinar on searching, in the Course Tips area, dated Jan 4, 2019, Search
• Enable the user to search the Part DataGridView on the main screen.
• Enable the user to search the Product DataGridView on the main screen.
• Enable the user to Add a Product
• Enable the user to Modify a Product (pre-fill textboxes)
• Enable the user to Delete a Product using the delete product button on the main screen.
• Enable the user to select Parts from the upper table and add them to the lower table
• Enable the user to select Parts from the lower table and delete them from that table
• Enable the user to search the upper table on the Add/Modify Product screen(s)
• Enable the user to Exit the main screen.

Part 5

• Read about MessageBox
• Handle the following Exceptions:
  • Detect non-numeric values in textboxes that expect numeric values
  • Min should be less than Max, and Inv should be between those two values
  • Prevent the user from deleting a product that has a Part associated with it
  • Confirm “Delete” actions
• Verify that everything functions as intended

Part 6

• Zip up project directory, as the evaluators will run the project in Visual Studio
• Submit via the Task View in the main course page