Sds astrology

Software Design Specification

Online AstroSoftware Design SpecificationDate of Submission : 12th November 2014Submitted by:

Meghana Aggarwal

08724302012

3rd Sem (Evening)

ABSTRACT

This project is on ASTROLOGY having 3 users Admin, Customer, and Guest.

Admin can modify the details of the customers account, modify the prediction details

Customer can edit their profile information, view basic details, love compatibility, daily, monthly, yearly predictions, death predictions, birth stone, know the sign according to the Indian horoscope of his own or any other by his sign, view basic details, love compatibility, daily, monthly, yearly predictions, birth stone, know the sign, know about feng shui & year of horse according to the Chinese Astrology of his own or any other by his sign, view basic details according to the number. Also can get the lucky number, get the fortune number by entering the details, and view the basic details and predictions by tarot card reading.

Guest can view basic details, love compatibility, daily, monthly, yearly predictions, death predictions, birth stone, know the sign according to the Indian horoscope of his own or any other by his sign, view basic details, love compatibility, daily, monthly, yearly predictions, birth stone, know the sign, know about feng shui & year of horse according to the Chinese Astrology of his own or any other by his sign, view basic details according to the number. Also can get the lucky number, get the fortune number by entering the details, and view the basic details and predictions by tarot card reading.TABLE OF CONTENT

TOPICSPAGE NO.

Acknowledgement2

Certificate3

Chapter 1:SYNOPSIS

1.1 Introduction 1.2 Objectives

1.3 Scheduling of activities

1.4 Conclusion

1.5 Achievement till date

1.6 Remaining work

1.7 Solution of problem

Chapter 2: SRS

2.1 Introduction

2.1.1Purpose

2.1.2Document Conventions

2.1.3Intended Audience and Reading Suggestions

2.1.4Project Scope

2.1.5References

2.2Overall Description

2.2.1Product Perspective

2.2.2Product Features

2.2.3User Classes and Characteristics

2.2.4Operating Environment

2.2.5Design and Implementation Constraints

2.2.6User Documentation

2.2.7Assumptions and Dependencies

2.3System Features

2.3.1Viewing Properties

2.3.2Adding of Proprety

2.3.3Register

2.3.4Login In

2.3.5Logout

2.4.External Interface Requirements

2.4.1User Interfaces

2.4.2Hardware Interfaces

2.4.3Software Interfaces

2.4.4Communications Interfaces

2.5Other Nonfunctional Requirements

2.5.1Performance Requirements

2.5.2Safety Requirements

2.5.3Security Requirements

2.5.4Software Quality Attributes

Appendix A: Glossary

Appendix B: Analysis Models

Chapter3: SDS

3.41.Revision History

3.42. Approved By

3.53. Introduction

63.1 Document Outline

73.2 Document Description

73.2.1 Introduction

83.2.2 System Overview

3.84. Design Considerations

84.1 Assumptions and Dependencies

84.2 General Constraints

94.3 Goals and Guidelines

94.5 Development Methods

3.95. Architectural Strategies

3.116. System Architecture

116.1 Subsystem Architecture

3.127. Policies and Tactics

3.138. Detailed System Design

3.138.1 Classification

3.138.2 Definition

3.138.3 Responsibilities

3.138.4 Constraints

3.148.5 Composition

3.148.6 Database Design

3.148.7 Table schemas

3.158.8 Class Diagrams and Classes

3.158.9 Uses/Interactions

3.158.10 Resources

3.158.11 Processing

3.168.12 Interface/Exports

3.168.13 Detailed Subsystem Design

3.169. Source Code Details

3.1610. Output

Chapter 4: 164.1. Glossary

174.2 . Bibliography

1. Revision History

VersionNameReason For ChangesDate

1.0Initial Revision

2. Approved By

Approvals should be obtained from faculty/ HODNameSignatureDepartmentDate

Bill CurrieBP-IT-Development

1.1 INTRODUCTION

This project provide the user to see the basic details & different predictions like, basic details, compatibility test, daily, yearly, monthly predictions etc, according to the Indian, Chinese Astrology, Numerology, Tarot Reading . Also the user can manage the account details & the admin can modify different details.

1.2 TITLE OF PROJECT

I have given tittle to my project as ASTROLOGY because it shows various predictions and various solutions to the customer according to the various types of astrology.

1.3 OBJECTIVESThere are many objectives behind the idea of this website:

Provide the user to know about him and predictions about himself by knowing the predictions.

Provide them proper predictions so that they can manage their day accordingly

Providing the user predictions based on different criteria according to different astrology

1.4 SCHEDULE OF ACTIVITIES

SNO.ACTIVITYDATE SCHEDULED

1.Research on the projectAug 1, 2014 Aug 15, 2014

2.Analyzing and gathering of the dataAug 15, 2014-Aug 20, 2014

3.SynopsisAug 25, 2014- Aug 29, 2014

4.Designing of modulesAug 25, 2014- Sept 5, 2014

5.Database creation and connectivitySept 5, 2014-Sept 10, 2014

6.Preparation of SRSSept 10, 2014-Sept 19, 2014

7.Testing Sept 19, 2014-Sept 25, 2014

8.ReportSept 25, 2014-Oct 10, 2014

1.5CONCLUSION

I have included the Abstract, Introduction , Revision History, Objectives, Schedule of activities, Conclusion, Achievement till date, Remaining works

From the above things my project has been approved by my guide .

1.6 ACHEIVEMENT TIL DATESNO.ACTIVITYDATE SCHEDULED

1.Research on the projectAug 1, 2014 Aug 15, 2014

2.Analyzing and gathering of the dataAug 15, 2014-Aug 20, 2014

3.SynopsisAug 25, 2014- Aug 29, 2014

4.Started designing of modulesAug 25, 2014

1.7 REMAINING WORKSSNO.ACTIVITY DATE

4.Designing of modulesAug 25, 2014- Sept 5, 2014

5.Database creation and connectivitySept 5, 2014-Sept 10, 2014

6.Preparation of SRSSept 10, 2014-Sept 19, 2014

7.Testing Sept 19, 2014-Sept 25, 2014

8.ReportSept 25, 2014-Oct 10, 2014

1.8 ENTITY-RELATIONSHIP DIAGRAM

2.1 Introduction

2.1.1 Purpose

The software described in this document is the Online Astro website (Version 1.0) and associated support pages. This document seeks to provide the Software Requirements Specifications for the website. The purpose of this document is to record the requirements for the design and development of Online Astro Website. The document reflects the current requirements of the project as understood by the project team. This document presents an initial description of the various functionalities and services provided by the software. The document will also serve the basis for acceptance testing by the user.

The scope of the website is not only limited to future predictions and encouraging personal, compatibility like predictions too.

2.1.2 Document Conventions

There are no standard document requirements for this document.

2.1.3 Intended Audience and Reading Suggestions

Primary readers of this document are the web designer contributing to and testing of the Online Astro website. Secondary reader is my guide. The remaining sections of this SRS describe the functional requirements for online astro website.

2.1.4 Project Scope

The scope of the website is to provide a high user friendly set of web pages that are easy to navigate and at the same time provides sufficient and depth prediction about user.

Three potential groups of viewers exist:

1. User who have already logged in interested in viewing predictions about him.

2. Guest who have not logged in but want to see the predictions.

3. Admin who can modify predictions and view details of different user.

The goal of website is to give the users different predictions for them so that they can improve their futures.

Maintaining a user friendly site that is deemed of highest importance in order to hold user attention and guide the viewer to information that will lead to a decision for future.

Benefits for using the site should include:

Personal information about the user defining different characteristics.

Future predictions of user for their better futures.

Love compatibility, Career predictions etc for different user accordingly.

This site does not restrict to one astrology type and give different types of predictions through different ways of astrology.

2.1.5 References

http://www.trustedtarot.com

http://www.psychic-revelation.com/reference/q_t/tarot/tarot_cards/ http://www.horoscope.com

http://www.google.co.in

2..2 Overall Description

2.2.1 Product Perspective

Online Astro is a self-contained product. It has no earlier versions. This is version 1.0 and further 2.0 can be made by adding the modules of kundli generation, shopping or incorporate ideas learned from version 1.

Website is aimed toward users who have their interest in astrology predictions and want to work accordingly.

Website should be user-friendly, quick to learn for the above purpose.

2.2.2 Product Features

Major features of the website include the following pages/subsections:

Horoscope

Basic Features and characteristics

Positive and negative qualities

Birthstone

Daily Predictions

Love compatibility

Chinese Astrology

Basic Features and characteristics

Birthstone

Love compatibility

Daily Predictions

Information about horse year and Feng Shui

Numerology

Basic traits

Compatible numbers

Know your lucky number

Daily Predictions

Tarot Reading

Basic predictions

Testimonials

Information about persons whom we are thankful to for this website

About Us

It specifies the aim of website

It specifies the qualities and uniqueness of website, including the details and pros that why one should opt this website and not any other

2.2.3 User Classes and Characteristics

This project is on ASTROLOGY having 3 users Admin, Customer, and Guest.

Admin can modify the details of the customers account, modify the prediction details

Customer can edit their profile information, view basic details, love compatibility, daily, monthly, yearly predictions, death predictions, birth stone, know the sign according to the Indian horoscope of his own or any other by his sign, view basic details, love compatibility, daily, monthly, yearly predictions, birth stone, know the sign, know about feng shui & year of horse according to the Chinese Astrology of his own or any other by his sign, view basic details according to the number. Also can get the lucky number, get the fortune number by entering the details, and view the basic details and predictions by tarot card reading.

Guest can view basic details, love compatibility, daily, monthly, yearly predictions, death predictions, birth stone, know the sign according to the Indian horoscope of his own or any other by his sign, view basic details, love compatibility, daily, monthly, yearly predictions, birth stone, know the sign, know about feng shui & year of horse according to the Chinese Astrology of his own or any other by his sign, view basic details according to the number. Also can get the lucky number, get the fortune number by entering the details, and view the basic details and predictions by tarot card reading.

2.2.4 Operating Environment

Development Requirements :

Software Requirements:

OS : Window XP Professional, 7 or higher

Visual Studio 2010 or higher

SQL Server 2008

Hardware Requirements:

Processor

-Intel Pentium IV

Cache Memory- 1MB

Hard disk

- 250 GB

Deployment Requirements :

Software Requirements:

OS : Window XP Professional, 7 or higher

Web browser(IE, Mozilla , etc.)

Hardware Requirements:

Processor

-Intel Pentium IV

Cache Memory- 1MB

Hard disk

- 250 GB

2.2.5 Design and Implementation Constraints

This program is created using Asp.net with C# programming language and uses the Qt4 libraries for the main modules. So a minimum PC having at least 64mb of RAM and CPU over 400MHz is required to run the program with good speed. Also the program uses at least 15 megabytes of hard disk space to store the program libraries. An installer is used to unpack them all in an install wizard.

For language support only English language packs can be enabled within the program.

For the connection stream Tcp-Ip is used as its the common gateway for internet applications.

The program is provided AS IT IS with ABSOLUTELY NO WARRANTY OF ANY KIND as noted in the official project website.

User Documentation

Here are the official links of the project where you can retrieve more information about it and

download the latest version:

http://localhost.com

2.2.6 Assumptions and Dependencies

For creating the windows forms and setting up the core program Trolltech Qt framework and

classes was used that offers a complete set of tools for developing cross platform projects and a

language editor for additional translations. For better understanding the know-what to do rather than

the know-how to do it we assume that the reader is not interested for knowing how to create and

design windows forms and how the program is coded at that time.

2.3 System Features

The following are the major features provided by the system.

2.3.1 HOME::REQ1

2.3.1.1Description and Priority

This allows a user to navigate to the different astrology to proceed further or login or could see about the website, its testimonials and contact details.

Priority level = Low

2.3.1.2Stimulus/Response Sequences

The user clicks login link to go to the login page.

The user clicks to about us, testimonials or contact us button to go to the particular page.

The user clicks to services button to go to services provided by the website.

2.3.2 USER REGISTRATION::REQ2

This allows a user to be a member of the website and enables him to see predictions particularly for himself. This is an essential part of the system of high priority as it adds new customer to the buyers of website.

Priority level = High

The user selects the sign up link to get the registration form and after following the instruction fills in the required information to create his/her profile.

Client side validation will be done for checking provided information.

The user will be asked for a login and password

After client side validation for uniqueness an activation link will be sent by mail.

On activation the user is now registered to the website.

2.3.2.3 Functional Requirements

Includes REQ1

Specializes:REQ1

Connected By: REQ3

2.3.3 LOGIN::REQ3

This allows a user to login to his account.

The user enters the id and password.

The guest is admitted as a user and can see the personalized predictions.

Includes REQ1

Specializes:REQ1, REQ2

Connected By : REQ4, REQ5, REQ6, REQ7, REQ8, REQ9, REQ10, REQ11, REQ12, REQ13, REQ14, REQ15, REQ16, REQ17, REQ18

2.3.4 HOROSCOPE::REQ4

This allows a user to see his predictions according to the Indian astrology. It also allows the user to see for love compatibility and predictions for other Indian astrology signs too.

3.4.2Stimulus/Response Sequences

The user selects the horoscope link and click for the type of details he wants.

Then the user selects the prediction like love compatibility, daily prediction etc.

Then he either can click the personal button for personal intro or can click any sign for particular info.

Includes REQ1, REQ3

Connects:REQ4, REQ5, REQ6, REQ7, REQ8, REQ9, REQ10, REQ15, REQ16

Connected by:REQ1, REQ3

2.3.5 LOVE COMPATIBILITY::REQ5

This allows a user to see his compatibility with other signs of horoscope.

