Designing Application Components (23 percent)
- Create the high-level design of a component. It may include but is not limited to:
- Establish the life cycle of a component
- Define user interface for each component
- Define interoperability requirements
- Identify and extract reusable components
- Document the design of a component by using pseudo code, class diagrams, sequence diagrams, activity diagrams, and state diagrams
- Decide whether to require constructor input
- Define the internal architecture of a component. It may include but is not limited to:
- Decide whether existing functionality can be implemented or inherited
- Decide how to handle unmanaged and managed resources
- Decide which extensibility features are required
- Determine state management implementation
- Decide whether a component must be multithreaded
- Decide which functions to implement in the base class, abstract class, or sealed class
- Define the data handling for a component. It may include but is not limited to:
- Define data access
- Analyze data relationships
- Analyze the data handling requirements of a component
- Consume components. It may include but is not limited to:
- Identify reusable components
- Handle unmanaged components;
- Identify whether a component needs to be extended
- Identify whether a component needs to be wrapped
- Identify whether any existing functionality needs to be hidden
- Test that reused components meet the specifications
- Define a strategy for exceptions and other component feedback. It may include but is not limited to:
- Identify expected exceptions
- Decide how to deal with expected exceptions
- Decide how to deal with unhandled exceptions
- Decide how to deal with WCF faults
- Define other component feedback, such as events, callbacks, and messages
- Define a reporting strategy
You have a lot of interesting items to reveal. You really are very welcome to investigate out my very own web-site and even let me learn what you consider in regard to my current posting. Thank you