The requirements are based on system functionalities and roles and so would not undergo any change with time.b) The requirement capturing process for the user interface is an on-going process as a few of the requirements are subjected to change with availability of measures such as skill level of users, type of interface access methodologies, compliance with technological advancements, etc.The model is generally used in small, simple throwaway projects with output as short lived demos, proof-of-concept or prototypes. No separate planning, risk assessment, designing, building, testing phases are required.The administrative system in AILS requires thorough gathering of requirements, understanding the working of existing processes and workflows and data accessing details for integration with the interface which the model fails to provide.For the user interface however, the model can be used the requirement of gaining user satisfaction. Interface can be made and tested. missing or ambiguous portions can be identified and fixed in the next build till a workable interface is achieved.In the AILS administrative system, the requirements necessitate the need of completely capturing of fixed requirements and functionalities to produce a complete product as deliverable. Therefore, the model seems to be appropriate for the task.Spiral model employs risk management approach, an essential requirement in the large mission-critical projects, where reusable, high quality versions of software are delivered before the requirements change again.For the user interface, applying the model would produce a workable solution but with an overhead of unnecessary risk analysis. User interface is not a critical task and therefore does not require extensive risk analysis.For the user interface, the model can be applied owing to the varying scope and requirements. An initial role based interface, accessing data may be developed and tested.
The software process models