University of Palestine Faculty of Engineering and Urban planning Software Engineering Department Project : Factory Automation System Eng : Mahmoud Hashem.

Slides:



Advertisements
Similar presentations
Gate Valve Assembly Lab
Advertisements

25 February 2009Instructor: Tasneem Darwish1 University of Palestine Faculty of Applied Engineering and Urban Planning Software Engineering Department.
® IBM Software Group © 2006 IBM Corporation Rational Software France Object-Oriented Analysis and Design with UML2 and Rational Software Modeler 04. Other.
Lecturer: Sebastian Coope Ashton Building, Room G.18 COMP 201 web-page: Lecture.
7M701 1 Software Engineering Software Requirements Sommerville, Ian (2001) Software Engineering, 6 th edition: Chapter 5
1 SWE Introduction to Software Engineering Lecture 5.
João Frazão An Agent-Oriented Software Architecture for Teams of Robots. RESCUE PROJECT João Frazão.
7. 2Object-Oriented Analysis and Design with the Unified Process Objectives  Detailed Object-Oriented Requirements Definitions  System Processes—A Use.
L ECTURE 2 S OFTWARE P ROCESSES 1. O BJECTIVES To describe outline process models for requirements engineering, software development, testing and evolution.
Course Instructor: Aisha Azeem
Software Process Activities. Process activities Real software processes are inter-leaved sequences of technical, collaborative and managerial activities.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 11 Slide 1 Architectural Design.
CS 4310: Software Engineering Lecture 3 Requirements and Design.
Chapter 7: Architecture Design Omar Meqdadi SE 273 Lecture 7 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
Chapter 5 – System Modeling
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 6 Slide 1 Requirements Engineering Processes l Processes used to discover, analyse and.
Instructor: Tasneem Darwish1 University of Palestine Faculty of Applied Engineering and Urban Planning Software Engineering Department Object Oriented.
SOFTWARE DESIGN AND ARCHITECTURE LECTURE 21. Review ANALYSIS PHASE (OBJECT ORIENTED DESIGN) Functional Modeling – Use case Diagram Description.
Eng. Mohammed Timraz Electronics & Communication Engineer University of Palestine Faculty of Engineering and Urban planning Software Engineering Department.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 10Slide 1 Architectural Design l Establishing the overall structure of a software system.
Instructor: Tasneem Darwish1 University of Palestine Faculty of Applied Engineering and Urban Planning Software Engineering Department Object Oriented.
Faculty of Computer & Information
University of Palestine Faculty of Engineering and Urban planning Software Engineering department Software Engineering Group Project Design Document for.
Eng. Mohammed Timraz Electronics & Communication Engineer University of Palestine Faculty of Engineering and Urban planning Software Engineering Department.
The Static Analysis Model Class Diagrams Prof. Hany H. Ammar, CSEE, WVU, and Dept. of Computer Science, Faculty of Computers and Information, Cairo University.
® IBM Software Group © 2006 IBM Corporation Writing Good Use Cases Module 1: Introduction to Use-Case Modeling.
Use Case Modeling Chapter 7 Part of Requirements Modeling Designing Concurrent, Distributed, and Real-Time Applications with UML Hassan Gomaa (2001)
CS 772: Global Knowledge Networks V. “Juggy” Jagannathan CSEE, West Virginia University.
SWT - Diagrammatics Lecture 4/4 - Diagramming in OO Software Development - partB 4-May-2000.
Chapter 6 – Architectural Design Lecture 1 1Chapter 6 Architectural design.
Final Class Diagram for C++ Implementation Clickermatic Software Clicker.
Use Case Diagrams.
Dynamic Models Sequence Diagrams Collaboration Diagrams Activity Diagrams.
CSC 480 Software Engineering High Level Design. Topics Architectural Design Overview of Distributed Architectures User Interface Design Guidelines.
UML (Unified Modeling Language)
Chapter 5 System Modeling (1/2) Yonsei University 2 nd Semester, 2015 Sanghyun Park.
OOAD (part 2) diagrams CSCI577a TAs: Alexey. Outline UML diagrams: – Use case diagrams – Robustness diagrams – Sequence diagrams – Artifacts diagrams.
Chapter 6: System Models Omar Meqdadi SE 273 Lecture 6 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
Design and implementation Chapter 7 – Lecture 1. Design and implementation Software design and implementation is the stage in the software engineering.
Introduction to UML Hazleen Aris Software Eng. Dept., College of IT, UNITEN. …Unified Modeling Language.
University of Palestine Faculty of Engineering and Urban planning Software Engineering Department Project : Factory Automation System Eng : Mahmoud Hashem.
Object Oriented Analysis Unified Modeling Language By Mary Biddle.
Chapter 7 Lecture 1 Design and Implementation. Design and implementation Software design and implementation is the stage in the software engineering process.
For More Tutorials ACC 210 WEEK 1 DQ 1  How does information flow between departments at your organizations? Why do some organizations.
Chapter 4 – System Modeling Lecture 1 1Chapter 5 System modeling.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 10Slide 1 Chapter 5:Architectural Design l Establishing the overall structure of a software.
Chapter 5 – System Modeling Lecture 1 1Chapter 5 System modeling.
LOGO Supervisor: Mr.Huỳnh Anh Dũng Students: Nguyễn Công Tuyến Nguyễn Cảnh Phương Phạm Thị Hằng Bùi Thị Huệ Trần Đức Bình Nguyễn.
Chapter 5 – System Modeling
CompSci 280 S Introduction to Software Development
Systems Analysis and Design in a Changing World, Fourth Edition
Chapter3:Software Processes
Chapter 5 System modeling
PMU E-Alumnus Project Presentation 1
Chapter 5 – System Modeling
Chapter 5 – System Modeling
CSC 480 Software Engineering
Behavioral Modeling.
System Modeling Chapter 4
Abstract descriptions of systems whose requirements are being analysed
Design and Implementation
CS310 Software Engineering Dr.Doaa Sami
Software Engineering System Modeling Chapter 5 (Part 1) Dr.Doaa Sami
King Saud University College of Engineering IE – 462: “Industrial Information Systems” Fall – 2018 (1st Sem H) Introduction (Chapter 1) part.
Chapter 5 Architectural Design.
Chapter 4 System Modeling.
System architecture, Def.
Substation Automation IT Needs
Accounting Discipline Overview
UML Design for an Automated Registration System
Presentation transcript:

