Systems analysis refers to a problem solving technique where a business or procedure is studied and the goals are identified in order to create information systems to help the business achieve their goal more efficiently and easier. Systems analysts obtain feedback from the system users in various ways e.g. interviews, questionnaires etc. More importantly they find out from the users what their specific requirements are regarding the proposed system and then use the information obtained to formulate requirements for the system, the system is then written ensuring that all the requirements and expectations are met.
Summary
Various Approaches for Systems Analysis
• Waterfall model.
• Prototyping.
• Rapid Application Development.
Waterfall model
The waterfall model consists of five phases such as requirements, Design, implementation, verification and maintenance. The method is a sequential design process where progress is seen as flowing downwards in a steadily manner, each development phase has its own distinct goals. The model is similar to water flowing down a cliff it can only flow in one way and cannot go back up it is the same with waterfall development ,after a development phase is completed it proceeds to the next development phase you cannot go back.
Phases explained:
The Requirements phase
This is the phase where the requirements are noted, feedback regarding requirements are obtained from users
The Design phase
The requirements from the previous phase are
Waterfall model is simple and easy to use. (Paper 11) This model is used only when the requirements are very well known, clear and fixed as well as the project is small. ( important) The client here will not be able to see the project in between of any phase. It will be available once the project is deployed. Waterfall model requires lot of documentation.
System analysts collect the existing functional requirements and system documentation from the old website of the company that is running by using the fact finding techniques. In addition, they will interview the employees to see what should be modify and update. System analysts are responsibility to select developing the software in house or packed solutions.
Waterfall does have its issues: the process is generally “uni-directional” meaning that once the project hits a certain stage, there’s no mechanism to go back to a previous stage. This prohibits this method from being responsive to changing environments and/or requirements. The extensive documentation required at each stage (requirements, specification, design documentation, test plans and status) requires a great deal of time to complete. Additionally if it is discovered that there was a major issue with a missing requirement or the coding (and it’s uncovered in time) it is extremely expensive to make an adjustment.
A traditional approach got a sequence of steps and cannot come back once done with sequence steps. Waterfall model is similar to this when we discuss traditional approach in software industry (Winston W. Royce, 1970). There is no need for all the projects to follow all steps in sequence. Some projects can skip some steps or can perform
Waterfall Model is the first software development process model proposed by Royce in 1970 which is a linear sequential software development life cycle (SDLC) model. It is a sequential process model which does not overlap. It means that until the one phase is not completed then next phase cannot start.
The Waterfall Method was first Process Model to be presented. It is likewise alluded to as a straight consecutive life cycle show. It is exceptionally easy to comprehend and utilize. In a waterfall model, each stage must be finished completely before the following stage can start. This sort of model is essentially utilized for the for the project which is little and there are no indeterminate prerequisites. Toward the finish of each stage, a survey happens to decide whether the project is on the correct way and regardless of whether to proceed or dispose of the project. In this model the testing begins simply after the advancement is finished. In waterfall display stages don 't cover.
The Waterfall Model is a sequential design process, often used in software development processes, in which progress is seen as flowing steadily downwards (like a waterfall) through the
This phase starts with gathering the business requirements in the baseline spiral. In the subsequent spirals as the product matures, identification of system requirements, subsystem requirements and unit requirements are all done in this phase.
Waterfall model: This model has five phase like requirements, design, implementation, verification and maintenance. It is a sequential process. It is originated from manufacturing and construction industries. It is proposed by Royce. This model is series of cascading steps that covers actual development process of the project and has iteration between its steps. The main problem with this model is that rigidity of the model and there is no iteration between any other stages other than adjacent stages. As we all know that web is the fastest mode of developing technology, therefore a model which will automatically adapt to the changes taking place in the environment are to be preferred.
Perhaps one of the most glaring differences between Agile development approaches and other models like the waterfall approach is the sequentiality that exists in the latter method. In the waterfall method the projects start with a requirements planning stage,
Waterfall model is based on sequential process that is used in software development process. It takes place in steps. It is called as waterfall because it moves step by step in downward direction. As seen in manufacturing and construction site, each process is well structured and carried out step by step, in software development Waterfall model carries out all phases in sequential manner. All the phases like Conception, Initiation, Analysis, Design, Construction, Testing, Implementation and Maintenance are carried out in a sequential manner, step wise. It is stated that the first formal description of Waterfall model was made in 1970 in the article written by Winston W. Royce. Though the first use of waterfall model was made in 1976 in the article written by Bell and Thayer.
Ans: The waterfall model shows a process, where developers are to follow these phases in order:
Systems analysis is a technique that divide a system into small parts for the aim of the learning however well those part components work and move to accomplish their purpose.
First of all, here is some brief description about Agile development model and Waterfall development model. Agile development model is a type of Incremental model which means the software is developed in incremental and rapid cycles. This results in small incremental releases with each release building on previous functionality. Software quality is ensured to maintain well by testing each release thoroughly. It is usually used for time critical applications.
The traditional approach to software development can be illustrated through the waterfall model which is time tested and easy to understand. The waterfall model approaches software development in sequential manner, completing one activity before the other. It brakes up project in stages: requirement analysis, design, coding and testing, operation and maintenance (see fig. 1 below).