AstroImage/SRS - Revision history

Coralie.Rachex at 09:44, 6 April 2016

2016-04-06T09:44:36Z

Show changes

Coralie.Rachex: /* 3.Specific requirements, covering functional, non-functional and interface requirements */

2016-03-06T16:20:31Z

3.Specific requirements, covering functional, non-functional and interface requirements

Show changes

Coralie.Rachex: /* 2.4 General constraints */

2016-03-05T21:20:24Z

2.4 General constraints

← Older revision		Revision as of 21:20, 5 March 2016
Line 85:		Line 85:
	* The software must be developed in Python, with Kivy for the UI.		* The software must be developed in Python, with Kivy for the UI.
	* Each set of input images are images RAW or FITS		* Each set of input images are images RAW or FITS
	* ~~output~~ images are TIFF or FITS		* Output images are TIFF or FITS

	==2.5 Assumptions and dependencies==		==2.5 Assumptions and dependencies==

Coralie.Rachex at 21:15, 5 March 2016

2016-03-05T21:15:44Z

← Older revision		Revision as of 21:15, 5 March 2016
Line 90:		Line 90:

	This project haven't any assumptions and dependencies		This project haven't any assumptions and dependencies


	=3.Specific requirements, covering functional, non-functional and interface requirements=		=3.Specific requirements, covering functional, non-functional and interface requirements=
Line 483:		Line 484:
	* '''Maintainability''' : The system is being developed in Python whith an object oriented programming, so it shall be easy to maintain.		* '''Maintainability''' : The system is being developed in Python whith an object oriented programming, so it shall be easy to maintain.
	* '''Reliability''' : Specify the factors required to establish the required reliability of the software system at time of delivery.		* '''Reliability''' : Specify the factors required to establish the required reliability of the software system at time of delivery.


	=4. Product evolution=		=4. Product evolution=

	=5. Appendices=		=5. Appendices=

	=6. Index=		=6. Index=

Coralie.Rachex: /* 2. General description */

2016-03-05T21:15:06Z

2. General description

← Older revision		Revision as of 21:15, 5 March 2016
Line 72:		Line 72:

	The goal of this project is to develop a processing chain of image stemming from spotting scope (post-processing software).		The goal of this project is to develop a processing chain of image stemming from spotting scope (post-processing software).


	==2.2 Product functions==		==2.2 Product functions==

	This product must be able to realizing the entire processing chain of the astronomical images. These functions will be retailed in the corresponding section.		This product must be able to realizing the entire processing chain of the astronomical images. These functions will be retailed in the corresponding section.


	==2.3 User characteristics==		==2.3 User characteristics==

	Users of this product are amateur astronomers, who have some knowledge in astronomical image processing and computing. But these users aren't experts in these two domains.		Users of this product are amateur astronomers, who have some knowledge in astronomical image processing and computing. But these users aren't experts in these two domains.


	==2.4 General constraints==		==2.4 General constraints==
Line 89:		Line 86:
	* Each set of input images are images RAW or FITS		* Each set of input images are images RAW or FITS
	* output images are TIFF or FITS		* output images are TIFF or FITS


	==2.5 Assumptions and dependencies==		==2.5 Assumptions and dependencies==

Coralie.Rachex: /* 2. General description */

2016-03-05T21:14:47Z

2. General description

← Older revision		Revision as of 21:14, 5 March 2016
Line 71:		Line 71:
	==2.1 Product perspective==		==2.1 Product perspective==

	The goal of this project is ~~TODO~~		The goal of this project is to develop a processing chain of image stemming from spotting scope (post-processing software).


	==2.2 Product functions==		==2.2 Product functions==

			This product must be able to realizing the entire processing chain of the astronomical images. These functions will be retailed in the corresponding section.
	This product must be able to TODO


