Design Capstone Project
Design Capstone Project CS 4911
Popular in Course
Popular in ComputerScienence
This 0 page Class Notes was uploaded by Alayna Veum on Monday November 2, 2015. The Class Notes belongs to CS 4911 at Georgia Institute of Technology - Main Campus taught by Staff in Fall. Since its upload, it has received 15 views. For similar materials see /class/234163/cs-4911-georgia-institute-of-technology-main-campus in ComputerScienence at Georgia Institute of Technology - Main Campus.
Reviews for Design Capstone Project
Report this Material
What is Karma?
Karma is the currency of StudySoup.
You can buy or earn more Karma at anytime and redeem it for class notes, study guides, flashcards, and more!
Date Created: 11/02/15
Design Review Checklist l N 6 7 8 Are the following attributes welldefined for each design entity a Identi cation unique name Type describing what kind of design entity it is Purpose describing why it was introduced in terms of the requirements Function summarizing what the component does Dependencies possibly none describing the requires or uses relationship f Interface provided by the design entity g Processing including autonomous activities h Data information hidden inside Is the relationship to the requirements clearly motivated Is it clear why the proposed architecture realizes the requirements Is the software architecture as simple as possible but no simpler o No more than 7 looselycoupled coherent highlevel components 0 Lowerlevel components possibly clustered into highlevel components hierarchy 0 Using standardized components 0 Is deviation from intuitively obvious solution motivated Is the architecture complete 0 Are all requirements covered 0 Trace some critical requirements through the architecture e g via use cases Are the component descriptions sufficiently precise 0 Do they allow independent construction 0 Are interfaces and external functionality of the highlevel components described in sufficient detail 0 Interface details Routine kind name parameters and their types return type pre and postcondition usage protocol wrt other routines File name format permissions Socket number and protocol Shared variables synchronization primitives locks 0 Have features of the target programming language been used where appropriate 0 Have implementation details been avoided No details of internal classes Are the relationships between the components explicitly documented 0 Preferably use a diagram Is the proposed solution realizable 0 Can the components be implemented or bought and then integrated together 0 Possibly introduce a second layer of decomposition to get a better grip on realizability Are all revelevant architectural Views documented oaoc
Are you sure you want to buy this material for
You're already Subscribed!
Looks like you've already subscribed to StudySoup, you won't need to purchase another subscription to get this material. To access this material simply click 'View Full Document'