The user either selects his sign or logs in to proceed.

The user selects the sign of the partner to get the prediction.

Extends:REQ4

Connected by:REQ4

Connects:REQ3

2.3.6 CAREER PREDICTION::REQ6

This allows a user to see his career prediction.

The user can see predictions related to his career.

Extends:REQ4

Connected by:REQ4

Connects:REQ3

2.3.7 DEATH PREDICTION::REQ7

This allows a user to see his predicted date and time of death.

The user either fills the several details or logs in.

The user gets the predicted date of his death.

Extends:REQ4

Connected by:REQ4

Connects:REQ3

2.3.8 DAILY PREDICTION::REQ8

This allows a user to see his prediction of the day according to his horoscope.

The user gets the daily prediction.

Extends:REQ4

Connected by:REQ4

Connects:REQ3

2.3.9 MONTHLY PREDICTION::REQ9

This allows a user to see his prediction of the month according to his sign of horoscope.

The user gets the monthly prediction.

Extends:REQ4

Connected by:REQ4

Connects:REQ3

2.3.10 CHINESE ASTROLOGY::REQ10

This allows a user to see his predictions according to the Chinese astrology. It also allows the user to see for love compatibility and predictions for other Chinese astrology signs too.

The user selects the horoscope link and click for the type of details he wants.

Then the user selects the prediction like love compatibility, daily prediction etc.

Includes REQ3

Connects:REQ1, REQ3, REQ4, REQ12, REQ13, REQ14, REQ15, REQ16

Connected by:REQ1

2.3.11 LOVE COMPATIBILITY::REQ11

This allows a user to see his compatibility with other Chinese astrology sign.

The user selects the sign of the partner to get the prediction.

Includes REQ1

Extends:REQ10

Connected by:REQ10

2.3.12 DAILY PREDICTION::REQ12

This allows a user to see his prediction of the day according to his Chinese Astrology sign.

The user gets the daily prediction.

Includes REQ1

Extends:REQ10

Connected by:REQ10

2.3.13 MONTHLY PREDICTION::REQ13

This allows a user to see his prediction of the month according to his sign of Chinese astrology.

Extends:REQ10

Connected by:REQ10

Connects: REQ3

2.3.14 YEARLY PREDICTION::REQ14

This allows a user to see his prediction of the month according to his sign of Chinese astrology.

Extends:REQ10

Connected by:REQ10

Connects : REQ3

2.3.15 NUMEROLOGY::REQ15

This allows a user to see his predictions according to the Numerology. It also allows the user to see predictions for other numbers too.

The user selects the Numerology link and click for the type of details he wants.

The user can also know lucky number by entering the date of birth.

Specializes:REQ1

Connected by:REQ1

Connects : REQ1, REQ3, REQ4, REQ10, REQ16

2.3.16 TAROT READING::REQ16

This allows a user to see his predictions according to the randomly generated tarot cards.

The user selects the Tarot card link.

Then the user clicks on the blank cards to generate a combination.

Accordingly it gives the prediction for the user.

Specializes:REQ1

Connected by:REQ1

Connects : REQ1, REQ3, REQ4, REQ10, REQ15

2.4 External Interface Requirements

2.4.1 HOME

User Interfaces

Web browser

Hardware Interfaces

Monitor : to see the interface

Modem : to connect internet

MOUSE : to click the button

Ram : to load page

Software Interfaces

.NET Framework .NET is a framework that covers all the layers of software development from the operating system up. It provides the richest level of integration among presentation technologies, component technologies and data technologies. The entire architecture has been created to make it as easy to develop Internet applications, as it is to develop for the desktop environment. (All REQs) ASP.NET ASP.NET is the language used to build classes, retrieve and manipulate data, and handle events. (All REQs) Front Page and Microsoft Visual Interdev - are the key tools for supporting site development.Communications Interfaces

Client on internet will be using HTTP/HTTPS protocols

Client on intranet will be using TCP/IP protocol

2.4.2 USER REGISTRATION

User Interfaces

Web browser

Hardware Interfaces

Keyboard : to enter values

Ram : to load page

Software Interfaces

Windows 2007 Server Windows 2007 server provides the core security, TCP/IP functionality and other fundamental requirement for a web operating system.

Internet Information Server (IIS) Internet Information Server supports the core web server functionality.

.NET Framework It provides the richest level of integration among presentation technologies, component technologies and data technologies.

ASP.NET ASP.NET is the language used to build classes, retrieve and manipulate data, and handle events.

Front Page and Microsoft Visual Interdev - are the key tools for supporting site development. SQL Server 2008 - SQL server 2008 is used to store and manipulate database.Communications Interfaces

2.4.3 LOGIN

User Interfaces

Web browser

Hardware Interfaces

Keyboard : to enter values

Ram : to load page

Software Interfaces

2.4.4 HOROSCOPE

User Interfaces

Web browser

Hardware Interfaces

MOUSE : to click the button, link etc.

Ram : to load page

Software Interfaces

ASP.NET ASP.NET is the language used to build classes, retrieve and manipulate data, and handle events. Front Page and Microsoft Visual Interdev - are the key tools for supporting site development.Communications Interfaces

2.4.5 LOVE COMPATIBILITY

User Interfaces

Web browser

Hardware Interfaces

Mouse : to click the button

Ram : to load page

Software Interfaces

2.4.6 CAREER PREDICTION

User Interfaces

Web browser

Hardware Interfaces

Ram : to load page

Software Interfaces

2.4.7 DEATH PREDICTION

User Interfaces

Web browser

Hardware Interfaces

Ram : to load page

Software Interfaces

2.4.8 DAILY PREDICTION

User Interfaces

Hardware Interfaces

Ram : to load page

Software Interfaces

2.4.9 MONTHLY PREDICTION

User Interfaces

Web browser

Hardware Interfaces

Ram : to load page

Software Interfaces

2.4.10 CHINESE

User Interfaces

Web browser

Hardware Interfaces

Ram : to load page

Software Interfaces

2.4.11 LOVE COMPATIBILTY

User Interfaces

Web browser

Hardware Interfaces

Ram : to load page

Software Interfaces

2.4.11 DAILY PREDICTION

User Interfaces

Web browser

Hardware Interfaces

Ram : to load page

Software Interfaces

2.4.12 MONTHLY PREDICTION

User Interfaces

Web browser

Hardware Interfaces

Ram : to load page

Software Interfaces

2.4.14 YEARLY PREDICTION

User Interfaces

Web browser

Hardware Interfaces

Ram : to load page

Software Interfaces

2.4.15 NUMEROLOGY

User Interfaces

Web browser

Hardware Interfaces

Ram : to load page

Software Interfaces

2.4.16 TAROT READING

User Interfaces

Web browser

Hardware Interfaces

Ram : to load page

Software Interfaces

2.5 Other Nonfunctional Requirements

Here we specify some nonfunctional constraints that the program satisfies in order to be more

