SaveUML
Project Description
Version:
1.0
Date: 2007-11-18
SaveUML
Project Description
Version 1.0
Page 1
Doc. No.:
SaveUML
Project Description
Version:
1.0
Date: 2007-11-18
Revision History
Date
Version
Description
Author
2007-11-07
0.01
Initial Draft
RD, AP
2007-11-11
0.02
Updated activity plan, added new member
to project.
AP
2007-11-12
0.03
Minor to large changes in multiple sections.
AP
2007-11-14
0.04
AP
2007-11-14
0.05
Entered roles for ME and added role to RD.
Minor rephrasing.
Minor spelling mistakes
2007-11-15
0.06
AP
2007-11-16
0.07
2007-11-18
1.0
Changes according to suggestions from
Rikard Land.
Added
configuration
management
information and Financial Plan.
Normalized version numbers. Final polish.
ME
AP
AP
Page 2
SaveUML
Project Description
Version:
1.0
Date: 2007-11-18
Table of Contents
1. Introduction ........................................................................................................................................................ 4
1.1 Purpose of this document ......................................................................................................................... 4
1.2 Intended Audience ................................................................................................................................... 4
1.3 Scope ........................................................................................................................................................ 4
1.4 Definitions and acronyms ........................................................................................................................ 4
1.4.1 Definitions .................................................................................................................................... 4
1.4.2 Acronyms and abbreviations ........................................................................................................ 4
1.5 References ................................................................................................................................................ 4
2. Organization ....................................................................................................................................................... 4
2.1 Project management ................................................................................................................................. 5
2.2 Project group ............................................................................................................................................ 5
2.3 Steering group .......................................................................................................................................... 5
2.4 Customer .................................................................................................................................................. 5
2.5 Others ....................................................................................................................................................... 5
3. Assumptions and constraints .............................................................................................................................. 5
3.1 Technological ........................................................................................................................................... 5
3.2 Environmental .......................................................................................................................................... 5
3.3 Interpersonal ............................................................................................................................................ 5
3.4 Work distribution ..................................................................................................................................... 5
3.5 Casual relationships ................................................................................................................................. 5
3.6 Time ......................................................................................................................................................... 6
4. Deliverables ........................................................................................................................................................ 6
4.1.1 Remarks ........................................................................................................................................ 6
5. Project risks ........................................................................................................................................................ 6
6. Communication .................................................................................................................................................. 7
7. Configuration management ................................................................................................................................ 7
8. Project plan ......................................................................................................................................................... 7
8.1 Time schedule .......................................................................................................................................... 7
8.2 Activity plan ............................................................................................................................................. 8
8.3 Financial Plan ........................................................................................................................................... 8
8.3.1 Remarks ........................................................................................................................................ 8
Page 3
SaveUML
Project Description
Version:
1.0
Date: 2007-11-18
1.Introduction
1.1Purpose of this document
This project description document gives an introduction to the SaveUML project, assigned as a
mandatory requirement of the Distributed Software Development course at MDH, Västerås and FER,
Zagreb. The purpose of the SaveUML project is to transform UML component models into SaveCCM
models in Save IDE.
SaveCCM is a component modeling language for embedded systems designed with vehicle
applications and safety concerns in focus.
1.2Intended Audience
 Ivica Crnkovic, the customer of the project.
 Aneta Vulgarakis and Rikard Land, members of the steering group.
 Future students of this course, Distributed Software Development.
 People interested in the project of transforming UML to SaveCCM.
