MdH/IDt1March 11, 2003 Software Engineering Lesson 8 Project preparation Andreas Sjögren

MdH/IDt2March 11, 2003 Software Engineering Lesson overview  Project’s actors  Responsibilities of the actors  Meetings  Artifacts  Remaining parts (for the lesson/assignment part)

MdH/IDt3March 11, 2003 Software Engineering Project actors  Customer(s)  Steering group  Project group  Project manager

MdH/IDt4March 11, 2003 Software Engineering Customer’s responsibilities Customer responsible for:  Have ideas of the product  Have time to discuss the ideas  Give feedback to the group (on issues of interest to the customer) But not responsible for:  Initiate meetings  Limit the project  Always be available

MdH/IDt5March 11, 2003 Software Engineering Steering group’s responsibilities Steering group responsible for:  Deal with serious problems in the project group  Discuss the progress of the project  Give feedback on artifacts  Approve (and grade) the project work But not responsible for:  Identify problems in the project group  Make the project approvable  Prevent bad decisions

MdH/IDt6March 11, 2003 Software Engineering Project manager’s responsibilities Project manager responsible for:  Lead the work of the project group  Keep an eye on the communication within the group  Be up to date But not responsible for:  Do all the work  Always remind people about there responsibilities

MdH/IDt7March 11, 2003 Software Engineering Project group’s responsibilities Project group responsible for:  Plan and carry out the project  Restrict the problem  Identify problems within the group But not responsible for:  ?

MdH/IDt8March 11, 2003 Software Engineering Weekly meetings  Meeting, discussions between the group and the steering group  Short presentation, emphasize on the most important for next week (new student each time)  Feedback on the weekly project report from previous week, and other documents

MdH/IDt9March 11, 2003 Software Engineering Weekly meetings  Feedback on documents, only on major revisions  First meeting Wed. 2 Apr , room v275  Weekly report (for previous week) delivered to the steering group every Monday, before  Schedule for meetings in lecture notes (and on project page)

MdH/IDt10March 11, 2003 Software Engineering Project Description  Template (on cvs: project/doc) –Organization, deliverables, reporting working hours, project plan  Hints: –Language –Intended reader –Divide the work –Internal reviewing within the group –More hints and examples in the template

MdH/IDt11March 11, 2003 Software Engineering Group web page  Members of the group  News section  Planned activities and divided responsibilities  Documents for download  Every thing else the group wants to put there

MdH/IDt12March 11, 2003 Software Engineering CVS  All files should be put under cvs  Repository: /export/users/se/gr i (where i is the group number)  Group password will be mailed to the group manager  Short manual available from project resources page

MdH/IDt13March 11, 2003 Software Engineering Group assignment 1.Gather the group 2.Select a project manager 3.Write first version of the project description 4.Make a project web page 5.Configuration management

MdH/IDt14March 11, 2003 Software Engineering Assignment deadline  Deadline  Feedback on the first weekly meeting (or )  If you are approved on the assignment, is not sure that the project description not have to be revised before that is finally approved  Assignment specification at the lab page

MdH/IDt15March 11, 2003 Software Engineering Remaining parts (for lessons)  Solve the group assignment  Finalize your assignments!