PROCOM@MDH
Project Description
Version:
1.0
Date: 2009-09-26
PROCOM@MDH
Project Description
Version 1.0
Page 1
Doc. No.:
PROCOM@MDH
Project Description
Version:
1.0
Date: 2009-09-26
Revision History
Date
Version
Description
2009-09-27
0.01
Initial Draft
2009-10-02
1
Contains changes
supervisor
Author
PG,BB
suggested
by
the
PG
Page 2
PROCOM@MDH
Project Description
Version:
1.0
Date: 2009-09-26
Table of Contents
1.
2.
3.
Introduction
4
1.1
1.2
1.3
1.4
Purpose of this document
Intended Audience
Scope
Definitions and acronyms
1.4.1 Definitions
1.4.2 Acronyms and abbreviations
1.5 References
4
4
4
4
4
4
5
Organization
5
2.1
2.2
2.3
2.4
2.5
5
5
5
5
5
Project management
Project group
Steering group
Customer
Others
Assumptions and constraints
5
3.1
3.2
3.3
3.4
3.5
3.6
5
6
6
6
6
6
Technological
Environmental
Interpersonal
Work distribution
Casual relationships
Time
4.
Deliverables
6
5.
Inputs
8
6.
Project risks
8
7.
Communication
8
8.
Configuration management
9
9.
Project plan
9
9.1
9.2
9.3
Time schedule
Activity plan
Financial Plan
9.3.1 Remarks
9
10
10
10
Page 3
PROCOM@MDH
Project Description
1.
Version:
1.0
Date: 2009-09-26
Introduction
1.1
Purpose of this document
This document provides detailed description of our project PROCOM@MDH. The audience of this project
would get a brief overview of the project. PROCOM model was developed at Mälardalen University as a part of
PROGRESS project which is used for formal modeling of embedded systems.
PROCOM@MDH project enables user to generate executable Java code for the PROCOM model created in
Progress IDE It would also enable user to retrieve the code for the existing models. These models are
component based and are well suited to analyze embedded system resources.
1.2
Intended Audience



Customer: Helps the customer to know the project milestones and their deadlines. Customer can
also raise an alarm in case of any concerns
Project group: Provides overview about the work to be done and the deadlines for the same
Steering group: Help the group to monitor the actual work with respect to the plan work
1.3
Scope
This document provides a clear picture about the project team along with their roles and
responsibilities. It also highlights the approach followed by the team, terminologies used, possible risks
identified and the possible steps to mitigate those risks. This document does not deal with the design
aspect of the project.
1.4
Definitions and acronyms
1.4.1
Definitions
Keyword
PROGRESS-IDE
The IDE which enables user to model the embedded system using the
PROCOM model.
Project Manager
Person responsible for team management and organization. He is
also responsible for interacting with the customer and the steering
group
files (documents, presentation) which team is supposed to deliver
to the customer/steering group
a date by which the specified task should be finished
Deliverables
Milestone
1.4.2
Definitions
Acronyms and abbreviations
Acronym or
abbreviation
PROCOM
MDH
SVN
UML
XML
Definitions
Progress Component Model
Mälardalen University
Subversion
Unified Modeling Language, language for modeling systems
Extensible Markup Language, language for storing information
Page 4
PROCOM@MDH
Project Description
1.5
Version:
1.0
Date: 2009-09-26
References
The materials referenced were as follows:


Formal semantics of ProCom (section 2 and 3).
ProCom - the progress component model reference manual
2.
Organization
2.1
Project management
Project Manager – Piyush Gupta
2.2
Project group
Name
Piyush Gupta
Priyadarshan Patil
Manzoor Ahmad
Bilal Butt
Iftikhar Ahmad
Parisa Zahedi
Initials
PG
PP
MA
BB
IA
PZ
Responsibility (Roles)
Project manager, coding, design
Design, testing, coding
Document Manager,design,coding
Document Manager,design,coding
Design, coding, testing
SVN manager, testing, coding
2.3
Steering group
Ana Petricic.
2.4
Customer
Ivica Crnkovic, Rikard Land
2.5
Others
3.
Assumptions and constraints
3.1
Technological

We will be using Eclipse together with the Eclipse Modeling Framework and Eclipse Rich
Client Platform plug-in for programming the GUI.

