LifeCycle - Foundations of Software Engineering(for...

Info icon This preview shows pages 1–9. Sign up to view the full content.

View Full Document Right Arrow Icon
Foundations of Software Engineering (for non-software engineers) Software Development Life Cycles Guy-Vincent Jourdan
Image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
Software Life Cycles Early software development was done with no planning, no formal design and analysis. To develop software, you would code, debug and test, “until done”. Software development life cycles have been introduced starting in 1970 to formalize a framework for the software development phases and give tools to assess whether the requirements and quality criteria expected have been satisfied
Image of page 2
Software Life Cycles Futrell, R., Shafer, D. and Shafer L., Quality Software Project Management , Prentice Hall PTR, 2002 Van Vliet, H. Software Engineering: Principles and Practice, 2nd Edition , Wiley, 2000 Christensen, M.J. and Thayer, R.H. Project Manager’s Guide to Software Engineering’s Best Practices , IEEE Press, 2002 IEEE 12207-1996 Software life cycle processes – Description IEEE 1074-1997 Developing Software Life Cycle Processes
Image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
Software Life Cycles Most well known software development life cycles: The waterfall model The v-shaped model The prototyping model The rapid application development model The incremental development model The spiral model The agile model
Image of page 4
The waterfall model Waterfall SDLC have been introduced as early as ’70. Several refinements have been proposed over the years, but the model is still used extensively today. It is not necessarily followed precisely, but the “flow” that it captures is often the default model that is used, usually informally, in many software projects today.
Image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
The waterfall model Waterfall SDLC example proposed by Boehm in 76. Software requirements Preliminary conceptual design Detailed design Code and debug Integrate and test Operation and maintenance System (user) requirements Barry W. Boehm. Software engineering. IEEE Transactions on Computers , C-25(12):1226-1241, December 1976.
Image of page 6
1. System (user) requirements: system user group identifies and develops the system level requirements in sufficiently complete details that preliminary software requirements can be specified. 2. Software Requirements: translation of the purposeful requirements identified in phase 1 into structural and functional requirements, focusing on the nature and style of the software being developed, the data and information that will be required, the required functionality, performance, interfaces. The resulting requirements are validated and a document is produced. The waterfall model
Image of page 7

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
3. Preliminary conceptual design: the requirements are converted into a preliminary design, including data structure, software architecture, identification of procedures and functions… 4. Detailed design: definition of the program modules and inter-modular interfaces, data format, detailed algorithms description etc. Output must allow a direct coding.
Image of page 8
Image of page 9
This is the end of the preview. Sign up to access the rest of the document.

{[ snackBarMessage ]}

What students are saying

  • Left Quote Icon

    As a current student on this bumpy collegiate pathway, I stumbled upon Course Hero, where I can find study resources for nearly all my courses, get online help from tutors 24/7, and even share my old projects, papers, and lecture notes with other students.

    Student Picture

    Kiran Temple University Fox School of Business ‘17, Course Hero Intern

  • Left Quote Icon

    I cannot even describe how much Course Hero helped me this summer. It’s truly become something I can always rely on and help me. In the end, I was not only able to survive summer classes, but I was able to thrive thanks to Course Hero.

    Student Picture

    Dana University of Pennsylvania ‘17, Course Hero Intern

  • Left Quote Icon

    The ability to access any university’s resources through Course Hero proved invaluable in my case. I was behind on Tulane coursework and actually used UCLA’s materials to help me move forward and get everything together on time.

    Student Picture

    Jill Tulane University ‘16, Course Hero Intern