52
INDEX

iDate Final

Embed Size (px)

Citation preview

Page 1: iDate Final

INDEX

Page 2: iDate Final

Introduction

Company Profile

HiddenBrains Infotech - is an ISO 9001:2008 and Microsoft Certified Partner Company in Ahmedabad, India with proven competencies in custom software development, Android, iPhone App Development, ASP.Net, Open Source, PHP, Web Application Development and offshore IT outsourcing services. Expertise in the design and development of robust and scalable web and mobile applications development.

HiddenBrains is a company providing professional-level customized solution, Web applications development, full-featured online shopping stores, Software development, Mobile app development services. We design, manage, build and maintain high quality solutions for a wide range of businesses and individuals. We have built our business by working with clients to ensure the solutions we develop are profitable for them.

With 120+ full time experienced computer professionals working for us,Our forte is to take your requirement, apply our understanding of web methodologies and propose innovative & technical features and site enhancements that help you to achieve your goals - while taking into account commercial considerations & timeframe with high level of communication and support.

By choosing HiddenBrains, you get more than our programming and design work. You also get our years of experience and expertise.

CompanyHiddenBrains is an innovative technology industry focused, business driven professional services firm. From web design and development to custom applications, our talented people work intelligently to solve and manage client’s needs. We serve to deliver cost effective interactive technology and design solutions without compromising on quality.

With clients globally, Hidden Brains produces innovative, high-performance Web sites for companies in multiple industries including hospitality, retail, wholesale, communications and so on. Using the latest programming and design technologies, Hidden Brains creates the optimal, effective online as well as desktop experience for every client. We can work within your existing corporate ID or create one for you to establish a sense of branding for your need.

Our Commitment

Page 3: iDate Final

We take pride in our on time delivery and ability to meet quick turn around requests while exceeding customer quality demands.

Customer Satisfaction continues to be of utmost importance to HiddenBrains, as do Consistent quality, Constant innovation, Technology enhancement, Process improvement and Customer orientation. We have developed our core competence and aligning objectives at all levels so as to realize synergy in operations. It is our collaborative approach, creative input, and emphasis on economical solutions that has allowed us to develop an impressive and diverse client list.

HiddenBrains believes in constant restructuring, adds new services and enhances infrastructure and increases the number of full time employees.

If your company is in need of Offshore PHP, ASP.Net, Coldfusion, C#, C++ Software development services, HiddenBrains is the best choice. We are sure that our relations will be mutually beneficial, and we will be able to satisfy your needs.

• Current system

Lots of social networking applications are available today. Those applications do not facilitates users to search mates on the basis of the current location.

• Proposed system – Introduction

In the world of social Networking, lots of applications are available each with new variety of features. Each User demands different requirements.

iDate is a social networking plus dating application with the requirement to enable users to search dating partners on the basis of the location they are geographically present. Idate

• Project profile

Project Title : iDate

Page 4: iDate Final

Objective : Idate is designed for people interested in Dating.Development Node : Mac Os X

Language : Objective C

Database : Sql Server 2005Guided By :

Mr. Kandarp DaveDeveloped By : Dimple P. Panchal

•• Project definition• Scope of the system

Idate, a social networking application is specially designed, for people interested in Dating, to create and maintain a bond of relation between people near around. People can make relationships while on the move with the people who are near to them. User can create his/her profile, manage his profile, find matching profile for dating. User can also maintain a channel of communication with other users through messages, winks and emails to other users.

• Objective of the systemObjectives of the system are as follows:

• To instantly connect compatible singles at the most present time and location.• To create a profile, define the person you want to meet and instantly connect with singles near you - right now.• Browse singles profiles in near you and compatible with you• Check out who is online RIGHT NOW and meet singles in their area who are online right now• Contact singles: send and receive winks, flirts and messages• Use the iPhone app while on the go• Meet users from almost every country• Advance search to find your perfect match• The fastest and most fun way to date new compatible singles near you

Advantages

• Improved application speed, load time and performance• Added functionality for Image gallery

Page 5: iDate Final

• Various graphic enhancements• Better search• Simplified sign up• Email features

• Drawback of existing system and alternatives

