Sig A&D - Documentation And Communication

SIG Architecture & Design Documentation and Communication of a Software Architecture David Meijers February 5, 2009

Documentation – Introduction (1/2) [ ] February 5, 2009 SIG A&D Siemens Four Views RUP / Kruchten 4+1 Image: Lack of agility

Documentation – Introduction (2/2) ,[object Object],[object Object],[ ] February 5, 2009 SIG A&D System simple_cs = { Component client = { Port send-request; }; Component server = { Port receive-request; }; Connector rpc = { Roels { caller, callee}}; Attachments { client.send-request to rpc.caller; server.receive-request to rpc.callee; } }

Stakeholders (1/2) [ ] February 5, 2009 SIG A&D Designers (of interoperating systems) Set of operations provided and required and the protocols for their operation (interface). Requirements Engineers (customer representation) Negotiating and making trade-offs among competing requirements. Managers Basis for: 1) forming development teams corresponding to Identified work assignments, work breakdown structure, planning, allocation of project resources 2) tracking of progress Designers (of constituent parts) Resolve resource contention. Establish performance and other kinds of run-time resource consumption budgets.

Stakeholders (2/2) [ ] February 5, 2009 SIG A&D Architects Reasoning Implementation teams Provide “marching orders”, inviolable constraints (plus exploitable freedoms) on downstream development activities. Testers and integrators Correct black-box behaviour of pieces that must fit together. Quality assurance team Basis for conformance checking (for assurance that implementations have in fact been faithful to architectural prescriptions). Transfer Engineers (or Product line managers) If and by how much a new product family member is out of scope. Maintenance team Starting point for maintenance activities, revealing the effects of change.

Documentation guidelines ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[ ] February 5, 2009 SIG A&D

The Carnegie Mellon approach (1/2) ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[ ] February 5, 2009 SIG A&D

Example: Module viewtype ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[ ] February 5, 2009 SIG A&D

The Carnegie Mellon approach (2/2) ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[ ] February 5, 2009 SIG A&D

Example: Implementation style ,[object Object],[ ] February 5, 2009 SIG A&D

Process ,[object Object],[object Object],[object Object],[ ] February 5, 2009 SIG A&D

So, what do we do specific for designers? [ ] February 5, 2009 SIG A&D ,[object Object],[object Object],[object Object]

What is design? ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[ ] February 5, 2009 SIG A&D As a noun, design is the named structure or behaviour of a system whose presence resolves or contributes to the resolution of one or more forces on that system. A design thus represents one point in a potential decision space. A design may be singular (representing a leaf decision) or it may be collective (representing a set of other decisions ). Grady Booch

What is software architecture? ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[ ] February 5, 2009 SIG A&D All architecture is design but not all design is architecture. Architecture represents the significant design decisions that shape a system, where significant is measured by cost of change. Grady Booch

No project is the same ,[object Object],[object Object],[object Object],[ ] February 5, 2009 SIG A&D 

Communication – Introduction ,[object Object],[object Object],[object Object],[ ] February 5, 2009 SIG A&D

Communication – Basic Techniques ,[object Object],[object Object],[object Object],[ ] February 5, 2009 SIG A&D

Become a friendlier person ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[ ] February 5, 2009 SIG A&D

Win people to your way of thinking ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[ ] February 5, 2009 SIG A&D

Change people’s attitude and behaviour ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[ ] February 5, 2009 SIG A&D

Communication – Software Architecture specific? ,[object Object],[object Object],[object Object],[object Object],[ ] February 5, 2009 SIG A&D

Conclusion ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[ ] February 5, 2009 SIG A&D

References (1/2) ,[object Object],[object Object],[ ] February 5, 2009 SIG A&D ,[object Object]

References (2/2) ,[object Object],[ ] February 5, 2009 SIG A&D ,[object Object],[object Object]

Sig A&D - Documentation And Communication

Recommandé

Recommandé

Contenu connexe

Similaire à Sig A&D - Documentation And Communication

Similaire à Sig A&D - Documentation And Communication (20)

Dernier

Dernier (20)

Sig A&D - Documentation And Communication