A metrics suite for object oriented design - Software Engineering ...
Software design metrics
-
Upload
prasad-narasimhan -
Category
Technology
-
view
105 -
download
1
description
Transcript of Software design metrics
![Page 1: Software design metrics](https://reader035.fdocuments.us/reader035/viewer/2022081816/54c6b4a14a79595d278b4573/html5/thumbnails/1.jpg)
Software Design Metrics
Prasad Narasimhan – Technical Architect
![Page 2: Software design metrics](https://reader035.fdocuments.us/reader035/viewer/2022081816/54c6b4a14a79595d278b4573/html5/thumbnails/2.jpg)
Software Architecture Anomaly
• Architecture is based on – business & Technical assumptions– Abstracted level of information.– Major Boundaries are only defined– Attributes of the software is set based on
Customer expectations– Precise definition makes it difficult to understand
and change
![Page 3: Software design metrics](https://reader035.fdocuments.us/reader035/viewer/2022081816/54c6b4a14a79595d278b4573/html5/thumbnails/3.jpg)
Software Design Anomaly
• Design is based on – More implementation depended.– Assumptions & Risks are not validated.– Design may not capture architecture details fully– Quality Attributes are not properly captured in
design– Multiple level of diagrams represent different
information should be an expert to understand as a whole
– Business & Technical link may be split.
![Page 4: Software design metrics](https://reader035.fdocuments.us/reader035/viewer/2022081816/54c6b4a14a79595d278b4573/html5/thumbnails/4.jpg)
Software Code Anomaly
• Code is based on – Fully the implementation.– Assumptions & Risks are not fully validated.– Design representation in code is still a concern– Quality Attributes if not properly captured in
design it may not be realized in Architecture– Interpretation of designs from multiple
viewpoints is still an issue.– Business & Technical link may be split.
![Page 5: Software design metrics](https://reader035.fdocuments.us/reader035/viewer/2022081816/54c6b4a14a79595d278b4573/html5/thumbnails/5.jpg)
Software Anomaly
• Software which is created may not match Customer expectations
• The Major issues are identified during acceptance testing phase.
• No Proper Metrics to show the disconnect between Architecture -> Design -> Code.
• There are few set of tools in market which caters to few of the above issues.
![Page 6: Software design metrics](https://reader035.fdocuments.us/reader035/viewer/2022081816/54c6b4a14a79595d278b4573/html5/thumbnails/6.jpg)
Where are we headed
• MDA(Model Driven Architecture) – Realizing code from Design and architecture still need to meet end goal.
• Agile Based Development – Quick Iterative demo based approach solves the expectation mismatch , But still the integrity of Architecture -> Design -> Code is still not there.
![Page 7: Software design metrics](https://reader035.fdocuments.us/reader035/viewer/2022081816/54c6b4a14a79595d278b4573/html5/thumbnails/7.jpg)
Quick Solution
• Agile provides Management level metrics and its discussed on Stand-up meeting. If the Code , Design & Architecture metrics are available which could be discussed on Stand-up meeting. The disconnect can be quickly resolved and it enables easy refactoring of code.