In software engineering (or computer science), a design pattern is a general repeatable solution to a commonly occurring problem in software design. A design pattern is not a finished design that can be transformed directly into code. It is a description or template for how to solve a problem that can be used in many different situations. Object-oriented design patterns typically show relationships and interactions between classes or objects, without specifying the final application classes or objects that are involved. Algorithms are not thought of as design patterns, since they solve computational problems rather than design problems.
Design patterns can be classified in terms of the underlying problem they solve.
|
Creational Patterns -- concern the process of object creation. |
|
Abstract Factory |
Provide an interface for creating families of related or dependent objects without specifying their concrete classes.
|
|
Builder |
Separates the construction of a complex object from its representation so that several different representations can be created, depending on the needs of the program.
|
|
Factory Method |
Define an interface for creating an object, but let subclasses decide which class to instantiate. Factory Method lets a class defer instantiation
|
|
Prototype |
The Prototype pattern starts with an instantiated class and copies or clones it to make new instances. These instances can then be further tailored using their public methods.
|
|
Singleton |
The Singleton pattern is a class of which there can be no more than one instance. It provides a single global point of access to that instance.
|
|
Structural Patterns -- describe how classes and objects can be combined to form larger structures. |
|
Adapter |
Convert the interface of a class into another interface clients expect.
Adapter lets classes work together that couldn't otherwise because of incompatible interfaces.
|
|
Bridge |
Decouple an abstraction from its implementation so that the two can vary independently.
|
|
Composite |
Compose objects into tree structures to represent part-whole hierarchies. Composite lets clients treat individual objects and Compositions of objects uniformly.
|
|
Decorator |
Attach additional responsibilities to an object dynamically. Decorators provide a flexible alternative to subclassing for extending functionality.
|
|
Facade |
Provide a unified interface to a set of interfaces in a subsystem. Façade defines a higher-level interface that makes the subsystem easier to use.
|
|
Flyweight |
Use sharing to support large numbers of fine-grained objects efficiently. |
|
Proxy |
Provide a surrogate or placeholder for another object to control access
to it. |
|
Behavioral Patterns -- characterize the ways in which classes or objects interact and distribute responsibility |
|
Chain of Resp. |
Avoid coupling the sender of a request to its receiver by giving more than one object a chance to handle the request. Chain the receiving objects and pass the request along the chain until an object handles it.
|
|
Command |
Encapsulate a request as an object, thereby letting you parameterize clients with different requests, queue or log requests, and support undoable operations.
|
|
Interpreter |
Given a language, define a representation for its grammar along with an interpreter that uses the representation to interpret sentences in the language.
|
|
Iterator |
Provide a way to access the elements of an aggregate object sequentially without exposing its underlying representation.
|
|
Mediator |
Define an object that encapsulates how a set of objects interact.
Mediator promotes loose coupling by keeping objects from referring to each other explicitly, and it lets you vary their interaction independently.
|
|
Memento |
Without violating encapsulation, capture and externalize an object's internal state so that the object can be restored to this state later.
|
|
Observer |
Define a one-to-many dependency between objects so that when one object changes state, all its dependents are notified and updated automatically.
|
|
State |
Allow an object to alter its behavior when its internal state changes. The object will appear to change its class.
|
|
Strategy |
Define a family of algorithms, encapsulate each one, and make them interchangeable. Strategy lets the algorithm vary independently from clients that use it.
|
|
Template Method |
Define the skeleton of an algorithm in an operation, deferring some steps to subclasses. Template Method lets subclasses redefine certain steps of an algorithm without changing the algorithm's structure.
|
|
Visitor |
Represent an operation to be performed on the elements of an object structure. Visitor lets you define a new operation without changing the classes of the elements on which it operates.
|
1MW 1 Microsoft Way
1TBS 1 True Brace Style
21D teach yourself ___ in 21 Days
3COM COMputer, COMmunication, COMpatibility
3Dwm 3-Dimensional Window Manager
3G 3rd Generation
3GIO 3rd Generation Input/Output
3GL 3rd Generation Language
3LD 3rd-Level Domain {IANA}
3NF 3rd Normal Form (databases)
3W World Wide Web
4GL 4th Generation Language
4WCD 4 Wire Conditioned Diphase
A/D Analog/Digital
A/UX Apple UniX
A2A Application TO Application
AA Administrative Authority
AA AntiAliasing
AAA Administration, Authorization, and Authentication (security)
AAA Asp Application Aggregator
AAAI American Association for Artificial Inelligence
AAB All-to-All Broadcast
AAC Advanced Audio Coding
AAEPS Anywhere Anytime Email Proxy Server
AAF Advanced Authoring Format
AAL Atm Abstraction Layer
AAMOF As A Matter Of Fact {chat}
AAP Application Access Point
AARP Appletalk Address Resolution Protocol {Apple}
AART Aggregate Average Response Time
AAS All-to-All Scatter
AAS Auto Area Segmentation
AASE Associate Accredited Systems Engineer {Compaq}
AASP Ascii Asynchronous Support Package
AAT Average Access Time
AAUI Apple Attachment Unit Interface {Apple}
ABA Address Book Archive
ABAP Advanced Business Application Programming
ABC A Bit Cypher
ABC Atanasoff-Berry Computer
ABCPP ABC PreProcessor
ABEL Advanced Boolean Expression Language
ABEND ABnormal END
ABGP
ABI Abstract Binary Interface
ABI Adaptive Brain Interface
ABI Application Binary Interface
ABIOS Advanced Basic Input/Output System
ABIST Automatic Built-In Self Test
ABLE Adaptive Battery Life Extender
ABM Anything But Microsoft
ABM Asynchronous Balanced Mode
ABNF Augmented Backus Normal Form
ABNF Augmented Backus-Naur Form
ABR Area Border Router
ABR Auto Band Rate
ABR Available Bit Rate
.
.
.
And retrieve the complete list fromt the attached Word document.
The definitive Acronym list.doc (1.06 MB)
| TYPES OF QUESTIONS |
| 1. Close-ended questions. These questions may sometimes be helpful when an interviewer(s) wants to know certain information at the onset or needs to determine specific kinds of knowledge. Example: "Could you name the five specific applications involved in...?" |
| 2. Probing questions. These questions allow the interviewer(s) to delve deeper for needed information. Example: "Why?", "What caused that to happen?", or "Under what circumstances did that occur?" |
| 3. Hypothetical questions. Hypothetical situations based on specific job-related facts are presented to the applicant for solutions. Example: "What would you do if..", "How would you handle..." |
| 4. Loaded questions. These questions force an applicant to choose between two undesirable alternatives. The most effective way to employ a loaded question is to recall a real-life situation where two divergent approaches were both carefully considered, then frame the situation as a question starting with, "What would be your approach to a situation where...". |
| 5. Leading questions. The interviewer(s) sets up the question so that the applicant provides the desired response. When leading questions are asked, the interviewer cannot hope to learn anything about the applicant. |
| 6. Open-ended questions. These are the most effective questions, yield the greatest amount of information, and allow the applicant latitude in responding. Example: "What did you like about your last job?" |
|
| Examples of open-ended effective probing: |
| 1. What are/were the three main responsibilities in your current/last position? Which responsibilities do/did you enjoy the most? Why? |
| 2. Of the three main responsibilities, which do/did you enjoy the least? Why? |
| 3. Describe your supervisor's management style. Did/Do you like his or her style of management? Why or why not? |
| 4. Describe your particular style of management, or the style of management you would choose if you were a manager. |
| 5. In the past have you worked in a team environment or independently? Which did you prefer and why? |
| 6. What amount of hours do you/ did you put in at your current/last position? How did you feel about working those hours? |
| 7. What are three of your strongest work related qualities and how were you able to demonstrate these on your job? |
| 8. What are three areas, with regard to your work, that you would like the opportunity to develop? |
| 9. Why did you/are you leave/leaving your last/present position? |
| 10. Of all the jobs you've held, which one did you like the most and why? |
| 11. What major problems have you encountered so far in your professional life and how did you deal with them? |
| 12. What have you learned from your mistakes? |
| 13. How do you react to pressure? |
| 14. What types of decisions are most difficult for you? |
| 15. How have your prior experiences and education prepared you for this job? |
| 16. What has been your biggest work-related frustration to date? How did you handle the situation? |
| 17. Have you ever supervised anyone in a work setting? Have you ever hired or fired anyone? |
| 18. What experience do you have in this field? How have you prepared yourself to switch fields? |
| 19. How have you influenced productivity and results in your previous work experiences? |
| 20. How have you prepared yourself to assume the challenges of this position? |
| 21. How do your current skills apply to this position? |
| 22. In what ways do you expect your relationships with current peers to change? How will you manage this shift? |
|
| Repeated Questions break rehearsed answers |
| 1. What did you like about your previous job/manager? |
| 2. What else did you like about your previous job/manager? |
In some cases, using view state is not feasible. The alternative for view state is session state. Session state is employed under the following situations:
o Large amounts of data - View state tends to increase the size of both the HTML page sent to the browser and the size of form posted back. Hence session state is used.
o Secure data - Though the view state data is encoded and may be encrypted, it is better and secure if no sensitive data is sent to the client. Thus, session state is a more secure option.
o Problems in serializing of objects into view state - View state is efficient for a small set of data. Other types like DataSet are slower and can generate a very large view state.
I have tested it using window application of C#, In this we have two Hexadecimal value, And we check that the source value exists in our database or not.
public Test()
{
InitializeComponent();
//8 Byte Hexadecimal Value of source
this.txtSource.Text = "0x00004000";
//8 Byte Hexadecimal Value of DB
this.txtDB.Text = "0xAF00D0b0";
}
private void button1_Click(object sender, EventArgs e)
{
//Convert the Hexadecimal value inot uint.
uint i = GetHexValue(txtDB.Text.ToString());
uint b = GetHexValue(txtSource.Text.ToString());
txtResult.Text = (i & b) > 0 ? "Match" : "UnMatch";
}
//This is the function used for returning uint value from hexadecimal value.
public uint GetHexValue(String text)
{
uint result = 0;
String parseText = text;
if (parseText.StartsWith("0x", true, CultureInfo.InvariantCulture))
{
parseText = text.Substring(2);
}
if (UInt32.TryParse(parseText, NumberStyles.AllowHexSpecifier, CultureInfo.InvariantCulture, out result) == false)
{
throw new ArgumentException("Text value must be a valid hexidecimal number" + text);
}
return result;
}
There are three levels of data modeling. They are conceptual, logical, and physical. This section will explain the difference among the three, the order with which each one is created, and how to go from one level to the other.
Conceptual Data Model
Features of conceptual data model include:
- Includes the important entities and the relationships among them.
- No attribute is specified.
- No primary key is specified.
At this level, the data modeler attempts to identify the highest-level relationships among the different entities.
Logical Data Model
Features of logical data model include:
- Includes all entities and relationships among them.
- All attributes for each entity are specified.
- The primary key for each entity specified.
- Foreign keys (keys identifying the relationship between different entities) are specified.
- Normalization occurs at this level.
At this level, the data modeler attempts to describe the data in as much detail as possible, without regard to how they will be physically implemented in the database.
In data warehousing, it is common for the conceptual data model and the logical data model to be combined into a single step (deliverable).
The steps for designing the logical data model are as follows:
- Identify all entities.
- Specify primary keys for all entities.
- Find the relationships between different entities.
- Find all attributes for each entity.
- Resolve many-to-many relationships.
- Normalization.
Physical Data Model
Features of physical data model include:
- Specification all tables and columns.
- Foreign keys are used to identify relationships between tables.
- Denormalization may occur based on user requirements.
- Physical considerations may cause the physical data model to be quite different from the logical data model.
At this level, the data modeler will specify how the logical data model will be realized in the database schema.
The steps for physical data model design are as follows:
- Convert entities into tables.
- Convert relationships into foreign keys.
- Convert attributes into columns.
- Modify the physical data model based on physical constraints / requirements.
Hi My Team,
It’s really painful to leave you all; you all have made my path to grow in Company Name Love, support, care, faith everything that I received from my team will always be with me and I hope I’ll be in your memories for a very long time, specially when one will see “yellow error page” due to framework.
One thing I would love to say is, we all are very lucky for having such an admirable leader who seldom acts as lead but as a guardian always, so thanks a lot Lovely sir for everything you did, for your support and faith, I wish one day I’ll join you again.
I’ll try my best to be in touch, but if I failed I hope you people will keep me in touch.
All the best for you all!!!
Soon I’ll update you with my new contact no., my mail id is: Your Email Address
Conceptual Design
A conceptual design is an abstract or high level design which includes only the most important components and entities. The main goal of a conceptual design is to provide an understandable picture of the overall purpose of the proposed solution. Components may include major technology systems, external systems that are required for integration or overall functionality, high level data flow, and system functionality. Think of this as the "black box" diagram where portions of the diagram may be simply a technology component to-be-named-later but is identified with its role and purpose.
Logical Design
A logical design is a more detailed design which includes all major components and entities plus their relationships. The data flows and connections are detailed in this stage. The target audience is typically developers or other systems architects. However, it is possible to create logical designs for business purposes to ensure that all components and functionality is accounted and well understood. Logical designs do not include physical server names or addresses. They do include any business services, application names and details, and other relevant information for development purposes.
Physical Design
A physical design has all major components and entities identified within specific physical servers and locations or specific software services, objects, or solutions. Include all known details such as operating systems, version numbers, and even patches that are relevant. Any physical constraints or limitations should also be identified within the server components, data flows, or connections. This design usually precludes or may be included and extended by the final implementation team into an implementation design.
A private constructor is a special instance constructor. It is commonly used in classes that contain static members only. If a class has one or more private constructors and no public constructors, then other classes (except nested classes) are not allowed to create instances of this class.
The XML API for the .NET Framework comprises the following set of functionalities:
XML readers: With XML readers the client application get reference to instance of reader class. Reader class allows you to scroll forward through the contents like moving from node to node or element to element. You can compare it with the "SqlDataReader" object in ADO.NET which is forward only. In short XML reader allows you to browse through the XML document.
XML writers Using XML writers you can store the XML contents to any other storage media. For instance you want to store the whole in memory XML to a physical file or any other media.
XML document classes XML documents provides a in memory representation for the data in an XMLDOM structure as defined by W3C. It also supports browsing and editing of the document. So it gives you a complete memory tree structure representation of your XML document.
|
Copyright © 2010 SoftwareCodeHelp. All rights reserved.
DasBlog 'Portal' theme by Johnny Hughes.
Pick a theme:
|
|