Convert the following arm assembly program (everything) into x86 program and then describe the differences between data movement instructions. @ this is my program .section .data a: .word 2 @ 32-bit variable a in memory b: .word 5 @ 32-bit variable b in memory c: .word 0 @ 32-bit variable c in memory .section .text .globl _start _start: ldr r1, =a @ load the memory address of a into r1 ldr r1, [r1] @ load the value a into r1 ldr r2, =b @ load the memory address of b into r2 ldr r2, [r2] @ load the value b into r2 add r1, r1, r2 @ add r1 to r2 and store into r1 ldr r2, =c @ load the memory address of c into r2 str r1, [r2] @ store r1 into memory c mov r7, #1 @ program termination: exit syscall svc #0 @ program termination: wake kernel .end

Good job, jason. he's more successful than i'll ever be loolll

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