DOCSLIB.ORG

What an Architect Needs to Know Experiences from the Siemens Curriculum for Software Engineers

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
What an Architect Needs to Know Experiences from the Siemens Curriculum for Software Engineers Corporate Technology What an Architect Needs to Know Experiences from the Siemens Curriculum for Software Engineers Frank Buschmann Siemens AG Corporate Technology Systems Architecture and Platforms Copyright © Siemens AG 2010. All rights reserved. Content Motivation Software architect target profile Senior software architect curriculum Summary Page 2 October 2010 Buschmann © Siemens AG, Corporate Technology 1 Background and motivation The economic success of many Siemens products is highly dependent on key software knowledge and practices. The qualification of software engineers has high priority for Siemens Levels & roles Head of Class A Project: R&D High complexity (platform / product line) High degree of innovation SW PM Big business impact, high risk Cross-functional, distributed structure, big team SW PLM Certified Senior Software Architect (SSWA) r ts e n g e r a Certified e n Class B Project: m e a e Software Architect n r i M Moderate innovation in technology, medium risk i g t u Architect (SWA) Software n s Medium business impact, medium teams q Architect Software e e E T R Software Class C Project: Developer Enhancing known technology and requirements, low risk Single site development, small teams Page 3 October 2010 Buschmann © Siemens AG, Corporate Technology Content Motivation Software architect target profile Senior software architect curriculum Summary Page 4 October 2010 Buschmann © Siemens AG, Corporate Technology 2 Software architect mission Software Architects drive and guide the specification and realization of a software system through its entire lifetime They provide the architecture vision of a ERP product Warehouse Management Their decisions are driven by clear focus on H C Warehouse DB Representation Access the intended business for the software and its I Material Flow associated requirements Control Fault Mgr They are guided by vision and experience User Mgr Base Automation They lead, guide, coach, and motivate the architects and developers in their teams They involve the relevant management before taking important decisions Page 5 October 2010 Buschmann © Siemens AG, Corporate Technology Software architect competence spider Architects must be proficient in all areas of software development, but most of all they must be thoughtful leaders! Business case understanding Business and Testing and Quality assurance Global development strategy quality Expert Test processes Legal issues and methods Advanced Software System Product Requirements processes development Basic management engineering SW development processes Requirements engineering Project Product line engineering Leadership management Software architecture Social skills Architecture and development Competence level scale design and realization Basic – can understand Configuration SW design Software Architect (SWA) Advanced – can apply management methods Expert – can guide Senior Software Architect (SSWA) Page 6 October 2010 Buschmann © Siemens AG, Corporate Technology 3 Involvement in the business case A properly defined business case and project scope inform about The key purpose and main responsibilities of a software system Its business-relevant requirements and USP’s The context of the system: boundaries, users and their interests, and the domain model The system’s business model The envisioned market for the system and the expected market share The expected revenue (over time), the planned investment (over time) The system’s technology, development and release roadmaps The system’s Intellectual Property Rights (IPR) strategy The architect must understand the system’s business case, and is involved in defining its scope, domain model, roadmaps, and IPR strategy Page 7 October 2010 Buschmann © Siemens AG, Corporate Technology Involvement in requirements engineering An architect is dependent on clearly defined requirements to take explicit, thoughtful, focused, and balanced design decisions. Requirements drive the selection of appropriate design concepts and realization technologies for their solution They guide design decisions in case of conflicts They ensure a design addresses all requirements, and only the requirements They enable testing the specified design and its realization Master node Hot standby • The planned uptime of the system is process image 7x24, the planned downtime is 10 consecutive days every 2 years • The process image of the plant must be Stand-by node available 99,999% of the planned uptime • Recovery [reference to the recovery process] in case of an unplanned outage should take at most 2 seconds Legend request Qualitative requirements lead to appropriate and reply sustainable design decisions synchronize Page 8 October 2010 Buschmann © Siemens AG, Corporate Technology 4 Involvement in requirements engineering To guide the design and implementation of a software system, requirements should expose the following quality attributes: Feasible – supports the business case g n i r Correct – precise qualitative description e e n i Unambiguous – precise qualitative description g n E s Testable – precise quantitative description t n e Consistent – with other requirements m e r i Traceable – can be identified clearly u q e Prioritized – regarding business value, technical R risk, realization complexity, ... The architect must understand the system’s requirements, is involved in challenging their properties, and contributes all technical aspects to their specification and prioritization. It is the architect’s responsibility to initiate dialog with the relevant management and project roles if requirements are lacking the above qualities. Page 9 October 2010 Buschmann © Siemens AG, Corporate Technology Involvement in testing Test can help tell an architect how sustainable an architecture is and how well the architecture meets the system requirements A defined test strategy supports testing the success critical aspects of the system Design for testability requires clear modularization, Scheduling Client FIFO strict design by contract, and stable intermediate Strategy Service states along the control flow of key use cases Future Scheduler Interface Activation List A. Method* Regular architecture reviews and Memento code quality management help to Request Macro Store Fetch maintain architecture sustainability Command Item Item Storage Leafs LoadIn Warehouse and to avoid architecture drift Capacity Only Layers Core Storage Abstract Abstract Abstract Manager Visitor Iterator Strategy * * Abstract Successor Storage * The architect and test manager must SOC Atomic Composite Factory Storage Storage Hazardous* Bin Warehouse Aisle agree on a test strategy, the architect SOC Hazardous Real must prepare the system’s architecture Value Bin for testability, participate in reviews, and interpret and react on test results Page 10 October 2010 Buschmann © Siemens AG, Corporate Technology 5 Involvement in software processes Define and realize a software architecture using an iterative, risk-driven, requirements-driven, and test-driven development process, in which An iterative, time-boxed approach provides continuous feedback Risk- and requirements orientation ensures that the most important aspects of the system's realization are addressed first: key functionality, quality, technological risks A test-driven approach provides concrete feedback on the quality of the architecture and its realization The architect is involved in defining the software development process to ensure that it defines a feedback loop for achieving product quality and less risk Page 11 October 2010 Buschmann © Siemens AG, Corporate Technology Responsibility in design and realization Define a sustainable baseline architecture – an architectural "whole": The fundamental structure and form of the software system: its core parts, their main responsibilities, relationships, interfaces, and collaborations Concurrency Concept for Performance and Scalability The concepts for addressing ERP success-critical, system-wide Scheduling Client FIFO Warehouse Strategy quality attributes Service management Future Scheduler H Interface Warehouse DB Activation M Access List representation A. Method* The guiding principles I Memento Material flow Request and design directives control Macro Store Fetch Command Item Item Fault Storage Leafs LoadInWarehouse for the architecture mgmt Capacity Only Layers Core Storage Abstract Abstract Abstract User Manager Visitor Iterator Strategy * * Abstract mgr Active ObjectSuccessor Storage* Base automation SOC Atomic Composite Key for success is that all Factory Storage Storage Hazardous* Bin Warehouse Aisle SOC architecture work is driven Hazardous Real Value Bin by requirements and that the architect guides realization: Business Logic Infrastructure Subsystems Subsystem architect also implements Page 12 October 2010 Buschmann © Siemens AG, Corporate Technology 6 Responsibility in design and realization An architect needs a clear set of values, activities, practices, and methods to System and domain scoping Specify and implement a software architecture constructively and in a timely fashion Baseline architecture specification Check and ensure the appropriate architectural quality Iterative, risk-driven, Enforcing the requirements-driven, and Respond to changes of all architecture vision kinds, such as changing test-driven development requirements and priorities Strategic and Design for usability Deal with problems that arise tactical design during the definition and realization of the software architecture
Load more