StarUML will be used for design of UML/class diagrams and use-case models. Both these
applications are freeware and available for all the team members.

Microsoft Projects is used for project management activities such as task management,
project plan, etc.
The following technologies will be used during the project development. All software’s are open
source standard:
1.
2.
3.
4.
JAVA (J2SE 1.6)
SVN
XML
Eclipse SDK 3.4
We will be getting error free XML from the progress IDE for code generator plug-in.
Page 5
PROCOM@MDH
Project Description
3.2
3.3
Version:
1.0
Date: 2009-09-26
Environmental

Since program will be made in Java; it's be easily run on any platform, from Windows to
UNIX. The programming itself will be made on windows 7, vista.

Eclipse 3.4 with Progress IDE plug-in must be installed on the machine with JDK 1.6 or
higher in order to run the project.

SVN is used for backup, it's both free and open source.
Interpersonal

Effective communication and quality feedback is expected from all the team members for
successful completion of the project.

Communication with team and customer would be organized once in a week to voice
concerns, evaluate risks and track progress.

English is the language of communication.

A Google group “[email protected]” is created to post any suggestions,
problems, criticism and seeking help from teammates etc. This group work would help in
better team building. An access to the group can be requested by an email to the document
manager.

A Google calendar is maintained for scheduling meetings and tasks in the team.
3.4
Work distribution
Work is distributed evenly among all the team members according to their expertise and interest. This
is achieved after continuous meetings with our MDH teammates. The work taken up by the members is
recorded as a reference and everyone is happy to work on their assigned task.
3.5
Casual relationships
The relationship among the team members need to be good and cooperative. This make fair work
environment. As our team members are from different culture, we need to have good communication
and cooperation among all. Proper communication between the team members, continuous feedback
from the customer and guidance from the supervisor gives more strength to the project.
3.6
Time
4.
Deliverables
To
Steering group,
Project Team
members
Project Team
members
Output
Project
Vision
Planned
week
W38
Promised
week
W38
Document
Project
Description
document
Steering Group, Project
Customer
Description
document
Steering
Project
group,Cutomer Description
presentation
WK39
WK39
WK40
WK40
WK40
WK40
Late +/0
Delivered
week
W38(200
9)
Rema
rks
Page 6
PROCOM@MDH
Project Description
Project Team Requirements
member
Description
document
Steering
Requirements
group,Cutomer Description
document
Project Team Design
members
Description
document
Steering Group Design
Description
document
Steering
Requirements
Group,Cutomer and
Design
Description
Presentation
Customer
Project Status
presentation
Steering Group, Design
Project Team Description
Member
documents
(revised)
Customer
Project Status
presentation
Steering Group, Design
Project Team Description
Member
documents
(revised)
Steering group, Acceptance
Project Team Test
Plan
members
document
Steering
Acceptance
group,Cutomer Test
Plan
document
Steering group, Test Report
Project Team
members
Steering Group Test report
Project Team Final Project
members
Report
document
Customer,
Final Project
Steering group report
document
Customers,
Final Project
Steering group Presentation
Steering group, Summary
Project Team Week Report
members
Steering group, Minutes
of
Project Team Meetings
members
Version:
1.0
Date: 2009-09-26
WK39
WK40
WK40
WK41
WK41
WK44
WK46
WK47
WK 51
WK48
WK49
WK50
WK01
WK02
WK01
WK02
WK01
WK02
WK02
WK02
WK38 to
WK02
WK38 to
WK02
Page 7
PROCOM@MDH
Project Description
Version:
1.0
Date: 2009-09-26
Steering group, Technical
Project Team Documents
members
5.
WK38 to
WK02
Inputs
This project is stand-alone; it is not split into other projects. So there are no inputs from other groups
6.
7.
Project risks
Possibility
Competency of the
Team.
Risk
Medium
Is the size of team
adequate
Hardware Failure
Unavailability of the
members of
development team
Medium
Change in requirements
Medium
Development of wrong
functionalities
Medium
Customer communication
problems
Medium
Problems in Integration
of the Plug-in
Medium
Wrong design of the
mapping
High
Low
Low
Preventive action
Reading and understanding ProCom
model. Proof of concepts for the target
implementation.
Uniform distribution of work in the team
Backup of the Peripheral support
Rescheduling of working days and/ or
increasing working hours per day. Efforts
will be taken to create backups and reduce
dependency on the individuals
Continuous prototype update must be
carried out to satisfy the requirements
Continuous testing and analysis of
development artifacts.
Establish meeting with the customer to
understand the requirement. If meeting is
not possible then email is use as the option
for finalizing requirement.
Rigorous testing of the integrated
components of the plug-in will be carried
out.
Establish the various testing scenarisso to
test the developed prototype based on the
design
Communication
The communication among the members of the group becomes very important as we are from
different countries and culture. Communication helps in building good team spirit and reduce
communication gap. As the project team is in MDH and supervisor is from Zagreb
(Temporarily in MDH) we are using various collaboration tools for the synchronous and
asynchronous communication such as:
1. Google Groups: A Google group (PROCOM MDH 2009) has already been created
to communicate between the team members and also the project supervisor. All the
required files are uploaded in the Google groups.
2. Google Docs and Google Poll: Google Docs helps to share a document on the Web
and helps all the team members to view the project documents. But document
manager is responsible for editing and uploading of the document. All team member
can share their comments or contribution on document via mail. Google polls are
important for getting suggestions and feedback from the team members on important
Page 8
PROCOM@MDH
Project Description
Version:
1.0
Date: 2009-09-26
issues.
3. Skype: Using Skype Video call and conferences for connecting with the Project
Supervisor and every member of the team. We conduct weekly meeting once using
Skype on weekends.
4. Email: All the important decisions and official meeting outcomes are sent via email.
8.
Configuration management
SVN is the tool used for software configuration management. It is used for source code and document
versioning. It is maintained by our team member Parisa Zahedi. We will create the separate folder
structure for code and documents.
9.
Project plan
9.1
Time schedule
Id
M001
M002
M003
M003
M004
M005
M006
M007
M008
M009
M010
M011
M012
M013
M009
M010
M010
M011
Finished week
Responsible
Dept./Initial
Forecast
Plan
Actual
s
Week +/Project Vision presented
PG
WK38
WK38
Project Description Presented
PG,BB
WK40
WK40
Learning PROCOM model
WK39
WK39
PG,MA,IA,
PP,PZ
Requirements analysis and definition PG,BB,PZ WK40
WK40
Design Mapping Identification
BB,PP,IA WK41
Project design version 1 delivered
IF, LL, AP WK41
First Prototype demonstrated
PG,PP,PZ, WK44
(Implementation of code generation for MA
PROSAVE component )
Design
mapping
for
PROSYS BB,IA,MA, WK45
component.
PG
Project Design Document version 2 BB,IA,PP,P WK46
delivered
G
Second
Prototype
demonstrated PG,PP,PZ, WK47
(Implementation of code generation for MA
PROSYS component )
Identify Possibility of ‘GLUE CODE’ BB,IA,PG, WK48
Generation
PP
Acceptance Test Plan Presented
PG,MA,IA WK49
Final Design Document Delivered
BB,IA,PP,P WK50
G
Third
Prototype
demonstrated PG,PP,PZ, WK51
(Implementation of code generation for MA
‘GLUE CODE’)
Testing complete
PZ,IA,PG WK01
User Documentation
MA,PZ,IA WK01
Final product demonstrated and PG,PP,MA, WK02
delivered
IA,PZ
Final Project Report delivered
PG
WK02
Milestone
Description
Metr.
Rem.
Page 9
PROCOM@MDH
Project Description
9.2
Version:
1.0
Date: 2009-09-26
Activity plan
Activity
Project Preparations
W38W39W40W41W42W43W44W45 W46 W47 W48 W49 W50 W51 W52 W1 W2
Requirements Analysis &
Definition
Tools Design
Tool Implementation
Integration of modules in tools
Testing
Troubleshooting
Documentation
Final Release
9.3
Financial Plan
Volume
(days)
14
10
6
10
21
33
18
Activity
Project management and Preparation
Team Documentation (know how)
Project Documentation and Presentation
Requirement Analysis and Gathering
Tool Design
Implementation
Testing
Cost
22400
16000
9600
16000
33600
62400
28800
Rem.
01
Planned effort (man-days)
Man-day cost
Planned project cost (100%)
112
1600 SEK
179200 SEK
9.3.1
Remarks
Remark
Id
01
Description
8 hour per day per person
Page 10