March 2010

Software application development ways:Prototyping model

Software prototyping, is the framework of activities during Software application development of creating prototypes, i.e., incomplete versions of the software program being developed.

Basic principles of prototyping are:

Not a standalone, complete development methodology, but rather an approach to handling selected portions of a larger, more traditional development methodology (i.e. Incremental, Spiral, or Rapid Application Development (RAD)).
Attempts to reduce inherent project risk by breaking a project into smaller segments and providing more ease-of-change during the development process.
User is involved throughout the process, which increases the likelihood of user acceptance of the final implementation.
Small-scale mock-ups of the system are developed following an iterative modification process until the prototype evolves to meet the users’ requirements.
While most prototypes are developed with the expectation that they will be discarded, it is possible in some cases to evolve from prototype to working system.

A basic understanding of the fundamental business problem is necessary to avoid solving the wrong problem

Advantages

Simple and easy to use.
Each phase has specific deliverables.
Higher chance of success over the waterfall model due to the development of test plans early on during the life cycle.
Works well for small projects where requirements are easily understood.

Disadvantages

Very rigid, like the waterfall model.
Little flexibility and adjusting scope is difficult and expensive.
Software is developed during the implementation phase, so no early prototypes of the software are produced.
Model doesn’t provide a clear path for problems found during testing phases.

Software application development ways:Waterfall model

Software application development ways

Every software development methodology has more or less its own approach to software development. There is a set of more general approaches, which are developed into several specific methodologies. These approaches are:
Waterfall: linear framework type.
Prototyping: iterative framework type
Incremental: combination of linear and iterative framework type
Spiral: combination linear and iterative framework type
Rapid Application Development (RAD): Iterative Framework Type
Waterfall model
This is classical model of Software application development The waterfall model is a sequential development process, in which development is seen as flowing steadily downwards (like a waterfall) through the phases of requirements analysis, design, implementation, testing (validation), integration, and maintenance. The first formal description of the waterfall model is often cited to be an article published by Winston W. Royce in 1970 although Royce did not use the term "waterfall" in this article.
Basic principles of the waterfall model are:

· Project is divided into sequential phases, with some overlap acceptable between phases.

· Emphasis is on planning, time schedules, target dates, budgets and implementation of an entire system at one time.

· Tight control is maintained over the life of the project through the use of extensive written documentation, as well as through formal reviews and approval/signoff by the user and information technology management occurring at the end of most phases before beginning the next phase.

Advantages:
Simple and easy to use.
Easy to manage due to the rigidity of the model – each phase has specific deliverables and a review process.
Phases are processed and completed one at a time.
Works well for smaller projects where requirements are very well understood.
Disadvantages:
Adjusting scope during the life cycle can kill a project
No working software is produced until late during the life cycle.
High amounts of risk and uncertainty.
Poor model for complex and object-oriented projects.
Poor model for long and ongoing projects.
Poor model where requirements are at a moderate to high risk of changing.

AddUsersToRoles Procedure with your custom COLLATE

USE

[YordatabaseName]

/****** Object: StoredProcedure [dbo].[aspnet_UsersInRoles_AddUsersToRoles] Script Date: 06/17/2009 13:22:03 ******/

SET

ANSI_NULLS ON

SET

QUOTED_IDENTIFIER OFF

CREATE

@ApplicationName

PROCEDURE [dbo].[aspnet_UsersInRoles_AddUsersToRoles]nvarchar(256),

@UserNames

nvarchar(4000),

@RoleNames

nvarchar(4000),

@CurrentTimeUtc

BEGIN

datetime

DECLARE @AppId uniqueidentifier

SELECT @AppId = NULL

SELECT @AppId = ApplicationId FROM aspnet_Applications WHERE LOWER(@ApplicationName) = LoweredApplicationNameIF (@AppId IS NULL)

RETURN(2)

DECLARE @TranStarted bit

SET @TranStarted = 0IF( @@TRANCOUNT = 0 )

BEGIN

BEGIN TRANSACTION

SET @TranStarted = 1END

DECLARE @tbNames table(Name nvarchar(256) COLLATE YorCollate _AS NOT NULL PRIMARY KEY)

DECLARE @tbRoles table(RoleId uniqueidentifier NOT NULL PRIMARY KEY)

DECLARE @tbUsers table(UserId uniqueidentifier NOT NULL PRIMARY KEY)

DECLARE @Num int

DECLARE @Pos int

DECLARE @NextPos int

DECLARE @Name nvarchar(256)

SET @Num = 0SET @Pos = 1WHILE(@Pos <= LEN(@RoleNames))

BEGIN

SELECT @NextPos = CHARINDEX(N',', @RoleNames, @Pos)

