Management of Information and Software Systems Projects

Basic Information

Offered by: Institute of Informatics and Software Engineering
Type of Study: Graduate in Software Engineering
Degree course: Software Engineering, Information systems
Duration: 12 weeks
Semester: Autumn
Hours per week (lectures - labs): 2 - 2
Credits: 6
Reader: Mária Bieliková
Students should have knowledge of the aspects of software development at a depth equal to that presented in the course Principles of Software Engineering.
Prior experience with a larger software development would be helpful but it is not required.

to Homepage to Teaching to the Top


Management of information and software systems projects encompasses the knowledge, techniques, and tools necessary to manage the development of information and software systems products. The purpose of this course is to introduce and discuss topics related to software project management such as management of team developing information and software systems, planning for development, risk management, management of change. Within this context, software quality is discussed together with software metrics and standards.

Software process maturity and alternative life-cycle models are explained (SEI capability maturity model).

This course has been designed so that, upon its completion, the student will understand requirements for the content of a project management plan and will understand the role of the manager in each phase of the software development life cycle.

Keywords: software engineering; information system; software system; software system development life cycle; team development; software configuration management; project plan; software metric.

to Homepage to Teaching to the Top


  • Introduction to management in software engineering: software system life cycle, quality, productivity and risk reduction within the context of effective software project management. The role of the software project manager.
  • Planning the software project. Business planning. Technical Planning: types of plans (documents), plan documentation methods (work breakdown structures, PERT and CPM, Gantt charts).
  • Software development resource estimation: cost, personnel, physical resources, schedule, size of the product, complexity of the product. Productivity measures. Effort prediction (COCOMO model).
  • Risk management and control. Prototyping in relation to risk management.
  • Software measurement: obstacles to software measurement, software measurement methods, process models and metrics.
  • Design evaluation (calling structure, ripple analysis, information flow, cluster analysis)
  • Quality assessment: quality standards, quality plans and quality metrics. Inspection in relation to quality improvement. Quality assurance and its role in project management. Standards related to software project management.
  • Methods of project team organization: chief programmer, surgical, egoless, democratic and hierarchical.
  • Configuration management and its role in project management. Mantaining product integrity. Version control.
  • Change management. Types of change. The principles of change control. The change life cycle. Configuration status accounting.
  • Alternative life-cycle models in context of project management.
  • Software process improvement: SEI capability maturity model.
  • Tools for software project management. The role of knowledge in project management support.

to Homepage to Teaching to the Top


Journey of the Software Professional. Prentice Hall. 1997.
Inroads to Software Quality. Prentice Hall. 1997
Wysocki, R.K. and DeMichiell, R.L.
Managing Information Across the Enterprise. John Wiley & Sons. 1997.
Pressman, R.S.
Software Engineering: A Practicioner's approach. McGraw-Hill. 1992.
Shepperd, M.
Foundations of Software Measurement. Prentice Hall. 1995.
Whitgift, D.
Methods and Tools for Software Configuration Management. Willey. 1991.
Shere, K.D.
Software Engineering and Management. Prentice Hall. 1988.
Sommerville, I.
Software Engineering. Addison-Wesley. 5th edition 1996.
Tietze, P.
Structured Analysis: The introduction to project management. Grada. 1992. (in czech)

to Homepage to Teaching to the Top

Conditions to obtain a grade

  1. "pass" mark for labs which requires:
    • active participation in lectures
    • elaboration of essay in given area
  2. at least 56% of marks. Marks are assigned as follows:
    • assignments during semester (max. 55 marks)
    • final exam (max. 45 marks)

to Homepage to Teaching to the Top

Last updated:
Mária Bieliková bielik [zavináč] fiit-dot-stuba-dot-sk
Design © 2oo1 KoXo