Translate the following C code to MIPS assembly code. The function g takes the address of an integer as input and outputs an integer. The function h takes an integer as input and outputs an integer. Assume the following: • Both functions g and h have been implemented. • d is a word (int) array that is already defined. d’s address is in $s0. • $s1 is allocated to sum. • $s2 is allocated to i. // prototype of g and h int g(int * a); int h(int n); // d is a word array // initialize sum sum = 0; for (i = 0; i < 1024; i += 1) { g(&d[i]); // pass d[i]’s address to g sum += h(d[i]); // note that function g may change d[i] }

Personality comes from within

Solution: the categorization of functional and non-functional requirement are as follows: some of the more typical functional requirements include: • business rules• transaction corrections, adjustments and cancellations• administrative functions• authentication• authorization levels• audit tracking• external interfaces• certification requirements• reporting requirements• historical data• legal or regulatory requirementswhile,some typical non-functional requirements are: • performance – for example response time, throughput, utilization, static volumetric• scalability• capacity• availability• reliability• recoverability• maintainability• serviceability• security• regulatory• manageability• environmental• data integrity• usability• interoperability