Abstract

In Fashion modeling world it is very critical to maintain the information of the models as per the specific schedules upon which they may be called upon. There are many factors and constraints through which a models data is managed. The constraints, which are highly relational, if not stored properly can, generate high level inconsistency within the systems data. The project has the view of distributed architecture, with centralized storage of the database. The application for the storage of the data has been planned. Using the constructs of MS-SQLServer2000 and all the user interfaces have been designed using the ASP.Net technologies.

The database connectivity is planned using the "SQL Connection" methodology. The standards of security and data protective mechanism have been given a big choice for proper usage. The application takes care of different modules and their associated reports, which are produced as per the applicable strategies and standards that are put forwarded by the administrative staff

In Fashion modeling world it is very critical to maintain the information of the models as per the specific schedules upon which they may be called upon. There are many factors and constraints through which a models data is managed. The constraints, which are highly relational, if not stored properly can, generate high level inconsistency within the systems data. At any proper time if the information of a model becomes necessary, the personal information of a model becomes necessary, the personal information of the model along with all the other related areas needs proper projection. To know the availability status of a particular model, is the core challenge in any fashion modeling agency.

The signed contracts of the model as per the agreements at the contractor side and the lock up periods should be known. To keep all this information in a manual system. It is highly complicated and requires more manpower. The information should be highly communicative to keep at least of the properties like consistency, reliability and authenticated

Proposed System:

The general description gives an "executive overview" and is very client-oriented. It expounds on the functional and data requirements of the application. It also lists the limitations, assumptions and dependencies of the application. It also touches on the performance and quality requirements of the application and provides a solid definition of the interface

The total number of modules that were identified within the project are as follows:

•  General user module

•  Clients module

Administrators module

<< back