| Statuss(Aktīvs) | Izdruka | Arhīvs(0) | Studiju plāns Vecais plāns | Kursu katalogs | Vēsture |
| Course title | Software Engineering Methods II |
| Course code | DatZ2058 |
| Credit points (ECTS) | 3 |
| Total Hours in Course | 81 |
| Number of hours for lectures | 16 |
| Number of hours for seminars and practical classes | 16 |
| Independent study hours | 49 |
| Date of course confirmation | 06/09/2022 |
| Responsible Unit | Institute of Computer Systems and Data Science |
| Course developers | |
| Dr. sc. comp., prof. (Emeritus) Rudīte Čevere |
|
| There is no prerequisite knowledge required for this course | |
| Course abstract | |
| The aim of the study course is to learn the final processes of the software development life cycle and the standards that regulate them, to analyze the tasks of quality management and quality assurance. Software system development and maintenance management issues are discussed in detail. Insight into the development and certification of companies' quality systems (standard ISO 9001, ISO 20000, ITIL, CMMI) is given. Sustainability aspects of the software life cycle are considered. | |
| Learning outcomes and their assessment | |
| As a result of mastering the study course, students
• know about process approach into software development projects with different life cycle models, and become acquainted with quality assurance tasks of the supporting processes (accordingly to standards J-STD-016-1995 and IEEE Std 12207) - (evaluation of practical work, final test); • have skills to organize interchange of mutual information between the team members of software development project, and to develop the project internal documentation - (evaluation of practical work); • acquire competence working in teams or independently, to use defined forms of documentation and to organize activities of information interchange, as well as assure the others and argue their own point of view - (evaluation of practical work). |
|
| Course Content(Calendar) | |
| 1. Preparation of requirements specification for design 1 (L) 2 (P)
2. Software design development 2 (L) 6 (P) 3. Software user documentation 1 (L) 4. Software user documentation Agile 1 (L) 4 (P) 5. Coding, coding standards 1 (L) 6. Software source code writing style1 (L) 2 (P) 7. Software testing 1 (L) 8. Software testing documentation 1 (L) 9. Software delivery 1 (L) 10. Software maintenance 1 (L) 11. Project management 2 (L) 2 (P) 12. Risk management 1 (L) 13. Sustainability of information technology 1 (L) 14. Course overview 1 (L) |
|
| Requirements for awarding credit points | |
| It is mandatory to complete and submit all independent work and obtain a successful evaluation of each work. | |
| Description of the organization and tasks of students’ independent work | |
| Students must independently learn additional information about the topics covered in the lectures. Practical work tasks are analyzed during practical classes, students must independently prepare the documents required in practical work tasks. The tasks of the independent work will be related to the software engineering methods acquired in the lectures. | |
| Criteria for Evaluating Learning Outcomes | |
| During the semester, a maximum of 80 points can be obtained for regular work, which are determined as follows: Full-time participation in the development of practical work = 32; Timely completion of practical tasks (for the first 4 works) = 4; Attendance of lectures =16; Total evaluation of practical works = 28; At the end of the semester, the points are added up and they can determine the exam mark. If the student wants to improve this assessment, additional theoretical questions must be answered. | |
| Compulsory reading | |
| 1. IEEE Computer Society SWEBOK Guide to the Software Engineering Body of Knowledge/ Project Management Institute. 2013. Fifth Version. [tiešsaiste]. Pieejams: http://www.swebok.org/htmlformat.html [Skatīts 08.09.2022.]
2. ISO/IEC 12207. Systems and software engineering. Software life cycle processes (LVS Standartu lasītava) 3. ISO/IEC 26514:2008. Systems and software engineering — Requirements for designers and developers of user documentation. 2008. (LVS Standartu lasītava) |
|
| Further reading | |
| Pressman R.S. Software Engineering. A Practitioner's Approach. European Adaptation. 7th edition. New York: McGraw-Hill Higher Education, 2010. | |
| Notes | |
| For students of ITF professional higher education bachelor study programs Information Technologies for Sustainable Development and ITF academic bachelor study programs Computer Management and Computer Science. | |