School Work

Project Plan

Description
pp
Categories
Published
of 8
All materials on our website are shared by users. If you have any questions about copyright issues, please report us to resolve them. We are always happy to assist you.
Related Documents
Share
Transcript
    Travel Arrangement System (TAS) Project Plan   27.10.2014   Ege University Computer Engineering Software Engineering Fall 2014   Mustafa Alper Kılcı / Burak Beynek / Kadri Suner / Özge Torunoğlu    1 Index 1. Introduction.............................................................................................................................. 3 2. Work Breakdown and Milestones ........................................................................................... 3 3. Project Schedule ...................................................................................................................... 5 3.1 Gantt Chart ................................................................................................................ 5 3.2 Network Diagram....................................................................................................... 6 3.3 Division of Labour....................................................................................................... 7 4. Risk Analysis.............................................................................................................................. 8  2 1 –  Introduction This is a software development project which aims to create a functional web based application for travel agencies. The system will provide the following basic functionalities to its users: ●  planning and arranging trips between two given cities ●  arranging reservations for accommodation ●  buying tickets for means of transportation ●  purchasing package and custom tours ●  arranging custom tours TAS will facilitate searching and purchasing every kind ofaccommodation and means of transportation according to the preferences of the customers that are specified through the system. On the other hand, it has to facilitate targeting and personalizing the marketing of transportation and accommodation providers to appropriate potential customers. Our project group will design and make the demonstration of a complete system that can handle all basic aspects (with preferably additional features) of the TAS defined above. Team Members:     Kadri Suner    Özge Torunoğlu      Burak Beynek    Mustaf  a Alper Kılcı   2 –  Work Breakdown and Milestones   PROJECT PLAN (27.10.2014) 1) Gantt Chart of the Project Plan 2) Network Diagram of the Project Plan 3) Division of labor within the team (who is going to do what) 4) Risk analysis document 5) Any other schema or other forms of description that you think is necessary REQUIREMENTS (ANALYSIS) REPORT (17.11.2014) 1) Introduction 2) Identification of Viewpoints Principal Viewpoints of the System Viewpoint Hierarchy Diagram  3 Requirements of each Viewpoint 3) Requirements Definition (considering functionality) Functional Requirements Non-functional Requirements Domain Requirements ** If any of #4 is applicable to your project: 4) Requirements Definition (considering lifetime) Volatile Requirements Enduring Requirements 5) Fully Dressed Use Cases 6) Domain Model as a UML class diagram 7) Any other schema or other forms of description that you think is necessary REQUIREMENTS PRESENTATION (24.11.2014) The teams are required to present the results of their analysis efforts as a short Power-Point slide-show. ARCHITECTURAL MODEL (08.12.2014) - Define the architecture of your system in order to indicate the major components of your system (subsystems) and the relations between them. - Show your architecture as a block diagram or a class diagram. - Indicate if you have employed any generic architecture, architectural style or a reference model. - Be realistic in determining your subsystems. Note that you will need to refer to this architectural partitioning in the project plan while arranging the division of labor between your developers. - Clarify all your entities with a legend or dictionary where necessary. DESIGN DOCUMENT (15.12.2014) 1. Introduction (purpose of the design document, organization of the document) 2. System Sequence Diagram of each use case 3. Sequence Diagram of main use cases 4. Design Class Diagram 5. Glossary (Explain your terms in a dictionary) 6. Any other schema or other forms of description that you think is necessary 7. Conclusion DESIGN PRESENTATION (29.12.2014) The teams are required to present the results of their design efforts and prototype implementation (demo) as a short (20 min.) presentation and demonstration. We expect to be able to understand your system design clearly from your presentation, so you should include anything you think is necessary to achieve this. You are recommended to present your design, referencing your system architecture. You may change any part of your previous choices as long as you explain in your report what has been changed and why. The prototype should cover the main use cases of your design and indicate how the user interface will function. The underlying system need not be implemented.
We Need Your Support
Thank you for visiting our website and your interest in our free products and services. We are nonprofit website to share and download documents. To the running of this website, we need your help to support us.

Thanks to everyone for your continued support.

No, Thanks