Not a single application from the Existing applications facilitates users to search for a dating partner while on the move. Idate is designed that it will filter the listed users on the basis of the distance of that user from other users. Wherever you are you can use your iphone to connect and meet other users using iDate application.

• Environment Specification• H/w & s/w requirements• Development description

Page 6: iDate Final

• System Planning• Feasibility Study

feasibility studies which will measure the technical, operational, schedule and economic feasibility of the app which depends on its practical and competitive advantage

• Technical feasibility

Technical feasibility of any application is the availability of technology for the proposed system.

Company owns good number of Mac Desktops with high configuration, hence application is technically feasible for the company.

• Economical feasibility

There is no overhead cost for software or hardware. Hence iDate is economically feasible.

• Operational feasibilityiDate is known for its highly user friendly interface. For applications

like iDate, it is highly expected that the application should be very easy to use for every levels of users. Hence, we can conclude that iDate is operationally feasible.

• Time Duration

We were having 4 months to develop the entire application and we scheduled our work to cope us with the defined time limit.• Resources

When developing any application we need proper environmental resources as well as man power. For developing iDate, we have available computer system with Proper configuration. For solving any query and problems faced during development of such application, we have provision of Internet Connection and support of company employees.

• Software Engineering Model

This application was developed with Incremental model.

Page 7: iDate Final

The incremental model delivers software in small but usable pieces, called “increments.” In general, each increment builds on those that have already been delivered.

Since the deadlines were too close , using this model, we were able to satisfy the client requirements with a new module.

The Incremental Model is type of Evolutionary Model approach.

Evolutionary models are iterative. They are characterized in a manner that enables software engineers to develop increasingly more complete versions of the software.

The incremental model combines elements of the linear sequential model with the iterative philosophy of prototyping

In the first increment, often called a core product, basic requirements are addressed, but many supplementary features (some known, others unknown) remain undelivered.The core product is used by the user (or undergoes detailed review). As a result of use and/or evaluation, a plan is developed for the next increment.The plan addresses the modification of the core product to better meet the needs of the customer and the delivery of additional features and functionality. This process is repeated above the delivery of each increment, until the complete product is produced. Early increments are stripped down versions of the final product, but they do provide capability that serves the user and also provide a platform for evaluation by the user.Incremental development is particularly useful when staffing is unavailable for a complete implementation by the business deadline that has been established for the project.

We were delivering a small module at regular interval and regular feedback was gained from the client so that changes can be reflected quickly.

• Scheduling

Page 8: iDate Final

• Risk Analysis

Risks Category Probability Impact RMMMWill the system be able to meet

all its objectives?Project risk 80% 1

Proper definition of project risk

Will the application be

able to meet its requirements?

Performance risk

40% 2

Proper requirement

gathering process

What if implementation

fails?

Functional risk

80% 4Using other

services.

Larger no. of users estimated.

Project size risk

50% 2Efficient database

management

Inability to meet the deadline.

Schedule risk

80% 1Accurate

estimation of time

A Technological failure

Technical risk

90% 1Keeping

backup ready

Does staff have the right skills?

People risk 70% 2Provide

necessary training

Impact values-1-Catastropic, 2-Critical, 3-Marginal, 4-Neglible

Page 9: iDate Final

• System Analysis• Detailed analysis

Detailed SRS:

Modules:

• RegistrationDescription:InputEventsOutputConstraints• User LoginDescription:InputEventsOutputConstraints

• Find MatchDescription:InputEventsOutputConstraints

• Profile ManagementDescription:InputEventsOutputConstraints

• MessagesDescription:InputEventsOutputConstraints

Page 10: iDate Final

• Extras Description:InputEventsOutput

Constraints

Page 11: iDate Final

• UMLUsecase Diagrams:

Login

Manage Admin User

Manage Iphone User

Manage Localization

Manage Advertisement

Manage Promotion

Manage Events

Manage Tracking

Admin

Logout

Page 12: iDate Final

Admin User List

View User List

Search User

Add new User

Delete

Edit

Admin

Page 13: iDate Final

Iphone User List

View User List

Search User

Suspend/Unsuspend User

R

Delete

Edit