1.3Scope
The document describes the basic structure of the SaveUML project focused on meeting the
requirements of the customer.
1.4Definitions and acronyms
1.4.1Definitions
Keyword
Metadata
Definitions
Data about data
1.4.2Acronyms and abbreviations
Acronym or
abbreviation
UML
SaveCCM
XML
XMI
Definitions
Unified Modeling Language. Standard language for modeling
systems.
SaveComp Component Model. Component modeling language for
embedded systems
eXtensible Markup Language. Language for structuring and storing
information
XML Metadata Interchange. Standard for exchanging metadata
information
1.5References
1. The SaveCCM Language Reference Manual.
2.Organization
Page 4
SaveUML
Project Description
Version:
1.0
Date: 2007-11-18
2.1Project management
Project Manager: Alexander Penner
Team Leader (Croatia): Mario Mucalo
2.2Project group
Name
Alexander Penner
Initials
AP
Mario Mucalo
MM
Muhammad
Rafique RD
Danish
Dennis Andersson
DA
Ivan Ferdelja
Luka Lednicki
Igor Smud
Mikael Engbom
Responsibility (roles)
Project Manager, communication with customer, report
writing.
Team Leader (FER), Forum, UML Profile.
Minutes of meetings, assisting report writer.
SVN management, Save-IDE.
IF
LL
UML Profile.
UML Tools, XML from UML.
IS
ME
DTD to Schema, UML-XML to Save-XML tools.
Backups, transformation of diagram visuals.
2.3Steering group
Rikard Land, Aneta Vulgarakis
2.4Customer
prof.dr.sc. Ivica Crnkovic
2.5Others
Igor Cavrak, prof.dr.sc. Mario Zagar
3.Assumptions and constraints
3.1Technological
Eclipse with Save IDE plug-ins, Visual Studio. All software used should be free or available free of
charge for students (MSDN Academic Alliance). In special circumstances commercial tools may be
used but restricted to evaluation releases of the software.
3.2Environmental
Microsoft Windows XP, Microsoft .NET Framework, JAVA.
3.3Interpersonal
Steering group members should be available for answering questions regarding the project.
3.4Work distribution
Each project member should always have clearly defined responsibilities and roles. Should a project
member find himself without work he should, as soon as possible, contact his local leader for
assignment of activities.
3.5Casual relationships
Possible relationships with the SaveCCM and SaveIDE developers.
Page 5
SaveUML
Project Description
Version:
1.0
Date: 2007-11-18
3.6Time
The project must be completed by 2007-01-25 and the final presentation be held on 2007-01-17.
4.Deliverables
To
Steering group/
Team members/
Customer
Steering group/
Team members/
Customer
Steering group/
Team members/
Customer
Steering group/
Team members/
Customer
Steering group/
Customer
Steering group/
Customer
Steering group/
Customer
Planned
week
46
Promised
week
46
Requirements
definition
46
46
Design description
delivered
47
47
Revised Design
description
48
48
Final product
3
3
Testing protocol
3
3
Final Project
Report and
documentation
4
4
Output
Project description
delivered
Late
+/-
Delivered
week
46
Rem
46
1
4.1.1Remarks
Remark
Id
1
Description
If necessary
5.Project risks
Possibility
Risk
Internal communication Moderate
problems.
Customer
Moderate to High
communication
problems.
Members dropping of.
Low
Tools
lacking Moderate
functionality.
Chosen tool may have Moderate to High
high learning curve.
Being late.
Moderate to High
Preventive action
Everyone should use Google Calendar to
schedule time for availability.
Try to schedule meetings well in advance.
Limit to emails when meetings are not
possible. Get requirements definition
formally accepted.
Keep good working atmosphere.
Make thorough analysis of available options
before committing to one tool.
Have one group member familiarize with the
tool as early as possible to answer future
questions.
Do as many tasks as possible in parallel. Be
prepared to work overtime.
Page 6
SaveUML
Project Description
Version:
1.0
Date: 2007-11-18
6.Communication
For the communication between the group members Skype shall be used. Meetings will be held at least
once a week for approximately two hours. Additional meetings will be scheduled according to demand,
that is, unresolved issues. Times for meetings are scheduled with the aid of a joint Google Calendar
account, where project members must enter their busy hours for each week. Furthermore, all project
members have each others' email addresses for alternative means of communication. The course web
page has a project related news page where information can be posted by team members. A project
forum has also been set up for topics requiring feedback, such as meeting agendas, for example.
7.Configuration management
Dennis Andersson was elected Subversion(SVN) manager because he had previous experience in
working with SVN. The repository is set up according to the following hierarchy.
 Documents folder
 Meetings folder. History for the Skype-meetings. Named like “Project meeting YYYYMM-DD.txt” for formal meetings and “Meeting X AB-CD YYYY-MM-DD.txt” for
informal meetings, where X is a number and AB-CD are the initials for participants in the
meeting. Informal history should only be uploaded when useful for others than the
participants.
 Presentations folder
 Documents, including Usage policy and work-in-progress reports. Final documents will
be uploaded to the project website.
 Save UML folder
 Code folder. Implementation for SAVE-IDE side.
 Documentation folder. Documentation regarding SAVE-IDE side.
 Models folder. Constructed models using SAVE-IDE side.
 Save XML folder
 Code folder. Implementation for XML related to Save.
 Documentation folder. Documentation for XML related to Save.
 UML folder
 Code folder. Implementation of the UML profile.
 Documentation folder. Documentation for the UML profile.
 Models folder. Constructed models using the UML profile.
 XML folder
 Code folder. Implementation for XML related to UML profile.
 Documentation folder. Documentation for XML related to UML profile.
8.Project plan
8.1Time schedule
Id
M001
M002
M003
M004
M005
M006
M007
M008
Milestone
Description
Responsible
Dept./Initials
Finished week
Plan
Project description accepted
AP, RD
46
Requirements definition accepted AP, RD
46
Project design delivered
IF, LL, AP
47
First Prototype demonstrated
MM, IF, IS, ME 48
Second Prototype demonstrated MM, IF, IS, ME 50
Testing complete
LL, DA
3
Final product demonstrated and MM, IF, IS, ME, 3
delivered
LL, DA
Final Project Report delivered
AP, RD
4
Forecast
Week +/46
46
47
48
50
3
3
Actual
Metr.
Rem.
4
Page 7
SaveUML
Project Description
Version:
1.0
Date: 2007-11-18
8.2Activity plan
Activity
w44 w45 w46 w47 w48 w49 w50 w51 w3 w4
Project preparations
Requirements analysis & definition
Project Design
Implementation
Testing
Integration
Final Product
Documentation
Final Project Presentation
Final Project Report
8.3Financial Plan
Volume
(days)
Activity
Project preparations
Requirements analysis & definition
Project Design
Implementation
Testing
Integration
Final Product
Documentation
Final Project Presentation
Final Project Report
14
28
28
35
20
12
12
16
6
9
Cost ( €)
5.600
11.200
11.200
14.000
8.000
4.800
4.800
6.400
2.400
3.600
Rem.
1
1
1
1
1
1
1
1
1
1
Planned effort (man-days)
Man-day cost
Planned project cost (100%)
180
400 €
72.000 €
8.3.1Remarks
Remark
Id
1
Description
Rough estimates.
Page 8