4. Explain why change is inevitable in complex systems and give examples (apart from prototyping and incremental delivery) of software process activities that can help predict possible changes and make the software being developed more resilient to change.

The answer is phishing : )

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

The one that’s keeps you out of legal trouble

It took 1.75 sec to get to the batter