SIW Team Development Plan

Revision A - 22 MARCH 1996

	Name	Position	E-mail address
Author(s):	Johan Sassner	Team Manager	pt93js@pt.hk-r.se
Responsible:	Johan Sassner	Team Manager	pt93js@pt.hk-r.se
To:	Marcus Ingemansson	Project Manager	pt93mi@pt.hk-r.se
Cc:	Fredrik Hall Peter Wikström Martin Fredriksson Lars Olofsson Jim Håkansson		pt93fh@pt.hk-r.se pt93pw@pt.hk-r.se pt93mf@pt.hk-r.se pt93lo@pt.hk-r.se pt93jha@pt.hk-r.se

Abstract

This document describes the development plan for the SIW (Superb Interaction Workshop) team in SAIDA [SAIDA 96-7].

1 System Overview

The goal for the project is to develop the CCN [SAIDA 96-6], and the SIW team develops these subsystems:

WWW interface (WWW) - a simple interface to allow get/set functions to be accessed via WWW.
Remote Data Navigator (RDN) - a hierarchy of external variable names, and maps get/set requests to the actual objects.
Remote development environment (RDE) - a client application for building, installing and running NeuronC programs.

See Solution Decomposition [SAIDA 96-5] for more details.

2 Delivery Plan

Delivery 1 on 1996-04-11, 13:00 (Thursday, week 15) which includes:

WWW interface.

Delivery 2 on 1996-04-25, 13:00 (Thursday, week 17) which includes:

Remote Data Navigator

Delivery 3 on 1996-05-09, 13:00 (Thursday, week 19) which includes:

Remote Development Environment

Delivery 4 (final delivery) on 1996-05-30, 13:00 (Thursday, week 22) which includes:

Remote Development Environment

3 Activity Description

See [SAIDA 96-8] for estimations of these activities.

Scheduled activity list
Id Name Description Start date End date Dependencies
1 Activities common for all subsystems
1.1 Planning/administration
1.1.1 Development plan Describe the project goals, activities, milestones etc. Performed by the Team Manager and results in a Team Development Plan (TDP). 1996-03-04 1996-03-30
1.1.2 Planning Plan the activities throughout the project. 1996-03-04 1996-05-30
1.1.3 Team management Managing the team. 1996-03-04 1996-05-30
1.2 Learning
1.2.1 OLE Learn how to build OLE-objects. 1996-03-04 1996-05-30
1.2.2 Visual C++ Learn how to use Microsoft Visual C++. 1996-03-04 1996-05-30
1.2.3 Visual Basic Learn how to use Microsoft Visual Basic. 1996-03-04 1996-04-25
1.2.4 HTML/cgi script Learn HTML and cgi-scripts programming. 1996-03-04 1996-03-19
1.2.5 Lonworks Component Architecture (LCA) Learn how to use the functionality in the Lonworks Component Architecture. 1996-03-20 1996-05-30
1.3 Meetings
1.3.1 Team meetings Internal meetings within the group. 1996-03-04 1996-05-30
1.3.2 Meetings with technical advisor Meetings with our technical advisors Fredrik Ygge and Jan Bosch. 1996-03-04 1996-05-30
1.3.3 Protocol/agenda 1996-03-04 1996-05-30 [1.3.1]
1.4 Reporting
1.4.1 Status reporting Reporting the team's status to the Project Manager, performed by the Team Manager and results in a weekly status report. 1996-03-04 1996-05-30

