CCSK Domain 1 : Cloud Computing Architectural Framework

CCSK Domain 1 : Cloud Computing Architectural Framework


What is Cloud Computing?
Cloud separates application and information resources from underlying infrastructure and the mechanisms used to deliver them.

Cloud enhances collaboration, agility, scaling and availability and provides the potential for cost reduction through optimized and efficient computing.

Advertisements

Certificate of Cloud Security Knowledge (CCSK ) premier

This blog is about CCSK certificate exam with all the resource information and links.


CCSK Exam :
Prerequisites: Study CSA Guidance pdf and ENISA report pdf
Number of questions: 50
Score needed to pass: 80%
Duration: 60 minutes
Price: $295 USD


CCSK Resources :

CSA Guidance: http://www.cloudsecurityalliance.org/guidance/csaguide.v3.0.pdf (70%)
ENISA: http://www.enisa.europa.eu/act/rm/files/deliverables/cloud-computing-risk-assessment (20%)


CCSK Key Examination Concepts
CSA Guidance For Critical Areas of Focus in Cloud Computing (14 Domains)


Section 1. Cloud Architecture
Domain 1 : Cloud Computing Architectural Framework


Section 2. Governing in the Cloud
Domain 2 : Governance and Enterprise Risk Management
Domain 3 : Legal Issues: Contracts and Electronic Discovery
Domain 4 : Compliance and Audit
Domain 5 : Information Management and Data Security
Domain 6 : Portability and Interoperability


Section 3. Operating in the Cloud
Domain 7 : Traditional Security, Business Continuity and Disaster Recovery
Domain 8 : Data Center Operations
Domain 9 : Incident Response, Notifications and Remediation
Domain 10: Application Security
Domain 11: Encryption and Key Management
Domain 12: Identity and Access Management
Domain 13: Virtualization
Domain 14: Security as a Service


IBM UML Certification Guide

UML Exam Part 1 (Analysis)

Test 000-833: Object Oriented Analysis and Design – Part 1 (Analysis)

Test information:
* Number of questions: 50
* Time allowed in minutes: 75
* Required passing score: 60%

 Cost : 200 USD (Prometric Test Center)

Section 1: UML and the Modeling Process (20%)
   1. The Unified Modeling Language
   2. Process and Visual Modeling
   3. Analysis & Design Key Concepts

Section 2: Concepts of Object Orientation (40%)
   1. Relationships
   2. Class
   3. Polymorphism
   4. Interface
         1. Provided
         2. Required
   5. Structured Classes & Ports

Section 3: Architectural Analysis (20%)
   1. Key Concepts
   2. Define high-level organization of the model
   3. Identify analysis mechanisms
   4. Identify key abstractions
   5. Create use-case realizations

Section 4: Use Case Analysis (20%)
   1. Supplement the Use-Case Description
   2. For each Use-Case Realization
         1. Find Classes from Use-Case Behavior
         2. Distribute Use-Case Behavior to Classes
   3. For each resulting analysis class
         1. Describe Responsibilities
         2. Describe Attributes and Associations
         3. Qualify Analysis Mechanisms
   4. Unify Analysis Classes

IBM UML Exam Part 2

Test 000-834: Object Oriented Analysis and Design – Part 2 (Design)

 

Test information:

  • Number of questions: 60
  • Time allowed in minutes: 75
  • Required passing score: 60%
  • Test languages: English

Section1: Identify Design Elements (17%)
   1. Identify classes and subsystems
   2. Identify subsystem interfaces
   3. Update the organization of the Design Model

Section 2: Identify Design Mechanisms (8%)
   1. Categorize clients of analysis mechanisms
   2. Document architectural mechanisms

Section 3: Distribution (17%)
   1. Define the network configuration
   2. Allocate processes to nodes
   3. Define the distribution mechanism

Section 4: Use Case Design (22%)
   1. Describe interaction among design objects
   2. Simplify sequence diagrams using subsystems
   3. Describe persistence-related behavior
   4. Refine the flow of events description
   5. Unify classes and subsystems

