SAI430 – Week 7 Lab – 100% Guaranteed Solution

Lab Price = $15
Please feel free to send us your queries at: support@iqrajavaid.com
Payment Methods

Add to Cart

Buy Now

View Cart


Problem Statement

 

SAI430 – Week 7 Lab – 100% Guaranteed Solution
SAI 430 – iLab Week 7: System integration
TCOs Satisfied
9
Given a set of system requirements, identify and implement the required integration of multiple database platforms, programming applications, and data transfer processes into a single functioning information system environment.
Introduction and Rationale
It’s time to put everything together. This week you will create a single C#.NET application that reads data from an XML file, validates the data, and then writes it into a MySQL database. After successfully performing a database load, the system will then generate three web pages that detail management and system administration reports. In this fashion, you are creating a “system integration” of the tools you have built all session.
Lab Setup
Resetting the database before and during testing (back to week 5 setup)
Before you begin this lab, you should reset the database to a new week five staring condition. You might also find that you want to reset it many times during the testing of your program. To reset your database back to the week five state – rerun the week 5 SQL script provided in week 5: Omni_InventoryDBWk5.sql. You can do this as often as you need. The script has been provided in the zip: SAI430_W7_iLab_Extras.zip located in document sharing. This script is run from within the Omnymbus MySQL server. Refer to Figure 1.
SAI 430 – iLab Week 7
Figure 1 – Resetting original database state by rerunning setup script
Lab Description
For week seven you will create a Visual Studio C#.NET program that reads an XML file which will contain items labeled with one of three commands: ADD, UPDATE, and DELETE. This file is named UpdateW7.xml and is found in the SAI430_W7_iLab_Extras.zip file in Document Sharing. You will perform an associated add, update, or delete in the Inventory database that we originally created in week one (see Figure 2). This part is identical to the week 5 iLab, and you should borrow heavily from this earlier assignment. You will also create three daily reports detailing all items in inventory, the items that need reordering, and the error log for the system administrators. These reports are identical to iLab #6 but must now be integrated with the XML processing of iLab #5. See Figure 3. After the UpdateW7.xml update, you will then update again with a test file of your own design.
Itemitem_id: int (PK)invent_id: int (FK)itemsize: varchar(10)color: varchar(10)curr_price: decimalqoh: intinventoryinvent_id: int (PK)invent_desc: varchar(100)errorlogError_id: int (PK)item_id: interrorTime: datetimeerrorMsg: varchar(255)
Figure 2 – Inventory Database ERD with new errorlog table
SAI 430 – iLab Week 7
XML file containing daily updates for the systemComputer program written for XML processing, data validation, database updating, and daily reporting.System DatabaseUser’s Browser displays reports112233
Figure 3 – Input, validation, database updates, and daily reporting integration
The results should look like the three reports listed below:
SAI 430 – iLab Week 7
Testing
You must then create your own XML file with at least 5 ADD statements, 5 UPDATE statements, and 5 DELETE statements. Add another 5 statements which are errors to see what happens. Name this file TestUpdate.xml. Use the UpdateW7.xml file as a model to make sure you create the statements properly. Run your program again with this test file as the input (you’ll need to change the filename in your code). You’ll want to name the output files something different – such as TESTAllInventory.html.
Hints and Tips
HINT 1: At this point you are combining at least two of your previous programs and many of your C# files. Remember that you have designed everything as class files, so they should all fit together easily. Be sure that you alter all of the “namespace” names to match (including capitalization). Classes from week 5 will have been in the projectWeek5 namespace (or whatever you named it), while classes from week 6 will have been in the projectWeek6 namespace. They must now match – along with the Main.
HINT 2: Don’t forget to change the filename of the input XML file to UpdateW7.xml and then TestUpdate.xml.
HINT 3: You may want to change the name of your output HTML files to be different than the week 6 files – especially if you are storing them in the same directory.
TIP: Although the most complex assignment so far – it should take you the least amount of time. Why? Spend your extra time working on the Course Project.
Deliverables
For iLab #7, you will submit the following deliverables to the course drop box in a single ZIP file:
1. Name your ZIP archive LastName_FirstName_W7_iLab.zip
2. Copy and paste your entire C#.NET program into a Word document. Add this document to the ZIP file. Your teacher may request that you include your entire week 7 project in the ZIP file, if so, you will need to revisit the Student Resources tab to learn about transferring files from CITRIX to your local PC. You should have at least six C# files including: Your main program, your Item class, your Error class, your Item Exception class, and your report class.
3. Run your program using the UpdateW7.xml file. Store all resulting HTML files in the ZIP file as well.
4. Run your program using the TestUpdate.xml file. Store the resulting HTML files in the ZIP file. Prefix their names with “Test”.
5. Include your TestUpdate.xml file.
Make sure you close and save your documents before adding them to the ZIP file. This will ensure that the latest version of the files are uploaded.
SAI 430 – iLab Week 7
Grading Rubric
iLab Deliverables
Description
Points
Item #1
Document header and comments in the code.
5
Item #2
Well written and functional C#.NET program Main.
5
Item #3
All support classes
• Item class
• Error classes
• Report class
10
Item #4
All html files after running UpdateW7.xml, but before running your TestUpdate.xml
10
Item #5
TestAllItems.html file
5
Item #6
TestReorder.html file
5
Item #7
TestErrorLog.html file
5
Item #8
Your 20 item TestUpdate.xml
5
Total Points
50
Course Project Tie-in
Week 7 will address the overall integration of the different iLabs into a single project. What is the overall project supposed to do? Why do you want to integrate the system rather than leave it as individual programs?
Also in Week 7 you should address the methods that were used to test this system. Did you test the components AND the whole system, or just the system? What are strategies to use in testing? How do you prove to the stakeholders that the testing was successful? What do you do with testing data? What do you do if there is a testing failure?
There is nothing to turn in for the course project until week 8, but your team must not get behind. This is the last week before the project is due. You should have completed it by now and just be working on final edits.