concrete and stable.

2.5.1 Performance Requirements

The application must allow for scheduled maintenance times where server will be interrupted

The application must keep a backup record of predictions, user, and notifications for users.

The application must have an intuitive interface designed for the general public

User must be able to access the website from any reputable Internet Browsers (i.e. Chrome, Firefox, and Opera).

2.5.2 Safety Requirements

Consistency: checking the fact that all clients must be attachable to one server, so there would

be appropriate control of the test statistics and information.

Also in case of a potential loss of connection between the client and the server the clients test

progress so far is lost. When the client finishes its test (by pressing the finish button) then its

progress is sent to the server and be logged. In case of a potential server breakdown only the so far

finished tests are saved to the log file.

2.5.3 Security Requirements

This program uses object oriented mechanisms to protect its data passed using methods

Also there is no currently a security schema of this program. Thus the log files that are being created

are readable using a simple text reader.

2.5.4 Software Quality Attributes

Practability The system must be stable and can be operated by the people with average intelligence.

Efficiency This involves accuracy, timeliness and comprehensiveness of the system output.

Cost It is desirable to aim for a system with a minimum cost subject to the condition that it must satisfy all requirements.

Flexibility The system should be modified depending on the changing needs of the user. Such modification should not entail extensive reconstructing or recreation.

3.1 . Introduction

The following is an attempt to put together a complete, yet reasonably flexible template for the specification of software designs. Wherever possible, I have tried to provide guidelines (instead of prescribing requirements) for the contents of various sections and subsections of the document. Some may prefer to require more detailed subsections of a particular section, choosing one or more of the subsection topics from the list of guidelines provided. In this sense, this document is really a template for a template.

It is my desire that a completed software design specification meet the following criteria:

It should be able to adequately serve as training material for new project members, imparting to them enough information and understanding about the project implementation, so that they are able to understand what is being said in design meetings, and won't feel as if they are drowning when they are first asked to create or modify source code.

It should serve as "objective evidence" that the designers and/or implementers are following through on their commitment to implement the functionality described in the requirements specification.

It needs to be as detailed as possible, while at the same time not imposing too much of a burden on the designers and/or implementers that it becomes overly difficult to create or maintain.3.1.1 Document Outline

This document will cover all the necessary details related to the designing specifications of the software. 3.2 Document Description

Here is the description of the contents (by section and subsection) of the proposed software for software design specifications:

3.2.1 Introduction

The software Online Astro provides the different types of predictions to all the users depending upon their details. It gives the predictions for Chinese, western astrology, numerology, tarot card reading etc.

This project gives the predictions to the users according to the details entered. The user can take different precaution for a better future and know what to do in different aspects. Also can see the basic predictions and their capabilities of which they are not known and can improve themselves. This document is used by software designer and reviewed by the customer. Main modules are : Login Form

Registration form

Western Astrology Chinese astrology Numerology Tarot Card Reading

3.2.2 System Overview

The software Online Astro provides the different types of predictions to all the users depending upon their details. It gives the predictions for Chinese, western astrology, numerology, tarot card reading etc. It also includes basic love compatibility checking along with the death prediction, simple theories of different aspects etc.3.4. Design Considerations

This section describes many of the issues which need to be addressed or resolved before attempting to devise a complete design solution.

3.4.1 Assumptions and Dependencies

The predictions are general. The user can see their prediction at any time by just entering the details.3.4.2 General Constraints

SQL Server 2008 used as DBMS because it support wide range of user access at same time.SQL Server has designed to help provide the highest level of security for enterprise data through features such as database encryption, more secure default settings, password policy enforcement, granular permissions control, and an enhanced security model Visual studio used as frontend using c# which is Microsofts brand new language, designed for its brand new platform, the DOT NET framework. C# is a very elegantly designed language, which encourages good programming practice in regard to OOPS programming. C# is descended directly from the powerful but complex C++ language, and inherits most of the power without the complexity. C# is a platform independent language that supports transparent web browser.

3.4.3 Goals and Guidelines

The website efficiently reduces man work and provides easy, quick and global access to the various details and predictions.Also the man have not to go to the astrologer to get the details and is easy to access.

The user must have the following characteristics. :

User details : His details like name date of birth etc. 3.4.4 Development Methods

The establishment and use of sound engineering principles in order to obtain economically developed software that is reliable and works efficiently on real machines is called software engineering.

Software engineering is the discipline whose aim is:

Production of quality software

Software that is delivered on time

Cost within the budget

Satisfies all requirements

Software process is the way in which we produce the software. Apart from hiring smart, knowledgeable engineers and buying the latest development tools, effective software development process is also needed, so that engineers can systematically use the best technical and managerial practices to successfully complete their projects.

A software life cycle is the series of identifiable stages that a software product undergoes during its lifetime. A software lifecycle model is a descriptive and diagrammatic representation of the software life cycle. A life cycle model represents all the activities required to make a software product transit through its lifecycle phases. It also captures the order in which these activities are to be taken.LIFE CYCLE MODELS

There are various life cycle models to improve the software processes.

WATERFALL MODEL

PROTOTYPE MODEL

ITERATIVE ENHANCEMENT MODEL

EVOLUTIONARY MODEL

SPIRAL MODEL

In the project, Waterfall model is followed.

Feasibility Study

Requirement Analysis and Specification

Design

Implementation and Unit Testing

Integration and System Testing

Maintenance

WATERFALL MODEL

This model contains 6 phases:

Feasibility studyThe feasibility study activity involves the analysis of the problem and collection of the relevant information relating to the product. The main aim of the feasibility study is to determine whether it would be financially and technically feasible to develop the product.

Requirement analysis and specificationThe goal of this phase is to understand the exact requirements of the customer and to document them properly. (SRS)

DesignThe goal of this phase is to transform the requirement specification to a structure that is suitable for implementation in some programming language.

Implementation and unit testing During this phase the design is implemented. Initially small modules are tested in isolation from rest of the software product.

Integration and system testingIn this all the modules are integrated and then tested altogether.

Operation and maintenanceRelease of software inaugurates the operation and life cycle phase of the operation.

3.5. Architectural Strategies

3.5.1 Module design

The system design shows how Software will be structured to satisfy the requirements identified during the analysis phase. The design process is a translation of requirements into a description of the software structure, software components, interfaces and data necessary for the implementation phase. The design phase provides a complete blueprint for the implementation activity.

System analysis begins by identifying the reports and the other outputs the system will produce. Then the specific on each are pin pointed. Usually, designers sketch the form or display as they expect it to appear when the system is complete. This may be done, on a paper or computer display, using one of the automated tools available. The system design also describes the data to be the input, calculated or stored. Individual data items and calculation procedures are written in detail. The procedures tell how to process the data and produce the output. The proposed system contains the following main module processes: -

