VBM616 - SOFTWARE ENG. LAB.
| Course Name | Code | Semester | Theory (hours/week) |
Application (hours/week) |
Credit | ECTS |
|---|---|---|---|---|---|---|
| SOFTWARE ENG. LAB. | VBM616 | Any Semester/Year | 1 | 0 | 2 | 3 |
| Prequisites | - | |||||
| Course language | Turkish | |||||
| Course type | Elective | |||||
| Mode of Delivery | Face-to-Face | |||||
| Learning and teaching strategies | Discussion Experiment | |||||
| Instructor (s) | Staff of Computer Engineering Dept. | |||||
| Course objective | To experiment the development of middle-size software systems by following basic software engineering practices. | |||||
| Learning outcomes |
| |||||
| Course Content | Engineering middle-size software applications from the scratch by using both management and development practices. Initial requirements of software projects and planning its development. Practicing requirements analysis, architectural design, and detailed design of software systems in accordance to a pre-defined software development life-cycle (based on Open Unified Process), and documenting the outputs of these activities in pre-defined formats (as recommended by IEEE). The students are required to show a working prototype of the software architecture by coding several critical requirements of the system at the end of the laboratory. The use of J2EE technologies is intended during the design and implementation of the software system. | |||||
| References | Sommerville I., Software Engineering, 9th ed., Addison-Wesley Professional, 2011. Pilone D. and Pitman N., UML 2.0 in a Nutshell, 2nd ed., O'Reilly Media, 2005. | |||||
Course outline weekly
| Weeks | Topics |
|---|---|
| Week 1 | OpenUP |
| Week 2 | OpenUP |
| Week 3 | OpenUP |
| Week 4 | Case Study |
| Week 5 | Case Study |
| Week 6 | Case Study Assessment |
| Week 7 | Cross Check of Case Studies |
| Week 8 | Project Assignment |
| Week 9 | Case study |
| Week 10 | Case study |
| Week 11 | Case Study Assessment |
| Week 12 | Project Review |
| Week 13 | Case Study |
| Week 14 | Project Review |
| Week 15 | Project Assessment |
| Week 16 | Project Assessment |
Assesment methods
| Course activities | Number | Percentage |
|---|---|---|
| Attendance | 0 | 0 |
| Laboratory | 0 | 0 |
| Application | 0 | 0 |
| Field activities | 0 | 0 |
| Specific practical training | 0 | 0 |
| Assignments | 5 | 50 |
| Presentation | 0 | 0 |
| Project | 1 | 50 |
| Seminar | 0 | 0 |
| Midterms | 0 | 0 |
| Final exam | 0 | 0 |
| Total | 100 | |
| Percentage of semester activities contributing grade succes | 0 | 100 |
| Percentage of final exam contributing grade succes | 0 | 0 |
| Total | 100 | |
WORKLOAD AND ECTS CALCULATION
| Activities | Number | Duration (hour) | Total Work Load |
|---|---|---|---|
| Course Duration (x14) | 0 | 0 | 0 |
| Laboratory | 14 | 2 | 28 |
| Application | 5 | 10 | 50 |
| Specific practical training | 0 | 0 | 0 |
| Field activities | 0 | 0 | 0 |
| Study Hours Out of Class (Preliminary work, reinforcement, ect) | 14 | 3 | 42 |
| Presentation / Seminar Preparation | 0 | 0 | 0 |
| Project | 1 | 60 | 60 |
| Homework assignment | 0 | 0 | 0 |
| Midterms (Study duration) | 0 | 0 | 0 |
| Final Exam (Study duration) | 0 | 0 | 0 |
| Total Workload | 34 | 75 | 180 |
Matrix Of The Course Learning Outcomes Versus Program Outcomes
| D.9. Key Learning Outcomes | Contrubition level* | ||||
|---|---|---|---|---|---|
| 1 | 2 | 3 | 4 | 5 | |
| 1. Has detailed knowledge about data and knowledge engineering (DKE). | X | ||||
| 2. Has a good understanding of common concepts such as abstraction, complexity, security, concurrency, software lifecycle and applies their expertise to the effective design, development and management of IS. | X | ||||
| 3. Understands the interaction of theory and practice and the links between them. | X | ||||
| 4. Has the ability to think at different levels of abstraction and detail; understands that an IS can be considered in different contexts, going beyond narrowly identifying implementation issues. | X | ||||
| 5. Solves any technical or scientific problem independently and presents the best possible solution; has the communication skills to clearly explain the completeness and assumptions of their solution. | X | ||||
| 6. Completes a project on a larger scale than an ordinary course project in order to acquire the skills necessary to work efficiently in a team. | X | ||||
| 7. Recognises that the field of DKE is rapidly evolving. Follows the latest developments, learns and develops skills throughout their career. | X | ||||
| 8. Recognises the social, legal, ethical and cultural issues related to DKE practice and conduct professional activities in accordance with these issues. | X | ||||
| 9. Can make oral presentations in English and Turkish to different audiences face-to-face, in writing or electronically. | X | ||||
| 10. Recognises that DKE has a wide range of applications and opportunities. | X | ||||
| 11. Is aware that DKE interacts with different fields, can communicate with experts from different fields and can learn necessary field knowledge from them. | X | ||||
| 12. Define a research problem and use scientific methods to solve it. | X | ||||
*1 Lowest, 2 Low, 3 Average, 4 High, 5 Highest