Informal Use Case

Sunday, July 27, 2014

In software and systems engineering, a use case is a list of steps, typically defining interactions between a role (known in Unified Modeling Language (UML) as an "actor") and a system, to achieve a goal. The actor can be a human or an external system. (by Wikipedia)   When we talk about steps; 1.     We are not talking about code, we are talking about actors and responsibilities. 2.     We are not talking about how to perform it, but how will do it. 3.     We are not talking about exception handling,...
one comment

Bigger is not Better – Small interfaces (coupling)

Sunday, April 27, 2014

Hi, As part of my work, not a litte part of it, is the APIs. What we want to reveal? the way we going to do so, the encapsulation and all other things that will describe the functionality we give. But, more than once I found out that the bad experience is not  by the way the API is written but by what it revealing. I’m taking about “The road to hell is paved with good intentions”. For example you have a developer that got a mission to create an API for “Account Management”; Create account Find account by name Delete account by Id Now’ your...

The S.O.L.I.D way: When it’s a Class and when it’s NOT???

Thursday, April 17, 2014

Actually at first it's seems a very dumb question, because for sure we know when we declaring a new class. But I found that it's not so true!!! Let's take the next scenario. You are creating a new website for "Games how to???" For example: Soccer​ 2 teams, 11 players on each team 1.5 hours with one breaks Cannot touch with the hand Ball cannot get out from the field borders Need soccer field Basketball 2 teams, 5 players on each team 1 hour game, with 4 breaks Cannot walk with the without dribble Ball cannot get out from the field borders Need basketball field Cheese 2 players Each move can/or not...
no comments