Development since the end of

0 like 0 dislike
7 views
Greetings, respected Hebraist!

Now work on the same project (web) I decided to try to move away from the traditional development process and try to guide her "the end" — that is, first I write the controllers, models, views, and then the actual implementation of their execution. Well, for example, the first write controller (examples in php, because it is, dear, development goes)
class Controller_Posts extends Controller { public function action_list() { $posts = Model::select('post'); $this->request->body = View::factory('list', array('posts' => $posts)); } } 

And then implement the Controller class, Model, View...

So, in the course of this development, the question arose — and whether she's got some special name? To read about the pros/cons could be (I have some identified, but if I'm not a pioneer like (which I seriously doubt), then I think you can learn about still unknown to me) to read how effective this is (yet undecided), etc.
by | 7 views

3 Answers

0 like 0 dislike
A really interesting question, although I do not. But I searched the Internet and here I found
\rgoo.gl/HgEOo
\r
Rising programming("programming bottom-up") is a method of programming in which the large blocks are assembled from previously created smaller blocks. Rising programming begins with the development of key procedures and routines, which are then constantly modifierade.
\r
Downward programming("programming top-down") — method of programming in which design begins by defining the goals of the solution, followed by sequential drill, ending with a detailed program.
If I understand correctly Your question, then You have the 2nd type.
If you did not get, then I'm sorry. It was interesting to look. If my answer is not correct, I will look forward to correct.
by
0 like 0 dislike
Well, this is not a reverse order of development. Still after all the planning — implementation — testing. With proper planning level, the implementation of the whole matter can go from complex to simple, although it is usually from the simple to the complex to see all the nuances.
Not found in the Internet references to your case, but the implementation stage, the majority describe a set of necessary actions. I think it is correct to argue that the design stage which is always prior to the implementation, we must design and structure. If further development (implementation) lead from the top down, not bottom up (simple to complex) will just be more problems of realization of separate functions (the implementation of their execution).
Sorry if couldn't help. Certainly an interesting question, but in all spheres of activities are usually recommended to go from simple to complex.
by
0 like 0 dislike
If you first write the tests to the controller, and creating fake\\ilili makovye model and the view, it will be TDD :)
by

Related questions

0 like 0 dislike
4 answers
0 like 0 dislike
3 answers
0 like 0 dislike
5 answers
0 like 0 dislike
1 answer
0 like 0 dislike
1 answer
110,608 questions
257,186 answers
0 comments
28,803 users