Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
LLAMA Observatory Software Toy Model | ||||||||
Line: 76 to 76 | ||||||||
Teams | ||||||||
Changed: | ||||||||
< < | The work has been divided in 4 development teams of 2 persons each, plus an integration team . Each team has to be ready to negotiate the scope of its portion if needed to be able to meet the deadline (which is fixed). Currently the following teams are defined: | |||||||
> > | The work has been divided in component development teams of 2 persons each, plus an integration team . Each team has to be ready to negotiate the scope of its portion if needed to be able to meet the deadline (which is fixed). The teams role and responsibilities are the following: | |||||||
| ||||||||
Line: 84 to 84 | ||||||||
| ||||||||
Added: | ||||||||
> > | ||||||||
References | ||||||||
Added: | ||||||||
> > | ||||||||
-- Jorge Ibsen - 2014-08-11 |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
Changed: | ||||||||
< < | LLAMA Observing Software Toy Model | |||||||
> > | LLAMA Observatory Software Toy Model | |||||||
Line: 71 to 71 | ||||||||
The following two communication diagrams illustrate the two main use cases to be implemented for this project.
Proposal Lifecyle | ||||||||
Changed: | ||||||||
< < | TBD | |||||||
> > | ||||||||
Automatic Proposal Execution | ||||||||
Changed: | ||||||||
< < | TBD | |||||||
> > | ||||||||
Teams | ||||||||
Changed: | ||||||||
< < | The work has been divided in 5 teams of 2 (or 3) persons each. Each team has to be ready to negotiate the scope of its portion if needed to be able to meet the deadline (which is fixed). Currently the following teams are defined: | |||||||
> > | The work has been divided in 4 development teams of 2 persons each, plus an integration team . Each team has to be ready to negotiate the scope of its portion if needed to be able to meet the deadline (which is fixed). Currently the following teams are defined: | |||||||
| ||||||||
Changed: | ||||||||
< < |
DatabaseSchedulerInstrumentTelescopeI&T
| |||||||
> > |
| |||||||
References | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > | ||||||||
Deleted: | ||||||||
< < | WorklogFirst DaySecond DayThird DayConclusions | |||||||
-- Jorge Ibsen - 2014-08-11 \ No newline at end of file | ||||||||
Added: | ||||||||
> > |
|
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
LLAMA Observing Software Toy Model |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
LLAMA Observing Software Toy Model |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
LLAMA Observing Software Toy Model | ||||||||
Line: 6 to 6 | ||||||||
General Description | ||||||||
Changed: | ||||||||
< < | The main goal of this project is to develop a more or less complete toy model of an observing software for LLAMA (LLAMA Observing Software or LOS for short) in the three days time frame allocated for the workshop. The software development cycle will include the system integration and tests. | |||||||
> > | The main goal of this project is to develop a more or less complete LLAMA Observing Software Toy Model, LOS(TM) for short, in the three days time frame allocated for the workshop. The software development cycle will include the system integration and tests. | |||||||
Changed: | ||||||||
< < | Some of the ACS concepts illustrated with these project are: | |||||||
> > | Some of the concepts illustrated with these project are: | |||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
|
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Added: | ||||||||
> > |
LLAMA Observing Software Toy ModelGeneral DescriptionThe main goal of this project is to develop a more or less complete toy model of an observing software for LLAMA (LLAMA Observing Software or LOS for short) in the three days time frame allocated for the workshop. The software development cycle will include the system integration and tests. Some of the ACS concepts illustrated with these project are:
Legacy softwareThe following components coming from external projects are available and will be used. They are all located inside theLOS/EXTERNAL module in git:
RequirementsActorsThere are two main external actors for this software project: Astronomers and Operators.
LOS component breakdown and responsibilitiesLOS will be composed of five components: Database, Console, Scheduler, Telescope and Instrument. Each component will have the following responsibilities:
InterfacesThe initial interfaces are stored in git in LOS/ICD. They can be modified if needed but this will have to be negotiated on a case by case basis between the interested parties and will have to be noted down in a change request publicly available.Implementation LanguagesThe implementation languages are already specified taking into account the information provided in the list of participants, Although this can be modified if needed.Communication DiagramsThe following two communication diagrams illustrate the two main use cases to be implemented for this project.Proposal LifecyleTBDAutomatic Proposal ExecutionTBDTeamsThe work has been divided in 5 teams of 2 (or 3) persons each. Each team has to be ready to negotiate the scope of its portion if needed to be able to meet the deadline (which is fixed). Currently the following teams are defined:
DatabaseSchedulerInstrumentTelescopeI&T
References
WorklogFirst DaySecond DayThird DayConclusions-- Jorge Ibsen - 2014-08-11 |