2 Activities for the 'WWW Interface'-application
2.1 Planning and Administration
2.1.1 Estimations Estimate the time needed for analysis, design, implementation, testing and inspection of the activities specific for the WWW interface. Performed by the Team Manager and results in an estimation document. 1996-03-08 1996-03-15
2.1.2 Follow up This includes looking at the earlier estimations 1996-03-08 1996-03-15
2.1.3 Requirement specification In the beginning of the WWW interface development, a requirements specification shall be produced. This document includes what shall be the result of this subsystem when delivered. 1996-08-08 1996-03-20
2.2 Analysis and design
2.2.1 Design Design the subsystem. A design document will be the result of this activity. 1996-03-08 1996-03-19
2.2.2 Design correction All errors found during inspection shall be fixed in this activity. 1996-03-22 1996-03-29 [2.2.1]
2.3 Implementation
2.3.1 Implementation The subsystem is implemented in this activity. Both source code and binaries will be the result of this activity. 1996-03-14 1996-03-20
2.3.2 Implementation correction All errors found in testing and inspection shall be fixed in this activity. 1996-03-25 1996-03-27 [2.3.1]
2.4 Testing
2.4.1 Test specification Writing a testspecification 1996-03-14 1996-03-19
2.4.2 Application test Test the application. If there are any errors; notify the responsible for implementation. 1996-03-20 1996-03-25 [2.4.1]
2.4.3 Correction test Test to examine whether the errors found in the application test is fixed or not. 1996-03-25 1996-03-25 [2.4.2]
2.5 Documents
2.5.1 Delivery document Document for the customer containing information about how this subsystem works and how to use it. 1996-03-20 1996-03-25
3 Activities for the 'Remote Navigator'-application
3.1 Planning and Administration
3.1.1 Estimations Estimate the time needed for analysis, design, implementation, testing and inspection of the activities specific for the remote navigator. Performed by the Team Manager and results in an estimation document. This includes looking at the earlier estimations. 1996-03-18 1996-03-18
3.1.2 Follow up Compare the actual worked time with the estimations. 1996-03-18 1996-03-18 [2.1.1]
3.1.3 Requirement specification In the beginning of the Remote Data Navigator development, a requirements specification shall be produced. This document includes what shall be the result of this subsystem when delivered. 1996-03-18 1996-03-20
3.2 Design
3.2.1 Design Design the subsystem. A design document will be the result of this activity. 1996-03-22 1996-04-01
3.2.2 Design correction All errors found during inspection shall be fixed in this activity. 1996-04-02 1996-04-03 [3.2.1]
3.3 Implementation
3.3.1 Implementation The subsystem is implemented in this activity. Both source code and binaries will be the result of this activity. 1996-03-27 1996-04-11
3.3.2 Implementation correction All faults found in testing and inspection shall be fixed in this activity. 1996-04-15 1996-04-22 [3.3.1]
3.4 Testing
3.4.1 Test specification Writing a testspecification 1996-04-01 1996-04-04
3.4.2 Application test Test the application. If there are any errors; notify the responsible for implementation. 1996-04-11 1996-04-18 [3.4.1]
3.4.3 Correction test Test to examine whether the errors found in the application test is fixed or not. 1996-04-18 1996-04-23 [3.4.2]
3.5 Documents
3.5.1 Delivery document Document for the customer containing information about how this subsystem works and how to use it. 1996-04-18 1996-04-24
4 Activities for the 'Remote Development Environment Client'-application
4.1 Planning and Administration
4.1.1 Estimations Estimate the time needed for analysis, design, implementation, testing and inspection of the activities specific for the development environment. Performed by the Team Manager and results in an estimation document. This includes looking at the earlier estimations. 1996-04-24 1996-04-24
4.1.2 Follow up Compare the actual worked time with the estimations. 1996-04-24 1996-04-24 [3.1.1]
4.1.3 Requirement specification In the beginning of the Remote Development Environment development, a requirements specification shall be produced. This document includes what shall be the result of this subsystem when delivered. 1996-04-24 1996-04-25
4.2 Design
4.2.1 Design Design the subsystem. A design document will be the result of this activity. 1996-04-25 1996-05-06
4.2.2 Design correction All errors found during inspection shall be fixed in this activity. 1996-05-09 1996-05-13 [4.2.1]
4.3 Implementation
4.3.1 Implementation The subsystem is implemented in this activity. Both source code and binaries will be the result of this activity. 1996-05-02 1996-05-10
4.3.2 Implementation correction All faults found in testing and inspection shall be fixed in this activity. 1996-05-09 1996-05-10 [4.3.1]
4.4 Testing
4.4.1 Test specification Writing a testspecification 1996-04-25 1996-04-29
4.4.2 Application test Test the application. If there are any errors; notify the responsible for implementation. 1996-05-08 1996-05-13 [4.4.1]
4.4.3 Correction test Test to examine whether the errors found in the application test is fixed or not. 1996-05-13 1996-05-14 [4.4.2]
4.5 Documents
4.5.1 Delivery document Document for the customer containing information about how this subsystem works and how to use it. 1996-05-13 1996-05-14
5 Activities for the 'Remote Development Environment Server'-application

