KORHAN TATARHAN 20070602051 ZEKİYE DAVAS 20080601016.

Slides:



Advertisements
Similar presentations
Project Management.
Advertisements

Project Analysis Course ( ) Final Project Report Overview.
CPSC 203. Use Case Diagram  A description of a system’s behavior as it responds to a request that originates from outside of that system. Specifies the.
Requirements Specification and Management
ICT Class System Life Cycle.  Large systems development projects may involve dozens of people working over several months or even years, so they cannot.
Lesson-16 Systems Analysis(2)
Chapter 2- Visual Basic Schneider1 Chapter 2 Problem Solving.
November 2005J. B. Wordsworth: J5DAMQVT1 Design and Method Quality, Verification, and Testing.
CAP 252 Lecture Topic: Requirement Analysis Class Exercise: Use Cases.
Chapter 14 Requirements and Specifications. Copyright © 2005 Pearson Addison-Wesley. All rights reserved Software Engineering The implementation.
1 SWE Introduction to Software Engineering Lecture 21 – Architectural Design (Chapter 13)
Would like to present to you:. Demo Overview Developed an online calendar Meant for small organizations –Efficiency –Communication As well as personal.
Chapter 10 System Sequence Diagrams. What is a System Sequence Diagram? A way of modeling input and output events related to systems It is a picture that.
Documenting Requirements using Use Case Diagrams
Monash University, SIMS, Semester One, DATA GATHERING FOR INFORMATION SYSTEMS DEVELOPMENT CSE Information Systems 1 CSE Information Systems.
Requirements Analysis 2 What objects collaborate to achieve the goal of a use case?
Modeling and Evaluation. Modeling Information system model –User perspective of data elements and functions –Use case scenarios or diagrams Entity model.
Hydro Models Team. Introduction RHESSys is a spatially distributed model of watershed carbon, water and nutrient dynamics. RHESSys stands for Regional.
Requirements Gathering : Determining the scope of the system 1. Elicitiation – fact finding 2. Specification 3. Validation.
Chapter 2- Visual Basic Schneider1 Chapter 2 Problem Solving.
AJAC Systems Hotel Reservation System
By Asma Khalil.  As now a days world is known as the global village. We can share our ideas through out the world and in this mean computer helps us.
USE Case Model.
System Design Chapter 8. Objectives  Understand the verification and validation of the analysis models.  Understand the transition from analysis to.
The Software Development Cycle Defining and understanding the problem.
Final Year Project COMP39X COMP390/3/4/5 Final Year Project Design Irina Biktasheva
SOFTWARE ENGINEERING BIT-8 APRIL, 16,2008 Introduction to UML.
ANALYSIS REQUIREMENT ANALYSIS DESIGN IMPLEMENTATION TEST.
Systems Analysis and Design in a Changing World, 6th Edition
ACCOUNTING INFORMATION SYSTEMS
Use Case Modeling. Watch the video on use cases Review at minute 2:41-3:37.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Slide 1 Message Analysis Table.
Shell Scripting Introduction. Agenda What is Shell Scripting? Why use Shell Scripting? Writing and Running a Shell Script Basic Commands -ECHO - REM.
Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.
An-Najah National University Faculty Of Engineering Industrial Engineering Department Implementation Of Quality Function Deployment On Engineering Faculty.
Okinawa International Hotel Management System. Overview Currently at the Okinawa International hotel, routine procedures like; vacant room inquiry, reservation.
Software Life Cycle Requirements and problem analysis. –What exactly is this system supposed to do? Design –How will the system solve the problem? Coding.
Why Written Requirements?  Unambiguous  Defines goals  Cost of finding a requirements bug later can be 100 times more expensive.
The importance of talking and listening for second language learners
PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 3rd Edition Copyright © 2009 John Wiley & Sons, Inc. All rights.
CSC480 Software Engineering Lecture 8-9 September 20, 2002.
UML Examples PRESETED BY: MEHRAN NAJAFI SHIMA AGHTAR.
Lecture 9-1 : Intro. to UML (Unified Modeling Language)
Context Process0. student Data Flow Diagram Progression.
Programming Models/ Paradigms Chapter 5: Programming Languages.
Knowledge, Information and Data. AIMS :  To understand the distinction between knowledge, information and data.  To understand that data can arise from.
PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 5th Edition Copyright © 2015 John Wiley & Sons, Inc. All rights.
Flowchart. a diagram of the sequence of movements or actions of people or things involved in a complex system or activity. a graphical representation.
 System Sequence Diagrams Sheridan SYST Engineering Quality Systems 11.
Software. Introduction n A computer can’t do anything without a program of instructions. n A program is a set of instructions a computer carries out.
Chapter 2- Visual Basic Schneider1 Chapter 2 Problem Solving.
TA: Shreya Rawal.  A use case is a description of a system’s behavior as it responds to a request that originates from outside of that system (Usually.
SYSTEM ANALYSIS AND DESIGN LAB NARZU TARANNUM(NAT)
Requirements Development An Introduction to the Process and Artifacts November 20, 2001 SIS Analysis Model System Analysis Model SIS Use Case Model System.
1 Advanced DataBases Unified Modelling Language An Introduction and Use Case Lecture 2 Susan Curtis.
AS Level ICT Analysis. Analysis is the process of breaking down a problem into small parts so that it is easier to understand and therefore easier to.
System.
System Design.
Business Process Modelling
1.Introduction to Rational Unified Process (RUP)
Requirements: Use Case Models and Narratives
Process Decomposition
مقدمه اي بر مهندسي نيازمنديها
Vendor Optimizer Part of Radar/Space-Time
Introduction to Software Planning and Design
Warm-Up 1) Write the Now-Next equation for each sequence of numbers. Then find the 10th term of the sequence. a) – 3, 5, 13, 21, … b) 2, – 12, 72, – 432,
Objective- To graph a relationship in a table.
WRITING AN ALGORITHM, PSEUDOCODE, AND FLOWCHART LESSON 2.
Lecture 23 CS 507.
General Workflow of Use-Case Driven Development
Presentation transcript:

KORHAN TATARHAN ZEKİYE DAVAS

THE AIM OF THE PROJECT  The purpose of our project is making hotel reservation system easier to use, more available for customers and hotel staff and solve possible problems during reservation.

 During project, we followed some steps in order. Every step was a preparation for the next one. We made a schedule week-by-week, and did our work according to that schedule. Thus, our project went on as we planned.

 Here are the steps we used in our project:  General Meeting About Project  Requirements Gathering  Classifying Requirements(Func./Nonfunc.)  Use Case Diagrams  Activity Diagrams  Class Diagrams  System Sequence Diagrams  Communication Diagrams  Relationship Matrix and Presentation  Review the Project

 If we make coding for our project, C++ would be available language for us. Because C++ is more usable anf flexible.  Also, our project is a transaction processing system. Because user is the main actor in project. For example, during a room reservation, user gives an input to the system and gets an output from the system according to input.