This is a repository for team A of PRT 583 Project Development Methodology unit to collectively work as a part of team on different refactoring concepts.
Date : 23 / 04 / 2020
Due Date for submission: every week from week 7, final project to be submitted on week 11. Solution will be implemented every week.
Students Names
| Student ID | Student Name |
|---|---|
| s317999 | ANIL CHAUDHARI |
| s315570 | SUJAN KAFLE |
| s260598 | SURENDRA PANDAY |
| s315674 | THESHAN RANATHUNGA MUDIYANSELAGE |
This is a software development process where we implement 15 to 16 design patterns using real scenarios individually but work as a group in Agile structure with the feeling that you are working in industry to refactor a codebase.
Showing your understanding of design pattern is more important than showing a working code in every sprint
Main objective of this project is to understand Design patterns and refactoring concepts and Agile practices.
- Abstract Factory
- Builder Pattern
- Factory Method
- Prototype
- Singleton
- Adapter
- Bridge
- Composite
- Decorator
- Facade
- Flyweight
- Proxy
- Command
- Mediator
- Observer
- Visitor
- Iterator
- Chain of Responsibility
- Template method
- Strategy
- State
Every week team members choose 3 to 4 random design patterns every week or in each iteration and work independently and write Before and After stages of implementing design patterns in your choice of programming language but pseudocode is important than showing working code as that is less of priority for showing competency in design pattern. For design pattern showing ER diagrams as well would be required. Tasks will be posted in Trello and implementation would be posted in your github repository.
Create your own branch and do your work and do a push to your branch every week to show your work to Lecturer. Otherwise, you could end up overwriting your code with someone else code unknowningly.
Team members then can share knowledge of design pattern learnt previously to other team members who will be learning and implementing those design patterns.
It is suggested to choose a different dissimilar design pattern to that of your peers so that what you learn would be independent but it's not so important to choose a different design pattern necessarily. Sometimes, you could have overlap as well with one of your team members
You have to come up with your own example to show you have learnt that design pattern
Please avoid copying from internet as mark will be zero for that case