Time line for Work Completion for Asp.net C# and SqlServer DB
-
I am building a system in asp.net C# with an Sql Server DB. I have split the work into separate tasks. I have put a timeline of around 41 days. The requirements are as below. Can anyone say how long it would take and if my timeline is too long? 1. Requirements Gathering and Associated Documentation - Requirements Specification/Functional Specification and Agreement with Stakeholder(s)/Users - 4 days 2 Create DB and Tables and 4 tables - 4 days 3 Create Login Form - 2 days 4 Create Menu - 2 days 5 Create Initial Input Form - containing all the fields that need to be recorded inititally and the 2 calculated fields - 5 days 6 Create “Update Single File” form - Allow user to update this file and write it back to the table in the DB - 3 days 7 Create “Update Multiple Files” form - Display multiple files maybe based criteria selected from dropdown and allow user to possibly do a bulk update of the records - 4 days 8 Create “Add Staff” form and have it writing to the Staff table - 2 days 9 Create “LogOut” form - 1 day 10 Create “Reports”. This would involve creating reports that would have the Grouping of the data in the various different scenarios e.g. Total for Invoice, Total for Trans Number. A report for Audit trail may be needed also. These reports may need to be created in SSRS reporting. - 5 days 11 Audit Trail - Create a record in the audit table each time a record has been updated. Maybe display this audit trail in the “Update Single File” form - 3 days 12 Create Stored Procedures in DB to carry out the above functions - 3 days 13 Carry out functional reviews with Stakeholder(s)/Users - 1 day 14 Carry out Unit testing - 1 day 15 UAT with Stakeholder(s)/Users and Sign Off of System - 1 day
-
I am building a system in asp.net C# with an Sql Server DB. I have split the work into separate tasks. I have put a timeline of around 41 days. The requirements are as below. Can anyone say how long it would take and if my timeline is too long? 1. Requirements Gathering and Associated Documentation - Requirements Specification/Functional Specification and Agreement with Stakeholder(s)/Users - 4 days 2 Create DB and Tables and 4 tables - 4 days 3 Create Login Form - 2 days 4 Create Menu - 2 days 5 Create Initial Input Form - containing all the fields that need to be recorded inititally and the 2 calculated fields - 5 days 6 Create “Update Single File” form - Allow user to update this file and write it back to the table in the DB - 3 days 7 Create “Update Multiple Files” form - Display multiple files maybe based criteria selected from dropdown and allow user to possibly do a bulk update of the records - 4 days 8 Create “Add Staff” form and have it writing to the Staff table - 2 days 9 Create “LogOut” form - 1 day 10 Create “Reports”. This would involve creating reports that would have the Grouping of the data in the various different scenarios e.g. Total for Invoice, Total for Trans Number. A report for Audit trail may be needed also. These reports may need to be created in SSRS reporting. - 5 days 11 Audit Trail - Create a record in the audit table each time a record has been updated. Maybe display this audit trail in the “Update Single File” form - 3 days 12 Create Stored Procedures in DB to carry out the above functions - 3 days 13 Carry out functional reviews with Stakeholder(s)/Users - 1 day 14 Carry out Unit testing - 1 day 15 UAT with Stakeholder(s)/Users and Sign Off of System - 1 day
It sounds rather high to me, but it's an estimate of how long it will take you to do the work, so it depends on how quickly you think you can do it.
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
-
I am building a system in asp.net C# with an Sql Server DB. I have split the work into separate tasks. I have put a timeline of around 41 days. The requirements are as below. Can anyone say how long it would take and if my timeline is too long? 1. Requirements Gathering and Associated Documentation - Requirements Specification/Functional Specification and Agreement with Stakeholder(s)/Users - 4 days 2 Create DB and Tables and 4 tables - 4 days 3 Create Login Form - 2 days 4 Create Menu - 2 days 5 Create Initial Input Form - containing all the fields that need to be recorded inititally and the 2 calculated fields - 5 days 6 Create “Update Single File” form - Allow user to update this file and write it back to the table in the DB - 3 days 7 Create “Update Multiple Files” form - Display multiple files maybe based criteria selected from dropdown and allow user to possibly do a bulk update of the records - 4 days 8 Create “Add Staff” form and have it writing to the Staff table - 2 days 9 Create “LogOut” form - 1 day 10 Create “Reports”. This would involve creating reports that would have the Grouping of the data in the various different scenarios e.g. Total for Invoice, Total for Trans Number. A report for Audit trail may be needed also. These reports may need to be created in SSRS reporting. - 5 days 11 Audit Trail - Create a record in the audit table each time a record has been updated. Maybe display this audit trail in the “Update Single File” form - 3 days 12 Create Stored Procedures in DB to carry out the above functions - 3 days 13 Carry out functional reviews with Stakeholder(s)/Users - 1 day 14 Carry out Unit testing - 1 day 15 UAT with Stakeholder(s)/Users and Sign Off of System - 1 day
If you have to write it from scratch, it may take that long for you to do it. If you already had all the planning done, and you just had to code it, it could be 1/2 the time. But the 80/20 rule still exists. You spend 20% of your time writing the code, and 80% fixing things you never thought a user could do, unless of course you already have that experience. Writing and testing RegEx to validate input could consume all your quoted times. I think a login page should not me more than 4 hours including the database table, cookies, and hashing using PWDTK, or whatever its called. And a logout page more than 2 hours. Reports are time consuming, they take me about 3 days depending on the complexity, and if it's a HTML or Report Writer report. When I quote jobs out, I quote the time to write the job 50%, and the time to test the job, make corrections, test validation, speed test, code analysis, user experience, 30%, and then artwork for buttons, icons, 20%. And then I add 20% more hours as a safety cap. I do quote jobs in units of days, then break it down into hours. I'll give you some tips that I have learned over the last 12 years. Don't write the project for Microsoft SQL Server, use Entity Framework instead I would just write SQL Linq for database functions, and not write out TSQL. Just start out with BootStrap.css, and create a responsive design. Even if your using webforms and not MVC. With webforms, you can make a DLL for Entity Frameworks, or stick it in App_Code. Write your HTML for Forms, such as textboxes as
Enter user name:
and use the bootstrap.css to toggle form errors. I know I'm going to get negative feedback on my suggestions here, but I should of implemented the practice years ago, and I regret not doing it. That SQL Linq is so slick, it's amazing what you can do with it. And the bootstrap.css allows you to just drop in any theme you want, plus it looks cool.
-
If you have to write it from scratch, it may take that long for you to do it. If you already had all the planning done, and you just had to code it, it could be 1/2 the time. But the 80/20 rule still exists. You spend 20% of your time writing the code, and 80% fixing things you never thought a user could do, unless of course you already have that experience. Writing and testing RegEx to validate input could consume all your quoted times. I think a login page should not me more than 4 hours including the database table, cookies, and hashing using PWDTK, or whatever its called. And a logout page more than 2 hours. Reports are time consuming, they take me about 3 days depending on the complexity, and if it's a HTML or Report Writer report. When I quote jobs out, I quote the time to write the job 50%, and the time to test the job, make corrections, test validation, speed test, code analysis, user experience, 30%, and then artwork for buttons, icons, 20%. And then I add 20% more hours as a safety cap. I do quote jobs in units of days, then break it down into hours. I'll give you some tips that I have learned over the last 12 years. Don't write the project for Microsoft SQL Server, use Entity Framework instead I would just write SQL Linq for database functions, and not write out TSQL. Just start out with BootStrap.css, and create a responsive design. Even if your using webforms and not MVC. With webforms, you can make a DLL for Entity Frameworks, or stick it in App_Code. Write your HTML for Forms, such as textboxes as
Enter user name:
and use the bootstrap.css to toggle form errors. I know I'm going to get negative feedback on my suggestions here, but I should of implemented the practice years ago, and I regret not doing it. That SQL Linq is so slick, it's amazing what you can do with it. And the bootstrap.css allows you to just drop in any theme you want, plus it looks cool.