Section 5: Subsystem Design (11%)
   1. Distribute subsystem behavior to subsystem elements
   2. Document subsystem elements
   3. Describe subsystem dependencies

Section 6: Class Design (25%)
   1. Create Initial Design Classes
   2. Define Operations
   3. Define Methods
   4. Define States
   5. Define Attributes
   6. Define Dependencies
   7. Define Associations
   8. Define Internal Structure
   9. Define Generalizations
  10. Resolve Use-Case Collisions
  11. Handle Nonfunctional Requirements in General

By identityguru Posted in UML

IBM UML Certification – Section 1

Section 1: UML and the Modeling Process (20%)

  1. The Unified Modeling Language
  2. Process an Visual Modeling
  3. Analysis and Design Key Concepts

The Unified Modeling Language (UML)

The UML is a language for specifying, visualizing, constructing, and documenting the artifacts of software systems, as well as for business modeling and other non-software systems.

Analysis and Design Concepts

Analysis emphsizes an investigation of the problem and requirements, rather than a solution. For example, If a new computerized library information system is desired,how will it be used?

Requiredment Analysis : An Investigation of the requirements

Object Analysis : An Insestigation of the domain objects

Design emphasizes a conceptual solution that fulfills the requirements, rather than its implementation. For example, a description of a database schema and software objects.

Object-Oriented Analysis and Design

During, object-oriented analysis, there is an emphasis on finding and describing the objects or concepts in the problem domain. For example, in the case of the library information system, some of the concepts include Book, Library, and Patron.

During object-orientied design, there is an emphasis on defining software objects and how they collobrate to fulfill the requirements. For example, in the library system, a Book software object may have a title attribute and a getChatpter method.

Finally, during implementation, design objects are implemented, such as a Book class in Java

public class Book{
private String tile;
   public Chapter getChapter(int pageNumber){....}
}

 

 

Spring Primer

Spring is Framework for enabling the use of Inversion of Control (IOC) or dependency injection.

Dependency Lookup -Application logic is in control of exactly what resource is acquired and create a hard dependency on some other class in the process. Check the below snippets of code on dependency lookup.

Auth auth = AuthFactory.getInstance(); or  Auth auth = new AuthImpl(); or Context based lookup.

Dependency Injection – solves the problem by removing the hard relationship with the classes. It helps unit testing the complex application and move application logic from one environment to another. Spring use the Don’t Repeat Yourself (DRY) Principle. This encourages developers to create logic once and only once. Use POJO – standard helper and library classes.

Aspect-Oriented Programming (AOP) – an approach to a set of problems that do not fit into Object Oriented Programing (OOP) to problem solving. The use of an AOP framework allows a solution to a problem to be applied before and after the invocation of various externally identified method calls. Example of Spring AOP is the declarative transaction management library.

With use of declarative transaction management,

@Transactional
public class AuthServiceImp extends ServiceImpl implements AuthService {
 public User createUser(){
           return dao.save(new Use());
}
}

Examples of AOP – managing transactions, security and providing auditing and logging info.

Spring libraries supports all of the Java EE – manage JTA transactions, connect to db, enforce security, send email, schedule operations, manage JMX, generated reports …list goes on.

Spring MVC – divided between views, controller classes and the model.

Views are JSPs, controller classes are provided that supports basic forms to any type complex form. you can chose the impl for the model.

Transfer classes (form beans) are conventional POJOs and validation framework is both POJO and simple to configure.

Spring Web Flow – model your application behavior as a state machine. Application resides in various states and events are raised to move application between these states. This is suited to more dynamic problems. ease of design – State machines are easy to model as diagrams.

Spring Portlet MVC – supports JSR 168 development

Eclipse Web Service Tutorial and Axis2 Setting

I was developing a simple webservice in Eclipse based on the Tutorial available in Eclipse.org and had issue with running it. I finally found that the Eclipse IDE (Galileo) sets the wrong webservice environment that causes all this issue.

Eclipse tutor

link

You can fix it by going to windows ->preference->Web Service -> Server and Runtime -> Web Service Runtime

Set it to Apache Axis2 instead of Apache Axis