The user, property dealer, property & employee registration and login: -This process has different faces when its come to registration for user, property, property dealer & employee. Registration is needed for the user and dealer to list their property and get the information about the property required. This registration is being done by the user and dealer directly from the website. After the registration process a unique login id will be given to the user and dealer. Employee registration is login dependent which will be done either by another employee or directly by the administrator.

Registration

A guest can register to become a user an easily access his predictions more fastly. A validation process automatically checks all the constraint regarding registration whenever a change at client side occurs to update the server side.

Login table is maintained for users and administration.

As the system is candidate dependent so proper user id and password based candidate system is necessary to accomplish the fact. Whatever and however the system is to maintain the candidate status and specific user enabled services as well as to track the candidates surfing for security and privacy reason.

Based on the login and the access rights granted by the administrator he is linked to the appropriate page. If the user is not registered on the site, he is linked to the Registration page.

A login status and log is maintained to find who and from where login-ed for which purpose and also to find the number of time a user logins.

Astrology

It shows all the varities of prediction done through western way of astrology like basic predictions, love match etc.

Chinese astrology

The Chinese predictions are shown in this module like the compatibility, basic predictions, strengths and weaknesses etc.Numerology

Different predictions according to the number of the user is shown along with the lucky number and all the other predictions one can get.Tarot Card Reading

Gets different prediction and many answers through random generation of the tarot card.

3.5.2Testing Method

System testing is done to find discrepancies between the system and its original objective, current specifications and system documentation. For each project, testing is done at every stage. Testing need is where errors remaining from all the previous phase must be detected. Hence testing performs a very critical role for quality assurance and for ensuring the reliability of software. During testing, the program to be tested is executed with a set of test cases and is evaluated to determine if the program performs as expected.

Some of the commonly used terms associated with testing are explained briefly in following lines:

a. Error=Error refers to the difference between actual output of software and the correct output. In this interpretation, error is essentially a measure of the difference between the actual and the ideal.

b. Fault=Fault is a condition that causes a system to perform a required function. A fault is the basic reason for software malfunction and is synonymous with the commonly used term bug.

c. FailureFailure is inability of a system to perform a required function according to its specifications. A software failure occurs if the behavior of the software is different from specified behavior.

6. System Architecture

About System Architecture

Examination system was helpful to separate teaching and testing. It promoted teacher to make the lesson planning and teach into class carefully it was also an important means of evaluating the teaching effect otherwise its stimulated student to conscientiously study and attend a lecture , to do their homework independently therefore the Online examination system could improve teaching level by providing better technical support the online examination system also provide online testing capability for student students could log in the system any time , test themselves , understand their learning level ,adjust their learning progress.

DATA FLOW DIAGRAM

A DFD also known as bubble chart , has the purpose of clarifying system requirements and identifying major transformations. It shows the flow of data through a system. It is a graphical tool because it presents a picture. The DFD may be partitioned into levels that represent increasing information flow and functional detail. Four simple notations are used to complete a DFD. These notations are given below:-

DATA FLOW

The data flow is used to describe the movement of information from one part of the system to another part. Flows represent data in motion. It is a pipe line through which information flows. Data flow is represented by an arrow.

PROCESS

A circle or bubble represents a process that transforms incoming data to outgoing data. Process shows a part of the system that transforms inputs to outputs.

PROCESS

EXTERNAL ENTITY

A square defines a source or destination of system data. External entities represent any entity that supplies or receives information from the system but is not a part of the system.

EXTERNAL ENTITY

ENTITY

DATA STORE

The data store represents a logical file. A logical file can represent either a data store symbol which can represent either a data structure or physical file on disk. The data store is used to collect data at rest or a temporary repository of data. It is represented by open rectangle.

OUTPUT

The output symbol is used when a hard copy is produced and the user of the copies cannot be clearly specified or there are several users of the output.

OUTPUT

Level 0 :-

Level 1:-

Level 2:-

2.1.1 :

2.1.2 :

2.2.1 :

2.2.2 :

2.2.3 :

2.3.1 :

2.3.2 :

3.8. Detailed System Design

The application will have a user friendly and menu based interface. It will have a login screen for entering user-name, password will be provided. Access to different screens will be based upon the user. There is a screen for displaying information regarding entries to be made by admin and broker. There is a screen for displaying information regarding filling of property details by in broker. There is a screen for displaying information regarding all types of property. There is a screen for displaying the information while deleting or adding property. There is a screen for displaying property details when they are view and purchase property . There is a screen for selling property to buyer .

3.8.1 Classification

Web browser was used as client asp.net as the business logic tier to achieve its function, and database as the data layer:

ClientClient was web browser which implemented the systems display logic. The function was to send request to web server through the web browser by user (buyer and dealer). While web server returns the requested html pages or html pages dynamically generated to the client, which were showing the web browser.

Business logic tierIt was achieved mainly by asp.net. It responded to the client request and achieved the business logic with the web server.

Data tierIt was realised with database system, use to store the business data such as property information and control data such as user data SQL server was used to achieve the data tier.3.8.2 Definition

The specific purpose and semantic meaning of the component. This may need to refer back to the requirements specification.

3.8.3 Responsibilities

The primary responsibilities and/or behavior of this component. What does this component accomplish? What roles does it play? What kinds of services does it provide to its clients? For some components, this may need to refer back to the requirements specification.

3.8.4 Constraints

Any relevant assumptions, limitations, or constraints for this component. This should include constraints on timing, storage, or component state, and might include rules for interacting with this component (encompassing preconditions, post conditions, invariants, other constraints on input or output values and local or global values, data formats and data access, synchronization, exceptions, etc.)

3.8.5 Composition

A description of the use and meaning of the subcomponents that are a part of this component.

3.8.6 Database Design

The database design specifies how the date of the software is going to be stored.

3.8.7 Table schemas

The complete (compliable) set of CREATE TABLE statements (and other SQL statements) that declare the database schema, including integrity constraints, domain specifications, assertions, and access privileges -- documented in a template with the intended use of each table and column.

Different tables used:TABLE 1. LOGIN

COLUMN NAMEDATA TYPE LENGTH KEY CONSTRAINTSDESCRIPTION

UerIDNvarchar50Primary KeyThis field is used as the key against all the tables, therefore should be Unique.

Passnvarchar 20The password specified by the user during registration.

UserTypeNvarchar20This specifies type of user i.e., Admin or user

TABLE 2. USER REGISTRATION

userIdNvarchar50Primary KeyThis field is used as the key against all the tables, and therefore Unique.

firstNameNvarchar100Stores firve st name of the user

lastNameNvarchar50Stores last name of the user

bdateNvarchar50Birth date of the user

bmonthNvarchar50Month of birth of the user

byearNvarchar50Year of birth of the user

genderNvarchar10Gender of the user

contactNvarchar50 Contact details of the user

emailNvarchar50Email address of the user

secQuesNvarchar100Security question by the user

secAnsNvarchar50Security answer given by the user

horoscopeSignNvarchar50Horoscope sign of the user

chineseSignNvarchar50Chinese sign of the user

