- Elicitation techniques for gathering user requirements
- Approaches for modelling customer requirements (modeling techniques and processes)
- Transformation of customer requirements to developer requirements (functional / non-functional requirements)
- Negotiation and priorization of requirements
- Variability management for requirements in a product line context
- Scoping of requirements
Software-Engineering 1 (M, 10.0 LP)
|Module Number||Module Name||CP (Effort)|
|INF-30-06-M-2||Software-Engineering 1||10.0 CP (300 h)|
|CP, Effort||10.0 CP = 300 h|
|Position of the semester||1 Sem. in WiSe|
|Level|| Bachelor (Fundamentals)|
|Language||[DE/EN] German or English as required|
|Area of study||[INF-SE] Software-Engineering|
|Reference course of study||[INF-82.B16-SG] B.Sc. Socioinformatics|
|Type/SWS||Course Number||Title||Choice in |
|SL||SL is |
required for exa.
|P||42 h||78 h||
|P||56 h||124 h||
- About [INF-31-55-K-6]: Title: "Requirements Engineering"; Presence-Time: 42 h; Self-Study: 78 h
- About [INF-31-55-K-6]:
The study achievement "[U-Schein] proof of successful participation in the exercise classes (ungraded)" must be obtained.
- It is a prerequisite for the examination for PL1.
- About [INF-02-16-K-2]: Title: "Project Management"; Presence-Time: 56 h; Self-Study: 124 h
- About [INF-02-16-K-2]: The study achievement "[U-Schein] proof of successful participation in the exercise classes (ungraded)" must be obtained.
Examination achievement PL1
- Form of examination: written or oral examination
- Examination Frequency: each winter semester
- Examination number: 63155 ("Requirements Engineering")
Evaluation of grades
The grade of the module examination is also the module grade.
- Basics of project management in software projects
Organization and planning
- Organization of the project environment and forms of organization: Line organization, matrix organization
- Definition of project objectives and estimation: procedure, surcharges, experience, min/max estimation
- Rough/fine planning, milestones, activities, dates, planning of funds
- Specifications, requirements, specification, design, development, integration, test
- Team organization through project phases, team building, roles in the team
- Controlling, estimation of remaining expenditure and progress control
- Selection of a procedural model for a project: waterfall, RUP, spiral model, incremental, prototyping
- Connection between process models and project management
- Means of work: meetings, protocols, agreements, lists of open points, project diary, project handbook
- Software support for project management
- Software management, libraries, repositories
- Quality concept and quality characteristics
- Constructive and analytical quality assurance
- Organizational measures, roles, reporting
- Risk management
- Management styles
- Change management
- Handling of supplies
- Information management in the project
- Relationship between IT system decomposition and team structure
- General Contractors
Competencies / intended learning achievements
After successfully completing the module, students will be able to
- explain methods for the engineer-like execution of the requirement process,
- explain suitable methods for capturing requirements by means of examples,
- justify appropriate techniques and procedures for modeling and specifying requirements
- derive techniques of requirements management,
- justify special features of the requirements specification in the context of product line development.
Furthermore, the students are able to orient themselves in a project and
- can work constructively in a project,
- have the theoretical knowledge to exercise project management,
- know the principles, methods and tools for the engineering development of "large" software systems
- know all important phases of software development and automatic tools,
- can analyze software development processes,
- can design large software systems according to engineering methods.
- Cockburn. Writing Effective Use Cases, Addison-Wesley, 2001.
- S. Robertson, J. Robertson, Mastering the Requirements Process, Addison-Wesley, 2002.
- S. Lauesen: Software Requirements, Addison-Wesley, 2002.
- M. Burghardt, Einführung in Projektmanagement: Definition, Planung, Kontrolle und Abschluss , 6. Aufl. Erlangen: Publicis Publishing, 2013.
- P. M. Institute, A Guide to the Project Management Body of Knowledge , 5 Rev ed. Newtown Square, Pennsylvania: Project Management Institute, 2013.
- Walter Ruf, Thomas Fittkau: Ganzheitliches IT-Projektmanagement. Wissen, Praxis, Anwendungen. Oldenbourg Verlag 2010.
Requirements for attendance of the module (informal)None
- Notice: Some Courses have informal requirements for attendance:
Requirements for attendance of the module (formal)None
References to Module / Module Number [INF-30-06-M-2]
|Course of Study||Section||Choice/Obligation|
|[INF-82.B16-SG] B.Sc. Socioinformatics||[Compulsory Modules] Computer Science||[P] Compulsory|