0% found this document useful (0 votes)
60 views

Week 14 - Deploying A Software Architecture in A Software Development Project

This document discusses software architecture testing and deploying an architecture in a software development project. It covers building organizational buy-in, establishing an evaluation team, and creating a corporate memory. Key points include convincing management to adopt an evaluation unit, identifying and training qualified evaluators, and maintaining a repository of past evaluation reports, risks, scenarios and other artifacts. The overall aim is to institutionalize the evaluation process.

Uploaded by

Arvin Kovan
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
60 views

Week 14 - Deploying A Software Architecture in A Software Development Project

This document discusses software architecture testing and deploying an architecture in a software development project. It covers building organizational buy-in, establishing an evaluation team, and creating a corporate memory. Key points include convincing management to adopt an evaluation unit, identifying and training qualified evaluators, and maintaining a repository of past evaluation reports, risks, scenarios and other artifacts. The overall aim is to institutionalize the evaluation process.

Uploaded by

Arvin Kovan
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 17

Software Architecture Testing

CT059-3-2

Deploying a software architecture in


a software development project
Topic & Structure of the lesson

• Building organizational buy-in


• Building a pool of evaluators
• Establishing a corporate memory

CT059-3.5-3 Software Architecture Testing Deploying a software architecture in a software Slide 2 (out of 14)
Learning Outcomes

• By the end of this lecture, YOU should be


able to :
– Prepare a report to convince the organisation
to build an architecture evaluation unit.
– Build a team to evaluate the architecture
– Establish an architectural evaluation repository

CT059-3.5-3 Software Architecture Testing Deploying a software architecture in a software Slide 3 (out of 14)
Key Terms you must be able to use

• If you have mastered this topic, you should


be able to use the following terms correctly
in your assignments and exams:
– Organisational buy-in
– Evaluators
– Cost and benefit
– Reusable artifact

CT059-3.5-3 Software Architecture Testing Deploying a software architecture in a software Slide 4 (out of 14)
Building organizational buy-in
• Should convince the management to adapt an
architectural evaluation unit
• Two strategies
– Top-down
• Involves finding a champion within management who
can fund the unit and defend the budget
– Bottom-up
• Find a project manager who is willing to host an
architectural evaluation
• Keep record for the future reference.
• Grow the group informally by finding qualified voluteers
CT059-3.5-3 Software Architecture Testing Deploying a software architecture in a software Slide 5 (out of 14)
Building a pool of evaluators
• Identify and target qualified people
• The team must perceived as independent in
their duties
• Must be an expert
• Start with the best (a pool of best architects)
• Mentoring process to bring new evaluators

CT059-3.5-3 Software Architecture Testing Deploying a software architecture in a software Slide 6 (out of 14)
How to Train New Members?

• On first evaluation assign them a


timekeeper, scenario, scribe, process
observer and questioner
• Have them to write the final report that
describe the process
• Following evaluations have them to
facilitate the processes

CT059-3.5-3 Software Architecture Testing Deploying a software architecture in a software Slide 7 (out of 14)
Establishing a corporate
memory
• Have a repository to make continues
success
• Repository is called as corporate memory
• It consists of
– Costs and benefit data
– Method guidance
– Reusable artifacts

CT059-3.5-3 Software Architecture Testing Deploying a software architecture in a software Slide 8 (out of 14)
Example: An ATAM End-of-
Exercise Participant’s Survey

CT059-3.5-3 Software Architecture Testing Deploying a software architecture in a software Slide 9 (out of 14)
Follow-up Survey to Gauge Project
Impacts of an Architecture Evaluation

CT059-3.5-3 Software Architecture Testing Deploying a software architecture in a software Slide 10 (out of 14)
Follow-up Survey to Gauge Organisational
Impacts of an Architecture Evaluation

CT059-3.5-3 Software Architecture Testing Deploying a software architecture in a software Slide 11 (out of 14)
Method Guidance

• Storing new heuristics, new steps, new


advice to give team member, new ideas for
better evaluation
• Create a process model for each evaluation
exercise
• Create a baseline of methodological
authority

CT059-3.5-3 Software Architecture Testing Deploying a software architecture in a software Slide 12 (out of 14)
Reusable Artifacts

• Evaluation reports are very important for


future use.
• Types of repositories are:
– Final reports
– Risks
– Scenarios
– Exemplary documentation
– Quality attribute characterisation
– ABAS
– Other artifacts
CT059-3.5-3 Software Architecture Testing Deploying a software architecture in a software Slide 13 (out of 14)
Reference
Clements, Kazman & Klein – Evaluating Software Architectures –– Addison-Wesley.

CT059-3.5-3 Software Architecture Testing Deploying a software architecture in a software Slide 14 (out of 14)
Summary of Main Teaching Points

• Building organizational buy-in


• Building a pool of evaluators
• Establishing a corporate memory

CT059-3.5-3 Software Architecture Testing Deploying a software architecture in a software Slide 13 (of 15)
Question and Answer Session

Q&A

CT059-3.5-3 Software Architecture Testing Deploying a software architecture in a software Slide 14 (of 15)
Next Session

• Project Close-out
• Formalising project completion
• Meeting Project success criteria
• Identifying lesson learned

CT059-3.5-3 Software Architecture Testing Deploying a software architecture in a software Slide 15 (of 15)

You might also like