Imagine that you are the asset manager for a major northern European Hub Airport. The airport is under strong competition from Amsterdam, Frankfurt, London, Madrid & Paris.
The probability of a winter snow closure is 0.333 per year. The downtime cost for the airport is 1m / day. In addition, the marketing department has estimated that reputation damage costs an additional 1m per closure.
With existing equipment it takes on average three days to clear snow during which time the airport has to be closed and penalties are incurred.
There is an option to buy new state of the art snow clearing equipment.
This equipment has been successfully used at Denver airport in the USA. It would cost 3m to buy and it would last 30 years if properly looked after and maintained. It is estimated that annual storage, upkeep, painting, maintenance and running costs for this equipment would be 50,000 per year. Training for drivers would be 10,000 initially and 500 / year thereafter. The snow clearance time with this equipment would be reduced from the current three days to one day.
Another option would be to lease the snow clearing equipment for 400,000 per year for a 30 year period. Under this option, the lease company would keep the equipment at the airport and undertake all maintenance and upkeep activities at their expense. You would still have to provide the drivers.
The airport finance department requires that all new investments have to make at least a 10% / year internal rate of return. It also states that a 5% discount rate has to be used in all financial calculations (this takes into account potential future inflation and the cost of raising capital).
Your task in this assignment is to consider the three available options:
1. The status quo where no additional investment is made
2. The purchase and upkeep of new snow clearing equipment
3. The lease of new snow clearing equipment.
Fully discuss each of these three options. Consider all benefits, costs and risks associated with each one. Then state which would be your preferred option giving reasons. If you have to make any assumptions to complete your answer, then please state what these assumptions are and why you have made them.
For your information, the airport risk matrix is made available as a separate file: risk matrix.pdf.
As always report presentation and content are both important. Good diagrams and relevant photos always add impact. Make sure that your report has an abstract, contents page and section headings. Detailed descriptions of methodologies can be put in appendices so that the main report reads smoothly.
At least 5,000 words will be needed to adequately describe your analysis and recommendations. You will not be penalised if you feel that you need to use more words than the minimum.
Category: Graduate
The topic is fuel cell and hybrid vehicles. The instructor asked me to write a matlab code and simulink for my control lecture as my final report. I am planning to do all literature survey and essay stuff but I only need a running matlab code and simulink model.
*750- to 1000-word paper.
*Prepare this assignment according to the guidelines found in the APA 6th Edition Style Guidelines.
*This assignment uses a rubric. Please review the rubric prior to beginning the assignment to become familiar with the expectations for successful completion.
You are tasked with designing a measurement and control system for a water supply system (see: Figure
1). Consider all of the mechanical components of the system to be already installed except the intake
valve and the pump. You must specify the pump, intake valve, any instruments you wish to use, and
whatever control logic and additional controls you intend to use to control the system. To make your life
easier, I have attached a pump curve that will work and a valve coefficient chart. You are free to use or
not use these resources as you see fit. Your objective is to operate the system at minimum cost (i.e.
least energy to the pump). You do not need to calculate the amount or cost of energy, but you should
make a good argument based on the pump specification and the control logic.
Handheld Solitaire requires no table, has simple rules, and is easily learned and played. It is played with a traditional 52 card deck of 4 suits (hearts, clubs, diamonds, and spades) and 13 ranks from ace (1) to king (13). Jokers are not included. The deck (face down) is held in one hand, while the actual hand of cards to be played is placed face up on top of the deck. This leaves the other hand free for dealing and discarding. The rules of play are as follows:
Shuffle the deck, then hold it face-down in one hand.
While the deck is not empty:
Deal a single card from the top of the deck into the top of the playing hand
While a match occurs in the playing hand between the top card and the card 3 back from it, either in rank or suit, collapse the hand using the following rules:
If the ranks match, all 4 top cards of the hand are discarded. For example, if the cards are: 2S 6S 9C 2H , we would be comparing the last card dealt, 2S, to the card which is three back from it, 2H. Because the values match, we would discard all four cards.
If the suits match, only the middle 2 (of the top 4) cards of the hand are discarded. For example, if the cards are: JH 3S 5C 7H , we would be comparing the last card dealt, JH, to the card which is three back from it, 7H. Because the suits match, we would discard the middle to cared (3S and 3C) and be left with JH 7H .
The final score is the number of cards left in the hand at the end of the game.
There are several requirements in designing this project.
A single card should be represented by a Card class. A card should be represented by a value (int) and a suit (char), and must include a pointer to a Card named nextCard as one of the private data members. Implement appropriate getter and setter functions and two constructors (one for default values and one with explicit parameters). It should also have a print() function described by the following bullet. Use Card.h and Card.cpp files to develop the class.
o The print function should print the value and suit of the card in two characters. Thus, print the numerical value. However, if the value is 1, print A (for [A]ce); if it is 10, print T (for [T]en); if it is 11, print J (for [J]ack); if it is 12, print Q (for [Q]ueen); if it is 13, print K (for [K]ing). Follow this by the character representing the suit ([S]pades, [C]lubs, [H]earts, [D]iamonds), The following give some examples of a card, followed by how it should be printed:
Ace of Hearts would be printed as: AH
10 of Diamonds would be printed as: TD
5 of Clubs would be printed as: 5C
A deck and a playing hand of cards should each be represented by a CardLL class containing two private data members: a length variable to store the number of items in the CardLL object and a Card pointer named top. This will be a pointer to a linked list of Card objects (Cards will be the nodes of the linked list). Implement the class using CardLL.h and CardLL.cpp files. The functions to implement for this class are as follows.
o CardLL (default constructor). The function sets the list pointer to be NULL and the length to be zero.
o ~CardLL (destructor). Deletes each item from the list, one by one.
o insertAtTop(suit, value). The function inserts a given card at the top of the list.
o getCardAt(pos). This function will return a Card pointer which points to the card at the given position. If the position doesnt exist in the list, just return NULL.
o removeCardAt(pos). This function will remove the card at the given position, returning true if successful. If the position outside the bounds of the list, return false.
o getLength(). Returns the length of the list.
o isEmpty(). Returns true if the list is empty; false otherwise.
o print(). Prints the word top: followed by each card in the linked list, all on one line. (Utilize the Card print() function to aid with printing each individual card.
o shuffle(). This will randomly shuffle a list of cards using the Fisher-Yates shuffle algorithm as follows (implement this function last):
Use a while loop to walk through each Card in the list. Also within the loop:
Get a random number between 0 and length 1
Use getCardAt to get the card at that position
Swap the card at the walk position with the card at the position random position. Just swap the suit and the value, not the nextCard pointer!
Notes about random numbers:
include the cstdlib and ctime files.
place the following line as the first line of main():
srand(time(NULL));
In your CardLL classs shuffle() function, use rand() (with the modulus operator) to generate a random number in the appropriate range. Click here for an example of using rand()or consult page 274-275 of your textbook.
If there are additional class member functions that you would like to implement to ease the programming, you are allowed to do so. However, they should be clearly documented where necessary and should follow a structured object-oriented design approach.
Game play should be simulated in a client file called HHSolitaire.cpp. Follow the directions on the first page for the way the game is played. Represent the Deck and the Hand (playing hand) using a CardLL object for each. Use comments and functions to aid in the readability of your code. One function in particular to implement is populateDeck, which handles creating a new complete deck of 52 playing cards as follows (wrapped onto two lines below):
AD 2D 3D 4D 5D 6D 7D 8D 9D TD JD QD KD AC 2C 3C 4C 5C 6C 7C 8C 9C TC JC QC KC AH 2H 3H 4H 5H 6H 7H 8H 9H TH JH QH KH AS 2S 3S 4S 5S 6S 7S 8S 9S TS JS QS KS
Hint: To create the deck, use a nested for loop (one for the values [1-13] and one for the suits [D, C, H, S]) to generate the suits and values for the cards as you insert them into the deck.
*Game play in this game, by its very nature, is deterministic. Thus, the entire game play can be printed to the output all at once. To give the program more of a game feel, though, you can use getchar() before each call to Hand.print() in main() to force the user to press the Enter key between each new card being played. Include stdio.h library in order to use this. This part should be saved until the very end of all testing!
Start early. I cannot emphasize this enough. This project will once again challenge your logical and critical thinking skills. Think of the design (structure, flow, logic sequence) of the program before implementing it. Learn from the previous projects. I will briefly reiterate the approach you should take below:
Write down/draw out, on paper, how the overall design of the program should look. Getting your thoughts down on paper will help you organize/refine your approach and get a better grasp of how the individual components should fit together.
Implement your program as empty function stubs at first and develop incrementally, testing one piece at a time before moving on. Building your program slowly from the ground up will allow you to foresee and prevent potential problems later on in development.
Test many different input cases as you are developing your program and even once you feel that the program is complete. A good strategy is to try to break your program with a variety of different test casesit is much better for you to find a software mistake and fix it early than to have the final product fail the end user(s) because you didnt test adequately.
Testing: Test the program in steps. Build the Card and CardLL classes and verify that adding and deleting cards from the list works as you expect. Then start adding in individual elements of game play, incrementally. You will likely get segmentation faults as you develop this program. These are frustrating. However, these are a lot easier to debug if you test your program little by little.
Submission: This project is worth 110 points and is due on Friday, March 27th before noon. Submission must include:
An electronic turn-in through Canvas. The entire Visual Studio solution folder must be zipped in order to do this. To create a zipped folder, right-click the folder and select Send to -> Compressed (zipped) folder. Rename this folder Project3_firstname_lastname where firstname and lastname are replaced with your first and last name, respectively. Upload this zipped folder to the Project 2 assignment page. Make sure that the following files are included in your project:
HHSolitaire.cpp
CardLL.cpp
CardLL.h
Card.cpp
Card.h
A paper printout of your code, along with console outputs from at least 3 separate program runs.
Grading: The program will be graded along the following dimensions. Note that the values in brackets are percentages of the project grade. Point distributions will be weighted accordingly.
[20] Card implementation
[35] CardLL implementation
[35] HHSolitaire implementation
[20] Overall quality of program design, code structure/readability, and user interaction
For the final bullet, ensure that the program files contain header comments, formatted as required by the CSCI documentation guidelines. Documentation (commenting) is used to illustrate major sections or unclear sections of code as well. Program design should clearly convey intent, especially focusing on proper use of variable names, whitespace, alignment and indentation
Make sure that the file names are correct, that your program contains no syntax errors, and that all of the code compiles. Programs that do not compile will receive an automatic 20 point deduction (20% of the project grade). This will be in addition to any deductions on the items listed above.
If you are unable to decipher a compiler error in your program, its better to comment out that section of code so that the program compiles without error. This way I can see that it was at least attempted and you may receive partial points for that section of code. In addition to the commented out section, write a detailed explanation of what you think the error may be, and the steps you tried in order to fix the error.
Academic Honesty: I expect you to maintain a high ethical standard when developing your programs. Students are bound by the academic honesty policies of the department, college, and university. Direct collaboration with others on this project is not permitted, and helping generate specific lines or chunks of code is strictly prohibited. General design strategies of the software program may be discussed at a high level.
Output: You may use the following as a guide to what your output should look like.
Top: 8C
Top: 9C 8C
Top: 4H 9C 8C
Top: 2S 4H 9C 8C
Top: TS 2S 4H 9C 8C
Top: 7H TS 2S 4H 9C 8C
Suit Match! Removing: TS 2S
Top: 7H 4H 9C 8C
Top: 7S 7H 4H 9C 8C
Top: KH 7S 7H 4H 9C 8C
Suit Match! Removing: 7S 7H
Top: KH 4H 9C 8C
Top: 9H KH 4H 9C 8C
Number Match! Removing: 9H KH 4H 9C
Top: 8C
Top: 8D 8C
Top: 3C 8D 8C
Top: QD 3C 8D 8C
Top: 4D QD 3C 8D 8C
Suit Match! Removing: QD 3C
Top: 4D 8D 8C
Top: 6C 4D 8D 8C
Suit Match! Removing: 4D 8D
Top: 6C 8C
Top: 2D 6C 8C
Top: AS 2D 6C 8C
Top: 9D AS 2D 6C 8C
Top: JS 9D AS 2D 6C 8C
Top: AD JS 9D AS 2D 6C 8C
Number Match! Removing: AD JS 9D AS
Top: 2D 6C 8C
Top: JC 2D 6C 8C
Suit Match! Removing: 2D 6C
Top: JC 8C
Top: AC JC 8C
Top: 4C AC JC 8C
Suit Match! Removing: AC JC
Top: 4C 8C
Top: TH 4C 8C
Top: 6H TH 4C 8C
Top: 5D 6H TH 4C 8C
Top: JH 5D 6H TH 4C 8C
Suit Match! Removing: 5D 6H
Top: JH TH 4C 8C
Top: 7C JH TH 4C 8C
Suit Match! Removing: JH TH
Top: 7C 4C 8C
Top: 4S 7C 4C 8C
Top: AH 4S 7C 4C 8C
Top: KC AH 4S 7C 4C 8C
Suit Match! Removing: AH 4S
Top: KC 7C 4C 8C
Suit Match! Removing: 7C 4C
Top: KC 8C
Top: 5H KC 8C
Top: 2H 5H KC 8C
Top: QC 2H 5H KC 8C
Suit Match! Removing: 2H 5H
Top: QC KC 8C
Top: TD QC KC 8C
Top: 3S TD QC KC 8C
Top: 5C 3S TD QC KC 8C
Suit Match! Removing: 3S TD
Top: 5C QC KC 8C
Suit Match! Removing: QC KC
Top: 5C 8C
Top: 8H 5C 8C
Top: KS 8H 5C 8C
Top: 2C KS 8H 5C 8C
Suit Match! Removing: KS 8H
Top: 2C 5C 8C
Top: 6D 2C 5C 8C
Top: 3H 6D 2C 5C 8C
Top: KD 3H 6D 2C 5C 8C
Top: 3D KD 3H 6D 2C 5C 8C
Suit Match! Removing: KD 3H
Top: 3D 6D 2C 5C 8C
Top: 7D 3D 6D 2C 5C 8C
Top: JD 7D 3D 6D 2C 5C 8C
Suit Match! Removing: 7D 3D
Top: JD 6D 2C 5C 8C
Top: TC JD 6D 2C 5C 8C
Suit Match! Removing: JD 6D
Top: TC 2C 5C 8C
Suit Match! Removing: 2C 5C
Top: TC 8C
Top: 5S TC 8C
Top: QH 5S TC 8C
Top: 8S QH 5S TC 8C
Top: 9S 8S QH 5S TC 8C
Suit Match! Removing: 8S QH
Top: 9S 5S TC 8C
Top: QS 9S 5S TC 8C
Top: 6S QS 9S 5S TC 8C
Suit Match! Removing: QS 9S
Top: 6S 5S TC 8C
Deck Empty! Printing leftover hand:
Top: 6S 5S TC 8C
Handheld Solitaire
Handheld Solitaire requires no table, has simple rules, and is easily learned and played. It is played with a traditional 52 card deck of 4 suits (hearts, clubs, diamonds, and spades) and 13 ranks from ace (1) to king (13). Jokers are not included. The deck (face down) is held in one hand, while the actual hand of cards to be played is placed face up on top of the deck. This leaves the other hand free for dealing and discarding. The rules of play are as follows:
Shuffle the deck, then hold it face-down in one hand.
While the deck is not empty:
Deal a single card from the top of the deck into the top of the playing hand
While a match occurs in the playing hand between the top card and the card 3 back from it, either in rank or suit, collapse the hand using the following rules:
If the ranks match, all 4 top cards of the hand are discarded. For example, if the cards are: 2S 6S 9C 2H , we would be comparing the last card dealt, 2S, to the card which is three back from it, 2H. Because the values match, we would discard all four cards.
If the suits match, only the middle 2 (of the top 4) cards of the hand are discarded. For example, if the cards are: JH 3S 5C 7H , we would be comparing the last card dealt, JH, to the card which is three back from it, 7H. Because the suits match, we would discard the middle to cared (3S and 3C) and be left with JH 7H .
The final score is the number of cards left in the hand at the end of the game.
There are several requirements in designing this project.
A single card should be represented by a Card class. A card should be represented by a value (int) and a suit (char), and must include a pointer to a Card named nextCard as one of the private data members. Implement appropriate getter and setter functions and two constructors (one for default values and one with explicit parameters). It should also have a print() function described by the following bullet. Use Card.h and Card.cpp files to develop the class.
o The print function should print the value and suit of the card in two characters. Thus, print the numerical value. However, if the value is 1, print A (for [A]ce); if it is 10, print T (for [T]en); if it is 11, print J (for [J]ack); if it is 12, print Q (for [Q]ueen); if it is 13, print K (for [K]ing). Follow this by the character representing the suit ([S]pades, [C]lubs, [H]earts, [D]iamonds), The following give some examples of a card, followed by how it should be printed:
Ace of Hearts would be printed as: AH
10 of Diamonds would be printed as: TD
5 of Clubs would be printed as: 5C
A deck and a playing hand of cards should each be represented by a CardLL class containing two private data members: a length variable to store the number of items in the CardLL object and a Card pointer named top. This will be a pointer to a linked list of Card objects (Cards will be the nodes of the linked list). Implement the class using CardLL.h and CardLL.cpp files. The functions to implement for this class are as follows.
o CardLL (default constructor). The function sets the list pointer to be NULL and the length to be zero.
o ~CardLL (destructor). Deletes each item from the list, one by one.
o insertAtTop(suit, value). The function inserts a given card at the top of the list.
o getCardAt(pos). This function will return a Card pointer which points to the card at the given position. If the position doesnt exist in the list, just return NULL.
o removeCardAt(pos). This function will remove the card at the given position, returning true if successful. If the position outside the bounds of the list, return false.
o getLength(). Returns the length of the list.
o isEmpty(). Returns true if the list is empty; false otherwise.
o print(). Prints the word top: followed by each card in the linked list, all on one line. (Utilize the Card print() function to aid with printing each individual card.
o shuffle(). This will randomly shuffle a list of cards using the Fisher-Yates shuffle algorithm as follows (implement this function last):
Use a while loop to walk through each Card in the list. Also within the loop:
Get a random number between 0 and length 1
Use getCardAt to get the card at that position
Swap the card at the walk position with the card at the position random position. Just swap the suit and the value, not the nextCard pointer!
Notes about random numbers:
include the cstdlib and ctime files.
place the following line as the first line of main():
srand(time(NULL));
In your CardLL classs shuffle() function, use rand() (with the modulus operator) to generate a random number in the appropriate range. Click here for an example of using rand()or consult page 274-275 of your textbook.
If there are additional class member functions that you would like to implement to ease the programming, you are allowed to do so. However, they should be clearly documented where necessary and should follow a structured object-oriented design approach.
Game play should be simulated in a client file called HHSolitaire.cpp. Follow the directions on the first page for the way the game is played. Represent the Deck and the Hand (playing hand) using a CardLL object for each. Use comments and functions to aid in the readability of your code. One function in particular to implement is populateDeck, which handles creating a new complete deck of 52 playing cards as follows (wrapped onto two lines below):
AD 2D 3D 4D 5D 6D 7D 8D 9D TD JD QD KD AC 2C 3C 4C 5C 6C 7C 8C 9C TC JC QC KC AH 2H 3H 4H 5H 6H 7H 8H 9H TH JH QH KH AS 2S 3S 4S 5S 6S 7S 8S 9S TS JS QS KS
Hint: To create the deck, use a nested for loop (one for the values [1-13] and one for the suits [D, C, H, S]) to generate the suits and values for the cards as you insert them into the deck.
*Game play in this game, by its very nature, is deterministic. Thus, the entire game play can be printed to the output all at once. To give the program more of a game feel, though, you can use getchar() before each call to Hand.print() in main() to force the user to press the Enter key between each new card being played. Include stdio.h library in order to use this. This part should be saved until the very end of all testing!
Start early. I cannot emphasize this enough. This project will once again challenge your logical and critical thinking skills. Think of the design (structure, flow, logic sequence) of the program before implementing it. Learn from the previous projects. I will briefly reiterate the approach you should take below:
Write down/draw out, on paper, how the overall design of the program should look. Getting your thoughts down on paper will help you organize/refine your approach and get a better grasp of how the individual components should fit together.
Implement your program as empty function stubs at first and develop incrementally, testing one piece at a time before moving on. Building your program slowly from the ground up will allow you to foresee and prevent potential problems later on in development.
Test many different input cases as you are developing your program and even once you feel that the program is complete. A good strategy is to try to break your program with a variety of different test casesit is much better for you to find a software mistake and fix it early than to have the final product fail the end user(s) because you didnt test adequately.
Testing: Test the program in steps. Build the Card and CardLL classes and verify that adding and deleting cards from the list works as you expect. Then start adding in individual elements of game play, incrementally. You will likely get segmentation faults as you develop this program. These are frustrating. However, these are a lot easier to debug if you test your program little by little.
Submission: This project is worth 110 points and is due on Friday, March 27th before noon. Submission must include:
An electronic turn-in through Canvas. The entire Visual Studio solution folder must be zipped in order to do this. To create a zipped folder, right-click the folder and select Send to -> Compressed (zipped) folder. Rename this folder Project3_firstname_lastname where firstname and lastname are replaced with your first and last name, respectively. Upload this zipped folder to the Project 2 assignment page. Make sure that the following files are included in your project:
HHSolitaire.cpp
CardLL.cpp
CardLL.h
Card.cpp
Card.h
A paper printout of your code, along with console outputs from at least 3 separate program runs.
Grading: The program will be graded along the following dimensions. Note that the values in brackets are percentages of the project grade. Point distributions will be weighted accordingly.
[20] Card implementation
[35] CardLL implementation
[35] HHSolitaire implementation
[20] Overall quality of program design, code structure/readability, and user interaction
For the final bullet, ensure that the program files contain header comments, formatted as required by the CSCI documentation guidelines. Documentation (commenting) is used to illustrate major sections or unclear sections of code as well. Program design should clearly convey intent, especially focusing on proper use of variable names, whitespace, alignment and indentation
Make sure that the file names are correct, that your program contains no syntax errors, and that all of the code compiles. Programs that do not compile will receive an automatic 20 point deduction (20% of the project grade). This will be in addition to any deductions on the items listed above.
If you are unable to decipher a compiler error in your program, its better to comment out that section of code so that the program compiles without error. This way I can see that it was at least attempted and you may receive partial points for that section of code. In addition to the commented out section, write a detailed explanation of what you think the error may be, and the steps you tried in order to fix the error.
Academic Honesty: I expect you to maintain a high ethical standard when developing your programs. Students are bound by the academic honesty policies of the department, college, and university. Direct collaboration with others on this project is not permitted, and helping generate specific lines or chunks of code is strictly prohibited. General design strategies of the software program may be discussed at a high level.
Output: You may use the following as a guide to what your output should look like.
Top: 8C
Top: 9C 8C
Top: 4H 9C 8C
Top: 2S 4H 9C 8C
Top: TS 2S 4H 9C 8C
Top: 7H TS 2S 4H 9C 8C
Suit Match! Removing: TS 2S
Top: 7H 4H 9C 8C
Top: 7S 7H 4H 9C 8C
Top: KH 7S 7H 4H 9C 8C
Suit Match! Removing: 7S 7H
Top: KH 4H 9C 8C
Top: 9H KH 4H 9C 8C
Number Match! Removing: 9H KH 4H 9C
Top: 8C
Top: 8D 8C
Top: 3C 8D 8C
Top: QD 3C 8D 8C
Top: 4D QD 3C 8D 8C
Suit Match! Removing: QD 3C
Top: 4D 8D 8C
Top: 6C 4D 8D 8C
Suit Match! Removing: 4D 8D
Top: 6C 8C
Top: 2D 6C 8C
Top: AS 2D 6C 8C
Top: 9D AS 2D 6C 8C
Top: JS 9D AS 2D 6C 8C
Top: AD JS 9D AS 2D 6C 8C
Number Match! Removing: AD JS 9D AS
Top: 2D 6C 8C
Top: JC 2D 6C 8C
Suit Match! Removing: 2D 6C
Top: JC 8C
Top: AC JC 8C
Top: 4C AC JC 8C
Suit Match! Removing: AC JC
Top: 4C 8C
Top: TH 4C 8C
Top: 6H TH 4C 8C
Top: 5D 6H TH 4C 8C
Top: JH 5D 6H TH 4C 8C
Suit Match! Removing: 5D 6H
Top: JH TH 4C 8C
Top: 7C JH TH 4C 8C
Suit Match! Removing: JH TH
Top: 7C 4C 8C
Top: 4S 7C 4C 8C
Top: AH 4S 7C 4C 8C
Top: KC AH 4S 7C 4C 8C
Suit Match! Removing: AH 4S
Top: KC 7C 4C 8C
Suit Match! Removing: 7C 4C
Top: KC 8C
Top: 5H KC 8C
Top: 2H 5H KC 8C
Top: QC 2H 5H KC 8C
Suit Match! Removing: 2H 5H
Top: QC KC 8C
Top: TD QC KC 8C
Top: 3S TD QC KC 8C
Top: 5C 3S TD QC KC 8C
Suit Match! Removing: 3S TD
Top: 5C QC KC 8C
Suit Match! Removing: QC KC
Top: 5C 8C
Top: 8H 5C 8C
Top: KS 8H 5C 8C
Top: 2C KS 8H 5C 8C
Suit Match! Removing: KS 8H
Top: 2C 5C 8C
Top: 6D 2C 5C 8C
Top: 3H 6D 2C 5C 8C
Top: KD 3H 6D 2C 5C 8C
Top: 3D KD 3H 6D 2C 5C 8C
Suit Match! Removing: KD 3H
Top: 3D 6D 2C 5C 8C
Top: 7D 3D 6D 2C 5C 8C
Top: JD 7D 3D 6D 2C 5C 8C
Suit Match! Removing: 7D 3D
Top: JD 6D 2C 5C 8C
Top: TC JD 6D 2C 5C 8C
Suit Match! Removing: JD 6D
Top: TC 2C 5C 8C
Suit Match! Removing: 2C 5C
Top: TC 8C
Top: 5S TC 8C
Top: QH 5S TC 8C
Top: 8S QH 5S TC 8C
Top: 9S 8S QH 5S TC 8C
Suit Match! Removing: 8S QH
Top: 9S 5S TC 8C
Top: QS 9S 5S TC 8C
Top: 6S QS 9S 5S TC 8C
Suit Match! Removing: QS 9S
Top: 6S 5S TC 8C
Deck Empty! Printing leftover hand:
Top: 6S 5S TC 8C
Hello,
I’m trying to teach myself how to code during my down time and have come into a roadblock regarding Bootstrap development. I struggle with the .navbar and creating .jumbotron or box-model. Looking for developer to help inform on how to create final result (attached images below).
Hello, I need some modifications on some code, the code is a social network analyzer fully functional, for facebook, youtube, twitter and instagram, I need some small rearrangements on the APIs and also 4 new directory pages, at the moment I just have Instagram directory, also I need to add some new features to the APIs like show country, and audiences from YouTube.
The social profile tracking script is an already existing script on CodeCanyon – “phpAnalyzer”.
– Create plugin TikTok (like https://cloutmeter.com/)
– Create Directory for Tiktok
– Create Directory for Youtube
– Create Directory for Facebook
– Create Directory for Twitter
Add features: (when possible by the APIs)
– Add audience analysis (gender ,age, location)
o General
o By Publication
– Add Category
– Add Country (location of the account)
Add non API Editable Fields to accounts:
– Manual Country (ability to add more than one Country)
– Manual Category (ability to add more than one Category)
– Average Cost
– Email
Make all the fields searchable on the directories
Must develop and ERD diagram for an Online retail business of choice. The retail business must be able to collect CC payments. At minimum the developed relational database must collect and store the following information;
Stock
Customer Details
Orders
Suppliers
Payments
Returns
Using the ERD diagram that was developed earlier in Part A now expand upon the original ERD and develop and populate a real life Relational Database to hold their business data and ALSO a Data Mart to support the reporting requirements of the retail company.
In order to implement this Data Mart students are required to automate the loading of the data from the live production database to the Data Mart. This should be done by scripting.
Project Report Document
a. Background Information Document and relevant graphs connected via Excel to 2 reports of YOUR CHOICE
b. Script File to Create the Data Mart database and tables and the following reports
c. The Data Mart SHOULD ONLY CONTAIN results only from Views (Questions 1, 3 and 4 ONLY)
1. Create a View showing all transactions for a given week in your business.
2. Create a trigger that stores stock levels once a sale takes place.
3. Create a View of stock (by supplier) purchased by you.
4. Create a View of Total stock sold to general public (group by supplier).
5. Detail and total all transactions (SALES) for the month-to-date. (A Group By with Roll-Up)
6. Detail and total all SALES for the year-to-date. (A Group By with Roll-Up)
7. Detail & total transactions broken down on a monthly basis for 1 year. (A Group By with Roll-Up)
8. Display the growth in sales/services (as a percentage) for your business, from the 1st month of opening until now.
9. Use Excel to create a graphical representation of any 2 of the queries of YOUR CHOICE, for example Q1 & Q4. (Any type of graph)
10. Add both the SQL statements and graphs into a Word document report (Your SQL code and the screenshots and relevant graphs & ERD Diagram). The Word document must show the results of your queries when run (Screen shot of the Output).
1. INTRODUCTION MiHotel is a mid-range hotel chain that started in Traverse City, Michigan in 1980. The chain offers three star service and moderately-priced rooms at its 15 hotels throughout Michigan. MiHotel has plans for a major expansion, building three new hotels in the next three years. As a part of the expansion, the company will be hiring dozens of employees for each new hotel. MiHotels Human Resources (HR) department has decided that the existing online application process is insufficient to handle the demand created by the companys expansion plans. As such, they have decided to implement a new applicant processing system to better meet the needs of their growing company.
2. Background In meeting with the parties involved in creating this system, you realize that people from different departments need to have different levels of access into the system. That is, employees in HR should not have the same screens or access to data that a hotel manager would have, or the access that executives would have. At the same time, the manager from hotel A should not be able to see the data from hotel B. The departments needed for this assignment: HR, Hotel Managers, Executives.
The first part is to think about the flow of logging in. This is something you’ve done over and over, but likely haven’t thought about. The users put in their user ID and password and the system determines which department they work and sends them where they need to go. For this part, you will set this up something like “if user is jsmith go to department XYZ”
3. Assignment
A. Create a flowchart or write out pseudocode for how you are going to control access to the system. Do not worry about specific users, just the department in which they work. (Later in the course we will learn how to authenticate users from a database and retrieve the department in which they work.)
B. Create a new project in Visual Studio, design the form(s) needed to implement your logic from part A. You may hard-code the departments in the decision portion of your code. Submit: a Word document containing your pseudocode/flowchart, screenshots of your screens with the project running, a copy of your code.
