SE
Software Engineering
SE1
Points:
- Project: 50 points
- 1st checkpoint (4th class): 15 pt
- 2nd checkpoint (7th class): 15 pt
- Final check (e-mail): 20 pt
- Practical tests: 30 points
- Theoretical tests: 20 points
- Activity points: individual arrangement with excercise supervisor
Grades (at least 25 points from project and 25 points from the rest):
- 91 and more - 5
- 81-90 - 4.5
- 71-80 - 4
- 61-70 - 3.5
- 51-60 - 3
- 50 and less - 2
I’ll do you one better! Why is Software Engineering?
Excercises
Lecture slides
- Literature and grade rules
- Introduction: roles and processes
- Can we PLEASE start programming already? - Software Developement Methods
- Doing agile or being Agile? - Software Developement Methods
- Are we Agile? - Software Developement Methods parts II and III
- Meeting the client - Gathering project requirements
- Agile - game of ideas in agile projects - Guest lecture 2019/20 Jakub Niemiec @ Netcompany
- Do not draw Finite State Machines on a first date - Tools supporting gathering of requirements: FURPS, BPMN, UML, User Stories
- Dude, where is my code? - Tools for code management: software revision systems and package repositories
- My code ALWAYS works - About tests and design principles
- Toolbox (part 1): git, Continuous Integration, bugtracking
- Toolbox (part 2): NuGet, Moq, memory and CPU profiling
- Utrzymywalne aplikacje (Guest lecture by Michał Sochoń @ CodiLime)
- Rafał Głowiński's blog @allegro
Rehearsal before test
Further reading
- Agile Manifesto
- Faux Agile comments - Ron Jeffries
- Manifesto for Software Craftsmanship
- Manifesto for Software Craftsmanship - Discussion
- DSDM Handbook
- Some comments on DSDM Timeboxes and SCRUM sprints
- Scrum Guide
- XP rules
- Concepts on how to use UML
- Use Cases
- Hexagonal architecture
- SOLID - the basic clean code rules
- TDD cycle
- git flow
Delivery schedule:
| No | Topic | |
|---|---|---|
| 1. | Presentation of The Project Game project | Use Case diagrams |
| 2. | Use Case presentation | Class diagrams |
| 3. | Class diagrams presentation | State diagrams |
| 4. | Consultations (prepared system specification in the areas of: Requirements, Architecture and Game Rules) | |
| 5. | State diagrams presentations | Activity diagrams |
| 6. | Activity diagram presentation | Sequence diagrams |
| 7. | Consultations (complete system specification created with accordance to initial system description and supervisor's guidelines) | |
| Last lecture | Practical and theoretical test (during lecture) | |
| First day of examination period | Specification is sent by the e-mail to the group supervisor by 12:00 p.m. (Polish time) | |
Rules:
- Only written arrangements (acknowledged by the supervisor) may be the basics for preparing the specification
- Diagram presentation part of the classess:
- All teams send PDFs with their specification (till 10:00 a.m.) to the e-mail of groups supervisor
- The diagrams of the group (or two) are chosen by the supervisor to be discussed
- All e-mail communication should be marked with [IO] in the title and sent from the student's e-mail in mini.pw.edu.pl domain
- All attached files should contain: SE, leader surname and document topic specification eg. SE_Smith_UseCase.pdf
