|
Volumn , Issue , 2008, Pages 354-
|
Four roles of instructor in software engineering projects
|
Author keywords
Role of instructor; Software engineering project
|
Indexed keywords
ARSENIC;
COLLEGE BUILDINGS;
COMPUTER SOFTWARE;
COMPUTERS;
CUSTOMER SATISFACTION;
EDUCATION COMPUTING;
INNOVATION;
MANAGERS;
NEURAL NETWORKS;
RISK ANALYSIS;
RISK MANAGEMENT;
SALES;
SOFTWARE ARCHITECTURE;
SOFTWARE ENGINEERING;
SPONTANEOUS EMISSION;
STUDENTS;
TECHNOLOGY;
TECHNOLOGY TRANSFER;
ACADEMIC PROGRAMS;
ARCHITECTURAL CHANGES;
ARCHITECTURAL DECISIONS;
DOMAIN KNOWLEDGES;
INDUSTRIAL PARTNERS;
INDUSTRIAL SETTINGS;
INDUSTRIAL SOFTWARE DEVELOPMENTS;
IT IMPACTS;
KEY FEATURES;
MODERN TOOLS;
ON TIMES;
ONE HANDS;
POTENTIAL CONFLICTS;
REAL WORLDS;
REQUIREMENTS ELICITATIONS;
REQUIREMENTS SPECIFICATIONS;
ROLE OF INSTRUCTOR;
SOFT SKILLS;
SOFTWARE ENGINEERING COURSES;
SOFTWARE ENGINEERING PROJECT;
SOFTWARE ENGINEERING PROJECTS;
SOFTWARE PROJECTS;
STUDENT TEAMS;
TEAM MEMBERS;
THREE COMPONENTS;
WRITTEN DESCRIPTIONS;
TEACHING;
|
EID: 57349155098
PISSN: None
EISSN: None
Source Type: Conference Proceeding
DOI: 10.1145/1384271.1384396 Document Type: Conference Paper |
Times cited : (4)
|
References (0)
|