Software parts dependency research(I)

When the develop team is in design phase have to think a lot of thing but there are two concepts that are the most important concepts. In addition, it is a good beginning for the design approach starting think in these concepts.

These concepts are:

•          Which are the parts of software?
•           How coupled are these parts?

Think about that… step by step

Which is the correct way to split the software up into parts? The software splitting can not be a mechanical process because the main factor is the information system that have to be solved by the software and this information system is fully subjective, that is to say:

•     The costumer have to explain it.
•          The  develop team have to understand.
•           The initial approaching, based on costumer/develop team interviews, will change when the software developing have skill that can be review, analyze, etc. In that moment, the fight will begin. Sure.  It will be because the costumer will say:”I don’t want this, this have to be in this way”. The develop team will say:” You said you want this”.  The costumer say:”you didn’t get it, I wanted this”… Do you know the song???   

I show you the “Box split” method for splitting information system up into parts that can be used like parts of the software. The purpose is the split information system process can set the base for development.

1º Step. Information capture process: Like all good development, the information system have to be understood by the team members. Advice: when the developers talk about their work (the software) usually use a technical words that  must not be understood by the  customer. It happened to costumer too. They usually use the their language for telling us that they want. This is good because if they use the their language then the develop team can suppose how the software interface have to be but warning because the customer explanation can be only good for interface. The business logic have to be a deal between the develop team and the customer said in a technical words. Never let the costumer explain the business logic in their language.