Dependencies among Architectural Views Got from Software Requirements Based on a Formal Model
A system architect has software requirements and some unspecified knowledge about a problem domain (e.g., an enterprise) as source information for assessment and evaluation of possible solutions and getting the target point, a preliminary software design. The solving factor is architect’s experience...
| Main Authors: | , , , |
|---|---|
| Format: | Article |
| Language: | English |
| Published: |
Sciendo
2014-12-01
|
| Series: | Applied Computer Systems |
| Subjects: | |
| Online Access: | https://doi.org/10.1515/acss-2014-0007 |
| Summary: | A system architect has software requirements and some unspecified knowledge about a problem domain (e.g., an enterprise) as source information for assessment and evaluation of possible solutions and getting the target point, a preliminary software design. The solving factor is architect’s experience and expertise in the problem domain (“AS-IS”). A proposed approach is dedicated to assist a system architect in making an appropriate decision on the solution (“TO-BE”). It is based on a formal mathematical model, Topological Functioning Model (TFM). Compliant TFMs can be transformed into software architectural views. The paper demonstrates and discusses tracing dependency links from the requirements to and between the architectural views. |
|---|---|
| ISSN: | 2255-8691 |