Phase 0

Index:

• Details on phase 0
• Activity 1: Project models, resources, legal rights and economy.
• Activity 2: Communication & Documentation models, skills and services.
• Activity 3: Brainstorming and Needfinding; approaching the requirements.
• Activity 4: Wireless communications.
• Activity 5: Distributed control systems.
• Who is responsible in the subgroups?

Details on phase 0: Product definition

Period: October 29 - end of December.

Main objective: To understand the problem to solve, to establish contacts with the people in-volved,to define and establish resources for the project, and prestudy of critical technology.

Result: The result of this phase will be described in a document called Product specification.This includes parts that defines aspects of the project organization and requirements on the actual product to be developed.

Activities part of Phase 0: The work in this phase will be divided into a number of activities;apreliminary list including allocation of number of persons is given here.

Top

TM1 is the student project leader for the project during this phase. Close contacts will be maintained with the related activities of the other projects. Team 1 is responsible for:

• developing organisational plans for common activities in this phase (meetings etc.)
• defining the product development model we should use during our project
• defining the quality assurance program (ISO9000 or other standards or common used mod-els)
• investigating legal right aspects for this project
• defining project resources and constraints/aims with respect to project finances
• making an outline for the next phase

Top

Close contacts will be maintained with the related activities of the other projects. Team 2 is re-sponsible for:

• choosing/defining standards and tools for communication and documentation
• choosing computer platform and programs and introduce them to the rest of the team.
• web page management (updating)
• establishing good contacts with our cooperation partner and the Stanford team (if one)
• the development of a good social atmosphere!
• forming the project room, to fulfil the functions needed for the rest of the project time
• the arrangement of visits to companies (e.g. consultancy companies Frontec and Sigma).

Top

Team 3 is responsible for:

• beginning to formulate specifications for our project/product
• developing an understanding of the market, customers and the end users for the product
• the search for similar systems on the market.
• looking for OEM manufactures of subsystems or other important partners

Team three should arrange a brainstorming session. The focus is to find the problems we are going to solve within the project. We need also to understand the context, framework, interfaces and environment for our project/product.

Top

Team 4 is responsible for:

• collecting basic material on this technology. It is important to develop a basic understandingwithin the project team.
• literature search on specific technologies.
• initiating discussions on basic properties, merits and drawbacks, of wireless technology
• identifying other alternative techniques

Top

Team 5 is responsible for:

• collecting basic material and understanding for distributed control systems; what are the problems, which design issues are important, which techniques are used?! Again, it is important to develop a basic understanding within the project team.
• collecting basic material about the ADTRANZ specific distributed control systems; ver-sions, base platform, tools and applications.

Top

Activity 1: Project models, resources, legal rights and economy.

 

Jonas Wedin and Jens Svensson

 

Activity 2: Communication & Documentation models, skills and services.

 

Mattias Linjeberg and Tomas Jansson

 

Activity 3: Brainstorming and Needfinding; approaching the requirements.

 

Anna Synnergren and Johan Ohlén

 

Activity 4: Wireless communications.

 

Magnus Uhlin, Måns Telander and Alexander Gordon

 

Activity 5: Distributed control systems.

 

Jonas Hultman and Magnus Wessberg

Top