5.1 Planning and Administration
5.1.1 Estimations Estimate the time needed for analysis, design, implementation, testing and inspection of the activities specific for the development environment. Performed by the Team Manager and results in an estimation document. This includes looking at the earlier estimations. 1996-05-15 1996-05-15
5.1.2 Follow up Compare the actual worked time with the estimations. 1996-05-15 1996-05-15 [4.1.1]
5.1.3 Requirement specification In the beginning of the Remote Development Environment development, a requirements specification shall be produced. This document includes what shall be the result of this subsystem when delivered. 1996-05-15 1996-05-15
5.2 Design
5.2.1 Design Design the subsystem. A design document will be the result of this activity. 1996-05-20 1996-05-21
5.2.2 Design correction All errors found during inspection shall be fixed in this activity. 1996-05-22 1996-05-23 [5.2.1]
5.3 Implementation
5.3.1 Implementation The subsystem is implemented in this activity. Both source code and binaries will be the result of this activity. 1996-05-22 1996-05-23
5.3.2 Implementation correction All faults found in testing and inspection shall be fixed in this activity. 1996-05-28 1996-05-28 [5.3.1]
5.4 Testing
5.4.1 Test specification Writing a testspecification 1996-05-22 1996-05-23
5.4.2 Application test Test the application. If there are any errors; notify the responsible for implementation. 1996-05-24 1996-05-24 [5.4.1]
5.4.3 Correction test Test to examine whether the errors found in the application test is fixed or not. 1996-05-28 1996-05-28 [5.4.2]
5.5 Documents
5.5.1 Delivery document Document for the customer containing information about how this subsystem works and how to use it. 1996-05-28 1996-05-29

Scheduled activity list
Id	Name	Description	Start date	End date	Dependencies
1	Activities common for all subsystems
1.1	Planning/administration
1.1.1	Development plan	Describe the project goals, activities, milestones etc. Performed by the Team Manager and results in a Team Development Plan (TDP).	1996-03-04	1996-03-30
1.1.2	Planning	Plan the activities throughout the project.	1996-03-04	1996-05-30
1.1.3	Team management	Managing the team.	1996-03-04	1996-05-30
1.2	Learning
1.2.1	OLE	Learn how to build OLE-objects.	1996-03-04	1996-05-30
1.2.2	Visual C++	Learn how to use Microsoft Visual C++.	1996-03-04	1996-05-30
1.2.3	Visual Basic	Learn how to use Microsoft Visual Basic.	1996-03-04	1996-04-25
1.2.4	HTML/cgi script	Learn HTML and cgi-scripts programming.	1996-03-04	1996-03-19
1.2.5	Lonworks Component Architecture (LCA)	Learn how to use the functionality in the Lonworks Component Architecture.	1996-03-20	1996-05-30
1.3	Meetings
1.3.1	Team meetings	Internal meetings within the group.	1996-03-04	1996-05-30
1.3.2	Meetings with technical advisor	Meetings with our technical advisors Fredrik Ygge and Jan Bosch.	1996-03-04	1996-05-30
1.3.3	Protocol/agenda		1996-03-04	1996-05-30	[1.3.1]
1.4	Reporting
1.4.1	Status reporting	Reporting the team's status to the Project Manager, performed by the Team Manager and results in a weekly status report.	1996-03-04	1996-05-30

