Presentation on theme: "Principles of Engineering System Design Dr T Asokan"— Presentation transcript:
Principles of Engineering System Design Dr T Asokan email@example.com
System Design Examples Contd.. InSeKTs
Customer support Satellite GPS And weather Airways service Railway service Supplier User Server and Data- base Internet Fax Printer Telephone Transmission
Type of User: Visitor/IITM community User request for directions Request to Print Map Destination Database Electric Power PROVIDE DIRECTIONS AND OTHER NAVIGATION DETAILS Acknowledgement that Request was received Current Location Directions from current location to Destination Printed Map Maintenance Services InSeKTs Service, Tests and Repair IDEF0 (Integrated Definition for Function Modeling) A0 diagram
Accept Request Process Request Search in Database Find routes Maintenance User Request for directions Power Supply Acknowledge Request Display directions Print Map InSeKTs Database Electricity Digitized Request
InSeKTs User Interface Components Processor GPS/Navigation aids Database server Communication module Power module keyboards Touch screen Telephone Speaker Display Screen Printer Fax Receiver Transmi- tter Network components
REDUNDANCY REQUIREMENTS Fault detection: User support/feedback system fails Access to printer/fax/telephone fails Power supply system fails Transmitter fails
Transmitter fails: for satellite GPS - Using hot standby sparing
User support/feedback system fails: Users maybe accessing from different locations - Using triplicated TMR
Access to printer/fax/telephone fails - Using cold standby Sparing
Power supply system fails - Using cold standby Sparing
UDaReS Unified Data Recording System
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.
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.
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.
System Context diagram
UDRAE Life cycle
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.
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.
Originating Requirements Document (ORD): Operational Phase 1.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
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
The system shall have a processing speed of 5GHz or more The system shall use Ipv6 protocol for networking
Use U-Dare Services Request U dare Services Students Software regulations Com- puters Maintenance system Provide support Provide U- Dare Services Main server Maintenance personnel Staff Faculty
EXTERNAL SYSTEM DIAGRAM
A-0 Context diagram
User Identity Authentication A1 Accept User Request A2 Provide Services A3 User Identity Authentication A4 Maintain Services A5 User Identity Authentication A1 Request Provide Services User Identity Authentication A4 Maintain Services A5
Morphological Boxes: Plastic Polymer Metal FRP Vinyl Coated Paper Bluetooth LAN Wi-Fi Wi-Max Password Iris eader Fingerprint scan Photo-verify Voice recognition
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.
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
Supplemental topics Graphical modelling techniques Decision analysis for design tradeoffs Uncertainty in decision making System reliability Statistical tools for system design THANK YOU