The specification of the software architectural description of the FMSoS was conceived as a joint work between SofTware ARchitecture Team (START/ICMC) at University of São Paulo and ArchWare (IRISA) at University of South Britanny, in France.
During this stage, the product team defines the specifications of the implementation software, developed in later stages.
Details of the S-WPIA calculation and the specifications of the S-WPIA software applications are described in Hikishima et al. (submitted to Earth, Planets and Space).
This stage accomplishes the transformation task, turning the specifications of the trading/investment system into software and hardware, where the design of the trading system from previous stages becomes the specification requirements for the software design.
We illustrate this process by means of a case study: the specification of a software architecture for intelligent agents which supports a fault tolerant anonymous interaction protocol.
There is a well documented problem in the software engineering field relating to a structural mismatch between the specification of requirements for software systems and the specification of object-oriented software systems.
The main reason for using scenarios in the specification of software quality requirements is that they can provide the specific contexts in which designs of a software system can be evaluated.
This chapter discusses the concept of scenarios and the uses of scenarios in the specification of software modifiability requirements.
Many of the proposed formalisms, such as Petri nets or process algebras, were originally created by the computational community for the specification of software systems, where the final system has to comply to the model.
The envisaged approach extends previous work by the authors on the use of coalgebraic models for the specification of software connectors.
