t-76.4115 software development project i customer info 15.9.2009 jari vanhanen...
TRANSCRIPT
T-76.4115 Software Development Project I
Customer Info
15.9.2009
Jari VanhanenOhjelmistoliiketoiminnan ja –tuotannon laboratorio
Software Business and Engineering Institute (SoberIT)
Agenda
16:15 – 17:00 Info for customers
17:00 – 17:05 Break
17:10 – 19:05 Topic presentations
19:05 – 19:45 Free discussion between customers and students
Roles
Customer organization provides the problem/system requirements helps with technical issues takes the responsibility of the system after the project
Project group 3 software engineering experts
project manager, QA manager, architect 60% of SE experts have already done the project in developer role
4-6 developers develops the software
Mentor course personnel ensures the fulfillment of the educational goals
helps with working methods
Educational Goal
To provide a context where the students can try in practice common SE methods and tools that have been taught in theory on other courses.
Allow the students spend enough effort for the educational aspects
of the project.
Support for the Project Groups from the Course Personnel Process framework Infrastructure
some hardware & software
Mentoring some participation helping with the work methods evaluation and feedback
Experience exchange sessions
Software Process – Framework
Enforces certain work practices and documents but allows lots of freedom (and responsibility) for customization
Purpose a basis for the groups to plan their work methods
a group has not worked together previously working in physically and temporarily distributed setting
emphasize educational goals project results are not the only thing that matters
“standardizing” projects more visibility easier control and evaluation
lower risks of total failure rather than slightly more results certain risks realize every year in a few projects 15 successful projects vs. 13 very successful and 2 failed
Software Process – Project Control Variables
Effort fixed 5-8 credits, 7-9 persons 27h/credit/person = 120-200h per person
project preparation (~15h) project work educational exercises
Calendar time fixed project schedule with major control points such as iteration demos
Quality ”fixed” high quality recommended, but customer may explicitly state if certain quality
aspects are not important (e.g. in prototype projects)
Scope flexible adjusted depending on the groups’ skills and knowledge of the problem domain
design; 8
documenting; 17
infrastructure; 4
meetings; 17programming; 32
proj. management; 8
studying; 8
testing; 6
Software Process - Iterations
Software Process - Iteration Planning
Group and customer plan each iteration’s goals and deliverables goals are higher level ideas of what is expected from the iteration deliverables include software units and documents to be created/updated
Iteration planning meeting customer selects and prioritizes iteration’s content based on
business importance group’s effort allocation for the iteration group’s rough effort estimates for implementing sw units group’s estimates about architectural impact
Group concretizes goals and deliverables into required tasks re-planning, if task effort estimates and allocated resources differ largely
Software Process – Iteration Demo
Arranged in the end of each iteration Tu-We 20.-21.10., 8.-9.12., 23.-24.2.
exact times (8:00-19:00) published in early October preferences to teacher immediately
at SoberIT (Innopoli 2, 4th floor, Tekniikantie 14)
Participants all project stakeholders, teacher, (consultants from Accenture)
Group presents project status (10-15 min) iteration’s results including sw demo (20-25 min)
Customer evaluates the work performed prepare in advance! private discussion about the given points with the mentor after the demo give comments about your evaluation to the group
Tip! Arrange the next iteration planning meeting right after the iteration demo.
Software Process – Controlling the Projects
Arrange regular meetings especially early in the project
Demand some regular, low overhead reporting Give concrete feedback
Software Process – Project Management
Software Process – Requirements Engineering
Software Process – Design and Implementation
Software Process – Quality Assurance
Software Process – Required Documentation
Project plan including description of work practices and QA plan
Requirements document Technical specification* User’s manual*
QA reports Progress reports (a slide set for the iteration demos)
Final report
Course provides some document templates their use is mandatory, but irrelevant topics can be omitted
*the course sets no requirements on the content or format of these two documents
Infrastructure
Hardware several computer classes at TKK
Software Microsoft MSDN AA
licenses for students’ own computers Magic Draw Personal Edition UML tool
licenses for students’ own computers TKK wiki, CVS, subversion, …
Customer must provide other necessary hardware/software: e.g. servers, phones for testing, bug tracking tool, …
Evaluation – General
Customer evaluates intermediate and final results, and slightly also working methods mentor ensures the objectivity of the evaluations
realistic expectations
Mentor evaluates working methods
Group members evaluate personal contribution of the other group members
Evaluation – Iterations (Customer)
Evaluation – Project’s Results (customer)
Compare to the original/updated project goals
Customer Satisfaction (2004-05)
Project Topics – Legal Issues
Intellectual property rights (IPR) open source, or customer gets IPRs
Non-disclosure agreement (NDA) must have been mentioned in the
topic proposal
Contracts prepared by TKK lawyers
TKK <-> companies TKK <-> students
Public documentation except code and technical specs if NDA required customer must
review documents before publication
Participation fee external: 3000e + VAT TKK: 1500e TKK/T-dep: 0e invoices sent in November
http://www.soberit.hut.fi/T-76.4115/09-10/instructions/contracts/TKK-yritys.pdf
Send two signed originals to Jari Vanhanen, PL 9210, 02015 TKK(DL mid October)
Project Topics – Selection Process
Students have formed 15 groups 3 SE experts + max. 3 developers teacher adds more developers 18.9.
A group contacts 2-4 customers
Groups appreciate customer’s commitment to the project customer’s domain understanding customer’s appreciation towards the
educational goals provided infrastructure provided technical guidance realistic description of the expected
skills from the group
Customer can choose any of the interested groups
…if they are still available
If you get a group email to Jari and he will remove the
topic from the list
If you don’t get any serious contacts by tomorrow
e-mail to Jari and he will highlight your topic on the list
Topic Presentations
Every 5 minutes if the presentation lasts < 5 minutes you can answer 1-2 short questions longer discussions after 19:00
Next presenter to the stage while the previous one answers questions
Topics