| Statuss(Aktīvs) | Izdruka | Arhīvs(0) | Studiju plāns Vecais plāns | Kursu katalogs | Vēsture |
| Course title | Software Engineering Methods I |
| Course code | DatZ2057 |
| 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 introduce students to the world-known and applied software engineering best practices taking into account international software engineering standards, existing legislative framework and the specifics of Latvia, as well as practical experience accumulated in Latvian IT companies. Aspects of sustainability in the software lifecycle are discussed. Basic processes of software development, and the relationship between the activities to be undertaken are analysed. Students are involved in team work implementing independently assigned tasks. | |
| 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 software engineering best practices - (evaluation of practical work); • 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. History of software engineering development 1 (L)
2. Software engineering tasks, place in program development 1 (L) 3. Technical writing style 1 (L) 2(P) 4. Types of life cycle models. Waterfall. 2 (L) 5. Concept development 1 (L) 4(P) 6. Documentation process 1 (L) 7. Specifying software requirements. 2 (L) 6 (P) 8. Types of life cycle models. Agile 1 (L) 9. Software engineering standards 1 (L) 10. Information technology regulatory documents (laws) 1 (L) 11. User story 1 (L) 12. Configuration management (versioning) 1 (L) 1(P) 13. Reviews 1 (L) 2(P) 14. Change management 1 (L) 1(P) |
|
| 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 test 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 2022.09.08.]
2.ISO/IEC 12207. 2008. Systems and software engineering. Software life cycle processes (LVS Standartu lasītava) 3.ISO/IEC 26514:2022. Systems and software engineering - Design and development of information for users, 2022. (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 | |