Project Evaluation Report.doc - Project Evaluation Report Deliverable V Project Group 22 Authors Belete Ayele Asfaw [email protected] Mihail

Project Evaluation Report.doc - Project Evaluation Report...

This preview shows page 1 - 5 out of 7 pages.

Project Evaluation Report Deliverable V Project Group 22 Authors: Belete Ayele Asfaw [email protected] Mihail Korabelnikov [email protected] Juma Hermed Lungo [email protected] Miria Grisot [email protected] Jose L. Nhampossa [email protected] Ou Weiqing [email protected] Johnny Nordvik [email protected]
Project Group 22 Deliverable V C ONTENTS 1 ................................................................ S TATUS OF IMPLEMENTED FUNCTIONALITY 2 2 ........................................................................ P LANNED VERSUS ACTUAL USED TIME 2 3 ..................................................................... E VALUATION OF THE PROJECT PROCESS 3 3.1 .................................................................................................................... P LANNING 3 3.2 ................................................................................................................. R ESOURCES 3 3.3 ........................................................................................................ C OMMUNICATION 4 3.4 ................................................................................................. T EAM /O RGANIZATION 4 4 ................................................ E VALUATION OF THE QUALITY OF THE APPLICATION 5 4.1 ..................................................................................................................... P RODUCT 5 4.2 ............................................................................................... T OOLS AND P RACTICES 5 5 ...................................... R ECOMMENDED CHANGES FOR THE OBLIGATORY PROJECT 6 Evaluation Document Page 1
Project Group 22 Deliverable V 1 Status of implemented functionality The project group did not manage to finish a product within the time limits. However three prototypes are developed. One for the User Interface, one for the Business Logic and one for the Data base. In the end, the most functionality that the system requires has been successfully realized in all these prototypes. The prototype for the business logic contains this functionality: register customer register employee register product show customer show employee show product delete customer delete employee delete product The remaining functionality was not prototyped due to lack of time and understanding for the problem to be solved. The next chapter will provide further details on this topic. 2 Planned versus actual used time The schedule developed for this project did not contain any administrative task as mentioned in chapter 3.1. The remaining tasks with planned and actual timed used are listed in the figure below. Time spend on the activities Task ID Task Duration Planned Actual T1 Requirement Analysis and Specification 24h 30h T2 Hardware and Software Installation 16h 4h T3 Database Design 24h - T4 User Interface Design 48h - T5 Interface Design 16h - TD1 System Design 88h 59h T7.1 Define 1. increment for programming 5h 5h T7.2 Implement increment 1. 100h 95h T7.3 Program code review 5h - Evaluation Document Page 2
Project Group 22 Deliverable V As long as we did not manage to implement increment 1 of the required functionality we conclude that the time estimation for this project failed. We believe that the main reason for this is a bad structured WBS.

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture