Team Project

• Basic Information
• Objective
• Contents
• Documentation
• Readings
• Grade Conditions

Basic Information

Offered by: Institute of Informatics and Software Engineering

Type of Study: Graduate in Software Engineering

Degree Course: Software Engineering

Duration: 24 weeks (2 semesters)

Semester: Autumn, Spring

Hours per week (lectures - labs): 1 - 3, 1 - 3

Credits: 6+6

Guarantee: Mária Bieliková

Prerequisites:

programming in arbitrary programming language;
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

Objective

The purpose of this course is to exercise software development in teams. Stress is put on an effective collaboration and communication between team members together with exercising several roles during a software development (e.g. software analyst, designer, programmer, project manager, documentation manager, quality assurance manager).

Keywords: software engineering, team, project management.

to Homepage

to Teaching

to the Top

Contents

Autumn:

1. An initiation of creation of teams, information about various problems to be solved during the course.
2. Elaboration of a bid for a particular problem. Each team should prepare two bids for two different problems.
3. Evaluation of bids and asignment of problem to the teams.
4. Problem analysis.
5. Requirements specification and architectural design.
6. Requirements specification and architectural design.
7. Delivering of requirements specification document.
8. Peer review of requirements specification.
9. Processing of found shortcomings.
10. Design of a prototype (selected parts, e.g. user interface).
11. Implementation of a prototype.
12. Delivering of a prototype together with documentation.
13. Peer review of a prototype.

Spring:

1. Evaluation of the results achieved in autumn semester together with processing of found shrotcomings.
2. Detailed design of a developed software system, plan of an integration, design of test data.
3. Detailed design of a developed software system, plan of an integration, design of test data.
4. Implementation and test of the modules.
5. Implementation and test of the modules.
6. Implementation and test of the modules, gradual integration.
7. Implementation and test of the modules, gradual integration.
8. Implementation and test of the modules, gradual integration.
9. Product integration and test.
10. Product integration and test.
11. Completion of a documentation.
12. Delivering of software system (programs and documentation).
13. Presentation and defence

to Homepage

to Teaching

to the Top

Documentation

Autumn:

• Requirements specification document
1. Introduction
2. Plan of the project (autumn)
3. Context of the system
4. Functional requirements specification
5. Data requirements specification
6. Behavioral requirements specification
7. Other requirements and constraints
• Review of requirements specification
• Prototype documentation (user manual)
• Review of prototype

Spring:

• Design, implementation and testing document
1. Introduction
2. Plan of the project (spring)
3. System architecture
4. Physical data model
5. Constraints, changes to a specification, priorities
6. Design of testing
7. Implementation language and environment
8. Coding standards
9. Description of implementation of modules
10. Testing
11. What we have learnt
12. User manual
• Review of design, implementation and testing document
• Review of a product
• Acceptance document

to Homepage

to Teaching

to the Top

Readings

Bieliková, M.

How to successfuly solve a project. Slovak University of Technology, 2000. (in Slovak)

Humprey, W.S.

Introduction to the Team Software Process. Addison-Wesley. 2000.

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 project work which requires:
   • active participation in team meetings
   • elaboration of projects documentation with defined structure and product with proper functionality demonstration (the last date for documentation and prototypes is lab in last week of the semester)
2. at least 56% of marks

to Homepage

to Teaching

to the Top