Well that is my application of an Architecture Design Chart Ginger. Meaning that if you look at the FDA guidance document and IEC 62304 the architecture should start at the highest system level describing things like the hardware requirements, hardware interfaces, components, connectivity, and then get down into the architecture of the software itself, i.e. modules, structure, content, functional units, etc.. There are different ways the document can be put together and while areas like the FDA guidance are pretty general, that is the way I have structured an architecture document. In fact, I would argue the architecture document is one of the first created because if I can use a fair analogy the architecture document is the blueprints of a house, the SRS is the outside/look of the house, and the SDS is all the components, wood, and wiring of the house. The architecture is just that, an architecture document describing what the entire software application is including external components like connecting to other devices through bluetooth or Wifi and different modules in the software itself.
------------------------------
Richard Vincins RAC
Vice President Global Regulatory Affairs
------------------------------
Original Message:
Sent: 12-Jan-2019 07:30
From: Ginger Cantor
Subject: Software Architecture Chart
Hello Richard,
The software architecture document could refer to external systems like printers, monitors etc, but that is more of a System architecture diagram, and the software architecture devolves from that?
------------------------------
Ginger Cantor, MBA, RAC
Founder/Principal Consultant
Centaur Consulting LLC
River Falls, Wisconsin 54022 USA
715-307-1850
centaurconsultingllc@gmail.com
Original Message:
Sent: 11-Jan-2019 09:45
From: Richard Vincins
Subject: Software Architecture Chart
I do not have anything that could be shared, but assuming you are talking about Software Architecture Design Chart this can be done in a number of ways. There is no one way for architecture diagram/design chart though I have found that a combination of graphical such as charts or diagram and text explaining things works pretty well. My suggestion is to review IEEE standards and there are some examples out there in the public domain. There is just so many varieties of software that there is not one way to create an architecture diagram, so looking at some different examples in public domain might help give some ideas. Just another note, make sure the architecture design chart/diagram takes into consideration external items to the system, i.e. Wifi, printers, monitors, hardware, and also make some references to cybersecurity document(s).
------------------------------
Richard Vincins RAC
Vice President Global Regulatory Affairs
Original Message:
Sent: 09-Jan-2019 15:15
From: Anonymous Member
Subject: Software Architecture Chart
This message was posted by a user wishing to remain anonymous
Hi everyone,
Does anyone have a sample architecture design chart that clearly shows the functional relationships between different functional units? I would appreciate some guidance on how to structure this. Thank you.