when the connection is successfully connected (means if only the user logged into the sql server)need to show the message "successfully logged on".
not just the connection opened before the server validate the user.
could any one help me with this..
Our organization is currently developing an SDLC process for managing development projects. Would anyone be willing to share what your organization is currently doing?
What we are looking for is when our development department is approached with a project, we want to first deliver to the requestor an SDLC type statement of work where everything is outlined and the proceedure that we will follow.
Before going throught the hassle of creating ours from cradle to grave I was hoping to see what others have already created?
More specifically I work in a application design department that designs in c#. They have just now decide to provide application development and are now in the process of defining the process that we will use to develop.
I'm tasked with coming up with the SDLC and also the way to document it (i.e. paperwork, statement of work, contract) that we give to the deparment that is requesting development.
There are a lot of different lifecycle models to choose from and each one has pros and cons.
Do you currently have any level of process in place that governs how software projects are run? It doesn't have to be something formally documented. If so, try to pick a model that resembles that process as close as possible and then refine the model from there.
The main thing is that no model is perfect and no model will completely fit your business without modification (to either the business, the model, or both).
In general, the documentation steps that should be followed are:
Define the business requirements (high level, business-oriented requirements). This is what the software needs to do, problems it needs to solve, etc. in order for it to be competitive in the market.
Define the technical requirements for each business requirement. The technical requirements define how the business requirement will be met by the software. Each business requirement can map to one or more technical requirement, but generally one technical requirement should map to one business requirement. This also should cover any integration points to other systems that might be needed.
(Optional)Define a lower-level set of technical requirements that map to a single higher-level technical requirements. Again, one high-level technical requirement could have multiple lower-level technical requirements.
The developers would work from one of the technical requirement docs. The QA group would base their test plans on the buisness requirements, and the test plans should be written at the same time as the business requirements.
As for actual development cycles, there are many different models and you should choose the one that works the best for you. I have found that the best approach is using short cycles (3-4 weeks each). Each cycle has a clearly defined set of goals and requirements that need to be met. At the end of the cycle, everything is reviewed and things that didn't get completed become part of the next cycle. This allows the business stakeholders to see progress and everyone to evaluate that progress against the business needs early enough where changes and/or rework aren't as painful. (They will always be painful, but it's much easier to loose a few weeks worth of work than a few months.)
The bottom line is that you need to evaluate all of the different models and make the best choice you can. Then figure out what pieces of the model and/or business need to be modified or adapted to work for you. It may be a trial-and-error process until you get things right, but as long as you're not constantly changing tactics every few days (or even few weeks) it shouldn't be a problem.
The key to a process is that you want to build something that allows for consistent repeatability.
Another thing to consider is that SDLC processes should also include things like how QA testing is performed, how builds are performed (automated builds are the best), and how the software is released.
Scott. —In just two days, tomorrow will be yesterday.
in my application i use sql server login and i want to verify whether the connection successfully built.to do this as one of you freinds said i tried connection.state, now i get the response but not the correct one,even wrong username/password it gives successfully logged.(means always dd.getconstate give open)
i created a DBconnection class
private SqlConnection SQLCON;
private SqlCommand sqlcommand;
private ConnectionState gg = new ConnectionState() ;
public void openConnection(string usr, string pwd)
SQLCON = new SqlConnection();
sqlcommand = new SqlCommand();
SQLCON.ConnectionString = "user id =" + usr + "password="
+ pwd+ "encrypt=true;" + ";integrated security = true;" + "
initial catalog = my;" + " data source =buddhika\\SQLEXPRESS";
i am working in windows application of C#
i am using hash table.
i want to add data to hash table from datatable named DTSchool. I have a school name in combobox. when iselect school in combo it takes the curresponding SchoolID from the datatable
i want to know how to write code for that. i wrote like this
.But it is not taking value from datatable.Please help me regarding this problem?
Do you mean create a file association so that when you double click on an mp3 it opens with WMP11? If so, that requires some registry hacking - check here[^]; this article simplifies things a bit by providing a wrapper for the registry nastiness
Last Visit: 31-Dec-99 18:00 Last Update: 1-Oct-23 8:18