Subject

Software Lifecycle Management

1.Course titleSoftware Lifecycle Management
2.CodeSI-Z-01
3.Study programme
4.Organizer of the study programme (unit, institute, department)Faculty of Computer Science and Engineering
5.Degree level (first, second, third cycle)Second cycle
6.Academic year / semester9 / Winter
7.Number of ECTS credits6
8.Teacher
9.Prerequisites for enrolling in the course—
10.Course objectives (competences)The purpose of the course is for students to acquire solid knowledge of software engineering in the development of large software development projects. Upon completion of the course, candidates will be able to: specify, model, implement and test software systems, define, plan and supervise a project for development and maintenance of complex software systems, working in a team, to collaborate with other teams when working on a joint project, They will be able to extract, analyze and document experiences from developing software and software intensive systems, to rule the general principles and techniques for controlling the quality of the software system as security, security, confidentiality characteristic of different types of software systems.
11.Course contentLife cycle of software, methodologies and techniques. Agile software development methods. Requirements Management. Methods for systemic and detailed design. Planning and managing the software development process. Managing software projects, resource management, risk control. Quality control through audits and testing. Delivery Strategies. Managing configurations and changes. Maintaining software, delivery of IT servants and customer relationships. Specifics in the development of web -based software and software for distributed and cloud systems. Service software oriented systems. Software for mobile devices and built -in systems. Software as a service. Economic aspects of software development. Software management software tools.
12.Learning methodsLectures supported by slide presentations, interactive lectures, practical classes (using equipment and software packages), teamwork, case studies, guest lecturers, independent preparation and defence of a project assignment and seminar paper, and learning in an electronic environment (forums and consultations).
13.Total available time6 ECTS x 30 hours = 180 hours
14.Distribution of the available time60 + 0 + 45 + 45 + 30 = 180 hours
15.Forms of teaching activities
15.1.Lectures – theoretical teaching60 hours
15.2.Exercises (laboratory, auditory), seminars, team work0 hours
16.Other forms of activities
16.1.Project assignments45 hours
16.2.Individual assignments45 hours
16.3.Home study30 hours
17.Grading
17.1.Tests35 points
17.2.Seminar paper / project (presentation: written and oral)45 points
17.3.Activity and participation0 points
17.4.Final exam0 points
18.Grading criteria (points / grade)
up to 50 points5 (five) (F)
from 51 to 60 points6 (six) (E)
from 61 to 70 points7 (seven) (D)
from 71 to 80 points8 (eight) (C)
from 81 to 90 points9 (nine) (B)
from 91 to 100 points10 (ten) (A)
19.Requirements for signature and taking the final examcompleted activities
20.Language of instructionMacedonian and English
21.Method of monitoring teaching qualityinternal evaluation and survey mechanism
22.Literature
22.1.Required literature
1. Ian Sommerville | Software Engineering | Addison Wesley | 2010
2. Roger S. Pressman | Software Engineering: A Practitioner`s Approach 7 th Ed. | McGraw - Hill Science | 2009
3. Joachim Rossberg | Beginning Application Lifecycle Management | Apress | 2014
22.2.Additional literature
No. Author Title Publisher Year