1

Topic: Estimate in man-days

From zero the online shop is written. Standard business processes - search, purchase, goods layout, registration. It is expected hardly more than  users. A database (Cassandra, DynamoDB, etc. In general arranged, not relational), the server on Java (rest, web), clients - web (JS, jQuery, etc.),  (Java), iOS (Objective-C). How many in man-days in your judgement the side occupies  put for  technologies?

2

Re: Estimate in man-days

Hello, Mishka, you wrote: M> From zero the online shop is written. Standard business processes - search, purchase, goods layout, registration. It is expected hardly more than  users. A database (Cassandra, DynamoDB, etc. In general arranged, not relational), the server on Java (rest, web), clients - web (JS, jQuery, etc.),  (Java), iOS (Objective-C). M> How many in man-days in your judgement the side occupies  put for  technologies? 0,5-10  years, I think.

3

Re: Estimate in man-days

Hello, 0x7be, you wrote: 0> 0,5-10  years, I think. pi*e.

4

Re: Estimate in man-days

Hello, Sinix, you wrote: 0>> 0,5-10  years, I think. S> pi*e. And where in this formula to substitute coefficient of curvature of hands of the developer?

5

Re: Estimate in man-days

Hello, 0x7be, you wrote: 0> And where in this formula to substitute coefficient of curvature of hands of the developer? pi*e <-

6

Re: Estimate in man-days

Hello, 0x7be, you wrote: 0> Hello, Mishka, you wrote: M>> From zero the online shop is written. Standard business processes - search, purchase, goods layout, registration. It is expected hardly more than  users. A database (Cassandra, DynamoDB, etc. In general arranged, not relational), the server on Java (rest, web), clients - web (JS, jQuery, etc.),  (Java), iOS (Objective-C). M>> How many in man-days in your judgement the side occupies  put for  technologies? 0> 0,5-10  years, I think. That is it is realistic for 1st programmer for half a year to lift system with expected loading in 1 + requests in day and 3-mja types of clients? Also I so understand polishing is not included testings, deployment and so forth the administrator the crap or really is ?

7

Re: Estimate in man-days

Hello, Mishka, you wrote: M> From zero the online shop is written. Standard business processes - search, purchase, goods layout, registration. It is expected hardly more than  users. A database (Cassandra, DynamoDB, etc. In general arranged, not relational), the server on Java (rest, web), clients - web (JS, jQuery, etc.),  (Java), iOS (Objective-C). M> How many in man-days in your judgement the side occupies  put for  technologies?" Pioneer "the version - for two months. Beauty of design and riches of possibilities for flight of commercial thought like" and here know, here at us it is some warehouses in a city, some cities, and still are hierarchy of dealers with accumulative discounts and integration with mail , and also automatic calculation of package for the goods and weight of sendings "it will not differ. Still, I do not understand, what flow of orders should be that the server of a DB with 32   and PCIE-SSD could not process it. All this elasticity of that people want to be launched on a shit because on good iron to them credits do not give. M> iOS (Objective-C). After - write on Xamarin.

8

Re: Estimate in man-days

Hello, Glory, you wrote: "the Pioneer" version - for two months. Beauty of design and riches of possibilities for flight of commercial thought like "and here know, here at us it is some warehouses in a city, some cities, and still are hierarchy of dealers with accumulative discounts and integration with mail , and also automatic calculation of package for the goods and weight of sendings" it will not differ. And generally hardly something will be able avalon 1.0rc3 build 430, zlib 1.2.5

9

Re: Estimate in man-days

Hello, Sinix, you wrote: S> S> pi*e <- Not-not-not, the coefficient reflects complexity and riskiness of the project.

10

Re: Estimate in man-days

Hello, 0x7be, you wrote: 0> Not-not-not, the coefficient reflects complexity and riskiness of the project. And it is all already in an imaginary part goes. A complex estimation.

11

Re: Estimate in man-days

Divide at first into tasks in the size from several o'clock about several days, and then already estimate. Otherwise you want, that to you here stupidly bad shot stuck.