1. Knowledge Management Issues in software Architecture Documentation Rambabu D, Dr T.V. Prabhakar Indian Institute of Technology Kanpur India

3. Bad Architecture

6. Functional Requirements Quality Requirements Design Constraints Architecture Knowledge C4 C6 C3 C2 C1 C4 Architecture Documents Architecture System Architect Designs Stakeholders Meets Concerns

7. Query Editor Ontology Viewer Metadata Annotator SWT Eclipse IDE Result Table Viewer Ontology Requestor Search Module Query Component Document Repository Annotated Files Repository Ontology Persistent Component Arch Property Object Query, Result Set Query, URL JFace

10. The Concept of Viewpoints End-User Project Manager Programmer IEEE Standard 1471-2000 recommends use of “viewpoints” as conventional practice.

11. ISO/ITU Standard Viewpoints for IT Systems X.900 Open Distributed Processing SAAM Copyright 2001 iCMG Private Limited Information Viewpoint Computational Viewpoint Engineering Viewpoint Technology Viewpoint Enterprise Viewpoint

12. Concept map of Software Architecture Documentation concepts

13. Framework of the proposed tool

14. ArchAware- Basic View Draw2D Synchronous communication GEF Synchronize requirements data Eclipse Meta data At the top level, · Architecture metadata · Graphical editor

15. Dependencies in Arch Aware

16. Module View of Arch Aware

17. The Component and Connector View of Arch Aware

18. Screenshots of the plug-in

22. On Archiving Architecture Documents ` View Types Styles Memory Physical Network Connectivity Domain Knowledge Quality Attributed scenarios Conceptual Terms & Usage Groups Tactics Service level agreements Failure cases Correctness Technical components Success Factors Non Functional Requirements Patterms Gough, POSA Non Software Negative consequences Structural Properties Architectural styles Information Exchange Best Practices Architecture patterns Antipatterns Tactics Domain Perspective Problem Domain and Concepts Scenarios handled Architecture Properties Annotation Architecture documents Annotated documents Other Issues Technology Components Runtime Issues Quality Requirements Search

36. On Archiving Architecture Documents Case Study: Online Cricket Broadcasting System Module View

37. On Archiving Architecture Documents Case Study: Online Cricket Broadcasting System C&C View

38. < ?xml version=’1.0’? > <!DOCTYPE OCBS SYSTEM &quot;ocbs.dtd&quot;> <ArchitectureDescription> <title>CricketBroadcastingSystem</title> <author>Rambabu D</author> <ArchitectureProperties> <ProblemDomain> Designing an online cricket broadcasting system enabling flawless integration with TV, Mobile, Internet </ProblemDomain> <Scenarios> <PerfScenario>FasterSearch </PerfScenario> <PerfScenario>Rendering </PerfScenario> <ModScenario>NoGlitch</ModScenario> <SecScenario>AccessControl</SecScenario> </Scenarios> <Technology> <component>Oracle</component> <component>DSMS</component> <component>Webserver</component> </Technology> <InformationExchange> <Memory>parameter passing</Memory> <Physical>Stream via pipe</Physical> </InformationExchange> <ArchitecturePattern> <pattern>MVC</pattern> <pattern>ParallelPipeline</pattern> </ArchitecturePattern> XML Annotation for the OCBS arch document

39. <!ELEMENT ArchitectureDescription(title,author, ArchitectureProperties)> <!ELEMENT ArchitectureProperties (ProblemDomain, Scenarios,Technology,InformationExchange, ArchitecturePattern, Style, Tactics, QualityRequirements, MISC)> <!ELEMENT Scenarios (ModScenario*, PerfScenario*, SecScenario*, TestScenario*, UseScenario*)> <!ELEMENT Technology(Component+)> <!ELEMENT InformationExchange (Memory+, PhysicalMedium+)> <!ELEMENT ArchitecturePattern (pattern*, Antipattern*)> <!ELEMENT Styles (CnCView+, ModuleView+, AllocationView+)> <!ELEMENT Tactics (FaultDetection*, FaultRecovery*, LocalizeChanges*, ResistingAttack*, BindingTime*, ManageI/O*> <!ELEMENT QualityRequirements( Performance*, Availability*,Modifiability*,Usability*)> <!ELEMENTMISC(Standard*,Version*,Success*)> <!ELEMENT ModScenario (#PCDATA)> <!ELEMENT PerfScenario (#PCDATA)> <!ELEMENT SecScenario (#PCDATA)> <!ELEMENT TestScenario (#PCDATA)> <!ELEMENT UseScenario (#PCDATA)> <!ELEMENT Component (#PCDATA)> <!ELEMENT Memory (#PCDATA)> <!ELEMENT PhysicalMedium (#PCDATA)> <!ELEMENTPattern (#PCDATA)> <!ELEMENT AntiPattern (#PCDATA)> <!ELEMENT CnCView (#PCDATA)> <!ELEMENT ModuleView (#PCDATA)> <!ELEMENT AllocationView (#PCDATA)> <!ELEMENT FaultDetection (#PCDATA)> <!ELEMENT FaultRecovery (#PCDATA)> <!ELEMENT LocalizeChanges (#PCDATA)> Corresponding DTD for the annotation

42. A global Picture

43. Problem domain

45. Patterns

46. Structural properties

47. Architecture Tactics

48. Scenarios handled

49. Information exchange between the components

53. Thank you for your attention Questions? On Archiving Architecture Documents