AdminView Profile

View Album

Delete Photo

Page 14: iDate Final

Localization (Country, State, City) / Promotion / Event / Advertisement

View List

Search

Add new

Delete

Edit

Admin

Page 15: iDate Final

iphone Module

Registration

Login

Find Match

Manage Settings

Manage Profile

Manage Account

Manage Image Gallery

Manage Messages

View Advertisements

Upgrade Application

Iphone User

Page 16: iDate Final

FIND MATCH

Updates Location

Filter

Find Match by Category

Manage Settings

Refresh Match Listing

Iphone User

Page 17: iDate Final

My Profile

View Profile Details

Edit Profile/Matching/Extended Profile

Manage My Account

Manage Album

Set Matching Profile

Iphone User

Page 18: iDate Final

View Matching Profile

View Profile Details

Send Message

Send Instant Wink

Flirt

Add to hotlist

Report Abuse Iphone User

Page 19: iDate Final

FILTER

Select Compatibility

User Location

User Status

Profile

Propularity

Charactistics

Reset All

Iphone User

Page 20: iDate Final

Settings

Set GPS On/Off

Set Online Status

Set Email Alerts On/Off

Account Details

Log out

Erase AccountIphone User

Page 21: iDate Final

Email Alerts

Set Wink Alert On/Off

Set Flirt Alert On/Off

Set Message Alert On/Off

Set profile Views

Once a week

Iphone User

Page 22: iDate Final

Account Details

Manage Details

View Album

Add Photo to Album

Update Account Details

Delete Photo from Album

Page 23: iDate Final

Activity Diagrams:

Admin Module

Page 24: iDate Final

Login Module

Loading Screen

Forgot Password Enter Email & Password New User

Registration Form

NO

Verify

Verify

YES

Enter Application

Send Email

Page 25: iDate Final

Find Match

All

View Friend Profile

Near By Hotlist Settings Update Location Filter

Send Message Instant Wink Flirt Add To Hotlist

Report Abuse

Page 26: iDate Final

Sequence Diagram:

Page 27: iDate Final

Database Diagram:

• Software Design• System Architecture

ApplicationUser

User

Comes in mutual Contact

Views

Receives Sends

DataBase

Page 28: iDate Final

• Database design

1.iDate_TermsCondition

Purpose: Stores Terms and conditions for using this application.

Primary Key: Terms_IdForeign Key: NA

Field Name Field TypeConstraint Description

Terms_IdNumber(5) PK Terms Code

Description text Null Terms Description

2. iDate_Users

Purpose: Stores Terms and conditions for using this application.

Primary Key: Terms_IdForeign Key: NA

Field NameField Type

Constraint Description

User_IdNumber(5) PK User Code

User_Emailvarchar(30) Not Null Store User Email Address

User_Passwordvarchar(20) Not Null Store User Password

IsSuspend bit Not Null user is suspend or notUser_AccessLevel_Id

Number(5) Not Null Store User Access Level code

IsDeleted bit Not NullStore delete flag if flag is true means deleted

Created_Date datetime Not Null User created date

Page 29: iDate Final

3. iDate_UserSettings

Purpose: Stores Terms and conditions for using this application.

Primary Key: Terms_IdForeign Key: NA

Field NameField Type

Constraint Description

Setting_IdNumber(5) PK Store setting code

User_IdNumber(5) FK Store user code

GPS bit Not Null Store user GPS statusOnline_Status

Number(2) Not Null User online status

Messages bit Not NullUser set Message alerts bit[True means on]

Winks bit Not NullUser set Winks alerts bit[True means on]

Flirts bit Not NullUser set Flirts alerts bit[True means on]

4. iDate_BlockedUser

Purpose: Stores Terms and conditions for using this application.

Primary Key: Terms_IdForeign Key: NA

Field NameField Type

Constraint Description

Block_IdNumber(5) PK User Block code

User_IdNumber(5) FK User Code

Block_Date datetime Not Null User block code

5. iDate_UserProfile

Purpose: Stores Terms and conditions for using this application.

Primary Key: Terms_IdForeign Key: NA

Field Name Field Type Constrai Description

Page 30: iDate Final

