Software Development Methodologies |
Lecture 10 | |
Software Development Methodologies Home - Lecture Support - Lecture 10 | |
|
Quick Links
|
There are different implementations of the software lifecycle, designed to reduce risk of failure The standard description of a software lifecycle is often given in the 'waterfall' form. This form is now largely discredited because it assumes that you only proceed to the next stage of the lifecycle when the current stage is fully completed, i.e. you must know all the requirements of a system before going on to the specification, design, coding and testing stages. To overcome these problems, variations in the implementation of the software lifecycle exist, including the incremental and evolutionary approaches. However the approach rapidly gaining acceptance is the Unified Process, which emphasises phases as well as the lifecycle stages. Legal issue, such as the Data Protection Act, must be designed into a system; they cannot be an afterthought It is better to design features into a system at its start than to add them in a subsequent maintenance phase. Legal issues, such as the Data Protection Act, place additional, often non-functional, requirements on a system and must be considered as essential requirements alongside those requested by the customer. Group working is essential for successful software development, but must be considered within the organisational structure Group working is vital to the efficient and effective development of an information system, since such a development is dependent upon many stakeholders. However, it is important to consider the organisational structure and the manner in which it typically arrives at decisions. CASE technology has variable reception- some good experiences and some bad experiences The use of computer-based technology in itself does not make a poor developer better. Tools can be used well and they can be used badly. A lot of CASE technology has been poorly regarded for the exaggerated claims made by vendors and an unrealistic expectation of their benefits. As with all new methods, techniques and tools, in whatever discipline, CASE technology requires training and familiarity in order to gain the greatest benefits. |
Quick Tips |
||
|
||||
|