Prepared by: Erol Mesut Gün
Related to: Çağlar Kara & Erol Mesut Gün
Date: 13.05.2009
As a final report of performance evaluation, we would like to make a general assessment of the period of whole project. As a project management style at a premium, we decided to take the path of composing our OM-LS project in 4 phases, namley Definition phase, Design phase, System Development Phase and Closing-Out Phase.
As mentioned before in the past performance reports, we as a team, has faced with various problems in the way. However, we estimated these problems as tragedies of commons and we tried to do our bests. Some of the problems that I mentioned about, can be predicted before, however none of us can know that we could not finalize the project as we started. One member of our team, namely Gülin Sonuç, and us as remaining part, namely Çağlar Kara and Erol Mesut Gün drifted away, because of some reasons. However, instead of moaning and groaning because of this departure, Çağlar and I decided to put effort into finalizing this project by doing our bests.
From the point where I stand, I appreciate the performance of our team by looking at what we got over. We achieved to complete both our documentations and programming codes. Therefore, I evaluated ourselves as successful and happy to handle the requirements of the project.
14 Haziran 2009 Pazar
Version 3
This document revised after the meetings with M. T. and M. A.
Date: 27.11.2008
Project Manager: Çağlar Kara
Team Member: Erol Mesut Gün
1. OM-LS will allow end users to register to system over the Internet.
2. Initially it is thought that end users can easily reach to the internet site by clicking the link under the Bilgi University domain. But it can change in the course of time.
3. OM-LS must be user friendly, and is needed to be clear and understandable
4. System must be helpful for the education but not directly educate the students. We assume that end users know about the operation management. But at this point, all we need to do is, to be helpful to students for learning operation management more efficiently.
5. System can be integrated with LMS (Learning Management System).
6. System will design for undergraduated junior (3rd grade) students to MBA ones. Beside this it will also satisfy the needs of Operation Management lectures.
7. In first step system will be in English but it can be multi-language (especially Turkish will be good).
8. This will be an open source system.
9. Knowledge about our enrollee is required. We can gather info about them like their age, at which grade they are or this member is lecture or student etc. For providing this, there need to be a membership system so we need provide accounts to our users.
10. System has ability of integration with database.
11. System can have tools such as chat, messaging, whiteboard etc. although these are not primary requirements, if system has this kind of features, will add value to system.
12. In further steps, authorization to some end-users, such as lectures, can be given about building their own blogs under this system.
13. System should need to provide solutions of all these three methods: Simplex, Integer and Transportation. Limitations about the data entries are up to our preferences. While determining the limitations, it necessitates to check text books for problem size.
14. Programming language is up to us but customer suggests us to use JAVA & JAVA Scipt for this system.
15. There are several LMS on the web site we can gather further information about them but Moodle and Blackboard are system that has close features that customer expect us to design.
Date: 27.11.2008
Project Manager: Çağlar Kara
Team Member: Erol Mesut Gün
1. OM-LS will allow end users to register to system over the Internet.
2. Initially it is thought that end users can easily reach to the internet site by clicking the link under the Bilgi University domain. But it can change in the course of time.
3. OM-LS must be user friendly, and is needed to be clear and understandable
4. System must be helpful for the education but not directly educate the students. We assume that end users know about the operation management. But at this point, all we need to do is, to be helpful to students for learning operation management more efficiently.
5. System can be integrated with LMS (Learning Management System).
6. System will design for undergraduated junior (3rd grade) students to MBA ones. Beside this it will also satisfy the needs of Operation Management lectures.
7. In first step system will be in English but it can be multi-language (especially Turkish will be good).
8. This will be an open source system.
9. Knowledge about our enrollee is required. We can gather info about them like their age, at which grade they are or this member is lecture or student etc. For providing this, there need to be a membership system so we need provide accounts to our users.
10. System has ability of integration with database.
11. System can have tools such as chat, messaging, whiteboard etc. although these are not primary requirements, if system has this kind of features, will add value to system.
12. In further steps, authorization to some end-users, such as lectures, can be given about building their own blogs under this system.
13. System should need to provide solutions of all these three methods: Simplex, Integer and Transportation. Limitations about the data entries are up to our preferences. While determining the limitations, it necessitates to check text books for problem size.
14. Programming language is up to us but customer suggests us to use JAVA & JAVA Scipt for this system.
15. There are several LMS on the web site we can gather further information about them but Moodle and Blackboard are system that has close features that customer expect us to design.
19 Aralık 2008 Cuma
18 Aralık 2008 Perşembe
8 December 2008 - 21 December 2008
Prepared by: Erol Mesut Gün
Related to: Çağlar Kara & Erol Mesut Gün
Date: 18.12.2008
According to the Gantt Chart that we composed, to stick to it, we as Lothusa IT team should finalize Class and Object Diagrams, Use case description, Collaboration and Method Specification Cards. Addition to these documents, we decided to put on paper prototypes to our site and make some changes in our use cases. Even all of these jobs seem that will be taking a lot of time, we managed to perform each tasks cautiously and elaborately. In addition to that, we agreed to accelerate a little bit more and get State, Deployment and Sequence Diagrams out of our way.
While finalizing our weekly performance, we are getting ready for our meeting with M. T. (Boss). We will present our weekly documents to him and hope to receive his approvals. We are satisfied with our performance for this week and feeling the pleasure of total fulfilling of our obligations (except "Risk Assessment" document, but as it would be appreciated, we achieved to compose State, Deployment and Sequence Diagrams in advance).
Related to: Çağlar Kara & Erol Mesut Gün
Date: 18.12.2008
According to the Gantt Chart that we composed, to stick to it, we as Lothusa IT team should finalize Class and Object Diagrams, Use case description, Collaboration and Method Specification Cards. Addition to these documents, we decided to put on paper prototypes to our site and make some changes in our use cases. Even all of these jobs seem that will be taking a lot of time, we managed to perform each tasks cautiously and elaborately. In addition to that, we agreed to accelerate a little bit more and get State, Deployment and Sequence Diagrams out of our way.
While finalizing our weekly performance, we are getting ready for our meeting with M. T. (Boss). We will present our weekly documents to him and hope to receive his approvals. We are satisfied with our performance for this week and feeling the pleasure of total fulfilling of our obligations (except "Risk Assessment" document, but as it would be appreciated, we achieved to compose State, Deployment and Sequence Diagrams in advance).
Kaydol:
Kayıtlar (Atom)