2	Activities for the 'WWW Interface'-application
2.1	Planning and Administration
2.1.1	Estimations	Estimate the time needed for analysis, design, implementation, testing and inspection of the activities specific for the WWW interface. Performed by the Team Manager and results in an estimation document.	1996-03-08	1996-03-15
2.1.2	Follow up	This includes looking at the earlier estimations	1996-03-08	1996-03-15
2.1.3	Requirement specification	In the beginning of the WWW interface development, a requirements specification shall be produced. This document includes what shall be the result of this subsystem when delivered.	1996-08-08	1996-03-20
2.2	Analysis and design
2.2.1	Design	Design the subsystem. A design document will be the result of this activity.	1996-03-08	1996-03-19
2.2.2	Design correction	All errors found during inspection shall be fixed in this activity.	1996-03-22	1996-03-29	[2.2.1]
2.3	Implementation
2.3.1	Implementation	The subsystem is implemented in this activity. Both source code and binaries will be the result of this activity.	1996-03-14	1996-03-20
2.3.2	Implementation correction	All errors found in testing and inspection shall be fixed in this activity.	1996-03-25	1996-03-27	[2.3.1]
2.4	Testing
2.4.1	Test specification	Writing a testspecification	1996-03-14	1996-03-19
2.4.2	Application test	Test the application. If there are any errors; notify the responsible for implementation.	1996-03-20	1996-03-25	[2.4.1]
2.4.3	Correction test	Test to examine whether the errors found in the application test is fixed or not.	1996-03-25	1996-03-25	[2.4.2]
2.5	Documents
2.5.1	Delivery document	Document for the customer containing information about how this subsystem works and how to use it.	1996-03-20	1996-03-25
3	Activities for the 'Remote Navigator'-application
3.1	Planning and Administration
3.1.1	Estimations	Estimate the time needed for analysis, design, implementation, testing and inspection of the activities specific for the remote navigator. Performed by the Team Manager and results in an estimation document. This includes looking at the earlier estimations.	1996-03-18	1996-03-18
3.1.2	Follow up	Compare the actual worked time with the estimations.	1996-03-18	1996-03-18	[2.1.1]
3.1.3	Requirement specification	In the beginning of the Remote Data Navigator development, a requirements specification shall be produced. This document includes what shall be the result of this subsystem when delivered.	1996-03-18	1996-03-20
3.2	Design
3.2.1	Design	Design the subsystem. A design document will be the result of this activity.	1996-03-22	1996-04-01
3.2.2	Design correction	All errors found during inspection shall be fixed in this activity.	1996-04-02	1996-04-03	[3.2.1]
3.3	Implementation
3.3.1	Implementation	The subsystem is implemented in this activity. Both source code and binaries will be the result of this activity.	1996-03-27	1996-04-11
3.3.2	Implementation correction	All faults found in testing and inspection shall be fixed in this activity.	1996-04-15	1996-04-22	[3.3.1]
3.4	Testing
3.4.1	Test specification	Writing a testspecification	1996-04-01	1996-04-04
3.4.2	Application test	Test the application. If there are any errors; notify the responsible for implementation.	1996-04-11	1996-04-18	[3.4.1]
3.4.3	Correction test	Test to examine whether the errors found in the application test is fixed or not.	1996-04-18	1996-04-23	[3.4.2]
3.5	Documents
3.5.1	Delivery document	Document for the customer containing information about how this subsystem works and how to use it.	1996-04-18	1996-04-24
4	Activities for the 'Remote Development Environment Client'-application
4.1	Planning and Administration
4.1.1	Estimations	Estimate the time needed for analysis, design, implementation, testing and inspection of the activities specific for the development environment. Performed by the Team Manager and results in an estimation document. This includes looking at the earlier estimations.	1996-04-24	1996-04-24
4.1.2	Follow up	Compare the actual worked time with the estimations.	1996-04-24	1996-04-24	[3.1.1]
4.1.3	Requirement specification	In the beginning of the Remote Development Environment development, a requirements specification shall be produced. This document includes what shall be the result of this subsystem when delivered.	1996-04-24	1996-04-25
4.2	Design
4.2.1	Design	Design the subsystem. A design document will be the result of this activity.	1996-04-25	1996-05-06
4.2.2	Design correction	All errors found during inspection shall be fixed in this activity.	1996-05-09	1996-05-13	[4.2.1]
4.3	Implementation
4.3.1	Implementation	The subsystem is implemented in this activity. Both source code and binaries will be the result of this activity.	1996-05-02	1996-05-10
4.3.2	Implementation correction	All faults found in testing and inspection shall be fixed in this activity.	1996-05-09	1996-05-10	[4.3.1]
4.4	Testing
4.4.1	Test specification	Writing a testspecification	1996-04-25	1996-04-29
4.4.2	Application test	Test the application. If there are any errors; notify the responsible for implementation.	1996-05-08	1996-05-13	[4.4.1]
4.4.3	Correction test	Test to examine whether the errors found in the application test is fixed or not.	1996-05-13	1996-05-14	[4.4.2]
4.5	Documents
4.5.1	Delivery document	Document for the customer containing information about how this subsystem works and how to use it.	1996-05-13	1996-05-14
5	Activities for the 'Remote Development Environment Server'-application
5.1	Planning and Administration
5.1.1	Estimations	Estimate the time needed for analysis, design, implementation, testing and inspection of the activities specific for the development environment. Performed by the Team Manager and results in an estimation document. This includes looking at the earlier estimations.	1996-05-15	1996-05-15
5.1.2	Follow up	Compare the actual worked time with the estimations.	1996-05-15	1996-05-15	[4.1.1]
5.1.3	Requirement specification	In the beginning of the Remote Development Environment development, a requirements specification shall be produced. This document includes what shall be the result of this subsystem when delivered.	1996-05-15	1996-05-15
5.2	Design
5.2.1	Design	Design the subsystem. A design document will be the result of this activity.	1996-05-20	1996-05-21
5.2.2	Design correction	All errors found during inspection shall be fixed in this activity.	1996-05-22	1996-05-23	[5.2.1]
5.3	Implementation
5.3.1	Implementation	The subsystem is implemented in this activity. Both source code and binaries will be the result of this activity.	1996-05-22	1996-05-23
5.3.2	Implementation correction	All faults found in testing and inspection shall be fixed in this activity.	1996-05-28	1996-05-28	[5.3.1]
5.4	Testing
5.4.1	Test specification	Writing a testspecification	1996-05-22	1996-05-23
5.4.2	Application test	Test the application. If there are any errors; notify the responsible for implementation.	1996-05-24	1996-05-24	[5.4.1]
5.4.3	Correction test	Test to examine whether the errors found in the application test is fixed or not.	1996-05-28	1996-05-28	[5.4.2]
5.5	Documents
5.5.1	Delivery document	Document for the customer containing information about how this subsystem works and how to use it.	1996-05-28	1996-05-29