IF (@NextPos = 0 OR @NextPos IS NULL)

SELECT @NextPos = LEN(@RoleNames) + 1SELECT @Name = RTRIM(LTRIM(SUBSTRING(@RoleNames, @Pos, @NextPos - @Pos)))

SELECT @Pos = @NextPos+1INSERT INTO @tbNames VALUES (@Name)

SET @Num = @Num + 1END

INSERT INTO @tbRolesSELECT RoleIdFROM dbo.aspnet_Roles ar, @tbNames tWHERE LOWER(t.Name) = ar.LoweredRoleName AND ar.ApplicationId = @AppIdIF (@@ROWCOUNT <> @Num)

BEGIN

SELECT TOP 1 Name

FROM @tbNamesWHERE LOWER(Name) NOT IN (SELECT ar.LoweredRoleName FROM dbo.aspnet_Roles ar, @tbRoles r WHERE r.RoleId = ar.RoleId)

IF( @TranStarted = 1 )

ROLLBACK TRANSACTION

RETURN(2)

END

DELETE FROM @tbNames WHERE 1=1SET @Num = 0SET @Pos = 1WHILE(@Pos <= LEN(@UserNames))

BEGIN

SELECT @NextPos = CHARINDEX(N',', @UserNames, @Pos)

IF (@NextPos = 0 OR @NextPos IS NULL)

SELECT @NextPos = LEN(@UserNames) + 1SELECT @Name = RTRIM(LTRIM(SUBSTRING(@UserNames, @Pos, @NextPos - @Pos)))

SELECT @Pos = @NextPos+1INSERT INTO @tbNames VALUES (@Name)

SET @Num = @Num + 1END

INSERT INTO @tbUsersSELECT UserIdFROM dbo.aspnet_Users ar, @tbNames tWHERE LOWER(t.Name) = ar.LoweredUserName AND ar.ApplicationId = @AppIdIF (@@ROWCOUNT <> @Num)

BEGIN

DELETE FROM @tbNamesWHERE LOWER(Name) IN (SELECT LoweredUserName FROM dbo.aspnet_Users au, @tbUsers u WHERE au.UserId = u.UserId)

INSERT dbo.aspnet_Users (ApplicationId, UserId, UserName, LoweredUserName, IsAnonymous, LastActivityDate)

SELECT @AppId, NEWID(), Name, LOWER(Name), 0, @CurrentTimeUtcFROM @tbNamesINSERT INTO @tbUsersSELECT UserIdFROM dbo.aspnet_Users au, @tbNames tWHERE LOWER(t.Name) = au.LoweredUserName AND au.ApplicationId = @AppIdEND

IF (EXISTS (SELECT * FROM dbo.aspnet_UsersInRoles ur, @tbUsers tu, @tbRoles tr WHERE tu.UserId = ur.UserId AND tr.RoleId = ur.RoleId))

BEGIN

SELECT TOP 1 UserName, RoleNameFROM dbo.aspnet_UsersInRoles ur, @tbUsers tu, @tbRoles tr, aspnet_Users u, aspnet_Roles rWHERE u.UserId = tu.UserId AND r.RoleId = tr.RoleId AND tu.UserId = ur.UserId AND tr.RoleId = ur.RoleIdIF( @TranStarted = 1 )

ROLLBACK TRANSACTION

RETURN(3)

END

INSERT INTO dbo.aspnet_UsersInRoles (UserId, RoleId)

SELECT UserId, RoleIdFROM @tbUsers, @tbRolesIF( @TranStarted = 1 )

COMMIT TRANSACTION

RETURN(0)

END

Resetting Password with ASP.NET 2.0 Membership,Using Multiple Membership Providers

By Tigran Sargsyan

www.progx.us

In asp.net 2 you can use Membership class to reset a user password. Which has 2 Overloaded Variants?

1.) Reason to use for admin tool

//This Variant for admin part password reset

MembershipUser Myuser;

string UserName =””;// change “” to UserName which password need to reset Membership.Providers["AdminMembershipProvider"].GetUser(UserName,false);

if (Myuser != null)

{

pass = Myuser.ResetPassword();

}

2) Reason to use for simple user interface In password recovery for example. This variant needs

MembershipUser Myuser;

string UserName =””;// change “” to UserName which password need to reset

string passwordanswer=””;//change “” with answer of secure quastion

Myuser= Membership.Providers["AdminMembershipProvider"].GetUser(UserName,false);

if (Myuser != null)

{

pass = Myuser.ResetPassword(passwordanswer);

}

!!!File web.config for this example

<membershipdefaultProvider="DefaultMembershipProvider">

<addname="DefaultMembershipProvider"

connectionStringName="ConnectionString"

