Slide set 1 (Traditional Software Development) (1).pptx

SDE

1. Traditional Software Development

2. Software and its types Module Learning Objective 01 History and evolution of software engineering 02 Methods of software development 03 Waterfall method of software development 04 Conflicts 05 How conflicts between the development and operation team impact product development?

3. Software A software is an organized information in the form of operating system, programs, utilities and applications that enables a computer to work. Any set of machine-readable instructions that directs a computer processor to perform specific operations. I ncludes computer programs liberaries and their associated documentation. S oftware programs are stored on the secondary storage and whenever they are needed, they are loaded in compter memory.

4. Software An interface between computer and human being who uses them. Software is everything that governs the functioning of a computer. Software is product as well as vehicle. Siftware is an information transformer: Producing M anaging A cquiring M odifying Displaying Transmiting

5. Software Engineering Definition Software Engineering is the technology that encompasses a process, a set of methods and an array of tools that allow professionals to build high quality computer software - By Roger S. Pressman

6. The software development models are the various processes or methodologies that are being selected for the development of the project depending on the project’s aims and goals. There are many development life cycle models that have been developed in order to achieve different required objectives. Software Development Models

7. Different Software Life Cycle Models Many life cycle models have been proposed so far, with their own merits and demerits. A few important and commonly applied life cycle models are as follows:

8. “ Great software today is often preferable to perfect software tomorrow. If you give your users something to play with early, their feedback will often lead you to a better eventual solution. ” —ANDY HUNT One of the seven original authors of Agile Manifesto

9. Explanation of Classical Model of Waterfall In “The Waterfall” approach, the outcome of one phase acts as the input for the next phase sequentially.

10. First Stage – Feasibility Study T he following activities are covered during the feasibility study phase. Financial Feasibility Technical Feasibility Client visit Study of input-output data Case study

11. Second Stage – Requirement Analysis & Specification Design T he following activities are carried out during the requirements analysis and specification design phase. Requirements gathering and analysis Requirement specification

12. Third Stage – Design Phase T he following activities are covered during the design phase. Creation of system design as per the requirements gathered during the previous phase. Definition of overall system architecture Documentation of design The two design phases are: High level design Low level design

13. Fourth Stage – Coding and Unit Testing T he following activities are covered during the code and unit testing phase. Implementation phase Developing source code Program modules Testing of modules Debug the errors

14. Fifth Stage – Integration and System Testing T he following activities are covered during the integration and system testing phase. Integration of planned manner Steps of integration Addition of modules System testing

15. Fifth Stage – Integration and System Testing (contd.) This is a level of software testing where a complete and integrated software is tested. The various test may include: Alpha Testing (Development team) Beta Testing (Set of customers) Acceptance Testing (customers)

16. Sixth Stage – System Deployment and Maintenance The following activities are covered during the system deployment and maintenance phase. Product deployment Development and maintenance Maintenance Corrective maintenance Perfective maintenance Adaptive maintenance

17. Discipline Every phase has a defined start and end point. The progress can be distinctly identified by both the client and the software developer, through the use of milestones Time and cost Effective The emphasis on requirement and design, before writing the codes/programs ensures the minimal wastage of time, effort, cost and decreases the risk of slipping of schedule. Quality Improvement The flaws can be easily caught and taken care of the design stage much earlier than the testing stage Advantages of Waterfall Model

18. Drawbacks of Waterfall Model

19. Traditional IT Organizations Cultural hindrance between development and operations team in traditional SDLC. Development and operations: two sides of an equation-holding their own roles and responsibilities. Development team works independently on code. Code sent to testing team for validation. Operations team comes in toward the end of the process, handover of release. No collaboration.

20. Developer vs IT Operations Conflict Meaning Development Changes Confusion/ Lack of communication Operations Stability

21. Problems with the Traditional Development and the Operations Organizational Silos Different Mindsets Different Implementations Different Tools Lack of interest in learning other tools Different environment Loss of work Blame game Build Rollback Disintegrated process No feedback loop