software engineering laboratory graduate school enhancing information assurance education with...

Software Engineering LaboratoryGraduate School

Enhancing Information Assurance Education with Remote Access Laboratories

Hasan Sayani

Copyright, H. Sayani, MD, 2005 2


Hasan Sayani, Ph.D.

Professor and Program Director,Software Engineering and Software Development Management

3501 University Boulevard EastAdelphi, MD 20783 USA301-985-4616 Fax [email protected] www.umuc.edu



• The Need to Build Robustly– To better withstand an attack– Rather than picking up the pieces later– Strategies to build better– Analogy



Conventional House – Before Hurricane



Conventional House – After Hurricane



Correctly Constructed House



An Extreme Solution – An Aerodynamic House



• Thrust of the Software Engineering Laboratory:

– Build Better– Develop Good Operational Procedures– Learn from Failures– Account for New Technical Architectures– Work with New Business Structures



• Build Better Software Systems– Applications– Application Data– Parametric Data– Secure the Platform– Protect Artifacts



• Develop Good Operational Procedures– Protection– Back Up– Access Control– Use of AI to Detect Anomalous Behavior



• Learn from Failures– Purposefully Designed– Post-mortem/Forensics

• Enable Tracing

– Corrective Measures– Incorporate into Good Practice



• Account for New Technical Architectures– Enterprise Architecture– Service-Oriented Architecture

• Enterprise Service Bus• Enterprise Data Bus

– Mobile Devices



• Work with New Business Structures– Out Sourcing– Contract-on-Demand (SOA)– Collaborative Work



• Life Cycle for the Software Engineering Laboratory– Acquire Tools– Install– Support– Integrate into Curriculum– Evaluate– Iterate



• Phased Introduction of Tools– Phase 1: Get most prominent tools

• Microsoft: Visual Studio .NET - MSWE 646, 617• Borland: Together - MSWE 646 • IBM/Rational: Enterprise Studio – MSWE 645,617• Telelogic: DOORS – MSWE 645• Microsoft: Project – MSWE 640, 617



• Issues Surfaced in Phase 1– Software Distribution– Pedagogy for Integration– Legal/Financial– Management of Additional Demands on

Faculty and Students– Need for Dedicated Servers



• Phase 2 and Beyond– Additional Tools within the same genre

• Allow cross-tool evaluations

– Focus on security• Purposeful Errors• Recovery• Protection



• Complications Introduced by On-line classes– Cannot Just Use a Physical Lab

• Several available on campus

– Lab must be available:• Remotely, Asynchronously, 24/7

– Need for Collaborative Mechanisms• UMUC – Web Tycho• Others – Share Point, Groove Office



• Summary– Initial Work Very Well Received by

• Students• Faculty• Employers of Graduates

– Need to Move from a Demonstrative Facility• To Everyday Status!

software engineering laboratory graduate school enhancing information assurance education with...

Documents

hurricane slide

software distribution

aerodynamic house slide

constructed house slide

better analogy slide

good practice slide

anomalous behavior slide

enterprise studio mswe