1 Information and Telecommunication System Design Lectures Information

1 Information and Telecommunication System Design Lectures Information and telecommunication systems design

Textbooks 1. The Communicaton Handbook / G. D. Gibson, Ed. – CRC Press, 1997. 2. Kossiakoff, A. , Sweet, W. N. , Systems Engineering: Principles and Practice. – Wiley-Interscience, 2003 3. Dennis, A. , Wixon, B. H. , Tegarden, D. System Analysis Design: UML Version 2. 0 – Wiley, 2009 Information and telecommunication systems design 2

Some Abbreviations 3 DNV - OPNET 3 D Network Visualization tool CCE - Code Composer Essentials CLB - Configurable Logic Block CUT – Circuit Under Test DFD- Data Flow Diagram DFMEA - Design Failure Mode and Effects Analysis DNS - Domain Name Server EPON - Ethernet Passive Optical Network ERD - Engineering Review Diagram FSM – Finite State Machine GPIO - General Purpose Input/Output GPON - Gigabit Passive Optical Network HEP - High Energy Physics Information and telecommunication systems design 3

Some Abbreviations IPDT - Integrated Product Development Test IPDT – Isolated Platform Decision Tree ISP - Internet Service Provider MACS - Multiply-ACcumulate per Second NPV - Negative Predictive Value ORB - Object Request Brokers PERT - Performance Evaluation and Review Technique PFMEA - Process Failure Mode and Effects Analysis PON – Passive Optical Network POSIX - Portable Operating System Interface ROI - Return of Investment QFD - Quality Function Deployment WRT - With Respect To Information and telecommunication systems design 4

Course plan • Lectures • Labs • Course work Information and telecommunication systems design 5

Lectures • • System Engineering System Design IT Systems Planning and Simulation UML System Description Telecom Networks Network Simulation Tools Information and telecommunication systems design 6

Lectures (contd. ) • • System-on-Chip, Network-on-Chip. VLSI RF System Design Embedded Systems. Co-Design FPGA Design DSP System Design Modem Design Real-time System Design Seamless Design Information and telecommunication systems design 7

Course Grading & Project Format • • Labs – 20% Intermediate Exam – 20% Final Exam – 30% Course Work – 30% • Course Work Format 4 Each student will do a total of either 1 -2 -3 team works from PHY/MAC/Network/Application Layers 4 Teams will be formed based on class break-up among Graduate students Information and telecommunication systems design 8

System Engineering Lecture 1 Information and telecommunication systems design 9

Supplemental texts • A. P. Sage. System Engineering. – Wiley, 1992 • B. S. Blanchard. System Engineering Management. - Wiley, 2008 Information and telecommunication systems design 10

Outline • • • System Engineering Complexity Management Adaptive Systems Security Information and telecommunication systems design 11

Systems are created to solve problems From Webster's New Collegiate Dictionary n 1: System - a regularly interacting or interdependent group of items forming a unified whole. Information and telecommunication systems design 12

What is a system? • A purposeful collection of inter-related components working together towards some common objective. • A system may include software, mechanical, electrical and electronic hardware and be operated by people. • System components are dependent on other system components • The properties and behaviour of system components are inextricably inter-mingled Ian Sommerville Information and telecommunication systems design 13

Two Approaches to System Development • Traditional approach – Also called structured system development – Structured analysis and design technique (SADT) – Includes information engineering (IE) • Object-oriented approach – Also called OOA, OOD, and OOP – Views information system as collection of interacting objects that work together to accomplish tasks Systems Analysis and Design in a Changing World Information and telecommunication systems design 14

Focus on Engineering Need • Focus of Systems Engineering Operations Concept – From Original Need – To Final Product • The Whole System Functional Requirements 15 • What needs are we trying to fill? • What is wrong with the current situation? • Is the need clearly articulated? • Who are the intended users? • How will they use our products? • How is this different from the present? • What specific capability will we provide? • To what level of detail? • Are element interfaces well defined? • Focus of Component Engineering • On Detailed Design • What is the overall plan of attack? • What elements make up the overall approach? • Are these complete, logical, and consistent? Allocated Requirements • The Full System Life Cycle System Architecture • Which elements address which requirements? • Is the allocation appropriate? • Are there any unnecessary requirements? Detailed Design Implementation • And Implementation Test & Verification The International Council On Systems Engineering (INCOSE) Information and telecommunication systems design • Are the details correct? • Do they meet the requirements? • Are the interfaces satisfied? • Will the solution be satisfactory in terms of cost and schedule? • Can we reuse existing pieces? • What is our evidence of success? • Will the customer be happy? • Will the users’ needs be met?

