Software architecture design process.

This part is in charge of providing a design for the software that implements and can be verified against the requirements. In this way every requirement should be covered.

• Art1- Every team in charge of this part will be composed of 4 members.

• Art2- The team will reveive a document containing all the functional and the nonfucntional requirements, which should be covered by the architecture

• Art3- Every decisión taken at this moment for a specific requirement (functional or non-functional) shoud be documented in a specific .docx document.

3.1- The name of that document should follow the next rules:
3.1.1- The first three letters should be ARC.
3.1.2- Followed by a hyphen splitting.
3.1.3- After that the ID of the requirement that can be solved with that
3.1.4- If a versioning is needed and changes are made in that document, both are saved and the last one gets added a point and a incremental number( .1, .2, .3, .4…)

• Art4- Every decisión should be taken in meetings, taken into account that the different parts of the team has to expose why that decisión has been taken and why they think its the optiimal one.

• Art5- At the end of the process, the implementer should deliver a documentation explaining why the architecture designed fulfils these characteristics:

o Traceability to the requirements of the software item.
o External consistency with the requirements of the software item.
o Internal consistency between the software components.
o Appropriateness of design methods and standards used.
o Feasibility of detailed design.
o Feasibility of operation and maintenance.

• Art6- Finally speciled diagrams and documentation is given to the software design process group.