It all depends on what you're doing online.
Answer:
Following are the program to this question:
#include <iostream>//defining header file
using namespace std;
void squareOfAsterisks(int x) //defining method squareOfAsterisks
{
int i,j; //defining integer variable
for(i=1;i<=x;i++) //defining loop to print column value
{
for(j=1;j<=x;j++) //defining loop to print row value
{
cout<<"*"; //print value
}
cout<<endl; //for line break
}
}
int main() //defining main method
{
int x; //defining integer variable
cout<<"Enter any number: "; //print message
cin>>x; //input value from user
squareOfAsterisks(x); //calling the method and pass the value
return 0;
}
Output:
Enter any number: 4
****
****
****
****
Explanation:
The description of the above program can be given as follows:
- In the given program a method "squareOfAsterisks" is declared, that accepts an integer value "x" in its arguments, inside the method two integer variable I, j is used, that uses a to print the given pattern.
- In the main method, an integer variable x is declared, which takes input from the user end, and then calls the method, that is "squareOfAsterisks" and passes its value.
Answer:
The answer is "Option d".
Explanation:
The Iteration Management is also an activity in which all members of the team will determine how many the backlog team will allocate towards the next Iteration, and each team wraps up the work only as a group of determined iteration targets. in the given question the "choice d" is correct because The plans to achieve without training entered PO or design staff and requirements have not even been identified, and the wrong choice can be defined as follows:
- In choice A, T' he PO doesn't give the story detail, that's why it's incorrect.
- In choice B, the doesn't a team left the past for more refining with the PO in the Project Backlog, that's why it's incorrect.
- In choice C, The Development Team has not found some other team dependency, that's why it's incorrect.
Answer:
top down approach
Explanation:
Top down approach is process of breaking down system into sub-system which helps in formulating the overall system. At the end every sub system can be refined with more details.
While bottom up approach is process of gathering systems to design large complex system.
Top down is better as basic information is present and resources can be utilized effectively without impacting maintennance and operations.
