lecture1-processes requirments ans use cases

Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development (3rd Edition)

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

View Full Document Right Arrow Icon
1 Lecture 1: Processes, Requirements, and Use Cases
Image of page 1

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

View Full Document Right Arrow Icon
2 Development Processes Early Days: evolve a system – Build and fix – Leads to chaos – Need for intelligent design Waterfall Model – Requirements, Design, Code, Tests, Maintenance
Image of page 2
3 Rational Unified Process Iterative, incremental development: Development cycle : results in a release Iteration phases : Inception, Elaboration, Construction, Transition Phase activities : Business Modeling, Requirements, Design, Implementation, Test, Deployment, Configuration & Change, Project Management, Environment (tools, process design)
Image of page 3

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

View Full Document Right Arrow Icon
4 Factors for Success and the RUP Iterative development: develop part of the functionality, explore designs such as GUI Daily builds: incorporate new code into (partially) complete system; rapid feedback via testing Team experience in shipping multiple products Early focus on building and evaluating a cohesive system architecture (Product Development Practices that Work, MIT Sloan Management Review , 42:2, 2001)
Image of page 4
5 Lightweight vs Heavyweight Process Formal, heavyweight: strict phases with defined formal documentation, often not iterative Agile: adjust to application, activities in one phase differently weighted Extreme programming: smaller projects, all staff eye to eye, paired programming, tests as specifications -> little formal documentation other than code
Image of page 5

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

View Full Document Right Arrow Icon
6 Introduction to Requirements Basic but not sole step in inception Types of requirements: FURPS – Functionality – Usability – Reliability – Performance – Supportability
Image of page 6
Image of page 7
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