This results in a program that is fast in its responses and free of errors. Also, a Unified modeling Language (UML) will be used to study use requirements in the system and identify possible cases for users at various levels. Use Case diagrams in UML will allow us to establish behavioral patterns for the users of the system in order to correctly asses and develop programming features necessary in an organized manner.
According to the notes of Jeffrey A. Hoffer, Joey F. George, Joseph S. Valacich (2009) presented in association with their distinguished course in modern systems analysis, the definition for the waterfall model is a traditional model that works in many phases, and is often useful in the design of new software systems. In this model, the first phases begins upon the completion of the proceeding phase, with each phase following sequentially. These systems have either no instance or only isolated instances of backtracking and looping. This system provides both simplicity in management and ease of use for the end user, and so lends itself to goal development in each phase (Higgins 2009).
The performance of the system will be evaluated in this section, including a detailed discussion of the operations necessary for the system to function. Functional requirements will necessitate the division of the system between two user types to be referred to as administrative users (Admin) and student users (students). Assessment of functional requirements will allow for the effective assessment of system requirements.
Non-functional requirements enhance the understanding of unique and specified requirements of the system that are not related to system functionality, including the ease of use and specific hardware/software/upkeep necessary for the successful implementation of the project.
According to the Inopedia hompage, the definition UML provides a nonproprietary standard of best-practices for engineers in software development. UML is a third