Line 86:		Line 86:
	==2.4 General constraints==		==2.4 General constraints==

			* The software must be developed in Python, with Kivy for the UI.
	TODO
			* Each set of input images are images RAW or FITS
			* output images are TIFF or FITS


	==2.5 Assumptions and dependencies==		==2.5 Assumptions and dependencies==

Coralie.Rachex: /* 3.6 emergent system properties and quality characteristics */

2016-03-05T20:56:43Z

3.6 emergent system properties and quality characteristics

← Older revision		Revision as of 20:56, 5 March 2016
Line 480:		Line 480:
	There aren't factors in the client's requirement that may restrict the choices of a designer. But there are some standars that must be followed; standard that shares a lot of image processing software (whites balance, color palettes, histogram, etc.). Respect these standard allows this software to be easily taken over by the user.		There aren't factors in the client's requirement that may restrict the choices of a designer. But there are some standars that must be followed; standard that shares a lot of image processing software (whites balance, color palettes, histogram, etc.). Respect these standard allows this software to be easily taken over by the user.

	==3.6 ~~emergent~~ system properties and quality characteristics ==		==3.6 Emergent system properties and quality characteristics ==

			* '''Maintainability''' : The system is being developed in Python whith an object oriented programming, so it shall be easy to maintain.
			* '''Reliability''' : Specify the factors required to establish the required reliability of the software system at time of delivery.

	=4. Product evolution=		=4. Product evolution=

Coralie.Rachex: /* 3.4 Logical database requirements */

2016-03-05T20:47:09Z

3.4 Logical database requirements

← Older revision		Revision as of 20:47, 5 March 2016
Line 474:		Line 474:
	==3.4 Logical database requirements ==		==3.4 Logical database requirements ==

			The system doesn't use a database.

	==3.5 Design constraints ==		==3.5 Design constraints ==

Coralie.Rachex: /* 3.5 Design constraints */

2016-03-05T20:45:03Z

3.5 Design constraints

← Older revision		Revision as of 20:45, 5 March 2016
Line 477:		Line 477:
	==3.5 Design constraints ==		==3.5 Design constraints ==

			There aren't factors in the client's requirement that may restrict the choices of a designer. But there are some standars that must be followed; standard that shares a lot of image processing software (whites balance, color palettes, histogram, etc.). Respect these standard allows this software to be easily taken over by the user.

	==3.6 emergent system properties and quality characteristics ==		==3.6 emergent system properties and quality characteristics ==

Coralie.Rachex: /* 3.3 Performance requirements */

2016-03-05T20:35:54Z

3.3 Performance requirements

← Older revision		Revision as of 20:35, 5 March 2016
Line 466:		Line 466:
	Performance requirements define quality and security rather than response time for system functionality. Indeed, computation times required for the algorithms of astronomical image processing are long. It's more important to have a software working correctly, that a software quickly working. The optimization isn't our main purpose.		Performance requirements define quality and security rather than response time for system functionality. Indeed, computation times required for the algorithms of astronomical image processing are long. It's more important to have a software working correctly, that a software quickly working. The optimization isn't our main purpose.

	* '''User ~~Satisfaction~~''' : The software is such that it stands up to the user expectations.		* '''User satisfaction''' : The software is such that it stands up to the user expectations.
	* '''User friendliness''' : The sofware must be easy to learn and undersand for a not expert user.		* '''User friendliness''' : The sofware must be easy to learn and undersand for a not expert user.
			* '''Image quality''' : The sofware has to keep the initial image quality.
	* '''Error ~~Handling~~''' : Response to user errors and undesired situations has been taken care of to ensure that the system operates without halting.		* '''Error handling''' : Response to user errors and undesired situations has been taken care of to ensure that the system operates without halting.
	* '''Safety and robustness''' : The software is able to avoid or tackle disastrous action. It safeguards against undesired events, without human intervention.		* '''Safety and robustness''' : The software is able to avoid or tackle disastrous action. It safeguards against undesired events, without human intervention.