The Systems Development Lifecycle • Systems development life cycle (SDLC) – Provides overall framework for managing systems development process • Two main approaches to SDLC – Predictive approach – assumes project can be planned out in advance – Adaptive approach – more flexible, assumes project cannot be planned out in advance • All projects use some variation of SDLC Systems Analysis and Design in a Changing World Information and telecommunication systems design 16

Traditional Predictive Approach to the SDLC • Project planning – initiate, ensure feasibility, plan schedule, obtain approval for project • Analysis – understand business needs and processing requirements • Design – define solution system based on requirements and analysis decisions • Implementation – construct, test, train users, and install new system • Support – keep system running and improve Information and telecommunication systems design 17

Life Cycles with Different Names for Phases Systems Analysis and Design in a Changing World Information and telecommunication systems design 18

Modified Waterfall Approach with Overlapping Phases 19 Information and telecommunication systems design

Computer-based System • A computer-based system makes use of the following four system elements that combine in a variety of ways to transform information – Software: computer programs, data structures, and related work products that serve to effect the logical method, procedure, or control that is required – Hardware: electronic devices that provide computing capability, interconnectivity devices that enable flow of data, and electromechanical devices that provide external functions – Database: A large, organized collection of information that is accessed via software and persists over time – People: Users and operators of hardware and software • The uses of these elements are described in the following: – Documentation: Descriptive information that portrays the use and operation of the system – Procedures: The steps that define the specific use of each system element or the procedural context in which the system resides Information and telecommunication systems design 20

Systems Theory • General systems theory: open systems; system integrity; nested system hierarchy, boundaries, webs, emergence (sum greater than parts) • Cybernetics: system feedback, information; differences (that make a difference); human – machine analogy; inclusion of the observer and the observed in the system • Systems dynamics: systems have reinforcing and balancing feedback loops, circularity, system archetypes, mental models, unintended consequences Information and telecommunication systems design 21

System Models • Linear vs. non-linear (differential equations) • Deterministic vs. Stochastic • Time-invariant vs. Time-varying – Are coefficients functions of time? • Continuous-time vs. Discrete-time Information and telecommunication systems design 22

System Thinking • A way of understanding reality that emphasizes the relationships among a system’s parts, rather than the parts themselves. • Concerned about interrelationships among parts and their relationship to a functioning whole • See underlying patterns and structures Information and telecommunication systems design 23

System Engineering has to do with the application of engineering principles in the development of systems. System Engineering – an interdisciplinary approach and means to enable the realization of successful systems. Information and telecommunication systems design 24

System engineering "System engineering is a robust approach to the design, creation, and operation of systems. In simple terms, the approach consists of identification and quantification of system goals, creation of alternative system design concepts, performance of design trades, selection and implementation of the best design, verification that the design is properly built and integrated, and postimplementation assessment of how well the system meets (or met) the goals. ” — NASA Systems Engineering Handbook, 1995. Information and telecommunication systems design 25

The scope of systems engineering activities Information and telecommunication systems design 26

Problems of systems engineering • Large systems are usually designed to solve 'wicked' problems • Systems engineering requires a great deal of co-ordination across disciplines – Almost infinite possibilities for design trade-offs across components – Mutual distrust and lack of understanding across engineering disciplines • Systems must be designed to last many years in a changing environment Ian Sommerville Information and telecommunication systems design 27

The systems engineering process Ian Sommerville Information and telecommunication systems design 28

Modern systems engineering Krste Asanovic, Chris Terman Information and telecommunication systems design 29

Software and systems engineering • The proportion of software in systems is increasing. Software-driven general purpose electronics is replacing special-purpose systems • Problems of systems engineering are similar to problems of software engineering • Software is (unfortunately) seen as a problem in systems engineering. Many large system projects have been delayed because of software problems Ian Sommerville Information and telecommunication systems design 30

