Developing projects outside of a classroom setting can be intimidating for students and is not always a seamless process. Real-World Software Projects for Computer Science and Engineering Students is a quick, easy source for tackling such issues. Filling a critical gap in the research literature, the book:
Is ideal for academic project supervisors.
Helps researchers conduct interdisciplinary research.
Guides computer science students on undertaking and implementing research-based projects
This book explains how to develop highly complex, industry-specific projects touching on real-world complexities of software developments. It shows how to develop projects for students who have not yet had the chance to gain real-world experience, providing opportunity to become familiar with the skills needed to implement projects using standard development methodologies.
The book is also a great source for teachers of undergraduate students in software engineering and computer science as it can help students prepare for the risk and uncertainty that is typical of software development in industrial settings.
| Authors |
|
ix | |
|
|
|
1 | (12) |
|
|
|
1 | (3) |
|
1.2 Fundamental elements of project-based learning |
|
|
4 | (1) |
|
|
|
5 | (3) |
|
1.4 Challenges when designing a PBL course |
|
|
8 | (1) |
|
1.5 Incremental project-based learning |
|
|
8 | (2) |
|
1.6 Target audience and structure |
|
|
10 | (3) |
|
2 Design dimensions of project courses |
|
|
13 | (18) |
|
2.1 Customers and projects |
|
|
13 | (6) |
|
|
|
14 | (2) |
|
|
|
16 | (3) |
|
|
|
19 | (3) |
|
|
|
19 | (1) |
|
|
|
20 | (2) |
|
2.3 Supervision and lectures |
|
|
22 | (1) |
|
|
|
22 | (4) |
|
2.5 Uncertainties when planning the course |
|
|
26 | (5) |
|
|
|
26 | (1) |
|
|
|
27 | (1) |
|
2.5.3 Project difficulties |
|
|
27 | (1) |
|
2.5.4 Customer involvement |
|
|
28 | (1) |
|
2.5.5 Experience with methodology and technology |
|
|
29 | (1) |
|
|
|
29 | (2) |
|
|
|
31 | (20) |
|
3.1 Introduction to project planning |
|
|
31 | (1) |
|
|
|
32 | (3) |
|
|
|
35 | (1) |
|
|
|
36 | (3) |
|
3.5 Communication planning |
|
|
39 | (2) |
|
|
|
41 | (6) |
|
3.6.1 Product backlog and prioritization |
|
|
42 | (1) |
|
|
|
43 | (1) |
|
3.6.3 Sprint plan meeting |
|
|
43 | (1) |
|
3.6.4 Daily standup meeting |
|
|
43 | (1) |
|
3.6.5 Retrospective meeting |
|
|
44 | (1) |
|
3.6.6 Sprint review meeting |
|
|
44 | (1) |
|
|
|
44 | (1) |
|
|
|
45 | (1) |
|
3.6.9 100% coverage for unit tests |
|
|
45 | (1) |
|
3.6.10 User acceptance test |
|
|
45 | (1) |
|
|
|
46 | (1) |
|
|
|
46 | (1) |
|
3.6.13 Test-driven development |
|
|
46 | (1) |
|
|
|
46 | (1) |
|
|
|
47 | (1) |
|
3.7 Tools and infrastructure |
|
|
47 | (4) |
|
|
|
51 | (16) |
|
4.1 Problem space vs. solution space |
|
|
51 | (2) |
|
|
|
53 | (3) |
|
|
|
56 | (2) |
|
|
|
58 | (9) |
|
4.4.1 Requirement Engineering |
|
|
59 | (1) |
|
|
|
60 | (2) |
|
|
|
62 | (1) |
|
|
|
63 | (4) |
|
|
|
67 | (12) |
|
|
|
67 | (3) |
|
|
|
68 | (1) |
|
|
|
68 | (1) |
|
|
|
69 | (1) |
|
|
|
70 | (9) |
|
|
|
70 | (1) |
|
|
|
71 | (1) |
|
|
|
71 | (1) |
|
|
|
72 | (1) |
|
|
|
73 | (1) |
|
5.2.6 Prestudy of problem space vs. solution space |
|
|
73 | (1) |
|
5.2.7 Software development methods |
|
|
74 | (1) |
|
|
|
74 | (1) |
|
5.2.9 Architectural design |
|
|
75 | (1) |
|
|
|
75 | (1) |
|
|
|
76 | (1) |
|
5.2.12 Project evaluation |
|
|
76 | (1) |
|
|
|
77 | (1) |
|
|
|
77 | (2) |
|
6 Incremental project-based learning |
|
|
79 | (8) |
|
6.1 Motivations to the incremental project-based learning |
|
|
79 | (3) |
|
6.2 Iteration 1 or "classical" project course setting |
|
|
82 | (1) |
|
6.3 Enhanced iteration or "classical" project course setting |
|
|
82 | (5) |
|
|
|
83 | (1) |
|
|
|
84 | (1) |
|
|
|
84 | (3) |
|
7 Dissemination of results |
|
|
87 | (14) |
|
|
|
87 | (1) |
|
|
|
88 | (3) |
|
7.3 Article types and formats |
|
|
91 | (7) |
|
7.4 Article type, suggested venues academic year wise |
|
|
98 | (3) |
| Appendix 1 Project description |
|
101 | (8) |
| Appendix 2 Student background questionnaire |
|
109 | (2) |
| Appendix 3 Lectures in PRO1000, Spring semester 2020 |
|
111 | (2) |
| Appendix 4 Suggested structure of the project report |
|
113 | (2) |
| Appendix 5 Templates of Sprint reports |
|
115 | (2) |
| References |
|
117 | (4) |
| Index |
|
121 | |
Varun Gupta received his Ph.D and Master of Technology (By Research) degrees in Computer Science & Engineering from Uttarakhand Technical University and Bachelor of Technology with Honors degree from Himachal Pradesh University respectively. He also holds an MBA degree from Pondicherry University.He currently is working as Postdoctoral Researcher with Universidade da Beira Interior, Portugal. He is also Visiting Postdoctoral Researcher, School of Business, FHNW University of Applied Sciences and Arts Northwestern Switzerland. He was an Honorary Research Fellow of the University of Salford, Manchester, United Kingdom (2018 to 2021). Dr. Gupta is an Associate Editor of IEEE Access, Associate Editor of International Journal of Computer Aided Engineering & Technology, Associate Editor of the IEEE Software Blog, Associate Editor of Journal of Cases on Information Technology (JCIT). His area of interest is Evidence based Software Engineering, Evolutionary Software Engineering (focusing on requirement management), Business Model Innovation, and Innovation Management.
Anh Nguyen-Duc is an Associate Professor at the University of South Eastern Norway since 2017. He received his Ph.D in Computer and Information Science at Norwegian University of Science and Technology from Trondheim, Norway. His current research interests include software startups, software ecosystems, AI ethics and secure software development. He has more than 80 peer-reviewed publications in high-ranked journals and conferences. He has three edited books in business-driven software engineering. He serves as a chair of 10 organization committees, a reviewer of recognized journals, and guest editor of special issues in different software engineering journals. Recently, Anh has worked as a regional coordinator in an EU Interreg project value of 4.2 million Eur. He is currently the chairman of the Software Startup Research community (www.softwarestartups.org)