University of Palestine Faculty of Engineering and Urban planning Software Engineering Department Project : Factory Automation System Eng : Mahmoud Hashem Badawi Supervisor : Eng : Mohammed Temraz

Factory Automation System Introduction : This system shows the system applied to the factory for the production of plastic, cork, and shows all stages of the production process for him, The system is Adistributed Syatem, and we will address in this presentation to illustrate a general summary of the project and the most important unsolved problems in, and view the use case

Factory Automation System Abstract : This paper describe architecture design of distributed factory automation system and describe facilitates creativity and perspective to implement robot technology. As this system is a server and client and this system was applied to a factory where many of the machines and the robot you Maker, and there is also inside the factory workers and supervisors to work, and shows the production line for a particular product, and is the system peer to peer and supply the most important: Server and client: a server here that is the factory which gives all the orders and decisions issued and the client is the customer, the customer is demand orders. Peer to peer: between the Manager and the robot in the system, the manager give production order, the robot execute the order. Workstations: These workstation are the production process and be linked to the robot of its own, either a real robot or robot agent.

Factory Automation System Use Case : This System is with 5 Actors : 1.Administrator. 2.Customer. 3.WorkStation. 4.Sensor. 5.Actuator.

Factory Automation System Use Case :

Factory Automation System Use Case details : The First Use Case : Description : in the case show all process for the some actors and relationship between process carried out by actors, As the WorkStation do some operation are also type of workstation for example : received material by a robot and the transfer material from received machine to assembly machine by robot in the line, and transfer product from assembly machine to shipping machine also by robot, however these process will not only after the signal from the sensor arrival and these machine start work include if actuator switched on or off. As the sensor carried out several operations for example : arrival pieces and monitor to work and relationship between other operations. As the customer carried out demand order and the admin received order from customer and give order to workstations. Use Case details : The First Use Case : Use Case details : The First Use Case : Actor : Administrator, Actuator, WorkStation, Customer, Sensor Use Case details : The First Use Case :

Factory Automation System Class diagram :

Factory Automation System Activity diagram :

Factory Automation System Sequence diagram :

Factory Automation System