ntProfile_Id Number(5) PK User Profile codeUser_Id Number(5) FK User code User_FirstName varchar(30) Not Null User Firstname User_LastName varchar(20) Null User LastnameUser_NickName varchar(20) Null User NickName

User_Gender bit Null

User Gender male means true and female means false

User_Dob datetime Null Store user Date of birth

User_AddressVarchar(200) Null Store user address

User_City Number(5) FK Store user city codeUser_State Number(5) FK Store user state codeUser_Country Number(5) FK Store user country code

User_Picture varchar(70) NullStore user picture url address

User_Seeking Varchar(50) Null Store user seeking

User_DescriptionVarchar(200) Null user commnets

User_Child varchar(40) NullStore user Child Information

User_EyeColor Varchar(10) Null User eye colorUser_Height varchar(5) Null User heightUser_BodyType varchar(20) Null User body type User_HairColor varchar(10) Null User Hair color

User_Personality varchar(20) NullStore user personality information

User_Education varchar(20) NullStore user education information

User_Entertainment varchar(20) NullEntertainment information

User_DinnerChoice varchar(20) NullStore user dinner choice information

User_Sport varchar(10) NullNumber(5)erested Sport information

User_DressCode varchar(20) NullUser dresscode information

User_Drink varchar(15) NullDrink realeted information store

User_Smoke varchar(20) NullSmoking releted information store

User_Pets varchar(20) Null User have pets than

Page 31: iDate Final

store information

User_PerferredLocation varchar(20) NullUser preferred location for datting

User_MorningFix varchar(20) NullUser store morning time for meeting

User_MeetingLocation varchar(20) Null User meeting locationUser_Personal_Description

Varchar(100) Null Store personal detail

User_Star_Sign varchar(10) Null User store star sigbn

User_Number(5)nerest varchar(50) Null

User store Number(5)nerested area

User_ProfileStatus bit Null User profile statusUser_Basis varchar(30) Null User store BasisUser_AgeGro varchar(10) Null User age group

6. iDate_LoginHistory

Purpose: Stores Terms and conditions for using this application.

Primary Key: Terms_IdForeign Key: NA

Field Name Field TypeConstraint Description

Login_Id Number(5) PK Store Login id

User_Id Number(5) FK Store user id

UserLng float NullStore user current location logitute

UserLat float NullStore user current location latitute

Login_Date datetime Not Null User login date

Logout_Date datetime Null User Logout date

Status bit Null User status

Device_IdVarchar(50) Null Store user device id

Device_TokenVarchar(50) Null Store user device token

CurrentLocation

Varchar(200) Null Store user current location

7. iDate_AdminUsers

Page 32: iDate Final

Purpose: Stores Terms and conditions for using this application.

Primary Key: Terms_IdForeign Key: NA

Field Name Field TypeConstraint Description

Admin_User_Id Number(5) PK Store admin user id

User_FirstName Varchar(50) Null Admin user firstname

User_LastName Varchar(30) Null Admin user lastname

UserName Varchar(30) Null Store admin username

Password Varchar(20) Null Store admin password

User_Email Varchar(50) Null Store admin user emailUser_CreatedDate datetime Not Null Admin user created date

Page 33: iDate Final

8. iDate_UserHotList

Purpose: Stores Terms and conditions for using this application.

Primary Key: Terms_IdForeign Key: NA

Field NameField Type

Constraint Description

UserHotList_IdNumber(5) PK Store iphone user hotlist id

User_IdNumber(5) FK Store iphone user id

9. iDate_Inbox

Purpose: Stores Terms and conditions for using this application.

Primary Key: Terms_IdForeign Key: NA

Field Name Field TypeConstraint Description

Message_Id Number(5) PK Store message id

Sender_User_Id Number(5) Not Null Store sender user id

Receiver_User_Id Number(5) Not Null Store receiver user id

Message_Type Number(5) Not Null Store message typeMessage_Description

Varchar(500) Null Message description

Message_Date datetime Not Null Store message date

10. iDate_PhotoGallery

Field Name Field TypeConstraint Description

Gallery_IdNumber(5) PK Store gallery id

User_IdNumber(5) FK Store User id

