After following this course, the students can:
- Carry out all phases of a non-trivial, industrially relevant software development project
- Use modern software development methods
- Assess tools and methodologies as to their usability in the context of such a project
- Assume several roles in a software project
- Assess individual competence and productivity in real-world situations
- Collaborate in a team to achieve a common goal
- Communicate effectively with customers
- Present project results
|
|
Plan and implement a professional software project! In a team of 4 students you will learn to plan, manage and implement a professional real-world software project. All project topics originate from industry partners, outside of the campus. You develop your own solution strategy and learn to organize yourself as a team. You have to collectively specify requirements and define processes for your team. Other main ingredients of this course are to learn how to create a design for a large software architecture and how to assure the quality of such a project. You have the freedom to choose the software engineering process and technologies that fit best to your project and your team. Apart from the technical details, you will acquire experience in communication with a client and you will develop invaluable soft skills. The software engineering project is scheduled to run during one semester. During this time, your team will have an experience direct supervisor from the university, who will provide support with experience and knowledge if you need help.
Assessment and Organization
In the course of this project, three documents have to be delivered. The exact extent of these documents may vary to a certain degree depending on the peculiarities of each project and the development process chosen by the team. But generally, the three documents are: 1) a specification document signed by the team and the industry partner; 2) a design document describing the architecture and detailed design of the solution; and 3) a document describing the quality assurance plan and test protocols, including an acceptance protocol signed by the industry partner. Before each of the documents is due, a steering committee meeting will be held where each group presents their current state to the group of all course participants and university supervisors. At these meetings, the teams will get feedback on their progress and their approach. In addition, each team will receive feedback from their supervisor on a draft version of the documents. The course is graded by the lecturers based on the three provided documents.
|
 |
|