TABLE 3. ADMIN DETAILSCOLUMN NAMEDATA TYPE LENGTH KEY CONSTRAINTSDESCRIPTION

adminIdNvarchar50Primary KeyThis field is used as the key against all the tables, and therefore Unique.

firstNameNvarchar100Stores first name of the user

lastNameNvarchar50Stores last name of the user

ContactNvarchar50Birth date of the user

EmailNvarchar50Month of birth of the user

GenderNvarchar50Year of birth of the user

DobNvarchar10Gender of the user

departmentNvarchar50 Contact details of the user

TABLE 4. ASTRO COMPATIBILITY

Colornvarchar40Color

Keywordnvarchar40Keyword

quickInterpretnvarchar1000Prediction in short

Detailnvarchar2000Detailed prediction

yinYangnvarchar2000Yin and yang

yinYinnvarchar2000Yin and yin

TABLE 5. HOROSCOPECOLUMN NAMEDATA TYPE LENGTH KEY CONSTRAINTSDESCRIPTION

Hsignnvarchar40Horoscope sign

Elementnvarchar1000Element of the sign

Planetnvarchar1000Planet of the sign

Symbolnvarchar1000Symbol of the sign

Stonenvarchar1000Stone of the sign

lifePersuitnvarchar1000Life persuit of the sign

Vibrationnvarchar1000Vibration of the sign

secretDesirenvarchar1000Secret desire of the sign

physicalTraitsnvarchar1000Physical traits of the sign

bodyPartnvarchar1000Main body parts

Dualitynvarchar1000Duality of the sign

Modalitynvarchar1000Modality of the sign

keywordsnvarchar1000Keywords of the sign

Colornvarchar1000Color of the sign

Housenvarchar1000House of the sign

Strengthnvarchar2000Strength of the sign

weaknessnvarchar2000Weakness of the sign

independencenvarchar-1Independence prediction of the sign

friendshipnvarchar-1Friendship prediction of the sign

Businessnvarchar-1Business prediction of the sign

temperamentnvarchar-1Temperament prediction of the sign

deepInsidenvarchar-1Deep inside prediction of the sign

Nutshellnvarchar-1Nutshell prediction of the sign

Womannvarchar-1Woman prediction of the sign

Mannvarchar-1Man prediction of the sign

dailyPredictionnvarchar-1Daily prediction of the sign

monthlyPredictionnvarchar-1Monthtly prediction of the sign

yearPredictionnvarchar-1Yearly prediction of the sign

Ariesnvarchar40Compatibility of the sign with aries

Taurusnvarchar40Compatibility of the sign with Taurus

Gemininvarchar40Compatibility of the sign with Gemini

Cancernvarchar40Compatibility of the sign with cancer

Leonvarchar40Compatibility of the sign with leo

Virgonvarchar40Compatibility of the sign with virgo

Libranvarchar40Compatibility of the sign with libra

Scorpionvarchar40Compatibility of the sign with scorpio

Sagitariusnvarchar40Compatibility of the sign with sagitarius

Capricornnvarchar40Compatibility of the sign with Capricorn

Aquariusnvarchar40Compatibility of the sign with aquarius

Piscesnvarchar40Compatibility of the sign with pisces

TABLE 6. ChineseCOLUMN NAMEDATA TYPE LENGTH KEY CONSTRAINTSDESCRIPTION

Csignnvarchar20Chinese sign

predictionnvarchar-1General prediction of the sign

Strengthnvarchar-1Strength prediction of the sign

weaknessnvarchar-1Weakness prediction of the sign

Earthynvarchar100Earthy sign prediction of the sign

wuXingnvarchar100wuXing prediction of the sign

yinYangnvarchar100yinYang prediction of the sign

directionsnvarchar100Directions prediction of the sign

Colornvarchar200Color prediction of the sign

avoidColornvarchar200Color that should be avoided

Numbernvarchar100Number prediction of the sign

avoidNumbernvarchar100Number that shoud be avoided

Flowernvarchar1000Flower prediction of the sign

compSignsnvarchar1000Compatible signs

avoidSignsnvarchar1000Avoidable signs

Celebsnvarchar-1Ceebraties having same sign

fotune2014nvarchar-1fotune2014 prediction of the sign

career2014nvarchar-1career2014 prediction of the sign

wealth2014nvarchar-1wealth2014 prediction of the sign

relation2014nvarchar-1relation2014 prediction of the sign

health2014nvarchar-1health2014 prediction of the sign

TABLE 7. NUMEROLOGY

Numberint4Number

Predictionnvarchar-1General prediction

Keywordsnvarchar-1Keywords

Pstvnvarchar-1Positivity

Ngtvnvarchar-1Negitivity

Generalnvarchar-1General

Tarotnvarchar-1Tarot card resemblance of number

Astronvarchar-1Western sign resemblance of number

Runenvarchar-1Rune resemblance of number

iChingnvarchar-1iChing resemblance of number

treeOfLifenvarchar-1treeOfLife resemblance of number

hebremLetternvarchar-1hebremLetter resemblance of number

Shamanismnvarchar-1Shamanism resemblance of number

Elementnvarchar-1Element resemblance of number

Alchemynvarchar-1Alchemy resemblance of number

Auranvarchar-1Aura resemblance of number

Colornvarchar-1Color resemblance of number

Gemstonenvarchar-1Gemstone resemblance of number

Crystalsnvarchar-1Crystals resemblance of number

Fmonthnvarchar-1Fmonth resemblance of number

fweekDaynvarchar-1 Week Day resemblance of number

luckyNumsnvarchar-1luckyNumber resemblance of number

Floranvarchar-1Flora resemblance of number

friendNumsnvarchar-1Friend Numbers

enemyNumsnvarchar-1Enemy Numbers

Metalnvarchar-1Metal resemblance of number

bodyChemnvarchar-1bodyChem resemblance of number

Karmicnvarchar-1Karmic resemblance of number

bestProfnvarchar-1Best profession

compBusinessNumsnvarchar-1Compatible Business Numbers

compMarriageNumsnvarchar-1Compatible Marriage Numbers

compRomanceNumsnvarchar-1Compatible Romance Numbers

TABLE 8. TAROT

Card1nvarchar50Card1

Card2nvarchar50Card2

Intronvarchar100Introduction to them

GeneralnvarcharmaxGeneral prediction of the cards

WorknvarcharmaxWork related prediction

LovenvarcharMaxLove related prediction

FinancenvarcharmaxFinance related prediction

HealthnvarcharMaxHealth related prediction

spritualitynvarcharMaxSpirituality related prediction

MeaningnvarcharMaxMeaning related prediction

PastnvarcharMaxPast related prediction

PresentnvarcharMaxPresent related prediction

FuturenvarcharmaxFuture related prediction

yes__nonvarcharmaxYes/no interpretation

date_tmng_astronvarcharmaxDate time according to astro

Tables data:

