Software requirements analysis

Software requirements analysis

1.

Subject title

Software requirements analysis

Анализа на софтверските барања

2.

Code

F23L2S002

3.

Study program

Примена на информациски технологии, Компјутерски науки, Компјутерско инженерство, Интернет, мрежи и безбедност, Информатичка едукација, Примена на информациски технологии, Компјутерски науки, Компјутерско инженерство, Интернет, мрежи и безбедност, Софтверско инженерство и информациски системи, Software engineering and information systems, Стручни студии за програмирање, Стручни студии за програмирање, Софтверско инженерство и информациски системи, Software engineering and information systems, IT management,

4.

Organizer of the study program (unit, institute, department, division)

Faculty of Information Sciences and Computer Engineering

5.

Study cycle (first, second, third)

Прв циклус

6.

Academic year / semester

2 / Летен

7. Number of ECTS credits

6.0

8.

Instructor

ворн. проф. д-р Ефтим Здравевски проф. д-р Георгина Мирчева проф. д-р Љупчо Антовски

9.

Prerequisites for enrollment

Објектно ориентирана анализа и дизајн или Објектно ориентирано програмирање

10.

Subject goals and competencies:


After finishing this course, the student is expected to understands and have deepened knowledge in application of knowledge extraction from his client, to understands techniques for documenting software and business needs, to understands and have deepened knowledge in application of techniques for change management in software and business requirements.

11.

Subject content:


(1) Requirements definition (for example, product, project, restrictions, system boundaries, both external and internal) (1) Requirements engineering process (1) Layers/levels of requirements (for example, needs, goals, user requirements, system requirements and software requirements) (1) Characteristics of requirements (for example, testing, unambiguous, consistent, precise, traceable and priority) (1) Analysis of quality (nonfunctional) requirements (for example, reliability, security, usability and performance) (1) Software requirements in the context of system engineering (1) Evolution of requirements, tracing, priority, compromise analysis, risk analysis and influence analysis (1) Requirements management (for example, consistency management, release planning and reusability), Interaction between requirements and architecture (1) Requirements elicitation, sources of extraction (for example, stakeholders, domain experts, and operational and organizational environments), elicitation techniques (for example, interviews, questionnaires/surveys, prototypes, use cases, observation and participation techniques) (1) Requirements specification and documentation, requirements documentation basics (for example, types, purpose, structure, quality, attributes and standards) (1) Techniques for software requirement specification (for example, planning requirements documentation, decision tables, user stories and behaviour specification) (1) Requirements validation, desk-checks and inspections, prototyping for requirements verification (1) Design of acceptance test, product quality attributes confirmation, requirements interaction analysis (for example, functional interaction), Formal requirements analysis

12.

Learning methods:


Предавања поддржани со презентации преку слајдови, интерактивни предавања, вежби (користење на опрема и софтверски пакети), тимска работа, пример случаи, поканети гости предавачи, самостојна изработка и одбрана на проектна задача и семинарска работа, учење во електронско опкружување (форуми, консултации).

13.

Total available time fund

6.0 ECTS x 30 hours = 180 hours

14.

Time distribution

30 + 45 + 15 + 15 + 75 = 180 hours

15.

Forms of teaching activities

15.1.

Lectures - theoretical teaching

30 hours

15.2.

Exercises (laboratory, classroom), seminars, team work

45 hours

16.

Other forms of activities

16.1.

Project tasks

15 hours

16.2.

Independent tasks

15 hours

16.3.

Homework

75 hours

17.

Grading method

17.1.

Tests

0 points

17.2.

Seminar work / project (presentation: written and oral)

15 points

17.3.

Activities and learning

30 points

17.4.

Final exam

30 points

18.

Grading criteria (points / grade)

up to 50 points

5 (five) (F)

from 51 to 60 points

6 (six) (E)

from 61 to 70 points

7 (seven) (D)

from 71 to 80 points

8 (eight) (C)

from 81 to 90 points

9 (nine) (B)

from 91 to 100 points

10 (ten) (A)

19.

Condition for signature and taking final exam

Редовно посетување настава (до 3 отсуства), навремно доставување на сите домашни задачи, семинарски работи, дискусии на форум и проект

20.

Language of instruction

македонски и англиски

21.

Quality assurance method

механизам на интерна евалуација и анкети

22.

Literature

22.1.

Mandatory literature

No.

Author

Title

Publisher

Year

2993

Karl E. Wiegers, Joy Beatty

Software Requirements

Microsoft Press

2013

2994

Ian K. Bray

An Introduction to Requirements Engineering

Addison Wesley

2002

2995

Ian F. Alexander, Richard Stevens

Writing better requirements

Addison-Wesley

2002

22.2.

Additional literature

No.

Author

Title

Publisher

Year