Image_NameVarchar(40) Not Null Image Name

Page 34: iDate Final

11. iDate_AccessLevel

Purpose: Stores Terms and conditions for using this application.Primary Key: Terms_IdForeign Key: NA

Field Name Field TypeConstraint Description

User_AccessLevel_Id

Number(5) PK Store User Access level id

Access_NameVarchar(30) Null Store Access name

12. iDate_Event

Purpose: Stores Terms and conditions for using this application.

Primary Key: Terms_IdForeign Key: NA

Field Name Field TypeConstraint Description

Event_Id Number(5) PK Store event id

Event_TitleVarchar(30) Not Null Store event name

Event_ThumbImageVarchar(50) Null

Store event thumbimage name

Event_BigPictureVarchar(50) Null Store event big picture

Event_ShortDescription

Varchar(50) Null Event short description

Event_DescriptionVarchar(500) Null Event description

Event_LinkVarchar(200) Null Event Link

13. iDate_AdvertisementTargetBy

Purpose: Stores Terms and conditions for using this application.

Primary Key: Terms_IdForeign Key: NA

Field NameField Type

Constraint Description

Page 35: iDate Final

Advertisement_Id

Number(5) PK Store Advertisement id

WorldWide bit NullAdvertisement published worldwide or not

Country_IdNumber(5) FK Store country id

State_IdNumber(5) FK Store state id

City_IdNumber(5) FK Store city id

Page 36: iDate Final

14. iDate_Advertisement

Purpose: Stores Terms and conditions for using this application.

Primary Key: Terms_IdForeign Key: NA

Field Name Field TypeConstraint Description

Advertisement_Id Number(5) PK Store advertiment id

Adv_NameVarchar(50) Null Store advertisement name

Adv_SourceVarchar(100) Null Store advertisement source

Adv_Click_LinkVarchar(200) Null advertisement link url

Adv_CreatedDate datetime Null advertisement created date

15. iDate_HotList_Message

Purpose: Stores Terms and conditions for using this application.

Primary Key: Terms_IdForeign Key: NA

Field Name Field TypeConstraint Description

HotList_IdNumber(5) FK Store user hot list id

User_IdNumber(5) FK Store user id

Message_IdNumber(5) FK Store message id

16. iDate_Country

Purpose: Stores Terms and conditions for using this application.

Primary Key: Terms_IdForeign Key: NA

Field Name Field TypeConstraint Description

Country_Id Number(5 PK Store country id

Page 37: iDate Final

)

Country_NameVarchar(50) Null Store country name

Page 38: iDate Final

17. iDate_State

Purpose: Stores Terms and conditions for using this application.

Primary Key: Terms_IdForeign Key: NA

Field Name Field TypeConstraint Description

State_IdNumber(5) PK Store state id

Country_IdNumber(5) FK Store country id

State_NameVarchar(30) Null Store state name

18. iDate_City

Purpose: Stores Terms and conditions for using this application.

Primary Key: Terms_IdForeign Key: NA

Field Name Field TypeConstraint Description

City_IdNumber(5) PK Store city id

State_IdNumber(5) Not Null Store state id

City_NameVarchar(30) Null Store city name

19. iDate_AdvertisementClick

Purpose: Stores Terms and conditions for using this application.

Primary Key: Terms_IdForeign Key: NA

Field Name Field TypeConstraint Description

Click_IdNumber(5) PK Store click id

Advertisement_Id

Number(5) FK Store advertisement id

Click_Count Number(1 Not Null Advertisement click count

Page 39: iDate Final

5)

Page 40: iDate Final

20. iDate_AdvertisementImpression

Purpose: Stores Terms and conditions for using this application.

Primary Key: Terms_IdForeign Key: NA

Impression_IdNumber(5) PK Store impression id

Advertisement_Id

Number(5) FK Store advertisement id

Impression_Count

Number(15)

Not Null

Store impression count of perticular advertisement

21. iDate_Promotion

Purpose: Stores Terms and conditions for using this application.

Primary Key: Terms_IdForeign Key: NA

Field Name Field TypeConstraint Description

Promotion_id Number(5) PK Store promotion id