4 Schedule

4.1 HTML

4.2 Navigator

4.3 Development Environment

4.4
Milestones
Milestone Initial
estimation
(h)
Planned date Subsystem
WWW interface 115 1996-03-20 [2]
Remote navigator 658 1996-04-25 [3]
RDE server 105 1996-05-10 [4]
RDE client 580 1996-05-29 [5]
Milestones

Milestones
Milestone	Initial estimation (h)	Planned date	Subsystem
WWW interface	115	1996-03-20	[2]
Remote navigator	658	1996-04-25	[3]
RDE server	105	1996-05-10	[4]
RDE client	580	1996-05-29	[5]

4.5 Needed Resources

5 Documents

These are the documents to be produced with start date, end date and when it are ready from inspection date. Inspection type is Shallow or Deep.

Documents
Name Description Start date End date Rel. date Activity Insp. type Rs
WWW Interface
WWW Estimation Document A document containing estimations for the WWW interface 1996-03-08 1996-03-15 1996-03-18 [2.1.1] S JS
WWW Requirements specification Requirements specification of the WWW interface. This document should be output from the 'WWW'-design activity. 1996-03-08 1996-03-20 1996-03-22
[2.1.3]
S JS
WWW Design Document A document containing the design for the WWW interface 1996-03-08 1996-03-18 1996-03-22 [2.2.1] D PW
WWW Implementation Source code developed in the WWW interface 1996-03-08 1996-03-20 1996-03-22 [2.3.1] S MF
WWW Test specification Test specification for the WWW interface 1996-03-14 1996-03-19 1996-03-26 [2.4.1] D JHA
WWW User's Guide User's guide to the WWW interface. 1996-03-20 1996-03-25 1996-03-28 [2.5.1] D MF
WWW follow-up document Compare the actual worked time and the estimations. 1996-03-18 1996-03-18 1996-03-20 [2.1.2] S JS
Remote Data Navigator
RDN Estimation Document A document containing estimations for the Remote Navigator 1996-03-18 1996-03-18 1996-03-20 [3.1.1] S JS
RDN Requirements specification Requirements specification of the Navigator. This document should be output from the 'Navigator'-design activity. 1996-03-18 1996-03-18 1996-03-20 [3.1.3] S JS
RDN Design Document A document containing the design for the Remote Navigator 1996-03-15 1996-03-27 1996-04-02 [3.2.1] D PW
RDN Implementation Source code developed in the Remote Navigator 1996-03-25 1996-04-19 1996-04-23 [3.3.1] S LO
RDN Test specification Test specification for the RDN interface 1996-04-12 1996-04-16 1996-04-22 [3.4.1] D JHA
RDN User's Guide User's guide to the RDN interface. 1996-04-15 1996-04-18 1996-04-24 [3.5.1] D MF
RDN follow-up document Compare the actual worked time and the estimations. 1996-04-25 1996-04-25 1996-04-29 [3.1.2] S JS
Remote Development Environment
RDE Estimation Document A document containing estimations for the Development Environment 1996-04-24 1996-04-24 1996-04-26 [4.1.1]
[5.1.1]
S JS
RDE Requirements specification Requirements specification of the Development Environment. This document should be output from the 'RDE'-design activity. 1996-04-24 1996-04-25 1996-04-29 [4.1.3]
[5.1.3]
S JS
Server
RDE Client Design Document A document containing the design for the Development Environment 1996-04-26 1996-05-03 1996-05-09 [4.2.1] D PW
RDE Client Implementation Source code developed in the Development Environment 1996-04-29 1996-05-08 1996-05-10 [4.3.1] S LO
RDE Test specification Test specification for the RDE interface 1996-05-06 1996-05-07 1996-05-10 [4.4.1] D JHA
RDE User's Guide User's guide to the RDE interface. 1996-05-06 1996-05-09 1996-05-14 [4.5.1] D MF
RDE follow-up document Compare the actual worked time and the estimations. 1996-05-15 1996-05-15 1996-05-15 [4.1.2] S JS
Client
RDE Server Design Document A document containing the design for the Development Environment 1996-05-13 1996-05-15 1996-05-21 [5.2.1] D PW
RDE Server Implementation Source code developed in the Development Environment 1996-05-14 1996-05-20 1996-05-22 [5.3.1] S LO
RDE Test specification Test specification for the RDE interface 1996-05-15 1996-05-20 1996-05-23 [5.4.1] D JHA
RDE User's Guide User's guide to the RDE interface. 1996-05-20 1996-05-23 1996-05-29 [5.5.1] D MF
RDE follow-up document Compare the actual worked time and the estimations. 1996-05-29 1996-05-29 1996-05-29 [5.1.2] S JS