applicationName="DefaultMembershipProvider"

enablePasswordRetrieval="false"

enablePasswordReset="true"

requiresQuestionAndAnswer="true"

requiresUniqueEmail="false"

passwordFormat="Hashed"

type="System.Web.Security.SqlMembershipProvider"

maxInvalidPasswordAttempts="7"

<addname="AdminMembershipProvider"

connectionStringName="ConnectionString"

applicationName="MyMembership"

enablePasswordRetrieval="false"

enablePasswordReset="true"

requiresQuestionAndAnswer="false"

requiresUniqueEmail="false"

passwordFormat="Hashed"

type="System.Web.Security.SqlMembershipProvider" />

</providers>

You can use 2 membership provider for same asp.net web application.

10 Minutes to Your Google Sitemap...

10 Minutes to Your Google Sitemap...

by: Ron Hutton

Copyright 2005 Ron Hutton

Google's calling your name...

Hi, Google here. We want to index your website...

Is anyone there?

This article has a free corresponding online video tutorial that shows you how to summons the magic Googlebot to spider and index every page on your website, and it will only take about 10 minutes of your time.

Go here now to watch exactly what to do, step-by-easy-step...

http://www.gothrive.com/google-sitemap-video.htm

What you have access to with the new Google Sitemaps program is truly a gift from the Google gods. They've offering you a tool that you can use to keep your site constantly indexed and updated in the search engine database. With Google Sitemaps, webmasters can now take charge and make sure that their entire site is crawled and indexed.

One important note to make is that the Google Sitemaps program will not necessarily improve the ranking of your site's pages. It only ensures that Google knows what you've got online for them to look at.

Before reading the following statement, promise yourself that you won't stop reading if you see a term that seems a little scary. OK? Promise? Good. Go ahead and keep reading then.

The format specified by Google for "their" sitemap is XML (extensible markup language). Did I loose you yet? No? Good again.

You do not need to understand how to code XML to participate in the Google Sitemap program. There are plenty of free online tools that will create your XML sitemap for you with no XML knowledge required on your part. More on this in a second.

What information is including in this XML sitemap?

1) The URL for every file on your website.

2) A relative priority rank that you can assign telling Google which pages on your site are most important for them to look at.

3) The date last modified for each page.

4) Anticipated change frequency per URL. This again is a variable that you control.

According to Google, your XML sitemap can include up to 50,000 URL's. If your site is a real monster and has in excess of 50,000 URL's, then you'll need to create a hierarchy of sitemaps with one leading to the next. This way you'll be able to lead Google to all of your pages.

The options for generating and maintaining your Google Sitemap range from complex systems that are highly automated to very simple systems using online sitemap generators that require nothing more than clicking a few buttons.

Google now keeps a list of these 'third party suppliers' of generators on their site. Find them here: http://code.google.com/sm_thirdparty.html

The program that's demonstrated in our free video tutorial (http://www.gothrive.com/google-sitemap-video.htm) is found here: http://www.auditmypc.com/free-sitemap-generator.asp

In a nutshell, here are the steps involved with using online generators:

1) Start the program.
2) Enter your site's URL
3) Click the "Start Crawling" button
4) Customize URL priorities and change frequencies
5) Save the site map to your local hard drive
6) Upload your new Google XML sitemap to your website in the root directory (where your home page resides)
7) Validate your new sitemap
(can be done here: http://www.smart-it-consulting.com/internet/google/submit-validate-sitemap/)
8) Submit your XML sitemap to Google.

You can access the pages for the Google Sitemap program here: https://www.google.com/webmasters/sitemaps/login

8 steps in about 10 minutes. That's all there is to it.

One question that you might ask is whether or not you still need an HTML sitemap, and the answer is "Yes, you still need your conventional sitemap". XML sitemaps are not intended for human visitors. To see what I mean, take a look at the two following sitemaps:

HTML sitemap: http://www.gothrive.com/sitemap.html

XML sitemap: http://www.gothrive.com/sitemap.xml

Which version do you prefer? Your visitors will like the HTML and Google prefers XML.

When you add pages or new content to your site and you want Google to go back to have a fresh look, just log in to your Google Sitemaps control panel, select the sitemap to revisit, and click "Resubmit". It's never been easier to get Google to spider and index a website. Don't miss your opportunity to use this tool to your advantage.

About the author:
Ron Hutton is a 20 year sales and marketing veteran with a passion for coaching and training. Subscribe to "GoThrive Online", for big juicy marketing tips in small, easy-to-chew, bite size servings. Free Video Tutorial Archives Here: http://www.gothrive.com/free-video-library/video-directory.html

1 2

> >>|

Software Development

News List

Software application development ways