11-08-2012, 02:24 PM
Future Fashion
[attachment=31128]
Introduction of Future Fashion
The FUTURE FASHION Web site is the application that provides customers with online shopping. Through a Web browser, a customer can browse the catalog, place items to purchase into a virtual shopping cart, create and sign in to a user account, and purchase the shopping cart contents by placing an order with a credit card.
The Application is a working demonstration of how to use blueprints principles in a real application design. This document is an online guide to the design and the implementation of the application Enterprise Applications with web technology.
Each release of the application maintains consistent design features such as separating logic and presentation, using web component for control and web pages for presentation, using business components, and so on. high-level design features, this document goes deeper into the implementation details of the current application release.
This document is provided as an online-only resource so that it may be continually extended and updated. This document begins with a description of the separate applications that the sample application comprises, describes the modular structure of the EMAT application, and provides an in-depth description of several pieces of the modules.
• Each FUTURE FASHION module has different requirements from the others. This section describes the requirements, design, and implementation of each module.
• Control module—the control module dispatches requests to business logic, controls screen flow, coordinates component interactions, and activates user sign on and registration. The control module is implemented by the WAF and application-specific WAF extensions.
• Shopping cart module—the shopping cart tracks the items a user has selected for purchase
• Sign on module—the sign on module requires a user to sign on before accessing certain screens, and manages the sign on process
• Messaging module—the messaging module asynchronously transmits purchase orders from the pet store to the OPC
• Catalog module—the catalog module provides a page-based view of the catalog based on user search criteria
• Customer module—the customer module represents customer information: addresses, credit cards, contact information, and so on
Control Module Requirements
The control module forms the framework underlying the application, so it naturally has the most high-level requirements. Extensibility and maintainability are prime considerations in this module. The control module must be extensible because all real-world enterprise applications change constantly. Because the control module plays a role in virtually every interaction, its code must be well-structured to avoid complexity-related maintenance problems. The requirements of the control module are:
• The module must handle all HTTP requests for the application. This module controls a Web application, and interacts with a user who sends HTTP service requests. The control module is responsible for classifying and dispatching each of these requests to the other modules.
• HTTP responses may be of any content type. Web application developers do not want to be limited to just textual content types. The control module must also be able to produce binary responses.
• Business logic must be easily extensible. Enterprise applications are always changing and growing as business rules and conditions change. A developer familiar with the control module should be able easily to add new functionality with minimal impact on existing functions.
• New views must be easy to add. Most business logic changes imply new user views, so developers must be able to create new views easily.
• Module must provide application-wide control of look and feel. Manually editing hundreds or dozens of user views is not a practical way to manage application look and feel. The control module must provide a way for application screen layout and style to be controlled globally.
• Application must be maintainable even as it grows. The control module must be structured so that new functions added over time do not result in a thicket of unmentionable “spaghetti” code. It should be possible to easily understand the control of even an application with several hundred business classes. Application-wide functionality must be easy to add. New application requirements occasionally apply to every operation or view in an application. The control module must be structured so that such requirements can be easily met.
TOOLS, PLATFORM & LANGUAGE TO BE USED
TOOLS:
FRONT-END : ASP.NET(With C# 2.0)
BACK-END : SQL SERVER 2000
PLATFORM:
WINDOW SERVER - 2000.
HARDWARE AND SOFTWARE ENVIRONMENT
HARDWARE ENVIRONMENT:
PROCESSOR : P-IV(1.80 GHZ)
RAM : 128 MB
STORAGE CAPACITY : 40 GB
DRIVERS : 52X24X
52X CD 1.44 MB FDD
SOFTWARE ENVIRONMENT:
OPERATING SYSTEM : WINDOW SERVER 2000
RDBMS : SQL SERVER 2000
The Microsoft .NET Framework version 2.0 extends the .NET Framework version 1.1 with new features, improvements to existing features, and enhancements to the documentation. This section provides information about some key additions and modifications.
For more information about compatibility and for a list of the public API modifications to the class library that might affect the compatibility of your application.
64-Bit Platform Support
The new generation of 64-bit computers enables the creation of applications that can run faster and take advantage of more memory than is available to 32-bit applications. New support for 64-bit applications enables users to build managed code libraries or easily use unmanaged code libraries on 64-bit computers. For more information, see 64-bit Applications.
Access Control List Support
An access control list (ACL) is used to grant or revoke permission to access a resource on a computer. New classes have been added to the .NET Framework that allow managed code to create and modify an ACL. New members that use an ACL have been added to the I/O, registry, and threading classes.
ADO.NET
New features in ADO.NET include support for user-defined types (UDT), asynchronous database operations, XML data types, large value types, snapshot isolation, and new attributes that allow applications to support multiple active result sets (MARS) with SQL Server 2005. For more information about these and other new ADO.NET features, see What's New in ADO.NET.
ASP.NET
The Microsoft .NET Framework 2.0 includes significant enhancements to all areas of ASP.NET. For Web page development, new controls make it easier to add commonly used functionality to dynamic Web pages. New data controls make it possible to display and edit data on an ASP.NET Web page without writing code. An improved code-behind model makes developing ASP.NET pages easier and more robust. Caching features provide several new ways to cache pages, including the ability to build cache dependency on tables in a SQL Server database.
You can now customize Web sites and pages in a variety of ways. Profile properties enable ASP.NET to track property values for individual users automatically. Using Web Parts, you can create pages that users can customize in the browser. You can add navigation menus using simple controls.
[attachment=31128]
Introduction of Future Fashion
The FUTURE FASHION Web site is the application that provides customers with online shopping. Through a Web browser, a customer can browse the catalog, place items to purchase into a virtual shopping cart, create and sign in to a user account, and purchase the shopping cart contents by placing an order with a credit card.
The Application is a working demonstration of how to use blueprints principles in a real application design. This document is an online guide to the design and the implementation of the application Enterprise Applications with web technology.
Each release of the application maintains consistent design features such as separating logic and presentation, using web component for control and web pages for presentation, using business components, and so on. high-level design features, this document goes deeper into the implementation details of the current application release.
This document is provided as an online-only resource so that it may be continually extended and updated. This document begins with a description of the separate applications that the sample application comprises, describes the modular structure of the EMAT application, and provides an in-depth description of several pieces of the modules.
• Each FUTURE FASHION module has different requirements from the others. This section describes the requirements, design, and implementation of each module.
• Control module—the control module dispatches requests to business logic, controls screen flow, coordinates component interactions, and activates user sign on and registration. The control module is implemented by the WAF and application-specific WAF extensions.
• Shopping cart module—the shopping cart tracks the items a user has selected for purchase
• Sign on module—the sign on module requires a user to sign on before accessing certain screens, and manages the sign on process
• Messaging module—the messaging module asynchronously transmits purchase orders from the pet store to the OPC
• Catalog module—the catalog module provides a page-based view of the catalog based on user search criteria
• Customer module—the customer module represents customer information: addresses, credit cards, contact information, and so on
Control Module Requirements
The control module forms the framework underlying the application, so it naturally has the most high-level requirements. Extensibility and maintainability are prime considerations in this module. The control module must be extensible because all real-world enterprise applications change constantly. Because the control module plays a role in virtually every interaction, its code must be well-structured to avoid complexity-related maintenance problems. The requirements of the control module are:
• The module must handle all HTTP requests for the application. This module controls a Web application, and interacts with a user who sends HTTP service requests. The control module is responsible for classifying and dispatching each of these requests to the other modules.
• HTTP responses may be of any content type. Web application developers do not want to be limited to just textual content types. The control module must also be able to produce binary responses.
• Business logic must be easily extensible. Enterprise applications are always changing and growing as business rules and conditions change. A developer familiar with the control module should be able easily to add new functionality with minimal impact on existing functions.
• New views must be easy to add. Most business logic changes imply new user views, so developers must be able to create new views easily.
• Module must provide application-wide control of look and feel. Manually editing hundreds or dozens of user views is not a practical way to manage application look and feel. The control module must provide a way for application screen layout and style to be controlled globally.
• Application must be maintainable even as it grows. The control module must be structured so that new functions added over time do not result in a thicket of unmentionable “spaghetti” code. It should be possible to easily understand the control of even an application with several hundred business classes. Application-wide functionality must be easy to add. New application requirements occasionally apply to every operation or view in an application. The control module must be structured so that such requirements can be easily met.
TOOLS, PLATFORM & LANGUAGE TO BE USED
TOOLS:
FRONT-END : ASP.NET(With C# 2.0)
BACK-END : SQL SERVER 2000
PLATFORM:
WINDOW SERVER - 2000.
HARDWARE AND SOFTWARE ENVIRONMENT
HARDWARE ENVIRONMENT:
PROCESSOR : P-IV(1.80 GHZ)
RAM : 128 MB
STORAGE CAPACITY : 40 GB
DRIVERS : 52X24X
52X CD 1.44 MB FDD
SOFTWARE ENVIRONMENT:
OPERATING SYSTEM : WINDOW SERVER 2000
RDBMS : SQL SERVER 2000
The Microsoft .NET Framework version 2.0 extends the .NET Framework version 1.1 with new features, improvements to existing features, and enhancements to the documentation. This section provides information about some key additions and modifications.
For more information about compatibility and for a list of the public API modifications to the class library that might affect the compatibility of your application.
64-Bit Platform Support
The new generation of 64-bit computers enables the creation of applications that can run faster and take advantage of more memory than is available to 32-bit applications. New support for 64-bit applications enables users to build managed code libraries or easily use unmanaged code libraries on 64-bit computers. For more information, see 64-bit Applications.
Access Control List Support
An access control list (ACL) is used to grant or revoke permission to access a resource on a computer. New classes have been added to the .NET Framework that allow managed code to create and modify an ACL. New members that use an ACL have been added to the I/O, registry, and threading classes.
ADO.NET
New features in ADO.NET include support for user-defined types (UDT), asynchronous database operations, XML data types, large value types, snapshot isolation, and new attributes that allow applications to support multiple active result sets (MARS) with SQL Server 2005. For more information about these and other new ADO.NET features, see What's New in ADO.NET.
ASP.NET
The Microsoft .NET Framework 2.0 includes significant enhancements to all areas of ASP.NET. For Web page development, new controls make it easier to add commonly used functionality to dynamic Web pages. New data controls make it possible to display and edit data on an ASP.NET Web page without writing code. An improved code-behind model makes developing ASP.NET pages easier and more robust. Caching features provide several new ways to cache pages, including the ability to build cache dependency on tables in a SQL Server database.
You can now customize Web sites and pages in a variety of ways. Profile properties enable ASP.NET to track property values for individual users automatically. Using Web Parts, you can create pages that users can customize in the browser. You can add navigation menus using simple controls.