Version 1

Prepared by: Çağlar Kara

Date: 25.11.2008

1.0 Definition Phase

1.1 Make kick-off meeting

1.2 Start up and orientation: This step involves starting to project and making some kind of discussions with project members.

1.3 General Meeting with M.Tülü (Boss) and M.Albayrakoğlu (Customer): Our boss Mustafa Tülü and our customer Murat Albayrakoğlu give us general information about the project itself and the which processes, the project will go through.

1.4 Preparing project commencing document: According to general meeting; preparetion of business case, project charter and team contract should do.

1.5 Interview with M.Albayrakoğlu: For understanding the needs and the perspective of the customer, this interview is needed to be done.

1.6 Preparing project requirements: According to notes that collect in interview with customer, these requirement must detemine.

1.7 Getting feedback from Customer: Determined requirements have to be approve by our customer.

1.8 Re-evaluate requirements: According to feedback, these requirements have to be justify.

1.9 Meeting with M.Tülü (Boss)

1.10 Preparing Scope Statement: Requirements and deliverables must determine.

1.11 Composing Future Plans: This step contains preparing to do list.

1.12 Finalizing Functional Specifications: In this step, final shape of definition is decided.

1.13 Preparing Milestone & Activity List

1.14 Meeting with M.Tülü (Boss)

2.0 Design Phase

2.1 Preparing on paper prototypes: This step includes, the determination of how the screens of the system will be like.

2.2 Getting feedback from Customer

2.3 Compose use case diagrams: According to feedback of on paper prototypes, flow of works and actors role can be easily determine and preparing use case diagram become easy.

2.4 Create Domain Model (Class Diagram): In the lights of use case diagrams, class diagrams need to be prepared.

2.5 Preparing Object Diagram that is the instance of Class Diagram: We should create the instance of the class diagrams.

2.6 Meeting with M.Tülü (Boss)

2.7 Composing Use Case Description Cards: This step includes, the definition of the each use case and contains info about the underlying process.

2.8 Preparing Risk Assesment: In this phase, possible problems and their risk need to be analyzed and there should be a activity plan for each situation.

2.9 Creating Method Specification: This stage contains the determination of the methods that will include in the whole programming code.

2.10 Preparing Collaboration Card (CRC): In this phase, detailed informaion about, relationship between classes, actors and classes themselves

2.11 Meeting with M.Tülü (Boss)

2.12 Creating State Diagrams: This stage contains general information of the work flow and show the direction of the info.

2.13 Creating Sequence Diagrams: It contains both information about work flow and the relationship these works with actors.

2.14 Composing Deployment Diagrams: At this stage general infromation about IT infrastructure for end-user site, computer site and server site.

2.15 Investigation of Operations Management Methods: There need to be made an detail search about simplex, trasportation and integer methods.

2.16 Searches about Peer Systems: Peer systems such as Moodle, Blackboard should be invesitaged in a detailed way

2.17 Meeting with M.Tülü (Boss)

2.18 Compose Technical Specifications: Technical specifications will be procured totally.

2.19 Building necessary Programming Codes: These are the JAVA codes for composing algorithms that works beneath of system.

2.20 Compose Physical Enviroment: Physical environment will be procured such as hardware devices and so on.

2.21 Struct System Component Prototypes:

2.22 Getting feedback from Customer

2.23 Meeting with M.Tülü (Boss)

3.0 System Development Phase

3.1 Creating Modules: In this part it is needed to be composed the working parts of the system. While these modules are integrated perfectly, whole system will be shaped.

3.2 Test Modules: Composed modules are needed to be tested.

3.3 Putting descriptive statements into the system: For providing ease of navigation and being user friendly, descriptive statements about how the system works, must be provided.

3.4 Getting feedback from Customer

3.5 Re-evaluate modules: In th lights of the feedback it is needed to be re-evaluate the system, and design must be changed for gettign customer acceptance.

3.6 Meeting with M.Tülü (Boss)

3.7 Evaluate Performance of Model: For measuring the effectivity of the system (such as time, easy of navigation, clarity etc.) settled criterian have to be provided.

3.8 Evaluate End-User Acceptance: For ensuring the acceptance of end-users, system can be tested by the professionals of Operations Management or Operations Management students.

3.9 Meeting with M.Tülü (Boss)

4.0 Closing-out Phase

4.1 Preparing Final Project Report: All the documents which are done by the process of this project, are needed to be collected.

4.2 Compose Lesson Learned Documents: Lesson which are taken by the problems during the project must be noted as Lesson Learned Document.