1 / 16

T-76.115 Project Review

Magnificent Seven Final demonstration 16.3.2005. T-76.115 Project Review. Agenda. Product presentation (5 min) Overview Customer benefits Demo (20 min) Project evaluation (10 min) Project planning Implementation 1 Implementation 2 Finalization & Delivery Summary Future work

montana-irwin
Download Presentation

T-76.115 Project Review

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Magnificent Seven Final demonstration16.3.2005 T-76.115 Project Review

  2. Agenda • Product presentation (5min) • Overview • Customer benefits • Demo (20 min) • Project evaluation (10 min) • Project planning • Implementation 1 • Implementation 2 • Finalization & Delivery • Summary • Future work • Discussion and questions (5 min)

  3. Product presentation

  4. Product presentationOverview IRMii is an information resource management software, which can be used to manage any type of resources. Based on an old tool (IRM). Essentially made for Nokia Networks to manage computer-related resources. Interface between customers-lab personnel. Reporting tool of resource availability and other related information. Resource tracking HTTP Administrator Customer IRMii

  5. Product presentationBenefits • Good control over resource usage • Good customer-administrator interaction • Any resources can be managed • Easy to learn • Easy to use • Integrated into Nokia intranet • Uses Nokia LDAP • Nokia look&feel • Implementation • Modular • Easy to maintain • Easy to develop further • Extended accessibility for customers • myirm • myprogramme • Easy to follow what is happening

  6. Demonstration20 min

  7. Project evaluation

  8. Project evaluationProject planning • First meetings with the customer to discuss the project domain. • Setup of infrastructure • Development platforms • Documentation system • Et cetera • Documented work practices • Deliverables • Project plan • Requirements document • Use cases • Problems • Unbalanced working hours • Slow start with PEAR learning • Requirements not studied enough • Installation of old IRM

  9. Project evaluationImplementation1 • System architectural work done. • Minor testing done. • Deliverables • Technical specification • Test plan and QA plan • Demonstration version of IRMii • Problems • Requirements changing. • Everyone still not understanding the system. • GUI specifications not done. • Installation of IRM

  10. Project evaluationImplementation2 • Most of implementation done. • Extraordinary work done despite materialized risks and problems. • Testing • Deliverables • Test cases • Test log • Test report • Peer test plan • Database migration plan • User’s and administrator’s guide • First version of IRMii • Problems • Lack of motivation • Slow progress • Hour usage

  11. Project evaluationFinalization & Delivery • Finalization of system • Testing and bug fixing • Peer-testing • Deliverables • Final report • Final version of IRMii • Problems • Too few hours to do any new implementation

  12. Project evaluationSummary – customer goals • Goals of the customer • 8 goals have been met: • IRM as baseline • Fully-functional core system • Modular and extendable implementation • Source code follows conventions • GUI uses Nokia guidelines • Intranet-integrated authentication mechanism • Integrated customer front-end and administrator back-end • Migration plan for old data • 1 goal still to be verified by the customer: • Light-weight and minimal overhead • 1 goal not completely met: • Well-documented

  13. Project evaluationSummary - requirements • Total 129 requirements of which 101 implemented. • Most requirements have been implemented and verified • A couple mandatory still not implemented, but they should maybe had been lower priority requirements. • Unbalanced prioritization • “impossible” to divide them in any other way. • IRM as baseline

  14. Project evaluationSummary – quality assurance • 12755 lines of code • 7200 lines of comments • Only three bugs open • 46 bugs closed • Quality assurance OK All bugs Open bugs

  15. Project evaluationFuture work • Real-environment deployment will determine the level of quality. • What would be nice? • Searching/sorting functionalities • Reports • Notifications and announcements • Binary attachments • Fine-tuning the code • Event logging • (Automated) unit testing for all classes and GUIs • Documentation for users, administrators and developers • Roll-back option for actions (undo) • Knowledge base add-on

  16. Thanks toOur customerOur mentorCourse personnel

More Related