#64 Weak Strong component concept

[Anonymous]

Originally created by: jon.nor...@fin-plus.co.uk
Originally owned by: jon.nor...@fin-plus.co.uk

Problem some components have tight coupling to objects even with interfaces that can not be shared via the Universal Model. Example Grid & Columns you need a grid to create a column and you cant test a grid without columns.

Possible introduction of weak components that break design and get tested through strong component tests or unit test.

Effectively we already have weak and strong components.

Strong component aspect though linking components via a Universal Model and
using its observability and weak in other respects.

We dont need to be 100% component in design just strong aspects of.

Phase 2 will evolve concepts.

[Anonymous]

Originally posted by: jon.nor...@fin-plus.co.uk

This is where view and service components will diverge but we already have a logical shared interface for both types. If new interfaces are introduced we want few but common interfaces.

I dont not want a solution with a mass of complex untestable interfaces that might obsfucate code. 

From the begining we where looking at RAD solution with stronger aspects than a none RAD or generic RAD solutions.

eg

IConnection : IComponent

[Anonymous]

Originally posted by: jon.nor...@fin-plus.co.uk

merge with note this is not directly dev related or a task just conjecture

Mergedinto: 61
Status: Duplicate