01_Introduction - Paradigmatic Software Development...

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

View Full Document Right Arrow Icon
Paradigmatic Software Development Introduction Paradigms What they are and why it is important to understand them.
Image of page 1

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

View Full Document Right Arrow Icon
Paradigm A philosophical and theoretical framework of a scientific school or discipline within which theories, laws, and generalizations and the experiments performed in support of them are formulated. Merriam-Webster Online Dictionary A methodology is a specific implementation of a paradigm. Paradigms – What A paradigm is a model or pattern, an archetype, for solving problems. Inherent in a paradigm are basic assumptions about problems. Consequently a paradigm defines or structures how problems are approached. Paradigms constrain the way that we think about problems, and guide the way problems are solved. A paradigm provides a broad philosophy to be adopted during the development process. It describes the general approach to be used, rather than the specific tools and methods.
Image of page 2
Paradigm Examples Computational Paradigms (Models of Computation) Function oriented State oriented Programming Paradigms – Procedural Object Oriented – Logic – Functional Development and Process Paradigms Waterfall Model Iterative/Incremental Development Agile Processes The Quality Paradigm Paradigms – Why Distinguishing between paradigms is valuable for solving problems, for several reasons: Understanding a paradigm involves identifying the important entities and strategies in problem solving. Knowing which paradigm is being applied reveals assumptions being made in modeling a problem. Understanding paradigms helps the problem solver avoid biases. Being able to state the advantages and drawbacks of various paradigms permits a decision between paradigms based on the problem under consideration.
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 Development The process of developing software products Software Development Cost estimation, budgeting, scheduling. Requirements analysis. • Design. • Implementation. • Testing. • Deployment. Measuring products and processes. Quality improvement. • Maintenance. And so on …
Image of page 4
Product Viewpoint What functionality is provided? What performance characteristics are required for the functions provided?
Image of page 5

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

View Full Document Right Arrow Icon
Image of page 6
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