The software process models Essay Example | Topics and Well Written Essays - 1000 words

The software process models - Essay ExampleThe askments are establish 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 mainly used in small, simple throwaway projects with output as short lived demos, proof-of-concept or prototypes. No kick downstairs planning, take chances assessment, designing, building, testing phases are required.The administrative system in AILS requires thorough gathering of requirements, understanding the running(a) 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 butt joint be used the requirement of gainin g user satisfaction. Interface can be made and tested missing or ambiguous portions can be identified and fixed in the next build trough a workable interface is achieved.In the AILS administrative system, the requirements necessitate the need of completely capturing of fixed requirements and functionalities to promote 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 in the first place the requirements change again.For the user interface, applying the model would produce a workable solution but with an overhead of unessential 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 kitchen stove and requirements. An initial role based interfac e, accessing data may be developed and tested.