The tables have to be populated by you and your client. Each table must contain an appropriate number of data. The contents of the tables have to be provided (in an organized way.)

Graphical User Interface

Provide, in an organized way, the pictures of all the forms in the graphical user interface with a reference to the functional requirement it implements. You may use html to present the graphical user interfaces.

For each form in the graphical user interface, provide:

The names of the controls and fields on that form,

The names of the events, methods, or procedures that cause that form to be displayed, and

The names of the events, methods, or procedures triggered by each control.

3.8.8 Class Diagrams and Classes

Provide a class diagram and an inheritance tree/diagram.

Each method has to be defined:

1. Method Name

2. Parameters, each documented with its intended use

3. Return Value, suitably documented

4. Informal description of what the procedure does

5. Data structure and tables it accesses

6. Pre-conditions: Assumptions the method can make about the state of the global data structures and database when it starts

7. Validity Checks, Errors, and other Anomalous Situations: Validity checks the method must make about the state of the global data structures, the database, and its parameters, including the actions that must be taken when such a check fails.

8. Post-conditions: The changes the method is supposed to make to the global data structures and database.

9. Called by: The methods or events that call it

10. Calls: The methods it calls and any events it causes.

3.8.9 Uses/Interactions

A description of this components collaborations with other components. What other components is this entity used by? What other components does this entity use (this would include any side-effects this entity might have on other parts of the system)? This concerns the method of interaction as well as the interaction itself. Object-oriented designs should include a description of any known or anticipated subclasses, superclasses, and metaclasses.

3.8.10 Resources

A description of any and all resources that are managed, affected, or needed by this entity. Resources are entities external to the design such as memory, processors, printers, databases, or a software library. This should include a discussion of any possible race conditions and/or deadlock situations, and how they might be resolved.

3.8.11 Processing

A description of precisely how this component goes about performing the duties necessary to fulfill its responsibilities. This should encompass a description of any algorithms used; changes of state; relevant time or space complexity; concurrency; methods of creation, initialization, and cleanup; and handling of exceptional conditions.

3.8.12 Interface/Exports

The set of services (resources, data, types, constants, subroutines, and exceptions) that are provided by this component. The precise definition or declaration of each such element should be present, along with comments or annotations describing the meanings of values, parameters, etc. .... For each service element described, include (or provide a reference) in its discussion a description of its important software component attributes (Classification, Definition, Responsibilities, Constraints, Composition, Uses, Resources, Processing, and Interface).

Much of the information that appears in this section is not necessarily expected to be kept separate from the source code. In fact, much of the information can be gleaned from the source itself (especially if it is adequately commented). This section should not copy or reproduce information that can be easily obtained from reading the source code (this would be an unwanted and unnecessary duplication of effort and would be very difficult to keep up-to-date). It is recommended that most of this information be contained in the source (with appropriate comments for each component, subsystem, module, and subroutine). Hence, it is expected that this section will largely consist of references to or excerpts of annotated diagrams and source code. Any referenced diagrams or source code excerpts should be provided at any design reviews.

3.8.13 Detailed Subsystem Design