Documents
Name	Description	Start date	End date	Rel. date	Activity	Insp. type	Rs
WWW Interface
WWW Estimation Document	A document containing estimations for the WWW interface	1996-03-08	1996-03-15	1996-03-18	[2.1.1]	S	JS
WWW Requirements specification	Requirements specification of the WWW interface. This document should be output from the 'WWW'-design activity.	1996-03-08	1996-03-20	1996-03-22	[2.1.3]	S	JS
WWW Design Document	A document containing the design for the WWW interface	1996-03-08	1996-03-18	1996-03-22	[2.2.1]	D	PW
WWW Implementation	Source code developed in the WWW interface	1996-03-08	1996-03-20	1996-03-22	[2.3.1]	S	MF
WWW Test specification	Test specification for the WWW interface	1996-03-14	1996-03-19	1996-03-26	[2.4.1]	D	JHA
WWW User's Guide	User's guide to the WWW interface.	1996-03-20	1996-03-25	1996-03-28	[2.5.1]	D	MF
WWW follow-up document	Compare the actual worked time and the estimations.	1996-03-18	1996-03-18	1996-03-20	[2.1.2]	S	JS
Remote Data Navigator
RDN Estimation Document	A document containing estimations for the Remote Navigator	1996-03-18	1996-03-18	1996-03-20	[3.1.1]	S	JS
RDN Requirements specification	Requirements specification of the Navigator. This document should be output from the 'Navigator'-design activity.	1996-03-18	1996-03-18	1996-03-20	[3.1.3]	S	JS
RDN Design Document	A document containing the design for the Remote Navigator	1996-03-15	1996-03-27	1996-04-02	[3.2.1]	D	PW
RDN Implementation	Source code developed in the Remote Navigator	1996-03-25	1996-04-19	1996-04-23	[3.3.1]	S	LO
RDN Test specification	Test specification for the RDN interface	1996-04-12	1996-04-16	1996-04-22	[3.4.1]	D	JHA
RDN User's Guide	User's guide to the RDN interface.	1996-04-15	1996-04-18	1996-04-24	[3.5.1]	D	MF
RDN follow-up document	Compare the actual worked time and the estimations.	1996-04-25	1996-04-25	1996-04-29	[3.1.2]	S	JS
Remote Development Environment
RDE Estimation Document	A document containing estimations for the Development Environment	1996-04-24	1996-04-24	1996-04-26	[4.1.1] [5.1.1]	S	JS
RDE Requirements specification	Requirements specification of the Development Environment. This document should be output from the 'RDE'-design activity.	1996-04-24	1996-04-25	1996-04-29	[4.1.3] [5.1.3]	S	JS
Server
RDE Client Design Document	A document containing the design for the Development Environment	1996-04-26	1996-05-03	1996-05-09	[4.2.1]	D	PW
RDE Client Implementation	Source code developed in the Development Environment	1996-04-29	1996-05-08	1996-05-10	[4.3.1]	S	LO
RDE Test specification	Test specification for the RDE interface	1996-05-06	1996-05-07	1996-05-10	[4.4.1]	D	JHA
RDE User's Guide	User's guide to the RDE interface.	1996-05-06	1996-05-09	1996-05-14	[4.5.1]	D	MF
RDE follow-up document	Compare the actual worked time and the estimations.	1996-05-15	1996-05-15	1996-05-15	[4.1.2]	S	JS
Client
RDE Server Design Document	A document containing the design for the Development Environment	1996-05-13	1996-05-15	1996-05-21	[5.2.1]	D	PW
RDE Server Implementation	Source code developed in the Development Environment	1996-05-14	1996-05-20	1996-05-22	[5.3.1]	S	LO
RDE Test specification	Test specification for the RDE interface	1996-05-15	1996-05-20	1996-05-23	[5.4.1]	D	JHA
RDE User's Guide	User's guide to the RDE interface.	1996-05-20	1996-05-23	1996-05-29	[5.5.1]	D	MF
RDE follow-up document	Compare the actual worked time and the estimations.	1996-05-29	1996-05-29	1996-05-29	[5.1.2]	S	JS

Documents produced
Documents Produced Shallow Inspection Deep Inspection
26 14 12

Documents produced
Documents Produced	Shallow Inspection	Deep Inspection
26	14	12

6 Risk Analysis

See the Project Development Plan [SAIDA 96-7] for more details.

