ticofab/caterina_quality_attributes_phases_answers.csv

## caterina_quality_attributes_phases_answers.csv

          
            Phase
            Attribute
            Answer(s)

            
              Design
              Availability
              Sources are the webservices mentioned above. I need to build services to fetch data from both.

            
              
              Successfulness
              Final outcome should be a reliable prediction issued when a new event comes up.

            
              Management
              Availability
              Data will be stored in a cloud persistence layer.

            
              
              Recoverability
              This is delegated to the cloud service provider.

            
              
              Portability
              Not immediate like copying a file. If this need arises I will need to create a parser to extract data.

            
              
              Security
              This is delegated to the cloud service provider.

            
              
              Well-documented
              A requirement will be to create proper documentation. These posts move in that direction!

            
              Collection
              Availability
              In this I am entirely dependent on the sources. If something breaks I will know because sources can only be polled.

            
              
              Completeness
              Of all the available data I don't need all. Requirements will specify what is needed from either source.

            
              
              Consent
              This data is publicy available at the moment of writing.

            
              
              Cost
              Sources are free of cost at the moment of writing.

            
              
              Monitorability
              The source APIs function in poll-style. Requirements will contain a simple way to raise an alert.

            
              
              Quantity
              It is unclear if the data will be enough but I believe it should be.

            
              
              Reliability
              This is delegated to the sources.

            
              
              Size
              TODO

            
              
              Timeliness
              This is delegated to the data sources. Hopefully yes.

            
              Processing
              Aggregability
              The coin symbols should be consistent across sources. There needs to be a tolerant conversion table anyway.

            
              
              Cost
              All in all it should be an affordable budget.

            
              
              Efficiency
              Probably some services can only be started when needed. This is to see.

            
              
              Monitorability
              Logging and alerts (maybe the same as for the sources failure) will be in place.

            
              
              Well-documented
              Requirement to document everything well.

            
              Dissemination
              Timeliness
              The previon should be fired as soon as a new event is detected.

            
              Closing
              Archivability
              Services will be easy to stop. To take offline all data it should be parsed into some file first.

            
              
              Forgettability
              Yes.

            
              
              Well-documented
              A requirement should be about documentation.
Phase	Attribute	Answer(s)
Design	Availability	Sources are the webservices mentioned above. I need to build services to fetch data from both.
	Successfulness	Final outcome should be a reliable prediction issued when a new event comes up.
Management	Availability	Data will be stored in a cloud persistence layer.
	Recoverability	This is delegated to the cloud service provider.
	Portability	Not immediate like copying a file. If this need arises I will need to create a parser to extract data.
	Security	This is delegated to the cloud service provider.
	Well-documented	A requirement will be to create proper documentation. These posts move in that direction!
Collection	Availability	In this I am entirely dependent on the sources. If something breaks I will know because sources can only be polled.
	Completeness	Of all the available data I don't need all. Requirements will specify what is needed from either source.
	Consent	This data is publicy available at the moment of writing.
	Cost	Sources are free of cost at the moment of writing.
	Monitorability	The source APIs function in poll-style. Requirements will contain a simple way to raise an alert.
	Quantity	It is unclear if the data will be enough but I believe it should be.
	Reliability	This is delegated to the sources.
	Size	TODO
	Timeliness	This is delegated to the data sources. Hopefully yes.
Processing	Aggregability	The coin symbols should be consistent across sources. There needs to be a tolerant conversion table anyway.
	Cost	All in all it should be an affordable budget.
	Efficiency	Probably some services can only be started when needed. This is to see.
	Monitorability	Logging and alerts (maybe the same as for the sources failure) will be in place.
	Well-documented	Requirement to document everything well.
Dissemination	Timeliness	The previon should be fired as soon as a new event is detected.
Closing	Archivability	Services will be easy to stop. To take offline all data it should be parsed into some file first.
	Forgettability	Yes.
	Well-documented	A requirement should be about documentation.