Promotion_TitleVarchar(50) Null Store promotion title

Promotion_ThumbImage

Varchar(50) Null

Store promotion thumbimage

Promotion_BigPictureVarchar(50) Null

Store promotion big picture

Promotion_LinkVarchar(200) Null Store promotion Link

Promotion_Description

Varchar(500) Null

Store promotion description

Page 41: iDate Final

• Interface design

IPHONE SCREENS1. Iphone Home Page 2. Splace screen

Page 42: iDate Final

• TestingSoftware Testing is a testing which test the data and examining the output of the software and also check the operational behavior of the software that it perform as per the requirements.

• Statistical Testing:

Statistical Testing is used to test the program’s performance and

reliability and to check how it works under operational conditions. Tests are

designed to reflect the actual user inputs and their frequency.

The stages involved in the static analysis for this system are follows.

Control flow analysis:

• I found many functions which are unreachable during execution, then

for solving this problem I put some extra conditions to make that code

reachable.

• I also found some unconditional branches into loops.

• Parameter type mismatches

• Parameter number mismatches

• Non-usage of the results of functions

• Uncalled functions and procedures

DEFECTING TESTING:

Testing is the process of exercising a program with the specific

intent of finding errors prior to delivery to the end user. A good test case is

of finding an as-yet-undiscovered error. A successful test is one that

uncovers an as-yet-undiscovered error.

Testing is useful for validation and verification, which ensure

that software conforms to its specification and meets the needs of the

software customer.

In the Idate Social networking System, we tested one of two ways:

• White-Box Testing

• Black-Box Testing

Page 43: iDate Final

White Box Testing:

White Box Testing, sometimes called glass-box testing, is tests that are run

an application with the knowledge of the internal working of the code base.

In Idate Social networking System i consider to type of testing in white-box

testing are as follows:

Component test: Users Details

Module:User specific class

Test case description: All functions of user class.

Ste

pInput test

Result Pass/Fail

Expected Actual

1

The User can

login of his

account.

In DB store the

administrator login id and

password automatically.

As per

expected

Pass

2

The User can

change his/her

password.

In DB store/change the

Client login id and

password automatically.

As per

expected

Pass

3

User Can Add,

Update, Delete

user Information.

All the necessary data are

store in DB i.e. User_id,

User_name, etc.

As per

expected

Pass

4

User Can

Compose, Send,

Delete,view The

user message

Information

Fields like Message user_id

store in DB.

As per

expected

Pass

5

user View

advertisement,

events, promos

Fields like Event_name,

Promos_name,

advertisemen_name

As per

expected

Pass

Page 44: iDate Final

Component test:Master Detail

Module:Admin Panel

Test case description:All functions of administrator class.

StepInput test Result Pass/

FailExpected Actual

1

Administrator can Add,

Delete, Update, Search

the Master Detail.

Administrator can

manage fields like

location, category,

reference about

user &it reflects to

the DB.

As per

expected

Pass

2

Administrator can send

the SMS-Email.

All the detail of the

SMS-Email are

store in DB.

As per

expected Pass

3

Admin can create user,

assign right &set profile

All the detail of

user management

are store in DB.

As per

expected Pass

Black Box Testing :

Black-Box Testing is testing without knowledge of the internal

workings of the item being tested.  For example, when black box

testing is applied to software engineering, the tester would only

know the "legal" inputs and what the expected outputs should be,

but not how the program actually arrives at those outputs. 

In Idate Social Networking i consider to type of

testing in black-box testing are as follows:

Page 45: iDate Final

Step Input test Result Pass /

FailExpected Actual

1 Users enter proper

name for accessing the

system.

Login is default

tab The tab

display proper.

As per

expected

Pass

2 User must enter proper

format password

An alert message

popup when user

will enter wrong

format of

password.

As per

expected

Pass

3 User can see the detail

about friends

Easy to see the

information.

As per

expected

Pass

4 User can get the sign

up after the fill-up the

details.

User can get the

sign up after the

fill-up the form.

As per

expected

Pass

5 user can add more

friends

Many services are

requird in this

module.

As per

expected

Pass

Page 46: iDate Final

• Future enhancement

• Reference