TheRealDexipher
commented
2 years ago Resources that are required for this project are a database and a web application tool. Based on the UCP, which is 111, the estimated effort of the project is between 1665 to 3330 developer-hours. Through the software estimation and the project management, it shows the estimated UUCW, TCF and EF required for the project. The duration estimated to complete each task is about 6 to 7 days. However, there are overruns that are due to occur. These overruns are further explained below.
The current status is that the user interface requirements such as the company colors, type of font used, and the type of design that is close to what the client wants. Based on the information gathered during the client meeting, functional and non-functional requirements, the examples of the user interface are created. This is to show the client what the web application will look like when a user logs into the system, the manager landing page as well as the job allocation for both daily and weekly.
Using the Waterfall model, our team is in the 'System Analysis and Design' phase. In the 'Requirements Specification' phase, our team had the requirements through the initial requirements in the project overview, client meeting as well as the client email that was sent. These requirements were then analyzed and documented in Milestone 1, specifically under Section 3 'Specific Requirements'. In the current phase, our team further analyze those requirements and come up with the system design to be created for the web application. Our team used the n-Tier architecture for the software design and factory pattern for the detailed design. This aids in developing the overall system architecture and establishes the hardware, software and system requirements.
Work allocations in the project are being assigned individually. Based on what is done in Milestone 1, the workload is then distributed according to what each member is efficient with. These work allocations are more detailed in the project board on GitHub.
One of the overruns that occurred is the user interface as the user interface needed some confirmirmation from the client. Based on the client’s response, the updated user interface can then be created for the report. Based on the gantt chart Figure 11, even though the dates and duration were specifically indicated, there are still overruns by at least 72 hours. (here can talk about how many hours incurred by the overrun from the gantt chart)
Changes to the use case model as well as description are made. These changes are made based on the client’s response to the questions that were asked in the client email that is being sent. One of the changes is when a staff or manager resigns from the company, the account will be deactivated instead of deleted. Another change is the reallocation of jobs. When a staff rejects a job with a valid reason, the manager will then reassign the job. The last change is the submission of a late request. When the staff misses the submission period, he/she can submit a late request to the manager, if no late request was submitted after missing the submission period the manager will assume the staff is available to take on any job. Another possible scenario is if the staff did not state his/her availability before submitting, the system will prompt the staff to indicate their availability before submitting. In the use case descriptions, changes were made since there was not a need to mention the user interface components as well as database. There is also a need to provide alternative scenarios if the precondition fails.
< Describe the resources required and overall time required for the project. Include the current status of the project and work allocations. Highlight any overruns and explain the reasons. >