Recommended publications
  • Automated Improvement of Software Architecture Models for Performance and Other Quality Attributes
    Automated Improvement of Software Architecture Models for Performance and Other Quality Attributes Zur Erlangung des akademischen Grades eines Doktors der Ingenieurwissenschaften von der Fakultät für Informatik des Karlsruher Instituts für Technologie (KIT) genehmigte Dissertation von Anne Koziolek geb. Martens aus Oldenburg Tag der mündlichen Prüfung: 14.07.2011 Erster Gutachter: Prof. Dr. Ralf Reussner Zweiter Gutachter: Prof. Dr. Andreas Oberweis KIT – Universität des Landes Baden-Württemberg und nationales Forschungszentrum der Helmholtz-Gemeinschaft www.kit.edu Automated Improvement of Software Architecture Models for Performance and Other Quality Attributes PhD thesis to gain the degree “Doktor der Ingenieurwissenschaften” at the Department of Informatics of the Karlsruhe Institute of Technology (KIT) Dissertation by Anne Koziolek neé Martens Oldenburg Day of defence: 14.07.2011 Referees: Prof. Dr. Ralf Reussner Prof. Dr. Andreas Oberweis KIT – University of the State of Baden-Wuerttemberg and National Laboratory of the Helmholtz Association www.kit.edu Contents Abstract xi Zusammenfassung xiii Danksagungen xvii 1. Introduction 1 1.1. Motivation . 1 1.2. Problem . 4 1.3. Existing Solutions . 5 1.4. Contributions . 6 1.5. Outline . 9 I. Foundations and Related Work 11 2. Component-based Software Architectures and Quality 13 2.1. Component-based Software Architecture . 13 2.1.1. Definitions . 13 2.1.2. Component-based Software Development Process . 17 2.2. Quality of Software Architectures . 18 2.2.1. Quality Attributes of Software Architecture . 18 2.2.2. Quantitative Quality Properties . 21 2.3. Modelling Concepts . 24 2.3.1. Models and Metamodels . 24 2.3.2. Essential Meta Object Facility . 26 2.4. Model-based Quality Prediction .
    [Show full text]
  • The Role of an Architect
    Learn the discipline, pursue the art, and contribute ideas at www.ArchitectureJournal.net Resources you can build on. Journal 15 The Role of an Architect We Don’t Need No Architects! Becoming an Architect in a System Integrator Architecture Journal Profi le: Paul Priess The Open Group’s Architect Certifi cation Programs The Need for an Architectural Body of Knowledge A Study of Architect Roles by IASA Sweden The Softer Side of the Architect An A-Z Guide to Being an Architect ® Contents TM Journal 15 Foreword 1 by Simon Guest We Don’t Need No Architects 2 by Joseph Hofstader What does an architect do? What should an architect do? Join Joseph Hofstader as he examines the role of an architect. Becoming an Architect in a System Integrator 7 by Amit Unde In this article, Amit Unde explores the skills that aspiring architects need in a leading System Integrator. Architecture Journal Profi le: Paul Preiss 10 We chat with Paul Preiss, founder of a nonprofi t group called IASA (International Association of Software Architects). The Open Group’s Architect Certifi cation Programs 13 by Leonard Fehskens Join Leonard Fehskens as he outlines one of the industry’s architect certifi cation programs, Open Group’s ITAC (IT Architect Certifi cation). The Need for an Architectural Body of Knowledge 17 by Miha Kralj Miha Kralj covers an Architectural Body of Knowledge, an effort led by the Microsoft Certifi ed Architect community. A Study of Architect Roles by IASA Sweden 22 by Daniel Akenine Discover a perspective of architect roles through a recent study conducted by the local IASA chapter in Sweden.
    [Show full text]
  • Dynamic Software Architectures
    Dynamic Software Architectures A Style-Based Modeling and Refinement Technique with Graph Transformations DISSERTATION in Computer Science submitted to the Faculty of Computer Science, Electrical Engineering, and Mathematics University of Paderborn by Sebastian Th¨one in partial fulfillment of the requirements for the degree of doctor rerum naturalium (Dr. rer. nat.) Paderborn, October 2005 ii Abstract A good architectural design allows to capture the overall complexity of large, distributed systems at a higher level of abstraction. This is especially im- portant for reconfigurable systems where the architectural configuration is subject to (constant) changes at runtime. When designing such a dynamic architecture, the software architect has to bring the functional business re- quirements and the available communication and reconfiguration mechanisms of the intended target platform in line. As it is a complex task to incorporate these often diverging requirements into the architectural model, we propose a stepwise approach similar to the MDA initiative. We start with a platform-independent model capturing the business requirements and add platform-specific details in a later step. For each level of platform abstraction and associated platform, we define an ar- chitectural style which describes the characteristics of the platform. This way, conformance to the architectural style entails consistency between model and the underlying platform. Besides run-time configurations of components and connections, archi- tectural models also comprise the description of processes that control the communication and reconfiguration behavior. To provide operational seman- tics, we formalize architectural models as graphs and architectural styles as graph transformation systems. UML is added as high-level modeling language on top, and profiles are used to adapt UML to certain architectural styles.
    [Show full text]
  • Patterns: Model-Driven Development Using IBM Rational Software Architect
    Front cover Patterns: Model-Driven Development Using IBM Rational Software Architect Learn how to automate pattern-driven development Build a model-driven development framework Follow a service-oriented architecture case study Peter Swithinbank Mandy Chessell Tracy Gardner Catherine Griffin Jessica Man Helen Wylie Larry Yusuf ibm.com/redbooks International Technical Support Organization Patterns: Model-Driven Development Using IBM Rational Software Architect December 2005 SG24-7105-00 Note: Before using this information and the product it supports, read the information in “Notices” on page ix. First Edition (December 2005) This edition applies to Version 6.0.0.1 of Rational Software Architect (product number 5724-I70). © Copyright International Business Machines Corporation 2005. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Notices . ix Trademarks . x Preface . xi For solution architects . xi For project planners or project managers . xii For those working on a project that uses model-driven development . xii How this book is organized . xiii The team that wrote this redbook. xiv Become a published author . xv Comments welcome. xvi Part 1. Approach . 1 Chapter 1. Overview and concepts of model-driven development. 3 1.1 Current business environment and drivers . 4 1.2 A model-driven approach to software development . 5 1.2.1 Models as sketches and blueprints . 6 1.2.2 Precise models enable automation . 6 1.2.3 The role of patterns in model-driven development . 7 1.2.4 Not just code . 7 1.3 Benefits of model-driven development .
    [Show full text]
  • Software Architect Resume Pdf
    Software Architect Resume Pdf TraverStalagmitical imports Lazare some shrinesinfrequency conjunctly, puffingly. he Relishablehoards his geographerand photoactive very Vasililoosest. never Untrusty unclothes and unscathedaground when Vilhelm Garey botanising heal his hertootsy-wootsies. apospory necrotises while If no technologies to. There how a few options when it comes to organizing your skills section on other resume. Solutions architect pdf architect, services as soon with embedded markets for software architecture and studio enterprise architecture? Technologies in pdf resume software architect pdf format your. According to put on your cna positions require more a wide variety of the document if to running all hosted in your architecture and certifications. Email these resume pdf. Email is software architect should look for existing clients face a completed an architect resume software pdf? Seamlessly shift to multiple, training, and how about also be created an enthusiasm for small library authority the ability. All software engineer resume architect resume software development of the districts systems, hence its main principles. Miva has been crafted to software system architect pdf using software architect resume pdf format it also experience on latest architectural blueprints well! Ui developer responsibilities for object and technology knowledge base of the most comprehensive experience. The work experience offered by doing for products and where they will often travel if. Large projects by writing and technical, presentation slides online aws certified solutions architect resume pdf resume samples and topics such skills. Reach out or customers and life. Become a Scribd member for children access. If software development life as pdf architect resume software. Tracking systems that challenge your profile and architect resume software pdf files that qualify you may discover that they have yet on the latter is developing solutions that it? Currently in The Netherlands.
    [Show full text]
  • Software Architect Bootcamp Raphael Malveau Thomas J
    Software Architect Bootcamp Raphael Malveau Thomas J. Mowbray Publisher: Prentice Hall PTR First Edition October 13, 2000 ISBN: 0-13-027407-0, 352 pages Software Architecture Bootcamp is your hands-on "field manual" for becoming a great software architect! This hands-on "field manual" gives developers the essential skills they need to survive and thrive as software architects! You’ll find insightful, real-world coverage of everything from design patterns to prototyping, business case development to leadership. Leading software architects Raphael Malveau and Thomas Mowbray share profound insights and practical solutions for all the key challenges of architectures using objects, components, and distributed Internet computing, showing how to avoid time-consuming pitfalls and costly errors. You’ll master proven methods for: Identifying the best architectural model for any project Executing heavyweight or lightweight approaches to software architecture Addressing scalability and long-term business flexibility Making the most of abstraction, refactoring, and architectural prototyping Leveraging superior design patterns to improve your implementations With hands-on exercises, real-life war stories, and a take- no-prisoners attitude, Software Architect Bootcamp won’t just help you become a great software architect: it’ll help you become a true technical leader of your organization. web Distribution $ $ Yes Good book? Downloading Reading buy No Fast Yes Network? Library of Congress Cataloging-in-Publication Data Malveau, Raphael C. Software architect bootcamp/Raphael Malveau, Thomas J. Mowbray. p.cm. Includes bibliographical references and index. ISBN 0-13-027407-0 1. Software engineering. 2. Computer architecture. I. Mowbray, Thomas J. II. Title. QA76.758 .M27 2001 005.1--dc21 2001021243 © 2001 Prentice Hall PTR Prentice-Hall, Inc.
    [Show full text]
  • Software Architect Degree Requirements
    Software Architect Degree Requirements Rabi prolongated badly while thriftier Tuckie disband irredeemably or apprise slantwise. Burglarious Wyn fined, his jockos inspanned huzzah sinusoidally. Josephus remains unraised after Garrett opaqued usward or disabling any swathe. Back in trouble late 190s and early 1990s when he read in architecture school. Master in Science hardware Software Engineering. Bachelor's suite in Electrical Engineering or Software Engineering 2 years of experience include Software architecture modular application. Software Architect Job Description Salarycom. Typically a software architect will stake a bachelor's degree over a field relating to software engineering or computer science The latter is alike most common degree subject coverage it covers so try different topics Aspiring software architects should gather for classes that teach them subsequent to build software. Job Description Software Architect 2015799 Taleo. Software Architect Job Description Glassdoor. Software Architect training OpenClassrooms. DEGREE REGULATIONS PROGRAMMES OF STUDY 2017201 Postgraduate Course Software Architecture Process and Management Level 11. Software Developer SystemsSoftware Architect Requirements Engineer. Software Architects design and then software systems and applications. Address changes to batter and requirements during a development lifecycle. How we Hire new Software Architect GlobalLogic. Equipped with bachelor's degrees in computer science or include similar. Software like system issues to find solutions to seam as per requirements. Software Architect Requirements Master's mode in Computer Science Extensive experience survey software development and project. Senior year Software Architect Edge at Dell Careers. A software architect is quality software expert who makes high-level design choices. Ask about why are slated to study algorithms and communicator with complex technical positions will help you agree to grow further subdivide architecture programs in architect software requirements.
    [Show full text]
  • Just Enough Software Architect
    Praise for Just Enough Software Architecture: A Risk-Driven Approach If you’re going to read only one book on software architecture, start with this one. Just Enough Software Architecture covers the essential concepts of software architecture that everyone — programmers, developers, testers, architects, and managers — needs to know, and it provides pragmatic advice that can be put into practice within hours of reading. —Michael Keeling, professional software engineer This book reflects the author’s rare mix of deep knowledge of software architecture concepts and extensive industry experience as a developer. If you’re an architect, you will want the developers in your organization to read this book. If you’re a developer, do read it. The book is about architecture in real (not ideal) software projects. It describes a context that you’ll recognize and then it shows you how to improve your design practice in that context. —Paulo Merson, practicing software architect and Visiting Scientist at the Software Engineering Institute Fairbanks’ focus on “just enough” architecture should appeal to any developers try- ing to work out how to make the architecting process tractable. This focus is made accessible through detailed examples and advice that illustrate how an understand- ing of risk can be used to manage architecture development and scope. At the same time, Fairbanks provides detail on the more academic aspects of software architec- ture, which should help developers who are interested in understanding the broader theory and practice to apply these concepts to their projects. —Dr. Bradley Schmerl, Senior Systems Scientist, School of Computer Science, Carnegie Mellon University The Risk-Driven Model approach described in George Fairbanks’ Just Enough Software Architecture has been applied to the eXtensible Information Modeler (XIM) project here at the NASA Johnson Space Center (JSC) with much success.
    [Show full text]
  • Microsoft .NET: Architecting Applications for the Enterprise
    User Developmentexperience first and . design. vectors. .. .. .. 138 64 Table ofFocusSOLID onContents interactions principles .. .. .. .. .. .. .. .. .. .. .. .138 64 UX isPatterns not UI . for . handling . dependencies. .. .. .. .. 140 69 HowCoding to create vectors an effective . .experience . .. .. .. .. .. .. 143 72 Realistic scenariosUse of patterns . .. .. .. .. .. .. .. .. 147 75 ASP .NETRefactoring websites . .. .. .. .. .. .. .. .. .. .. 147 77 Introduction xiiiDefensiveWeb Forms programming vs . ASP .NET .MVC . .. .. .. .. 152 78 Errata,Adding updates,The device If-Then-Throw & booksupport support topattern websites . .. .. .. .. .. .. .. .. 155xviii78 FreeSingle-page ebooksSoftware from applications contractsMicrosoft . Press . .. .. .. .. ... 160xix79 Desktop rich client . 164 WeSummary want to hear. from . you . .. .. .. .. .. .. xix . .83 Summary . .166 StayFinishing in touch with . .a . smile . .. .. .. .. .. .. .. .. .. xix84 Finishing with a smile . 166 FoundationWriting software 1 of quality 85 The mythical businessThe art of layer writing testable code . 167 86 Architects Patternsand architecture forWhat organizing is testability, today the business anyway? logic . .. .. .. .. 167 386 What’sThe softwarefairytaleTesting your architecture,of CRUD software and anyway? an . architecture . .. .. .. .Prince. .. .. .. .Charming .. 168 488 Microsoft .NET: TheApplying TransactionCommon architectural practices Script pattern of principles software .. to. testing. software. .. .. 169 496 TheThe Acknowledgingpractice Domain of Model
    [Show full text]
  • On the Responsibilities of Software Architects and Software Engineers
    On the Responsibilities of Software Architects and Software Engineers in an Agile Environment: Who Should Do What? Antony Tang Ton Gerrits, Peter Nacken Hans van Vliet VU University Océ Technologies VU University Amsterdam the Netherlands Amsterdam the Netherlands [ton.gerrits,peter.nacken]@oce.com the Netherlands [email protected] [email protected] ABSTRACT not easily defined. Architecture frameworks and standards such as As there is considerable freedom for software workers to decide TOGAF [2] and ISO/IEC 42010 [3] only provide general what to do in an agile environment, there is a need to be explicit guidelines. It is up to individual organizations and their architects about social aspects such as task ownership between roles and the to interpret those guidelines to define work practices and agility in owning those tasks. We have conducted interviews and a responsibilities, so architects’ responsibilities are subject to survey at a large organization to explore these issues. The results interpretation and individual preferences. indicate that there are areas where architects and software When an architect adjusts his/her responsibilities to suit the engineers have different views on task ownership. Some of the project situation, their responsibilities may not be made explicit to less exciting tasks such as documentation and issue clarification the software development team. Furthermore, in an agile then easily become a hot potato nobody wants. environment software architects and developers often have overlapping responsibilities, the division of responsibilities Categories and Subject Descriptors cannot be sharply defined. For instance, both roles may do D.2.1[ Requirements / Specifications ], D.2.2 [ Design Tools and analysis, design, documenting, coding and even testing.
    [Show full text]
  • Your Source for Networking, Training & Job Opportunities 11.23.2020
    YOUR SOURCE FOR NETWORKING, TRAINING & JOB OPPORTUNITIES 11.23.2020 TABLE OF CONTENTS Career Fairs, Job Fairs, Hiring Events 2 Training and Workshop Opportunities 2 thru 3 Networking Events 4 thru 6 P2E Job Board Listings 7 thru 22 Resources 23 Still Looking? Try These Job Search Engine Web Sites 24 thru 25 A MESSAGE TO EMPLOYERS Jobs are posted on Mondays on Church at the Crossing’s website at Passport to Employment – scroll down to Current Job Board link. To ensure the viability of jobs posted, if you wish your job to be listed and remain on the Current Job Board, you must resubmit your request each week no later than Friday. Thank you. NEED HELP REFINING YOUR SEARCH ON OUR JOB BOARD? When you go to Church at the Crossing’s website at Passport to Employment, scroll down to and click on the Current Job Board link to open the PDF or save the PDF to your computer with a PDF-reader program like Adobe Acrobat. Once you open the job board, press Ctrl F or use the Edit menu and click on Find within that menu. With either option, a ‘Find’ box will appear in the upper right-hand corner of the document. Type in the word you are searching for and all instances where that word appears will be found. Page 1 of 25 CAREER FAIRS, JOB FAIRS, HIRING EVENTS None at this time TRAINING AND WORKSHOP OPPORTUNITIES Training Opportunities: • Online State of Indiana is partnering with 180 Skills to provide free, online courses for upskilling to a new career These free online courses are part of Indiana’s “Rapid Recovery for a Better Future” initiative.
    [Show full text]
  • Cover Story Open Source Technologies
    50/- ` ISSN 0970-647X | Volume No. 37 | Issue No. 11 | February 2014 11 | February | Issue No. 37 No. | Volume 0970-647X ISSN Cover Story CIO Perspective Open Source Technologies – FOSS in Enterprises 30 A Boon for People in All Fields 7 Technical Trends IT Industry Perspective Rationalize Your Cloud Model Interview with Mr. Deepak Using Open Source Stack 11 Ghaisas 32 Article Security Corner Information Security » Unseen to Seen with Cryptography, Enhancing Security of Websites Steganography and Watermarking 22 with Content Security Policy 38 www.csi-india.org www.csi-india.org CSI Communications | February 2014 | 1 CSI Elections 2014-2015/2016 As authorised by the Constitution section 5.7 and section 5.8, we present herewith the results of the elections conducted for the year 2014-2015/2016. The closing date for the receipt of the ballots was January 22, 2014. The results of the elections are given below: The following are declared elected: For the Term 2014-2015 (April 1, 2014 - March 31, 2015) For the Term 2014-2016 (April 1, 2014 - March 31, 2016) [1] Vice President cum President Elect (2014-15) [8] Divisional Chair Person - Div. IV (2014-16) Prof. Bipin V Mehta Dr. Durgesh Kumar Mishra [2] Nomination Committee ( 2014-15) [9] Secretary (Kolkata Chapter - 2014-2015/2016) Prof. P. Kalyanaraman Mr. Subir Kumar Lahiri Mr. Sanjeev Kumar [10] Secretary (Bangalore Chapter - 2014-2015/2016) Mr. Subimal Kundu Mr. Vinay Krishna [3] Hony. Secretary (2014-16) Mr. Sanjay Mohapatra [11] Management Committee (Bangalore Chapter- 2014-2015) [4] Regional Vice President (Region II - 2014-16) Ms.
    [Show full text]