Systems Engineering Methodology • Analyze, Decompose and Allocate System Requirements – Validate Requirements – Requirements Management Requirements Engineering • Define System Behavior – Functionality – Operations • Define System Architecture – Internal and External Interfaces – Subsystems/Assemblies/Components • Define System Verification and Validation – Verification Requirements – Verification Planning (Events and Resources) Information and telecommunication systems design 31

System Engineering Process 32 Behavior Domain Source Requirements Domain Originating requirements trace to behavior CORE Repository verified by Architecture Domain V&V Domain verified by Vitech Corporation Behavior is allocated to physical components Originating requirements trace to physical components Information and telecommunication systems design

Role of Systems Engineering in Product Development 33 The International Council On Systems Engineering (INCOSE) Information and telecommunication systems design Civil Engrg SW Engrg Chem Engrg Elec Engrg Processes Structures Communications Systems Engineering Computers Producibility Environment Maintainability Reliability Safety Systems Engineering Mech Engrg Integrates Technical Effort Across the Development Project – Functional Disciplines – Technology Domains – Specialty Concerns Avionics •

Complexity A complex system has a set of different elements so connected or related as to perform a unique function not performable by the elements alone. (Rechtin and Maier, “The Art of System Architecting”). “…Complexity is the property of a real world system that is manifest in the inability of any one formalism being adequate to capture all its properties. It requires that we find distinctly different ways of interacting with systems. - (Bob Rosen and Don Mikulecky) Information and telecommunication systems design 34

Global Economy Drivers • Computer Industry: Moore’s Law – 2 x Integration every 18 Months • Networks Industry: Metcalfe’s Law – Network Cost ~ #nodes, Value ~ #nodes² • Communication Industry: Gilder’s Law – 3 x Bandwidth every 12 months • Automotive Industry: Quality Leadership – 2 x Printed-Circuit-Board reduction every 3 years – Embedded leadership: integrating FLASH, Analog, Power Information and telecommunication systems design 35

What is Complexity? • Complexity is a measure of how hard something is to understand or achieve – – Components — How many kinds of things are there to be aware of? Connections — How many relationships are there to track? Patterns — Can the design be understood in terms of well-defined patterns? Requirements — Timing, precision, algorithms • Two kinds of complexity: – Essential Complexity – How complex is the underlying problem? – Incidental Complexity – What extraneous complexity have we added? • Complexity appears in at least four key areas: – – Complexity in requirements Complexity of the software itself Complexity of testing the system Complexity of operating the system Flight Software Complexity Information and telecommunication systems design 36

Complexity Management • Challenging requirements raise downstream complexity (unavoidable) • Lack of requirements rationale permit unnecessary requirements • Requirements volatility creates a moving target for designers • Engineering trade studies not done: a missed opportunity • Architectural thinking/review needed at level of systems and software • • Inadequate software architecture and poor implementation General lack of design patterns (and architectural patterns) Coding guidelines help reduce defects and improve static analysis Descopes often shift complexity to operations • Growth in testing complexity seen at all centers • More software components and interactions to test • COTS software is a mixed blessing • Shortsighted FSW decisions make operations unnecessarily complex • Numerous “operational workarounds” raise risk of command errors Flight Software Complexity Information and telecommunication systems design 37 Requirements Complexity System-Level Analysis & Design Flight Software Complexity Verification & Validation Complexity Operations Complexity

Complexity • Many entities, many interactions, collective behavior • Structural complexity • Computational complexity • Dynamic complexity Information and telecommunication systems design 38

Features of complex systems • Difficult to determine boundaries – It can be difficult to determine the boundaries of a complex system. The decision is ultimately made by the observer (modeler). • Complex systems may be open – Complex systems are usually open systems — that is, they exist in a thermodynamic gradient and dissipate energy. In other words, complex systems are frequently far from energetic equilibrium: but despite this flux, there may be pattern stability. • Complex systems may have a memory (often called state) – The history of a complex system may be important. Because complex systems are dynamical systems they change over time, and prior states may have an influence on present states. More formally, complex systems often exhibit hysteresis. • Complex systems may be nested – The components of a complex system may themselves be complex systems. For example, an economy is made up of organizations, which are made up of people, which are made up of cells - all of which are complex systems. Information and telecommunication systems design 39