Relevant Material
Screenshots

 

Instructions
* If you want to purchase multiple products then click on “Buy Now” button which will give you ADD TO CART option.Please note that the payment is done through PayPal.
* You can also use 2CO option if you want to purchase through Credit Cards/Paypal but make sure you put the correct billing information otherwise you wont be able to receive any download link.
* Your paypal has to be pre-loaded in order to complete the purchase or otherwise please discuss it with us at support@iqrajavaid.com.
* As soon as the payment is received, download link of the solution will automatically be sent to the address used in selected payment method.
* Please check your junk mails as the download link email might go there and please be patient for the download link email. Sometimes, due to server congestion, you may receive download link with a delay.
* All the contents are compressed in one zip folder.
* In case if you get stuck at any point during the payment process, please immediately contact us at support@iqrajavaid.com and we will fix it with you.
* We try our best to reach back to you on immediate basis. However, please wait for atleast 8 hours for a response from our side. Afterall, we are humans.
* Comments/Feedbacks are truely welcomed and there might be some incentives for you for the next lab/quiz/assignment.
* In case of any query, please donot hesitate to contact us at support@iqrajavaid.com.
* MOST IMPORTANT Please use the tutorials as a guide and they need NOT to be used for any submission. Just take help from the material.
******************************************** Good Luck ***************************************************
Payment Details

 

Lab Price = $15
Please feel free to send us your queries at: support@iqrajavaid.com
Payment Methods

Add to Cart

Buy Now

View Cart

Privacy Policy
We take your privacy seriously and will take all measures to protect your personal information.
Any personal information received will only be used to fill your order. We will not sell or redistribute your information to anyone.
Refund Policy
Incase you face any issues with the tutorial, please free to contact us on support@iqrajavaid.com
We will try our best to resolve the issue and if still persists we can discuss for a refund in case its required.


Leave a Reply