CS3240: Adv. SW Dev. Refactoring and Maintenance

Slides:



Advertisements
Similar presentations
The Design and Problem Solving Process. What is the point? A proven method and process Can be utilized for any problem Helps you to produce quality work.
Advertisements

HIPAA Security Rule Overview and Compliance Program Presented by: Lennox Ramkissoon, CISSP The People’s Hospital HIPAA Security Manager The Hospital June.
Introduction to Risk Management 26 September 2014 Peter Fowler CPPD.
COBIT - II.
Security Engineering II. Problem Sources 1.Requirements definitions, omissions, and mistakes 2.System design flaws 3.Hardware implementation flaws, such.
DITSCAP Phase 2 - Verification Pramod Jampala Christopher Swenson.
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
Ch 3 Usability page 1CS 368 Usability Models the authors compare three usability models and introduce their own “the extent to which a product can be used.
Risk Management Vs Risk avoidance William Gillette.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 30 Slide 1 Security Engineering.
Information Security Compliance System Owner Training Richard Gadsden Information Security Office Office of the CIO – Information Services Sharon Knowles.
Chapter 10.
Moving into Design SYSTEMS ANALYSIS AND DESIGN, 6 TH EDITION DENNIS, WIXOM, AND ROTH © 2015 JOHN WILEY & SONS. ALL RIGHTS RESERVED. 1 Roberta M. Roth.
Current Trends in Systems Develpment
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 30 Slide 1 Security Engineering 1.
Introducing Computer and Network Security. Computer Security Basics What is computer security? –Answer depends on the perspective of the person you’re.
 Explain the role of a system analyst.  Identify the important parts of SRS document.  Identify the important problems that an organization would face.
Topic (1)Software Engineering (601321)1 Introduction Complex and large SW. SW crises Expensive HW. Custom SW. Batch execution.
Cyber Authentication Renewal Project Executive Overview June – minute Brief.
Certification and Accreditation CS Phase-1: Definition Atif Sultanuddin Raja Chawat Raja Chawat.
Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.
Lecture 13 Page 1 CS 236 Online Secure Programming CS 236 On-Line MS Program Networks and Systems Security Peter Reiher.
Assessing the influence on processes when evolving the software architecture By Larsson S, Wall A, Wallin P Parul Patel.
Definitions of Business, E- Business, and Risk  Business: An organization involved in trade of goods and/or services to the consumers  E-Business: Application.
Security Engineering Assurance & Control Objectives Priyanka Vanjani ASU Id #
CS CS 5150 Software Engineering Lecture 2 Software Processes 1.
Risk Assessment Richard Newman. Six Phases of Security Process 1. Identify assets 2. Analyze risk of attack 3. Establish security policy 4. Implement.
Information Security: Model, Process and Outputs Presentation to PRIA WG November 10, 2006.
Welcome to LifeSkills  Do you have your student guide????  Do you have last week assignment??? Student guide – page 18 – worksheet #4 Everyday decisions.
Information Security Measures Confidentiality IntegrityAccessibility Information cannot be available or disclosed to unauthorized persons, entities or.
1 Certification and Accreditation CS Unit 4:RISK MANAGEMENT Jesus Gonzalez Kalpana Bahunoothula Jocelyne Farah.
12/9-10/2009 TGDC Meeting The VVSG Version 1.1 Overview John P. Wack National Institute of Standards and Technology
CMGT 400 Entire Course CMGT 400 Week 1 DQ 1  CMGT 400 Week 1 Individual Assignment Risky Situation  CMGT 400 Week 1 Team Assignment Kudler Fine Foods.
Lecturer: Eng. Mohamed Adam Isak PH.D Researcher in CS M.Sc. and B.Sc. of Information Technology Engineering, Lecturer in University of Somalia and Mogadishu.
SEC 440 OUTLET The learning interface/sec440outletdotcom.
Database Security Threats. Database An essential corporate resource Data is a valuable resource Must be strictly controlled, managed and secured May have.
For more course tutorials visit
CMGT 400 GUIDE Real Success CMGT 400 Entire Course FOR MORE CLASSES VISIT CMGT 400 Week 1 Individual Assignment Risky Situation CMGT.
For More Best A+ Tutorials CMGT 400 Entire Courses (UOP Course) CMGT 400 Week 1 DQ 1 (UOP Course)  CMGT 400 Week 1 Individual Assignments.
Information Security KRISHNAKUMAR RAGHAVAN (KK) NASWA's Information Technology Support Center 1.
Security Management in Practice
Information Security Policy
Information Security, Theory and Practice.
Outline Basic concepts in computer security
Update from the Faster Payments Task Force
Design for Security Pepper.
Health Services Administration
TASHKENT UNIVERSITY OF INFORMATION TECHNOLOGIES NAMED AFTER MUHAMMAD AL-KHWARIZMI THE SMART HOME IS A BASIC OF SMART CITIES: SECURITY AND METHODS OF.
What is Design? The word “design” is often used as a generic term that refers to anything that was made by a conscious human effort. Design is also a process.
Introduction to System Analysis and Design
CEEN 525 Policy Analysis Framework
CJA 385Competitive Success/tutorialrank.com
CIS 333 RANK Perfect Education/ cis333rank.com.
CJA 385 Education for Service-- tutorialrank.com.
CMGT 431 Education for Service/tutorialrank.com
CMGT 400 Education for Service-- tutorialrank.com
I have many checklists: how do I get started with cyber security?
Design Process Overview
Security Protection Goals
Understanding Security Layers
Design Process Overview
Project Management Process Groups
Design Process Overview
Design Process Overview
Lecture 10: Usable Security
Design Process Overview
CS 575 – Drexel University – Fall 2007
Design Process Overview
Presentation transcript:

CS3240: Adv. SW Dev. Refactoring and Maintenance

Where we’re heading Towards “the end”, of course Towards maintenance and evolution, to be precise

Design Tradeoffs Design: Identifying alternative solutions that meet the requirements Analyzing these solutions and choosing one, based on… what? Will it work? (Of course) ???

Design Tradeoffs Design: Identifying alternative solutions that meet the requirements Analyzing these solutions and choosing one, based on… what? Will it work? (Of course) Efficiency Flexibility, maintainability Security Usability Others?

Design Tradeoffs and OneDir Being agile, we didn’t do a formal design doc Did you design? Somehow, somewhere Class activity: Groups of 2 or 3, with team members if possible Discuss some design alternatives you saw as you built OneDir Think about why you made a design choice What SW design principles guided (or in retrospect) might have guided your choice Consequences for your final design? Turn in: Brief discussion on these points for one good example among your group’s experience One piece of paper per group, with everyone’s name and ID

SW Security: An Overview

Security CIA: Confidentiality, Integrity, Availability Confidentiality Making sure data only viewable by authorized users Integrity Ensuring accuracy and consistency of data over its entire life-cycle Availability Data and services are available when needed, avoiding single points of failure, etc.

Confidentiality Data at rest, data in transit Encryption Authentication Authorization Your implementation of OneDir? Vulnerabilities Risk modeling, threat assessment

Integrity Hashing Consistency

Feedback: Privacy Policy Feedback
Do Not Sell My Personal Information
About project: SlidePlayer Terms of Service

© 2025 SlidePlayer.com. Inc. All rights reserved.