System Architecture Review Checklist Version 1.

0
System/LRU Name: System Architecture Document: Document Release Version: Reviewer: Standards Used:

Date: Review Date:

Checklist Item
General Format

Standards Conformance

Yes/ No Yes Yes Yes

Comments

1. Is the document under configuration control? 2. Is a revision history provided and accurate? 3. Does the title page include program name, document release date, document identification and revision level? 4. Are the references in the table of contents completed and correct? 5. Are terms and acronyms defined? 6. Does the referenced document section include all documents referenced in the text?
Architecture Components

Yes Yes Yes

7. Is the architecture organized such that the components are divided into different levels or groups/subsystems of components? 8. Are the hardware and software items uniquely identified? 9. Are the hardware and software items part of a database? 10. Does the architecture define the static relationship of the components? 11. For each component, are the corresponding system design requirements identified? 12. Is the purpose of each component provided?

Yes

Yes Yes Yes Yes

Yes

Checklist Item 13. Is the status of each (new, re-used, reengineered) component defined, including the version, identification and references? 14. Are the software and hardware qualification conditions identified? 15. Are the mechanical and electrical characteristics of the system identified? 16. Are the software partitioning, memory and throughput margins identified? 17. For each computer hardware resource identified, are the following resources defined: 18. Computer processor including name, model, speed, capacity, set of instructions, applicable compilers, standard interfaces, interrupt capabilities, physical features? 19. Memory size, type, speed, configuration? 20. I/O devices type, speed, capacity? 21. Communications/network equipment such as modems, cards, hubs, gateways, transfer rates, topologies?
Concept of execution

Standards Conformance

Yes/ No No

Comments No aplica, no se considera el trabajo con piezas de software

Yes No Yes Yes

Yes

Yes Yes No

22. Is the dynamic relationship of the components defined? 23. Is the flow of execution control defined? 24. Is the data flow provided? 25. Are the state transition diagrams (use cases, state charts, message sequence charts) defined? 26. Are the timing and sequencing diagrams provided? 27. Are the priorities among components defined? 28. Does the concept of execution include handling of interrupts? 29. Does the concept of execution include exception handling? 30. Does the concept of execution include dynamic allocation/deallocation? 31. Does the concept of execution include concurrent execution, tasking, and processes?

Yes Yes Yes No

No Yes No No No Yes

The current review status is: --Closed as acceptable with no action items.

---

Closed as acceptable with action items. Open pending completion of defined action items.

Action items (excluding: PRs and their status): Accept Assigned Item # Review Comment Action(s) Taken Yes/No to -

System/LRU Name: System/LRU Name: System Architecture Document: Document Version: Reviewer: Standards Used: Release Date: Review Date:

Enea is registered trademark of ENEA A.B. 2007 Enea. All Rights Reserved. For more information please visit www.enea.com

Corporate Headquarters P.O. Box 1033 Skalholtsgatan 9 SE-164 21 Kista, Sweden Phone: +46 (0)8 507 140 00 Email: info@enea.se Web : www.enea.com US Headquarters 25 South Arizona Place Chandler, AZ 85225 Phone: 480-753-9200 Toll-free: 866-844-7867 Email: info@enea.com Web: www.enea.com Asian Headquarters 1-4-2 Kanda Ogawa-machi, Chiyoda-ku Tokyo, Japan 101-0052 Phone: +81 3 5207 6167 E-mail: osesales_jp@enea.se Web: www.enea.com

Embedded for Leaders