Software Applications Undergo Software Development Life Cycle

Good Essays
Software applications undergo software development life cycle (SDLC) which involve requirement gathering, system design, application development, quality analysis and maintenance. Different strategies such as extreme programming, agile, and scrum can be employed to achieve efficient software development and maintenance plan. System analysis and design models built using object oriented methodology and UML help in understanding the purpose of software application and act as blueprint to implement the software. 2.1 Object Oriented Analysis and Design Object–Oriented Analysis and Design (OOAD) approach is important for successful planning and execution of web applications which can function efficiently over long period of time. OOAD approach…show more content…
Functional requirements are operations, technical computation and data processing that explain the functionality of the application. Non-functional requirements describe expected behaviour of the functionality specified for the system. Non-functional requirement specifies the design constraints and characteristics that need to be taken care of to satisfy user requirements. Non-functional requirement specifies the behaviour of the system with respect to various quantifiable attributes like performance, availability, etc. [8]. System design specifies plan to implement functional requirements whereas system architecture specifies plan to implement non-functional requirement. Functional requirements can be explained using use cases and non-functional are listed in a table. Functional Requirements for Travel Helper are explained using use cases models. Non-Functional Requirements are listed in Appendix A. 2.2.2 Use Case Use case is a behavioural diagram. It depicts the sequence of actions a user of a system can perform to achieve functionality of system. User has a role in the system which needs to be satisfied. Use Case describes complete details of the role, condition and action corresponding to functional requirement of the system. The various sections of use case model are explained below. 1. Use Case Name: Describes the name of the user action. 2.
Get Access