SLIDE 1
2
Software Process
Requirements
Agile SCRUM Waterfall / V Cycle Spiral Quality Collaborative Development
T esting Design Modular
User Interface Refactoring Pattern
Course Review Software Process Agile Spiral Waterfall / V Cycle - - PowerPoint PPT Presentation
Course Review Software Process Agile Spiral Waterfall / V Cycle - - PowerPoint PPT Presentation
CPSC 310 Software Engineering Course Review Software Process Agile Spiral Waterfall / V Cycle SCRUM Design Requirements T Modular esting Pattern Refactoring User Interface Quality Collaborative Development CPSC310 TOPICS 2
SLIDE 2
SLIDE 3
3
Software Process
Requirements
Agile SCRUM Waterfall / V Cycle Spiral Quality Collaborative Development
T esting Design Modular
User Interface Refactoring Pattern
- describe benefits of
using a software process
- describe waterfall
and spiral model including drawbacks
- describe the
importance of agile methods
SLIDE 4
4
Software Process
Requirements
Agile SCRUM Waterfall / V Cycle Spiral Quality Collaborative Development
T esting Design Modular
User Interface Refactoring Pattern
- describe the
general principles
- f agile
- understand that
agile encompass different approaches and that it's not a silver bullet
- describe SCRUM
- Roles
- Ceremonies
- Artifacts
SLIDE 5
5
Software Process
Requirements
Agile SCRUM Waterfall / V Cycle Spiral Quality Collaborative Development
T esting Design Modular
User Interface Refactoring Pattern
- Why requirements
are needed
- How to elicit
requirements
- User stories, and
how to write good
- nes (INVEST
guidelines)
SLIDE 6
6
Software Process
Requirements
Agile SCRUM Waterfall / V Cycle Spiral Quality Collaborative Development
T esting Design Modular
User Interface Refactoring Pattern
- Describe benefits of
design
- How to approach
design
- UML Class Diagram
and Sequence Diagram (210 review)
SLIDE 7
7
Software Process
Requirements
Agile SCRUM Waterfall / V Cycle Spiral Quality Collaborative Development
T esting Design Modular
User Interface Refactoring Pattern
- Understand/apply
- Strong cohesion
- Low coupling
- Information hiding
- Liskov Substitution
Principle
- Open/Closed
Principle
- Law of Demeter
SLIDE 8
8
Software Process
Requirements
Agile SCRUM Waterfall / V Cycle Spiral Quality Collaborative Development
T esting Design Modular
User Interface Refactoring Pattern
- Describe benefits
and drawbacks of design patterns
- Use the following
patterns:
- Factory
- Singleton
- Decorator
- Proxy
- Template
- Composite
- Adapter
- Observer
- Know what anti-
pattern are
SLIDE 9
9
Software Process
Requirements
Agile SCRUM Waterfall / V Cycle Spiral Quality Collaborative Development
T esting Design Modular
User Interface Refactoring Pattern
- Why refactor
- When refactor
- How to refactor
- Identify code
smells
- Apply
transformation rules
- Ensure that
behavior is constant
SLIDE 10
10
Software Process
Requirements
Agile SCRUM Waterfall / V Cycle Spiral Quality Collaborative Development
T esting Design Modular
User Interface Refactoring Pattern
- be able to assess
the usability of an interface
- Nielsen Principles
- f Design
- Components for
usage
- Usability Testing
SLIDE 11
11
Software Process
Requirements
Agile SCRUM Waterfall / V Cycle Spiral Quality Collaborative Development
T esting Design Modular
User Interface Refactoring Pattern
- Types of Testing
(Unit, Regression, Integration, Acceptance)
- Black Box Testing
- Equivalence
classes
- Boundary Tests
- White Box Testing
- Coverage
SLIDE 12
12
Software Process
Requirements
Agile SCRUM Waterfall / V Cycle Spiral Quality (mainly code) Collaborative Development
T esting Design Modular
User Interface Refactoring Pattern
- Know that quality is
affected by the whole process
- describe techniques
for checking/ improving code quality
SLIDE 13
13
Software Process
Requirements
Agile SCRUM Waterfall / V Cycle Spiral Quality Collaborative Development
T esting Design Modular
User Interface Refactoring Pattern
- Know why VCS are
great (yes they are)
- Describe the
difference between centralized and distributed VCS
SLIDE 14
14
How to study
- Re-read the slides and follow
the links for clarification and more context.
- Master in-class exercise
- Ask questions on Piazza after
looking if the answer is not already there
- I will be holding office hours
next week (see course calendar)