7 Interface with External Resources

If any team member wants to contact any external resources he must have the team manager's approval. If the communication is by e-mail the team manager should be included a recipient of the mail.

8 Procedure for Formal Inspection

The inspection procedure should follow the one described in the Project Quality Manual. All the documents should be inspected to attain high quality of our software.

9 Software Engineering

9.1 Standards and Procedures

The Quality Management Group developed a Course Quality Manual. This manual is implemented in the SAIDA project by the Project Quality Manual (PQM). This PQM contains all the standards and procedures to be used in this subproject. If you have any problem by using the PQM you should talk to the Quality Coordinator.

9.2 Development Resources

We are going to use the latest version of Microsoft Visual C++ (version 4.0). The operating system we use is Microsoft Windows NT.

At the moment there is only four Windows NT workstations available at Sikt, this will probably not be sufficient. Read more about this in chapter [6], "Risk analysis".

9.3 Personnel - Qualifications and Function

The hours in the table show how many hours each person is available in the project. These hours include work in the project, lectures, meetings etc.

Personal resources.
Name	Position	e-mail	Phone	Signature
Johan Sassner	Team manager	pt93js@pt.hk-r.se	0457 - 13378	js
Fredrik Hall	Inspection Moderator	pt93fh@pt.hk-r.se	0457 - 14842	fh
Peter Wikström		pt93pw@pt.hk-r.se	0457 - 16123	pw
Martin Fredriksson	Delivery Manager	pt93mf@pt.hk-r.se	0457 - 19019	mf
Lars Olofsson		pt93lo@pt.hk-r.se	-	lo
Jim Håkansson	Test Manager	pt93jha@pt.hk-r.se	0455 - 28146	jha

9.4 Available Personnel

Available personnel, week-by-week
Name 12 13 14 15 16 17 18 19 20 21 22
Johan Sassner 40 40 40 40 40 40 40 40 40 40 40
Fredrik Hall 15 26 25 28 30 21 20 15 30 26 32
Peter Wikström 40 40 40 40 40 40 40 40 40 40 40
Martin Fredriksson 30 30 30 30 30 30 30 30 30 30 30
Lars Olofsson 40 40 40 40 40 40 40 40 40 40 40
Jim Håkansson 34 34 34 34 34 34 34 34 34 34 34
Total 233 210 209 212 214 205 204 199 214 210 216
Minus (see table 3-4) 79 1 25 97 19 1 67 1 67 7 49
Inspection 8 8 8 8 8 8 8 8 8 8 8
Total 146 201 176 107 187 196 129 190 139 195 159
Time left 2021 1875 1674 1498 1391 1204 812 683 493 354 159

Available personnel, week-by-week
Name	12	13	14	15	16	17	18	19	20	21	22
Johan Sassner	40	40	40	40	40	40	40	40	40	40	40
Fredrik Hall	15	26	25	28	30	21	20	15	30	26	32
Peter Wikström	40	40	40	40	40	40	40	40	40	40	40
Martin Fredriksson	30	30	30	30	30	30	30	30	30	30	30
Lars Olofsson	40	40	40	40	40	40	40	40	40	40	40
Jim Håkansson	34	34	34	34	34	34	34	34	34	34	34
Total	233	210	209	212	214	205	204	199	214	210	216
Minus (see table 3-4)	79	1	25	97	19	1	67	1	67	7	49
Inspection	8	8	8	8	8	8	8	8	8	8	8
Total	146	201	176	107	187	196	129	190	139	195	159
Time left	2021	1875	1674	1498	1391	1204	812	683	493	354	159

Time wasted on global activities and holidays
Activity Hours Comment
Week 12 79
Full project meeting 6 1 hour, 6 persons
Lecture 12 2 hours, 6 persons
Project summary meeting 1 1 hour, 1 person
Lecture 12 2 hours, 6 persons
Visit to Malmö 48 8 hours, 6 persons
Week 13 1
Project summary meeting 1 1 hour, 1 person
Week 14 25
Full project meeting 6 1 hour, 6 persons
Project summary meeting 1 1 hour, 1 person
Lecture 12 2 hours, 6 persons
Customer meeting 6 2 hours, 3 persons
Week 15 97
Holiday 48 8 hours, 6 persons
Holiday 48 8 hours, 6 persons
Project summary meeting 1 1 hour, 1 person
Week 16 19
Full project meeting 6 1 hour, 6 persons
Lecture 12 2 hours, 6 persons
Project summary meeting 1 1 hour, 1 person
Week 17 1
Project summary meeting 1 1 hour, 1 person
Week 18 67
Full project meeting 6 1 hour, 6 persons
Lecture 12 2 hours, 6 persons
Project summary meeting 1 1 hour, 1 person
Holiday 48 8 hours, 6 persons
Week 19 1
Project summary meeting 1 1 hour, 1 person
Week 20 67
Full project meeting 6 1 hour, 6 persons
Lecture 12 2 hours, 6 persons
Holiday 48 8 hours, 6 persons
Week 21 7
Full project meeting 6 1 hour, 6 persons
Project summary meeting 1 1 hour, 6 persons
Week 22 49
Holiday 48 8 hours, 6 persons
Project summary meeting 1 1 hour, 1 person

