1 / 43

Principles of Engineering System Design

Principles of Engineering System Design. Dr T Asokan asok@iitm.ac.in. System Design Examples Contd. InSeKTs. Railway service. Airways service. Satellite GPS And weather. Supplier. Transmission. Customer support. User. Server and Data- base. Telephone. Printer. Internet.

timothykadams
Download Presentation

Principles of Engineering System Design

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Principles of Engineering System Design Dr T Asokan asok@iitm.ac.in

  2. System Design ExamplesContd.. InSeKTs

  3. Railway service Airways service Satellite GPS And weather Supplier Transmission Customer support User Server and Data- base Telephone Printer Internet Fax

  4. IDEF0 (Integrated Definition for Function Modeling)A0 diagram User request for directions Type of User: Visitor/IITM community Request to Print Map Database Destination Acknowledgement that Request was received Current Location PROVIDE DIRECTIONS AND OTHER NAVIGATION DETAILS Electric Power Directions from current location to Destination Service, Tests and Repair Printed Map InSeKTs Maintenance Services

  5. A0 Diagram

  6. User Request for directions Power Supply Acknowledge Request Accept Request Process Request Database Digitized Request Search in Database Electricity Display directions Find routes Print Map Maintenance InSeKTs

  7. A11 DIAGRAM

  8. A111 DIAGRAM

  9. InSeKTs User Interface Components Communication module Power module GPS/Navigation aids Network components Receiver keyboards Touch screen Transmi-tter Telephone Speaker Processor Database server Display Screen Printer Fax

  10. MORPHOLOGICAL BOX

  11. REDUNDANCY REQUIREMENTS Fault detection: User support/feedback system fails Access to printer/fax/telephone fails Power supply system fails Transmitter fails

  12. Transmitter fails: for satellite GPS - Using hot standby sparing

  13. User support/feedback system fails: Users maybe accessing from different locations - Using triplicated TMR

  14. Access to printer/fax/telephone fails - Using cold standby Sparing

  15. Power supply system fails - Using cold standby Sparing

  16. UDaReS Unified Data Recording System

  17. SYSTEM DESIGN: Example 3 UDaReS Unified Data Recording System 1.0 Mission:   To develop a unified data-recording system to monitor and control the academic, administrative and other day-to-day activities across the campus.

  18. 2.0 Objectives: • Online recording and compilation of attendance for students/staff/faculty on a day-to-day basis. • Real time analysis of slot-wise engagement of students/faculty. • Online compilation of student grades and TCF. • Integration with the online database of central library.

  19. Serve as a real time data base for leave/salary/scholarship • computation. • Monitor usage of various facilities like mess/SFC/ Gym/swimming pool etc. by the students/staff. • Record faculty/student/staff usage of common services like hospital, engg. unit etc. of the institute and usage of the data for futuristic planning. • Enable cashless transactions at various campus stores. • Develop an online database for projects undertaken by IC&SR and provide online access to financial information.

  20. System Context diagram

  21. UDRAE Life cycle

  22. 3.0 Scope of Project: The project will be limited to: 1. Limited data recording and retrieval by students 2. Data recording by all the staff and limited retrieval by authorized staff. 3. Unlimited data entry and limited retrieval by faculty. 4. Cashless transaction at select establishments/ centres only. 4.0 System Operation Few typical operational scenarios are listed to elaborate on the system functioning.

  23. Scenario 1. Faculty records daily attendance. • An input data device (portable) connected to the • network (through cable/wireless) display the options • available • Faculty chooses attendance record • System asks for authentication • Faculty provides authentication • System accepts authentication and displays the • options available for the faculty • Faculty chooses course name • System display student name and offers opportunity • for faculty to enter data. • Faculty enters data and completes the process by • logging out.

  24. Originating Requirements Document (ORD): • Operational Phase • Input/Output Requirements: • The system shall accept identification details from • professor/students/staff. • The system shall give feedback to user within • x seconds. • The system shall display fonts at least to the • size of ‘y’ • The system shall have provision to enter fees • payment details by the bank personnel

  25. The system shall have provision for auto generating • mail for request of slot exchange with other faculty • The system shall have provision to send mail to • students notifying them regarding scholarships etc. • The system shall compile the staff attendance data • The system shall send mail to the students • regarding changes in the class schedules • Technology/ System wide requirements: • The system shall auto-save data every 30 seconds • The system shall allocate 1Gb space for every • faculty, 500Mb space for every student/staff

  26. The system shall have a processing speed of 5GHz or • more • The system shall use Ipv6 protocol for networking

  27. Use U-Dare Services Software regulations Request U dare Services Maintenance system Provide U- Dare Services Provide support Com-puters Students Maintenance personnel Main server Faculty Staff

  28. EXTERNAL SYSTEM DIAGRAM

  29. A-0 Context diagram

  30. User Identity User Identity Authentication A1 Authentication A1 Accept User Request Request A2 Provide Services Provide Services A3 User Identity User Identity Authentication A4 Authentication A4 Maintain Maintain Services A5 Services A5

  31. Network database Network database Power supply Power supply Feedback Feedback Data search Data search User Identity User Identity request request Authentication Authentication (A1) (A1) Accept user Accept user request/provid request/provid Display data Display data Navigation Navigation e feedback e feedback (A2) (A2) request request Provide navigation Provide navigation Control Control services services Cashless Cashless operation (A3) operation (A3) transaction transaction Enable cashless Enable cashless Provide utility Provide utility request request transaction transaction services (A4) services (A4) Maintenance Maintenance Proper functioning Proper functioning Maintenance Maintenance and repair (A5) and repair (A5) services services UDARE UDARE SYSTEM SYSTEM A0 diagram:

  32. A3 diagram:

  33. A32 diagram:

  34. A322 diagram

  35. Morphological Boxes: Bluetooth LAN Wi-Fi Wi-Max Password Iris eader Fingerprint scan Photo-verify Voice recognition Plastic Polymer Metal FRP Vinyl Coated Paper

  36. Interface Design Interface requirements: Transfer of data between different modules. Operational concept: Intranet (LAN based system). DHUs---------------Server--------------Display unit System shall have shared memory network with storage at server.

  37. Interface options • wi-fi • Using LAN cables • Telephone connection • Wi-fi is too expensive. Data transfer is slow. • Telephone connection is slow. • LAN cables are already present in almost all the • rooms. Fast and cheap. • Select LAN Integration and qualification

  38. Supplemental topics • Graphical modelling techniques • Decision analysis for design tradeoffs • Uncertainty in decision making • System reliability • Statistical tools for system design THANK YOU

More Related