IE04: Integrated Exercise for Software II
AY2023 S2
Last revised on 2024/01/24.
Introduction
Overview
Developing software is an activity that involves, understanding of requirements, design of computational
structures and behavior, and implementation of the designs. It requires practical application and integration of
various knowledge/skills including but not limited to programming and software engineering.
In this course, 4 to 5 students work in teams to learn practical software development by developing a software
that solves a given problem (project theme). Project themes will be decided at beginning of the course,
development is performed incrementally in phases, and results are reported at an interim review and a final review
session. Teams working on the same project theme will compete on developing a better software product. The teams
are required to plan and manage their development using project tools to provide high transparency of their
activity.
For Integrated Exercise for Software II, software that integrates contents covered in multiple 1st to 3rd (up to
S1) year courses will be developed. Themes will include requirements, in addition to the contents of Integrated
Exercise for Software I, on object-oriented design, databases, and user-interfaces.
Goals
- Understand software requirements and define corresponding models
- Create a software design that satisfies functional and quality requirements
- Setup a suitable development environment and effectively manage development activities
- Design and perform sufficient tests to verify software
- Validate software by checking that it meets the needs of stakeholders
Notes
- This course is based on practical activities that requires proactive participation by the students.
- Due to the nature of activity, necessary knowledge/skills vary depending on the theme. Students are requested
to self-study (individually or in teams, outside of classroom hours) any knowledge or skills as required to
complete the project.
- You can decide the programming language and frameworks to be used.
Time and Place
| Class |
Time |
Room |
Instructor |
| Group 1 (std1) |
Wednesday, 2, 3, 4 |
std1 |
Prof. Uday Kiran Rage |
| Group 2 (std2) |
Wednesday, 2, 3, 4 |
std2 |
Prof. Maxim Mozgovoy |
| Group 3 (std5) |
Wednesday, 2, 3, 4 |
std5 |
Prof. Rentaro Yoshioka |
| Group 4 (std6) |
Wednesday, 2, 3, 4 |
std6 |
Prof. Pierre-Alain Fayolle |
Instructors
Professors
TAs/SAs
| Name |
E-mail |
Room |
| Madhavi Palla |
m5272017@u-aizu.ac.jp |
std1
|
| Peter Kudry |
d8232106@u-aizu.ac.jp |
std2
|
| Atsuki Yanada |
m5261202@u-aizu.ac.jp |
std5
|
| Peng Zhao |
m5271509@u-aizu.ac.jp |
std6
|
Schedule
| 1 |
10/4 |
Team formation, setup, read and understand RFP
|
Plan |
Team profile |
|
Common |
| 2 |
10/11 |
Requirements and use-case analysis
|
Req. Def. |
Product backlog |
|
Separate |
| 3 |
10/18 |
Requirements definition and use-case analysis
|
Phase 1 |
Phase backlog, Use-case diagram, Class-diagram (model) |
Hello world |
Separate |
| 4 |
10/25 |
Design and implementation |
Phase 1 |
Use-case diagram (description), Class-diagram (model), UI definition |
UI mockups |
Separate |
| 5 |
11/8 |
Phase 1 demo |
Phase 1 |
Class-diagram, sequence-diagram, program |
Phase 1 product |
Common |
| 6 |
11/15 |
Revise & update requirements and use-cases
|
Phase 2 |
Phase backlog |
|
Separate |
| 7 |
11/22 |
Design and implementation.
|
Phase 2 |
Use-case diagram (description), Class-diagram (model), UI definition |
|
Separate |
| 8 |
12/6 |
Phase 2 demo |
Phase 2 |
Class-diagram, sequence-diagram, program |
Phase 2 product |
Common |
| 9 |
12/13 |
Revise and update requirements and use-cases
|
Phase 3 |
Phase backlog |
|
Separate |
| 10 |
12/20 |
Design and implementation.
|
Phase 3 |
Use-case diagram (description), Class-diagram (model), UI definition |
|
Separate |
| 11 |
1/10 |
Phase 3 demo |
Phase 3 |
Class-diagram, sequence-diagram, program |
Phase 3 product |
Common |
| 12 |
1/17 |
Validate and verify
|
Test |
Test-plan (including test-cases) |
|
Separate |
| 13 |
1/24 |
Final improvement and prepare for presentation
|
Test |
Test report, issue-list |
|
Separate |
| 14 |
1/31 |
Final presentation |
Finish |
Final report (presentation slides), program |
Tested and improved product |
Common |
Final Presentation
The final presentation will be held as follows:
- Date: January 31 (Wednesday)
- Place: std5
- Time: 9:50 - 12:30
Presentation format:
- Presentation: 15 minutes (please use the template below)
- Questions and Answers: 10 minutes
Schedule and presentation order will be announced later.
Materials
Introduction
Project Assignment
RFP (Request for Proposals): Available through the template project
Tools
Forms
Student Evaluation
- Presentation at each review (interim and final) 25%
- Software product (documents and software) 40%
- Final exam (individual interview) 25%
- Participation in class activities and attitude 10%
Evaluation criteria:
- Assessment of software product will be based on fulfillment of requirements (implemented functions and
precision), performance, creativity, and innovation.
- Contribution of each student will be checked in each review and development records.
- Form and content of final examination will be announced at the beginning of the course.