Provide a detailed description of this software component (or a reference to such a description). Complex diagrams showing the details of component structure, behavior, or information/control flow may be included in the subsection devoted to that particular component (although, unless they are very large or complex, some of these diagrams might be more appropriately included in the System Architecture section. The description should cover any applicable software component attributes (some of which may be adequately described solely by a source code declaration or excerpt).

3.9. Source Code Details

SLOC: Source Lines of Code. Use the free software sloc to calculate the SLOC

S.NoFilenameSLOC

1. frmHome.aspx

frmHome.aspx

background: url('Images/bg6.jpg') no-repeat top;

background-size : 100% 800px;

background: url('Images/bgPannel.png') no-repeat top;

background-size : 100% 100%;

.btnStyl

background-color:Black;

border-style:Inset;

border-color:Navy;

font-weight:bold;

font-style:italic;

font-family:Kristen ITC;

font-size:10pt;

color:Olive;

height:30px;

width:100px;

.btnStyl1

background-color:Black;

border-style:Inset;

border-color:Navy;

font-weight:bold;

font-style:italic;

font-family:Kristen ITC;

font-size:10pt;

color:Olive;

height:30px;

width:100px;

margin:0px;

function opage() {

document.getElementById("frame1").src = "frmAboutUs.aspx";

ASTROLOGY

About Us

Testimonials

Contact Us

frmHome.cs

using System;

using System.Collections.Generic;

using System.Linq;

using System.Web;

using System.Web.UI;

using System.Web.UI.WebControls;

using System.Web.UI.HtmlControls;

public partial class frmHome : System.Web.UI.Page

protected void Page_Load(object sender, EventArgs e)

protected void lbtnServices_Click(object sender, EventArgs e)

Response.Redirect("frmServices.aspx");

protected void lbtnLogin_Click(object sender, EventArgs e)

Response.Redirect("frmSignIn.aspx");

MastrePage.master

background: url('Images/bgpg1.png') no-repeat top;

background-size : cover;

function panShow() {

document.getElementById("Panel1").setAttribute("Visible", "true");

Sign Out

Astrology

HOROSCOPE

Know about yourself

Basics

Srength and Weakness

Get your stone

Different Aspects

CHINEESE

NUMEROLOGY

TAROT READING

Know about yourself

Introduction

General

Work

Love

Finances

Health

Sprituality

Past

Present

Future

Yes/No Key Interpretation

Copyrights Reserved

MasterPage.master.csusing System;

using System.Linq;

using System.Web;

using System.Web.UI.HtmlControls;

public partial class MasterPage : System.Web.UI.MasterPage

if (Global.Retfname == "")

imbtnLogin.Visible = true;

lblName.Text = "Welcome";

lbtnSignOut.Visible = false;

imbtnLogin.Visible = false;

lblName.Text = "Welcome " + Global.Retfname;

lbtnSignOut.Visible = true;

protected void imbtnLogin_Click(object sender, ImageClickEventArgs e)

Response.Redirect("frmSignIn.aspx");

protected void btnLove_Click(object sender, ImageClickEventArgs e)

Response.Redirect("frmHoroLoveMatch.aspx");

protected void lbtnSignOut_Click(object sender, EventArgs e)

Global.RetUserId = "";

Global.Retfname = "";

imbtnLogin.Visible = true;

Ddmenu.css

/* main menu

----------------------------*/

#ddmenu

display:block;

font-family:Arial;

text-align:center; /* Specify the alignment of the whole UL if UL is not width:100%;*/

letter-spacing:normal;

/*workable with bootstrap*/

#ddmenu, #ddmenu div {

-webkit-box-sizing: content-box;

-moz-box-sizing: content-box;

box-sizing:content-box;

#ddmenu ul

/*text-align:right;*/ /* Here you can further customize the alignment of its LIs */

width:90%;

margin:0;

padding:0;

font-size:0;

background:#FFFFCC;

/*border:1px solid #FFFFCC;

border-bottom:none;*/

display:inline;

list-style:none;

position:relative;

z-index:999999990;

visibility:hidden;

border-radius:4px;

#ddmenu li

margin:0;

padding:0;

font-size:11px;

display:inline-block;

position:relative;

color:#000000;

#ddmenu a

color:#000000;

padding:0 22px;

line-height:30px;

font-weight:normal;

text-decoration:none;

display:inline-block;

outline:0;

position:relative;

white-space:nowrap;

/* links without sub-menu */

#ddmenu li.over a

background-color:#DDDDDD;

color:#000000;

/* links with sub-menu */

#ddmenu a.arrow

background-image:url(arrow1.gif);

background-repeat:no-repeat;

background-position:right center;

border-left:1px solid transparent;

border-right:1px solid transparent;

#ddmenu li.over a.arrow

background-color:#FFFFFF;

color:#003366;

border-left:1px solid #DDDDDD;

border-right:1px solid #DDDDDD;

/*text-decoration:underline;*/

#ddmenu li > div

padding:0;

margin:0;

display:none;

/* sub-menu layout

----------------------------*/

#ddmenu div.drop

position:absolute;

text-align:left;

border:1px solid #DDDDDD;

background:#FFFFFF;

padding:20px;

color:#000000;

line-height:30px;

font-size:13px;

font-family:Arial;

font-weight:bold;

border-radius:0 0 6px 6px;

/* sub-menu offset

----------------------------*/

#ddmenu div.drop

left:0px;/*Use this property to change offset of the sub-menu*/

#ddmenu div.dropToLeft

left:auto; right:0px;

#ddmenu div.dropToLeft2

left:auto; right:-120px;

/* links in sub menu

----------------------------*/

#ddmenu div.drop a

line-height:20px;

font-size:12px;

font-family:Arial;

font-weight:normal;

color:#003399;

text-decoration:none;

display:block;

text-align:left;

position:static;

background:none;

background-image:none;

padding:0 0;

#ddmenu div.drop a:hover

text-decoration:underline;

color:#0099FF;

/* blocks within the sub-menu

----------------------------*/

#ddmenu div.drop div

background:none;

#ddmenu div.column

width:auto;

float:left; /*align each column in one row*/

padding:0 10px; /*padding of each column*/

#ddmenu div.column div

padding:0px 10px; /*sub-div within div.column. 10px for indent.*/

#ddmenuLink {display:none;}

frmServices.aspx

function iframeLoaded() {

var iFrameID = document.getElementById('Iframe1');

if (iFrameID) {

// here you can make the height, I delete it first, then I make it again

iFrameID.height = "";

iFrameID.height = iFrameID.contentWindow.document.body.scrollHeight + 20 + "px";

frmSignin.aspx

protected void Timer1_Tick(object sender, EventArgs e)

lblDateTime.Text = DateTime.Now.ToString();

background: url('Images/bg5.jpg') no-repeat fixed center;

background-size: cover;

color:White;

width:20px;

height:20px;

function pageLoad() {

$find('behavior')._onSubmit = function () {

If not signed in..

for free.

User Name :

Password:

&nbsp&nbsp&nbsp&nbsp

Forgot your password..?

Copyrights Reserved

frmSignIn.csusing System;

using System.Linq;

using System.Web;

using System.Configuration;

using System.Data;

using System.Data.SqlClient;

public partial class frm : System.Web.UI.Page

string constr = ConfigurationManager.ConnectionStrings["astroConnectionString"].ConnectionString;

protected void imbtnRegister_Click(object sender, ImageClickEventArgs e)

Response.Redirect("frmRegister.aspx");

protected void imbtnLogin_Click(object sender, ImageClickEventArgs e)

if (txtUserName.Text == "")

ScriptManager.RegisterStartupScript(this, typeof(string), "Error",

"alert('Enter Username!');", true);

else if (txtPassword.Text == "")

ScriptManager.RegisterStartupScript(this, typeof(string), "Error",

"alert('Enter Password!');", true);

// ScriptManager.RegisterStartupScript(this, typeof(string), "Error",

//"alert('Logged In!');", true);

// txtUserName.Text = "";

// txtPassword.Text = "";

string paswd = "";

SqlConnection con = new SqlConnection(constr);

con.Open();

SqlCommand cmd = new SqlCommand("select pass, userType from LoginDet where userId = '" + txtUserName.Text + "'", con);

SqlDataReader dr = cmd.ExecuteReader();

if (dr.HasRows)

while (dr.Read())

paswd = dr.GetString(0);

con.Close();

con.Open();

if (paswd == txtPassword.Text)

Global.RetUserId = txtUserName.Text;

SqlCommand cmd1 = new SqlCommand("select firstName from UserDet where userId = '" + txtUserName.Text + "'", con);

SqlDataReader dr1 = cmd1.ExecuteReader();

while (dr1.Read())

Global.Retfname = dr1.GetString(0);

Response.Redirect("frmServices.aspx");

con.Close();

protected void Timer1_Tick(object sender, EventArgs e)

lblDateTime.Text = DateTime.Now.ToString();

protected void btnHome_Click(object sender, EventArgs e)

Response.Redirect("frmHome.aspx");

frmRegister.aspx

background: url('Images/bg4.jpg') no-repeat center;

background-size: cover;

color:White;

width:90%;

height:50%;

top:0;

.CustomValidatorCalloutStyle div,

.CustomValidatorCalloutStyle td {

border:solid 1px blue;

background-color: #ADD8E6;

If already have an account..

CREATE YOUR ACCOUNT

One account is all you need

A single username and password gets you into everything in Astro.

Choose your Username:

Create a password :

Confirm password

Date of birth :

Gender :

Mobile :

Your current email address

Prove you're not a robot

Type the text:

Security Question :

Select one of the following

What was your fist pet's name ?

Where were you born ?

What is your pet name ?

Other Ques

Enter the answer :

Copyrights Reserved

frmRegister.cs

using System;

using System.Linq;

using System.Web;

using System.Data;

using System.Data.SqlClient;

using System.Configuration;

using System.Windows.Forms;

using System.Drawing;

public partial class frmRegister : System.Web.UI.Page

string constr = ConfigurationManager.ConnectionStrings["astroConnectionString"].ConnectionString;

string asign, chSign;

int number;

ddlDate.Items.Add("--DD--");

for (int i = 1; i b, #slider a>b {

position:absolute; border:none; display:none; width:20px; height:50px;

#slider div.sliderInner {

overflow:hidden;

-webkit-transform: rotate(0.000001deg);/* fixed the Chrome not crop border-radius bug*/

position:absolute; top:0; left:0;

#slider>a, #slider video, #slider audio {display:none;}

Js-image-slider.js

var sliderOptions=

sliderId: "slider",

startSlide: 0,

effect: "series1",

effectRandom: false,

pauseT

Sds astrology

Documents

Transcript of Sds astrology