Enterprise Design Pattern

Design patterns which are used mostly for Enterprise Application Architecture areknown as Enterprise Design Pattern.Enterprise Design patterns are introduced in Core J2EE Patterns, the patterns deal with presentation, and application logic.

Examples of Enterprise Design Pattern:

Base Patterns

• Command: An object encapsulates everything needed to execute a method in another object
• Registry: This pattern is useful for making data available to all classes in a process.Through careful use of serialization, it can also be used to store information across a session or even across instances of an application.

Web Presentation Patterns:

• Front Controller: A controller that handles all requests for a Web site.
• Application Controller: A centralized point for handling screen navigation and the flow of an application
• Template View: Renders information into HTML by embedding markers in an HTML page.
• Page Controller: An object that handles a request for a specific page or action on a Web site. Lighter weight but less flexible than Front Controller, Page Controller addresses the same need. Use this pattern to manage requests and handle view logic if you want fast results and your system is unlikely to grow substantially in complexity.

Domain Logic Patterns

• Transaction Script: When you want to get things done fast, with minimal up-front planning, fall back on procedural library code for your application logic. This pattern does not scale well. This pattern Organizes business logic by procedures where each procedure handles a single request from the presentation.
• Domain Model: An object model of the domain that incorporates both behavior and data.

Source: From lecture notes of Design and Development Open Multi-tier Application

Solution of CakePHP Notices: Please change the value of 'Security.salt' and 'Security.cipherSeed'

I have seen following notices during using CakePHP,

• Notice (1024): Please change the value of 'Security.salt' in app/Config/core.php to a salt value specific to your application [CORE\Cake\Utility\Debugger.php, line 657]
• Notice (1024): Please change the value of 'Security.cipherSeed' in app/Config/core.php to a numeric (digits only) seed value specific to your application [CORE\Cake\Utility\Debugger.php, line 661]

This error is generating, because your application doesn't have the same security seed out of million of other installations. So this is a serious security problem. So follow the following steps to solve the issue,

1. Open this file, 'YourProjectName/app/config/core.php'
2. Find this two words, 'Security.salt' and 'Security.cipherSeed'
3. Replace this two words with some random characters.
4. Save core.php

How to use IIS and XAMPP together

I have IIS setup in my PC which use 80 port by default. Today I have installed XAMPP in my PC so that I can do both ASP and PHP programming together. But I have seen that Apache is not running. Thus I am failing to run php files. This is happening, because Apache server also use 80 port. IIS is using the same port, so Apache server will not work in this port. So I have to set Apache server in other port (8080) so that it can run properly. To change the port, please follow the following steps,

1/ Change to this file, C:\xampp\apache\conf\httpd.conf

• Find "Listen 80" and replace with "Listen 8080"
• Find "ServerName localhost:80" and replace with "ServerName localhost:8080"

2/ Change to this file, C:\xampp\apache\conf\extra\httpd-ssl.conf

• Find "Listen 443" and replace with "Listen 4499"
• Find "ServerName localhost:443" and replace with "ServerName localhost:4499"

Now you will be able to use both server together using following URL,

• IIS Server: http://localhost/YourProjectName/
• Apche Server: http://localhost:8080/YourProjectName/

5 basic improvement parameters of software cost model

Five basic improvement parameters of software cost model are,

1. Reducing the size or complexity of what needs to be developed
2. Improving the development process.
3. Using more-skilled personnel and better terms (not necessarily the same thing)
4. Using better environment (tools to automate the process)
5. Trading off or backing off on quality thresholds

Source: Software Project Management by Barry W. Boehm