The Need for Complexity Management The very need for systems analysis and design strategies stems from complexity. If systems or problems were simple enough for humans to be grasped by merely glancing at them, no methodology would have been required. Due to the need for tackling sizeable, complex problems, both a system development methodology and language must be equipped with a comprehensive approach, backed by set of reliable and useful tools, for controlling and managing this complexity. This challenge entails balancing two forces that pull in opposite directions and need to be traded off: completeness and clarity. Information and telecommunication systems design 40

Managing Requirements DECOMPOSITION INTEGRATION • Decomposition techniques create “chunks” that can be handled by design teams and eventually individual designers Information and telecommunication systems design 41

Impact of Economics 42 Performance (Complexity) (Process) * (Team) * (T = Performance = Complexity Process Team Tools = = Effort or time Volume of human-generated code Methods, notations, maturity Skill set, experience, motivation Software process automation Grady Booch Information and telecommunication systems design

How do Systems Engineers Handle Complexity? • Hierarchically • Physical Based Composition • Functionally-Based Information and telecommunication systems design 43

Partitioning • Decomposition of a complex system into smaller subsystems – Done hierarchically – Partitioning done until each subsystem has manageable size – Each subsystem can be designed independently • Interconnections between partitions minimized – Less hassle interfacing the subsystems – Communication between subsystems usually costly [Sherwani] Information and telecommunication systems design 44

Hierarchical Partitioning • Levels of partitioning: – System-level partitioning: Each sub-system can be designed as a single printed circuit board (PCB) – Board-level partitioning: Circuit assigned to a PCB is partitioned into subcircuits each fabricated as a VLSI chip – Chip-level partitioning: Circuit assigned to the chip is divided into manageable sub-circuits NOTE: physically not necessary [Sherwani] Information and telecommunication systems design 45

The physical interconnect hierarchy Michiel De Wilde Information and telecommunication systems design 46

Levels of Partitioning 47 System Level Partitioning PCBs Board Level Partitioning Chips Chip Level Partitioning David Pan Information and telecommunication systems design Subcircuits / Blocks

Partitioning Terminology • Partitioning: Dividing bigger circuits into a small number of partitions (top down) • Clustering: cluster small cells into bigger clusters (bottom up). • Covering / Technology Mapping: Clustering such that each partitions (clusters) have some special structure (e. g. , can be implemented by a cell in a cell library). • k-way Partitioning: Dividing into k partitions. • Bipartitioning: 2 -way partitioning. • Bisectioning: Bipartitioning such that the two partitions have the same size. [Pan] Information and telecommunication systems design 48

The Challenge of Product Line Engineering Processes, tools and techniques cannot overcome the exponential complexity A new approach is required. . . rin e gine n E ty abili p g Ca Time Information and telecommunication systems design Engineering Complexity 49

Tools • Functional "thread" analysis involving use of stimulus-condition-response threads for specifications, development, testing, and reviews • N-squared charts, QFD, Timeline analysis, and Functional Flow Diagrams • Activity Network Diagrams and professional quality project and task schedules • Object-oriented methodologies and distributed networked IPDT’s Information and telecommunication systems design 50

The Object-Oriented Approach to Managing System Complexity: 51 OO development methods, notably the UML (Unified Modeling Languqge) standard (Object Management Group, 2000), address the systems complexity by a “Divide and Conquer” strategy UML and Sys. ML divide the system model into each one of the important aspects of the system structure, dynamics, state transitions For each aspect there are several diagram types Information and telecommunication systems design

The Systems Challenge • At Least Within Reasonable - Time - Cost - Effort - Sense of Security from Risk Faster, Better and Cheaper Information and telecommunication systems design 52

Zoom Source: http: //www. almaden. ibm. com/almaden/talks/Morris_AC_10 -02. pdf Information and telecommunication systems design 53

Adaptive (Complex) System Attributes • Dynamical patterns – parts adapting, coevolving with each other and environment • Parts are massively entangled and interdependent; nested webs, networks • Parts self-organize, learn, and change • Equilibrium in flux, sensitive to initial conditions; system change emerges through interactions among parts Beverly Parsons Information and telecommunication systems design 54

Engineering of self-adaptive systems • High degree of dynamism • Goals / policies change at run-time • Validation and verification performed at run-time • Agility at run-time Müller Information and telecommunication systems design 55

Security and Correctness • System correctness – If user supplies expected input, system generates desired output • Security – If attacker supplies unexpected input, system does not fail in certain ways Information and telecommunication systems design 56

What is Security? • “The quality or state of being secure—to be free from danger” • A successful organization should have multiple layers of security in place: – Physical security – Personal security – Operations security – Communications security – Network security – Information security Information and telecommunication systems design 57

Security properties • Confidentiality – Information about system or its users cannot be learned by an attacker • Integrity – The system continues to operate properly, only reaching states that would occur if there were no attacker • Availability – Actions by an attacker do not prevent users from having access to use of the system Information and telecommunication systems design 58

Security Concerns • Damage to any IT-based system or activity can result in severe disruption of services and losses • Systems connected by networks are more prone to attacks and also suffer more as a result of the attacks than stand-alone systems (Reasons? ) • Concerns such as the following are common – How do I know the party I am talking on the network is really the one I want to talk? – How can I be assured that no one else is listening and learning the data that I send over a network – Can I ever stay relaxed that no hacker can enter my network and play havoc? Information and telecommunication systems design 59

IT Security Concepts • Authentication: The process by which one entity verifies that another entity is who they claim to be • Authorization: The process that ensures that a person has the right to access certain resources • Confidentiality: Keeping private or sensitive information from being disclosed to unauthorized individuals, entities, or processes • Integrity: Being about to protect data from being altered or destroyed in an unauthorized or accidental manner • Confidentiality: Keeping private or sensitive information from being disclosed to unauthorized individuals, entities, or processes • Nonrepudiation: The ability to limit parties from refuting that a legitimate transaction took place, usually by means of a signature Information and telecommunication systems design 60

CERT: Recommendations for Evolving the Security Approach Information and telecommunication systems design 61

Network Security • Security Devices – Firewalls • Packet Filters • Stateless or Stateful • Network or Host-based – Intrusion Detection/Prevention Systems (IDS/IPS) • Network or Host-based • Security Protocols – Ident – SSH – Secure Shell – SSL – Secure Sockets Layer – IPSec Scott M. Ballew Information and telecommunication systems design 62

Information Security Policy encompass the following matters 63 • • • Information Infrastructure Protection Anti-Hacking and Virus activities Promotion of a Culture of Security Distribution of Electronic Signatures Privacy Protection and Ethical cyberspace Technology and Industry Information and telecommunication systems design

Methods of Defense • Encryption • Software Controls – (access limitations in a data base, in operating system protect each user from other users) • Hardware Controls – (smartcard) • Policies – (frequent changes of passwords) • Physical Controls Information and telecommunication systems design 64

Cyber Threats (2001) 65 Crime Incidents Rate (%) Leaks of personal information and invasion of privacy Spam mail Virus and cracking Obscene and violent images Alienation and digital divide Infringement of copyright and illegal copy of S/W Others 870 43. 5 659 219 181 50 15 33. 0 11. 0 9. 1 2. 5 0. 8 6 0. 3 Totals 2 000 100. 0 Korea Information Security Agency Information and telecommunication systems design

Global Attack Trend Source: Websense Information and telecommunication systems design 66

How Much Security is Enough? Needs to shift Information and telecommunication systems design 67

Bridging Polarities We will move from Either/Or to “Yes, And” Thinking Paradox frames the door to life. Charles Johnson Information and telecommunication systems design 68

References • Brun, Y. , Di Marzo Serugendo, J. , Gacek, C. , Giese, H. , Kienle, H. M. , Litoiu, M. , Müller, H. A. , Pezzè, M. , Shaw, M. : Engineering Self. Adaptive Systems through Feedback Loops, In: Software Engineering for Self-Adaptive Systems, LNCS 5527, pp. 47 -69 (2009) • Huebscher, M. C. , Mc. Cann, J. A. : A Survey of Autonomic Computing—Degrees, Models, and Applications. ACM Computing Surveys, 40 (3): 7: 1 -28 (2008) Information and telecommunication systems design 69