Computer hardware and software
how much time should be spent on software design as a percent of the entire construction phase?
Question : how much time should be spent on software design as a percent of the entire construction phase?
We are estimating the design phase and overall construction phase of an IT software (j2EE) project. Is there any industry “standard” as to how much time should be spent designing , compared with total construction. I have seen figures ranging from 10-30 % . Would like to hear from some experts. Thank you!
construction estimating software
Best answer:
Answer by alsmithjpsnet
Depends on the nature of the project, but I think a good general rule of thumb is 50/50. Since they are developing from design specifications, the beter the specifications the beter the results.
-
-
#3 written by mantaray1970 1 year ago
If your design is unique and there is a sufficient market for it’s use, you can spend as much time as needed as it will pay for itself when production starts. Do some market research to see if ppl R interested in your product and work out your Target market. It is best to have a Monopoly on your product so there is no competition. With software design there are probably problems in it that you may overlook so take your time and get it right from the start. Depending on how popular you think this software will be, that is how much time/effort you should put into it. You obviously R worried that you’ll lose money on this venture so do your market research first and go from there. I hope this helps.
-
#4 written by scotthpowell 1 year ago
It would depend on the nature of the project. It could be 10-30%. Here are some factors to consider:
* What kind of system are you building? Web or Desktop, which both have lots of user interaction scenarios? Or a processing system, with relatively few user scenarios.
* Are you building something that’s bleeding edge with completely new features? Or are you customizing an off-the-shelf package?
* Are you adopting an existing framework (for J2EE, Hibernate and Spring come to mind)?
* How good is your team? Experienced teams won’t need as much time.
* How large and distributed is your team? Larger teams with lots of remote developers will need more time.
* How integrated is your software design process into your system design process? Are you following waterfall, UP, Agile? Depending on those answers, how integrated your system designers are with requirements gathering and how you’re defining “design phase” your answer will vary. For example, because we do web development, we combine graphical design and system design in one task because they’re pretty closely related.
* What are the testing and validation requirements? Applications subject to audit industry, client or government audit will take more time.
* What’s the lifetime of the application? Obviously there’s a balance to strike between “straight line development” and “designing for every eventuality.” - Comment Feed for this Post
10-50 percent