Skip to main content

Software Engineering Laboratory (6 cr)

Code: G-04138-3003

General information


Enrolment period
27.07.2015 - 06.09.2015
Registration for the implementation has ended.
Timing
01.08.2015 - 31.12.2015
Implementation has ended.
Credits
6 cr
Local portion
6 cr
Mode of delivery
Contact learning
Unit
ICT Engineering
Campus
TAMK Main Campus
Teaching languages
Finnish
Degree programmes
Degree Programme in ICT Engineering, students who began in 2013 or earlier
Teachers
Erkki Hietalahti
Tietotekniikka Virtuaalihenkilö
Person in charge
Erkki Hietalahti
Course
G-04138

Objectives (course unit)

The students deepen their knowledge on the methods, techniques and tools of software technology by doing laboratory works.

Content (course unit)

Methods for defining, designing, implementing, troubleshooting, testing and maintaining.

Prerequisites (course unit)

1. – 3. year mandatory courses in software technology

Exam schedules

There are no exams in this course.

Evaluation methods and criteria

Information in this totsu are preliminary becaou
Accepted completion is assessed grading scale of 1-5 (unsuccessful
performance rating is 0). Assessment is based on student groups produced
a description of documents. Each description provides rating, which is
the same for all students in the group in question. selostuk-of future
rating. So all the members of one working group will receive the same
grade of a particular job. The final grade of the student is weighted by
the amount of work up a rounded average of the arvosa-those that have
given his team the writing selos-tions.
The review criteria for evaluation include. the following: - The working
process and schedule management - The achievement of the objective of -
results - The clarity, comprehensibility, concentration on essentials,
logic, structure - Ability to give conclusive results (eg usefulness.)
And further conclusions - A description of the document layout, spelling
and potential graphical representations clarity

Teaching methods

Laboratory work on the software engineering field. To deepen the familiarization of software engineering methods and tools. For defining, designing, implementing, troubleshooting, testing and maintenance methods and ways of working.
The course is made of small-scale laboratory work-related software technology for these subjects. Topics are based, as a rule 1 - studied in the 3rd year courses, but also new issues may be involved. Jobs are typically in the programming work, study hard, work hard testing, etc., And their purpose is to deepen the things already learned, or access to key software engineering technologies.
Actual lectures on the course does not exist. If necessary, the labor theory can be presented & repeat 1. During the assembly time.
All participants must be present at the start of each work session. Otherwise, the requirement is the presence of Job level and job responsibilities the teacher says this.
This document does not describe any one job. These appear in the descriptions before starting work.

Learning materials

Work-related material will be published in most cases tabula virtual learning system before ao. The commencement of work. Job responsibilities the teacher tells her work place material. However, Tabulaan published in the general course material, for example. This implementation plan.

Student workload

Classroom education is 4 - 8 hours per week. Laboratory work must also make substantial investments in their own time outside of controlled education, for jobs to have enough time to make ready. The exercises are done in groups.
Course news to the students by e-mail. As a result, each participant is obliged to follow their e-mail. If you own the e-mail does not work, the student should contact the Computer Centre. All of the course briefing sent to the distribution list g-04138-3003@tamk.fi. This list is automatically generated Winha course registered and approved on the basis of the pupils.

Attending the given lectures is compulsory.

Content scheduling

The course consists exclusively laboratory work. Each laboratory typically takes 1-6 weeks depending on the scope; Exceptions are possible due to the different nature of work. Laboratory work to do to control the teacher in charge. Making work can be roughly divided into the following stages:
1) Making work-related advance preparation. This can include things already learned reread, work instructions, check out Mista, access to documents etc.
2) The actual work to begin on 1 assembly time. Work fac, be under supervision in most cases 1-6 weeks 4 - 8 hours per week (for detailed timing information can be found Tabulaan publish only kurs-sikalenterista (Excel file)). Weekly working and student-ded for 2 with 4 hours working scab-country; Note: The size of this time does not necessarily give guidance!. Guidance is given addressed to the course in a computer lab.
3) If during the control of ice time a group of students, it can be used to initiate a description of the document concluded. Explanation is completed on their own time, and it is returned to the set to work no later than the end date. The document must indicate its authors; each job task data describes the work to be written description of the document things tehdys-in. It is desirable that the narration is done in parallel interspersed with the conclusion of the work. Eg. The results achieved in connection with the conclusion of the work-to include a description of the document.
4) Job responsibilities assessed by the teacher returned to work reports. Regulation Selos-rating is given to all students of the producing group - that is, every member of the student group will receive the same rating given report. The student throughout the course ar-vosana is his team-weighted Workload works written by commentary in the book-words mean.
The requirements of each individual laboratory work is discussed separately below its working instructions, which will be published before the work 1. The assembly time. Similarly, work instructions mentioned in question. required job description issues.
The student group will do all of the course work. Only valid reason, the work schedule may be permitted deviation. In this case, a group of students should contact the teacher in charge of a new work schedule preparation.
If the work will remain in spite of everything to be done, they should do seu-Raavana-held in a similar course in question. within the framework of the course time-table. Thus, for example. Getting the course rating is delayed approx. One year. Note: The work can vary each year; The next year will make do mainly of the surplus work for the job.
Reviews may not be copied from others. Ts. a group of students is done every description of yourself. Copied description of the result in question. laboratory work and at the same time rejecting the entire course at runtime.
Job completion dates are absolute and shall not be accepted for slippage. In order to work is a time for the whole autumn term, so this should not be a problem.
Job themes tentatively related to the following topics:
• JavaScript work
• Web Programming and Application of the MVC model in
• Browser interfaces, the server will head operations, database
The course may come later new topics.

Further information

Literature: Material given during the course. Laboratory work and independent work Language of instruction: Finnish Contact person: Director of degree programme .

Assessment criteria - fail (0) (Not in use, Look at the Assessment criteria above)

Did not participate in classes and did the tasks assigned. There is no proven know-how.

Assessment criteria - satisfactory (1-2) (Not in use, Look at the Assessment criteria above)

Necessary course of its own software technical capabilities. The reports do not contain material deficiencies and are, as a rule returned on time. Can handle group work.

Assessment criteria - good (3-4) (Not in use, Look at the Assessment criteria above)

Able to apply treated courses dossiers and programming methods. Reports have been prepared in accordance with the instructions and largely restored in time. Some of the software technical matters of the course and knows how to use the tools associated with them. Is able to work in a group.

Assessment criteria - excellent (5) (Not in use, Look at the Assessment criteria above)

Able to independently and extensively apply the treated courses dossiers and programming methods. Able to prove the case load management course. Reports have been prepared in accordance with the instructions and returned on time. Manages programming methods and tools used, how to apply them and be able to analyze the results obtained. Is able to work in a group proactively.

Go back to top of page