1 / 9

Practical Software and Systems Measurement Objective Information for Decision Makers

Applying Measurement to Software and System Architecture March 14, 2012 Alejandro Bianchi alejandro.bianchi@liveware.com.ar. Practical Software and Systems Measurement Objective Information for Decision Makers. Workshop´s Agenda. Intros and expectations

raanan
Télécharger la présentation

Practical Software and Systems Measurement Objective Information for Decision Makers

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Applying Measurement to Software and System Architecture March 14, 2012 Alejandro Bianchi alejandro.bianchi@liveware.com.ar Practical Software and SystemsMeasurement Objective Information for Decision Makers

  2. Workshop´s Agenda • Intros and expectations • Objectives of the Workshop • Work done • Software Architecture Measurement Framework: Discussion • Introducing Systems Architecture Measurements • Future Work

  3. Objectives of the WorkshopJuly, 2011 • Identify measurement categories and specific measures for SA Design • Write measures specifications for candidate measures • Outline a white paper about SA Design Measurement

  4. Objectives of this Workshop • Present work done so far • Analyze and validate the draft version of SA Measurement Framework • Integrate System Architecture • Coordinate next steps and work New one

  5. Integration of SA with Software life Cycle ADD, 4+1, Others Methods Patterns, Tactics, Reference Architecture and Standards Architectural Synthesis Architectural Documentation. (Views and Beyond) QAW Method Architectural Knowledge Architectural Analysis Architectural Evaluation Architectural implementation Architectural Evolution Global Functional Req. Quality attributes Architectural Impact Analysis Software Life Cycles Control of Integrity of Architectural Documentation (checklist) Analysis of Architectural Decisions. (ATAM) Technical and Business Restrictions Maintain Conformance with Architectural decisions Adapted of Ali Babar, 2009

  6. Last July Workshop: Conclusions • The seven information categories of PSM are enough to measure the Software Architecture Design • We identified: • 14 concerns and/or Information needs about Software Architecture Design and Software Development Architecture Centric • 27 candidate measures

  7. Work done so far • Refinement of information needs • Definition of new measurable concepts for Software Architecture, (14 new concepts) • Definition of Candidate Measurements, (55 measures) • Synthesis in a first draft version of the Software Architecture Measurement Framework • Specification of couple candidate measurement

  8. Discussion • Are there more information needs that should be considered? • Are the new measurable concepts correct?. Do we need someone else? • Are the candidate measurements adequate and/or relevant? • What do we need modify to System Architecture?

  9. Future work • Adjusting SA Measurement Framework according this revision • Work on the integration of Software and System • Specify a set of Candidate Measurement: • Software Architecture Estimation • Technical Debt in agile context • SA Completeness and Correctness • Planning this work to present results in PSM Conference, July 2012

More Related