Time wasted on global activities and holidays
Activity	Hours	Comment
Week 12	79
Full project meeting	6	1 hour, 6 persons
Lecture	12	2 hours, 6 persons
Project summary meeting	1	1 hour, 1 person
Lecture	12	2 hours, 6 persons
Visit to Malmö	48	8 hours, 6 persons
Week 13	1
Project summary meeting	1	1 hour, 1 person
Week 14	25
Full project meeting	6	1 hour, 6 persons
Project summary meeting	1	1 hour, 1 person
Lecture	12	2 hours, 6 persons
Customer meeting	6	2 hours, 3 persons
Week 15	97
Holiday	48	8 hours, 6 persons
Holiday	48	8 hours, 6 persons
Project summary meeting	1	1 hour, 1 person
Week 16	19
Full project meeting	6	1 hour, 6 persons
Lecture	12	2 hours, 6 persons
Project summary meeting	1	1 hour, 1 person
Week 17	1
Project summary meeting	1	1 hour, 1 person
Week 18	67
Full project meeting	6	1 hour, 6 persons
Lecture	12	2 hours, 6 persons
Project summary meeting	1	1 hour, 1 person
Holiday	48	8 hours, 6 persons
Week 19	1
Project summary meeting	1	1 hour, 1 person
Week 20	67
Full project meeting	6	1 hour, 6 persons
Lecture	12	2 hours, 6 persons
Holiday	48	8 hours, 6 persons
Week 21	7
Full project meeting	6	1 hour, 6 persons
Project summary meeting	1	1 hour, 6 persons
Week 22	49
Holiday	48	8 hours, 6 persons
Project summary meeting	1	1 hour, 1 person

10 Security

The documents produced in this subproject is strictly internal and should only be available for people within the project (including the head of department). All documents that shall reach the customer must have been inspected.

11 Testing Procedure

The method for testing is described in detail in the test plan and in the Project Quality Manual [SAIDA 96-2].

12 Software Configuration Management

The method for configuration management is described in detail in the Configuration Management Plan [SAIDA 96-1].

13 Software Quality Assurance

The quality coordinator is responsible for assuring that the Project Quality Manual is implemented properly and that deliveries are of the right quality.

For further information: read the Project Quality Manual [SAIDA 96-2].

14 APPENDIX A

[SAIDA 96-1], QMQ, "Course Quality Manual " - Rev. A - University/College of Karlskrona/Ronneby, 1996.

[SAIDA 96-2], QMQ, "Project Quality Manual " - Rev. A - University/College of Karlskrona/Ronneby, 1996.

[SAIDA 96-3], QMQ, "Configuration Management Plan", Rev. A - University/College of Karlskrona/Ronneby, 1996.

[SAIDA 96-4], QMQ, "Test Procedure Plan" - Rev. A - University/College of Karlskrona/Ronneby, 1996.

[SAIDA 96-5], SAIDA, "Solution Decomposition" - Rev. A - University/College of Karlskrona/Ronneby, 1996.

[SAIDA 96-6], SAIDA, "Requriements specification" - Rev. B- University/College of Karlskrona/Ronneby, 1996.

[SAIDA 96-7], Project Manager, "Project Development Plan" - Rev. A - University/College of Karlskrona/Ronneby, 1996.

[SAIDA 96-8], SIW Team Manager, "SIW Estimations" - Rev. A - University/College of Karlskrona/Ronneby, 1996.

SIW Team Development Plan
Abstract
1 - System Overview
2 - Delivery Plan
3 - Activity Description
4 - Schedule
4.1 - HTML
4.2 - Navigator
4.3 - Development Environment
4.4 - Milestones
4.5 - Needed Resources
5 - Documents
6 - Risk Analysis
7 - Interface with External Resources
8 - Procedure for Formal Inspection
9 - Software Engineering
9.1 - Standards and Procedures
9.2 - Development Resources
9.3 - Personnel - Qualifications and Function
9.4 - Available Personnel
10 - Security
11 - Testing Procedure
12 - Software Configuration Management
13 - Software Quality Assurance
14 - APPENDIX A